[dkropachev]

Issue

In #2, completion-only agent messages could become blocking Reply requests when question classification failed or a daemon restarted during an unfinished check. Those synthetic requests could remain pending after later successful work.

Fixes #2

Fix

Require positive evidence of an unanswered question before creating text fallback. Classifier failures ask the original retained agent for question-only clarification in Plan mode with read-only access and no approvals. Clarification and native-form repair share a durable budget of at most two automatic turns; unconfirmed results retain diagnostics without adding attention or continuing the task.

Recheck ambiguous legacy requests at startup and after later successful turns. Retire only matching requests positively classified as obsolete, while preserving genuine unanswered questions, explicitly nonblocking delivery, approvals, and claimed answers. Owner takeover invalidates late recovery callbacks. The UI shows clarification progress and its shared attempt count without false attention badges.

Keep one current answer route for recovered async questions across process loss and restart. Retire matching obsolete synthetic requests atomically while retaining their history, and preserve final originating claims when delivery is uncertain. A live repair answer completes its turn before continuation restores the original task policy.

Claim retained-agent setup attempts durably from the shared recovery budget. Setup failure consumes its claim; successful setup reuses it for the first question-only turn. Only remaining budget permits automatic retries. Preserve takeover cancellation before turn delivery and use later owner-directed work as evidence for legacy rechecks.

Reconcile the attention, recovery, interaction, and UI contracts with the implementation and regression assertions.

Run push checks only on main and verify feature work through pull requests to main. Main push before/after and PR event base/head comparisons, fixture verification, and successful-main-push release provenance remain unchanged. Feature branches without an open PR receive no automatic push checks. Manual dispatch keeps its existing parent comparison and receipt-base limitation.

Decisions

• Choice: Run CI on main pushes and pull requests to main. Feature branches without an open PR receive no automatic push checks. Keep exact main-push before/after and PR event base/head comparisons, fixture verification, and successful-main-push release provenance unchanged. Manual dispatch keeps its current parent comparison and receipt-base limitation. Use this smallest workflow/documentation change to resolve the conflicting feature-push and PR receipt bases.
• Choice: Keep one current answer route for each recovered async question across restart. Retire only matching obsolete synthetic requests atomically with resolution events and retain their history. Claim the originating question once before delivery; uncertain delivery must not reopen it or let a sibling request deliver another answer. Preserve its delivery status and originating recovery attempt count. Complete this correction in this PR to satisfy the original async-question and answer-claim preservation requirements.