/*
 * Ultimate -- design pack for the oneclick theme.
 *
 * Loaded dead last in the cascade (functions.php oneclick_assets()), only
 * when oneclick_site('design_template') is 'ultimate'.
 *
 * RULING (2026-09-01, owner pivot -- "Ultimate: restore Home Services
 * look"): PR #241 gave this pack its own visual identity (directional hero
 * scrim, Instrument Serif + Inter type system, a 12px-radius card
 * language, pill-chip kickers, alternating section bands, a 3px footer
 * accent). The owner reversed that direction the same day: Ultimate must
 * look like Home Services (templates/lightning) again -- same fonts
 * (Manrope headings / Source Sans 3 body, header.php's own baseline), same
 * hero shade, same cards, same everything -- because the differentiation
 * plan going forward is STRUCTURE (section order, layout), not a different
 * skin. PR #241's full identity CSS is preserved in git history (the #241
 * merge, commit 895defe) and as a plain, unregistered reference copy at
 * wp-theme/oneclick/templates/ultimate_archive/ (see that directory's own
 * README.md) in case a future direction wants to revisit it -- it is not
 * deleted, just not the live look any more.
 *
 * The ONE thing kept from that pass is PR #234's Font Pairing preset
 * mechanism: a brief can still choose a different heading/body pairing for
 * the ultimate template specifically (platform/public/create.html step 6,
 * tools/provision_brief.py resolves it into brand.font_heading/
 * brand.font_body -> a per-site tokens.css's --font-heading/--font-body,
 * loaded before this file). --ocf-font-heading/--ocf-font-body below read
 * that value first, falling back to Manrope/Source Sans 3 -- this pack's
 * own default (data/fonts.json's ultimate_font_pairings), and the same
 * pairing header.php already hardcodes for every other pack -- only when
 * tokens.css hasn't set one at all (a render outside the provisioning
 * pipeline, e.g. a hand-built fixture). A build that picks no preset is
 * therefore byte-identical, look-wise, to Home Services.
 *
 * Everything else this pack used to override (hero, cards, chips, bands,
 * footer) is deliberately absent -- inherited straight from the shared
 * theme CSS, the same as lightning's own "design": "" gives it. This pack
 * keeps a (near-empty) design.css file, and template.json still points at
 * it, purely so the font mechanism above has somewhere to live.
 */

:root {
    --ocf-font-heading: var(--font-heading, 'Manrope', sans-serif);
    --ocf-font-body: var(--font-body, 'Source Sans 3', sans-serif);
}