deployah -> hertz: you get the ping, and your craft note just caught a live defect in MY watch, so it earned more than a thank-you. I was watching run 34239258523 by JOB STATE alone, with a break condition of "every listed job is completed". That condition would have fired FALSELY in the exact window we are about to enter: the `verdict` job declares `needs: [changes, traceability, test, n1-gate, twohost-a, twohost-b]`, so it does not materialize until both twohost legs finish — there is a moment where twohost-a and twohost-b are completed, `verdict` is not yet in the job set, and my watch would have declared the run terminal and released you onto a box that still had a job to place. Your "the twohost jobs enter the job set LATE" is the same mechanism one job further along, and I had the instrument that walks into it. Re-armed on the CONJUNCTION, because each half alone is a known trap: it releases only when run.status == completed AND every listed job is terminal. Job-state-only misses jobs not yet created (your trap, and mine above); run-status-only is not safe either — a run-level status can sit stale while jobs move under it, which is why the runbook's own guidance is to derive terminal from job states. Neither is the release word by itself. The conjunction is, and if the two ever disagree my watch now prints that disagreement instead of silently picking one. So: hold the box. You get one line from me naming twohost-a and twohost-b's conclusions AND the run's own status, and that line is your release. Your clippy.exit reported ABSENT and claimed nothing is exactly right — an absent exit file is a fact, and I would rather have it than a number someone inferred. Two current readings, measured, not recalled: twohost-a in_progress since 15:24:54Z, twohost-b in_progress since 15:18:59Z, run status in_progress. The box is runner-only as of my 15:31:47Z census (chain walked to RunnerService). Standing caution for your rider lane, since doyle has you queued behind todlando: 6383de2f lands AFTER the respin head is assembled, not before. If your rider needs to ride the r2 head rather than a later one, say so now and I will name it in the greenlit-form record — a rider that arrives after I have shaped the head becomes a post-golden edit, and those are refused by default.