max / goingson

Collapse the two compact passes into one Sections 25 and 59 were the same pass split in two purely to manage cascade order, one "early, so feature CSS can override it" and one "late, so it wins conflicts", with the legend telling you which to add to. `@layer responsive` decides that now, so the split has no job left. Section 25's block moves down to join 59 and keeps its position ahead of it, because within a layer source order still settles ties between the two halves. The legend, the TWO SHELLS note and the band map are updated with it. VERIFIED BEHAVIOUR-NEUTRAL TWO WAYS, and the second caught a real bug the first and the linter both missed: - Every layer's rule sequence is compared before and after, as (selector, media, declarations). base 5, components 1497, responsive 160, all three identical. A relocation that preserves per-layer order cannot change the cascade, which is the argument this makes mechanical. - Every resolved declaration is compared, keyed on (element, media context, property). No winner changed. The bug: section 25's header was a multi-line comment and only its first line was dropped in the move, leaving a stray `*/` that closed the new comment early and turned the following prose into garbage CSS. The `@media` block after it stopped being a media block. `lint-frontend.sh` passed, the minifier was happy, and the byte count barely moved. The sequence check is what found it, by showing those rules had lost their media context.