/* ──────────────────────────────────────────────────────────────────
   This deployment's theme — replaceable AFTER the build.

   The console links `/deployment/theme.css` from every page. Editing it
   here re-themes the next build; replacing it in the SERVED directory
   re-themes a deployment already running, with no rebuild. Both are
   supported, and which you use is an operational choice.

   The full contract, the rules and the reasoning are in the console's
   own stub — read it once:

     node_modules/@acaso/os-console/public/deployment/theme.css

   The four rules in short:

     1. Token overrides go inside `@layer acaso.theme`. Layer order beats
        specificity AND load order, so you need no `!important` and no
        repeated `:root:root` selectors.
     2. Prefer PRIMITIVES (`--brand-*`, `--neutral-*`). A derived token
        (`--bg-*`, `--fg-*`, `--border-*`) set in `:root` alone also beats
        the `.dark` rule meant to answer it, flattening dark mode.
     3. Never target `--font-sora`. Override `--font-sans`,
        `--font-display`, `--font-mono`.
     4. `url()` in a custom property must be root-absolute, or it 404s in
        Safari while working in Chrome.

   Check before shipping — it measures contrast in both schemes and
   fails on anything this theme breaks relative to the stock console:

     npm run check-theme
   ────────────────────────────────────────────────────────────────── */

@layer acaso.theme {
  :root {
    /* Delete this block for the stock acaso look, or replace the values.

       --brand-500:      #d5571a;
       --neutral-100:    #faf5ec;
       --font-sans:      "Whyte Inktrap", ui-sans-serif, system-ui, sans-serif;
       --radius-control: var(--radius-full);
       --logo-mark-image: url("/deployment/brand/mark.svg"); */
  }
}