ticket: record intake claim coder delegation
This commit is contained in:
parent
d2a040d77a
commit
78a779e48d
|
|
@ -8,7 +8,7 @@ priority: P1
|
|||
labels: [tui, panel, ticket, intake, bug]
|
||||
workflow_state: 'inprogress'
|
||||
created_at: 2026-06-07T22:02:25Z
|
||||
updated_at: '2026-06-08T03:08:26Z'
|
||||
updated_at: '2026-06-08T03:08:56Z'
|
||||
assignee: null
|
||||
legacy_ticket: null
|
||||
queued_by: 'workspace-panel'
|
||||
|
|
|
|||
|
|
@ -140,3 +140,29 @@ Critical risks / reviewer focus:
|
|||
Accepted queued implementation after reading the Ticket, workspace state, and Intake claim lifecycle code map. This acceptance precedes worktree creation and coder/reviewer Pod spawning.
|
||||
|
||||
---
|
||||
|
||||
<!-- event: plan author: orchestrator at: 2026-06-08T03:08:56Z -->
|
||||
|
||||
## Plan
|
||||
|
||||
Implementation routing accepted and worktree created.
|
||||
|
||||
Worktree plan:
|
||||
- Branch: `commit-intake-claims-after-launch-success`
|
||||
- Worktree: `.worktree/commit-intake-claims-after-launch-success`
|
||||
- Base: `d2a040d ticket: route intake claim and spawn cwd tickets`
|
||||
- Scope: implement post-success existing-Ticket Intake claim commit and focused tests.
|
||||
|
||||
Delegation plan:
|
||||
- Spawn sibling coder Pod with write scope limited to `.worktree/commit-intake-claims-after-launch-success`.
|
||||
- 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.
|
||||
|
||||
Related queued/preflight note:
|
||||
- `allow-spawnpod-child-workspace-cwd` was routed as `preflight_needed` and remains queued; do not depend on the future `SpawnPod.cwd` field for this implementation.
|
||||
|
||||
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.
|
||||
|
||||
---
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user