Ragnor Comerford 64f2b994f5 bench: assert --heavy-concurrency > 0 instead of silently clamping ... Closes the cubic P2 finding on commit 22d76db: `Semaphore::new(concurrency.max(1))` silently coerced --heavy-concurrency=0 to 1, so the JSON output reported 0 while execution actually used 1. Reported settings differed from actual. Adds an explicit `--heavy-concurrency > 0` check in `main()` (with a helpful error message pointing to --heavy-batches=0 as the way to disable heavy traffic) and a defensive `assert!()` inside `drive_heavy_actor` so future callers can't pass 0 silently. Verified: `bench_actor_isolation --heavy-concurrency 0` exits with code 2 and the explanatory error message. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-05-08 19:23:02 +02:00
..
examples	bench: assert --heavy-concurrency > 0 instead of silently clamping	2026-05-08 19:23:02 +02:00
src	server+bench: AppState::new_with_workload; bench drops set_var, exercises heavy cap	2026-05-08 17:57:42 +02:00
tests	tests: pin branch_merge swap-restore race (red)	2026-05-08 19:12:03 +02:00
Cargo.toml	server: add WorkloadController for per-actor admission (PR 2 Step E)	2026-05-07 16:59:45 +02:00