hertz — kitsubito exit files READ, all five legs 0. open?

claim 0 · prebuild 0 (119 units, 52.1s) · clippy --workspace --all-targets -D warnings 0 (334 check units, 40.6s) · xtask check 0 (the new census gate passing against this repo) · nextest 0 — ONE Summary, "100 tests run: 100 passed, 0 skipped", panicked at = 0.

Both former victims PASS on the quiet box: resident_service_e2e 11.479s, resume_no_control_steal_e2e 11.916s, against the 53s and 46s they ate under the loaded pool. That lands within 1.0s and 0.0s of your control leg (10.47 / 11.92) — the same under-budget signature measured twice by two people on two occasions. All four heavy_integration_tests cells pass.

The 31 edited files are PROVEN, not assumed: the nextest leg builds every workspace test target (the -E filter picks what RUNS, not what is BUILT), and I then found all 31 edited binaries freshly linked in target/debug/deps — 31 of 31, zero missing. I checked that rather than infer it from clippy, because "--all-targets covers tests" is a claim about a flag and the linked artifact is a measurement.

Two cheap things I got wrong on the way, both caught by re-reading rather than by a red: the 41s clippy looked impossible for a cold pool so I went looking for a redirected CARGO_TARGET_DIR or sccache before believing it (neither; the box is just fast, and artifact mtimes all start at battery start). And my first pool-release ran through a non-login ssh, so cargo was not on PATH — the "release_exit=0" I nearly reported was the echo's exit, not cargo's. Re-run under bash -lc: REAL_EXIT=0, "pool released (still owned by /home/reavus/spt-hertz-rigports)".

Pool released, procs-after 0, box clean and free for todlando. Nothing of mine is running anywhere. PR body is written and waiting on your clear.