The cap on the rail's advance over the gap between the counter's window and the oracle's now
also runs on shared spans, and had been measured only beside the test's own burner child and an
empty-command-buffer churner. Measured on the build host beside three more burners of the test's
kernel (the test binary in its burner-child mode), so five clients burned at once and the GPU
drew about 49 W across each window: the power over the gap and republish allowance, the quantity
the cap bounds, was at most 19.2 W over three runs (15.4-19.2 W), against 12-17 W beside the child
alone; every run passed, every span shared or refused. That is well below 80% of the cap, so it
stays; the comment above the assertion records the measurement.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
f48b015d32