/* ============================================================
   Baridy Design System — tokens.css
   3-layer token architecture (see docs/plan/07-DESIGN-SYSTEM.md §2).
   THE ONLY FILE THAT KNOWS HEX VALUES. Everything else uses var().
   ============================================================ */

/* ---- @font-face — four self-hosted variable fonts (no external URLs) ---- */
/* Plus Jakarta Sans is PINNED to the Google-served build the mockups load (v12 variable woff2,
   latin-ext + latin slices) — 2026-07-19 lead parity fix, same class as the Inter pin below:
   the previous variable TTF painted ~1.3% narrower than the mockup (402.4 vs 407.9px at weight
   400). The 500 800 weight range mirrors the mockup's Google request (wght@500;600;700;800) so
   out-of-range weights CLAMP exactly as they do in the mockup browser (e.g. 400 renders as 500). */
@font-face {
    font-family: 'Plus Jakarta Sans';
    src: url('../fonts/PlusJakartaSans-v12-latin-ext.woff2') format('woff2');
    font-weight: 500 800;
    font-display: swap;
    unicode-range: U+0100-02BA, U+02BD-02C5, U+02C7-02CC, U+02CE-02D7, U+02DD-02FF, U+0304, U+0308, U+0329, U+1D00-1DBF, U+1E00-1E9F, U+1EF2-1EFF, U+2020, U+20A0-20AB, U+20AD-20C0, U+2113, U+2C60-2C7F, U+A720-A7FF;
}
@font-face {
    font-family: 'Plus Jakarta Sans';
    src: url('../fonts/PlusJakartaSans-v12-latin.woff2') format('woff2');
    font-weight: 500 800;
    font-display: swap;
    unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+0304, U+0308, U+0329, U+2000-206F, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD;
}
/* Inter is PINNED to the exact Google-served build the mockups load (Inter v20 variable woff2,
   latin-ext + latin slices, same unicode-ranges, same order) — 2026-07-19 lead parity fix: the
   previous Inter-variable.ttf was a different build that painted Latin text ~1% wider than the
   mockup. Re-pin by re-downloading from fonts.gstatic.com/s/inter/v20/ if the mockup ever updates.
   The 400 800 weight range mirrors the mockup's Google request (wght@400;500;600;700;800) so
   out-of-range weights CLAMP exactly as in the mockup browser (e.g. 900 renders as 800). */
@font-face {
    font-family: 'Inter';
    src: url('../fonts/Inter-v20-latin-ext.woff2') format('woff2');
    font-weight: 400 800;
    font-display: swap;
    unicode-range: U+0100-02BA, U+02BD-02C5, U+02C7-02CC, U+02CE-02D7, U+02DD-02FF, U+0304, U+0308, U+0329, U+1D00-1DBF, U+1E00-1E9F, U+1EF2-1EFF, U+2020, U+20A0-20AB, U+20AD-20C0, U+2113, U+2C60-2C7F, U+A720-A7FF;
}
@font-face {
    font-family: 'Inter';
    src: url('../fonts/Inter-v20-latin.woff2') format('woff2');
    font-weight: 400 800;
    font-display: swap;
    unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+0304, U+0308, U+0329, U+2000-206F, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD;
}
@font-face {
    font-family: 'JetBrains Mono';
    src: url('../fonts/JetBrainsMono-variable.ttf') format('truetype');
    font-weight: 100 800;
    font-display: swap;
}
@font-face {
    font-family: 'Alexandria';
    src: url('../fonts/Alexandria-variable.ttf') format('truetype');
    font-weight: 300 900;
    font-display: swap;
}
/* Tajawal is a static-weight family (no variable file exists) — one face per weight.
   HISTORY: briefly the admin body font (2026-07-19 Tajawal wave), REVERSED the same day by the
   designer-README intake ruling (Arabic body = Alexandria; the mockup's runtime Tajawal injection
   was a designer-declared bug). The admin site.css override is gone; nothing references Tajawal
   now, so these declarations load nothing anywhere — kept only in case the designer's updated
   mockup build re-legitimizes the family (CHANGELOG 2026-07-19). Weight 600 intentionally
   absent (the family has none) — the browser resolves 600 to the 700 face. */
@font-face {
    font-family: 'Tajawal';
    src: url('../fonts/Tajawal-Regular.ttf') format('truetype');
    font-weight: 400;
    font-display: swap;
}
@font-face {
    font-family: 'Tajawal';
    src: url('../fonts/Tajawal-Medium.ttf') format('truetype');
    font-weight: 500;
    font-display: swap;
}
@font-face {
    font-family: 'Tajawal';
    src: url('../fonts/Tajawal-Bold.ttf') format('truetype');
    font-weight: 700;
    font-display: swap;
}
@font-face {
    font-family: 'Tajawal';
    src: url('../fonts/Tajawal-ExtraBold.ttf') format('truetype');
    font-weight: 800;
    font-display: swap;
}

/* ============================================================
   LAYER 1 — primitives (raw values, never used directly by views)
   ============================================================ */
:root {
    /* palette */
    --kp-navy-600: #0033a0;
    --kp-navy-700: #002680;
    --kp-navy-500: #1a4db8;
    /* navy alphas — mockup .user-civil-id pill + .user-nationality-chip (style.css:9253/9270,
       2026-07-23 subscribers parity) */
    --kp-navy-600-a22: rgb(0 51 160 / .22);
    --kp-navy-600-a08: rgb(0 51 160 / .08);
    --kp-navy-500-a10: rgb(26 77 184 / .1);  /* the official #1A4DB8 at 10%: the shipment route's sending pill (Core Rule 13 palette clause) */
    --kp-navy-600-a06: rgb(0 51 160 / .06);
    --kp-navy-600-a04: rgb(0 51 160 / .04);
    --kp-navy-600-a03: rgb(0 51 160 / .03);  /* corporate mock .corp-grid line colour (corporate-details.css:53, 2026-10-10 company pages' ground) */
    --kp-slate-50: #f8fafc;
    --kp-slate-100: #f1f5f9;  /* mockup --border-light (style.css:113) — nav-link hover fill (P4 shell parity item 13) */
    --kp-white: #fff;
    --kp-slate-900: #0f172a;
    --kp-slate-600: #475569;
    --kp-slate-500: #64748b;
    --kp-slate-400: #94a3b8;
    --kp-slate-300: #cbd5e1;  /* mockup scrollbar-thumb / .perm-toggle off-track (style.css:7171 slider); permission-matrix toggle off-track, 15 #96 F13d */
    --kp-slate-200: #e2e8f0;
    --kp-gold-500: #cba052;
    --kp-gold-300: #dfc080;
    /* gold @ .12 alpha — mockup .type-chip-doc discount-pill fill (style.css:4869); spelled as its own
       primitive per this file's alpha precedent (a custom property can't parameterize alpha). 15 #96 F11. */
    --kp-gold-500-a12: rgba(203, 160, 82, .12);
    --kp-coral-500: #ff6b4a;
    /* emerald-500 = #009a44 per the admin mockup-v2 brand rebrand (2026-07-18, supersedes the old
       #10b981); -600 arrived with the portal B1 branch (portal-mockup value); -700 (#047857) is
       defined once below in the P3 text-safe status-tone block (merge dedupe 2026-07-19). */
    --kp-emerald-500: #009a44;
    --kp-emerald-600: #059669;
    --kp-emerald-900: #065f46;
    --kp-violet-600: #7c3aed;
    --kp-violet-900: #5b21b6;
    --kp-red-600: #c8102e;
    /* Bootstrap's important danger utilities read this channel. Palette clause 15 #137 D1 requires
       their ink to resolve to the official Kuwait Mail red instead of the vendor default. */
    --bs-danger-rgb: 200, 16, 46;
    /* Cyan — the mockup's true .role-type-badge.custom hue (style.css:7305-7309: #0ea5e9 tint / #0284c7 text).
       Mints the family the earlier "no-new-cyan-hex" deviation lacked; retargets the custom role badge from
       our navy surrogate to the mockup's cyan (owner design-review batch 2026-07-23, ledger 15 #96 F7). */
    --kp-cyan-500: #0ea5e9;
    --kp-cyan-600: #0284c7;
    --kp-amber-500: #f59e0b;
    --kp-amber-900: #78350f;
    /* vbx-card suspended/expired edge-gradient ends + status dots (mockup style.css:9473-9474 &
       9538-9539; subscribers view-drawer parity 2026-07-23). */
    --kp-amber-400: #fbbf24;
    --kp-red-400: #f87171;

    /* spacing (4 / 8 / 16 / 24 / 32) */
    --kp-space-xs: 4px;
    --kp-space-sm: 8px;
    --kp-space-md: 16px;
    --kp-space-lg: 24px;
    --kp-space-xl: 32px;

    /* radii */
    --kp-radius-xs: 4px;
    --kp-radius-sm: 6px;
    --kp-radius-md: 8px;
    --kp-radius-lg: 10px;
    --kp-radius-xl: 12px;
    --kp-radius-full: 999px;

    /* layout */
    --kp-sidebar-w: 264px;
    --kp-topbar-h: 64px;
    /* PO-20 / 15 #190g (2026-09-08), amended by the owner on 2026-09-09: below the desk tier the admin page
       title takes a smaller size first (tablet 15px, phone 13px) and drops to its own row under the top bar ONLY
       when it still does not fit beside the bar's controls; the row height and the two sizes are tokens so the
       shell and its pin agree. */
    --kp-topbar-title-row-h: 36px;
    --kp-topbar-title-tablet-size: 0.9375rem;
    --kp-topbar-title-phone-size: 0.8125rem;

    /* Layer 1 additions — admin shell + drawers (mockup port, spec 2026-07-12) */
    --kp-drawer-w: 560px;
    --kp-drawer-w-lg: 760px;
    --kp-drawer-w-sm: 420px;
    /* The WIDE detail drawer — the subscriber drawer only (spec 2026-07-27 §2.6, owner rounds 2+5:
       "about half the page", trimmed from the first 720px/56vw). The 680px floor sits ABOVE the
       575.98px mobile breakpoint on purpose, so between 576px and 680px of viewport it is the
       min(…, 100vw) in the .modal-drawer--xl modifier — not the media query — that keeps the dialog
       inside the screen. */
    --kp-drawer-w-xl: clamp(680px, 52vw, 1000px);

    /* Layer 1 additions — launchpad card grid (mockup main.html .launch-grid/.launch-card, Task 3).
       Dated 2026-11-10 (risk row HAC-LAUNCHER-DS-LEFTOVERS): the launcher left with owner ruling 15 #904(a) and
       its two card-size tokens, which nothing read any more, are removed; the two spacing steps stay, read by
       many other rules. */
    --kp-space-14: 14px;
    --kp-space-22: 22px;

    /* Layer 1 additions — modal drawers (mockup style.css §29 .modal-body, Task 5 fix batch 1) */
    --kp-space-28: 28px;

    /* Layer 1 additions — auth-shell brand/form panel padding (mockup login.html
       .auth-brand/.auth-form, style.css:9100,9197; Task 7) */
    --kp-space-48: 48px;
    --kp-space-56: 56px;
    --kp-space-64: 64px;

    /* Layer 1 additions — auth-card composition exact spacing (mockup login.html
       .auth-brand-eyebrow/.auth-brand-tagline h1 style.css:9156,9169 and
       .auth-card-hint style.css:9236; Task 7 fix batch 1) */
    --kp-space-18: 18px;
    --kp-space-36: 36px;

    /* Layer 1 additions — page background-wash gradient stops (mockup style.css lines 170-198
       body::before/::after; Phase A-2 Task 1). Named as a primitive family (not a palette shade) because
       each stop carries the mockup's exact alpha; the underlying rgb triplets equal existing palette
       entries where one exists (kp-navy-500/600, kp-gold-500, kp-coral-500, kp-gold-300) — reproduced here
       instead of re-deriving alpha from var() (CSS custom properties can't parameterize a color's alpha
       channel without color-mix()/relative-color syntax, so the stops are spelled out directly). */
    --kp-wash-a-1: rgb(26 77 184 / .85);
    --kp-wash-a-2: rgb(0 51 160 / .55);
    --kp-wash-a-3: rgb(120 80 255 / .25);
    --kp-wash-b-1: rgb(203 160 82 / .65);
    --kp-wash-b-2: rgb(255 107 74 / .5);
    --kp-wash-b-3: rgb(223 192 128 / .25);

    /* Layer 1 additions — subscriber-portal mockup palette (docs/reference/postOffice_PublicUser_html,
       intake ruling 13 D17 2026-07-17). Sources verified by the session lead 2026-07-17:
       css/theme-parity.css :root (--blue #0033a0 / --blue-2 #002680 / --gold #cba052 — the JS-injected
       final CTA/brand layer, react-parity.js:486) and css/app.css (--postal-navy(-deep/-soft),
       --stamp-gold(-soft), --delivered-green, --alert-red). The mockup's #ff6b4a and #f59e0b already
       exist above as --kp-coral-500/--kp-amber-500 and are NOT re-added. These are a SECOND navy/gold
       family (brand chrome), not shades of --kp-navy-*: the portal uses both. */
    --kp-postal-navy-600: #0033a0;
    --kp-postal-navy-700: #002680;
    --kp-postal-navy-400: #1a4db8;
    --kp-stamp-gold-500: #cba052;
    --kp-stamp-gold-300: #dfc080;
    --kp-green-700: #009a44;
    --kp-red-700: #c8102e;
    /* Task 4 (2026-07-18 portal-box-data-and-linking plan): the populated dashboard ticket's footer
       action-button background (--kp-navy-600 at the mockup's measured 5% alpha, live cascade probe
       -- CSS custom properties can't parameterize alpha without color-mix()/relative-color syntax, so
       per this file's wash-token precedent above the alpha variant is spelled out as its own
       primitive). The VBX-side equivalent used to reuse --portal-ship-gold-tint below; since the P3 fix
       round (2026-08-08) it spells its own measured .10/.18 pair in components.css instead, because the
       reference's gold wash is a step lighter than that shared token's .13.
       Restyle P3 D1 mapping (2026-08-08): the triplet was the PRE-REBRAND blue (17 94 232 = #115ee8),
       which the v2 package still paints and the palette clause forbids copying. Same 5% alpha, official
       navy triplet -- this is the token's ONE consumer (.dc-ticket-action), so the swap is local.
       (Dated clause 2026-10-19: no longer the one consumer - among others, the Delegation page's Add control reads it
       for its hover wash, Portal site.css `[data-surface="standing"] .poa-add:hover`.) */
    --kp-navy-600-a05: rgb(0 51 160 / .05);
    /* The Delegation page's standing-delegate rules (Portal site.css, [data-surface="standing"], dated 2026-10-19):
       the alphas those rules painted as literal colours, each spelled as its own primitive per this file's alpha
       precedent (a custom property cannot supply only the alpha of a colour). Every triplet is an official palette
       colour - navy #0033A0, green #009A44, red #C8102E - at the alpha the page already rendered, so the swap from the
       literal to the token leaves every computed colour as it was (measured before and after in both languages).
       The 5% navy wash is not repeated here: the page reads --kp-navy-600-a05 above and --kp-portal-icon-tint-blue
       below, which already carry it. The two zero and 9% greens are the 0% and 50% stops of the page's breathing ring
       around the active badge. The equal-value tokens that already exist were checked and deliberately not borrowed:
       the semantic ones (--color-focus-ring at navy .30, --color-stat-icon-navy-bg at navy .1) name another job, and the
       component ones (--portal-ship-navy-tint, --portal-ship-green-tint at .10) belong to the shipments family, so a later
       change to either would silently repaint this page; a primitive of the same value keeps the two independent. */
    --kp-navy-600-a10: rgb(0 51 160 / .1);
    --kp-navy-600-a30: rgb(0 51 160 / .3);
    --kp-navy-600-a90: rgb(0 51 160 / .9);
    --kp-green-700-a00: rgb(0 154 68 / 0);
    --kp-green-700-a09: rgb(0 154 68 / .09);
    --kp-green-700-a10: rgb(0 154 68 / .1);
    --kp-red-700-a05: rgb(200 16 46 / .05);
    --kp-red-700-a25: rgb(200 16 46 / .25);

    /* Layer 1 additions -- portal feedback layer (dialogs/toasts/inline-validation, fix wave 2,
       the mockup dialog spec; ruling B2, the 2026-07-18 re-judgment). Confirmed
       FINAL by the spec doc's cascade trace (react-parity.css :root, NOT overridden by
       theme-parity.css -- see spec §0/§4.2) so these are safe to treat as the live values, not a
       stale layer. --kp-portal-danger-500 is the badge/banner/icon red (rp-chip.danger fg,
       .sr-dialog-icon.danger); --kp-portal-danger-btn-500 is a SEPARATE, punchier destructive-
       BUTTON red the mockup itself uses only for its one real danger button
       (.plan-cancel-confirm button.danger, react-parity.css:295) -- the two are genuinely
       different mockup values, not a duplicate to consolidate.
       RE-POINTED 2026-08-08 (portal mockup v2 intake ruling D6, 15 #148; restyle package P1): the
       #c9545b above was a PRE-REBRAND red carried in from the v1 package. The official alert red
       supersedes it, so this token now resolves to --kp-red-700 (#C8102E) and every surface reading
       it -- the inline validation panel, the required-field marker, the SweetAlert2 error icon and
       the danger focus ring below -- moves to the official red together. The BUTTON red is NOT
       named by D6 and is left as-is pending its own ruling. */
    --kp-portal-danger-500: var(--kp-red-700);
    --kp-portal-danger-btn-500: #c43c43;
    --kp-portal-toast-bg: #182236;

    /* Layer 1 additions — portal radii (mockup theme-parity.css: .dc-status-tab/.dc-ship-panel/
       .dc-shipment/.dc-appointments 16px; .dc-hero 18px mobile / 24px desktop) */
    --kp-radius-2xl: 16px;
    --kp-radius-3xl: 18px;
    --kp-radius-4xl: 24px;

    /* Layer 1 additions — portal shell layout. HISTORY: these were 256px rail / 1408px max-width /
       "the 64px header equals the existing --kp-topbar-h and is NOT re-added", all read off the v1
       package's theme-parity.css. All three sentences are superseded below -- the portal now has its
       own 68px topbar token, and the rail/max-width carry the v2 measurements. */
    --kp-portal-rail-w: 272px;
    --kp-portal-rail-w-compact: 80px;
    --kp-portal-content-max-w: 1632px;
    /* Portal topbar height. NOT --kp-topbar-h: that token is 64px and the ADMIN reads it too, so the
       portal's own 68px gets its own name rather than moving a shared value under the admin's feet.
       Dated clause 2026-11-05 (owner ruling 15 #1020): the bigger ministry logo needs a taller header, 76px on a phone
       and 88px at 721px and wider; the wide value has its own name, read in the Portal's stylesheet. */
    --kp-portal-topbar-h: 76px;
    --kp-portal-topbar-h-desktop: 88px;
    /* PORTAL MOCKUP v2 RE-MEASURE (restyle package P1, 2026-08-08; intake ruling D6, 15 #148).
       Rail 256 -> 272 and the header/wrap max-width 1408 -> 1632 come from the v2 bundle's own
       measured shell (css/sidebar-navigation.css --sidenav-expanded-width + css/app-pages.css
       .rp-header/.rp-wrap). The compact rail stays 80px; its BAND stays 721-1279px -- see the
       components.css compact-band comment for why D6's "1024-1279" phrasing is not a band change.
       Dated clause 2026-10-16 (15 #429(b)): the compact band is now 721-1023px; from 1024px the labelled
       272px rail shows, a dated departure from the reference's 1280. The two widths above are unchanged. */

    /* Layer 1 additions — typography scale (mockup css/style.css :root lines 21-31; adopted in the
       SHELL in P2, components in P3). NOTE: --leading-body is DELIBERATELY NOT added here — the name
       already exists in the font-semantics block below with a culture-switched value (1.5 / 1.625 for
       Arabic); the mockup's constant 1.6 body-leading is a P3 reconciliation, never a silent clobber. */
    --text-caption: 0.75rem;
    --text-small: 0.8125rem;
    --text-ui: 0.875rem;
    --text-body: 0.875rem;    /* 14px — admin body baseline per mockup v3's deployed-reference :root
                                 (postOfficeAdmin-2/css/style.css:10702; ruling 15 #137, 2026-08-02),
                                 which lowered it from the 1rem this group was first adopted at.
                                 CONSTRAINT: this is the SHARED Layer-1 sheet — the portal loads it too —
                                 but the VALUE is admin-derived. As of 2026-08-02 its only consumer anywhere
                                 is the Admin body rule (KwtPost.Admin/wwwroot/css/site.css); the portal has
                                 none. A portal author must NOT bind to this token expecting the 16px it used
                                 to carry: reuse a portal-scoped size or mint one instead. */
    --text-subheading: 1rem;
    --text-heading-sm: 1.125rem;
    --text-heading: 1.625rem;
    --text-display: 1.75rem;
    --leading-tight: 1.25;
    --leading-ui: 1.45;

    /* Layer 1 addition — shell motion easing (mockup css/style.css :root line 149) */
    --ease-smooth-out: cubic-bezier(0.16, 1, 0.3, 1);
    /* Layer 1 addition — the Material "standard" curve the portal v2 topbar uses for its colour
       transitions (app.bundle.css:885, restyle package P1 2026-08-08); --ease-smooth-out stays the
       curve for the same controls' TRANSFORM leg, exactly as the package pairs them. */
    --ease-standard: cubic-bezier(0.4, 0, 0.2, 1);

    /* Layer 1 additions — navy soft tints for the topbar-control cluster hover + the user-dropdown
       header band / active states (mockup css/style.css :root --primary-light #e6f0fe line 38,
       --primary-lighter #f1f6ff line 39). These are new palette shades; no existing token holds them. */
    --kp-navy-100: #e6f0fe;
    --kp-navy-050: #f1f6ff;

    /* Layer 1 addition — unified icon-container radius (mockup css/style.css :root line 128
       --icon-radius: var(--radius-xs); mockup --radius-xs = 6px == OUR --kp-radius-sm, NOT --kp-radius-xs
       which is 4px — the radius scales are offset). */
    --icon-radius: var(--kp-radius-sm);

    /* Layer 1 additions — mockup text-safe status tones (P3 badge/status rebuild; mockup style.css :root).
       --success #047857 / --warning #b45309 are darker, WCAG-text-safe variants, DISTINCT from the
       delivered-green --kp-emerald-500 (#009a44) and amber --kp-amber-500 (#f59e0b); --stamp-gold-text /
       --dispatch-coral-text are the text-safe gold/coral tones. Added as primitives now (documentation +
       future text use); the badge borders below spell their rgba forms literally because a custom property
       cannot parameterize a color's alpha channel (same precedent as the --kp-wash-* tokens). */
    --kp-emerald-700: #047857;      /* mockup --success            (style.css:62) */
    --kp-amber-700: #b45309;        /* mockup --warning            (style.css:65) */
    --kp-stamp-gold-text: #765700;  /* mockup --stamp-gold-text    (style.css:52) */
    --kp-coral-text: #c2410c;       /* mockup --dispatch-coral-text (style.css:58) */

    /* Layer 1 addition — admin input-border parity fix (lead ruling on the drawer ritual's app-wide
       finding, 2026-07-18 P4 batch). Distinct from --kp-slate-200/-600 (no existing shade matches). */
    --kp-input-border: #8290a3;       /* mockup --input-border       (style.css:154) */
    --kp-input-border-hover: #5b677a; /* mockup --input-border-hover (style.css:155) */
    --kp-slate-550: #5b677a;          /* mockup secondary-muted TEXT (bc-email/bc-lbl, live-measured
                                         2026-07-19); same hex as --kp-input-border-hover by mockup
                                         coincidence — kept separate for semantic clarity */

    /* Layer 1 additions — sticky-column edge-line tints (owner ruling B5, 2026-07-19; mockup branches
       sticky first/last-column box-shadow edges, style.css:8579/8582/8589). Two light blue-gray hairlines
       DISTINCT from --kp-slate-200 (#e2e8f0, the standard border): a stronger frame edge (#d9e1ea = header
       row + last/sticky-end column) and a softer body edge (#e8edf3 = body first/sticky-start column).
       Tokenized so the reusable .table-custom--sticky-edges modifier carries no raw hex. */
    --kp-slate-edge: #d9e1ea;
    --kp-slate-edge-soft: #e8edf3;

    /* (The --kp-th-band #f3f6fa / --kp-th-text #526176 heavy grid-header primitives lived here until
       2026-08-02. Their only consumer was the Branches page-scoped heavy-band override in the admin
       site.css, retired with the rest of that family by the mockup-v3 restyle wave U1 — one light band on
       every grid, owner ruling D6, ledger 15 #137 — so they were removed rather than left orphaned.) */

    /* Solid stat-icon tile fills (mockup .stat-icon.{blue,green,orange,cyan} — live-measured
       2026-07-19: the mockup paints SOLID tiles, not white-dependent rgba tints; green fg is the
       mockup --success #047857). blue reuses --kp-navy-100 (#e6f0fe) via the Layer-2 alias below. */
    --kp-tile-green: #d1fae5;
    --kp-tile-orange: #fef3c7;
    --kp-tile-cyan: #e8eef5;
    --kp-tile-purple: #ede9fe;   /* mockup --purple-light (style.css:75) — the solid purple tile */
    --kp-emerald-700: #047857;
    /* Layer 1 additions — portal shell chrome (mockup react-parity.css .rp-* rules lines 5-17 +
       .notification-bell line 170; shell phase 2026-07-17, intake 13 D17). Near-duplicate mockup
       border grays (#e9edf4/#e8ebf0/#e6eaf0/#e8ebf1) are consolidated to --kp-slate-200 and the
       #111827 topbar ink to --kp-slate-900 (visual-equivalence house-law conversion, Core Rule 13
       carve-out — recorded in the plan's divergence ledger); every value below is genuinely new
       to the system and mockup-exact. */
    /* P1 re-measure (portal mockup v2, 2026-08-08): the rail/topbar chrome below was re-pointed to the
       values the v2 bundle's LAST layer (css/sidebar-navigation.css) actually paints. Every one of them
       resolves to an EXISTING slate/official-brand primitive — nothing new was minted, and the D1 palette
       clause is satisfied by construction (the package's stale #0a47bd marker, #1345aa mobile-active,
       #c95960 sign-out and #2da664 online dot are NEVER copied; they map to official navy/red/green). */
    --kp-portal-nav-ink: var(--kp-slate-600);   /* rail nav resting text — v2 #475569 */
    /* Fix-wave 3 (2026-07-18 live-parity ledger item 6, L1381/1385): the lead reversed the general
       "consolidate near-duplicate border grays" policy above for .rp-header-back specifically --
       dedicated tokens so the shared --kp-portal-nav-ink/--color-border stay untouched elsewhere.
       THE INK MOVED TO SLATE-900 (parity round 2, fix package E item E9a, 2026-08-12). #314056 was a
       v1 value; the rendered portal mockup v2 paints this control's glyph rgb(15,23,42) on the desktop
       header at 1440, 1100 and 390 in both languages -- which the sibling token's comment below had
       ALREADY recorded as the reference's desktop value while this one kept the old number. It is a
       neutral slate, not a brand colour, so the palette clause does not apply and the shipped
       --kp-slate-900 primitive expresses it exactly (#0f172a = rgb(15,23,42)); nothing new is minted.
       THE BORDER TOKEN IS RETIRED, not renamed: the reference's hairline is a white-alpha glass edge
       (rgba(255,255,255,.7)) which no hex can express, so .rp-header-back declares it inline exactly
       as its .rp-mobile-header-back sibling already declares its own -- and this token had no other
       consumer (grepped across src/ before removal). */
    --kp-rp-header-back-ink: var(--kp-slate-900);   /* .rp-header-back text/icon -- v2 rgb(15,23,42) */
    /* .rp-mobile-header-back icon (parity fix wave P2.4, 2026-08-11). A DIFFERENT value from its
       desktop sibling above, because the reference gives the two controls different inks: measured
       #1c304f on the phone control (app.bundle.css:22804) against rgb(15,23,42) on the desktop one.
       A neutral slate-navy, not a brand colour, so the palette clause does not apply; it lives here
       rather than in the rule because no hex may sit outside this file. */
    --kp-rp-mobile-back-ink: #1c304f;      /* .rp-mobile-header-back icon */
    --kp-portal-nav-hover-bg: #f4f7ff;     /* rail nav hover fill */
    --kp-portal-nav-active-a: #eef3ff;     /* rail active gradient start */
    --kp-portal-nav-active-b: #f9fbff;     /* rail active gradient end */
    --kp-portal-nav-active-ink: var(--kp-slate-900);      /* rail active label + row hover ink — v2 #0f172a */
    --kp-portal-nav-active-bar: var(--kp-postal-navy-600); /* rail active 3px marker — OFFICIAL navy (D1) */
    --kp-portal-section-label: rgba(71, 85, 105, .7);      /* ACCOUNT divider label — slate-600 at 70% */
    /* Sign-out: v2 paints the OFFICIAL alert red at three alphas (rest fill .08, border .4, hover solid).
       Alpha variants are spelled out because a custom property cannot parameterize a color's alpha
       channel — same precedent as the --kp-wash-* tokens above. */
    --kp-portal-logout-border: rgba(200, 16, 46, .4);
    --kp-portal-logout-bg: rgba(200, 16, 46, .08);
    --kp-portal-logout-ink: var(--kp-red-700);   /* text; also the hover fill — OFFICIAL #C8102E */
    --kp-portal-online-dot: var(--kp-green-700); /* user-chip online indicator — OFFICIAL #009A44 */
    --kp-portal-mobile-active: var(--kp-postal-navy-600); /* bottom-nav active item — OFFICIAL navy (D1) */
    --kp-portal-mobile-ink: #6c7687;       /* bottom-nav resting item */
    /* Topbar controls (chip/bell/lang) share ONE hover wash in v2 — a white veil over the #f8fafc body.
       The old per-bell ink/tint trio is retired: the bell's resting color is now the shared muted ink and
       its hover is this wash, exactly like its two siblings. */
    --kp-portal-topbar-hover-bg: rgba(255, 255, 255, .4);
    --kp-portal-title-gold-2: #d9bf8d;     /* rp-title accent gradient end (pairs --kp-stamp-gold-500) */

    /* Fix-wave (rows 135/136, 2026-07-18 re-judgment): mockup-exact near-white surface + cool border
       gray shared by the notification/empty-state family (react-parity.css .notification-empty/
       .notification-dropdown/.notification-page-item -- #fdfefe/#dfe6ef pervasively) and the light-blue
       icon-badge tint (.notification-empty>span -- #edf3ff; the icon glyph color itself is the EXISTING
       --kp-navy-600, not re-added). Portal-scoped new primitives -- --color-bg-surface/--color-border
       stay #fff/#e2e8f0 for Admin (Core Rule 1, shared tokens untouched). */
    --kp-portal-surface-soft: #fdfefe;
    --kp-portal-border-soft: #dfe6ef;
    /* Restyle P4 (2026-08-08) -- the tint was the reference package's flat #edf3ff, which is the
       PRE-REBRAND blue (#115ee8) laid over white; the D1 palette clause (intake ruling, 15 #148)
       forbids carrying a stale package value, so the same role now carries the OFFICIAL primary at the
       tint alpha the package's own later layer uses for exactly this tile -- app.bundle.css:17978,
       `body[data-app-page="notifications"] .notification-empty > span { background: rgba(0,51,160,.05);
       color: var(--color-primary) }`. That later layer is also what CLOSES the open value question the
       .mb-empty block in components.css has carried since 2026-08-02 (navy glyph vs portal blue): the
       reference itself pairs the official navy glyph with an official navy tint, which is what we now
       ship on both halves. Two consumers, both P4-owned: .mb-empty-icon and .svc-success-icon.neutral. */
    --kp-portal-icon-tint-blue: rgb(0 51 160 / .05);
    /* Fix-wave 3 (2026-07-18 live-parity ledger L2031/L2038): the SweetAlert2 dialog card/confirm-
       button-text paper is a DIFFERENT mockup-measured near-white (#fefeff) than --kp-portal-surface-
       soft (#fdfefe, correct as-is for .mb-empty per the same ledger, L2117) -- kept as its own token
       rather than overloading the shared one, so .mb-empty's already-correct value is untouched. */
    --kp-portal-modal-surface: #fefeff;

    /* Layer 1 additions — public/auth backdrop (.ref-grid-bg), portal restyle package P2, 2026-08-08.
       v2 paints the login wash as two coloured radial tints over a three-stop near-white sweep
       (app.bundle.css:25183). D1 forbids copying the package's own tint hexes, so the two BRAND tints
       are re-expressed in official values at the package's exact alphas: the package's #3867cb blue
       becomes the official mid navy #1a4db8 (= --kp-postal-navy-400) and its #efae85 peach becomes the
       official light gold #dfc080 (= --kp-stamp-gold-300, measured as the nearer of the two official
       golds — RGB distance 24.6 vs 64.0 for #cba052). Alphas are spelled out rather than composed from
       the palette tokens because a custom property cannot supply only the rgb part of an rgba() — the
       same reason the --kp-wash-* family above is written this way.
       The three sweep stops are PAPER, not brand: no official-palette entry holds them and no existing
       portal near-white matches (--kp-portal-surface-soft #fdfefe / --kp-portal-modal-surface #fefeff are
       both different values with their own consumers), so they get their own portal-scoped primitives. */
    --kp-portal-auth-wash-blue: rgb(26 77 184 / .30);
    --kp-portal-auth-wash-gold: rgb(223 192 128 / .27);
    --kp-portal-auth-paper-1: #f6f8ff;
    --kp-portal-auth-paper-2: #fbfcff;
    --kp-portal-auth-paper-3: #fffaf7;

    /* Layer 1 additions — dashboard landing chrome (mockup react-parity.css "Dashboard 2 parity" +
       "Dashboard2 mailbox tickets" blocks, B1 dashboard-landing phase 2026-07-18, the dashboard task notes).
       Prominent/recurring colors get an exact new primitive here (mockup-exact, same precedent as the
       portal shell chrome group above); low-visibility one-off badges/borders instead consolidate to the
       closest existing token (documented per occurrence in components.css) rather than growing this list
       for single-use values — Core Rule 13's visual-equivalence carve-out. */
    /* 15 #190e: the existing phone shell gutter, shared with full-bleed dashboard strips. */
    --kp-portal-phone-gutter: 17px;
    /* 15 #191c: share the edge-attached bar height with launcher clearance. */
    --kp-portal-mobile-nav-height: 72px;
    --kp-dc-strip-fade-width: 24px;
    /* 15 #191b: smaller phone assistant; 15 #190d/e keep one inset of air beside the direction row. */
    --kp-portal-assistant-phone-size: 64px;
    --kp-portal-assistant-phone-inset: 6px;
    --kp-dc-phone-assistant-corridor: calc(var(--kp-portal-assistant-phone-size) + 2 * var(--kp-portal-assistant-phone-inset));
    --kp-dc-panel-padding: 12.75px;
    --kp-dc-panel-border-width: 1px;
    /* Dated 2026-11-01 (client item 1.3): the greeting eyebrow token left with the greeting; this line keeps the lines after it. */
    --kp-dc-plan-ink: var(--kp-slate-500);/* .dc-plan resting text (restyle P3: v2 #64748b) */
    /* Restyle P3 (2026-08-08): the resting tab fill is an INK WASH in v2, not the flat #f2f4f7 grey the
       v1 layer painted -- it has to read over the panel's own tint, so it stays an alpha. */
    --kp-dc-tab-bg: rgb(15 23 42 / .03); /* .dc-status-tab resting background */
    --kp-dc-tab-ink: #657084;          /* .dc-status-tab resting text */
    /* --kp-dc-tab-active-ink RETIRED 2026-08-11 (parity fix wave P1.5). It carried ONE navy ink for
       every active status tab; the tabs now take their own status colour from the --portal-ship-* trio
       family, so the token had no consumer left. Its value (#0033a0) survives as --portal-ship-navy. */
    --kp-dc-tab-badge-bg: #e4e8ee;     /* .dc-status-tab span RESTING count-badge background (the ACTIVE tab's badge takes the status tone) */
    --kp-dc-tab-badge-ink: #5b6575;    /* .dc-status-tab span count-badge text */
    /* Restyle P3 D1 mapping (2026-08-08): the panel's accent border and tint were the pre-rebrand blue
       family (#0a47b5 / the #f4f6fa grey it was paired with). v2 paints the OFFICIAL primary and its own
       3% tint of the same colour, so both resolve onto the brand navy. */
    --kp-dc-panel-border: var(--kp-postal-navy-600); /* .dc-ship-panel top accent border */
    --kp-dc-panel-bg: rgb(0 51 160 / .03);           /* .dc-ship-panel background */
    --kp-dc-direction-border: #e6ebf1; /* .dc-direction resting border */
    --kp-dc-direction-ink: #657083;    /* .dc-direction resting text */
    --kp-dc-direction-active-bg: #17223a; /* .dc-direction.active background */
    --kp-dc-view-all-ink: #667389;     /* .dc-view-all text */
    /* Restyle P3 fix round (2026-08-08): the shipment card's frame measures #eceff4 on the rendered
       reference, a step lighter than the shared --color-border (#e2e8f0) the B1 port substituted. Own
       token rather than a near-miss reuse -- the same call fix-wave 3 made for --kp-dc-plan-border.
       The card's HOVER border is a different value (#cbd5e1) and keeps the shared --kp-slate-300. */
    --kp-dc-shipment-border: #eceff4;  /* .dc-shipment resting border */
    /* Fix-wave 3 (2026-07-18 live-parity ledger L770/928): the lead reversed the prior "imperceptible
       2-channel delta, reuse --color-border" call for .dc-plan's border -- dedicated token so the
       shared --color-border stays untouched for everything else that uses it. Restyle P3 (2026-08-08):
       v2 measures the pill's border at the standard #e2e8f0, so the dedicated token now points at the
       shared slate step rather than carrying its own near-miss value. */
    --kp-dc-plan-border: var(--kp-slate-200); /* .dc-plan border */
    /* The dashboard announcements (2026-10-16, 15 #441, #444): neutral greys measured on the rendered reference
       with no token at their exact value, so each gets its own (the shipment-border precedent). The brand
       colours of the same surfaces map onto the official palette instead and need no token here: the row
       megaphone --kp-navy-600 on --kp-navy-600-a06, the details megaphone --kp-stamp-gold-500 on
       --kp-gold-500-a12 (Core Rule 13 palette clause). */
    --kp-dc-announcement-ink: #000;              /* .dc-announcement text: the reference row keeps the button's default ink */
    --kp-dc-announcement-border: #eceef3;        /* .dc-announcement divider */
    --kp-dc-announcement-date: #6e7a8d;          /* .dc-announcement-date */
    --kp-dc-announcement-arrow: rgba(71, 85, 105, .5); /* .dc-announcement-arrow: slate-600 at 50%, the reference's muted arrow */
    --kp-an-kicker-ink: #36445d;                 /* .an-kicker */
    --kp-an-close-ink: #8794a6;                  /* .an-close at rest */
    --kp-an-close-hover-bg: #f3f6fa;             /* .an-close:hover fill */
    --kp-an-rule: #edf1f5;                       /* .an-header and .an-footer dividing rules */
    --kp-an-date-ink: #69778b;                   /* .an-title-row small */
    --kp-an-title-ink: #111b2e;                  /* .an-title-row h2 */
    --kp-an-text-ink: #526177;                   /* .an-text */

    /* ---- Restyle P3 additions (2026-08-08) -- portal mockup v2's dashboard, measured values that the
       system had no home for. ---- */
    /* The hero ticket's spine. THREE stops, official navy ramp: v2 authors
       linear-gradient(160deg, --color-primary-deep, --color-primary, --color-primary-soft), whose own
       :root resolves to exactly our #002680 / #0033a0 / #1a4db8. Distinct from --gradient-brand, which
       pins its middle stop at 45% -- the spine's stops are evenly spaced. */
    --gradient-portal-ticket-spine: linear-gradient(160deg, #002680, #0033a0, #1a4db8);
    /* The side-column card shell (.dc-appointments / .dc-announcements). v2 paints them through its own
       glass card rule at 74% white -- lighter than the shipped --glass-card-bg (82%) and heavier than
       the hero ticket's --glass-bg (62%), so it is its own step rather than a reuse. */
    --kp-portal-card-glass-bg: rgb(255 255 255 / .74);
    --kp-portal-card-glass-shadow: 0 12px 40px -12px rgb(15 23 42 / .12), inset 0 1px 0 rgb(255 255 255 / .7);

    /* ---- Subscription purchase slice, Phase 2 package P1 (2026-08-01) -------------------------------------
       Sources, read directly from the mockup files this package:
         * svc-*  -> postOffice_PublicUser_html css/register-services.css (its own :root maps 1:1 onto the
                     postal-navy / stamp-gold / slate families ALREADY defined above, so only the values with
                     no existing home are added here);
         * plan-* -> postOffice_PublicUser_html css/react-parity.css "Dashboard plan chooser modal" block;
         * payment-history-* -> the same file's "Payment history" block.
       Same policy as the --kp-dc-* group above: an exact new primitive for every value the system has no home
       for, so components.css keeps its no-hex-in-declarations rule. */

    /* The mockup's react layer paints its neutrals from the GRAY ramp, not the slate ramp the admin uses
       (#1f2937 vs #0f172a, #6b7280 vs #64748b, ...). They are visibly different families at the same step, so
       they are a second ramp rather than shades of --kp-slate-*. Consumed by the payment-history family. */
    --kp-gray-050: #f9fafb;
    --kp-gray-100: #f3f4f6;
    --kp-gray-200: #e5e7eb;
    --kp-gray-300: #d1d5db;
    --kp-gray-400: #9ca3af;
    --kp-gray-500: #6b7280;
    --kp-gray-700: #374151;
    --kp-gray-800: #1f2937;

    /* The mockup's bright action blue (react-parity.css .plan-option.selected .plan-check; the midpoint of
       register-services.css's physical icon gradient). DISTINCT from --kp-postal-navy-600 (#0033a0, the brand
       navy): this is the lighter blue the portal uses for a SELECTED control, and the same triplet the
       shipped --kp-navy-600-a05 already carries in alpha form.
       ORPHANED-KEPT since restyle P4 (2026-08-08): its last declaration consumer was
       --gradient-svc-icon-physical, which the D1 palette clause moved onto the official navy ramp (see the
       Layer-2 block below). Nothing declares it now; it stays as this file's byte-exact record of the
       reference's pre-rebrand action blue, cited by three explanatory comments in components.css, on the
       same orphaned-with-a-dated-note footing as --kp-plan-border / --portal-ship-gold-tint (restyle P3).
       It must NOT be consumed by new work -- D1 makes the official navy the intent everywhere. */
    --kp-portal-blue-500: #115ee8;

    /* svc-* service cards / checkout summary (register-services.css). Only the gradient stops lived here --
       every flat color in that stylesheet already has a token above.
       RETIRED in restyle P4 (2026-08-08), D1 palette clause: the six stops this block held were raw
       reference values with no official home -- the virtual icon's #e7ad35 -> #f3c85e, the physical icon's
       #0d4ab8 -> #115ee8 45% -> #3a7af0, and the CTA's #2456b8 -> #2144a0. Every one of the three gradients
       they fed now composes OFFICIAL brand stops instead (Layer-2 block below), so the primitives had no
       consumer left and would only have invited a future author to paint a stale value. The reference's own
       measured shapes are preserved exactly -- same angles, same stop count, same 45% midpoint -- which is
       why the two icon gradients could be expressed as the already-shipped --gradient-stamp/--gradient-brand
       rather than re-minted. The retired values remain readable in the reference package itself
       (docs/reference/subscribersPortal-KuwaitMail/css/register-services.css). */
    /* The two glass fills of the service card. Spelled as alpha primitives (the wash-token precedent above)
       because a custom property cannot parameterize a color's alpha channel: the resting fill's #ebf1ff has
       no flat twin in the system, and the selected fill's #f9fbff is --kp-portal-nav-active-b at a different
       alpha than that token carries. */
    --kp-svc-option-bg: rgba(235, 241, 255, .72);
    --kp-svc-option-selected-bg: rgba(249, 251, 255, .82);

    /* plan-* dashboard plan modal (react-parity.css). The modal carries its own near-white / blue-gray
       palette, deliberately softer than both the admin shell and the dashboard landing family. */
    /* Kept, unreferenced since restyle P3 (2026-08-08): v2's plan sheet has NO border at any width, so
       .plan-sheet stopped consuming this. It stays as the family's border step rather than being deleted
       and re-derived if a bordered plan surface returns. */
    --kp-plan-border: #dce3ed;              /* .plan-sheet border */
    --kp-plan-ink: #172033;                 /* .plan-sheet text */
    --kp-plan-muted: #687588;               /* header sub-line, close button, resting duration button */
    --kp-plan-hover-bg: #f1f4f8;            /* close button hover fill */
    /* Unreferenced since 2026-10-13: the rendered reference shows no grab handle at any width, so no rule paints the
       handle; kept as the family's handle step, as --kp-plan-border above is kept. */
    --kp-plan-handle: #d8dfe8;              /* mobile sheet grab handle */
    /* The sheet's own scrim (2026-10-13): the rendered reference paints its plan scrim at .42 on the --kp-slate-900
       triplet, while --portal-dialog-backdrop stays .44 for the Portal's message dialogs. Alpha spelled out for the
       same reason that token gives. */
    --kp-plan-scrim: rgba(15, 23, 42, .42);
    /* Restyle P3 (2026-08-08): v2's later plan-chooser layer paints the current-plan card and the crown
       tile in its pre-rebrand blue (#115ee8 at .2 / .04, and the flat #115ee8). The D1 palette clause
       forbids copying those, so the same alphas and the same role are carried on the official navy. */
    --kp-plan-current-border: rgb(0 51 160 / .2);   /* .plan-current card */
    --kp-plan-current-bg: rgb(0 51 160 / .04);
    --kp-plan-crown-bg: var(--kp-postal-navy-600);  /* .plan-crown tile */
    --kp-plan-on-navy: #f8fbff;             /* ink ON the navy tiles/buttons */
    /* CONTRAST REBIND (plan P5, docs/plans/2026-08-25-post-wave-followups-plan.md — P3 design-lane
       finding, adjudicated ACCEPTED 2026-08-25): the four metadata-label tokens below sat below the
       4.5:1 WCAG normal-text floor on their #f5f7fb surfaces (current-card / option surface) —
       eyebrow #6c788b 4.17:1, renewal-label #6e7a8c 4.06:1, note #738095 3.73:1,
       duration-label #6d798c 4.11:1. All four rebind by var() reference to the approved muted
       semantic token --color-text-muted (#475569): each now reads 7.07:1 on #f5f7fb.
       Colour-only change — zero geometry edits (size/spacing/weight untouched); consumers are the
       .plan-current-top p / .plan-renewal span / .plan-other > p + .plan-option-price small /
       .plan-duration > span rules in components.css. */
    --kp-plan-eyebrow: var(--color-text-muted);             /* the "current plan" eyebrow */
    --kp-plan-renewal-ink: #657286;         /* .plan-renewal glyph + .plan-price unit */
    --kp-plan-renewal-label: var(--color-text-muted);
    --kp-plan-renewal-value: #1d2839;
    --kp-plan-section-label: #647185;       /* the h4 section labels */
    --kp-plan-feature-ink: #5f6c80;         /* feature bullet text */
    /* PALETTE SWEEP, parity fix wave P2.9b (2026-08-11). The restyle-P3 pass re-expressed FOUR members
       of this block on official brand values (the current-plan card, the crown tile, the selected-option
       ring, the VBX bullet dots) and left five behind; the owner found one of them on the deployed
       footer CTA. All five are corrected together here, each keeping the reference's ROLE and alpha and
       taking an official value (portal palette clause, 15 #148 D1):
         feature tick  #25a966 -> the official green. The reference's own tick asset
                       (assets/icon-check-square-duotone-success.svg) is filled #009a44, which IS the
                       official green -- so this token was the only thing standing between us and the
                       reference's actual value.
         Renew fill    #e7eefb -> the shipped navy-at-8% tint. Measured over white the reference's own
                       #e7eefb is not one navy alpha at all (its channels imply .094/.083/.042), so the
                       nearest honest expression is the system's existing soft-navy tint rather than a
                       new alpha primitive minted to chase a value the clause forbids copying.
         Renew ink     #1152bd -> the official navy.
         term chip     #0e45ae -> the official navy (its shadow follows, in components.css).
         footer CTA    #0d45b3 -> the official navy, which is also what --color-action-primary resolves
                       to, so the sheet's primary button now paints the same brand action colour as
                       every other primary CTA in the product (its shadow follows too).
       All five reference values sit in the pre-rebrand blue family the clause names; the reference
       renders them live (measured on the rendered plan sheet, 2026-08-11: rgb(17,82,189) /
       rgb(231,238,251) / rgb(14,69,174) / rgb(13,69,179), and rgb(17,94,232) on the parts P3 already
       fixed), which is exactly the trap the clause exists for. */
    --kp-plan-feature-check: var(--kp-green-700);   /* feature bullet tick */
    --kp-plan-action-bg: var(--kp-navy-600-a08);    /* the Renew button */
    --kp-plan-action-ink: var(--kp-postal-navy-600);
    --kp-plan-rule: #e5eaf1;                /* .plan-other top rule */
    --kp-plan-note: var(--color-text-muted);                /* .plan-other sub-line + per-option unit */
    --kp-plan-option-border: #e2e7ee;
    /* Restyle P3 (2026-08-08): same D1 mapping as the current-plan card -- v2 rings the selected option
       with its pre-rebrand blue at 55%; the official navy carries the same alpha. */
    --kp-plan-option-selected-border: rgb(0 51 160 / .55);
    --kp-plan-check-border: #9aa6b6;
    --kp-plan-bullet-gold: var(--kp-stamp-gold-500); /* the VBX option's bullet dots — OFFICIAL gold (Restyle P3 D1 mapping, 2026-08-08: v2 paints the pre-rebrand #d4a017 here) */
    --kp-plan-duration-label: var(--color-text-muted);
    --kp-plan-duration-border: #e1e6ed;
    --kp-plan-duration-active-bg: var(--kp-postal-navy-600);
    --kp-plan-footer-bg: #f8faff;
    --kp-plan-footer-btn-bg: var(--kp-postal-navy-600);
    /* The physical option icon's gradient END. Also swept in P2.9b: #164ebd was the last raw member of
       the stale blue family in this block. The reference's own gradient runs #04276f -> #115ee8; the
       official navy ramp's light end (#1a4db8) carries the same role, and pairing it with the deep navy
       this gradient already starts from makes the tile read as the same brand ramp the service cards
       took in restyle P4. */
    --kp-plan-icon-blue-b: var(--kp-postal-navy-400);
}

/* ============================================================
   LAYER 2 — semantic (the redesign touchpoint — recolor here)
   ============================================================ */
:root {
    /* surfaces & text */
    --color-action-primary: var(--kp-navy-600);
    --color-bg-canvas: var(--kp-slate-50);
    --color-bg-surface: var(--kp-white);
    --color-text: var(--kp-slate-900);
    --color-text-muted: var(--kp-slate-600);
    --color-border: var(--kp-slate-200);
    --color-input-border: var(--kp-input-border);
    --color-input-border-hover: var(--kp-input-border-hover);
    --color-accent: var(--kp-gold-500);
    --color-focus-ring: rgba(0, 51, 160, .30);
    /* Danger focus ring — mockup-exact (postOffice_Admin_html css/style.css --focus-ring-danger,
       rgb triplet == --kp-red-600). Full box-shadow value, consumed by .is-invalid:focus in
       components.css (inline-field-validation standard, 2026-07-20). */
    --focus-ring-danger: 0 0 0 3px rgba(200, 16, 46, .30);
    --color-lang-toggle-bg: rgb(255 255 255 / .12);

    /* Layer 2 additions — admin shell control cluster + user-profile dropdown surfaces
       (mockup css/style.css §"Unified topbar controls" + .user-profile-btn/.user-dropdown).
       Backed by the navy-tint hex primitives added in Layer 1. rgba() navy-alpha borders/shadows are
       written inline in components.css (Tasks 3/4), consistent with the .sidebar-overlay precedent. */
    --color-shell-soft: var(--kp-navy-050);         /* #f1f6ff — control hover + dropdown header band */
    --color-shell-soft-strong: var(--kp-navy-100);  /* #e6f0fe — expanded/active + dropdown-item hover */

    /* sticky-column edge lines (owner ruling B5, 2026-07-19) — consumed only by the reusable
       .table-custom--sticky-edges modifier (components.css). strong = header row + sticky-end column;
       soft = sticky-start body column. */
    --color-table-sticky-edge: var(--kp-slate-edge);
    --color-table-sticky-edge-soft: var(--kp-slate-edge-soft);

    /* Data-grid three-state zebra (mockup style.css:8568-8570, byte-exact): even-row wash + hover +
       focus-within navy tints. DISTINCT from --color-bg-canvas (#f8fafc page paper — the old, wrong
       even-row value) and from the shell-soft pair (#f1f6ff/#e6f0fe control tints, which stay on the
       shell controls only). Literals live here (the hex home) per the badge-token precedent. Consumed
       by the admin grids' zebra rules in the admin site.css. */
    --color-table-row-even: #fbfcfe;
    --color-table-row-hover: #f3f7ff;
    --color-table-row-focus: #eef4ff;

    /* Grid header band + borders. CORRECTED 2026-07-23 (lead cross-page census, ledger 15 #96): 7 of the 8
       mockup grid pages paint the LIGHT band — #f8fafc bg / #475569 text (mockup .table-custom thead th,
       style.css:1407-1417 + 4980-4991). ONLY branches.html painted the heavy #f3f6fa/#526176 band; the
       2026-07-19 port mistook that one page for "the mockup's grid" and heavy-styled every grid for four
       days. Since 2026-08-02 these tokens are the band for EVERY admin grid without exception — the
       Branches page-scoped heavy override and its --kp-th-band/--kp-th-text primitives were retired by the
       mockup-v3 restyle wave U1 (owner ruling D6, ledger 15 #137). The v3 reference keeps this same light
       pair, so the values below did not move. Body borders unchanged. */
    --color-table-head-bg: var(--kp-slate-50);
    --color-table-head-text: var(--kp-slate-600);
    --color-table-head-border: var(--kp-slate-edge);
    --color-table-row-border: var(--kp-slate-edge-soft);

    /* clean slate chevron (matches --color-text-muted) for native selects — var() can't live inside a data-uri */
    --select-chevron: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='16' height='16' fill='none' stroke='%23475569' stroke-width='2' stroke-linecap='round' stroke-linejoin='round' viewBox='0 0 24 24'%3E%3Cpath d='m6 9 6 6 6-6'/%3E%3C/svg%3E");

    /* the thumb of a switch that reads off, under focus: --color-action-primary's value, because var() can't live inside a data-uri */
    --switch-thumb-focus: url("data:image/svg+xml,%3csvg xmlns='http://www.w3.org/2000/svg' viewBox='-4 -4 8 8'%3e%3ccircle r='3' fill='%230033a0'/%3e%3c/svg%3e");

    /* status pairs — soft tint fill + dark tone text */
    --status-success-bg: rgba(0, 154, 68, .12);
    --status-success-fg: var(--kp-emerald-900);
    --status-transit-bg: rgba(124, 58, 237, .12);
    --status-transit-fg: var(--kp-violet-900);
    --status-alert-bg: rgba(200, 16, 46, .1);
    --status-alert-fg: var(--kp-red-600);
    --status-pending-bg: rgba(245, 158, 11, .12);
    --status-pending-fg: var(--kp-amber-900);
    --status-draft-bg: rgba(71, 85, 105, .1);
    --status-draft-fg: var(--kp-slate-600);
    --status-scheduled-bg: rgba(0, 51, 160, .12);
    --status-scheduled-fg: var(--kp-navy-700);
    /* The Admin range tab under the pointer (risk row HSH-ADMIN-RANGE-TAB-HOVER, 2026-11-10): the official navy at 6%,
       the strength the rendered admin reference paints its own .range-btn:hover at (rgba(0, 51, 160, .06)). Half the
       scheduled wash above, which the tab wore until this date; the alpha is spelled out per this file's precedent. */
    --color-range-hover-bg: rgba(0, 51, 160, .06);

    /* Layer 2 additions — sidebar logout button surfaces (mockup .btn-logout style.css:533,535). A
       distinct outline: fill at .06 alpha, border at .15 alpha, both derived from the alert-red
       triplet (200,16,46 == --kp-red-600). Kept separate from --status-alert-bg (a single .1 alpha)
       so the button reads as an outlined action, not a filled tint (P4 shell parity item 11). */
    --kp-logout-bg: rgba(200, 16, 46, .06);
    --kp-logout-border: rgba(200, 16, 46, .15);

    /* Layer 2 additions — operational status BADGE tokens (mockup style.css :root lines 83-97,
       "Operational Status Badges"): solid fill + text + 1px hairline border — the consolidated badge
       look. DISTINCT from the translucent --status-*-bg/-fg surface tints above, which stay unchanged
       and keep backing every hover / note / stat-icon / chip / pill. Only the badge CLASSES (components.css
       Task 2) read these. Values byte-exact from the mockup; literals live here (the hex home) per the
       existing --status-*-bg precedent. Border rgba forms carry the mockup's exact alpha. */
    --badge-success-bg: #e6f8f2;  --badge-success-text: #065f46;  --badge-success-border: rgba(4, 120, 87, 0.22);
    --badge-warning-bg: #fef6e7;  --badge-warning-text: #78350f;  --badge-warning-border: rgba(180, 83, 9, 0.24);
    --badge-danger-bg: #fdf2f2;   --badge-danger-text: #9b1c1c;   --badge-danger-border: rgba(185, 28, 28, 0.22);
    --badge-info-bg: #eef4ff;     --badge-info-text: #002680;     --badge-info-border: rgba(0, 51, 160, 0.20);
    --badge-neutral-bg: #f1f5f9;  --badge-neutral-text: #475569;  --badge-neutral-border: #d7dee8;

    /* Layer 2 additions — role-type badge tokens (mockup .role-type-badge.system/.custom, style.css:7300-7309).
       System's fg is an exact match to --kp-violet-600 (mockup fg #7c3aed). Custom is now the mockup's TRUE
       CYAN (owner design-review batch 2026-07-23, ledger 15 #96 F7 — supersedes the earlier "no-new-cyan-hex"
       navy surrogate): bg rgba(14,165,233,.08) == --kp-cyan-500 @ .08 (literal per this file's alpha
       precedent — a custom property cannot parameterize a color's alpha), fg the darker --kp-cyan-600. */
    --status-role-system-bg: rgba(124, 58, 237, .08);
    --status-role-system-fg: var(--kp-violet-600);
    --status-role-custom-bg: rgba(14, 165, 233, .08);
    --status-role-custom-fg: var(--kp-cyan-600);

    /* Layer 2 additions — stat-card icon variants (mockup users.html stat row;
       soft tinted background + colored glyph, per the mockup's actual .stat-icon rule) */
    /* SOLID tile fills + mockup fg set (live-measured 2026-07-19 on branches.html: blue
       #e6f0fe/#0033a0, green #d1fae5/#047857, orange #fef3c7/#cba052, cyan #e8eef5/#1a4db8 — the
       earlier rgba-tint fills painted a visibly different wash; owner-flagged with the counters). */
    --color-stat-icon-blue-bg: var(--kp-navy-100);
    --color-stat-icon-blue-fg: var(--kp-navy-600);
    --color-stat-icon-green-bg: var(--kp-tile-green);
    --color-stat-icon-green-fg: var(--kp-emerald-700);
    --color-stat-icon-orange-bg: var(--kp-tile-orange);
    --color-stat-icon-orange-fg: var(--kp-gold-500);
    --color-stat-icon-cyan-bg: var(--kp-tile-cyan);
    --color-stat-icon-cyan-fg: var(--kp-navy-500);

    /* Layer 2 addition — stat-icon purple variant (mockup :has(.stat-icon.purple), style.css:978-979,
       Task 2); rgba derived from --kp-violet-600 (#7c3aed = rgb(124,58,237)) at the same .12 alpha as its
       blue/green/orange/cyan siblings above — the exact mockup purple, no new hex. */
    --color-stat-icon-purple-bg: var(--kp-tile-purple); /* SOLID per the 2026-07-19 live-measured tile fix */
    --color-stat-icon-purple-fg: var(--kp-violet-600);

    /* P4 D1 — stat-icon soft-navy variant (mockup DASHBOARD V2 override, style.css:5885-5889: the
       dashboard's per-card icon coloring is unified to a soft navy tint — rgba(0,51,160,.10) bg +
       postal-navy fg — with coral reserved for exception KPIs). .10 alpha is the mockup's exact
       DASHBOARD-V2 value (a hair softer than the .12 blue variant); fg is --kp-navy-600 (#0033a0 =
       the mockup's --postal-navy). Consumed by the dashboard KPI cards only; the colored variants above
       stay for other pages' cards (e.g. AdminUsers' tier card). */
    --color-stat-icon-navy-bg: rgba(0, 51, 160, .1);
    --color-stat-icon-navy-fg: var(--kp-navy-600);

    /* Exception-card coral icon tint (mockup style.css:5892-5895, rgba(255,107,74,.12) — the coral
       family's only alpha surface; wired 2026-07-23 with the dashboard's attention cards). */
    --color-stat-icon-coral-bg: rgba(255, 107, 74, .12);
    --color-stat-icon-coral-fg: var(--kp-coral-500);

    /* shadows */
    --shadow-card: 0 1px 3px rgba(0, 0, 0, .04), 0 4px 12px rgba(0, 0, 0, .06);
    --shadow-card-hover: 0 4px 16px rgba(0, 51, 160, .12);
    /* The Admin form field at rest (risk row ADMIN-FIELD-SHADOW, 2026-11-10): the admin reference's --shadow-xs under
       every text input and select (its UNIFIED FORM CONTROLS rule). Read by the Admin stylesheet only. */
    --shadow-field: 0 1px 2px rgba(0, 0, 0, .04);
    /* The chosen receiver card's soft lift (2026-11-15): the admin reference's chosen option, 1px down and 2px of blur in
       the ink at 6% (its .receiver-option:has(input:checked)). Read by the hand-over choice list only. */
    --shadow-choice-chosen: 0 1px 2px rgba(15, 23, 42, .06);
    --shadow-float: 0 8px 32px rgba(0, 0, 0, .12);
    --shadow-xl: 0 20px 25px -5px rgba(0, 0, 0, .1), 0 8px 10px -6px rgba(0, 0, 0, .04);  /* mockup --shadow-xl (style.css:135): the notification panel */
    --shadow-stamp: 0 6px 24px rgba(203, 160, 82, .22);
    --shadow-glow: 0 0 0 4px rgba(0, 51, 160, .12), 0 12px 32px -8px rgba(0, 51, 160, .45);
    --shadow-nav-active-glow: 0 0 8px rgba(0, 51, 160, .6);
    --shadow-cell-icon: 0 1px 2px rgba(15, 23, 42, .08), 0 4px 12px rgba(0, 51, 160, .14);
    --shadow-avatar: 0 2px 8px rgb(0 51 160 / .25);

    /* Docked-control shadow (owner ruling 2026-09-02, the grid's floating sideways scrollbar). This is the
       ONLY token that casts UPWARD: a positive vertical offset under a control pinned to the bottom of the
       window falls into the browser frame and is seen by nobody, and the one token above with no vertical
       offset at all (--shadow-nav-active-glow) is a glow rather than an elevation. Same soft ambient blur
       as --shadow-card's second layer, lifted upward, so a docked bar reads as sitting above the page it
       scrolls. */
    --shadow-dock: 0 -4px 12px rgba(0, 0, 0, .06);

    /* Layer 2 addition — auth submit button hover shadow (mockup login.html
       .auth-submit:hover, style.css:9347-9350); navy-family rgb(0 51 160) is the same
       literal already established by --shadow-avatar above at the same .25 alpha —
       reproduced verbatim here at the mockup's exact offset/blur, not re-derived. */
    --shadow-auth-submit-hover: 0 6px 18px rgb(0 51 160 / .25);

    /* brand gradient */
    --gradient-brand: linear-gradient(160deg, #002680 0%, #0033a0 45%, #1a4db8 100%);

    /* P4 D6 — stamp-gold gradient (mockup .quick-action--cta .quick-action-icon, style.css:5982-5984:
       linear-gradient(135deg, #CBA052 0%, #DFC080 100%)). #cba052/#dfc080 already exist as
       --kp-gold-500/--kp-gold-300; reproduced here in the gradient's hex home (same convention as
       --gradient-brand above). Consumed by the dashboard's first quick-action CTA tile. Note for a
       future editor: since restyle P4 (2026-08-08) --gradient-svc-icon-virtual carries the SAME two
       stops at the same 135deg (the portal reference draws its virtual-service icon that way, D1-mapped
       onto official gold). It is spelled out separately on purpose, so a change here does NOT move it --
       but if the intent is a palette-wide gold change, both need editing. */
    --gradient-stamp: linear-gradient(135deg, #cba052 0%, #dfc080 100%);

    /* Layer 2 additions — page background-wash (mockup style.css body::before/::after, Task 1) */
    --gradient-wash-a: radial-gradient(circle at 30% 30%, var(--kp-wash-a-1) 0%, var(--kp-wash-a-2) 40%, var(--kp-wash-a-3) 75%, transparent 100%);
    --gradient-wash-b: radial-gradient(circle at 70% 70%, var(--kp-wash-b-1) 0%, var(--kp-wash-b-2) 40%, var(--kp-wash-b-3) 75%, transparent 100%);

    /* glass surfaces */
    --glass-bg: rgba(255, 255, 255, .62);
    --glass-border: rgba(255, 255, 255, .55);
    --glass-blur: blur(22px) saturate(140%);
    --glass-shadow: 0 12px 40px -12px rgba(15, 23, 42, .18), inset 0 1px 0 rgba(255, 255, 255, .85);
    --glass-strong-bg: rgba(255, 255, 255, .78);
    --glass-strong-blur: blur(28px) saturate(160%);
    --glass-card-bg: rgba(255, 255, 255, .82);
    --glass-card-border: 1px solid rgba(226, 232, 240, .9);
    --glass-card-blur: blur(14px) saturate(140%);
    --glass-search-blur: blur(12px);

    /* Dated 2026-11-10 (risk row HAC-LAUNCHER-DS-LEFTOVERS): the launcher's glass tile, search box, footer hairline
       and keyboard-hint tokens stood here (fifteen, every one named launchpad). The launcher page left with owner
       ruling 15 #904(a); no stylesheet, view or script of the three apps read any of them, so they are removed. */

    /* Layer 2 additions — subscriber-portal semantics (mockup CTA/brand layer, theme-parity.css;
       intake 13 D17). ADMIN TOKENS UNTOUCHED — --color-action-primary stays var(--kp-navy-600);
       portal views/components will bind to the --*-portal-* names below. Literal rgba() stops carry
       the mockup's exact alpha (custom properties can't parameterize a color's alpha — same
       precedent as the wash tokens above). */
    --color-portal-action: var(--kp-postal-navy-600);
    --color-portal-action-hover: var(--kp-postal-navy-700);
    --color-portal-accent: var(--kp-stamp-gold-500);
    --color-portal-focus-ring: var(--kp-postal-navy-600);

    /* portal shadows — theme-parity.css verbatim (.rp-card family; .ref-primary; .ref-login
       .ref-primary; .ap-card/.an-card) */
    /* Kept, unreferenced since restyle P3 (2026-08-08): its one consumer was the dashboard's two side
       cards, which moved onto the reference's glass treatment (--kp-portal-card-glass-shadow). It stays
       as the portal's flat-card shadow step for the surfaces packages P4/P5 still measure. */
    --shadow-portal-card: 0 1px 3px rgba(15, 23, 42, .04), 0 4px 12px rgba(15, 23, 42, .05);
    --shadow-portal-cta: 0 8px 20px rgba(0, 51, 160, .18);
    --shadow-portal-cta-raised: 0 8px 0 rgba(0, 51, 160, .12), 0 16px 28px -14px rgba(0, 51, 160, .65);
    /* register .user-submit ring+drop shadow — live-measured on the running mockup 2026-07-19 */
    --shadow-portal-cta-register: 0 0 0 4px rgba(0, 51, 160, .12), 0 12px 32px -8px rgba(0, 51, 160, .45);
    --shadow-portal-modal: 0 28px 70px rgba(15, 23, 42, .26);
    --shadow-portal-toast: 0 12px 32px rgba(40, 48, 73, .08);

    /* Layer 2 additions -- portal feedback layer semantics (fix wave 2, ruling B2). Literal rgba()
       stops carry the mockup's exact alpha (same precedent as the wash tokens above --
       --portal-dialog-backdrop's rgb triplet equals --kp-slate-900's, alpha spelled out because
       custom properties can't parameterize alpha without color-mix()/relative-color syntax). */
    --status-portal-alert-bg: #fff1f1;
    --status-portal-alert-fg: var(--kp-portal-danger-500);
    /* Portal danger focus ring (inline-field-validation standard, 2026-07-20): the negative mirror
       of the shipped .ref-field .is-valid ring — portal danger family rgb triplet at the green ring's
       .16 alpha; literal rgba() per this block's alpha precedent.
       DERIVED VALUE -- it must be re-spelled whenever --kp-portal-danger-500 moves, because a custom
       property cannot supply only the rgb part of an rgba(). Moved from rgb(201,84,91) to the official
       rgb(200,16,46) in the same change that re-pointed that token (D6, 2026-08-08). */
    --focus-ring-portal-danger: 0 0 0 3px rgba(200, 16, 46, .16);
    --portal-dialog-backdrop: rgba(15, 23, 42, .44);

    /* portal shipment 4-tone set — react-parity.css --shipment-tab-color/-tint/-ring +
       --shipment-panel-color families, verbatim alphas */
    --portal-ship-navy: var(--kp-postal-navy-600);
    --portal-ship-navy-tint: rgba(0, 51, 160, .10);
    --portal-ship-navy-ring: rgba(0, 51, 160, .38);
    --portal-ship-green: var(--kp-green-700);
    --portal-ship-green-tint: rgba(0, 154, 68, .10);
    --portal-ship-green-ring: rgba(0, 154, 68, .36);
    --portal-ship-violet: var(--kp-violet-600);
    --portal-ship-violet-tint: rgba(124, 58, 237, .10);
    --portal-ship-violet-ring: rgba(124, 58, 237, .38);
    --portal-ship-gold: var(--kp-stamp-gold-500);
    --portal-ship-gold-tint: rgba(203, 160, 82, .13);
    --portal-ship-gold-ring: rgba(203, 160, 82, .42);
    /* fix wave 2026-07-18: .ref-lang hover border, same 203/160/82 gold as the
       ring above at the mockup's own .user-language button:hover alpha (user-info.css:106,
       reused for the shared .ref-lang pill component per ledger row 49). */
    --portal-lang-hover-border: rgba(203, 160, 82, .7);

    /* Layer 2 additions — portal shell chrome semantics (shell phase 2026-07-17; RE-MEASURED against
       portal mockup v2 in restyle package P1, 2026-08-08). Literal rgba() stops carry the package's
       exact alphas (#ffffffa5=.647, #6e83a733=.2 — wash-token precedent).
       WHY THE -rtl GRADIENT TWINS ARE GONE (P1): v2's own mechanism mirrors the WHOLE rail with
       [dir=rtl] .rp-aside{transform:scaleX(-1)} and counter-flips its direct children, so the
       authored gradients stay 90deg in BOTH directions (measured: computed background-image is the
       same string in ar and en) and the rail's painted fade + art mirror for free. components.css
       carries that flip pair now, so a 270deg twin would double-flip. */
    --portal-rail-bg: linear-gradient(90deg, var(--kp-white) 0%, var(--kp-white) 84%, rgba(255, 255, 255, .647) 100%);
    --portal-nav-active-bg: linear-gradient(90deg, var(--kp-portal-nav-active-a) 0%, var(--kp-portal-nav-active-b) 100%);
    --portal-title-accent: linear-gradient(var(--kp-stamp-gold-500), var(--kp-portal-title-gold-2));
    --portal-schedule-title-mark: linear-gradient(var(--kp-postal-navy-600), var(--kp-stamp-gold-500)); /* 2026-09-06: standalone Schedule title mark. */
    /* P1: the v2 bottom nav is a FLOATING glass PILL, not a full-width bar — .88 paper, 18px blur,
       a white hairline (not a slate border) and its own ambient shadow (app.bundle.css:22823). */
    --portal-mobile-nav-bg: rgba(255, 255, 255, .88);
    --portal-mobile-nav-blur: blur(18px);
    --portal-mobile-nav-border: rgba(255, 255, 255, .7);
    --shadow-portal-mobile-nav: 0 12px 31px rgba(15, 23, 42, .15);
    --shadow-portal-nav-icon: 0 3px 3px rgba(110, 131, 167, .2);
    /* P1: the avatar tile is a two-stop OFFICIAL primary gradient (D1 — the package's own
       --color-primary/-deep ARE #0033A0/#002680) under a neutral ambient shadow pair; the old
       single navy-tinted 0 4px 8px shadow is retired. The online dot's white ring is a box-shadow
       in v2, not a border, so the dot's own 8.5px box is the measured size. */
    --portal-user-avatar-bg: linear-gradient(to right bottom, var(--kp-postal-navy-600), var(--kp-postal-navy-700));
    --shadow-portal-user-chip: 0 1px 3px rgba(0, 0, 0, .04), 0 4px 12px rgba(0, 0, 0, .06);
    --shadow-portal-online-ring: 0 0 0 2px var(--kp-white);

    /* Layer 2 additions -- subscription purchase slice, Phase 2 package P1 (2026-08-01). Gradients live in
       the hex home like --gradient-brand/--gradient-stamp above; the plan modal's GOLD option icon is the
       already-shipped --gradient-stamp (135deg #cba052 -> #dfc080, byte-identical to the mockup's own), so
       no gold twin is minted here.
       RE-EXPRESSED in restyle P4 (2026-08-08) under the D1 palette clause. The reference's register-services
       layer is byte-identical between portal mockup v1 and v2 (diffed file-to-file this package), so its
       GEOMETRY needed nothing -- but its three gradients paint pre-rebrand values the clause forbids
       copying. Each keeps the reference's measured SHAPE -- same angle, same stop count, same midpoint --
       and takes official stops:
         * virtual icon  135deg, 2 stops -> the official gold pair #cba052 -> #dfc080, which makes it
                         currently byte-equal to --gradient-stamp;
         * physical icon 160deg, 3 stops with the middle pinned at 45% -> the official navy ramp
                         #002680 0% / #0033a0 45% / #1a4db8 100%, currently byte-equal to --gradient-brand;
         * CTA           100deg, 2 stops -- the reference runs a light navy into a deeper one (#2456b8 ->
                         #2144a0), whose nearest official pair by channel distance is #1a4db8 -> #0033a0.
       All three are SPELLED OUT from the ramp tokens rather than aliased to --gradient-stamp /
       --gradient-brand, following this block's own --gradient-svc-duration-active convention: those two
       are shared brand tokens with admin consumers, and a future brand tweak must not silently move a
       subscription control that only happens to match today. */
    --gradient-svc-icon-virtual: linear-gradient(135deg, var(--kp-stamp-gold-500), var(--kp-stamp-gold-300));
    --gradient-svc-icon-physical: linear-gradient(160deg, var(--kp-postal-navy-700) 0%, var(--kp-postal-navy-600) 45%, var(--kp-postal-navy-400) 100%);
    --gradient-svc-cta: linear-gradient(100deg, var(--kp-postal-navy-400), var(--kp-postal-navy-600));
    --gradient-svc-duration-active: linear-gradient(145deg, var(--kp-postal-navy-600), var(--kp-postal-navy-700));
    --gradient-plan-icon-blue: linear-gradient(145deg, var(--kp-postal-navy-700), var(--kp-plan-icon-blue-b));
}

/* ---- font semantics + culture switch (07 §3 — one selector flips the type system) ---- */
:root{ --font-display:'Plus Jakarta Sans',sans-serif; --font-body:'Inter',sans-serif; --font-mono:'JetBrains Mono',monospace;
       --leading-body:1.5; --leading-heading:1.25; --tracking-display:-.01em;
       /* Deliberately NOT culture-switched: the ONE control that always renders the OTHER language's
          word (the portal's language toggle shows عربي in English and English in Arabic) needs both
          families reachable in a single stack, or the Arabic label falls back to a system font in EN.
          Byte-equal to the v2 bundle's own .lang-label stack (app.bundle.css:1031).
          (Corrected 2026-10-09: one more place takes this stack -- the Arabic fields of the English company
          pages, whose rule in components.css writes the same stack out rather than naming this token, so the
          Latin of a mixed value keeps Inter and the Arabic takes Alexandria; a governance arm keeps the two
          equal. And the company pages' header draws a second control showing the other language's word; on the
          English page its Arabic word takes Alexandria through its own lang attribute, not through this stack.) */
       --font-portal-bilingual:'Inter','Plus Jakarta Sans','Alexandria',sans-serif; }
html[lang="ar"]{ --font-display:'Alexandria',sans-serif; --font-body:'Alexandria',sans-serif;
       --leading-body:1.6; --leading-heading:1.35; --tracking-display:0; }
/* THE ARABIC FACE IS KEYED ON THE ELEMENT'S OWN LANGUAGE, NOT ONLY THE PAGE'S. The rule above switches the
   type system when the DOCUMENT is Arabic. An element that declares Arabic inside an English page -- the
   Arabic half of a bilingual form, a preview of an Arabic message -- was left in the Latin face, because a
   form control takes the family it INHERITS and inheritance carries the computed family, not the token
   behind it: re-declaring --font-body on the field alone changes nothing. So the family is set here, on the
   language the element itself declares, and every present and future Arabic-content control gets the Arabic
   face wherever it sits. The tokens travel with it so a descendant reaching for the body or display family
   gets the Arabic one too, and the display tracking is zeroed because the negative Latin tracking pulls
   Arabic letterforms apart.
   LINE HEIGHT IS DELIBERATELY NOT SET HERE. The admin supersedes the culture-switched body leading with one
   literal ratio for both languages (mockup v3 ruling 15 #137 adjudication 7, 2026-08-02,
   src/KwtPost.Admin/wwwroot/css/site.css); a leading declaration on this selector would outrank that body
   rule and give Arabic-content fields an optical leading the ruling removed. */
[lang="ar"]:not(html){ --font-display:'Alexandria',sans-serif; --font-body:'Alexandria',sans-serif;
       --tracking-display:0; font-family:var(--font-body); }

/* ============================================================
   Dark theme — reserved stub. Do NOT design one now (07 §1).
   ============================================================ */
[data-theme="dark"] {
    /* intentionally empty — dark palette overrides land here later */
}

/* ============================================================
   High-contrast preference — tighten hairline borders (mockup style.css:10479).
   Hex lives here because tokens.css is the only hex home.
   ============================================================ */
@media (prefers-contrast: more) {
    :root {
        --color-border: #8290a3;
    }
}
/* ---- the portal header (owner rulings 15 #1031 to #1049, 2026-11-05). Only what its block in the Portal's site.css reads.
   The tints are read off the owner's own picture, so they stand outside the official palette on his word. */
:root {
    --kp-portal-page-wash-1: #dce7fa;
    --kp-portal-page-wash-2: #e9eefa;
    --kp-portal-page-wash-3: #edf0f9;
    --kp-portal-sheet-1: #c6d7f5;
    --kp-portal-sheet-2: #e3ecfb;
    --kp-portal-sheet-3: #e9f0fb;
    --kp-portal-ship-panel-bg: #e6ecfc;
    --kp-navy-500-a95: rgb(26 77 184 / .95);
    --kp-portal-header-paint: radial-gradient(70% 150% at 62% 0, var(--kp-navy-500-a95), transparent 70%), linear-gradient(100deg, var(--kp-navy-700), var(--kp-navy-600) 55%, var(--kp-navy-700));
    --kp-portal-header-h: 153px;
    --kp-portal-header-overlap: 22px;
}
@media (max-width: 720px) {
    :root {
        --kp-portal-header-h: 98px;
        --kp-portal-header-overlap: 18px;
    }
}
