ticket: close orchestrator diagnostic persistence

.yoi/tickets/closed/20260607-095142-workspace-orchestrator-spawn-diagnostic-persistence/item.md

@@ -2,13 +2,13 @@
 id: 20260607-095142-workspace-orchestrator-spawn-diagnostic-persistence
 slug: workspace-orchestrator-spawn-diagnostic-persistence
 title: Keep workspace Orchestrator spawn diagnostics visible
-status: open
+status: closed
 kind: task
 priority: P2
 labels: [tui, panel, orchestrator, diagnostic]
-workflow_state: intake
+workflow_state: done
 created_at: 2026-06-07T09:51:42Z
-updated_at: 2026-06-07T10:15:40Z
+updated_at: 2026-06-07T10:16:08Z
 assignee: null
 legacy_ticket: null
 ---

.yoi/tickets/closed/20260607-095142-workspace-orchestrator-spawn-diagnostic-persistence/resolution.md

@@ -0,0 +1,24 @@
+Implemented, reviewed, merged, and validated.
+
+Summary:
+- Added panel/app state to retain the latest actionable workspace Orchestrator lifecycle failure.
+- Subsequent `Observe` refreshes that only report plain `missing` / `stopped` keep the prior actionable diagnostic visible.
+- Stale diagnostics are cleared when Orchestrator becomes `live`, `spawned`, or `restored`.
+- New `Unavailable` lifecycle diagnostics supersede older failures.
+- Orchestrator scope policy was unchanged.
+- `Observe` refresh still does not retry spawn.
+- Ticket actionbar gate messages remain separate from Orchestrator lifecycle diagnostics.
+
+Implementation:
+- Child commit: `e15e9b7 fix: persist orchestrator lifecycle diagnostics`
+- Merge commit: `merge: orchestrator diagnostic persistence`
+
+Review:
+- External reviewer `orchestrator-diagnostic-reviewer-20260607` approved with no blockers.
+
+Validation after merge:
+- `cargo test -p tui multi_orchestrator --lib`
+- `cargo test -p tui --lib`
+- `cargo fmt --check`
+- `git diff --check`
+- `target/debug/yoi ticket doctor`

.yoi/tickets/closed/20260607-095142-workspace-orchestrator-spawn-diagnostic-persistence/thread.md

@@ -150,4 +150,45 @@ Reviewer validation:
 - `CARGO_TARGET_DIR=/tmp/yoi-review-target cargo run -p yoi -- ticket doctor`
 
 
+---
+
+<!-- event: state_changed author: hare at: 2026-06-07T10:16:08Z from: intake to: done reason: closed field: workflow_state -->
+
+## State changed
+
+Ticket closed; workflow_state set to done.
+
+
+---
+
+<!-- event: close author: hare at: 2026-06-07T10:16:08Z status: closed -->
+
+## Closed
+
+Implemented, reviewed, merged, and validated.
+
+Summary:
+- Added panel/app state to retain the latest actionable workspace Orchestrator lifecycle failure.
+- Subsequent `Observe` refreshes that only report plain `missing` / `stopped` keep the prior actionable diagnostic visible.
+- Stale diagnostics are cleared when Orchestrator becomes `live`, `spawned`, or `restored`.
+- New `Unavailable` lifecycle diagnostics supersede older failures.
+- Orchestrator scope policy was unchanged.
+- `Observe` refresh still does not retry spawn.
+- Ticket actionbar gate messages remain separate from Orchestrator lifecycle diagnostics.
+
+Implementation:
+- Child commit: `e15e9b7 fix: persist orchestrator lifecycle diagnostics`
+- Merge commit: `merge: orchestrator diagnostic persistence`
+
+Review:
+- External reviewer `orchestrator-diagnostic-reviewer-20260607` approved with no blockers.
+
+Validation after merge:
+- `cargo test -p tui multi_orchestrator --lib`
+- `cargo test -p tui --lib`
+- `cargo fmt --check`
+- `git diff --check`
+- `target/debug/yoi ticket doctor`
+
+
 ---