fix(tui): keep process notifications out of agent turns

[iwillwill-ALLWILL]

Summary

• Keep process completion and watch notifications as UI/terminal status instead of synthetic agent user turns.
• Allow async delegation completions to auto-chain only when their opaque dispatch_turn_id still owns the current real user turn.
• Carry immutable turn identity through classic CLI, queued TUI prompts, inline TUI turns, compute-host isolation, goal follow-ups, and single/batch delegation producers.
• Preserve current owner-scoped routing, compression lineage, durable delivery claims, shutdown draining, and failure requeue behavior.

Reimplementation

This replaces the previous patch with a clean implementation on current main (b1fc65308). It addresses the sweeper feedback on both modern TUI delivery paths and adds the equivalent stale-delegation guard to classic CLI.

The implementation is fail-closed: missing, restored, or stale turn tokens may still surface as status, but cannot create a new agent turn.

Verification

• 504 passed across the affected CLI, goal, delegation, TUI gateway, queued-prompt, and compute-host suites.
• ruff check .
• python3 scripts/check-windows-footguns.py --all
• git diff --check
• staged secret/credential scan: no matches

Regression coverage

Includes coverage for:

• process/watch status-only delivery in live, shutdown, and post-turn paths;
• fresh vs stale delegation ownership;
• queued-user races and immutable turn capture;
• compute-host frame propagation and fail-closed empty tokens;
• claim failures, transport write failures, ack failures, and safe requeue/defer behavior;
• classic CLI goal/slash-command ownership;
• single and batch delegation producers.

[alt-glitch]

This was generated by AI during triage.

Related to the notify_on_complete/process-notification family: #35317 (queued input pollution), #41875 (CLI direct-display), #35667 (owner-scoped TUI routing), and the #15248 root issue. This PR takes a distinct angle — keeping background process completion/watch notifications as UI-only status (not synthetic user turns) while preserving async delegation completions as chainable follow-up turns. Not a duplicate; cross-linking so a maintainer can pick the canonical direction across this cluster.

[teknium1]

Thanks for isolating the process-notification/agent-turn boundary; the underlying behavior remains present on current main.

Problems

• Current main has diverged materially from this branch. TUI now applies owner and durable-delivery safeguards before dispatch in tui_gateway/server.py:8738-8815, with a separate post-turn injection path at tui_gateway/server.py:9418-9436. The change needs a manual port into both paths.
• The proposed CLI helper still queues every async_delegation event. That does not satisfy the PR's stated stale-delegation guarantee for classic CLI; current CLI likewise queues all drained notifications at cli.py:9190-9198.

Suggested changes

• Port the process-status split while retaining the current ownership and delivery-claim logic in both TUI paths.
• Either narrow the stale-delegation claim to TUI/Desktop or implement an equivalent CLI turn-ownership guard.

Automated hermes-sweeper review.