This is the canonical approve-in-context rendering (finding #21C). One Needs-You gate,
magnified: the task's detail and its required-vs-delivered artifact panel render inline,
in the same place you approve — never a bare row + button. Every other approval surface (1a's
Needs-you count, the board's ▶
marker, task-detail's gate banner) cites this exact pattern, so getting the shape right here
keeps them all consistent.
Needs You yours only
DEV-1612test-results-approval
Heartbeat store — safety-gate write path. Advancing here moves the task to
in-development, recorded
changed_by=Nishad.
Required
PLAN
TEST
Commits
✔ Approve → in-development
↩ Send back…
critical gate — confirm step on approve
This is a critical gate, so clicking Approve opens a confirm step first (not shown here —
see after Approve for the outcome once confirmed). A failed
Approve call shows a loud error and this card stays exactly as-is — never a silent "approved."