ticket: defer role launch input routing

.yoi/tickets/00001KTVPS6K3/artifacts/orchestration-plan.jsonl

@@ -0,0 +1 @@
+{"id":"orch-plan-20260612-091119-1","ticket_id":"00001KTVPS6K3","kind":"waiting_capacity_note","note":"Workspace Panel Queue notification was received, but this Orchestrator cannot safely accept implementation yet. The Orchestrator Ticket backend still reads the Ticket as `ready`, while the root workspace has unsynced/uncommitted queued Ticket changes for `00001KTVPS6K3`; root workspace is dirty (`.yoi/tickets/00001KTVPS6K3/*` plus `crates/tui/src/multi_pod.rs`). Current active work `00001KTWPE3KQ` is also in review and is specifically fixing the Panel Queue durable handoff/sync path. Re-route this Ticket after the Queue handoff is safely synced/committed and active review/merge state is clear.","author":"orchestrator","at":"2026-06-12T09:11:19Z"}

.yoi/tickets/00001KTVPS6K3/item.md

@@ -2,7 +2,7 @@
 title: 'Ticket role launch inputを短縮し、role behaviorをInstruction/Workflowへ分離する'
 state: 'ready'
 created_at: '2026-06-11T16:03:28Z'
-updated_at: '2026-06-11T16:03:33Z'
+updated_at: '2026-06-12T09:11:30Z'
 assignee: null
 risk_flags: ['prompt-context', 'workflow-boundary', 'role-launch']
 ---

.yoi/tickets/00001KTVPS6K3/thread.md

@@ -21,3 +21,30 @@ Ticket role launch の初回 user message を短縮し、情報所管を Instruc
 要件・受け入れ条件・境界判断が揃ったため、Orchestrator routing 可能。実装はユーザーが panel で queue した後に開始する。
 
 ---
+
+<!-- event: decision author: orchestrator at: 2026-06-12T09:11:30Z -->
+
+## Decision
+
+Routing decision: blocked_by_dependency_or_missing_authority
+
+Reason:
+- Workspace Panel Queue notification was received, but this Orchestrator backend still reads the Ticket as `ready`, not `queued`.
+- The root workspace has unsynced/uncommitted queue-related changes for this Ticket and is dirty, including `.yoi/tickets/00001KTVPS6K3/*` and `crates/tui/src/multi_pod.rs`.
+- Active in-progress work `00001KTWPE3KQ` is currently fixing the Panel Queue durable handoff/sync path and is in reviewer handoff; accepting this new Ticket before that path is reviewed/merged would require manual sync/queue recovery and could mix queue-side effects with unrelated dirty root changes.
+
+Evidence checked:
+- TicketShow `00001KTVPS6K3`: Orchestrator backend state is `ready`.
+- TicketRelationQuery: no relation blockers.
+- TicketOrchestrationPlanQuery: no prior plan records before this routing note.
+- Root/orchestrator git state: Orchestrator branch has local routing record changes; root workspace is dirty with this Ticket's `.yoi` files and `crates/tui/src/multi_pod.rs`.
+- Visible Pods: active reviewer `yoi-reviewer-panel-queue-sync` for `00001KTWPE3KQ`.
+
+Next action:
+- Leave this Ticket unaccepted for implementation in this Orchestrator pass.
+- Re-route after the Panel Queue durable handoff work is resolved and the root/orchestration Ticket state is synchronized cleanly, or after a human explicitly instructs manual recovery for the queued root-side changes.
+
+Escalate if:
+- The queued root-side changes should be manually committed/synced despite the current dirty workspace and active Queue-handoff fix.
+
+---