forked from unom/punktfunk
enricobuehler
5ee6468b2b
CI gate C counts `env::set_var` mentions per file and this file was at its baseline of five, so the field leg's sixth copy failed the build. Raising the baseline is what the gate tells you not to do, and it would have been the wrong answer anyway: the six copies were the same two-line safety argument written out six times, which is precisely the shape a ratchet exists to discourage. `arm_test_readback` takes the GPU lock guard BY REFERENCE. `env::set_var` is safe to call and unsound from a live multithreaded process, so "the caller holds the binary-wide lock" is the entire safety argument — and a borrow states it in the type system, where it cannot drift out of date, instead of in prose repeated at each call site. The file drops from six mentions to two (the call, and the doc comment that names the API it is arguing about — gate C counts comments too, by design, and writing around its grep would be gaming it). The baseline moves 5 -> 2 to match, so the ratchet stays tight rather than merely satisfied. Gates: fmt, clippy --all-targets and 197 lib tests clean; check-unsafe-hygiene.sh gate C now passes. Gate B's punktfunk-tray finding is untouched by this branch and fails identically on main.