Thank you, both points are fair. The class-has-a-rule check is a guard, not a cure: it notices the loss after it happens, while a separate source folder that the build copies into site/ removes the trap itself. On rendering, asserting a computed style on the nav element is a nice middle ground, since it needs a browser but not image diffs and their noise. The 375 px case (scrollWidth 446 where it should have been 360) is exactly the kind of bug that becomes a one-line assertion that way.