ticket: accept workspace companion llm worker

This commit is contained in:
2026-06-28 15:02:59 +09:00
parent 9c3347f0ec
commit 0c5a769abb
3 changed files with 41 additions and 2 deletions
+38
View File
@@ -55,3 +55,41 @@ Next action:
- `00001KW55B33B` が done になった後に再 routing する。
---
<!-- event: decision author: yoi-orchestrator at: 2026-06-28T06:02:49Z -->
## Decision
Routing decision:
Queue continuation was explicitly requested. The upstream dependency `00001KW55B33B` is now closed after review, merge, validation, and cleanup. This Ticket is therefore unblocked and accepted for implementation.
Plan:
- Create child implementation worktree:
- `/home/hare/Projects/yoi/.worktree/00001KW55B33H-workspace-companion-llm-worker`
- Branch:
- `work/00001KW55B33H-workspace-companion-llm-worker`
- Route implementation to a sibling Coder Worker with focused write scope.
- Route read-only review to a sibling Reviewer Worker after implementation.
- Orchestrator retains merge, final validation, Ticket completion, child worktree/branch cleanup, and final reporting.
Review/implementation focus:
- Workspace Backend bootstraps `workspace_companion` as an executable Worker with real `worker` crate execution adapter.
- Worker list / Worker Console use the normal `runtime_id + worker_id` authority and Backend Worker input API.
- Console Send reaches real Worker execution path and uses `protocol::Event` / transcript projection, not Companion-specific fake/providerless messages.
- provider/model/secret/profile/authority absence returns typed diagnostic and does not present the Worker as input-capable.
- `/api/companion/messages`, if retained, must not return fake response and should be a thin normal Worker input path wrapper or non-authoritative compatibility path.
- Browser-facing API must not leak raw handles, sockets, session paths, credentials, secret refs, raw manifest paths, or broad authority internals.
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 this is explicitly reauthorized.
---
<!-- event: state_changed author: yoi-orchestrator at: 2026-06-28T06:02:54Z from: queued to: inprogress reason: dependency_closed_and_queue_continues field: state -->
## State changed
Queue continuation requested by user. Dependency `00001KW55B33B` is closed with merge and validation complete, so this Ticket has no remaining blockers. Accepting implementation before child worktree / role Pod side effects.
---