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

ticket: record intake idle shutdown coder delegation

Browse Source
This commit is contained in:
Keisuke Hirata 2026-06-08 16:38:32 +09:00
parent 64318e8045
commit 2f4addbfb9
No known key found for this signature in database
2 changed files with 27 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.yoi/tickets/open/20260608-054546-shutdown-intake-pod-after-ready-idle/item.md
View File

@ -8,7 +8,7 @@ priority: 'P2'
labels: ['ticket', 'intake', 'pod', 'lifecycle', 'panel']
workflow_state: 'inprogress'
created_at: '2026-06-08T05:45:46Z'
updated_at: '2026-06-08T07:37:20Z'
updated_at: '2026-06-08T07:37:50Z'
assignee: null
legacy_ticket: null
queued_by: 'workspace-panel'

26
.yoi/tickets/open/20260608-054546-shutdown-intake-pod-after-ready-idle/thread.md
View File

@ -203,3 +203,29 @@ Critical risks / reviewer focus:
Accepted queued implementation after human clarification and routing IntentPacket were recorded. This acceptance precedes worktree creation and coder/reviewer Pod spawning.
---
<!-- event: plan author: orchestrator at: 2026-06-08T07:37:50Z -->
## Plan
Implementation routing accepted and worktree created.
Worktree plan:
- Branch: `shutdown-intake-pod-after-ready-idle`
- Worktree: `.worktree/shutdown-intake-pod-after-ready-idle`
- Base: `64318e8 ticket: route intake idle shutdown implementation`
- Scope: implement transient post-idle shutdown for actual Ticket Intake Pods after successful `TicketIntakeReady`.
Delegation plan:
- Spawn sibling coder Pod with write scope limited to `.worktree/shutdown-intake-pod-after-ready-idle`.
- 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:
- `allow-spawnpod-child-workspace-cwd` remains active in a separate worktree/fix-loop. This implementation must remain isolated and should not depend on the unmerged `SpawnPod.cwd` work.
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.
---