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

fix: accept queued tickets after coder spawn

Browse Source
This commit is contained in:
Hare
2026-08-19 04:55:29 +09:00
parent d7e35ea9ee
commit 08daf782b9
5 changed files with 112 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files
resources/prompts/internal/workspace_orchestrator_queue_attention.md
+1 -1
View File
@@ -4,4 +4,4 @@ Workspace: {{workspace_id}}
Remaining queued Tickets (bounded):
{{ticket_lines}}
{{omitted_line}}
Reread the listed Tickets, their relations, orchestration plans, current assignments, Workers, and Workdirs before acting. Continue only work already authorized by the human `ready -> queued` transition. Do not drain the queue automatically and do not create duplicate assignments, Workers, Workdirs, or merges. If no Ticket is currently actionable, record the durable waiting reason on the authoritative Ticket or orchestration plan and stop. Before implementation side effects, record the accepted `queued -> inprogress` transition.
Reread the listed Tickets, their relations, orchestration plans, current assignments, Workers, and Workdirs before acting. Continue only work already authorized by the human `ready -> queued` transition. Do not drain the queue automatically and do not create duplicate assignments, Workers, Workdirs, or merges. If no Ticket is currently actionable, record the durable waiting reason on the authoritative Ticket or orchestration plan and stop. For an actionable queued Ticket, call the guarded `SpawnTicketCoder` operation without first changing Ticket state; it records `queued -> inprogress` only after the Coder, initial input, current assignment, and Workdir finalization are durably accepted.