/* App-surface CSS that utilities provably cannot express. * * Everything here was measured against Crosswind's generated sheet before it * was moved: pseudo-elements, attribute-state selectors, bare element * selectors, `@keyframes`, and page-scoped custom properties all produce NO * rule when written as a utility or variant. The failure is silent — no error, * no warning, just a class that does nothing — so the test is always "does the * served sheet contain it", never "does it look plausible". * * `config/crosswind.ts` `preflights` is where ch.11.2/11.7 says this belongs. * It does not work on the stx serve path: the entry is spread into the * generator config and then never emitted, verified with a probe token that * appears nowhere in the served CSS on any route. A linked stylesheet is the * substitute, and it is also the router-safe home — the SPA router destroys * every style that is not the Crosswind tag, but leaves s alone. * * Linked once from config/stx.ts `app.head.link`, after /tokens.css so it can * read the palette, before the Crosswind sheet so utilities still win a * specificity tie against anything here. * * Rules that WERE expressible are deliberately absent — they live as utilities * in the markup. Do not move a rule back here because it is more convenient. */ /* --------------------------------------------------------------------------- * Page-scoped tokens * * dashboard is the one surface with its own accent: indigo, so navigation * never reads as a severity colour (see 20f40ed). It used to be a `:root` * block inside dashboard.stx's