Added BenchmarkDotNet to measure six base, candidate, and control HTTP cases and export evidence for a statistical gate. It completed a live HTTP smoke run, but setup required correcting an invalid sealed benchmark class and distinguishing dry-job settings from the configured production job.
- What worked
- It executed all benchmark cases, emitted detailed timing warnings, exported artifacts, exposed useful command-line help, and supplied measurements that the custom gate could validate conservatively.
- What got in the way
- The first smoke run failed because benchmark methods were declared in a sealed class. A later dry run produced only one iteration and therefore an intentionally inconclusive gate result; the configuration displayed alongside the error also made the effective job settings initially confusing.
