/*
  themes/default.css — the SAFE FALLBACK theme for generated event pages.

  This is what any event gets when its `theme.theme_id` is missing, empty,
  or not one of the small allowlist scripts.lib.context.KNOWN_THEME_IDS
  recognizes (see that module's resolve_theme_id() — the fail-closed
  contract: an unrecognized theme_id resolves to "default" here, never to
  "kanye" or any other event's theme). It must therefore never reference
  any event-specific asset — no artist photo, no signature artwork, no
  brand-specific font, nothing that would look wrong or borrowed on an
  unrelated event.

  Loaded after event-base.css, before nothing else — this file supplies
  ONLY the custom-property values event-base.css consumes, plus the two
  purely-decorative hooks (.hero background image, .themeArtwork) that
  event-base.css deliberately leaves theme-defined. See that file's own
  header comment for the full custom-property contract.
*/

:root{
  --event-bg:#0a0a0a;
  --event-surface:#f5f4f0;
  --event-accent:#315cff;
  /* Safe neutral default: the same blue as --event-accent, not a second
     "acid"-style color — a neutral theme has no reason to invent a
     distinct operational-status hue. See event-base.css's own comment on
     --event-status-accent for why this token exists at all (Kanye's real
     production styling uses two different accents for CTA vs. status
     indicators; a theme with only one accent just reuses it here). */
  --event-status-accent:#315cff;
  /* --event-accent (#315cff) only reaches 3.87:1 contrast against
     --event-bg (#0a0a0a) — below the 4.5:1 WCAG AA threshold for normal
     text — so text placed directly on an accent background (.cta,
     .statusStamp, .statusCenter .label, aside a, .moreEvents, .mobileCta;
     see event-base.css's own comment on --event-accent-foreground) needs
     an explicit, contrast-safe override rather than falling back to
     --event-bg like every other theme may. White reaches 5.12:1. */
  --event-accent-foreground:#ffffff;
  /* --event-status-accent (#315cff, same as --event-accent above) only
     reaches 3.87:1 against --event-bg (#0a0a0a) — below the 4.5:1 WCAG
     AA threshold — so text that reads the status hue directly (.updated,
     .vote .label, .saved, .statusSummary>div:first-child dd; see
     event-base.css's own comment on --event-status-foreground) needs a
     brighter, text-safe variant instead of --event-status-accent itself,
     which stays #315cff for decorative uses (status stamp/label
     backgrounds, the status dot, the status-card border) that don't need
     this override. #8fa5ff (8.48:1) is the same lighter blue
     site-v3.css's own legacy default styling already uses for this exact
     role, not an arbitrary new color. */
  --event-status-foreground:#8fa5ff;
  /* --event-accent (#315cff) only reaches 3.87:1 against --event-bg
     (#0a0a0a) — below the 4.5:1 WCAG AA threshold — so the poll section's
     .votePanel button.active state (which reads --event-accent directly
     as text on the --event-bg-backed .vote section; see event-base.css's
     own comment on --event-vote-active-foreground) needs the same
     text-safe treatment as --event-status-foreground above, but as its
     own token rather than reused — Kanye's real production active-vote
     color is its red/pink CTA hue, not its acid operational hue.
     #8fa5ff (8.48:1) is the SAME lighter blue site-v3.css's own legacy
     default styling already uses for this exact role
     (`.votePanel button.active{color:#8fa5ff}`), not an arbitrary new
     color. */
  --event-vote-active-foreground:#8fa5ff;
  --event-text:#fff;
  --event-muted:#6c6c6c;
  --event-line:#d8d8d8;
  --event-font-display:Arial,Helvetica,sans-serif;
  --event-font-body:Arial,Helvetica,sans-serif;
}

/* No --event-hero-bg override: event-base.css's own default
   (a plain two-tone gradient built from --event-bg/--event-surface)
   applies. No .themeArtwork background — the hook stays empty/invisible. */