2 lines
1.8 KiB
JSON
2 lines
1.8 KiB
JSON
{"id":"orch-plan-20260628-164808-1","ticket_id":"00001KW7726H9","kind":"accepted_plan","note":"Workspace Dashboard Queue authorized routing. Ticket has no blocker relations, related upstream execution boundary/adapter/Companion Tickets are closed, no current inprogress Tickets, and orchestration worktree is clean.","accepted_plan":{"summary":"Runtime Worker 起動経路を Browser-facing launch と Runtime worker creation に分離し、Worker creation を正規の Execution/ConfigBundle 経路へ一本化する。実装前に `api-field-audit.md` と現行 create/catalog/fs-store/config bundle/execution backend/Segment/Workspace launch 経路を再確認し、最終 request field は実装内で検証して確定する。embedded / Companion / remote-facing の Worker 作成 bypass をなくし、未接続 input-capable Worker、fake/providerless response、raw workspace/cwd/tool scope/secret/path leak を防ぐ。","branch":"work/00001KW7726H9-runtime-worker-launch-unification","worktree":"/home/hare/Projects/yoi/.worktree/00001KW7726H9-runtime-worker-launch-unification","role_plan":"Orchestrator が dedicated child worktree を作成し、coder Worker に `crates/worker-runtime`, `crates/worker`, `crates/workspace-server`, 必要に応じて `web/workspace`, `resources/profiles`, `resources/prompts`, root Cargo/package files の focused write scope を委譲する。reviewer Worker は read-only で API 境界、ConfigBundle sync 分離、execution binding 境界、transaction/persistence/retry、Browser-facing non-leak、fake response absence、既存 related Tickets との整合を確認する。merge/validation/done/cleanup は Orchestrator が行う。現時点では `StopPod` は使用せず、cleanup は child worktree/branch のみ行う。"},"author":"yoi-orchestrator","at":"2026-06-28T16:48:08Z"}
|