/*
 * Brand tokens — the one place this site's colours are decided.
 *
 * The captured pages ship a minified Tailwind bundle (assets/css/site.css)
 * that defines --ploy-* custom properties under :root, .light and .dark. That
 * file is generated output, so it is not edited by hand; this sheet loads
 * after it and overrides the few tokens we actually own. Re-capturing the site
 * therefore cannot silently revert a colour decision.
 *
 * Scoped to :root.light — which is exactly the captured pages, every one of
 * which is hard-coded class="h-full light" — for two reasons. It wins on
 * specificity rather than load order, and it cannot reach /zipsplit/, which is
 * not a captured page and carries its own light/dark tokens in
 * styles/tokens.css. A bare :root here would have overwritten that page's
 * --background in dark mode too, painting a dark page beige.
 *
 * The generated case-study pages opt in by emitting class="light" as well, so
 * this one sheet covers every page the site owns.
 *
 * The page background is FT beige. Everything else — the coral accents,
 * buttons and borders — is left as it was: those are separate tokens in
 * site.css and keep their own values, so the accent colour still reads against
 * the new background.
 *
 * Dark mode is not wired up anywhere (every captured page is hard-coded
 * class="h-full light" and nothing toggles it), so .dark is left untouched. If
 * it is ever switched on, its background needs deciding then — beige is a
 * paper colour and has no business being a dark-mode surface.
 */
:root.light {
  /* Financial Times paper. Warm enough to read as paper rather than grey,
     light enough to keep near-black body text around 13:1. */
  --ploy-neutral-primary: #fff1e5;
  --ploy-text-primary: oklch(20% 0 0);
  /* site.css sets --background to the same coral; the shared nav reads it as a
     fallback, so it has to move too or the bar keeps the old colour. */
  --background: #fff1e5;
}