Run the sandbox cap tests in every configuration
The two per-IP cap tests were ignored unless `fast-tests` was on, which
dated from when that feature swapped the rate-limit constants: under
production values a test creating four sandboxes was throttled by its own
setup. The limits are runtime config now and the default harness builds
the relaxed profile, so the gate was holding back tests that pass.
Both configurations now enumerate the same 1,244 integration tests, which
was the point of moving the limits off the feature. `fast-tests` is down
to argon2 parameters, a cost knob with no behaviour a feature-gated build
fails to exercise; recorded at the call site so it is not re-litigated.
Co-Authored-By
Claude Opus 5 (1M context) <noreply@anthropic.com>
Author: Max Johnson <me@maxj.phd> · 2026-08-05 13:41 UTC