/* Cascade layer order for the public site — declared once, loaded first. See docs/CSS-ARCHITECTURE.md.

     reset        box model, element resets
     tokens       design tokens: custom properties only (colour in theme.css, everything else in tokens.css)
     base         element defaults and accessibility primitives (focus ring, skip link, screen-reader text)
     layout       page shell: sidebar, rail, header, bottom bar, responsive frames        (media queries; css/layout.css)
     components   shared component chrome: panels, buttons, matrix, dialogs, detail host  (container queries)
     utilities    a few single-purpose helpers
     views        the six page views' own rules (css/views.css) + the print sheet (css/print.css)

   `views` is LAST, and it holds BOTH the page views' rules and print.css. That pairing is the whole trick, and it is
   what makes the printed page come out identical to the pre-refactor build:

     - for NORMAL declarations a later layer wins, so the view rules out-rank `components` and the print rules out-rank
       every screen sheet — which is what "unlayered" used to give them;
     - for `!important` the layer order is REVERSED, so this last layer sits BELOW `utilities` — which is exactly where
       the unlayered print sheet was, and where `utilities`' `[hidden]{display:none!important}` can still beat print's
       `display:block!important`.

   No single named layer can reproduce both at once: put print later and it wins screen rules it used to lose to; put it
   earlier and its `!important`s win where they used to lose. All four placements were measured — only this one gives
   18/18 print scenes pixel-identical. See docs/CSS-ARCHITECTURE.md §19.4, and docs/PRINT-STYLES.md.

   Inside the layer, source order still decides ties, so index.html loads css/views.css before css/print.css.

   Engines without @layer ignore this file and every layered block, which is why css/flat.css exists: it flattens every
   layered stylesheet in layer order. */
@layer reset, tokens, base, layout, components, utilities, views;