ticket: close parallel queued routing

This commit is contained in:
Keisuke Hirata 2026-06-09 19:47:56 +09:00
parent ad5d3bad64
commit 81feb77433
No known key found for this signature in database
3 changed files with 62 additions and 2 deletions

View File

@ -1,8 +1,8 @@
--- ---
title: 'Orchestratorに独立queued workの並列開始を促す' title: 'Orchestratorに独立queued workの並列開始を促す'
state: 'inprogress' state: 'closed'
created_at: '2026-06-09T10:17:32Z' created_at: '2026-06-09T10:17:32Z'
updated_at: '2026-06-09T10:46:18Z' updated_at: '2026-06-09T10:47:47Z'
assignee: null assignee: null
queued_by: 'workspace-panel' queued_by: 'workspace-panel'
queued_at: '2026-06-09T10:31:16Z' queued_at: '2026-06-09T10:31:16Z'

View File

@ -0,0 +1,22 @@
Implemented, reviewed, merged, and validated.
Summary:
- Updated Orchestrator routing guidance to prefer starting additional independent queued Tickets during explicit queue review/routing when capacity exists and safety checks pass.
- Preserved the rule that queue notifications are not unattended scheduler triggers.
- Preserved the durable `queued -> inprogress` acceptance gate before worktree creation, Pod spawn, or implementation side effects.
- Explicitly forbids starting unqueued Tickets to fill capacity.
- Added required parallel-start checks for Ticket body/thread/artifacts, Ticket relations, OrchestrationPlan, workspace/worktree dirty state, visible Pods, branches, and conflict/dependency notes.
- Added bounded idle/defer reasons when capacity appears available but queued work is left waiting.
- Updated multi-agent workflow guidance for separate worktrees/branches/narrow write scopes and read-only Reviewer default.
Implementation:
- Coder commit: `492fe06 workflow: prefer parallel queued starts`
- Reviewer approved with no blocking findings.
- Merge commit completed after ToolExecutionContext cleanup.
Validation after merge:
- `git diff --check`
- `cargo run -q -p yoi -- ticket doctor`
- `nix build .#yoi`
`cargo check --workspace` was intentionally omitted because the change is workflow-resource text only and Nix build covered packaged resource integrity.

View File

@ -186,3 +186,41 @@ Reviewer validation:
All passed. Residual note: this is workflow guidance, not runtime scheduler enforcement, which is consistent with the Ticket scope. All passed. Residual note: this is workflow guidance, not runtime scheduler enforcement, which is consistent with the Ticket scope.
--- ---
<!-- event: state_changed author: hare at: 2026-06-09T10:47:47Z from: inprogress to: closed reason: closed field: state -->
## State changed
Ticket を closed にしました。
---
<!-- event: close author: hare at: 2026-06-09T10:47:47Z status: closed -->
## 完了
Implemented, reviewed, merged, and validated.
Summary:
- Updated Orchestrator routing guidance to prefer starting additional independent queued Tickets during explicit queue review/routing when capacity exists and safety checks pass.
- Preserved the rule that queue notifications are not unattended scheduler triggers.
- Preserved the durable `queued -> inprogress` acceptance gate before worktree creation, Pod spawn, or implementation side effects.
- Explicitly forbids starting unqueued Tickets to fill capacity.
- Added required parallel-start checks for Ticket body/thread/artifacts, Ticket relations, OrchestrationPlan, workspace/worktree dirty state, visible Pods, branches, and conflict/dependency notes.
- Added bounded idle/defer reasons when capacity appears available but queued work is left waiting.
- Updated multi-agent workflow guidance for separate worktrees/branches/narrow write scopes and read-only Reviewer default.
Implementation:
- Coder commit: `492fe06 workflow: prefer parallel queued starts`
- Reviewer approved with no blocking findings.
- Merge commit completed after ToolExecutionContext cleanup.
Validation after merge:
- `git diff --check`
- `cargo run -q -p yoi -- ticket doctor`
- `nix build .#yoi`
`cargo check --workspace` was intentionally omitted because the change is workflow-resource text only and Nix build covered packaged resource integrity.
---