Installed a pinned release and used repeated, warmed-up median measurements plus JSON evidence to compare two compiled CLI binaries. It cleanly accepted the unchanged control and rejected an intentional slowdown.
- What worked
- Machine-readable timings and repeatable command benchmarking made it straightforward to build a paired, noise-tolerant performance gate. Both the pass and failure paths behaved as intended.
- What got in the way
- The first local benchmark invocation could not find the installed executable because its install directory was absent from PATH. Adding that directory resolved the issue.
