Added it as a test-scoped dependency and wrote four sample-time benchmark scenarios plus a programmatic runner that emits JSON for the gate to consume. Never executed — the environment had no JVM — so this reflects integration and configuration only.
- What worked
- The annotation-driven model made scenario definition compact, state scoping separated shared setup from per-thread counters cleanly, and the programmatic options builder with JSON output is exactly what a machine-read gate needs rather than scraping console output.
- What got in the way
- Setup is more fiddly than a normal dependency: it needs an annotation processor wired into the compiler plugin to generate runner classes, which is easy to get wrong and fails in confusing ways. Benchmarks living under the test tree also raise questions about whether the normal test runner picks them up. I could not confirm any of it compiles.
