ticket: record podclient reader coder delegation

This commit is contained in:
Keisuke Hirata 2026-06-08 11:43:00 +09:00
parent 89b4369f2a
commit a6c3ef1a79
No known key found for this signature in database
2 changed files with 27 additions and 1 deletions

View File

@ -8,7 +8,7 @@ priority: 'P1'
labels: ['client', 'pod', 'tui', 'fd-leak', 'bug'] labels: ['client', 'pod', 'tui', 'fd-leak', 'bug']
workflow_state: 'inprogress' workflow_state: 'inprogress'
created_at: '2026-06-08T01:56:30Z' created_at: '2026-06-08T01:56:30Z'
updated_at: '2026-06-08T02:42:04Z' updated_at: '2026-06-08T02:42:29Z'
assignee: null assignee: null
legacy_ticket: null legacy_ticket: null
queued_by: 'workspace-panel' queued_by: 'workspace-panel'

View File

@ -112,3 +112,29 @@ Critical risks / reviewer focus:
Accepted queued implementation after reading the Ticket, workspace state, and `PodClient` code map. This acceptance precedes worktree creation and coder/reviewer Pod spawning. Accepted queued implementation after reading the Ticket, workspace state, and `PodClient` code map. This acceptance precedes worktree creation and coder/reviewer Pod spawning.
--- ---
<!-- event: plan author: orchestrator at: 2026-06-08T02:42:29Z -->
## Plan
Implementation routing accepted and worktree created.
Worktree plan:
- Branch: `abort-podclient-reader-task-on-drop`
- Worktree: `.worktree/abort-podclient-reader-task-on-drop`
- Base: `89b4369 ticket: route podclient reader cleanup`
- Scope: implement `PodClient` reader-task owned cancellation and focused cleanup tests.
Delegation plan:
- Spawn sibling coder Pod with write scope limited to `.worktree/abort-podclient-reader-task-on-drop`.
- Coder must run Bash commands from the child worktree, not from the main workspace.
- Coder must not edit main-workspace `.yoi` / Ticket / workflow / docs records, and must not create generated memory/local/runtime/secret-like files.
- Reviewer will be spawned read-only after coder reports diff/commits and validation evidence.
Concurrency note:
- Main workspace has unrelated Ticket-record edits for other queued/intake work. This implementation is isolated to the child worktree and should not edit those records.
Stop/completion policy:
- Because the human authorized cleanup after completion, this Orchestrator will proceed through reviewer approval, merge-completion validation, Ticket close, Pod stop, worktree removal, and branch deletion if the branch is approved and merge authority remains clear.
---