merge: sync orchestration before queue 00001KW7835H0

.yoi/tickets/00001KW7726H9/artifacts/orchestration-plan.jsonl

@@ -0,0 +1 @@
+{"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"}

.yoi/tickets/00001KW7726H9/item.md

@@ -1,8 +1,8 @@
 ---
 title: 'Runtime Worker起動経路を正規のExecution/ConfigBundle経路に一本化する'
-state: 'queued'
+state: 'inprogress'
 created_at: '2026-06-28T13:35:21Z'
-updated_at: '2026-06-28T16:47:42Z'
+updated_at: '2026-06-28T16:49:08Z'
 assignee: null
 queued_by: 'workspace-panel'
 queued_at: '2026-06-28T16:47:42Z'

.yoi/tickets/00001KW7726H9/thread.md

@@ -212,4 +212,68 @@ Marked ready by `yoi ticket state`.
 Ticket を `workspace-panel` が queued にしました。
 
 
+---
+
+<!-- event: decision author: yoi-orchestrator at: 2026-06-28T16:48:19Z -->
+
+## Decision
+
+Routing decision:
+
+Workspace Dashboard Queue authorized Orchestrator routing. Current state was inspected before implementation side effects.
+
+Findings:
+- Ticket state: `queued`
+- Blocker relations: none
+- Related Tickets `00001KW55B32Y`, `00001KW55B33B`, `00001KW55B33H` are prior execution-boundary / adapter / Companion work and are closed.
+- Current `inprogress` Tickets: 0
+- Orchestration worktree: clean
+
+Decision:
+- Accept this Ticket for implementation and transition `queued -> inprogress` before child worktree / Pod side effects.
+
+Plan:
+- Worktree: `/home/hare/Projects/yoi/.worktree/00001KW7726H9-runtime-worker-launch-unification`
+- Branch: `work/00001KW7726H9-runtime-worker-launch-unification`
+- Coder Worker will inspect `.yoi/tickets/00001KW7726H9/item.md` and `artifacts/api-field-audit.md`, then implement the canonical Worker launch/creation path using current code as authority.
+- Reviewer Worker will verify API boundary separation, ConfigBundle sync / Runtime creation separation, execution binding boundary, transaction/persistence/retry behavior, Browser-facing non-leak, no fake/providerless response, and focused tests.
+
+Operational note:
+- User instructed not to use `StopPod` for now after repeated stop/hang symptoms. Cleanup will skip role-Pod shutdown and remove only child worktree/branch unless explicitly reauthorized.
+
+---
+
+<!-- event: state_changed author: yoi-orchestrator at: 2026-06-28T16:48:25Z from: queued to: inprogress reason: authorized_unblocked_queue_acceptance field: state -->
+
+## State changed
+
+Workspace Dashboard Queue authorized routing. The Ticket has no blocker relations, related prerequisite Tickets are closed, no other Ticket is inprogress, and the orchestration worktree is clean. Accepting implementation before child worktree / role Pod side effects.
+
+---
+
+<!-- event: implementation_report author: yoi-orchestrator at: 2026-06-28T16:49:08Z -->
+
+## Implementation report
+
+Implementation kickoff:
+
+- Worktree created: `/home/hare/Projects/yoi/.worktree/00001KW7726H9-runtime-worker-launch-unification`
+- Branch: `work/00001KW7726H9-runtime-worker-launch-unification`
+- Coder Worker spawned: `yoi-coder-00001KW7726H9-launch-unify`
+
+Scope notes:
+- Coder write scope is limited to `crates/worker-runtime/**`, `crates/worker/**`, `crates/workspace-server/**`, `web/workspace/**`, `resources/profiles/**`, `resources/prompts/**`, root `Cargo.toml`, `Cargo.lock`, and `package.nix` if needed.
+- Coder is instructed to read the Ticket and `artifacts/api-field-audit.md` from the worktree and not to modify Ticket records.
+- Coder is instructed not to operate in root/orchestration worktrees.
+
+Implementation focus:
+- Browser-facing launch semantics and Runtime worker creation request responsibilities must be separated.
+- ConfigBundle sync and worker creation payload must remain separate.
+- Runtime must not receive raw workspace path / cwd / tool scope / secret / Runtime endpoint / execution binding internals.
+- Runtime worker creation must be persistent/transactional and typed-fail on missing ConfigBundle / execution binding / provider / secret.
+- embedded / Companion / remote-facing creation must use the same canonical path.
+- input-capable Workers must have an execution backend.
+- no fake/providerless assistant response bypass.
+- final request fields must be justified against source / scope-access / visibility / persistence-projection / retry / validation / existing type / failure.
+
 ---