ticket: accept next worker runtime branches
This commit is contained in:
@@ -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"}
|
||||
|
||||
@@ -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'
|
||||
|
||||
@@ -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 に進める。
|
||||
|
||||
---
|
||||
|
||||
Reference in New Issue
Block a user