ticket: hold knowledge removal for workflow cleanup

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

@@ -0,0 +1,2 @@
+{"id":"orch-plan-20260715-202731-1","ticket_id":"00001KXKP2A71","kind":"after","related_ticket":"00001KXKJGYGD","note":"この Ticket は Knowledge removal 自体には blocker relation がないが、現在 `00001KXKJGYGD` が inprogress で Workflow tracking/resource removal を実装中。両者は `crates/worker` prompt/context、`crates/protocol`/session item、resource/docs cleanup、および Workflow required Knowledge dependency 周辺で重なる。Ticket body も Workflow required Knowledge dependency は Workflow removal 側で消える前提としているため、`00001KXKJGYGD` の review/merge/close 後に開始する。","author":"orchestrator","at":"2026-07-15T20:27:31Z"}
+{"id":"orch-plan-20260715-202739-2","ticket_id":"00001KXKP2A71","kind":"waiting_capacity_note","note":"Queue routing inspected. `00001KXKP2A71` is concrete and has no typed blocker relation, but it should not be started in parallel with active `00001KXKJGYGD`: both remove old context/resource machinery and likely touch shared prompt/context/session/protocol/resource/docs surfaces. Running both now would create conflict and review-boundary risk. Leave queued until `00001KXKJGYGD` is approved/merged/closed, then re-route Knowledge removal before Skills support `00001KXKMX0QM`.","author":"orchestrator","at":"2026-07-15T20:27:39Z"}

.yoi/tickets/00001KXKP2A71/item.md

@@ -2,7 +2,7 @@
 title: 'Remove Knowledge support'
 state: 'queued'
 created_at: '2026-07-15T20:04:08Z'
-updated_at: '2026-07-15T20:27:02Z'
+updated_at: '2026-07-15T20:27:51Z'
 assignee: null
 queued_by: 'workspace-panel'
 queued_at: '2026-07-15T20:27:02Z'

.yoi/tickets/00001KXKP2A71/thread.md

@@ -30,4 +30,38 @@ Marked ready by `yoi ticket state`.
 Ticket を `workspace-panel` が queued にしました。
 
 
+---
+
+<!-- event: decision author: orchestrator at: 2026-07-15T20:27:51Z -->
+
+## Decision
+
+Routing decision: hold_queued_due_conflict_with_active_removal_work
+
+Reason:
+- Dashboard queue authorization was inspected, and this Ticket is concrete with no outgoing blocker relation。
+- However, `TicketList(inprogress)` shows active Ticket `00001KXKJGYGD` (`Remove workflow tracking and workflow resources`) currently in implementation with Coder Pod running。
+- This Knowledge removal Ticket and Workflow removal Ticket likely touch overlapping surfaces:
+  - `crates/worker` prompt/context/resident injection paths。
+  - `crates/protocol` / `crates/session-store` reference/system-item state paths。
+  - resource cleanup under prompts/resources/docs。
+  - Workflow required Knowledge dependency, which this Ticket body explicitly says is expected to disappear via Workflow removal。
+- Starting this Ticket now would create avoidable merge conflicts and make reviewer acceptance boundaries ambiguous。
+- Therefore this pass leaves the Ticket `queued` and does not record `queued -> inprogress`, create a worktree, or spawn role Pods。
+
+Evidence checked:
+- Ticket body / thread / relations。
+- `TicketRelationQuery(00001KXKP2A71)`: incoming `depends_on` from Skills support Ticket `00001KXKMX0QM`; no blocker for this Ticket。
+- `TicketOrchestrationPlanQuery(00001KXKP2A71)`: no prior records; recorded `after 00001KXKJGYGD` and waiting note in this pass。
+- `TicketList(inprogress)`: `00001KXKJGYGD` active。
+- Orchestrator worktree status and worktree list: active Workflow removal worktree exists。
+- Visible Pods: Workflow removal Coder Pod is running。
+
+Next action:
+- Wait for `00001KXKJGYGD` to be reviewed, merged, validated, and closed。
+- Then re-route `00001KXKP2A71` before starting dependent Skills support `00001KXKMX0QM`。
+
+Escalate if:
+- Human explicitly wants Knowledge removal and Workflow removal combined in one branch/worktree, or accepts parallel conflict/review-boundary risk。
+
 ---