What this test proves
Inside the colima testbed, a real agent executes prompt AT10 and observes assignment transitions only through public ATM CLI JSON. Queue, ready, close, reassign, move, cancel, and busy-assigner behavior must match the task protocol while pending-ack remains untouched.
Evidence layout
This procedure is one step of a colima integration run. The agent's unedited prompt-report-1 JSON is retained beside step.json; scripts/integration/render_colima.py renders the panel and aggregate. Historical payloads remain byte-identical and render through the same path.
Changes
The revision sections below list every runner revision that produced committed evidence, newest first. A run whose source revision is not an ancestor of any listed revision links to the revision in effect on its run date and is marked inferred.
Flow
Steps
| step | action | observable | evidence |
|---|---|---|---|
| 1 | Tell the agent to assign three tasks | task events show queued positions 1–3, one ready, and pending-ack zero | `prompt-AT10.json` and `step.json` cases |
| 2 | Start and close the ready task | bounded task-list/events polling shows the next task ready | `prompt-AT10.json` and `step.json` cases |
| 3 | Reassign a queued task | public mail/events show reassigned to the old assignee and queued to the new | `prompt-AT10.json` and `step.json` cases |
| 4 | Move an idle assignee's queued task to head | task events show exactly one new ready transition | `prompt-AT10.json` and `step.json` cases |
| 5 | Cancel a queued task | public mail/events show the cancelled terminal outcome | `prompt-AT10.json` and `step.json` cases |
| 6 | Start and complete while the assigner is busy | assigner mail/history shows started before completed | `prompt-AT10.json` and `step.json` cases |