kami
92adf0477d
A running but empty server answers "no current target". hasSession only knew "can't find session", "no server running" and "no sessions", so it returned that as a real error. Kill then failed for a pane that was already gone, the quarantine never cleared, and the worker's only session slot stayed pinned. This is a side effect ofdea56e4. Before the runtime became its own unit the server exited with its last session and answered "no server running", which hasSession already handled, so this reply had never been produced. AgentStatus shares the same helper and now reports "exited" instead of erroring. Found live: the F28 disposable task's session survived its own block on93338b7, quarantined and unreapable. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011xsXyr5J1RACo71YeKG3Pu