ticket: accept remote runtime registry
This commit is contained in:
@@ -53,3 +53,77 @@ Next action:
|
||||
- REST command server と WebSocket observation proxy が done になった後に再 routing する。
|
||||
|
||||
---
|
||||
|
||||
<!-- event: decision author: yoi-orchestrator at: 2026-06-26T05:48:59Z -->
|
||||
|
||||
## Decision
|
||||
|
||||
Routing decision: implementation_ready
|
||||
|
||||
Reason:
|
||||
- Dependencies are done: `00001KVZKST83` FS store、`00001KVZKSTE2` REST command server、`00001KVZKSTJT` WebSocket observation proxy、`00001KVZKSV6C` RuntimeRegistry foundation。
|
||||
- Existing relation to `00001KVZQHPNY` is `related`, not blocking, and says v0 can use builtin/default fallback where applicable.
|
||||
- 本 Ticket は remote Runtime process connection / routing を主目的とし、Dynamic registration / full auth / Web Console / Profile config sync は Non-goals。
|
||||
- 現在 `inprogress` は 0 件。remote Runtime connection は TUI migration の blocker なので優先して受理する。
|
||||
|
||||
Evidence checked:
|
||||
- Ticket body: remote Runtime client handle、REST command API client、Runtime event stream client/proxy、config/policy boundary、Non-goals、acceptance criteria。
|
||||
- Relations: outgoing dependencies to FS/REST/WS/Registry foundation are done。Incoming TUI dependency is downstream。
|
||||
- Orchestration plan: accepted plan `orch-plan-20260626-054840-2` を記録。
|
||||
- Workspace state: orchestration worktree clean、embedded Runtime registry Ticket done/cleanup 済み。
|
||||
|
||||
IntentPacket:
|
||||
|
||||
Intent:
|
||||
- Workspace Backend `RuntimeRegistry` に remote worker-runtime process handle を追加し、Backend-owned REST/WS client で remote Runtime operations を route/proxy できるようにする。
|
||||
|
||||
Binding decisions / invariants:
|
||||
- Browser は remote Runtime base URL / token / direct endpoint を知らない。
|
||||
- Browser-facing authority は embedded/local と同じ `runtime_id + worker_id`。
|
||||
- Remote command は worker-runtime REST command API に対する Backend-owned client。
|
||||
- Remote observation は worker-runtime WS observation API に対する Backend-owned client/proxy。
|
||||
- Dynamic registration、full auth/permission model、Backend Web Console、Profile/config bundle sync は実装しない。
|
||||
- Embedded/local compatibility source の behavior を壊さず、remote source を implementation kind/diagnostics で区別する。
|
||||
|
||||
Requirements / acceptance criteria:
|
||||
- Config-like data から remote Runtime client handle を登録できる。
|
||||
- Runtime summary/status/capabilities、worker list/detail/create/input/stop/cancel/transcript/event proxy を route できる。
|
||||
- Network/auth/timeout/remote unsupported/remote worker not found を typed Backend errors/diagnostics に map する。
|
||||
- Browser-facing API/WS envelope に remote base URL/token/direct endpoint/socket/session path を露出しない。
|
||||
- Focused workspace-server tests cover mocked remote routing and error mapping。
|
||||
|
||||
Implementation latitude:
|
||||
- HTTP/WS client dependencies、mock remote test harness、internal source/handle trait shape、error type naming は Coder が既存 `workspace-server` pattern に合わせて選べる。
|
||||
- v0 config-like data は in-memory/static constructor/test fixture でよい。Dynamic registration は不要。
|
||||
|
||||
Escalate if:
|
||||
- worker-runtime REST/WS public API 変更が必要になる。
|
||||
- Profile/config sync がないと remote Worker creation が成立しない場合。
|
||||
- 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:
|
||||
- remote endpoint/token/direct URL leak。
|
||||
- worker_id-only routing regression。
|
||||
- remote REST/WS client errors being collapsed into generic unavailable。
|
||||
- scope creep into dynamic registration/auth/Web Console/Profile sync。
|
||||
|
||||
---
|
||||
|
||||
<!-- event: state_changed author: yoi-orchestrator at: 2026-06-26T05:49:13Z from: queued to: inprogress reason: routing_accepted_after_remote_runtime_prerequisites_done field: state -->
|
||||
|
||||
## State changed
|
||||
|
||||
Routing decision: implementation_ready。
|
||||
|
||||
FS store、REST command server、WebSocket observation proxy、RuntimeRegistry foundation は done。Ticket body / relations / workspace state / accepted plan を確認し、remote worker-runtime process connection slice は unblocked と判断した。Profile/config sync は related であり v0 builtin/default fallback が許容されているため blocker ではない。
|
||||
|
||||
これ以降、worktree creation / coder Worker routing などの implementation side effect に進める。
|
||||
|
||||
---
|
||||
|
||||
Reference in New Issue
Block a user