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