/* Legacy /assets/css/styles.css (Tailwind v3) is rendered into the LOW-PRIORITY
   `legacy` cascade layer, slotted AFTER Tailwind v4's `base` layer but BEFORE
   its `components`/`utilities` layers.

   Reasoning:
   - styles.css has ZERO @layer statements, so every rule it defines is
     UNLAYERED. CSS gives unlayered rules priority over ALL layered rules,
     regardless of specificity. That made legacy rules like `button{background-
     color:transparent}`, `a{color:inherit}` and `input{...}` override the
     portal's layered `.btn-primary` / `.text-accent-orange` / `.form-input`.
   - Here we pull that file in through a named layer: `legacy`.
   - Layer order matters (first-declared = lowest priority):
        properties < theme < base < legacy < components < utilities
   - `base` stays below `legacy` so Tailwind v4's preflight (e.g. heading
     font-size resets) does NOT re-clash with the legacy static-site styles on
     marketing pages.
   - `components`/`utilities` sit above `legacy`, so the new design system's
     classes (buttons, forms, accent links) always win on portal pages.

   Note: `@import` must precede every other rule except `@layer` statements,
   hence the order below. */
@layer properties, theme, base, legacy, components, utilities;
@import url("/assets/css/styles.css") layer(legacy);