ticket: accept next worker runtime branches

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

@@ -1 +1,2 @@
 {"id":"orch-plan-20260625-164354-1","ticket_id":"00001KVZKST83","kind":"blocked_by","related_ticket":"00001KVZBCQH4","note":"Queue routing checked after Dashboard Queue. FS store feature depends on worker-runtime core `00001KVZBCQH4`, which is currently inprogress and under review. Do not start FS persistence implementation until core API is reviewed/merged/done.","author":"yoi-orchestrator","at":"2026-06-25T16:43:54Z"}
+{"id":"orch-plan-20260625-165525-2","ticket_id":"00001KVZKST83","kind":"accepted_plan","note":"`00001KVZBCQH4` が done になり dependency blocker 解消。Backend Registry foundation Ticket とは主対象が `crates/worker-runtime` vs `crates/workspace-server` で分離できるため並行受理候補。ただし Cargo/package lock conflict は merge時に Orchestrator が解消する。","accepted_plan":{"summary":"worker-runtime core done 後の optional `fs-store` feature slice。core no-default-features を維持しつつ FS persistence backend、layout、atomic writes、bounded reads、corrupt diagnostics、memory/FS tests を追加する。REST/Backend integration は扱わない。","branch":"work/00001KVZKST83-worker-runtime-fs-store","worktree":"/home/hare/Projects/yoi/.worktree/00001KVZKST83-worker-runtime-fs-store","role_plan":"Orchestrator が dedicated child worktree を作成し、coder Worker に `crates/worker-runtime` と lock/package files の write scope を委譲する。reviewer Worker は read-only で feature gating、atomic/corrupt diagnostics、runtime_id+worker_id authority、no standalone worker-store を確認する。merge/validation/done/cleanup は Orchestrator が行う。"},"author":"yoi-orchestrator","at":"2026-06-25T16:55:25Z"}

.yoi/tickets/00001KVZKST83/item.md

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

.yoi/tickets/00001KVZKST83/thread.md

@@ -59,3 +59,76 @@ Escalate if:
 - FS feature を core Ticket に巻き戻す必要が出る。
 
 ---
+
+<!-- event: decision author: yoi-orchestrator at: 2026-06-25T16:55:42Z -->
+
+## Decision
+
+Routing decision: implementation_ready
+
+Reason:
+- `00001KVZBCQH4` worker-runtime core は done。dependency blocker は解消済み。
+- 本 Ticket は optional FS persistence feature であり、REST server / Backend Registry integration とは分離されている。
+- queued/inprogress 再確認時点で `00001KVZKSV6C` を受理したが、主変更面は Backend Registry foundation (`crates/workspace-server`) と FS feature (`crates/worker-runtime`) で分離できる。Cargo/package files の機械的 conflict は Orchestrator merge時に解消可能と判断する。
+
+Evidence checked:
+- Ticket body: `fs-store` feature、runtime/worker scoped layout、atomic write、corrupt diagnostics、bounded reads、Non-goals。
+- Relations: outgoing dependency `00001KVZBCQH4` は done。incoming remote Runtime Ticket は後続であり blocker ではない。
+- Orchestration plan: accepted plan `orch-plan-20260625-165525-2` を記録。
+- Workspace state: orchestration worktree clean。worker-runtime core merge/validation/done/cleanup 済み。
+
+IntentPacket:
+
+Intent:
+- `worker-runtime` に optional `fs-store` feature と filesystem persistence backend を追加する。
+
+Binding decisions / invariants:
+- Feature disabled 時に core library は FS store dependency を強制しない。
+- Store authority は `runtime_id + worker_id`。legacy pod path / socket path / session path を authority にしない。
+- Standalone `worker-store` crate は作らない。`worker-runtime` 内 feature/module として実装する。
+- REST command server / event stream / Backend integration / legacy Pod session migration / SQLite store は実装しない。
+- Existing memory store/core tests を壊さない。
+
+Requirements / acceptance criteria:
+- `fs-store` feature がある。
+- `cargo test -p worker-runtime --no-default-features` が通る。
+- `cargo test -p worker-runtime --features fs-store` が通る。
+- Worker create/state update/event append/transcript append/bounded read が FS store で動く。
+- Runtime/Worker scoped layout、atomic write、directory creation、corrupt/missing diagnostics を扱う。
+
+Implementation latitude:
+- FS layout、module split、serialization structs、atomic write helper、diagnostics typeの詳細は Coder が既存 style に合わせて選べる。
+- 旧 `pod-store` の atomic write pattern は参考にしてよいが、依存/責務移植は不要。
+
+Escalate if:
+- core Runtime store abstraction の大幅 rewrite が必要になる。
+- REST/Backend integration を同時実装しないと acceptance を満たせないと判明する。
+- `worker-store` standalone crate が必要に見える。
+
+Validation:
+- `cargo fmt --all`
+- `cargo test -p worker-runtime --no-default-features`
+- `cargo test -p worker-runtime --features fs-store`
+- `cargo check -p yoi`
+- `git diff --check`
+- 可能なら `nix build .#yoi --no-link`
+
+Critical risks / reviewer focus:
+- Feature gating failure causing core to pull FS dependencies。
+- FS layout leaking legacy Pod/session authority。
+- Atomic write / corrupt record handling が不十分。
+- Memory store semantics regression。
+
+---
+
+<!-- event: state_changed author: yoi-orchestrator at: 2026-06-25T16:55:50Z from: queued to: inprogress reason: routing_accepted_after_worker_runtime_core_done field: state -->
+
+## State changed
+
+Routing decision: implementation_ready。
+
+Dependency `00001KVZBCQH4` worker-runtime core は done。Ticket body / relations / workspace state / orchestration plan を確認し、optional FS store feature は unblocked と判断した。accepted plan と IntentPacket は thread / orchestration plan に記録済み。
+
+これ以降、worktree creation / coder Worker routing などの implementation side effect に進める。
+
+---

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

@@ -1 +1,2 @@
 {"id":"orch-plan-20260625-164410-1","ticket_id":"00001KVZKSTE2","kind":"blocked_by","related_ticket":"00001KVZBCQH4","note":"Queue routing checked after Dashboard Queue. REST command server depends on worker-runtime core `00001KVZBCQH4`, which is currently inprogress and under review. Do not start HTTP/server implementation until core API is reviewed/merged/done.","author":"yoi-orchestrator","at":"2026-06-25T16:44:10Z"}
+{"id":"orch-plan-20260625-165601-2","ticket_id":"00001KVZKSTE2","kind":"waiting_capacity_note","note":"Core dependency is now done, but this REST/http-server Ticket is left queued in this acceptance pass because FS store and Backend Registry foundation were accepted first. `http-server` is likely to modify `crates/worker-runtime` feature/dependency/package surfaces and conflict with FS store work; start after FS store branch stabilizes or Orchestrator explicitly serializes merge conflict handling.","author":"yoi-orchestrator","at":"2026-06-25T16:56:01Z"}

.yoi/tickets/00001KVZKSTE2/item.md

@@ -2,7 +2,7 @@
 title: 'worker-runtimeにREST command serverを追加する'
 state: 'queued'
 created_at: '2026-06-25T14:44:02Z'
-updated_at: '2026-06-25T16:44:20Z'
+updated_at: '2026-06-25T16:56:01Z'
 assignee: null
 queued_by: 'workspace-panel'
 queued_at: '2026-06-25T16:39:39Z'

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

@@ -1 +1,2 @@
 {"id":"orch-plan-20260625-163206-1","ticket_id":"00001KVZKSV6C","kind":"blocked_by","related_ticket":"00001KVZBCQH4","note":"Queue routing checked after Dashboard Queue. This Backend RuntimeRegistry foundation Ticket depends on `00001KVZBCQH4` worker-runtime core. That dependency is currently inprogress and only at coder implementation report stage, not reviewed/merged/done, so implementation side effects for this Ticket are blocked.","author":"yoi-orchestrator","at":"2026-06-25T16:32:06Z"}
+{"id":"orch-plan-20260625-165451-2","ticket_id":"00001KVZKSV6C","kind":"accepted_plan","note":"`00001KVZBCQH4` が done になり dependency blocker 解消。FS store Ticket とは主対象が workspace-server vs worker-runtime feature で分離できるため並行受理候補。","accepted_plan":{"summary":"worker-runtime core done 後の Backend RuntimeRegistry foundation slice。embedded/remote 実 handle は作らず、workspace-server の Registry identity/projection/error boundary と local compatibility source naming/diagnostics を worker-runtime domain model に合わせる。","branch":"work/00001KVZKSV6C-backend-runtime-registry","worktree":"/home/hare/Projects/yoi/.worktree/00001KVZKSV6C-backend-runtime-registry","role_plan":"Orchestrator が dedicated child worktree を作成し、coder Worker に `crates/workspace-server` 中心の narrow write scope を委譲する。reviewer Worker は read-only で Registry identity/projection/error boundary と existing API behavior preservation を確認する。merge/validation/done/cleanup は Orchestrator が行う。"},"author":"yoi-orchestrator","at":"2026-06-25T16:54:51Z"}

.yoi/tickets/00001KVZKSV6C/item.md

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

.yoi/tickets/00001KVZKSV6C/thread.md

@@ -80,3 +80,73 @@ Escalate if:
 - Backend Registry foundation 側で worker-runtime core の追加変更が必要になる。
 
 ---
+
+<!-- event: decision author: yoi-orchestrator at: 2026-06-25T16:55:09Z -->
+
+## Decision
+
+Routing decision: implementation_ready
+
+Reason:
+- `00001KVZBCQH4` worker-runtime core は done。dependency blocker は解消済み。
+- 本 Ticket の目的は Backend RuntimeRegistry foundation の整理で、embedded runtime 接続や REST/FS 実装そのものではない。
+- queued/inprogress 再確認時点で `inprogress` は 0 件。FS store Ticket とは主変更面が `crates/workspace-server` vs `crates/worker-runtime` feature で概ね分離できるため、本 Ticket は受理可能。
+
+Evidence checked:
+- Ticket body: Backend RuntimeRegistry foundation、runtime_id / worker_id authority、existing local compatibility source、workspace-server hosts/server target、Non-goals。
+- Relations: outgoing dependency `00001KVZBCQH4` は done。incoming dependent `00001KVZSGT0Q`, `00001KVZSGT14` は後続であり blocker ではない。
+- Orchestration plan: accepted plan `orch-plan-20260625-165451-2` を記録。
+- Workspace state: orchestration worktree clean。worker-runtime core merge/validation/done/cleanup 済み。
+
+IntentPacket:
+
+Intent:
+- Backend `RuntimeRegistry` の domain boundary を、legacy process/source abstraction から worker-runtime を受けられる形へ整理する。
+
+Binding decisions / invariants:
+- Backend Registry の authority は Runtime / Worker domain identity を扱い、raw socket/session/path/pod name を public authority にしない。
+- この Ticket では embedded `worker_runtime::Runtime` を実際に接続しない。handle/trait/enum/boundary と diagnostics/projection 整理まで。
+- Remote Runtime HTTP client / REST server / Web Console / dynamic Runtime registration は実装しない。
+- 既存 local compatibility source の behavior は壊さない。
+- `worker-runtime` core crate の API を大きく変更しない。必要になれば escalation。
+
+Requirements / acceptance criteria:
+- `workspace-server` の RuntimeRegistry foundation が worker-runtime 向けの identity / projection / error boundary を持つ。
+- Existing local/process compatibility source と将来 embedded/remote source の境界が型で分かる。
+- Browser/API response へ socket/session/path authority を露出しない。
+- Existing workspace-server tests が通る。
+
+Implementation latitude:
+- Type/module split、内部 trait/enum naming、diagnostic representation は既存 `crates/workspace-server/src/hosts.rs` の形に合わせてよい。
+- Minimal compile/test slice でよい。実 embedded handle は placeholder/boundary でよい。
+
+Escalate if:
+- `worker-runtime` crate の public API 変更が必要になる。
+- Backend embedded connection を実装しないと acceptance を満たせないと判明する。
+- API response schema 互換性や dashboard expectations を大きく変える必要がある。
+
+Validation:
+- `cargo fmt --all`
+- `cargo test -p yoi-workspace-server`
+- `cargo check -p yoi`
+- `git diff --check`
+- 可能なら `nix build .#yoi --no-link`
+
+Critical risks / reviewer focus:
+- Registry boundary が legacy Pod/socket/session authority を引きずること。
+- `00001KVZSGT0Q` の実 embedded接続まで scope creep すること。
+- Existing local compatibility source の API/diagnostics regression。
+
+---
+
+<!-- event: state_changed author: yoi-orchestrator at: 2026-06-25T16:55:16Z from: queued to: inprogress reason: routing_accepted_after_worker_runtime_core_done field: state -->
+
+## State changed
+
+Routing decision: implementation_ready。
+
+Dependency `00001KVZBCQH4` worker-runtime core は done。Ticket body / relations / workspace state / orchestration plan を確認し、Backend RuntimeRegistry foundation は unblocked と判断した。accepted plan と IntentPacket は thread / orchestration plan に記録済み。
+
+これ以降、worktree creation / coder Worker routing などの implementation side effect に進める。
+
+---

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

@@ -1 +1,2 @@
 {"id":"orch-plan-20260625-164457-1","ticket_id":"00001KVZQHPNY","kind":"blocked_by","related_ticket":"00001KVZBCQH4","note":"Queue routing checked after Dashboard Queue. Profile/config bundle sync depends on worker-runtime core `00001KVZBCQH4`, which is currently inprogress and under review. Do not start sync implementation until core CreateWorkerRequest/Profile boundary is reviewed/merged/done.","author":"yoi-orchestrator","at":"2026-06-25T16:44:57Z"}
+{"id":"orch-plan-20260625-165606-2","ticket_id":"00001KVZQHPNY","kind":"waiting_capacity_note","note":"Core dependency is now done, but this bundle-sync Ticket is left queued in this acceptance pass because Backend Registry foundation and FS store were accepted first. Bundle sync likely touches `worker-runtime` creation/profile boundary and Backend Registry availability semantics, so it should start after at least the foundation branch shape is reviewed or merged to avoid design/API churn.","author":"yoi-orchestrator","at":"2026-06-25T16:56:06Z"}

.yoi/tickets/00001KVZQHPNY/item.md

@@ -2,7 +2,7 @@
 title: 'RuntimeへProfile/config bundleを同期する'
 state: 'queued'
 created_at: '2026-06-25T15:49:30Z'
-updated_at: '2026-06-25T16:45:08Z'
+updated_at: '2026-06-25T16:56:06Z'
 assignee: null
 queued_by: 'workspace-panel'
 queued_at: '2026-06-25T16:44:39Z'