/**
 * Lid Life events — design token alias layer.
 *
 * VALUES come from this site's own live Kadence global palette/typography
 * settings (the actual source of truth — see CLAUDE.md "Front-end pass 1"),
 * never copied from the events-v2.lidlife.co.uk reference app. Component
 * CSS (lidlife-events.css) must reference ONLY these --ll-* names, never
 * Kadence's --global-* variables directly — that's what makes a future
 * parent-theme migration a matter of redefining the aliases below, not
 * rewriting every component rule (decision #3's portability requirement).
 *
 * Hard-coded fallbacks match today's real Kadence values exactly (pulled
 * 2026-07-23 via `wp option get kadence_global_palette` and by grepping the
 * live homepage's rendered <style> block for the actual --global-paletteN
 * declarations - not guessed names). If Kadence's palette is ever edited in
 * the Customizer, the var() reference still wins; the fallback only matters
 * if --global-paletteN is ever undefined.
 *
 * Diffed against the app's own tokens (events-v2.lidlife.co.uk/css/styles.css)
 * per the "diff, don't assume" brief - close but NOT identical everywhere;
 * the site wins per that rule. Noted per-token below where they drifted.
 */

:root {
	/* Red: site #de2027 vs app #D6202A - same brand red, slightly different hue. Site wins. */
	--ll-red: var(--global-palette1, #de2027);
	--ll-red-dk: var(--global-palette2, #ff0a14);

	/* Ink: site's pure #000000 vs app's near-black #0E0E10 - site wins (genuinely pure black here, not a near-black). */
	--ll-ink: var(--global-palette4, #000000);

	/* Steel (secondary/meta text grey): no exact Kadence palette slot matches the app's #6B6E75.
	   palette5 (#4c4c4d) is the closest but noticeably darker. Rather than force a mismatched
	   site color onto a role the palette doesn't define, the app's own value is used directly here -
	   this is the one token NOT sourced from a --global-palette slot. Flagged for Matt: worth adding
	   a dedicated palette slot for this role if it recurs elsewhere on the site. */
	--ll-steel: #6b6e75;

	/* Bone (cream background for date blocks etc.): site #eeeae2 vs app #F4F1EA - both warm off-whites, close but not identical. Site wins. */
	--ll-bone: var(--global-palette8, #eeeae2);
	--ll-bone-2: var(--global-palette9, #eeeae2);

	/* Border: no exact site slot; palette6 (#e0e0dd) is the closest neutral and reads correctly
	   as a hairline row separator against --ll-bone. */
	--ll-border: var(--global-palette6, #e0e0dd);

	/* Hi-viz accent: site #efff00 vs app #E8FF3A - both yellow-green, close. Site wins.
	   (Not used by the card component today - carried for a future component that needs it.) */
	--ll-hiviz: var(--global-palette10, #efff00);

	/*
	 * Display face (large date numeral, titles, headings): Anton on BOTH the
	 * app and this site (site's own `heading_font`) - an exact match, not a
	 * diff. No new font load needed.
	 */
	--ll-f-display: var(--global-heading-font-family, Anton, sans-serif);

	/*
	 * Letterspaced uppercase label face (category chip, date month/weekday,
	 * venue/address line, buttons, pagination): the app uses "JetBrains Mono"
	 * (a face this site never loads). Rather than self-host a new font purely
	 * to chase the app's choice, this uses the site's OWN existing
	 * letterspaced-uppercase treatment instead - Sora at weight 700, already
	 * loaded site-wide for the primary nav (see theme_mods_kadence-child ->
	 * primary_navigation_typography) and already visible in the site's own
	 * brand voice (the red category chips on article pages). Per "the site
	 * wins as the living brand implementation": this is a deliberate
	 * substitution, not a shortcut - flag to Matt in case a genuinely
	 * monospace label look was wanted specifically. Net result: ZERO new
	 * fonts to self-host for this pass, not the one face the brief expected.
	 */
	--ll-f-label: "Sora", sans-serif;
	--ll-f-label-weight: 700;

	/* Body/description prose: this site's own base font, not the app's Barlow
	   Condensed (which the app itself only uses for its own chrome - search
	   box, filters - none of which this card component reproduces). */
	--ll-f-body: var(--global-body-font-family, "Source Sans Pro", sans-serif);
}