/* The app's `honey` palette, shared by every marketing page (KAN-208). It used
   to be hand-copied twice -- once into index.html's <style>, once into
   pricing.css -- and nothing noticed when the two drifted apart or when the app
   moved on. It is still a copy, because the marketing site is raw static files
   on S3 with no build step to generate one, so the copy is pinned instead:
   infra/tests/test_marketing_theme_tokens.py fails if any value below stops
   matching frontend/src/index.css's honey block. Laid out to mirror that block
   line for line so the two can be read side by side.

   Dark mode is the OS preference here, not the app's `.dark` class -- these
   pages have no theme switcher. Only the values are shared, not the mechanism. */
:root {
  --c-bg: 250 247 238; --c-surface: 255 255 255; --c-surface-2: 237 234 223;
  --c-ink: 51 50 42; --c-muted: 111 109 96; --c-line: 227 224 210;
  --c-primary: 92 127 94; --c-primary-ink: 255 255 255;
  --c-accent-food: 158 107 27;
}
@media (prefers-color-scheme: dark) {
  :root {
    --c-bg: 33 31 26; --c-surface: 43 41 34; --c-surface-2: 63 60 48;
    --c-ink: 237 235 224; --c-muted: 169 166 149; --c-line: 74 71 58;
    --c-primary: 143 175 145; --c-primary-ink: 33 31 26;
    --c-accent-food: 224 169 78;
  }
}

/* ---- Marketing-only names. The drift test compares by token name, so nothing
        below is pinned to the app -- which is what lets these pages grow their
        own tokens. ---- */
:root {
  /* The pages have always called this `--c-accent`; the app's name for the same
     colour is `--c-accent-food`, and the name is what the drift test matches
     on. Aliasing keeps the honey value in exactly one place. */
  --c-accent: var(--c-accent-food);
  /* There is no --c-card any more (KAN-210): the cards sit on the shared
     --c-surface above. The old warm off-white (255 253 247 light / 41 39 33
     dark) was within a hair of the app's surface (255 255 255 / 43 41 34),
     and only one of the near-twins could survive; the shared, app-pinned one
     did. Pure white also does the card's job better, not worse: it is further
     from the cream --c-bg than the off-white was (1.07:1 vs 1.05:1 relative
     luminance), so cards read as more raised, and every KAN-209 text ratio
     improves on it in light mode (--c-ink-honey 4.97 -> 5.06:1) while dark
     mode's all stay clear of AA (worst pair: --c-muted at 5.94:1). */
  /* Text-safe accents (KAN-209). --c-primary and --c-accent are tuned for
     fills; as body-size text on the light --c-bg they measure 4.21:1 and
     4.29:1, both under WCAG AA's 4.5:1. The ink-* pair is the same two hues
     darkened until they read. Named ink-* ("this colour is an ink") as the
     inverse of the established *-ink suffix ("the ink to put ON that fill");
     KAN-211 mirrors the pair in the app's Tailwind theme under the same names.
     Measured on the light palette: ink-sage on bg 6.30:1, on surface 6.75:1;
     ink-honey on bg 4.72:1, on surface 5.06:1, hue 37 -- the same hue as
     --c-accent, so links still read as honey. --c-ink-sage is the value the
     pages have always known as --c-ok, which stays as an alias for the
     existing tick/link rules in site.css. */
  --c-ink-sage: 63 100 66;
  --c-ink-honey: 149 101 26;
  --c-ok: var(--c-ink-sage);
}
@media (prefers-color-scheme: dark) {
  :root {
    /* In dark mode the fills themselves are already text-safe, so the inks
       alias them rather than fork the value: sage 6.83:1 and honey 7.80:1 on
       the dark bg (6.90:1 on the dark surface). */
    --c-ink-sage: var(--c-primary);
    --c-ink-honey: var(--c-accent-food);
  }
}