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

ticket: delegate orchestrator merge completion

Browse Source
This commit is contained in:
Keisuke Hirata 2026-06-07 15:16:24 +09:00
parent 8db57dd59a
commit 3a0ec9feb9
No known key found for this signature in database
2 changed files with 23 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.yoi/tickets/open/20260607-035231-orchestrator-merge-completion/item.md
View File

@ -8,7 +8,7 @@ priority: P1
labels: [orchestrator, merge, ticket, workflow, validation] labels: [orchestrator, merge, ticket, workflow, validation]
workflow_state: ready workflow_state: ready
created_at: 2026-06-07T03:52:31Z created_at: 2026-06-07T03:52:31Z
updated_at: 2026-06-07T06:15:32Z updated_at: 2026-06-07T06:16:17Z
assignee: null assignee: null
legacy_ticket: null legacy_ticket: null
--- ---

22
.yoi/tickets/open/20260607-035231-orchestrator-merge-completion/thread.md
View File

@ -93,4 +93,26 @@ Implementation-ready as the third Orchestrator automation slice: add merge-compl
Ticket intake complete; workflow_state intake -> ready. Ticket intake complete; workflow_state intake -> ready.
---
<!-- event: implementation_report author: hare at: 2026-06-07T06:16:17Z -->
## Implementation report
## Delegation
Implementation delegated to child Pod `orchestrator-merge-coder-20260607` in worktree `.worktree/orchestrator-merge-completion` on branch `work/orchestrator-merge-completion`.
Scope:
- Add Orchestrator merge/completion guidance for reviewed in-progress Tickets with merge-ready dossiers.
- Preserve branch-local reviewer verdict vs final main Ticket approval boundary.
- Define dogfooding merge authority vs conservative stop-at-dossier behavior.
- Include post-merge validation, Ticket completion, worktree/branch/Pod cleanup guidance.
- Do not implement queue routing or worktree/coder/reviewer routing.
Workflow note:
- Child worktree excludes `.yoi`; if workflow file updates are needed, the child should report an exact parent-side patch rather than editing `.yoi`.
The child should commit implementation work in the child worktree and report diff/tests. Merge, review, Ticket closure, workflow file updates, and cleanup remain with the parent/human workflow.
--- ---