/* The cascade, declared once (2026-10-07). Read this before adding a rule anywhere.

   @layer corpus    the seven recovered stylesheets, in the order the pages load them: styles, allous, evolution,
                    lens, sanctum-theme, sanctum, frontier. They share ONE layer on purpose: they override each other
                    by specificity, in waves, so one layer per file would flip those decisions. Inside a single layer
                    the cascade is exactly what it was; a computed-style diff of every element on all three pages,
                    at 375 and 1280 px, proved it unchanged.
   @layer features  new modules: bodies.css (the models of every body of work), the Manifest. A rule here wins over
                    any corpus rule whatever the corpus selector weighs, so new work never needs a specificity war.
   @layer page      a page's own final word, used sparingly.

   Inline style attributes sit outside every layer and still win, as they always did.

   The map for a later cleanup of the corpus layer (where its files fight by specificity, found by the diff):
   - .systems-explorer padding-top and h2 max-width are declared !important in evolution, lens, sanctum-theme
     and sanctum; the most specific one (.sn-atlas .systems-explorer, sanctum) decides.
   - sanctum-theme restyles generic parts (.glass, .lm-node rect, .hero-copy, h3 letter-spacing) with #systems-sanctum
     or plain selectors; variants in earlier files (.move.on, .lm-node.core rect, .hero-short .hero-copy) win only
     because their selectors are heavier.
   scripts/release.cjs refuses a linked stylesheet that sits outside these layers. */
@layer corpus, features, page;