/* One palette, both surfaces.
 *
 * The landing page and the account pages were designed a week apart and ended up disagreeing
 * about everything a visitor notices while crossing between them: the landing page's primary
 * action was near-black and the account's was dark green, the landing page set everything in
 * Arial while the account pages used the system stack, and the language control was a compact
 * chip on one and a full-width word button on the other. Each was internally consistent, so
 * nothing looked broken — it just felt like leaving the company at /login.
 *
 * style.css and account.css now both consume these. Add a colour here, not there.
 *
 * The two grounds stay different on purpose. A marketing page reading as warm paper and an
 * application reading as near-white is a distinction people expect; the primary action, the
 * ink, the rules and the type are what have to agree, and now do.
 */
:root {
  /* Ink */
  --ink: #1c2420;
  --muted: #5b635d;
  --line: #d6dbce;

  /* The single primary action colour, on both surfaces. Dark green rather than near-black:
     it is warmer, it is already what :focus-visible draws, and it is the one colour here that
     reads as the product rather than as default text. White on it measures 8.0:1. */
  --accent: #245b3b;
  --accent-ink: #ffffff;
  --accent-hover: #1b4a2f;
  --focus: #476928;

  /* Grounds */
  --paper: #f3f1e9;  /* the marketing page */
  --app: #f6f7f3;    /* the account pages */
  --tint: #e7efdf;   /* a block lifted off either ground */

  --radius: 6px;

  /* No webfont: the Content-Security-Policy has no font-src, so an @font-face file would be
     blocked, and the account pages were already using this stack. Loading a real typeface
     means adding `font-src 'self'` to website/vercel.json *and*
     deploy/nginx-veora-site.conf, and shipping the file. */
  --font: system-ui, -apple-system, "Segoe UI", Roboto, "Helvetica Neue", Arial, sans-serif;
}
