awesome-regression-sweeplisted

# Regression Sweep One question — *did anything break* — answered in layers, because the layers fail differently. A green unit suite says nothing about a byte format two independent implementations have to agree on; a passing suite says nothing about whether the code that is deployed is the code you tested; and a green working tree says nothing about the scheduled job that stopped running last night. Everything here is read-only. No deploy, no database write, no mutating admin call, no destructive suite against production. When a check would need one, say so and stop rather than doing it. Reference files (load the one the run needs): - [`references/live-contract-checks.md`](references/live-contract-checks.md) — the black-box checklist for a public read surface, the invariants of append-only and derived data, and the golden-vector method for cross-implementation parity. - [`references/deployment-and-infrastructure.md`](references/deployment-and-infrastructure.md) — proving the deployed code is the tested code, and the infrastructure layer that fails with no code change at all. Scripts (Node ≥18, no dependencies): - [`scripts/sweep.mjs`](scripts/sweep.mjs) — runs the aspect list from a config: one line per aspect, deltas against a stored baseline, per-aspect timeouts, output assertions for tools whose exit code lies, and a `SKIP` where a prerequisite is absent. - [`scripts/http-contract.mjs`](scripts/http-contract.mjs) — black-box probe of a public read endpoint: cache-key