/* ═══════════════════════════════════════════════════════════
   Capplon Design System — "Philip — Neutral" theme

   SUPPORTED and vendorable, same standing as philip-warm.css — a sibling,
   not a replacement. Ludvig's correction (2026-08-24, on a screenshot of
   WMS's /statistics/history): "instead we make the white background grey
   and the rest white! except the relevant stuff." That's an INVERSION of
   philip-warm's inverse layering, back to the conventional shape — a
   tinted page, white panels — while keeping the one thing philip-warm
   exists for: Capplon Blue (#2017DF) as the accent instead of tokens.css's
   default teal (WMS #423 — the default accent is wrong for WMS, full stop,
   independent of which neutral layering sits under it).

   "except the relevant stuff": color that carries meaning — the accent,
   status badges, KPI icon tints, scan in/out — stays exactly as it already
   is everywhere else in the system. This file touches ONLY the accent
   token group. Nothing else is overridden here on purpose, which is the
   whole point below.

   WHY THIS FILE HAS SO FEW OVERRIDES: tokens.css's own :root defaults
   (--tn-bg-page #F5F5F3, --tn-bg-card #FFFFFF, --tn-bg-hover #FAFAF8,
   --tn-border #E3E3E0, --tn-text-primary #1A1A1A, etc.) ARE ALREADY a
   light-grey-page / white-card / conventional-layering palette — that's
   what "Scandinavian Industrial" ships without any theme applied at all.
   Building a bespoke set of "neutral-grey" tokens here would just be
   redrawing values tokens.css already has, with the attendant risk of
   drifting from them over time. So this file does the minimum: swap the
   accent to Capplon Blue (reusing philip-warm.css's exact values, so a
   product switching between the two themes doesn't also get a second,
   unrelated accent-hue change) and let every neutral surface/text token
   fall through to tokens.css's real default. Two themes, one accent
   block, defined once (there — copied here, not var()'d, since each
   theme file is meant to be vendorable standalone).

   EXCEPTION TO "let it fall through" — --tn-text-secondary and
   --tn-text-muted, added 2026-08-24 (same day, found by scaneasy-agent
   vendoring into WMS): tokens.css's own defaults for these two
   (#5F6368, #686C72) are leftover Material Design grey-700/600 literals
   from before WMS's #463 cleanup, and #5F6368 specifically is on WMS's own
   banned-literal list (palette.spec.js). philip-warm.css was accidentally
   masking this the whole time — its own warm-toned #43413F/#726F6B
   overrides both of them, so the retired default was never actually
   reachable through that theme. This file's "fall through to tokens.css"
   premise assumed the defaults were clean; for these two specifically they
   aren't, so they're overridden here with genuinely distinct, cool/neutral
   -toned values (the counterpart to philip-warm's warm ones, not a re-hue
   of the retired Material greys) rather than left to fall through.
   tokens.css:93/101 themselves still ship the old values — that's a
   separate, bigger question (moving the *default* palette affects every
   consumer, themed or not) flagged to manager, not decided here.

   This is NOT the same as palettes.css's showcase-only "Philip — Light"
   (data-theme="philip-light") — that experiment keeps its own distinct
   beige/ink-toned neutrals (page #F7F4F1, border #DCDBDB, etc.) per
   Philip's brand spec. This file is deliberately plainer: tokens.css's
   own neutrals, unchanged, which is what "very light grey, not beige"
   turned out to mean once measured against the actual screenshot.

   --tn-bg-active follows the accent here, same as every other Philip
   palette in this repo (light/white/warm all repoint it to their own
   accent-light rather than leaving it on default's teal-tinted value) —
   an "active" surface reads as brand-colored, not as a leftover of
   whichever accent tokens.css shipped with.

   --tn-info is left alone (still teal), matching the precedent tokens.css
   itself documents for this palette shape: a theme that moves --tn-accent
   to a distinct brand color while keeping teal's own identity leaves
   --tn-info exactly where it was rather than following the accent.

   HOW TO USE:
     1. Vendor tokens.css (required, as always) + this file.
     2. Link this file AFTER tokens.css: <link rel="stylesheet" href=".../philip-neutral.css">
     3. Set `<html data-theme="philip-neutral">` wherever this look should
        apply — the whole document, or scope it narrower if your app
        supports multiple concurrent themes.
   ═══════════════════════════════════════════════════════════ */

html[data-theme="philip-neutral"] {
    --tn-accent: #2017DF;
    --tn-accent-hover: #09046E;
    --tn-accent-active: color-mix(in srgb, #09046E 82%, black);
    --tn-accent-light: #EEF0FE;
    --tn-accent-contrast: #fff;
    --tn-accent-rgb: 32, 23, 223;
    --tn-bg-active: #EEF0FE;
    /* Cool/neutral counterparts to philip-warm's #43413F/#726F6B — not a
       re-hue of tokens.css's own #5F6368/#686C72 (retired Material grey,
       see header). Both clear 4.5:1 on --tn-bg-card (#FFFFFF) and
       --tn-bg-page (#F5F5F3) with margin: secondary 9.03:1/8.27:1, muted
       5.11:1/4.68:1. */
    --tn-text-secondary: #454951;
    --tn-text-muted: #6B6E75;
}