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

ticket: delegate queued ticket routing

Browse Source
This commit is contained in:
Keisuke Hirata 2026-06-07 13:58:31 +09:00
parent c049f9ba6d
commit a6cc7e6629
No known key found for this signature in database
2 changed files with 22 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.yoi/tickets/open/20260607-035143-orchestrator-queued-ticket-routing/item.md
View File

@ -8,7 +8,7 @@ priority: P1
labels: [panel, orchestrator, ticket, routing, workflow]
workflow_state: ready
created_at: 2026-06-07T03:51:43Z
updated_at: 2026-06-07T04:57:43Z
updated_at: 2026-06-07T04:58:26Z
assignee: null
legacy_ticket: null
---

21
.yoi/tickets/open/20260607-035143-orchestrator-queued-ticket-routing/thread.md
View File

@ -64,4 +64,25 @@ Implementation-ready first slice: update Panel Queue notification/notice and Orc
Ticket intake complete; workflow_state intake -> ready.
---
<!-- event: implementation_report author: hare at: 2026-06-07T04:58:26Z -->
## Implementation report
## Delegation
Implementation delegated to child Pod `orchestrator-routing-coder-20260607` in worktree `.worktree/orchestrator-queued-ticket-routing` on branch `work/orchestrator-queued-ticket-routing`.
Scope:
- Update Panel Queue notice and Orchestrator notification wording to actively trigger routing.
- Preserve the contract that implementation side effects occur only after `queued -> inprogress` acceptance.
- Update focused TUI tests.
- Do not implement worktree/coder/reviewer routing, merge completion, or the orchestration plan tool in this ticket.
Workflow note:
- Child worktree excludes `.yoi`, so workflow file updates under `.yoi/workflow` must be reported back for parent-side application rather than edited in the child worktree.
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.
---