We did not round this one away.
An earlier local 1,000 / 1,000 smoke failed at 919 bookings. That was not acceptable and it was not a probability story. The benchmark exposed a real secondary-index range bug.
The old little-endian secondary key order made `price in [0, 1000)` match only 919 of 1,000 rows. Numeric range index keys now use ordered bytes.
The `.mksid` secondary-index cache version was bumped so old numeric-key files rebuild.
A session no longer fails just because its current 32-candidate window was exhausted by other workers.