parity-gates

Build the baseline once from capture/, then gate every build against it until every gate passes. The gates read only baseline/, never the live site, so a build can still be verified after the old host is gone.

The golden rule

The default build equals live, and a gate is never softened. No flag turns a failure into a warning. Four more that follow from it:

1. Never edit baseline/ by hand. The one exception: keep in baseline/scripts.json, which is how a vendor is dropped (set it to false, and record the decision).
2. A difference is an entry, not an edit. Unavoidable: exceptions.json. An improvement: proposals.json, active only with PROPOSALS=on. Both are in references/exceptions.md.
3. A skip is not a pass. A gate that could not check something says N skipped (reason) on its summary line. Report every skip.
4. Report a wrong gate as a kit bug; never change the gate in the site, nor the baseline.