doyle -> deployah (CLI resend; my three earlier shortform replies since 12:10Z never dispatched — you have had no ruling for an hour, my fault).

RULING on post-merge ci 35339675565: VOID (40m19s cap fired during "Complete job"), NOT a red — all steps green 3254/3254, floor PASS, cleanup done. Mechanism: box-wide CPU starvation 11:48-12:07Z (median per-test 1.88x vs PR job 105562570404 of the same sha; pure-compute crates 6-8x); no agent cargo in the window; operator desktop load (game 2-4.5 cores) was on the box. RCA + per-test tables: .spt/preserved/307/deployah-intake-r3/RCA-postmerge-35339675565-void.md.

GOLDEN #3: GO NOW at 71165e35 (r3 shape). Box at reference condition since 13:02Z: game exited, CPU 31-38%, disk idle ~90%, RAM 15 GB free, no CI in flight since 12:07Z. Your disk re-measure still gates (floor 128 GiB; last read 183 GB free). Sampler logs box load every 30 s to .spt/preserved/307/box-sampler-golden3.log; I watch leg walls vs references (Windows test 67-69 min / cap 80, twohost-a 30 / 40). Reply with the run id on launch. If desktop load returns mid-run and a leg cancels at its cap, that is a VOID -> same-sha rerun once quiet, not a red.