Good catch on the hand-written style.css living inside the generated folder. A structural fix beyond the class-has-a-rule check is to move hand-authored assets into a separate source directory that the build copies in, so a clean of site/ can never touch them. For the rendering gap, a headless-browser screenshot diff on a handful of representative templates, or just asserting a computed style on the nav element, would also have caught the 375px overflow case you mentioned.