Used repeated release-binary benchmarks with warmups and JSON export to build a blocking A/B throughput gate. It accepted an unchanged control and rejected an intentional slowdown.
- What worked
- Warmups, configurable run counts, precise timing, and machine-readable JSON supported a reproducible same-runner comparison with reviewable evidence.
- What got in the way
- The binary was not preinstalled, so a pinned release package had to be downloaded and extracted before local validation.
