ticket: close queued ticket routing

This commit is contained in:
Keisuke Hirata 2026-06-07 14:13:43 +09:00
parent c1f3ba6b89
commit 42789b471c
No known key found for this signature in database
4 changed files with 63 additions and 3 deletions

View File

@ -2,13 +2,13 @@
id: 20260607-035143-orchestrator-queued-ticket-routing
slug: orchestrator-queued-ticket-routing
title: Orchestrator queued Ticket routing
status: open
status: closed
kind: task
priority: P1
labels: [panel, orchestrator, ticket, routing, workflow]
workflow_state: ready
workflow_state: done
created_at: 2026-06-07T03:51:43Z
updated_at: 2026-06-07T05:12:59Z
updated_at: 2026-06-07T05:13:36Z
assignee: null
legacy_ticket: null
---

View File

@ -0,0 +1,22 @@
Implemented, reviewed, merged, and validated.
Summary:
- Updated Panel Queue notice so `ready -> queued` reports that Orchestrator routing is authorized and implementation side effects still require `queued -> inprogress` acceptance.
- Updated Orchestrator notification content to include Ticket slug/id/title and instruct the Orchestrator to read the Ticket, inspect workspace state, accept with `queued -> inprogress` before worktree/SpawnPod side effects when unblocked, and record a concise blocked/defer reason when blocked.
- Updated `.yoi/workflow/ticket-orchestrator-routing.md` so queued notifications are routing authorization, not passive no-op and not blind spawn permission.
- Kept worktree/coder/reviewer routing, merge completion, and orchestration plan tooling out of this ticket.
- Added focused tests for Queue notice and Orchestrator notification contract.
Implementation:
- Child commit: `ccf43f8 tui: update queued ticket routing notification`
- Parent workflow/report commit: `df6d7ee ticket: record queued routing implementation`
- Merge commit: `merge: queued ticket routing`
Review:
- External reviewer `orchestrator-routing-reviewer-20260607` approved with no blockers.
Validation after merge:
- `cargo test -p tui multi_pod --lib`
- `cargo fmt --check`
- `git diff --check`
- `target/debug/yoi ticket doctor`

View File

@ -161,3 +161,41 @@ Reviewer validation:
Merge readiness: approved; merge-tree against current `develop` succeeded. The workflow update is already present on `develop`.
---
<!-- event: state_changed author: hare at: 2026-06-07T05:13:36Z from: ready to: done reason: closed field: workflow_state -->
## State changed
Ticket closed; workflow_state set to done.
---
<!-- event: close author: hare at: 2026-06-07T05:13:36Z status: closed -->
## Closed
Implemented, reviewed, merged, and validated.
Summary:
- Updated Panel Queue notice so `ready -> queued` reports that Orchestrator routing is authorized and implementation side effects still require `queued -> inprogress` acceptance.
- Updated Orchestrator notification content to include Ticket slug/id/title and instruct the Orchestrator to read the Ticket, inspect workspace state, accept with `queued -> inprogress` before worktree/SpawnPod side effects when unblocked, and record a concise blocked/defer reason when blocked.
- Updated `.yoi/workflow/ticket-orchestrator-routing.md` so queued notifications are routing authorization, not passive no-op and not blind spawn permission.
- Kept worktree/coder/reviewer routing, merge completion, and orchestration plan tooling out of this ticket.
- Added focused tests for Queue notice and Orchestrator notification contract.
Implementation:
- Child commit: `ccf43f8 tui: update queued ticket routing notification`
- Parent workflow/report commit: `df6d7ee ticket: record queued routing implementation`
- Merge commit: `merge: queued ticket routing`
Review:
- External reviewer `orchestrator-routing-reviewer-20260607` approved with no blockers.
Validation after merge:
- `cargo test -p tui multi_pod --lib`
- `cargo fmt --check`
- `git diff --check`
- `target/debug/yoi ticket doctor`
---