Hare/yoi
1
1
Fork 0
Code Actions Packages Releases Activity

ticket: delegate companion pod lifecycle

Browse Source
This commit is contained in:
Keisuke Hirata 2026-06-07 19:18:01 +09:00
parent e418560a12
commit 2177dbf019
No known key found for this signature in database
2 changed files with 43 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.yoi/tickets/open/20260607-001651-workspace-panel-companion-pod-lifecycle/item.md
View File

@ -8,7 +8,7 @@ priority: P2
labels: [tui, panel, companion, pod] labels: [tui, panel, companion, pod]
workflow_state: ready workflow_state: ready
created_at: 2026-06-07T00:16:51Z created_at: 2026-06-07T00:16:51Z
updated_at: 2026-06-07T10:17:33Z updated_at: 2026-06-07T10:18:01Z
assignee: null assignee: null
legacy_ticket: null legacy_ticket: null
--- ---

42
.yoi/tickets/open/20260607-001651-workspace-panel-companion-pod-lifecycle/thread.md
View File

@ -74,4 +74,46 @@ Validation expected:
- `target/debug/yoi ticket doctor`. - `target/debug/yoi ticket doctor`.
---
<!-- event: plan author: hare at: 2026-06-07T10:18:01Z -->
## Plan
## Delegation intent
Implement `workspace-panel-companion-pod-lifecycle` in a dedicated worktree.
Worktree:
- `.worktree/workspace-panel-companion-pod-lifecycle`
- branch `work/workspace-panel-companion-pod-lifecycle`
Coder Pod:
- `companion-lifecycle-coder-20260607`
Key decision to preserve:
- Companion Pod id/name is the workspace directory basename.
- In this repository, the Companion Pod id/name is `yoi`.
- Do not use `yoi-companion` for the normal workspace Companion.
- `yoi panel` should treat an existing live/restorable default workspace Pod named `yoi` as the Companion.
- Workspace Orchestrator remains distinct, e.g. `yoi-orchestrator`.
Scope and boundaries:
- Companion is not a Ticket role; do not route this through `TicketRole` or `.yoi/ticket.config.toml` role slots.
- Preserve Ticket Intake as a separate composer target and separate history path.
- Do not reintroduce selected-Pod direct send, `--multi`, or `:ticket`.
- Panel close must not stop Companion.
- Existing live `yoi` Pod may own workspace write scope; lifecycle should reuse/route to it instead of spawning a duplicate with a conflicting scope.
- Keep diagnostics bounded and visible.
- Avoid broad UI restructuring.
Requested validation:
- Focused TUI tests for Companion naming/lifecycle decisions and composer routing separation.
- Existing panel/orchestrator tests affected by lifecycle changes.
- `cargo test -p tui ... --lib` for affected tests.
- `cargo fmt --check`.
- `git diff --check`.
- `target/debug/yoi ticket doctor`.
--- ---