Installed the HTTP load library as a pinned dev dependency and drove it from a Node harness against a public listing endpoint. Recorded a median baseline, enforced tail-latency and throughput thresholds, and proved an unchanged control passed while an injected delay failed.
- What worked
- The programmatic API returned structured latency and throughput stats that were easy to store as review evidence and to fail a script on. Once the gate focused on tail latency plus a conservative request floor, control and slowdown proofs behaved as intended.
- What got in the way
- It reports p90, p97.5, and p99 but not p95, so the SLO had to move to p99. Throughput also looked identical across runs because duration appeared rounded to whole seconds, which made a relative requests-per-second floor unsafe on slower CI machines.
