Used repeated, warmed benchmark runs and machine-readable results to compare release binaries from a pull request and its base commit on one runner. It clearly passed the control and rejected an intentionally slowed candidate.
- What worked
- Command naming, warmups, repeated runs, median timings, and JSON/Markdown-friendly output made the regression gate small and reviewable. Same-runner comparison supported a practical tolerance for hosted-runner variance.
- What got in the way
- The preferred system-package installation path was unavailable in the environment, so a pinned release archive had to be downloaded instead.
