/* =====================================================================
   The Collectorium — CSS entry point
   ---------------------------------------------------------------------
   Single stylesheet loaded by templates/base.html.twig. Cascade layers
   order the design system, later layers beating earlier ones:

     tokens      → design tokens (custom properties, theming)
     base        → self-hosted font, reset, semantic typography
     components  → v3 component styles
     pages       → per-page v3 styles

   The layer order is the override order, and it beats selector
   specificity: a rule in `components` can never override one in `pages`,
   however specific it is. Put a rule in the layer that owns the thing it
   styles rather than reaching for specificity to win.

   Through the v3 migration there was also a `legacy` layer first, holding
   the pre-v3 stylesheets, plus a `legacy-bridge.css` that pinned
   not-yet-migrated page bodies to a light surface so they stayed legible
   in the dark theme. Web v3 · 17 removed both once the last page that
   needed them was migrated.
   ===================================================================== */

@layer tokens, base, components, pages;

@import url('v3/tokens.css') layer(tokens);
@import url('v3/base.css') layer(base);

@import url('v3/components.css') layer(components);
@import url('v3/shell.css') layer(components);

@import url('v3/pages/auth.css') layer(pages);
@import url('v3/pages/category.css') layer(pages);
@import url('v3/pages/collection.css') layer(pages);
@import url('v3/pages/forms.css') layer(pages);
@import url('v3/pages/item.css') layer(pages);
@import url('v3/pages/profile.css') layer(pages);
@import url('v3/pages/search.css') layer(pages);
@import url('v3/pages/static.css') layer(pages);
