fix(inbox): answering an agent's question or its blocked task resolves both (v0.455.1)

[vikasprogrammer]

Problem

A run that asks and then parks its task blocked raises two Inbox cards for one decision — "needs your input" and "task blocked — needs you" — and they were not linked. Answering the question left the task blocked (card open); unblocking the task left the question pending. On the live case (instapods tsk_5f40…) the answer was also lost: the human answered 3s after the run parked the task, its pane was still up, so answerQuestion assumed a live asker would poll — but the run had stopped waiting and ended.

Fix

• Answer → task: answering (Inbox/DM/durable default) files Answered: … on the task the run left blocked, returns it to the board (blocked card closes via syncTaskBlockedCards), and delivers by dispatching the task with the Q/A as extra — retrying every 15s (≤5 min) while the asking pane winds down, falling back to the wake queue only if it never goes. Not via the wake queue first: its resume is invisible to the one-live-run guard.
• Task → question: a human moving a task off blocked settles the run's pending questions (resolveTaskQuestions) — the card's note is the answer, no note cancels. TaskNotice now carries the note filed in the same update.
• Not linked: an agent leaving its own block; a park behind unfinished dependencies.

Tests

scripts/ask-block-link-test.cjs (14 checks, 8 fail on main), added to test:governance. Full suite green.

🤖 Generated with Claude Code