ticket: route panel nonblocking transitions preflight

.yoi/tickets/open/20260606-233520-workspace-panel-nonblocking-transitions/item.md

@@ -7,13 +7,12 @@ kind: task
 priority: P2
 labels: [tui, panel, ux, performance]
 created_at: 2026-06-06T23:35:20Z
-updated_at: 2026-06-06T23:36:10Z
+updated_at: 2026-06-07T22:36:33Z
 assignee: null
 legacy_ticket: null
-workflow_state: intake
-attention_required: null
-queued_by: null
-queued_at: null
+workflow_state: queued
+queued_by: workspace-panel
+queued_at: 2026-06-07T22:36:07Z
 ---
 
 ## Background

.yoi/tickets/open/20260606-233520-workspace-panel-nonblocking-transitions/thread.md

@@ -23,4 +23,70 @@ Desired direction:
 - especially make return-from-attach redraw the previous panel immediately and refresh in the background.
 
 
+---
+
+<!-- event: intake_summary author: intake at: 2026-06-07T22:30:10Z -->
+
+## Intake summary
+
+Existing Ticket refined sufficiently for routing. Request is to make `yoi panel` transition paths non-blocking: return from nested Pod should redraw the previous panel immediately and refresh in background; Pod open/attach should show attaching/restoring progress before socket/restore waits; initial panel load should avoid blocking first draw on non-essential snapshot/Orchestrator observation where practical. Acceptance criteria and non-goals are already explicit. Readiness: implementation_ready. needs_preflight: true because this touches async TUI lifecycle, background reload guarding, Pod attach/restore UX, and Orchestrator observation timing while preserving Ticket workflow and Pod authority semantics. risk_flags: [tui-lifecycle, async-reload, pod-attach, orchestrator-observation].
+
+---
+
+<!-- event: state_changed author: intake at: 2026-06-07T22:30:10Z from: intake to: ready reason: intake_ready field: workflow_state -->
+
+## State changed
+
+Intake found the existing Ticket specific enough for Orchestrator routing. No duplicate Ticket was created; implementation must still preserve Ticket workflow semantics and Pod restore/spawn authority.
+
+---
+
+<!-- event: decision author: hare/intake at: 2026-06-07T22:35:08Z -->
+
+## Decision
+
+Scope clarification requested by user:
+
+Panel-originated Pod launch/restore/open dispatch is explicitly in scope for this Ticket when the issue is visible blocking before feedback. Pressing the panel action to launch, restore, open, or attach a Pod should enter a visible progress/transition state such as `launching`, `restoring`, or `attaching` before awaiting runtime socket connect, restore, or spawn work.
+
+This clarification is about non-blocking UX and progress/error surfacing for the dispatch path. It does not expand the Ticket to redesign role launch policy, Ticket workflow semantics, Orchestrator scheduling, Pod authority, or automatic coder/reviewer startup.
+
+---
+
+<!-- event: state_changed author: workspace-panel at: 2026-06-07T22:36:07Z from: ready to: queued reason: queued field: workflow_state -->
+
+## State changed
+
+Ticket queued for Orchestrator routing.
+
+
+---
+
+<!-- event: decision author: orchestrator at: 2026-06-07T22:36:33Z -->
+
+## Decision
+
+Routing decision: preflight_needed
+
+Reason:
+- The Ticket is specific and valuable, but it touches async TUI lifecycle boundaries: panel first draw, nested Pod return, background reload guarding, Pod attach/restore/spawn progress, and Orchestrator observation timing.
+- Intake explicitly marked readiness as implementation-ready only with `needs_preflight: true` and risk flags `[tui-lifecycle, async-reload, pod-attach, orchestrator-observation]` in the intake summary.
+- Several implementation choices can preserve or violate important invariants: no duplicate overlapping reload tasks, no dropped key input during progress states, no Ticket workflow semantic changes, and no Pod restore/spawn authority changes.
+
+Evidence checked:
+- Ticket body requirements, non-goals, acceptance criteria, and problem paths.
+- Thread plan, intake summary, user scope clarification for panel-originated launch/restore/open dispatch, and `ready -> queued` event.
+- Workspace state: `develop` is clean except this Ticket's queued item/thread updates; no existing worktree or branch for this slug.
+- Visible Pods: intake peer for this Ticket is idle; no implementation/review Pods are active for this Ticket.
+
+Next action:
+- Run `ticket-preflight-workflow` before implementation delegation.
+- Preflight should produce a concise design/authority note covering: which transition paths become background/progress states first, how `PendingReload` or equivalent prevents overlap, how selection/composer/input are preserved, what remains synchronous for correctness, and focused test strategy.
+- Do not transition `queued -> inprogress`, create `.worktree/workspace-panel-nonblocking-transitions`, or spawn coder/reviewer Pods until preflight records that the Ticket is implementation-ready.
+
+Escalate if:
+- Making initial panel first draw non-blocking requires a broader TUI runtime-loop rewrite.
+- Pod launch/restore progress state would require changing spawn/restore authority semantics.
+- Background reload cancellation/ordering needs a new durable scheduler or lease concept rather than a local UI guard.
+
 ---