/* ============================================================
   Mooney Vision Solutions - brand tokens
   Phase 0. Variable names match the Whitecotton/Carolina contract
   so the shared component CSS drops in unmodified.

   Every colour below was sampled from Shari's supplied logo or
   derived from it. Contrast ratios are measured, not estimated;
   the figures in comments are the numbers the build asserts.
   ============================================================ */

:root {
  /* ---- Core navy, from the logo wordmark and lower arc -------
     Sampled #081641 / #101B48. Settled on #0B1B47 as the single
     brand navy: 16.6:1 on white, 15.5:1 on --warm-white. */
  --navy: #0B1B47;
  --navy-mid: #1D4173;   /* upper-arc mid facet */
  --steel: #205886;      /* lightest facet in the logo arc */

  /* ---- Accent -----------------------------------------------
     RECOMMENDATION, open for Shari's sign-off. The logo carries
     no third colour, so an accent has to be introduced. Ryan owns
     antique gold (#C69A4E) and Jim owns Carolina blue (#4B9CD3);
     picking either again would make the three sites read as one
     template. This muted teal-green sits harmoniously against the
     navy, is distinct from both, and reads clean without being
     cold - which suits Shari's warmer tone.

     --accent is the brand value. It is 4.9:1 on white, so it does
     pass AA for body text, but it is used for rules, borders and
     large graphics; --accent-ink exists for small text on light. */
  --accent: #2E7D6E;
  --accent-ink: #245F54;      /* 6.6:1 on white - small text on LIGHT only */
  --accent-on-navy: #6FC0AF;  /* 7.6:1 on navy - never use --accent-ink here */
  --accent-light: #5FB3A3;    /* 6.7:1 on navy - eyebrows, section labels */
  --accent-glow: rgba(46, 125, 110, .12);

  /* ---- Neutrals ---------------------------------------------
     Slightly cooler than Whitecotton's warm-white, to sit with a
     cool navy and a teal accent rather than a warm gold. */
  --warm-white: #F8F7F5;
  --cream: #EFEEEB;
  --g1: #F5F6F7;
  --g2: #E7E9EC;
  /* Phase 5.1. --g3 was referenced by the form-field border rule and declared
     nowhere, so every input on /contact fell back to the CSS-wide initial
     border-color - currentColor - and drew its border in the field's own text
     colour by accident. The ramp genuinely had a hole here: --g2 is a fill and
     --g4 is a small-text colour, with no border value between them. 3.7:1 on
     white, 3.5:1 on --warm-white and 3.2:1 on --cream, so it clears the 3:1
     WCAG 1.4.11 asks of a control boundary on every background the form sits
     on. */
  --g3: #7E8593;   /* control borders; non-text contrast only, never text */
  --g4: #5C6270;   /* small text on LIGHT; see --on-navy for dark */
  --g5: #575D6B;
  --g6: #4E5462;
  --g7: #474D5C;
  --g8: #374151;
  --td: #16192B;
  --on-navy: #B4BBC8;  /* 8.0:1 on --navy - body text on dark sections */

  /* ---- Type -------------------------------------------------
     Newsreader for display, DM Sans for everything else. Phase 4
     moved off Playfair Display, which was byte-identical to both
     sibling sites and was being asked to work down to 17px. The
     display face renders at weight 600 and nowhere else - if that
     ever changes, the instanced font in site/fonts has no other
     weight to give and the browser will synthesise one. */
  --font-display: 'Newsreader', Georgia, serif;
  --font-body: 'DM Sans', -apple-system, BlinkMacSystemFont, 'Segoe UI', sans-serif;
}