Multiplayer agent harness for work.
Add Prod-like QA to the Wall of shame (#2233)
Regan Bell609eabddbd20
diff --git a/docs/SPEC.md b/docs/SPEC.mdindex 443be4aad..96e750504 100644--- a/docs/SPEC.md+++ b/docs/SPEC.md@@ -180,6 +180,12 @@ Keeping old endpoints, data shapes, and code paths alive next to their replacemeDescription and examples pending human input.+### Prod-like QA (1 example)++QA every behavior change in a prod-like setting on the real system it touches before merge. Mocks and unit tests don't count; a missing credential is a blocker to solve or report, not a reason to merge.++- **Shipped changes for a provider without testing on that provider** (2026-10-12): [qm#2226](https://github.com/yc-software/qm/pull/2226) changed how the Fly deploy provider starts and supervises apps, and merged with only mocked unit tests for Fly. The agent had no working Fly token and shipped anyway.+### Performance (3 examples)Doing unnecessary work, repeating expensive work, or making independent work wait. Watch for hot polling loops, unbounded database reads, and locks that serialize unrelated operations. Token costs belong under Token performance.