ticket: record ticket language coder delegation

This commit is contained in:
Keisuke Hirata 2026-06-08 16:42:18 +09:00
parent 17ac5b04f0
commit a987250cd3
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: 'P2'
labels: ['ticket', 'language', 'config', 'profile', 'workflow']
workflow_state: 'inprogress'
created_at: '2026-06-08T03:29:11Z'
updated_at: '2026-06-08T07:41:11Z'
updated_at: '2026-06-08T07:41:39Z'
assignee: null
legacy_ticket: null
queued_by: 'workspace-panel'

View File

@ -170,3 +170,29 @@ Critical risks / reviewer focus:
Accepted queued implementation after user confirmation and routing IntentPacket were recorded. This acceptance precedes worktree creation and coder/reviewer Pod spawning.
---
<!-- event: plan author: orchestrator at: 2026-06-08T07:41:39Z -->
## Plan
Implementation routing accepted and worktree created.
Worktree plan:
- Branch: `separate-ticket-record-language-from-worker-language`
- Worktree: `.worktree/separate-ticket-record-language-from-worker-language`
- Base: `17ac5b0 ticket: route ticket record language implementation`
- Scope: add optional Ticket record language config and propagate it to role guidance/generated Ticket-record paths where practical.
Delegation plan:
- Spawn sibling coder Pod with write scope limited to `.worktree/separate-ticket-record-language-from-worker-language`.
- 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` and `shutdown-intake-pod-after-ready-idle` are active in separate worktrees. This language-policy implementation must remain isolated and should not depend on those unmerged branches.
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.
---