ticket: record spawn launcher blocker

.yoi/tickets/00001KVZKST83/item.md

@@ -2,7 +2,7 @@
 title: 'worker-runtimeにFS永続化featureを追加する'
 state: 'inprogress'
 created_at: '2026-06-25T14:44:02Z'
-updated_at: '2026-06-25T16:55:50Z'
+updated_at: '2026-06-25T16:58:41Z'
 assignee: null
 queued_by: 'workspace-panel'
 queued_at: '2026-06-25T16:39:26Z'

.yoi/tickets/00001KVZKST83/thread.md

@@ -132,3 +132,26 @@ Dependency `00001KVZBCQH4` worker-runtime core は done。Ticket body / relation
 これ以降、worktree creation / coder Worker routing などの implementation side effect に進める。
 
 ---
+
+<!-- event: implementation_report author: yoi-orchestrator at: 2026-06-25T16:58:41Z -->
+
+## Implementation report
+
+Implementation startup blocked after acceptance:
+
+- Worktree created:
+  - `/home/hare/Projects/yoi/.worktree/00001KVZKST83-worker-runtime-fs-store`
+  - branch `work/00001KVZKST83-worker-runtime-fs-store`
+- Coder Worker was not spawned because the immediately preceding SpawnPod attempt for parallel accepted Ticket `00001KVZKSV6C` failed with:
+  - `yoi: unknown command pod`
+
+Interpretation:
+- No implementation code changes have been made in this worktree yet.
+- This appears to be the same runtime/launcher compatibility issue after the Pod→Worker CLI rename.
+- Because this Ticket was already accepted (`queued -> inprogress`) and worktree creation completed, it remains inprogress with a recovery note rather than being silently returned to queued.
+
+Recovery needed:
+- Restart/restore Orchestrator on a consistent runtime binary or repair the launcher compatibility path, then spawn the Coder Worker for this accepted worktree.
+- If retry remains impossible, use an explicit human-authorized alternative implementation route.
+
+---

.yoi/tickets/00001KVZKSV6C/item.md

@@ -2,7 +2,7 @@
 title: 'Backend RuntimeRegistryの基盤をworker-runtime向けに整理する'
 state: 'inprogress'
 created_at: '2026-06-25T14:44:03Z'
-updated_at: '2026-06-25T16:55:16Z'
+updated_at: '2026-06-25T16:58:32Z'
 assignee: null
 queued_by: 'workspace-panel'
 queued_at: '2026-06-25T16:31:28Z'

.yoi/tickets/00001KVZKSV6C/thread.md

@@ -150,3 +150,28 @@ Dependency `00001KVZBCQH4` worker-runtime core は done。Ticket body / relation
 これ以降、worktree creation / coder Worker routing などの implementation side effect に進める。
 
 ---
+
+<!-- event: implementation_report author: yoi-orchestrator at: 2026-06-25T16:58:32Z -->
+
+## Implementation report
+
+Implementation startup blocked after acceptance:
+
+- Worktree created:
+  - `/home/hare/Projects/yoi/.worktree/00001KVZKSV6C-backend-runtime-registry`
+  - branch `work/00001KVZKSV6C-backend-runtime-registry`
+- Coder Worker spawn attempted:
+  - `yoi-coder-00001KVZKSV6C-runtime-registry`
+- Spawn failed before child socket appeared:
+  - `yoi: unknown command pod`
+
+Interpretation:
+- No implementation code changes have been made in this worktree yet.
+- This appears to be a runtime/launcher compatibility issue after the Pod→Worker CLI rename: the SpawnPod tool path attempted to invoke a `pod` subcommand that the child-launch binary rejected.
+- Because this failure happened after `queued -> inprogress` acceptance and worktree creation, the Ticket remains inprogress with a recovery note rather than being silently returned to queued.
+
+Recovery needed:
+- Restart/restore Orchestrator on a consistent runtime binary or repair the launcher compatibility path, then retry Coder Worker spawn for this accepted worktree.
+- If retry remains impossible, use an explicit human-authorized alternative implementation route.
+
+---