616d6c5432
reconcileBusyStatesOnReconnect downgraded stale busy/awaiting claims by writing the $sessionStates mirror directly. The claim has four holders — the wiring cache, that mirror, the focused view's draft $busy / $awaitingResponse, and busyRef — and only the write path (the delegate's updateSessionState) keeps them in lockstep. After a reconnect that orphans a mid-turn runtime (a respawned backend re-mints runtime ids, so the terminal busy:false never arrives) the mirror cleared but the composer stayed latched: Send failed isTargetSessionBusy and silently no-oped until restart, and warm resume could OR the stale cache copy back over the backend's running:false. - SessionTileDelegate.retireBusyClaim?: optional twin of invalidateRuntimeBindings; writes through updateSessionState, returns false (and writes nothing) for a runtime the cache never held. - reconcileBusyStatesOnReconnect routes each in-scope downgrade through it, keeps the mirror publish as the fallback, and on a primary reconcile also clears the focused draft latches. Scoped reconciles leave the composer alone. Tests: hook (real useGatewayBoot + fake socket), store (write-path route, miss fallback, primary vs scoped), cache (real updateSessionState) and delegate (hit/miss) — RED on main, GREEN here. Full desktop UI suite, typecheck and lint pass. Written with LLMs under human direction: initial report and diagnosis by GPT-5.6 (OpenAI Codex); root-cause refinement, design and review by Claude Fable 5; implementation and tests by Claude Opus 5. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>