diff --git a/.yoi/tickets/00001KVZQHPNY/artifacts/orchestration-plan.jsonl b/.yoi/tickets/00001KVZQHPNY/artifacts/orchestration-plan.jsonl index 548df084..4453977e 100644 --- a/.yoi/tickets/00001KVZQHPNY/artifacts/orchestration-plan.jsonl +++ b/.yoi/tickets/00001KVZQHPNY/artifacts/orchestration-plan.jsonl @@ -1,2 +1,3 @@ {"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"} +{"id":"orch-plan-20260626-051843-3","ticket_id":"00001KVZQHPNY","kind":"waiting_capacity_note","note":"Core/foundation dependencies are now done, but config bundle sync is left queued while embedded Backend RuntimeRegistry connection `00001KVZSGT0Q` is accepted/inprogress. Bundle sync likely touches worker creation/profile boundary and Backend Registry availability semantics; start after embedded connection branch shape is reviewed or merged to avoid API churn.","author":"yoi-orchestrator","at":"2026-06-26T05:18:43Z"} diff --git a/.yoi/tickets/00001KVZQHPNY/item.md b/.yoi/tickets/00001KVZQHPNY/item.md index 8b1a8f35..3260433b 100644 --- a/.yoi/tickets/00001KVZQHPNY/item.md +++ b/.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:56:06Z' +updated_at: '2026-06-26T05:18:43Z' assignee: null queued_by: 'workspace-panel' queued_at: '2026-06-25T16:44:39Z' diff --git a/.yoi/tickets/00001KVZSGT0Q/artifacts/orchestration-plan.jsonl b/.yoi/tickets/00001KVZSGT0Q/artifacts/orchestration-plan.jsonl index d7a6b330..5a557216 100644 --- a/.yoi/tickets/00001KVZSGT0Q/artifacts/orchestration-plan.jsonl +++ b/.yoi/tickets/00001KVZSGT0Q/artifacts/orchestration-plan.jsonl @@ -1 +1,2 @@ {"id":"orch-plan-20260625-163225-1","ticket_id":"00001KVZSGT0Q","kind":"blocked_by","related_ticket":"00001KVZKSV6C","note":"Queue routing checked after Dashboard Queue. Embedded Runtime connection depends on Backend RuntimeRegistry foundation `00001KVZKSV6C`, which is still queued and itself blocked by inprogress worker-runtime core `00001KVZBCQH4`. Do not start this Ticket until the foundation dependency is accepted/completed.","author":"yoi-orchestrator","at":"2026-06-25T16:32:25Z"} +{"id":"orch-plan-20260626-051805-2","ticket_id":"00001KVZSGT0Q","kind":"accepted_plan","note":"Dependencies are unblocked: `00001KVZKSV6C` RuntimeRegistry foundation is done; worker-runtime core is done. No active inprogress remains after WS proxy cleanup.","accepted_plan":{"summary":"Backend RuntimeRegistry に embedded `worker_runtime::Runtime` source を接続し、backend-internal Runtime として summary/status/capabilities、worker list/detail/create/input/transcript projection を direct lib call で扱えるようにする。remote process/FS/REST/WS/Web Console/Profile sync は扱わない。","branch":"work/00001KVZSGT0Q-embedded-runtime-registry","worktree":"/home/hare/Projects/yoi/.worktree/00001KVZSGT0Q-embedded-runtime-registry","role_plan":"Orchestrator が dedicated child worktree を作成し、coder Worker に `crates/workspace-server` 中心の narrow write scope を委譲する。reviewer Worker は read-only で embedded Runtime registration、runtime_id+worker_id routing、no internal path/credential leak、local compatibility separation を確認する。merge/validation/done/cleanup は Orchestrator が行う。"},"author":"yoi-orchestrator","at":"2026-06-26T05:18:05Z"} diff --git a/.yoi/tickets/00001KVZSGT0Q/item.md b/.yoi/tickets/00001KVZSGT0Q/item.md index ef0329b2..339130d2 100644 --- a/.yoi/tickets/00001KVZSGT0Q/item.md +++ b/.yoi/tickets/00001KVZSGT0Q/item.md @@ -1,8 +1,8 @@ --- title: 'Backend RuntimeRegistryにembedded worker-runtimeを接続する' -state: 'queued' +state: 'inprogress' created_at: '2026-06-25T16:23:58Z' -updated_at: '2026-06-25T16:32:35Z' +updated_at: '2026-06-26T05:18:35Z' assignee: null queued_by: 'workspace-panel' queued_at: '2026-06-25T16:31:30Z' diff --git a/.yoi/tickets/00001KVZSGT0Q/thread.md b/.yoi/tickets/00001KVZSGT0Q/thread.md index ba9f1877..9ec20be5 100644 --- a/.yoi/tickets/00001KVZSGT0Q/thread.md +++ b/.yoi/tickets/00001KVZSGT0Q/thread.md @@ -59,3 +59,76 @@ Escalate if: - worker-runtime core API が embedded Backend integration に必要な create/send/projection semantics を満たさない。 --- + + + +## Decision + +Routing decision: implementation_ready + +Reason: +- `00001KVZKSV6C` Backend RuntimeRegistry foundation は done。`00001KVZBCQH4` worker-runtime core も done。 +- 本 Ticket の scope は embedded Runtime handle を Backend Registry に接続することで、remote Runtime process / FS store / REST command server / event stream / Web Console / config bundle sync は Non-goals。 +- 現在 `inprogress` は 0 件。実装 surface は主に `crates/workspace-server` の RuntimeRegistry source/route であり、queued の remote/WebConsole/TUI は本 Ticket 完了後に判断すべき依存関係。 + +Evidence checked: +- Ticket body: embedded Runtime registration、direct lib call Worker operations、Backend API exposure、Non-goals、acceptance criteria。 +- Relations: outgoing dependency `00001KVZKSV6C` は done。incoming `00001KVZ9JGK0` / `00001KW04A8K6` は後続であり blocker ではない。 +- Orchestration plan: accepted plan `orch-plan-20260626-051805-2` を記録。 +- Workspace state: orchestration worktree clean、WS proxy Ticket は done/cleanup 済み。 + +IntentPacket: + +Intent: +- Workspace Backend の `RuntimeRegistry` に embedded `worker_runtime::Runtime` source を追加し、`backend-internal` Runtime として扱えるようにする。 + +Binding decisions / invariants: +- Embedded Runtime は HTTP endpoint / token / socket path / session path を持たない。 +- Browser-facing API は `runtime_id + worker_id` authority で扱い、embedded Runtime internals / store path / provider credentials を露出しない。 +- v0 は memory store / builtin/default Profile fallback / toolsなし Worker でよい。 +- Remote Runtime process client、FS store、REST command server、event stream server、Web Console、Profile/config bundle sync は実装しない。 +- Local compatibility source は残し、embedded Runtime source と diagnostics / implementation kind で区別する。 + +Requirements / acceptance criteria: +- Workspace Backend が embedded `worker_runtime::Runtime` を生成・保持し、RuntimeRegistry に登録できる。 +- Backend API から `backend-internal` Runtime の summary/status/capabilities を確認できる。 +- Registry が embedded Runtime の worker list/detail/create/send input/transcript projection を direct lib call で扱える。 +- v0 toolsなし Worker が create でき、input acceptance まで確認できる。 +- socket/session/runtime internal store/provider credential が Browser-facing API に出ない。 +- Focused workspace-server tests cover embedded runtime registration and routing。 + +Implementation latitude: +- Existing `/api/workers` / runtime list に含めるか、新 runtime-scoped endpoint に寄せるかは Coder が既存 API shape とテスト容易性に基づいて選び、実装報告で方針を明記する。 +- Internal source enum/handle/trait の分割、typed error mapping、test fixture の形は既存 `hosts.rs` / `server.rs` に合わせてよい。 + +Escalate if: +- `worker-runtime` public API の大幅変更が必要になる。 +- Profile/config bundle sync を同時に実装しないと embedded Worker create が成立しない場合。 +- Browser-facing API schema を大きく変える必要がある場合。 + +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: +- Embedded Runtime internals/path/credentials の漏洩。 +- Local compatibility source と embedded Runtime source の混同。 +- `runtime_id + worker_id` routing ではなく worker_id-only routing に戻る regression。 +- Non-goals（remote/REST/WS/WebConsole/Profile sync）への scope creep。 + +--- + + + +## State changed + +Routing decision: implementation_ready。 + +Dependency `00001KVZKSV6C` Backend RuntimeRegistry foundation と `00001KVZBCQH4` worker-runtime core は done。Ticket body / relations / workspace state / accepted plan を確認し、embedded worker-runtime Registry connection slice は unblocked と判断した。 + +これ以降、worktree creation / coder Worker routing などの implementation side effect に進める。 + +---