The parity check compares every ported component against the design system's own preview, pixel for pixel, and for most of an evening it failed components that had passed all day — but only sometimes.
The first culprit was the check itself. It wrote a temporary copy of each preview into src/, the dev server spotted a new file and reloaded our page halfway through the capture. Moving the temp file out of the project fixed that, and the failures carried on anyway.
The real one was !important inside cascade layers. With reduced motion on, the design system sets every transition to 0.01ms with !important, inside a layer. The check had its own "no transitions" rule, also !important, but unlayered — and with !important the order flips, so the earliest layer wins and unlayered loses. Waiting a couple of frames was flaky, waiting for transitions to finish was flaky. Moving the rule into the first layer was one line and fixed it properly.
(Then a merge went through with a failing result because the command was piped through tail, which ate the exit code. Exactly the kind of thing the check is there to stop.)