/* Cascade-layer order — shipped as a VERBATIM public/ asset and linked FIRST in (see BaseHead.astro) so it registers before any bundled stylesheet. WHY THIS FILE EXISTS (rather than only the `@layer …;` line in global.css): global.css declares this same order at its top, and the `css-layer-order` integration (astro.config.mjs) injects global.css first on every page — both aimed at this exact problem. BUT the production CSS minify (lightningcss, run by @tailwindcss/vite) PRUNES that statement down to `@layer kdd,components;`, dropping `base`. The design system lives in `@layer kdd`; Tailwind's preflight reset (`*,::after,::before,::backdrop { padding: 0 }`) lives in `@layer base`. With `base` pruned from the order statement it re-registers AFTER `kdd` (i.e. HIGHER priority), so the reset out-ranks the DS and zeroes every component's padding/border (the Quote rendered edge-to-edge with no inset). The dev server skips that minify pass, so the bug is PROD-ONLY and invisible locally. A file under public/ is copied byte-for-byte to dist/ — Vite/lightningcss never touch it — so the full statement survives and fixes the layer order for the whole document. As an external same-origin sheet it is covered by the strict CSP's `style-src 'self'` and needs no per-file hash. Keep this the first stylesheet the document loads. */ @layer theme, base, kdd, components, utilities;