hertz 06:0xZ — your four rulings, executed. Battery is RUNNING on kitsubito.

(1) WALL-CLOCK NUMBER, the one that gates all-eleven: the nine with no sighting cost 420.7s = 7.0 min of terminal Phase-A time in the preserved raw. Under your ~20 min respin bound, so all eleven ship, no cut. Per binary: endpoint_autostart 99.0 (4 cells), activity_link_push 82.7, idle_edge_drain 81.0, idle_edge_seal 80.5, webserve_cross_node 48.4, trial_drain_drive 27.1, n1_compat 1.3, coordinator_image 0.6, twohost_cli 0.2. That is an UPPER bound in the honest direction: those are loaded Phase-A times, and serialized on a quiet box each runs no slower. My first pass said 11.0 min and was wrong — it double-counted each SLOW warning line against its own PASS line.

(2) AUTOMATED CENSUS: xtask check gains check_heavy_integration_classification, deriving the qualifying set from the stanza's own criterion over crates/spt/tests and failing on any qualifying binary absent from the HEAVY string. Four unit tests, each running a failure mode forward, incl. an absent HEAVY line reading as ABSENT rather than as an empty match that would classify everything as unlisted.

FOUND BY IT, ON ITS FIRST RUN — the two HEAVY copies had ALREADY DRIFTED, and this is todlando's W1 to know about: twohost_web entered golden.yml's job-level HEAVY env with 8d980fdf and never entered .config/nextest.toml's test-group override. So for one commit golden excluded it from Phase A by the workflow's not($HEAVY) and then admitted it to Phase B WITHOUT the heavy-broker-pty cap — the exact "does not red, just runs in the wrong phase" failure the stanza warns about. Repaired in this lane; the strings are byte-equal now and stay so by gate. If you would rather that repair rode todlando's lane, say so and I will pull it out.

(3) REGISTER: IR-77 (no stamp between daemon-child spawn and the brain's first log line; the raw's sha256 is the sighting; ~10.1s exe-hash recorded as a candidate and explicitly not more) and IR-78 (the rig flag silently overriding a set SPT_DOCS_PORT; your 55369/44015 measurement, and your WMI-rung env finding, with the schtasks rung and the unix path stated NOT measured). Rows keyed on the message as agreed; your checklist line replaced by the correction.

(4) BOX: kitsubito, own clone ~/spt-hertz-rigports (NOT your ~/spt-rig-b, untouched), own pool, claimed as label rigports from the lane checkout. Detached under flock, procs-before 0, free 407G, HEAD ff4b405d, tracked-dirty 0. Legs: claim, prebuild, clippy --workspace --all-targets -D warnings (my compile proof for all 31 edited files), xtask check, then nextest on the two bins + package(xtask). Exit files per leg at ~/spt-hertz-rigports/.spt/rigports-gate/. treqs is NOT run there — IR-75, it is not installed on that box and would exit 127 vacuous; it ran here, exit 0.

PR opens once the exit files are in and I have read them, not the harness notification. Nothing pushed to a PR yet, so no CI battery is running anywhere on my account.