/*
 * theme.css — WRITABLE, and almost always correct AS IS (empty).
 *
 * design.css defines the whole palette and every other token. This file is
 * loaded after it and overrides ONLY what you put here. Leave it empty unless
 * the user asked for a specific look.
 *
 * DO NOT paste the token list in here. Copying the defaults across and pinning
 * them changes nothing visually and permanently opts this app out of every
 * later design-system improvement — a fix to the palette can no longer reach
 * it. If you are writing a value identical to the default, delete the line.
 *
 * DO NOT invent a brand colour. The platform accent is deliberate and applies
 * across every app; a todo list or a feedback form is not a reason to change
 * it. Only set --accent when the user names a colour or an existing brand.
 *
 * When the user DOES ask ("make it purple", "match our orange"), the whole
 * edit is two or three lines:
 *
 *   :root {
 *     --accent: #7c5cff;
 *     --accent-soft: #efeaff;
 *   }
 *
 * Tokens are listed at the top of public/design.css — read them there.
 * Component rules never belong in this file.
 */

/* Brand tokens — set because the client named an explicit palette (white
   background, deep navy/blue, solar green, orange/yellow reserved for the
   primary CTA). --ink drives body copy + the default button; --accent
   drives only .btn.accent (the "GET FREE SOLAR QUOTE" style CTAs), which is
   exactly the "accent only for important CTA elements" request. Existing
   --success green is left untouched — it already reads as "solar green" for
   checkmarks/badges without inventing a second colour. */
:root {
  --ink: #0b2a4a;
  --accent: #ea7b1f;
  --accent-soft: #fdecd8;
}