/* =============================================================================
   Mythic Canonical Shell — AGENCY THEME LAYER
   =============================================================================
   Loaded AFTER site.css. Redefines the shared theme tokens site.css already
   consumes via var(...) — so a single palette swap here cascades through
   every rule without duplicating a stylesheet.

   Master-design contract:

       assets/css/site.css     ← MASTER, shared across every Mythic agency site
                                 (consumes theme tokens via var(--brand-*)).
       assets/css/theme.css    ← PER-AGENCY, this file.
                                 Redefines the brand tokens with THIS agency's
                                 palette. That is the ONLY place per-agency
                                 color lives.

   SHELL DEFAULTS (this file, unmodified) intentionally mirror the current
   ARS neutral appearance so a freshly-cloned site is visually stable before
   agency customization. To brand a cloned agency, edit ONLY the values in
   Section 1 below — every consumer downstream picks the new palette up
   through the var() remaps in Section 2. Never edit site.css to change
   agency colors.

   Prestige is a real-world example of this pattern (see
   Prestige Planning/00_SITE/assets/css/theme.css) — the shell mirrors
   that architecture with neutral (non-agency) defaults.
   ============================================================================= */


/* ─── 1. Semantic brand tokens (edit ONLY THIS block to rebrand) ─────────
   These are the seven canonical Mythic brand slots. Every agency theme
   fills them with its own palette. Shell defaults below are ARS neutrals
   so the shell renders correctly out of the box. Accessibility check any
   changes: white text on primary/secondary should hit WCAG AA at minimum.
   ------------------------------------------------------------------------ */
/* ─── MYTHIC ENTERPRISES BRAND PALETTE — set 2026-09-15 ──────────────────
   BEFORE THIS DATE THIS FILE STILL CARRIED THE UNBRANDED SHELL DEFAULTS
   (the ARS neutrals: navy #0f2645, blue #1e6c99, gold #c9a35c). Because
   site.css consumes --blue / --navy / --gold via var(), that un-swapped
   shell palette was leaking a foreign ARS blue into live Mythic UI —
   the "Why Mythic" proof labels, every "View Agency ->" link, and every
   pill-button hover state rendered #1e6c99 on a site whose actual brand
   is black + warm stone + cream. That is the contamination CLAUDE.md
   warns about ("do not introduce a new brand/accent color for a heading
   unless the surrounding site already uses that treatment").

   Mythic's real identity is already established by its own assets: a
   black wordmark, a warm stone/tan action color, a cream editorial
   ground and a near-black footer. The tokens below name that palette so
   it cascades correctly instead of being hard-coded per rule.

   Contrast, checked not assumed:
     #16161a on #ffffff ....... 17.4:1  AAA
     #ffffff on #16161a ....... 17.4:1  AAA
     #1e2028 on #ccb7a3 ........ 8.5:1  AAA   (tan pill, ink label)
     #ffffff on #8a6a4f ........ 4.9:1  AA    (stone links/accents)
   ------------------------------------------------------------------------ */
:root {
    --brand-primary:   #16161a;   /* near-black: the wordmark, primary CTA, dark surfaces */
    --brand-secondary: #8a6a4f;   /* deep stone: links + accents. Replaces the ARS blue.  */
    --brand-accent:    #b08d6a;   /* warm tan: eyebrows, numerals, small highlights       */
    --brand-light:     #f5f1e8;   /* cream editorial ground (unchanged)                   */
    --brand-neutral:   #e4dfd4;   /* borders / separators / muted UI                      */
    --brand-charcoal:  #1e2028;   /* body text / neutral dark UI (unchanged)              */
    --brand-white:     #ffffff;

    /* One-step siblings for hover / raised states site.css carries as -2. */
    --brand-primary-2:   #2a2a30;
    --brand-secondary-2: #6f5340;

    /* Darker sibling of primary for inset / recessed surfaces. */
    --brand-primary-dark: #0b0b0d;

    /* The established Mythic action tan. Named here so the button layer
       stops hard-coding it and every consumer moves together. */
    --mythic-tan:      #ccb7a3;
    --mythic-tan-deep: #b9a189;   /* hover sibling of the action tan */
}


/* ─── 2. Re-bind site.css's legacy token names to brand tokens ───────────
   site.css consumes --navy, --blue, --gold, --cream, --ink, etc. via
   var(...). Redefining those tokens here (loaded AFTER site.css) redirects
   every consumer to whatever Section 1 declares — no site.css edit needed.
   ------------------------------------------------------------------------ */
:root {
    /* Dark / primary surfaces + strong UI emphasis */
    --navy-deep:  var(--brand-primary-dark);
    --navy:       var(--brand-primary);
    --navy-2:     var(--brand-primary-2);
    --ink:        var(--brand-charcoal);
    --ink-2:      var(--brand-charcoal);
    --charcoal:   var(--brand-charcoal);
    --charcoal-2: var(--brand-charcoal);

    /* Secondary brand color */
    --blue:   var(--brand-secondary);
    --blue-2: var(--brand-secondary-2);

    /* Decorative accent (site.css used --gold for eyebrows + small labels) */
    --gold: var(--brand-accent);

    /* Backgrounds + panels */
    --cream:      var(--brand-light);
    --off-white:  var(--brand-light);
    --line:       var(--brand-neutral);
    --panel-warm: var(--brand-neutral);
    --panel-blue: var(--brand-primary);

    /* Text + supporting greys (kept generic; agencies rarely override these) */
    --text:       var(--brand-charcoal);
    --text-2:     #4a5468;
    /* 2026-09-15 contrast pass: was #7a8595, which measured 3.74:1 on white
       (WCAG AA needs 4.5:1). Darkened 11% to #6d7685 -> 4.58:1. Changing the
       TOKEN rather than the call sites is the narrowest fix available here:
       every one of this token's uses is a `color:` declaration - it is never a
       background, border or rule - and three of them are inline styles on the
       legal pages that no stylesheet could reach without editing PHP. */
    --text-muted: #6d7685;
    --slate:      #3a4657;
    --slate-2:    #4a5768;
}


/* ─── 3. Generic footer token layer ──────────────────────────────────────
   Shell defaults match ARS's current footer treatment (dark neutral outer
   + slightly-lifted inset panel). Agencies with two-tone brand footers
   (e.g. Prestige Navy + darker Navy) redefine these tokens here — they
   do NOT need matching-specificity overrides on .cta-footer / .footer-*
   because site.css already consumes these tokens.
   ------------------------------------------------------------------------ */
:root {
    --footer-bg:        #1a1a1a;                     /* outer field around footer + CTA   */
    --footer-panel-bg:  #262a30;                     /* rounded inset navigation panel     */
    --footer-bottom-bg: var(--footer-bg);            /* legal / disclaimer block (inherits)*/
    --footer-border:    rgba(255, 255, 255, 0.06);   /* subtle edge on inset panels        */
}


/* ─── 4. Agency-specific overrides (rare — prefer editing Section 1) ─────
   Reserved for cases where the shell's token layer cannot express an
   agency-specific rule (e.g. Prestige's two-tone navy footer, which needs
   matching-specificity !important overrides because some site.css rules
   hard-code hex + !important). Leave EMPTY in the canonical shell.
   ------------------------------------------------------------------------ */