fix(coding-agent): answer ACP prompts only once the session admits the next turn

[parkerpettit]

ACP could answer session/prompt after its first idle check even though injected work had restarted the session. An immediate follow-up was then rejected as Agent is already processing.

Without this change:

1. The current ACP turn finishes.
2. waitForHeadlessCompletion() observes an idle session.
3. Injected work, such as a subagent message, starts another turn.
4. ACP returns end_turn.
5. The client sends its next prompt and Prime Agent rejects it because the session is busy.

Re-check connection.waitForIdle() before returning the ACP response. This closes the admission race seen in multi-turn Verifiers runs.

#881 fixes a different gap: waitForIdle() did not include a continuation already scheduled by compact.run. One makes the idle check complete; this PR puts a final check at the response boundary.

Verification:

• ACP response waits for the final admission check
• an immediate second prompt is accepted

Note

Queue ACP follow-up prompts behind in-flight work instead of rejecting

• ACP session/prompt requests now pass queueIfBusy: true so they wait behind ongoing injected work rather than immediately failing with a busy error.
• A cancellation signal is threaded from the request's AbortController through to promptAndWait, allowing a queued-but-not-yet-started prompt to be dropped when session/cancel is received.
• AgentDaemon now calls admission.controller?.abort() when cancelling a session-owned admission, wiring the abort signal through to the queued action.
• Behavioral Change: ACP callers that previously received an immediate busy rejection will now have their request queued; they must cancel explicitly to abort a queued prompt.

^{Macroscope summarized bf2c00e.}

---

Note

Medium Risk
Changes daemon worker lifecycle, persisted launch environment, and ACP turn-boundary semantics that verifiers and embedders depend on; behavior is heavily tested but mis-timed idle or env handling could still break reconnect or scoring.

Overview
ACP session/prompt now awaits connection.waitForIdle() before returning end_turn, so clients are not told the turn finished while injected work (e.g. subagent messages) has already restarted the session and would reject an immediate follow-up with “Agent is already processing.”

ACP session lifecycle and scoring metadata: session/new reserves the single-session slot before the first await, subscribes before getInitialSnapshot(), and fails setup cleanly if the snapshot read errors. After headless completion, a session_info_update carries namespaced quiescence (outstandingSubagents, remainingAutonomousContinuations) plus autonomous state from a live roster snapshot; snapshot failures at emission time propagate instead of reporting a false zero.

Daemon / ACP residency: Normal ACP sessions (with a session file) use resident workers so disconnect/reconnect can reattach; --no-session ACP stays client-owned. Resident creates always forward launchEnv from the caller (model endpoint, tokens, proxy, etc.). The supervisor persists launchEnv on resident worker descriptors for recovery after restart and strips it when promoting to client-owned, with integration tests for env across worker recovery and live IPython namespace across ACP reconnect.

^{Reviewed by Cursor Bugbot for commit ac97743. Bugbot is set up for automated code reviews on this repo. Configure here.}

[snimu]

Missing CHANGELOG entry: this fixes a user-visible ACP race (immediate follow-up prompt rejected with "Agent is already processing"). Please add a bullet under ## [Unreleased] in packages/coding-agent/CHANGELOG.md.

[parkerpettit]

Reworked per review: ACP prompts now queue behind in-flight work (streamingBehavior: "followUp", queueIfBusy: true) instead of waiting for whole-session idleness; the final waitForIdle() is removed, so the stop reason comes from the status captured after the turn the response gates and the response is never held open by detached work. Regression tests inject real work after the first idle observation; CHANGELOG entry added.