max / goingson

Adopt CSS cascade layers so ordering stops being specificity's job @layer base, components, responsive. A layer beats specificity outright, so a responsive rule now wins over a component rule wherever it sits in the file, and inserting a component rule can no longer silently kill one. That hazard was the reason for this. `.ui-mode-mobile .foo` was (0,2,0) and `.foo` was (0,1,0), so which won was decided by a prefix; removing the prefix made file position start mattering, two rules had to be re-homed on the spot and two more were found already dead. Sections 25 and 59 exist only to manage cascade order and can now be collapsed, which is the next commit. Wrappers are inserted without re-indenting the 9800 lines they enclose, so the diff is the seven inserted constructs rather than the whole file. VERIFIED WITH A BEFORE/AFTER CASCADE DIFF, which the task said did not exist and which turned out to be the only reason this was safe. It parses every rule, models each rule's own selector as an element, resolves every property against every other rule that could match it, and reports where the winner changes between (importance, specificity, order) and (importance, layer, specificity, order). Control: demoting `responsive` below `components` produces 96 changes, so it detects what it claims to. Four winners changed. One was a real regression and is fixed here: `.event-row-virtual:last-child { border-bottom: none }` in §16 was outranked by §59's `.event-row-virtual`, so the last row of a compact event list would have grown a border the wide shell does not give it. §59 now restates it. The other three stand: - `.month-heatmap-cell` hover: §60 (touch) now beats the component rule. That is a FIX. §60 exists to disable hover on touch and currently fails to. - `.main-content` max-width in print: `100%` gives way to §24's `none`. Same intent, since both exist to not constrain it. - `.task-row:hover` background: print against a max-width 599px query. Print renders around 816px, so the two never co-occur; the diff over-reports across mutually exclusive queries deliberately. PRINT STAYS IN `components`, at its current position, which preserves today's print output exactly. Giving it a layer above `responsive` is arguably right and changes what prints in 8 places, because print currently loses to the component rules in §49-70 that follow it. Nobody has looked at that output, so it is filed rather than changed. UTILITIES stay in `components` for the same reason: they do not beat later component rules today either, so a lower layer would have changed behaviour. `.hidden` is `!important` and is unaffected.