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
..
omnigraph	engine: serialize concurrent branch merges via merge_exclusive mutex	2026-05-08 19:14:54 +02:00
omnigraph-cli	mr-686: bundle PR 0/1a/1b foundation + PR 2 catalog/schema_source ArcSwap	2026-05-07 16:22:38 +02:00
omnigraph-compiler	release: bump version to 0.4.1	2026-05-02 23:20:50 +02:00
omnigraph-server	bench: assert --heavy-concurrency > 0 instead of silently clamping	2026-05-08 19:23:02 +02:00