/* assets/css/fonts.css */
/* ==================================================================
   Kwizzbit fonts — explicit @font-face. theme.json registers these too (front-end), but the
   block-editor iframe doesn't always pick up the theme.json font-library faces, so headlines
   render in a fallback font and tightly-tuned mixed-size layouts look broken WHILE EDITING.
   Loading this file in the editor (and front-end as a harmless backup) guarantees the real
   licensed fonts everywhere. Paths are relative to this file (assets/css/ -> ../fonts/).
   ================================================================== */
@font-face{
	font-family: 'Roobert';
	src: url("https://kwizzbit.com/wp-content/themes/kwizzbit/assets/fonts/Roobert-Medium.woff2") format('woff2');
	font-weight: 500; font-style: normal; font-display: swap;
}
@font-face{
	font-family: 'Roobert';
	src: url("https://kwizzbit.com/wp-content/themes/kwizzbit/assets/fonts/Roobert-Bold.woff2") format('woff2');
	font-weight: 700; font-style: normal; font-display: swap;
}
@font-face{
	font-family: 'Roobert Semimono';
	src: url("https://kwizzbit.com/wp-content/themes/kwizzbit/assets/fonts/RoobertSemiMono-Regular.woff2") format('woff2');
	font-weight: 400; font-style: normal; font-display: swap;
}
@font-face{
	font-family: 'Roobert Semimono';
	src: url("https://kwizzbit.com/wp-content/themes/kwizzbit/assets/fonts/RoobertSemiMono-SemiBold.woff2") format('woff2');
	font-weight: 600; font-style: normal; font-display: swap;
}
@font-face{
	font-family: 'Pixelar';
	src: url("https://kwizzbit.com/wp-content/themes/kwizzbit/assets/fonts/Pixelar-Regular.ttf") format('truetype');
	font-weight: 400; font-style: normal; font-display: swap;
}

/* assets/css/base.css */
/* ==================================================================
   Kwizzbit base — global resets + utility classes used across patterns.
   Tokens come from theme.json; nothing here should declare colour or
   spacing values directly.
   ================================================================== */

/* The page-loader FOUC guard (html.kwb-loading { ... visibility:hidden }) lives in the
   page-loader segment's own CSS, not here — so it is only active on pages that actually
   include the loader, and is dismissed by the loader's own script. */

/* Dark-mode defensive line: the site is a deliberate light-only design. Declaring
   the light colour-scheme stops browsers from auto-darkening UA-styled controls
   (inputs, selects, textareas, scrollbars) in OS dark mode — which would otherwise
   render dark fields on our cream backdrops. Pairs with the <meta name="theme-color">
   in functions.php. Does NOT touch our explicitly-coloured elements. */
html {
	color-scheme: light;
	/* Paint the page CANVAS cream, matching <body>. iOS Safari draws its
	   dynamic-toolbar / overscroll regions (the strip beneath the floating
	   URL bar, pull-to-refresh, rubber-banding) from the canvas, NOT from
	   body — an unset canvas defaults to white and flashed through as a
	   naff white band at the bottom when the mobile-menu scrim faded in.
	   body still paints cream over the whole page, so this only ever shows
	   where body doesn't reach; the top status area stays as-is (driven by
	   theme-color, already cream). */
	background-color: var(--wp--preset--color--cream);
}

/* ==================================================================
   LOADER GATE — keep animations and reveals suppressed while the
   page-loader is showing (html has the .kwb-loading class).

   Two problems solved:
   1. Run-once CSS animations (e.g. content-rise, ~0.72s) would burn
      through their full duration while hidden behind the 3s loader,
      so the user never sees them. Pausing keeps them at frame 0.
   2. IntersectionObservers fire during load and add .is-visible, so
      when the loader lifts the [data-reveal] lift transition is already
      "done" — nothing moves. Forcing opacity/transform to their start
      state ensures the transition fires fresh when kwb-loading is removed.

   #kwb-loader lives directly in <body> (not in .kwb-segment) so
   the .kwb-segment scope never touches the loader's own animations.
   ================================================================== */
html.kwb-loading .kwb-segment,
html.kwb-loading .kwb-segment *{
	animation-play-state: paused !important;
}
/* Hold [data-reveal] elements at their start state even after
   .is-visible is added by the observer — transition fires on dismiss. */
html.kwb-loading [data-reveal]{
	transition: none !important;
}
html.kwb-loading [data-reveal].is-visible{
	opacity: 0 !important;
	transform: translateY(32px) !important;
}
/* Same guard for the JS-primed hero reveals (.has-scroll-reveal). Unlike scroll
   reveals — which are born hidden in CSS and never "prime" — the hero starts
   visible and only gets its hidden state when hero.js adds .has-scroll-reveal.
   With transitions live, that makes the hero animate INTO the hidden state
   (a priming fade/slide-down) before it lifts. If that priming animation hasn't
   finished when the loader lifts, its tail leaks on-screen: the hero flashes and
   restarts its lift from a slightly lower position. Suppressing transitions while
   the loader is up makes priming SNAP instantly, so the only transition the user
   ever sees is the lift itself (fires cleanly once .kwb-loading is removed).
   This is why ONLY the first, load-triggered block was affected. */
html.kwb-loading .has-scroll-reveal,
html.kwb-loading .has-scroll-reveal *{
	transition: none !important;
}
/* On a cross-PAGE view-transition navigation (NOT reloads — those skip the
   transition and keep the loader + lift) the cross-fade is the entrance. The
   pagereveal hook snaps the in-view reveal elements to .is-visible just before
   the snapshot is captured; suppress their transitions while the transition is
   active so that snap is instant, not a second lift fighting the cross-fade. */
html.kwb-vt-active .has-scroll-reveal,
html.kwb-vt-active .has-scroll-reveal *,
html.kwb-vt-active [data-reveal]{
	transition: none !important;
}

/* ==================================================================
   CONTENT-RISE — shared entry lift for load-gated section reveals
   (blog/FAQ header stagger, article + legal "window" lift). Held at
   frame 0 by the html.kwb-loading animation pause above, so it only
   plays once the page-loader clears — exactly like the rest of the
   site's entry choreography. `backwards` fill keeps the start state
   through any stagger delay and leaves NO lingering transform after,
   so it never creates a containing block for fixed/sticky children.
   ================================================================== */
@keyframes kwb-content-rise {
	from { opacity: 0; transform: translateY(28px); }
	to   { opacity: 1; transform: translateY(0); }
}

/* Universal reset — every source segment was authored against
   "* { box-sizing: border-box; margin: 0; padding: 0 }". The per-segment slices rely on it
   (e.g. footer/nav <ul> have list-style:none but no padding:0, so without this they inherit
   the browser's 40px list indent). Specificity 0 — WordPress block styles + theme.json
   spacing override it cleanly. */
*, *::before, *::after{
	box-sizing: border-box;
}
:where(*){
	margin: 0;
	padding: 0;
}

body{
	-webkit-font-smoothing: antialiased;
	-moz-osx-font-smoothing: grayscale;
	/* clip (not hidden): hidden forces overflow-y to `auto`, making <body> a
	   scroll container — which breaks `position: sticky` on the header relative
	   to the viewport. `clip` leaves overflow-y visible, so the sticky header
	   (and the Get started button within it) stays pinned while still trimming
	   the full-bleed .kwb-segment horizontal overflow. */
	overflow-x: clip;
	touch-action: pan-y;
}

/* Kill any bottom gap WP's layout system adds between the <main> and the
   footer template part. Target every wrapper layer individually to ensure
   no padding, margin or min-height sneaks through. */
.wp-site-blocks,
.wp-site-blocks > *{
	margin-bottom: 0 !important;
}
.wp-block-template-part[class]{
	display: block;
	margin-top: 0 !important;
	margin-bottom: 0 !important;
}
/* Collapse padding on the main group + post-content wrappers.
   WP's constrained layout and flow-root display can silently add
   bottom space that shows as a cream strip before the footer. */
main.wp-block-group,
.wp-block-post-content,
.entry-content{
	padding-bottom: 0 !important;
	margin-bottom: 0 !important;
}
/* The cookie-modal pattern sits as a bare wp:html block inside the footer
   template part. WP renders it as a div.wp-block-html which has no visual
   content (the <aside> is `hidden`) but still takes up layout space, creating
   a white strip under the footer. Collapse it to zero so it's invisible. */
footer.wp-block-template-part .wp-block-html:has(#cookie-modal){
	display: contents;
}

#kwb-page-wrap{
	position: relative;
	overflow-x: clip; /* clip, not hidden — preserves sticky (see body note above) */
	touch-action: pan-y;
}

.sr-only{
	position: absolute;
	width: 1px; height: 1px;
	padding: 0; margin: -1px;
	overflow: hidden;
	clip: rect(0,0,0,0);
	white-space: nowrap;
	border: 0;
}

:focus-visible{
	outline: 2px solid var(--wp--preset--color--coral);
	outline-offset: 3px;
}

.container{
	max-width: var(--wp--custom--layout--page-max);
	margin-inline: auto;
	padding-inline: var(--wp--custom--layout--gutter);
}

/* ------------------------------------------------------------------
   Segment full-bleed. Every pattern wraps its markup in
   <div class="wp-block-group alignfull kwb-segment kwb-segment--NAME">.
   `alignfull` only LIFTS WordPress's max-width clamp inside a constrained
   content column — it does NOT guarantee full-viewport width (it just fills
   whatever the content container is). This forces true 100vw regardless of
   the container, centred on the viewport (margin:calc(50% - 50vw)).
   body{overflow-x:hidden} clips the 100vw so there's no horizontal scrollbar.
   Each segment's own inner element re-centres its content via its own max-width.
   ------------------------------------------------------------------ */
.kwb-segment{
	width: 100vw;
	margin-left: calc(50% - 50vw);
	margin-right: calc(50% - 50vw);
	/* WP's is-layout-flow adds margin-block-start to direct children of the
	   post-content wrapper. Force 0 here so kwb-segments always butt flush. */
	margin-block: 0;
}

/* ------------------------------------------------------------------
   Off-screen animation pause (driven by assets/js/perf.js). When a
   segment scrolls well out of view, perf.js adds .kwb-anim-paused;
   freezing animation-play-state stops the compositor doing per-frame
   work for sections nobody is looking at, which keeps long pages
   smooth. Only affects the segment and its descendants; on-screen
   segments are untouched. (No effect in the editor — perf.js is a
   front-end-only script.)
   ------------------------------------------------------------------ */
.kwb-segment.kwb-anim-paused,
.kwb-segment.kwb-anim-paused *,
.kwb-segment.kwb-anim-paused *::before,
.kwb-segment.kwb-anim-paused *::after{
	animation-play-state: paused !important;
}

/* ------------------------------------------------------------------
   Editor-only scroll-reveal override. Scroll-reveal segments hide their
   content (opacity:0) until front-end JS adds .is-visible — but that JS
   doesn't run in the block-editor canvas, so patterns would show blank/faded
   while editing. In the editor the canvas is wrapped in .editor-styles-wrapper
   (absent on the front end), so this reveals reveal-elements ONLY in the editor
   and is completely inert on the published page. Covers [data-reveal] and any
   class containing "reveal" (.js-reveal, .scroll-reveal, …).
   ------------------------------------------------------------------ */
.editor-styles-wrapper [data-reveal],
.editor-styles-wrapper [class*="reveal"],
.editor-styles-wrapper .hiw-step,            /* how-it-works steps */
.editor-styles-wrapper .ready-made__header,  /* ready-made reveal targets */
.editor-styles-wrapper .ready-made__formats,
.editor-styles-wrapper .features__header,    /* features-9 reveal targets */
.editor-styles-wrapper .feature-panel,       /* (these gate on .is-visible, no "reveal" in the class) */
.editor-styles-wrapper .feature-tour__row [class*="feature-tour__"],  /* features-tour: rows reveal their children on .is-visible */
.editor-styles-wrapper .testimonials__header,   /* testimonials reveal targets */
.editor-styles-wrapper .testimonial-card,
.editor-styles-wrapper .impact-2__mic,          /* impact (GSAP-revealed, JS-gated) */
.editor-styles-wrapper .impact-2__headline,
.editor-styles-wrapper .impact-2__this,
.editor-styles-wrapper .impact-2__cta-wrap,
.editor-styles-wrapper .player-experience__copy,  /* player-experience reveal targets */
.editor-styles-wrapper .player-experience__photo,
.editor-styles-wrapper .beliefs__eyebrow,         /* beliefs reveal targets (no "reveal" in class) */
.editor-styles-wrapper .beliefs__statement-wrap,
.editor-styles-wrapper .beliefs__tags,
.editor-styles-wrapper .cc-offer__inner{          /* offer reveal target */
	opacity: 1 !important;
	transform: none !important;
}
.editor-styles-wrapper .impact-2__char{ visibility: visible !important; }  /* impact "This." chars */
/* Exception: layered "echo" headlines have a DESIGNED resting opacity below 1 (they sit behind
   the primary line). They're also .js-reveal, so the broad rule above would force them to full
   opacity in the editor. Restore their intended opacity here. Add new low-opacity reveal
   elements to this list if future segments introduce them. */
.editor-styles-wrapper .mantra__row--echo-1{ opacity: 0.28 !important; }
.editor-styles-wrapper .mantra__row--echo-2{ opacity: 0.12 !important; }

/* ------------------------------------------------------------------
   Flashing coral period — the blinking "." used at the end of titles
   (how-it-works steps, features-9 headline; mirrors the features-tour
   title accent). Shared utility so any title can borrow it.
   ------------------------------------------------------------------ */
.kwb-flash-period{
	color: var(--wp--preset--color--coral);
	animation: kwb-period-blink 1.1s step-end infinite;
	display: inline-block;
}
@keyframes kwb-period-blink{ 0%, 100%{ opacity: 1; } 50%{ opacity: 0; } }
@media (prefers-reduced-motion: reduce){
	.kwb-flash-period{ animation: none; }
}

/* ------------------------------------------------------------------
   iOS 26 Safari bottom-bar tint anchor (2026-09-16).
   Safari 26 colours the strip behind its minimised tab bar from the
   background-color of any fixed OR sticky element that touches the
   bottom 3px of the screen, is >= 80% of the screen wide and >= 3px
   tall. The mobile card decks (Ask/Post/Host, Modes) leave the next
   card waiting off the bottom edge, so its #FFFAF5 fill was painting a
   white strip under the URL bubble. This full-width cream element sits
   8px below the edge (4px inside, under the bar itself, never seen) and
   outranks everything, so Safari always samples the page cream instead.
   iOS-only via the touch-callout support test; other browsers never
   render it. Pseudo-elements are ignored by the sampler, hence a real
   element. It lives FIRST in parts/header.html: at the end of the
   footer it lost to the deck's sticky cards, which suggests Safari
   takes the first qualifying element in DOM order (round 4, still
   unverified). Height 0 does NOT qualify, keep >= 3px.
   ------------------------------------------------------------------ */
.kwb-tint-anchor{ display: none; }
@supports (-webkit-touch-callout: none){
	.kwb-tint-anchor{
		display: block;
		position: fixed;
		left: 0;
		right: 0;
		bottom: -8px;
		height: 12px;
		background-color: var(--wp--preset--color--cream);
		z-index: 300;               /* above the cookie sheet (200) and nav (100) */
		pointer-events: none;
	}
}

/* assets/css/components/announce-bar.css */
/* ============================================================
   ANNOUNCE BAR — kwizzbit/announce-bar
   Thin sitewide strip above the nav. Light coral band with
   NEW badge, offer copy and a text CTA link.

   ABOUT PAGE (body.page-id-115): the light strip read oddly
   sitting directly above the blood-orange hero, so it switches
   to a dark ink band with white copy. See the scoped block at
   the end of this file.

   MODES PAGE (body.page-id-97): used to carry the same dark ink
   band, matching the old coral mic-photo hero. The hero backdrop
   is cream now (modes.css/modes.js), so Modes reverted to the
   sitewide light strip — no scoped override left for it here
   (2026-08-12, user's call).
   ============================================================ */
/* ── PINNED AT THE TOP, AT ALL TIMES (Kev's call, 2026-07-15) ──────
   The strip is position:sticky, not fixed: it keeps its place in the
   page flow (so nothing needs artificial padding to compensate, and
   pages without the bar — the no-chrome ones — are untouched), and it
   pins itself to the viewport top the moment scrolling would carry it
   away. body{overflow-x:clip} in base.css was chosen precisely so
   viewport-sticky keeps working — see the comment there.

   Sticky can't travel beyond its PARENT box, and WP wraps the bar +
   site-header together in a ~127px <header class="wp-block-template-
   part"> — inside which the bar could only stick for 88px of scroll.
   So that wrapper is dissolved below (display:contents, the same
   trick base.css already uses on the cookie-modal's wrapper), which
   lifts the bar's sticky range to the full-height .wp-site-blocks.

   z-index 800: above all page content, below the mobile-menu backdrop
   (900), the floating burger (950) and the page loader. The desktop
   Get-started CTA (500) and the burger never overlap it spatially —
   both hold positions BELOW the bar now (see nav.css). */
.announce-bar {
  position: sticky;
  /* 0 for visitors. For LOGGED-IN views WP fixes its grey admin
     toolbar across the viewport top (32px desktop / 46px mobile) and
     publishes its height as this core variable — without the offset
     the pinned strip slides up BEHIND the toolbar and looks like it
     "isn't fixing" (exactly how it first presented on a logged-in
     desktop). Visitors never have the var, so they get top:0. */
  top: var(--wp-admin--admin-bar--height, 0px);
  z-index: 800;
  background: #FCE9E7;
  border-bottom: 1px solid rgba(255, 54, 35, 0.12);
  padding-block: 0.5rem;
  /* Glass ramp discipline (same lesson as the burger circle): the
     backdrop-filter idles at ZERO strength and rides the same
     transition as the fill, so the saturate() can never arrive ahead
     of the translucency and flash-boost whatever sits behind. */
  backdrop-filter: blur(0px) saturate(100%);
  -webkit-backdrop-filter: blur(0px) saturate(100%);
  transition:
    background-color 0.3s ease,
    backdrop-filter 0.3s ease,
    -webkit-backdrop-filter 0.3s ease;
}

/* Once content is actually scrolling beneath the pinned strip
   (.kwb-nav-floating = scrolling under way, the same flag that fades
   the burger's circle in), the solid band turns to liquid glass —
   one material language across all the floating chrome. High-alpha
   wash of the strip's own pink + strong blur keeps the offer copy
   and CTA fully legible over anything that passes underneath. At the
   top of the page nothing is beneath it, so it rests solid. */
.kwb-nav-floating .announce-bar {
  /* 0.88 fill: enough see-through for the frosted texture to read,
     opaque enough that content underneath is a whisper, not a voice
     (0.78 first cut felt "a bit too much" on device — user call). */
  background: rgba(252, 233, 231, 0.88);
  backdrop-filter: blur(14px) saturate(160%);
  -webkit-backdrop-filter: blur(14px) saturate(160%);
}

@media (prefers-reduced-motion: reduce) {
  .announce-bar { transition: none; }
}

/* Dissolve the header template-part wrapper (see the note above).
   header. + [class] beats base.css's `.wp-block-template-part[class]
   {display:block}` (0,2,1 vs 0,2,0). Scoped to <header> so the footer
   part keeps its box. The wrapper carried no other styling (verified:
   only the base.css display/margin rule targets it). */
header.wp-block-template-part[class] {
  display: contents;
}

/* With a permanent strip overlaying the top of the viewport, in-page
   anchor jumps (FAQ rail, future #links) must land BELOW it, not
   under it. Scoped with :has so pages without a bar are untouched. */
html:has(.announce-bar) {
  scroll-padding-top: calc(var(--kwb-announce-h, 2.4375rem) + 12px);
}
.announce-bar__inner {
  display: flex;
  align-items: center;
  justify-content: center;
  gap: 0.625rem;
  padding-inline: var(--wp--custom--layout--gutter);
  flex-wrap: wrap;
}
/* Slides — on desktop they're just inline groups sitting on one line.
   On mobile they become stacked, crossfading panes (see media query). */
.announce-bar__slide {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  gap: 0.625rem;
}
/* Badge */
.announce-bar__badge {
  display: inline-flex;
  align-items: center;
  background: var(--wp--preset--color--ink);
  color: #fff;
  font-family: var(--wp--preset--font-family--body);
  font-weight: 700;
  font-size: 0.625rem;
  letter-spacing: 0.08em;
  padding: 0.2rem 0.5rem;
  border-radius: 0;
  flex-shrink: 0;
  line-height: 1;
}
/* Copy */
.announce-bar__copy {
  font-family: var(--wp--preset--font-family--body);
  font-size: 0.875rem;
  font-weight: 400;
  color: var(--wp--preset--color--ink);
  margin: 0;
  line-height: 1.2;
}
.announce-bar__copy strong {
  font-weight: 700;
}
/* "Are we mad?" — separate item so it can be dropped on mobile */
.announce-bar__prompt {
  font-family: var(--wp--preset--font-family--body);
  font-size: 0.875rem;
  font-weight: 400;
  color: var(--wp--preset--color--ink);
  line-height: 1.2;
}
/* CTA link */
.announce-bar__cta {
  display: inline-flex;
  align-items: center;
  gap: 0.3rem;
  font-family: var(--wp--preset--font-family--body);
  font-size: 0.875rem;
  font-weight: 600;
  color: var(--wp--preset--color--coral);
  text-decoration: underline;
  text-decoration-color: transparent;
  text-underline-offset: 2px;
  transition: text-decoration-color 0.2s ease;
  white-space: nowrap;
  flex-shrink: 0;
}
.announce-bar__cta:hover {
  text-decoration-color: var(--wp--preset--color--coral);
}
/* Looping "beckon" on the arrow — nudges right, settles, pauses, repeats — to
   draw the eye to the offer. Transform-only (composited, no jitter). */
.announce-bar__cta svg {
  animation: ab-cta-beckon 1.6s ease-in-out infinite;
  will-change: transform;
}
.announce-bar__cta:hover svg { animation-play-state: paused; } /* hold still while being clicked */
@keyframes ab-cta-beckon {
  0%, 65%, 100% { transform: translateX(0); }
  32%           { transform: translateX(4px); }
}
@media (prefers-reduced-motion: reduce) {
  .announce-bar__cta svg { animation: none; }
}
/* ============================================================
   MOBILE — crossfade rotator
   The two slides stack in the same spot and fade one after the
   other on a loop:
     Slide A:  [NEW]  3 months of Game-show for £60.
     Slide B:  Are we mad?  Yes, get offer →
   ============================================================ */
@media (max-width: 600px) {
  .announce-bar__inner {
    position: relative;
    display: block;
    /* Reserve one line's height so the absolute slides have a stage */
    min-height: 1.35rem;
  }
  .announce-bar__slide {
    position: absolute;
    inset: 0;
    /* gap a touch tighter on the small stage */
    gap: 0.5rem;
    will-change: opacity;
  }
  .announce-bar__slide--a {
    animation: ab-rotate-a 7s ease-in-out infinite;
  }
  .announce-bar__slide--b {
    animation: ab-rotate-b 7s ease-in-out infinite;
  }

  /* The two lines hand over one AFTER the other (out, a beat of empty
     stage, then in) rather than crossfading, so they never sit on top of
     each other mid-fade (Max, 2026-09-28; was a straight crossfade).
     Slide A: first half, fades out for slide B. */
  @keyframes ab-rotate-a {
    0%   { opacity: 1; pointer-events: auto; }
    42%  { opacity: 1; }
    47%  { opacity: 0; pointer-events: none; }
    95%  { opacity: 0; }
    100% { opacity: 1; pointer-events: auto; }
  }
  /* Slide B: second half. pointer-events gated so the CTA is only
     tappable while visible. */
  @keyframes ab-rotate-b {
    0%   { opacity: 0; pointer-events: none; }
    48%  { opacity: 0; }
    53%  { opacity: 1; pointer-events: auto; }
    89%  { opacity: 1; }
    94%  { opacity: 0; pointer-events: none; }
    100% { opacity: 0; }
  }

  /* Reduced motion — no fade loop. Fall back to a static inline flow
     (both slides shown, wrapping naturally) so nothing is hidden. */
  @media (prefers-reduced-motion: reduce) {
    .announce-bar__inner {
      position: static;
      display: flex;
      flex-wrap: wrap;
      min-height: 0;
    }
    .announce-bar__slide {
      position: static;
      inset: auto;
      animation: none;
      opacity: 1;
      pointer-events: auto;
    }
  }
}

/* ============================================================
   ABOUT PAGE — dark variant (body.page-id-115)
   Deep ink band + white copy so the strip doesn't clash sitting
   above the About hero's blood-orange. Scoped by body id, so the
   sitewide light bar is untouched everywhere else. First pass —
   easy to retune (band colour, badge, CTA) from here.
   ============================================================ */
body.page-id-115 .announce-bar {
  background: var(--wp--preset--color--ink);          /* #1D0B09 */
  border-bottom-color: rgba(255, 255, 255, 0.10);
}
/* Copy + prompt → white */
body.page-id-115 .announce-bar__copy,
body.page-id-115 .announce-bar__copy strong,
body.page-id-115 .announce-bar__prompt {
  color: #fff;
}
/* NEW badge: flip to a coral accent (the ink badge would vanish on the ink band) */
body.page-id-115 .announce-bar__badge {
  background: var(--wp--preset--color--coral);        /* #FF3623 */
  color: #fff;
}
/* CTA → light coral so it pops off the ink band, with a matching hover underline */
body.page-id-115 .announce-bar__cta {
  color: #FF6F5F;
}
body.page-id-115 .announce-bar__cta:hover {
  text-decoration-color: #FF6F5F;
}

/* ── Glass-on-scroll for the DARK variant (About only now) ──────────
   The about solid-ink rule above is (0,2,1) and outranks the sitewide
   glass rule (0,2,0), so without this the dark strip would stay solid
   while scrolled. Same translucency step as the pink band, in the ink;
   the blur comes from the sitewide glass rule (this page rule never
   declares backdrop-filter, so it cascades through untouched). (0,3,1)
   beats the solid variant. Modes dropped out of this selector when it
   reverted to the sitewide light strip — the plain glass rule elsewhere
   in this file already covers it correctly. */
.kwb-nav-floating body.page-id-115 .announce-bar {
  /* Same "thicker glass" step as the pink band (0.80 → 0.90; the ink
     runs a touch more opaque than the pink for text contrast). */
  background: rgba(29, 11, 9, 0.90);
}


/* ============================================================
   PUB-GROUPS PAGE — Enterprise variant (2026-09-28, Max)
   /for-pub-groups/ swaps the promo for "ENTERPRISE  Running
   multiple venues?  Yes, contact sales ->" on a peach band, just a
   shade more orange than the sitewide pink (Max: ever so slightly).
   Keyed off the page's own hero section rather than a page ID,
   because IDs differ between local, staging and live.
   2026-09-30 (Max): /for-pubs-bars-venues/ shows it too, so the
   key is now any hx hero (pub-groups -v1 AND the pubs -pb fork).
   ============================================================ */
.announce-bar .announce-bar__inner--enterprise { display: none; }
body:has(.kwb-segment--hx-hero) .announce-bar__inner:not(.announce-bar__inner--enterprise) { display: none; }
body:has(.kwb-segment--hx-hero) .announce-bar .announce-bar__inner--enterprise { display: flex; }
@media (max-width: 600px) {
  body:has(.kwb-segment--hx-hero) .announce-bar .announce-bar__inner--enterprise { display: block; }
}
@media (max-width: 600px) and (prefers-reduced-motion: reduce) {
  body:has(.kwb-segment--hx-hero) .announce-bar .announce-bar__inner--enterprise { display: flex; }
}
body:has(.kwb-segment--hx-hero) .announce-bar {
  background: #FDE5D6;                                  /* a touch peachier than the promo pink #FCE9E7 */
}
.kwb-nav-floating body:has(.kwb-segment--hx-hero) .announce-bar {
  background: rgba(253, 229, 214, 0.88);                /* same glass step as the pink band */
}

/* assets/css/components/button.css */
/* ==================================================================
   Button — kwizzbit/button (SHARED component)
   Spec: STYLEGUIDE.md §3. Used by every segment that renders .btn.
   Enqueued globally (front-end + editor iframe) via functions.php glob,
   so any pattern referencing .btn / .btn--primary / .btn--secondary
   inherits the full coral/dark gradient treatment without re-declaring it.
   ================================================================== */

.btn{
	display: inline-flex;
	align-items: center;
	gap: 7px;
	min-height: 44px;
	font-family: var(--wp--preset--font-family--body);
	font-size: var(--wp--preset--font-size--sm);
	font-weight: 700;
	letter-spacing: 0;
	line-height: 1;
	border-radius: 0;
	border: none;
	cursor: pointer;
	text-decoration: none;
	transition:
		transform  var(--wp--custom--motion--dur-base) var(--wp--custom--motion--ease-out),
		background var(--wp--custom--motion--dur-fast) var(--wp--custom--motion--ease-out),
		box-shadow var(--wp--custom--motion--dur-base) var(--wp--custom--motion--ease-out);
}

.btn__arrow{
	width: 10px;
	height: 10px;
	flex-shrink: 0;
	transition: transform var(--wp--custom--motion--dur-base) var(--wp--custom--motion--ease-out);
}
/* ════════════════════════════════════════════════════════════════════════
   THE brand arrow — one definition, every button, zero drift.
   Every primary/secondary CTA on the site (whatever its class — .btn,
   .learn-more, .features__cta, .features-trio__cta, .ah-hero__cta, .mode-cta,
   .plan-card__cta, .hero__cta …) embeds the SAME polygon: the "See all
   features" arrow on How it Works. We target it by its OWN geometry, not by
   button class, so no CTA — present or future — can opt out or drift. Glyph
   rendering, size, and the anti-jitter compositor layer ALL live right here.
   ════════════════════════════════════════════════════════════════════════ */
polygon[points^="82.391 9.65"]{          /* attribute selector → works in every browser */
	fill: #fff;
	stroke: #fff;
	stroke-width: 1;
	paint-order: stroke fill;            /* crisp silhouette, byte-identical everywhere */
}
svg:has(> polygon[points^="82.391 9.65"]){
	width: 10px;
	height: 10px;
	flex-shrink: 0;
	display: block;
	transform: translateZ(0);            /* own GPU layer → never re-rasterises during a button's hover-lift → no shimmer */
	backface-visibility: hidden;
}
.btn:hover .btn__arrow{ transform: translateZ(0); } /* no 2D nudge; keeps the icon's compositor layer (see ICON STABILITY below) */

/* Primary — coral gradient */
.btn--primary{
	background: var(--wp--preset--gradient--btn-primary);
	color: var(--wp--preset--color--white);
	height: 42px;
	padding: 0 2.5rem;
}
@media (hover: hover){
	.btn--primary:hover{
		background: var(--wp--preset--gradient--btn-primary-hover);
		transform: translateY(-1px);
	}
}
/* Touch press — hover gradient + a tactile push-DOWN (fires on finger-down) */
.btn--primary:active{
	background: var(--wp--preset--gradient--btn-primary-hover);
	transform: translateY(1px);
}

/* Secondary — dark warm gradient */
.btn--secondary{
	background: var(--wp--preset--gradient--btn-secondary);
	color: var(--wp--preset--color--white);
	height: 42px;
	padding: 0 1.0625rem;
}
@media (hover: hover){
	.btn--secondary:hover{
		background: var(--wp--preset--gradient--btn-secondary-hover);
		transform: translateY(-1px);
	}
}
.btn--secondary:active{
	background: var(--wp--preset--gradient--btn-secondary-hover);
	transform: translateY(1px);
}

/* ==================================================================
   CTA CONSISTENCY — enforced across every button variant in every pattern
   (.btn, .mode-cta, .learn-more). Single source of truth; overrides any
   per-segment button styling that loads later.
   1. Arrow is always 10x10 (the modes reference).
   2. The arrow NEVER moves on hover.
   3. A button container NEVER carries a glow/shadow.
   ================================================================== */
.btn__arrow,
.mode-cta__arrow{
	width: 10px;
	height: 10px;
	flex-shrink: 0;
}
/* Some patterns wrap the SVG in a <span class="btn__arrow"> — an inline span ignores
   width/height, so the nested SVG would render at its natural (bigger) size. Size the
   inner SVG directly so every arrow is 10x10 regardless of span-vs-direct markup. */
.btn__arrow svg,
.mode-cta__arrow svg{
	width: 10px;
	height: 10px;
	display: block;
}
/* Some patterns (e.g. flow) put a BARE <svg> straight inside the button with no
   .btn__arrow wrapper and its own larger width/height attrs. Size those directly too
   so every CTA arrow is the 10x10 modes reference regardless of markup shape. */
.btn > svg,
.mode-cta > svg,
.learn-more > svg{
	width: 10px;
	height: 10px;
	flex-shrink: 0;
	display: block;
}
/* Kill any per-pattern 2D arrow-nudge on hover. translateZ(0) (not `none`)
   so the icon's compositor layer survives the hover — see ICON STABILITY. */
.btn:hover .btn__arrow,
.mode-cta:hover .mode-cta__arrow,
.learn-more:hover .btn__arrow{
	transform: translateZ(0) !important;
}
.btn,
.btn--primary,
.btn--secondary,
.mode-cta,
.learn-more{
	box-shadow: none !important;
}

/* ==================================================================
   BUTTON EDGES — Max, 2026-09-16 (the card edge system's sibling).
   Every primary coral button wears a 1px #F42D1A edge, every secondary
   dark-brown button a 1px #120504 edge: one tone deeper than each fill,
   so the button reads as a solid object with a defined rim rather than a
   flat gradient patch. Enforced here, globally, across every variant the
   site renders (the survey of 2026-09-16 found these classes; add any new
   coral / dark CTA to the matching list). !important because segment
   sheets load after this one and several declare border: 0 / none at the
   same specificity. box-sizing is border-box sitewide, so no size change.
   The edge stays put on hover / active; only the fill shifts.
   ================================================================== */
.btn--primary,
.mode-cta--coral,
.plan-card__cta--primary,
.btn--pay,
.kwb-cta .kwb-cta__btn--coral,
.qh-gate__btn,
.mobile-menu__cta{
	border: 1px solid #F42D1A !important;
}
.btn--secondary,
.learn-more,
.features__cta,
.features-trio__cta,
.impact-2__btn,
.mode-cta,
.plan-card__cta--enterprise,
.contact__submit,
.bh-newsletter__btn,
.blog-newsletter__btn,
.anthem-trigger,
.gateway__cta,
.gateway__forgot-cta,
.payment-success__cta,
.kwb-cta .kwb-cta__btn--dark,
.qh-interval__next,
.qh-end__cta{
	border: 1px solid #120504 !important;
}
/* .mode-cta carries both classes when coral; the coral list must win */
.mode-cta.mode-cta--coral{ border-color: #F42D1A !important; }
/* Hover / press: the fill shifts to its hover gradient, so the rim steps
   down with it and stays one tone deeper (same delta as at rest:
   #D82A18 → #CD210F on coral, #0D0504 → #020000 on dark). Dark list first,
   coral second, so a coral .mode-cta resolves to the coral rim. The
   article offer card hovers as a whole card, hence the .kwb-cta:hover
   forms. */
@media (hover: hover){
	.btn--secondary:hover,
	.learn-more:hover,
	.features__cta:hover,
	.features-trio__cta:hover,
	.impact-2__btn:hover,
	.mode-cta:hover,
	.plan-card__cta--enterprise:hover,
	.contact__submit:hover,
	.bh-newsletter__btn:hover,
	.blog-newsletter__btn:hover,
	.anthem-trigger:hover,
	.gateway__cta:hover,
	.gateway__forgot-cta:hover,
	.payment-success__cta:hover,
	.kwb-cta:hover .kwb-cta__btn--dark,
	.qh-interval__next:hover,
	.qh-end__cta:hover{
		border-color: #020000 !important;
	}
	.btn--primary:hover,
	.mode-cta--coral:hover,
	.mode-cta.mode-cta--coral:hover,
	.plan-card__cta--primary:hover,
	.btn--pay:hover,
	.kwb-cta:hover .kwb-cta__btn--coral,
	.qh-gate__btn:hover,
	.mobile-menu__cta:hover{
		border-color: #CD210F !important;
	}
}
.btn--secondary:active,
.learn-more:active,
.features__cta:active,
.features-trio__cta:active,
.impact-2__btn:active,
.mode-cta:active,
.plan-card__cta--enterprise:active,
.contact__submit:active,
.bh-newsletter__btn:active,
.blog-newsletter__btn:active,
.anthem-trigger:active,
.gateway__cta:active,
.gateway__forgot-cta:active,
.payment-success__cta:active,
.kwb-cta:active .kwb-cta__btn--dark,
.qh-interval__next:active,
.qh-end__cta:active{
	border-color: #020000 !important;
}
.btn--primary:active,
.mode-cta--coral:active,
.mode-cta.mode-cta--coral:active,
.plan-card__cta--primary:active,
.btn--pay:active,
.kwb-cta:active .kwb-cta__btn--coral,
.qh-gate__btn:active,
.mobile-menu__cta:active{
	border-color: #CD210F !important;
}

/* ==================================================================
   ICON STABILITY — eliminate the sub-pixel "wiggle" on hover.
   When a button lifts (translateY) and/or cross-fades its gradient,
   the browser re-rasterises the whole button — SVG included — at
   fractional pixel offsets on every frame of the transition, so the
   icon's crisp edges shimmer. Promoting each icon to its own compositor
   layer (translateZ + backface-visibility) means it's painted ONCE and
   merely composited (moved/faded) with the button — never repainted —
   so it sits perfectly still. Pure rendering hint: no layout, colour,
   size or motion of the button itself changes. Covers every lift-button
   family sitewide (this file is enqueued globally).
   ================================================================== */
.btn svg,
.mode-cta svg,
.learn-more svg,
.impact-2__btn svg,
.footer-nav__social-link svg,
.plan-card__cta svg,
.anthem-trigger svg,
.gateway__cta svg,
.gateway__google svg,
.features__cta svg,
.features-trio__cta svg,
.ah-hero__cta svg,
.hero__cta svg,
.modes__cta svg,
.blog-post__quiz-cta svg,
.arrow-btn svg{
	display: block;
	transform: translateZ(0);
	backface-visibility: hidden;
}

@media (prefers-reduced-motion: reduce){
	.btn:hover,
	.btn:active,
	.btn:hover .btn__arrow{ transform: none !important; }
}

/* ==================================================================
   TOUCH SIZING — mobile & tablet (≤1023px) only; desktop untouched.
   Unifies every rectangular CTA family to a 48px touch target
   (the comfortable standard, vs the 44px legal minimum) with 15px
   label text so the type holds its proportion in the taller box.
   Before this block the families were uneven: .btn 44, .mode-cta 42,
   .learn-more ~38, .plan-card__cta ~36.
   !important because the per-segment files that set these families'
   heights/font-sizes load AFTER button.css alphabetically — same
   enforcement trick as the CTA CONSISTENCY block above.
   ================================================================== */
@media (max-width: 1023px){
	.btn,
	.mode-cta,
	.learn-more,
	.features__cta,
	.features-trio__cta,
	.mobile-menu__cta,
	.mobile-menu__login, /* sits flex-paired beside .mobile-menu__cta — must grow with it or the pair mismatches */
	.impact-2__btn,
	.plan-card__cta{
		min-height: 48px !important;
		font-size: 0.9375rem !important;
	}
	/* .plan-card__cta is inline-block (text-only label, text-align centring),
	   so min-height alone would leave its label pinned to the top — flex it
	   so the taller box still centres vertically. !important because
	   pricing.css loads after this file and would win the display battle. */
	.plan-card__cta{
		display: inline-flex !important;
		align-items: center !important;
		justify-content: center !important;
	}
}

/* ==================================================================
   TOUCH PRESS FEEDBACK — reduced-motion guard for every CTA family.
   The per-family :active push-down is suppressed for users who asked
   for reduced motion; the gradient/colour shift still confirms the tap.
   ================================================================== */
@media (prefers-reduced-motion: reduce){
	.btn--primary:active, .btn--secondary:active, .mode-cta:active, .learn-more:active,
	.impact-2__btn:active, .features__cta:active, .features-trio__cta:active,
	.anthem-trigger:active, .plan-card__cta:active, .btn--pay:active,
	.gateway__google:active, .gateway__cta.is-visible:active, .gateway__forgot-cta.is-active:active,
	.mobile-menu__cta:active, .blog-newsletter__btn:active, .blog-post__share-btn:active,
	.cookie-modal__btn--ghost:active, .cookie-modal__btn--outline:active{
		transform: none !important;
	}
}

/* assets/css/components/contact.css */
/* ==================================================================
   Contact — kwizzbit/contact (whole-file segment)
   Faithful slice of /HTML/contact.html. Globals (reset/body/font-face/:root)
   dropped; tokens canonical (theme.json). Full-bleed via the .kwb-segment wrapper.
   ================================================================== */

.contact {
  --contact-label-color: #473833;
  --contact-label-optional-color: #8C7068;
  --contact-placeholder: #827571;
}

.contact {
  padding-inline: var(--wp--custom--layout--gutter);
  padding-block: 3.5rem 6rem;
  /* Vertical rhythm: generous top breathing room below sticky header */
}

/* Desktop: this page has no nav/footer, so centre the content vertically in
   the window. Column flex + min-height lets it grow & scroll if it ever
   exceeds the viewport (no clipping). */
@media (min-width: 1024px) {
  .contact {
    min-height: 100vh;
    display: flex;
    flex-direction: column;
    justify-content: center;
    padding-block: 2.5rem;
  }
}

.contact__inner {
  max-width: 1100px;   /* matches hero/audience-split constrain width */
  margin-inline: auto;
  display: grid;
  grid-template-columns: 420px 1fr;
  gap: 80px;           /* matches hero-split column gap */
  align-items: start;
}

/* =============================================================
   LEFT COLUMN
   ============================================================= */
.contact__left {
  display: flex;
  flex-direction: column;
  gap: 2.5rem;
  /* WP deviation: no .container class — see hero-split QA note */
}

/* --- Headline ------------------------------------------------ */
.contact__headline {
  font-family: var(--wp--preset--font-family--display);
  font-weight: 400;
  font-size: 4.5rem;    /* H2-sketch: 72px */
  line-height: 0.889;
  letter-spacing: -0.10769em;
  color: var(--wp--preset--color--ink);
}

.contact__headline-accent {
  color: var(--wp--preset--color--coral);
}

/* Zero-width anchor — same technique as testimonials finger + pricing handshake
   Does NOT affect line-height or text layout at any breakpoint */
.contact__headline-anchor {
  position: relative;
  display: inline-block;
  width: 0;
  overflow: visible;
  pointer-events: none;
}

/* Pixel pointing finger floating asset
   WP handoff: replace src with WP media library URL, same as pricing handshake
   NOTE: finger image provided as Image 2 in design handoff.
   Using CSS emoji render as preview stand-in — swap for real PNG/WebP on WP handoff. */
.contact__finger {
  position: absolute;
  bottom: -0.15em;
  left: 0.12em;
  width: 115px;
  height: auto;
  pointer-events: none;
  animation: finger-point 3.5s cubic-bezier(0.65, 0, 0.35, 1) infinite;
  image-rendering: pixelated;  /* preserves pixel art quality */
}

@keyframes finger-point {
  0%, 100% { transform: translateX(0)    rotate(-2deg); }
  35%       { transform: translateX(8px)  rotate(1deg); }
  65%       { transform: translateX(4px)  rotate(-1deg); }
}

/* --- Lead ---------------------------------------------------- */
.contact__lead {
  font-family: var(--wp--preset--font-family--body);
  font-weight: 500;
  font-size: var(--wp--preset--font-size--md);  /* 17px */
  line-height: 1.412;
  color: var(--wp--preset--color--ink);
  width: 327px;   /* locked — matches hero-split lead width spec */
  max-width: 100%;
}

/* --- Trust logos -------------------------------------------- */
.contact__trust {
  display: flex;
  flex-direction: column;
  gap: 1rem;
}

/* ── Trust logo strip — exact pricing__social spec, contact__ namespace ── */
.contact__social-label {
  font-family: var(--wp--preset--font-family--body);
  font-weight: 600;        /* SemiBold */
  font-size: 0.8125rem;   /* 13px */
  color: var(--wp--preset--color--ink);
}
/* Desktop + tablet: 4-col × 2-row static grid, logos dark + small */
.contact__logos {
  display: block;           /* wrapper — grid lives on the track */
}
.contact__logos svg {
  display: block;
  flex-shrink: 0;
}
.contact__logos-ticker  { display: contents; }
.contact__logos-track   {
  display: grid;
  grid-template-columns: repeat(4, auto);
  gap: 1.375rem 1.5rem;
  align-items: center;
  justify-content: start;
}
/* SVGs at natural height — small, full opacity, matching Sketch */
.contact__logos-track svg {
  height: 17px;
  width: auto;
  opacity: 1;
}
/* "& more" SVG is smaller by design — roughly half the logo height */
.contact__logo-more-wrap svg {
  height: 13px;
}
.contact__logos-track:last-child { display: none; }

@media (max-width: 640px) {
  /* Mobile: static 4×2 grid — no ticker */
  .contact__logos-ticker { display: contents; }
  .contact__logos-track  {
    display: grid;
    grid-template-columns: repeat(4, auto);
    gap: 0.75rem 1.25rem;
    align-items: center;
    justify-content: start;
  }
  .contact__logos-track:last-child { display: none; }
  .contact__logos-track svg {
    height: 14px;
    width: auto;
    opacity: 1;
  }
  .contact__logo-more-wrap svg { height: 11px; }
} /* end @media (max-width: 640px) */



/* --- Back link ---------------------------------------------- */
.contact__back {
  display: inline-flex;
  align-items: center;
  gap: 0.375rem;
  font-family: var(--wp--preset--font-family--body);
  font-weight: 600;        /* SemiBold */
  font-size: var(--wp--preset--font-size--nav);
  color: var(--wp--custom--color--nav-ink);
  text-decoration: none;
  margin-top: 0.75rem;    /* extra breathing room below trust logos */
  transition: color var(--wp--custom--motion--dur-fast) ease;
  align-self: flex-start;
}
.contact__back:hover {
  color: var(--wp--preset--color--coral);
}
.contact__back:hover .contact__back-chevron polygon {
  fill: var(--wp--preset--color--coral);
}
/* Chevron rotated 90° counter-clockwise (points left) */
.contact__back-chevron {
  display: flex;
  align-items: center;
  transform: rotate(90deg);
  flex-shrink: 0;
}

/* =============================================================
   FORM CARD
   ============================================================= */
/* Card edge system (2026-09-16): #FFFAF5 fill + 1px pure-white hairline on every
   card, whichever cream it sits on. See ready-made.css .quiz-panel for the why. */
.contact__card {
  background: #FFFAF5; /* was white */
  border: 1px solid #FFFFFF;
  border-radius: 0;
  padding: 2.25rem 2.25rem 2rem;
  box-shadow: 0 20px 50px rgba(255, 54, 35, 0.10);
  transition: background-color 360ms ease;
}

/* =============================================================
   FORM LAYOUT
   ============================================================= */
.contact__form {
  display: flex;
  flex-direction: column;
  gap: 1.125rem;
}
.contact__row {
  display: grid;
  grid-template-columns: 1fr 1fr;
  gap: 1rem;
}
.contact__field {
  display: flex;
  flex-direction: column;
  gap: 0.5625rem;  /* 9px */
  min-width: 0;    /* allows grid cells to compress equally */
}
.contact__field--full {
  grid-column: 1 / -1;
}

/* =============================================================
   LABELS
   ============================================================= */
.contact__label {
  font-family: var(--wp--preset--font-family--body);
  font-weight: 500;        /* Medium */
  font-size: 0.8125rem;   /* 13px */
  color: var(--contact-label-color);
  line-height: 1;
  letter-spacing: 0.005em;
}
.contact__label-optional {
  font-weight: 500;
  color: var(--contact-label-optional-color);
  margin-left: 0.2em;
}

/* =============================================================
   INPUTS — from Sketch design:
   - Warm cream fill #F5DFCE
   - No visible border (0.5px same-tone, effectively invisible)
   - border-radius: 0 (site convention)
   - Comfortable padding, slightly taller than default
   - Placeholder in muted warm tone
   - Focus: coral border + white bg
   ============================================================= */
.contact__input,
.contact__select,
.contact__textarea {
  font-family: var(--wp--preset--font-family--body);
  font-weight: 500;        /* Medium */
  font-size: 0.875rem;    /* 14px */
  color: var(--wp--preset--color--ink);
  background: #F6EEE7;
  border: none;
  border-radius: 0;
  padding: 0.8125rem 0.9375rem;
  width: 100%;
  line-height: 1.4;
  outline: none;
  transition: background var(--wp--custom--motion--dur-fast) ease,
              box-shadow  var(--wp--custom--motion--dur-fast) ease;
  -webkit-appearance: none;
  appearance: none;
}
.contact__input::placeholder,
.contact__textarea::placeholder {
  color: var(--contact-placeholder);
  font-weight: 500;
}
.contact__input:focus,
.contact__select:focus,
.contact__textarea:focus {
  background: #F6EEE7;   /* hold the warm fill — no jarring white flash */
  box-shadow: inset 0 0 0 1px #D7BAAF;  /* single thin warm border, matches card border */
  outline: none;
}

/* =============================================================
   PHONE FIELD
   ============================================================= */
.contact__phone-wrap {
  display: flex;
  align-items: stretch;
  background: #F6EEE7;
  border: none;
  border-radius: 0;
  min-width: 0;         /* prevents grid blowout — keeps phone equal width to email */
  overflow: hidden;     /* clips prefix-wrap within bounds */
  transition: background var(--wp--custom--motion--dur-fast) ease,
              box-shadow var(--wp--custom--motion--dur-fast) ease;
}
.contact__phone-wrap:focus-within {
  background: #F6EEE7;
  box-shadow: inset 0 0 0 1px #D7BAAF;
}
/* Suppress red :focus-visible outline on prefix select and phone input */
.contact__phone-country:focus-visible,
.contact__phone-input:focus-visible {
  outline: none;
}
.contact__phone-prefix-wrap {
  position: relative;
  display: flex;
  align-items: center;
  flex-shrink: 0;
  width: 5.75rem;
}
/* Subtle vertical divider */
.contact__phone-prefix-wrap::after {
  content: '';
  position: absolute;
  right: 0;
  top: 25%;
  height: 50%;
  width: 0.5px;
  background: rgba(29,11,9,0.12);
  pointer-events: none;
}
/* Flag emoji */
.contact__phone-flag-overlay {
  position: absolute;
  left: 0.75rem;
  top: 50%;
  transform: translateY(-50%);
  font-size: 1rem;        /* normalised — emoji renders more consistently across browsers */
  line-height: 1;
  pointer-events: none;
  z-index: 1;
  -webkit-font-smoothing: antialiased;
}
/* Dial code — after flag */
.contact__phone-dial-overlay {
  position: absolute;
  left: 2.25rem;    /* pushed right — reliable gap from flag emoji across Safari/Chrome */
  top: 50%;
  transform: translateY(-50%);
  font-family: var(--wp--preset--font-family--body);
  font-weight: 600;
  font-size: 0.8125rem;
  color: var(--wp--preset--color--ink);
  pointer-events: none;
  z-index: 1;
  white-space: nowrap;
  letter-spacing: -0.01em;
}
/* Chevron — tight after dial code */
.contact__phone-chevron {
  position: absolute;
  left: 4.35rem;
  top: 50%;
  transform: translateY(-50%);
  pointer-events: none;
  flex-shrink: 0;
}
/* Transparent select — full tap target over prefix */
.contact__phone-country {
  -webkit-appearance: none;
  appearance: none;
  border: none;
  background: transparent;
  color: transparent;
  cursor: pointer;
  outline: none;
  width: 100%;
  height: 44px;
  min-height: 44px;
  border-radius: 0;
  padding: 0;
}

.contact__phone-input {
  flex: 1;
  min-width: 0;
  border: none;
  background: transparent;
  padding: 0.8125rem 0.9375rem 0.8125rem 0.75rem;
  font-family: var(--wp--preset--font-family--body);
  font-weight: 500;
  font-size: 0.875rem;
  color: var(--wp--preset--color--ink);
  outline: none;
  border-radius: 0;
}
.contact__phone-input::placeholder {
  color: #827571;
}

/* =============================================================
   SELECT
   ============================================================= */
.contact__select-wrap {
  position: relative;
}
.contact__select {
  cursor: pointer;
  padding-right: 2.5rem;
  color: var(--contact-placeholder);
}
.contact__select.has-value {
  color: var(--wp--preset--color--ink);
}
.contact__select-chevron {
  position: absolute;
  right: 0.875rem;
  top: 50%;
  transform: translateY(-50%);
  pointer-events: none;
  flex-shrink: 0;
}

/* =============================================================
   TEXTAREA
   ============================================================= */
.contact__textarea {
  resize: none;
  min-height: 8.5rem;
  font-size: 0.9375rem;
  line-height: 1.5;
  /* Thin scrollbar — Firefox */
  scrollbar-width: thin;
  scrollbar-color: #D7BAAF transparent;
}
/* Thin scrollbar — Chrome/Safari */
.contact__textarea::-webkit-scrollbar {
  width: 4px;
}
.contact__textarea::-webkit-scrollbar-track {
  background: transparent;
}
.contact__textarea::-webkit-scrollbar-thumb {
  background: #D7BAAF;
  border-radius: 0;
}



/* Character counter */
.contact__char-count {
  font-family: var(--wp--preset--font-family--body);
  font-weight: 500;
  font-size: 0.75rem;    /* 12px */
  color: #827571;
  text-align: right;
  margin-top: 0.375rem;
  transition: color var(--wp--custom--motion--dur-fast) ease;
}
.contact__char-count.is-low {
  color: var(--wp--preset--color--coral);
}

/* =============================================================
   SUBMIT BUTTON
   ============================================================= */
.contact__submit-wrap {
  padding-top: 0;
  margin-top: -0.5rem;  /* pulls submit up tighter to message box */
}
.contact__submit {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  gap: 0.5rem;
  font-family: var(--wp--preset--font-family--body);
  font-weight: 700;
  font-size: var(--wp--preset--font-size--sm);
  color: var(--wp--preset--color--white);
  background: var(--wp--preset--gradient--btn-secondary);
  border: none;
  border-radius: 0;
  padding-inline: 1.5rem;
  height: 44px;
  min-height: 44px;
  min-width: 8.5rem;    /* locks width — prevents shrink during loading dots state */
  cursor: pointer;
  letter-spacing: 0.01em;
  transition: background var(--wp--custom--motion--dur-fast) ease,
              transform  var(--wp--custom--motion--dur-fast) ease,
              opacity    var(--wp--custom--motion--dur-fast) ease,
              color      var(--wp--custom--motion--dur-base) ease,
              border     var(--wp--custom--motion--dur-base) ease;
}
.contact__submit:hover:not(:disabled) {
  background: var(--wp--preset--gradient--btn-secondary-hover);
  transform: translateY(-1px);
}
.contact__submit:active:not(:disabled) {
  transform: translateY(0);
}
/* Disabled state — fields not yet complete */
.contact__submit:disabled:not(.is-sent) {
  opacity: 0.38;
  cursor: not-allowed;
}
.contact__submit-arrow {
  flex-shrink: 0;
  will-change: transform;
  transition: none;
}
/* Submit loading + sent states */
.contact__submit-dots {
  display: none;
  align-items: center;
  gap: 4px;
  flex-shrink: 0;
}
.contact__submit-dot {
  display: block;
  width: 5px;
  height: 5px;
  background: #fff;
  border-radius: 0;     /* square bits — matches loader spec */
  animation: submit-pulse 1.2s ease-in-out infinite;
}
.contact__submit-dot:nth-child(2) { animation-delay: 0.2s; }
.contact__submit-dot:nth-child(3) { animation-delay: 0.4s; }
@keyframes submit-pulse {
  0%, 100% { transform: scale(0.6); opacity: 0.6; }
  50%       { transform: scale(1);   opacity: 1; }
}
/* Loading state */
.contact__submit.is-sending .contact__submit-label { display: none; }
.contact__submit.is-sending .contact__submit-arrow { display: none; }
.contact__submit.is-sending .contact__submit-dots  { display: flex; }
/* Sent state */
.contact__submit.is-sent {
  background: var(--wp--preset--color--white);
  border: 0.5px solid #D7BAAF;
  color: var(--wp--preset--color--ink);
  pointer-events: none;
  border-radius: 0;   /* locked — no corner radius */
}
.contact__submit.is-sent .contact__submit-dots  { display: none; }
.contact__submit.is-sent .contact__submit-arrow { display: none; }
.contact__submit.is-sent .contact__submit-label { display: inline; opacity: 1; }

/* =============================================================
   SEND CONFIRMATION — full-screen takeover
   Added 2026-08. QA flagged that the tick on the Send button was the only
   success signal. A second after the button flips to "Sent" this fades up over
   the whole screen, holds, then fades back out to the form, where the spent
   "Sent" button remains as the receipt. Modelled on .payment-success.

   THE FAIL-SAFE DIRECTION IS INVERTED HERE, ON PURPOSE. Everywhere else in this
   theme the rule is "fail visible". An overlay is the opposite case: one that
   fails to APPEAR costs nothing (the Sent button still tells the story), but one
   that fails to LEAVE covers the entire page and traps the visitor. So the
   resting state is comprehensively inert — opacity 0, visibility hidden AND
   pointer-events none — and every one of those has to be actively switched on.
   Dropping the .is-visible class alone fully disarms it, even if the JS teardown
   never removes the element.
   ============================================================= */
.contact__success[hidden] { display: none; }

.contact__success {
  position: fixed;
  inset: 0;
  z-index: 9999;
  display: flex;
  flex-direction: column;
  align-items: center;
  justify-content: center;
  text-align: center;
  padding: 1.5rem;
  background: var(--wp--preset--color--cream);
  opacity: 0;
  visibility: hidden;
  pointer-events: none;
  transition: opacity 0.45s ease, visibility 0s linear 0.45s;
}
.contact__success.is-visible {
  opacity: 1;
  visibility: visible;
  pointer-events: auto;
  transition: opacity 0.45s ease, visibility 0s;
}

/* Inner choreography mirrors .payment-success: badge springs, then the title
   lifts, then the sub. Each is gated on .is-visible so it replays cleanly.
   These are decoration only — if they never run, the overlay is simply a cream
   screen for its ~2s hold and then leaves, which is recoverable. The overlay's
   own dismissal never depends on them. */
/* Badge, type scale and stagger timings below are a deliberate 1:1 mirror of
   .payment-success (payment.css) so the two confirmations are the same screen in
   two places. Same asset too: /wp-content/uploads/quiz-tick.webp, which is the
   tick the payment portal and the blog newsletter badge both use.
   The 50px top / -20px title pull is payment's own pairing — it sits the badge
   low and tucks the headline under it. Carried across on purpose, not a stray. */
.contact__success-badge {
  width: 100px;
  height: 100px;
  margin-top: 50px;
  margin-bottom: 0.75rem;
  transform: scale(0.6) translateY(10px);
  opacity: 0;
  transition: transform 0.55s cubic-bezier(0.34, 1.56, 0.64, 1) 0.2s,
              opacity 0.4s ease 0.2s;
}
.contact__success.is-visible .contact__success-badge {
  transform: scale(1) translateY(0);
  opacity: 1;
  /* Own keyframe name, NOT the shared `badge-float`. Three @keyframes
     badge-float already exist (blog.css, gateway.css, payment.css) and keyframes
     are global, so the last file loaded wins for all of them. Don't add a fourth;
     these values are a copy of payment's so the motion still matches. */
  animation: contact-badge-float 3.5s cubic-bezier(0.65, 0, 0.35, 1) infinite 0.75s;
}
.contact__success-badge img {
  width: 100%;
  height: 100%;
  object-fit: contain;
}

@keyframes contact-badge-float {
  0%   { transform: translateY(0px)   rotate(-2deg); }
  25%  { transform: translateY(-7px)  rotate(0deg);  }
  50%  { transform: translateY(-12px) rotate(2deg);  }
  75%  { transform: translateY(-6px)  rotate(0deg);  }
  100% { transform: translateY(0px)   rotate(-2deg); }
}

.contact__success-title {
  font-family: var(--wp--preset--font-family--display);
  font-weight: 400;
  font-size: clamp(1.5rem, 3.5vw, 2rem);
  line-height: 1.05;
  letter-spacing: -0.05em;
  color: var(--wp--preset--color--ink);
  margin-top: -20px;
  margin-bottom: 0.875rem;
  opacity: 0;
  transform: translateY(16px);
  transition: opacity 0.5s ease 0.35s,
              transform 0.5s cubic-bezier(0.22, 1, 0.36, 1) 0.35s;
}
.contact__success.is-visible .contact__success-title {
  opacity: 1;
  transform: translateY(0);
}
.contact__success-accent { color: var(--wp--preset--color--coral); }

.contact__success-sub {
  font-family: var(--wp--preset--font-family--body);
  font-weight: 500;
  font-size: var(--wp--preset--font-size--base);
  line-height: 1.5;
  color: #473531;
  margin: 0;
  max-width: 240px;
  opacity: 0;
  transform: translateY(12px);
  transition: opacity 0.5s ease 0.5s,
              transform 0.5s cubic-bezier(0.22, 1, 0.36, 1) 0.5s;
}
.contact__success.is-visible .contact__success-sub {
  opacity: 1;
  transform: translateY(0);
}

/* =============================================================
   SPENT FORM
   Once the confirmation overlay has been seen, the form is done: the submit
   button is already inert (.is-sent carries pointer-events:none) so the fields
   are dimmed to match rather than sitting there looking live. contact.js also
   sets `disabled` on each control, which takes them out of the tab order — the
   dim alone would leave keyboard users tabbing through a dead form.

   The submit button is deliberately NOT dimmed: it is the receipt, and
   `.contact__submit:disabled:not(.is-sent)` already excludes it from the greyed
   disabled treatment. Only .contact__row is touched, and the button lives
   outside those in .contact__submit-wrap.
   ============================================================= */
.contact__row { transition: opacity 0.5s ease; }

.contact__form.is-spent .contact__row {
  opacity: 0.5;
  pointer-events: none;
}

/* Browsers (Safari especially) grey disabled control text themselves via
   -webkit-text-fill-color rather than `color`, which would stack on top of the
   row dim and leave the visitor's own words unreadable. Defer to whatever colour
   the cascade already computed, so the placeholder-vs-filled distinction that
   the .has-value logic sets up survives being disabled. */
.contact__form.is-spent .contact__row input,
.contact__form.is-spent .contact__row select,
.contact__form.is-spent .contact__row textarea {
  -webkit-text-fill-color: currentColor;
  opacity: 1;
  cursor: default;
}

/* Reduced motion: everything snaps to its end state, nothing animates.
   NB the transitions and the badge float are declared on COMPOUND selectors
   (`.contact__success.is-visible`, 0,2,0 / `.contact__success.is-visible
   .contact__success-badge`, 0,3,0). A media query adds no specificity, so a
   plain `.contact__success` override here loses and the fade plays anyway —
   which is exactly what verification caught. Match the compound form. */
@media (prefers-reduced-motion: reduce) {
  .contact__row { transition: none; }
  .contact__success,
  .contact__success.is-visible { transition: none; }
  .contact__success-badge,
  .contact__success-title,
  .contact__success-sub,
  .contact__success.is-visible .contact__success-badge,
  .contact__success.is-visible .contact__success-title,
  .contact__success.is-visible .contact__success-sub { transition: none; animation: none; }
}

/* =============================================================
   SCROLL REVEAL
   ============================================================= */
.sr-reveal {
  opacity: 0;
  transform: translateY(40px);
  transition:
    opacity   0.65s var(--wp--custom--motion--ease-out),
    transform 0.65s var(--wp--custom--motion--ease-out);
  will-change: transform, opacity;
}
.sr-reveal.is-visible {
  opacity: 1;
  transform: translateY(0);
}
/* The headline is the page's LCP, so it RISES BUT DOESN'T FADE (Max, 2026-10-12; Liam's
   rule, hero.css: Chrome doesn't count an element painted while it sits at opacity 0, so
   a fade-in holds LCP back until the reveal runs). Same 40px lift and timing as the rest.
   Covers /contact/ and /register-my-pub/ (both use this headline). */
.contact__headline.sr-reveal {
  opacity: 1;
  transition: transform 0.65s var(--wp--custom--motion--ease-out);
  will-change: transform;
}
@media (prefers-reduced-motion: reduce) {
  .sr-reveal,
  .contact__headline.sr-reveal {
    opacity: 1;
    transform: none;
    transition: none;
  }
  .contact__finger { animation: none; }
}

/* =============================================================
   PAGE LOADER
   ============================================================= */

/* =============================================================
   FOCUS
   ============================================================= */

/* =============================================================
   SITE HEADER
   ============================================================= */

/* =============================================================
   CONTACT SECTION
   ============================================================= */
.contact {
  padding-inline: var(--wp--custom--layout--gutter);
  padding-block: 3.5rem 6rem;
}
.contact__inner {
  max-width: 1100px;
  margin-inline: auto;
  display: grid;
  grid-template-columns: 420px 1fr;
  gap: 80px;
  align-items: start;
}
.contact__left {
  display: flex;
  flex-direction: column;
  gap: 2.5rem;
}

/* =============================================================
   TABLET — ≤1023px
   ============================================================= */
@media (max-width: 1023px) {
  .contact {
    padding-block: 4rem 5rem;
  }
  .contact__inner {
    grid-template-columns: 1fr;
    gap: 3rem;
    max-width: 600px;
  }
  /* Tablet headline matches desktop — 4.5rem */
  .contact__finger { width: 88px; }
  .contact__lead   { max-width: 100%; }
}

/* =============================================================
   MOBILE — ≤640px
   ============================================================= */
@media (max-width: 640px) {
  .contact {
    padding-block: 2.5rem 3.5rem;
    padding-inline: clamp(1rem, 5vw, 1.5rem);
  }
  .contact__inner {
    gap: 1.25rem;   /* tighter between left column and card */
    max-width: 100%;
    width: 100%;
  }
  .contact__headline {
    font-size: clamp(2.1rem, 11.5vw, 2.75rem);
    line-height: 0.8421;
    letter-spacing: -0.10763em;
  }
  .contact__finger { width: 64px; }
  .contact__left  { gap: 1.25rem; }   /* was 2.5rem desktop */
  .contact__back  { order: -1; margin-top: -0.5rem; margin-bottom: 0.5rem; }  /* lifted, gap below to headline */
  .contact__lead   { font-size: 1rem; width: min(240px, 88vw); }
  .contact__social-label { font-size: 13px; }
  .contact__trust { margin-top: 0.5rem; }   /* extra gap above trust strip */
  .contact__card  { margin-top: 1.25rem; }   /* increased gap above input card */
  .contact__card   { padding: 1.5rem 1.25rem 1.25rem; margin-inline: 0; box-sizing: border-box; width: 100%; }
  /* Prevent iOS Safari auto-zoom — must be ≥16px on all inputs */
  .contact__input,
  .contact__select,
  .contact__textarea,
  .contact__phone-input,
  .contact__phone-country { font-size: 16px; }
  .contact__row    { grid-template-columns: 1fr; gap: 0.875rem; }
  .contact__field--full { grid-column: auto; }
  .contact__submit { width: 100%; }
}

/* Honeypot — off-screen for bots to find and people never to see. Not
   display:none, which some bots skip; kept focusable-adjacent but out of the
   tab order via tabindex="-1" on the input itself. */
.contact__hp {
  position: absolute;
  left: -9999px;
  width: 1px;
  height: 1px;
  overflow: hidden;
}

.contact__error {
  font-family: var(--wp--preset--font-family--body);
  font-weight: 500;
  font-size: 0.875rem;
  line-height: 1.4;
  color: #C4271A;
  margin-top: 0.875rem;
  max-width: 34em;
}

/* ── White lift (2026-09-16, Max: "roll the transition into white across all
   cells") ── every card lifts from #FFFAF5 to pure white: on hover for pointer
   devices, and while it is mostly on screen on touch devices (.is-focus from
   the global card-focus.js driver, 50% threshold). */
@media (hover: hover) { .contact__card:hover { background: #FFFFFF; } }
.contact__card.is-focus { background: #FFFFFF; }

/* =============================================================
   REGISTER MY PUB (patterns/register-pub.php, Max 2026-10-01)
   The contact page's spin-off for managed-pub landlords. Everything
   above still applies; these are the two additions to the left
   column: the group badge (per-group links only) and the three
   "what happens next" steps that replace the trust ticker.
   ============================================================= */
.reg__group[hidden] { display: none; }
.reg__group {
  display: inline-flex;
  align-items: center;
  gap: 1rem;
  align-self: flex-start;
  padding: 0.75rem 1.125rem;
  background: #FFFAF5;
  border: 1px solid #FFFFFF;   /* card edge system */
}
.reg__group-label {
  font-family: var(--wp--preset--font-family--body);
  font-weight: 600;
  font-size: 0.8125rem;
  color: var(--wp--preset--color--ink);
  white-space: nowrap;
}
.reg__group-logo { display: flex; align-items: center; }
.reg__group-logo svg,
.reg__group-logo img {
  display: block;
  width: auto;
  height: 28px;
  max-width: 150px;
}

.reg__steps {
  list-style: none;
  margin: 0;
  padding: 0;
  display: flex;
  flex-direction: column;
  gap: 1rem;
  max-width: 360px;
}
.reg__step {
  display: grid;
  grid-template-columns: 2.25rem 1fr;
  align-items: baseline;
}
.reg__step-num {
  font-family: var(--wp--preset--font-family--pixel);
  font-size: 1rem;
  letter-spacing: 0.06em;
  color: var(--wp--preset--color--coral);
}
.reg__step-copy {
  display: flex;
  flex-direction: column;
  gap: 0.125rem;
  font-family: var(--wp--preset--font-family--body);
  font-size: 0.8125rem;   /* 13px (Max: smaller under the bold titles) */
  line-height: 1.4;
  color: var(--contact-label-color);
}
.reg__step-copy strong {
  font-weight: 700;   /* bold (Max); Roobert has no 600, it would snap here anyway */
  font-size: 1rem;
  color: var(--wp--preset--color--ink);
}

/* The register lead runs a little longer than the contact one. */
.contact--register .contact__lead { width: 360px; }

@media (max-width: 640px) {
  .contact--register .contact__lead { width: auto; max-width: 300px; text-wrap: pretty; }   /* a touch narrower on phones (Max, 2026-10-04); pretty = no lone group name on the last line */
  .reg__group { padding: 0.625rem 0.875rem; gap: 0.75rem; }
  .reg__group-logo svg,
  .reg__group-logo img { height: 24px; }
  .reg__steps { gap: 0.75rem; margin-top: 0.25rem; }
}

/* assets/css/components/nav.css */
/* ==================================================================
   Nav — kwizzbit/site-header + kwizzbit/mobile-menu (shared chrome)
   Faithful slice of /HTML/nav.html. Tokens are canonical wp tokens; reset, body,
   sr-only, container, font-face stripped (global). Dropdowns, hamburger, mobile overlay.
   ================================================================== */

    /* ==========================================================
       SITE HEADER (kwizzbit/site-header) — minimal version
       Full spec already documented in COMPONENTS.md §1.
       Dropdown JS omitted here — chevrons shown but inert.

       LAYOUT: At desktop the inner uses a 3-col grid (1fr auto 1fr)
       so the nav is always geometrically centred regardless of how
       wide the logo or actions columns are. padding-inline is fixed
       at 36px at desktop so logo and CTA sit exactly 36px from
       their respective page edges, as requested.
       ========================================================== */
    /* Standard top nav, links centred via the 1fr / auto / 1fr grid below.
       The Get started button floats fixed top-right at all times (relume-style)
       — a great always-visible conversion CTA. Its footprint is reserved in the
       actions group so Login keeps its place. NOTE: this only stays centred
       because no component leaks a `display` onto .site-header (the contact
       pattern used to — fixed at source). */
    .site-header {
      background: var(--wp--preset--color--cream);
      min-height: 5.5rem;
      position: relative;
    }

    @media (min-width: 1024px) {
      .site-header__actions .btn--secondary {
        position: fixed;      /* floats over content + stays visible on scroll */
        /* Clear the announce bar (its measured height, published by nav.js)
           then centre in the 5.5rem header below it.
           The bar is PINNED to the viewport top at all times now
           (announce-bar.css), so this is the button's permanent home —
           the old .kwb-scrolled rise to 1.5rem is gone: it would park
           the button on top of the strip.
           FALLBACK MUST EQUAL THE STRIP'S REAL HEIGHT. nav.js is deferred,
           so the first paint uses the fallback and the measured value lands
           a frame or two later; with the `top` transition below, any gap
           between the two plays as a visible slide on EVERY page arrival.
           The old 2rem fallback sat 6px short of the 38px strip, so the
           button eased 6px down after each navigation. 2.375rem = 38px,
           verified identical on every page at 1024/1200/1440/1920. If the
           strip's copy or padding ever changes its height, update this. */
        top: calc(var(--kwb-announce-h, 2.375rem) + 1.5rem);
        right: 36px;          /* matches the nav's 36px desktop gutter */
        z-index: 500;         /* floats over content; below cookie modal + loader */
        transition: top 0.35s var(--wp--custom--motion--ease-out),
                    background 0.2s ease,
                    transform 0.2s ease;
        /* FOOTPRINT LOCK — the button is pinned by its right edge, so any
           change to its padding/gap grows it leftwards and it visibly
           differs page to page. Segment stylesheets load conditionally
           (inc/assets.php) and several once redeclared a bare `.btn`
           (faq.css: 24px padding, offer.css: 8px gap), so Pricing's button
           came out 14px wider than the homepage's. Those are now scoped to
           their segments, and this restates button.css's own spec at
           higher specificity so nothing loaded after it can shift the
           header CTA again. Sizes here MUST match .btn / .btn--secondary
           in button.css. */
        padding: 0 1.0625rem;
        gap: 7px;
        font-size: var(--wp--preset--font-size--sm);
        min-height: 44px;
        height: 42px;
      }
      @media (prefers-reduced-motion: reduce) {
        .site-header__actions .btn--secondary { transition: none; }
      }
      /* Belt and braces for the fallback above: nav.js publishes the strip
         height inside applyInstant() (html.kwb-nav-instant is set for that
         one synchronous tick), so if the measured value ever differs from
         the fallback the correction is applied in place rather than eased.
         Live changes (a resize that rewraps the strip) still transition. */
      html.kwb-nav-instant .site-header__actions .btn--secondary { transition: none; }
      /* Reserve the button's footprint (~140px) + a tight 6px gap.
         padding-right is the only lever here — gap: has no effect since
         the fixed button is out of the flex flow. */
      .site-header__actions {
        padding-right: 148px;
      }
    }

    .site-header__inner {
      display: flex;
      align-items: center;
      justify-content: space-between;
      min-height: 5.5rem;
      /* Mobile: fluid gutter, no max-width — full viewport width always */
      padding-inline: var(--wp--custom--layout--gutter);
    }

    @media (min-width: 1024px) {
      .site-header__inner {
        display: grid;
        grid-template-columns: 1fr auto 1fr;
        /* Hard 36px against the viewport at ALL screen sizes, no cap */
        padding-inline: 36px;
      }
    }

    .site-logo {
      color: var(--wp--preset--color--coral);
      display: inline-flex;
      justify-self: start;
      /* anchor for the absolutely-positioned version tag */
      position: relative;
      transform-origin: left center;
      transition: transform var(--wp--custom--motion--dur-base)
                  var(--wp--custom--motion--ease-out);
    }
    .site-logo:hover { transform: rotate(-1deg); }

    /* ── Hover easter egg: "3.0" version tag ───────────────────────────
       Sits just past the wordmark's right edge as a small superscript tag.
       Tucked behind the edge (translateX) + invisible at rest; on hover it
       glides out and fades in — a quiet wink, no layout shift (absolute).
       Coral by default; auto-whitened on the About page because it lives
       inside .site-logo, which gets brightness(0) invert(1) there. */
    .site-logo__ver {
      position: absolute;
      left: 100%;
      top: -1px;                 /* lift it superscript-style toward the cap line */
      margin-left: 3px;
      font-family: var(--wp--preset--font-family--body);
      font-weight: 700;
      font-size: 11px;
      line-height: 1;
      letter-spacing: 0.01em;
      color: var(--wp--preset--color--coral);
      white-space: nowrap;
      pointer-events: none;      /* never intercepts the logo's click target */
      opacity: 0;
      transform: translateX(-7px);   /* tucked back under the right edge */
      transition: opacity 0.18s ease,
                  transform 0.28s cubic-bezier(0.22, 1, 0.36, 1);
    }
    .site-logo:hover .site-logo__ver,
    .site-logo:focus-visible .site-logo__ver {
      opacity: 1;
      transform: translateX(0);
    }

    @media (prefers-reduced-motion: reduce) {
      .site-logo__ver { transform: none; transition: opacity 0.18s ease; }
      .site-logo:hover .site-logo__ver,
      .site-logo:focus-visible .site-logo__ver { transform: none; }
    }

    .primary-nav {
      display: none;
    }
    @media (min-width: 1024px) {
      .primary-nav { display: block; }
    }

    .primary-nav__list {
      display: flex;
      /* 40px between each nav item */
      gap: 30px;
      list-style: none;
      margin: 0;
      padding: 0;
    }

    .primary-nav__link {
      color: var(--wp--custom--color--nav-ink);
      font-family: var(--wp--preset--font-family--body);
      font-weight: 500;
      font-size: 15px;
      /* 42px height for the hover highlight, matching button height */
      height: 42px;
      padding: 0 0.625rem;
      display: inline-flex;
      align-items: center;
      gap: 6px;
      border-radius: 0;
      transition:
        background-color var(--wp--custom--motion--dur-fast)
          var(--wp--custom--motion--ease-out);
    }
    .primary-nav__link:hover {
      /* Text colour unchanged on hover */
      color: var(--wp--custom--color--nav-ink);
      background-color: #EEDED0;
    }
    .primary-nav__link--active { font-weight: 700; }
    /* Bold + persistently highlight the top-level link (e.g. "Product") when
       the current page lives under it — class set by nav.js active-state logic. */
    .primary-nav__item--active > .primary-nav__link {
      font-weight: 700;
      background-color: #EEDED0;
    }
    .primary-nav__chevron {
      width: 8px;
      height: 5px;
      flex-shrink: 0;
      /* Nudge down slightly to optically align with text baseline */
      vertical-align: middle;
      position: relative;
      top: 1px;
      /* Animate the flip (see .primary-nav__item--open below) rather than snap */
      transition: transform 0.25s ease;
    }

    @media (prefers-reduced-motion: reduce) {
      .primary-nav__chevron { transition: none; }
    }

    .site-header__actions {
      display: flex;
      align-items: center;
      /* Tight gap — Login sits close to Get started */
      gap: 6px;
      justify-self: end;
    }

    .site-header__login {
      color: var(--wp--custom--color--nav-ink);
      font-weight: 500;
      font-size: 0.9375rem;
      display: none; /* shown at desktop */
      text-decoration: none;
      /* Match the nav link highlight: 42px height, same horizontal padding */
      height: 42px;
      padding: 0 0.625rem;
      align-items: center;
      transition: background-color var(--wp--custom--motion--dur-base) var(--wp--custom--motion--ease-out);
    }
    .site-header__login:hover {
      background-color: #EEDED0;
    }
    @media (min-width: 1024px) {
      .site-header__login { display: inline-flex; }
    }

    /* Mobile hamburger — visible < 1024px.
       Drawer overlay is a separate section (not yet built). */
    .hamburger {
      display: inline-flex;
      align-items: center;
      justify-content: center;
      flex-direction: column;
      gap: 5px;
      width: 44px; height: 44px;
      background: transparent;
      border: none;
      color: var(--wp--custom--color--nav-ink);
      cursor: pointer;
    }
    @media (min-width: 1024px) {
      .hamburger { display: none; }
    }
    /* Two-bar icon that morphs to an X.
       CSS reads aria-expanded on the <button> — no class toggling needed in JS. */
    .hamburger__bar {
      display: block;
      width: 17px;
      height: 3px;
      background: currentColor;
      border-radius: 0;
      transform-origin: center center;
      transition:
        transform 0.28s cubic-bezier(0.22, 1, 0.36, 1),
        opacity   0.18s ease;
    }
    /* While the menu is OPEN, the burger must sit above the menu's
       full-screen backdrop (z 900) even when docked in the header —
       otherwise, at the top of the page, taps on the visible X land
       on the backdrop instead of the button. The backdrop's own
       close-on-tap makes that mostly indistinguishable, but it
       bypasses the button's guarded toggle path, and rapid tap
       sequences get messier for it. The floating state already pins
       at z 950; this covers the docked state. (On modes/about the
       header's scoped z-index:30 caps this within its stacking
       context — there the backdrop fallback still handles the tap,
       unchanged.) */
    .hamburger[aria-expanded="true"] {
      position: relative;
      z-index: 950;
    }

    /* gap: 5px + bar height 3px → center-to-center = 8px → translateY(4px) */
    .hamburger[aria-expanded="true"] .hamburger__bar:first-child {
      transform: translateY(4px) rotate(45deg);
    }
    .hamburger[aria-expanded="true"] .hamburger__bar:last-child {
      transform: translateY(-4px) rotate(-45deg);
    }
    @media (prefers-reduced-motion: reduce) {
      .hamburger__bar { transition: none; }
    }

    /* ==========================================================
       NAV DROPDOWNS
       White panel, 0px radius, glass effect with warm orange glow.
       Positioned below the nav, left-aligned to the trigger.
       ========================================================== */
    .primary-nav__item {
      position: relative;
    }

    .primary-nav__dropdown {
      display: none;
      position: absolute;
      /* 8px gap from trigger — bridged by ::before pseudo so cursor
         doesn't escape the <li> when moving from trigger to panel */
      top: calc(100% + 8px);
      left: 0;
      background: rgba(255, 255, 255, 0.96);
      backdrop-filter: blur(100px);
      -webkit-backdrop-filter: blur(100px);
      box-shadow:
        2px 2px 0px rgba(253, 106, 97, 0.20),
        0px 20px 50px rgba(255, 54, 35, 0.20);
      border-radius: 0;
      z-index: 100;
      white-space: nowrap;
    }

    /* Product + Learn: 168px wide, padding to hit 159px tall across 4 items */
    .primary-nav__dropdown--sm {
      width: 168px;
      padding: 10px 0;
    }

    /* Hosts dropdown is wider — two columns */
    .primary-nav__dropdown--wide {
      /* Fixed width — prevents Safari from crushing the columns.
         width:max-content lets the grid determine the panel size,
         capped so it doesn't run off screen. */
      width: max-content;
      max-width: 420px;
      display: none;
      padding: 10px 0;
    }

    .primary-nav__item--open .primary-nav__dropdown {
      display: block;
    }

    /* Invisible bridge fills the 8px gap so the cursor stays within
       the <li> as it moves from the nav link down to the panel */
    .primary-nav__dropdown::before {
      content: '';
      position: absolute;
      top: -8px;
      left: 0;
      right: 0;
      height: 8px;
    }

    .primary-nav__dropdown-grid {
      display: grid;
      /* Fixed column widths — no fluid fractions that can collapse in Safari */
      grid-template-columns: 190px 190px;
      /* row-gap draws the 1px line between rows; column-gap stays 0. Using the
         grid gap (rather than per-li margin-top) keeps both columns on the same
         row baseline so their highlights align perfectly. */
      gap: 1px 0;
      padding-right: 10px;
    }

    .primary-nav__dropdown-link {
      display: flex;
      align-items: center;
      gap: 12px;
      /* 42px height for hover highlight */
      height: 42px;
      padding: 0 18px;
      color: var(--wp--custom--color--nav-ink);
      font-family: 'Roobert', system-ui, -apple-system, sans-serif;
      font-weight: 500;
      font-size: 14px;
      line-height: 1;
      text-decoration: none;
      transition:
        color var(--wp--custom--motion--dur-fast) var(--wp--custom--motion--ease-out),
        background-color var(--wp--custom--motion--dur-fast) var(--wp--custom--motion--ease-out);
    }

    .primary-nav__dropdown-link:hover {
      color: var(--wp--custom--color--nav-ink);
      background-color: #F2E8DF;
    }

    /* Current sub-page — persistent highlight in the open dropdown.
       Class set by nav.js when the page matches this link. */
    .primary-nav__dropdown-link--active {
      background-color: #F2E8DF;
    }

    /* In the wide (Hosts) dropdown, bleed the highlight through the grid's
       padding-right so it stretches flush to the modal edge.
       SCOPED to the right-hand column only (nth-child(even) in row-major
       flow): if the left column also bled by -10px it would widen into the
       right column's track, making the right column's highlight look like it
       borrows space from the left. Left-column items stay inside their track.
       Apply to both hover AND active so the width is always identical. */
    .primary-nav__dropdown--wide .primary-nav__dropdown-grid li:nth-child(even) .primary-nav__dropdown-link:hover,
    .primary-nav__dropdown--wide .primary-nav__dropdown-grid li:nth-child(even) .primary-nav__dropdown-link--active {
      margin-right: -10px;
      padding-right: 28px;
    }

    /* 17px vertical space between items via margin-top on li siblings */
    .primary-nav__dropdown ul,
    .primary-nav__dropdown {
      list-style: none;
      padding-left: 0;
      margin: 0;
    }
    .primary-nav__dropdown li + li {
      margin-top: 1px;
    }
    /* …but in the wide 2-column grid, row spacing comes from the grid's row-gap.
       Zero the margin so the first right-column item isn't pushed 1px below the
       first left-column item (which would misalign the two columns' highlights). */
    .primary-nav__dropdown--wide .primary-nav__dropdown-grid li {
      margin-top: 0;
    }

    /* Plain marks, no tile (a boxed version was tried and reverted the
       same day, 2026-09-14). 20px on desktop; 24px in the mobile menu. */
    .primary-nav__dropdown-icon {
      width: 20px;
      height: 20px;
      flex-shrink: 0;
    }

    /* Chevron rotates when dropdown is open */
    .primary-nav__item--open .primary-nav__chevron {
      transform: rotate(180deg) translateY(-1px);
    }

    /* ==========================================================
       TABLET/MOBILE (<1024px) — nav-related rules only
       ========================================================== */
    @media (max-width: 1023px) {
      /* Hide Get started button in nav at tablet/mobile — hamburger takes over */
      .site-header__actions .btn--secondary {
        display: none;
      }
    }

    /* ==========================================================
       MOBILE (<=640px) — nav-related rules only
       ========================================================== */
    @media (max-width: 640px) {
      .site-header {
        min-height: 3.5rem;
      }
      .site-header__inner {
        padding-inline: 4vw;
      }
    }


    /* ==========================================================
       MOBILE / TABLET MENU OVERLAY — full-screen bleed
       Only active < 1024px. Since 2026-09-14 the menu IS the screen
       (Max's call, Relume's mobile nav as the reference): an
       edge-to-edge white panel with its own logo + close row, the
       accordion sections below, Get started + Login pinned to the
       bottom. It covers the announce strip, the header and the page.

       What this replaced, so nobody resurrects it by accident: a card
       that hung 10px in from the edges below the header, with the page
       visible + scrollable behind it, a tap-outside-to-close backdrop,
       a "focus dim" cast as the card's own shadow (a workaround for an
       iOS Safari seam under full-screen scrims), and positioning that
       followed the floating burger through its three scroll beats.
       All of that is gone: the page is scroll-locked (html.kwb-menu-open,
       set by nav.js), the burger hides while the menu is open and the
       overlay's own X does the closing, and the panel's position is a
       constant inset:0.
       ========================================================== */
    @media (max-width: 1023px) {

      /* The overlay itself carries the backdrop: a glass top half that
         settles into plain white (Max 2026-09-14). The page behind shows
         through the blur near the top, is gone by the middle. Fades in
         as a whole (opacity here); the panel adds its own short rise. */
      .mobile-menu {
        display: none;
        position: fixed;
        inset: 0;
        /* Above the cookie modal (200) and the page; the pinned promo
           strip (800) is lifted ABOVE this while the menu is open, see
           the html.kwb-menu-open block further down. */
        z-index: 900;
        /* Second pass (Max: "can't really notice it"): far less white
           at the top and a lighter blur, so the page's shapes and colour
           actually read through the top third before the white takes
           over past halfway. */
        background: linear-gradient(
          180deg,
          rgba(255, 255, 255, 0.38) 0%,
          rgba(255, 255, 255, 0.62) 28%,
          rgba(255, 255, 255, 0.90) 48%,
          #FFFFFF 62%
        );
        backdrop-filter: blur(14px) saturate(170%);
        -webkit-backdrop-filter: blur(14px) saturate(170%);
        opacity: 0;
        transition: opacity 240ms ease;
        /* Rows and the logo row share ONE gutter, the site header's own,
           so the overlay's logo lands exactly where the header's logo was
           and the list text lines up beneath it. Mirrors .site-header__inner:
           layout gutter, 4vw at <=640px. */
        --mm-gutter: var(--wp--custom--layout--gutter);
        /* The cream highlight (current page / tap / hover on the rows) as
           a translucent tint rather than the solid #F2E8DF: 16% of this
           warm brown over white resolves to that exact cream; taken down
           to 12% at Max's request so it sits lighter over the glass and
           on the white alike. Same idea as the grain-page header
           highlight further down. */
        --mm-highlight: rgba(174, 111, 55, 0.12);
      }
      @media (max-width: 640px) {
        .mobile-menu { --mm-gutter: 4vw; }
      }
      .mobile-menu.is-open {
        display: block;
      }
      .mobile-menu.is-visible {
        opacity: 1;
      }

      /* Scroll lock. The page under the overlay must not move when a
         finger drags on the menu. overflow:hidden goes on the ROOT ONLY:
         the root's overflow propagates to the viewport, so the document
         stops scrolling with its position preserved (the page is exactly
         where it was on close) and the viewport is still the scroll
         container the pinned promo strip sticks to. It must NOT also go
         on body: that makes body its own scroll container, and the strip
         then sticks to body's (unscrolled) box, i.e. it vanishes off the
         top the moment the menu opens (seen 2026-09-14). iOS touch
         scrolling is stopped by touch-action:none on body instead; the
         panel re-enables vertical panning for itself (it is a scroll
         container, so the touch-action chain stops there) and is its own
         scroll container with overscroll-behavior:contain, so a long
         expanded section scrolls INSIDE the menu and never chains out. */
      html.kwb-menu-open {
        overflow: hidden;
      }
      html.kwb-menu-open body {
        touch-action: none;
      }
      /* iOS Safari paints the strip behind the status bar from the
         document's own background, not from what's rendered under it,
         so with the overlay open that strip stayed cream (Max, on
         phone). The root goes white for the menu's lifetime; nav.js
         swaps the theme-color meta to white at the same time, the
         other input Safari reads for that surface. */
      html.kwb-menu-open,
      html.kwb-menu-open body {
        background: #FFFFFF;
      }

      /* The list panel: everything BELOW the logo row, down to the
         bottom edge. It is the scroll container, and it starts under the
         logo row rather than behind it, so nothing can ever scroll up
         past the wordmark and the burger (it did, when the panel ran
         full-height under a white row: on the glass there is no solid
         row to hide behind). The top edge is feathered with a mask so
         rows leaving the panel dissolve instead of being cut. */
      .mobile-menu__panel {
        position: absolute;
        left: 0;
        right: 0;
        top: calc(var(--mm-row-top, var(--kwb-announce-h, 0px)) + 5.5rem);
        bottom: 0;
        overflow-y: auto;
        overscroll-behavior: contain;
        touch-action: pan-y;
        -webkit-overflow-scrolling: touch;
        background: transparent;
        display: flex;
        flex-direction: column;
        -webkit-mask-image: linear-gradient(to bottom, transparent, #000 24px);
        mask-image: linear-gradient(to bottom, transparent, #000 24px);
        /* A short rise in; reverse out. */
        transform: translateY(10px);
        transition: transform 280ms cubic-bezier(0.22, 1, 0.36, 1);
      }
      .mobile-menu.is-visible .mobile-menu__panel {
        transform: translateY(0);
      }
      @media (prefers-reduced-motion: reduce) {
        .mobile-menu__panel { transform: none; transition: none; }
      }

      /* Logo row: absolute inside the fixed .mobile-menu (which has no
         transform, unlike the panel), so it is viewport-anchored and does
         NOT scroll with the list. --mm-row-top is set by nav.js at open
         time from the burger's live position (row centred on the burger,
         5.5rem tall like the header's own row): at the top of a page that
         is exactly the header row, so the wordmark lands on the header's
         wordmark to the pixel; scrolled, it lines up with the floating
         burger. Transparent: the glass shows through it. */
      .mobile-menu__top {
        position: absolute;
        left: 0;
        right: 0;
        top: var(--mm-row-top, var(--kwb-announce-h, 0px));
        height: 5.5rem;
        display: flex;
        align-items: center;
        padding-inline: var(--mm-gutter);
      }
      .mobile-menu__logo {
        display: inline-flex;
        color: var(--wp--preset--color--coral);
        line-height: 0;
      }
      .mobile-menu__logo svg { display: block; }

      /* flex:1 so the actions block is pushed to the bottom of the
         screen when the list is short; sticky (below) keeps it there
         when an expanded section makes the list longer than the screen. */
      .mobile-menu__nav {
        flex: 1;
        padding-top: 12px;     /* first row's text starts past the 24px feather above */
        padding-bottom: 16px;
      }

      /* No dividers between sections */
      .mobile-menu__section {
        /* no border */
      }

      /* Top-level nav items — one 48px tap row each (2026-09-14, Max).
         Was 15px text in a 35px row, the smallest thing on the panel and
         under the 44px touch minimum. 18px / 48px puts every top-level
         item at a confident menu size (Relume's mobile nav was the
         reference: ~20px in 44px rows) while staying a step below the
         h-scale so the chevron sections still read as navigation, not
         headings. line-height 1 + 15px top/bottom = 48px exactly. */
      .mobile-menu__trigger {
        display: flex;
        align-items: center;
        justify-content: space-between;
        width: 100%;
        min-height: 48px;
        padding: 14px var(--mm-gutter);   /* 20 + 28 = the 48px row */
        background: none;
        border: none;
        font-family: var(--wp--preset--font-family--body);
        font-weight: 500;      /* Medium (was SemiBold; at 18px the extra weight read heavy, Max 2026-09-14) */
        /* One notch up from Medium without a SemiBold licence: a hairline stroke in the
           text colour fattens every stem by ~0.3px. Sits between Medium and Bold (Max 2026-09-16). */
        -webkit-text-stroke: 0.3px currentColor;
        font-size: 1.25rem;    /* 20px (18 -> 20 after Max's first phone check) */
        color: var(--wp--preset--color--ink);
        cursor: pointer;
        text-align: left;
        text-decoration: none;
        line-height: 1;
        transition: background-color 140ms ease;
      }
      /* Brief tap-feedback on the section title — clears instantly, not persistent */
      .mobile-menu__trigger:active {
        background-color: var(--mm-highlight);
        color: var(--wp--preset--color--coral);
      }
      /* Pricing / About are plain page links, not accordion toggles — they get coral
         text on tap (same as sublinks) but no background strip, since there's no
         sub-row beneath them to visually "open". Only sublinks inside accordion
         sections should show the full highlight treatment. */
      .mobile-menu__trigger--plain:active {
        background-color: transparent;
      }

      /* Sections sit on a uniform 48px rhythm now — the old extra
         section-to-section top padding (20px, 16px on the first) is gone;
         the 15px row padding already gives 30px between neighbouring
         titles, more than the ~20px it used to add. */

      .mobile-menu__chevron {
        flex-shrink: 0;
        /* Centred under the X: the burger is a 44px box flush to the
           gutter with its 17px bars centred, so its centre sits 22px in
           from the gutter; this 12px chevron's centre lands there with
           16px of margin (16 + 6 = 22). */
        margin-right: 16px;
        transition: transform 260ms cubic-bezier(0.22, 1, 0.36, 1);
      }

      .mobile-menu__section--open > .mobile-menu__trigger .mobile-menu__chevron {
        transform: rotate(180deg);
      }

      .mobile-menu__submenu {
        list-style: none;
        padding: 0;
        margin: 0;
        overflow: hidden;
        max-height: 0;
        transition: max-height 320ms cubic-bezier(0.22, 1, 0.36, 1);
      }

      /* max-height driven entirely by JS */

      /* Sub-links: 16px Medium in a 44px row (was 14px / ~41px). One step
         below the 18px section titles so the hierarchy holds, but never
         smaller than page body copy. 1.5 line-height (24px) + 10px
         top/bottom = 44px, the touch minimum. */
      .mobile-menu__sublink {
        display: flex;
        align-items: center;
        gap: 14px;
        min-height: 44px;
        padding: 10px var(--mm-gutter);   /* 24px line + 20 = the 44px row */
        font-family: var(--wp--preset--font-family--body);
        font-weight: 500;     /* Medium */
        font-size: 1rem;      /* 16px */
        line-height: 1.5;
        color: var(--wp--custom--color--nav-ink);
        text-decoration: none;
        transition: background-color 160ms ease;
      }

      /* Tap highlight suppressed on touch devices — hover-only on desktop */
      .mobile-menu__sublink,
      .mobile-menu__trigger {
        -webkit-tap-highlight-color: transparent;
      }
      /* Tap-press feedback on sub-links (the real action buttons inside the accordion) */
      .mobile-menu__sublink:active {
        background-color: var(--mm-highlight);
        color: var(--wp--preset--color--coral);
      }
      /* Coral tap-flash for page navigation links. CSS :active is unreliable on
         iOS Safari for <a> tags (page loads before the paint). JS adds .is-tapping
         on touchstart — fires on finger contact, before navigation — so the colour
         renders in the brief window between touch and page unload. */
      .mobile-menu__sublink.is-tapping,
      .mobile-menu__trigger--plain.is-tapping {
        color: var(--wp--preset--color--coral);
      }
      @media (hover: hover) {
        .mobile-menu__sublink:hover {
          background-color: var(--mm-highlight);
        }
      }

      /* Active state (parity with desktop): bold the section title and
         highlight the current sub-page. Classes set by nav.js. */
      /* Resting titles are Medium + a 0.3px stroke (faux semibold), so real Bold is
         now a single step up. 600 is NOT loaded and would snap to 700 anyway; say 700
         and drop the stroke so Bold doesn't get fattened further. */
      .mobile-menu__section--active > .mobile-menu__trigger { font-weight: 700; -webkit-text-stroke: 0; }
      .mobile-menu__sublink--active { background-color: var(--mm-highlight); }

      /* +20% on the marks in the menu (Max 2026-09-14) */
      .mobile-menu__sublink .primary-nav__dropdown-icon {
        width: 24px;
        height: 24px;
        flex-shrink: 0;
      }

      /* Actions: stacked full-width buttons, Get started on top, Login
         under it (Max 2026-09-14; was a side-by-side pair). The markup
         order is Login then Get started, so `order` flips them visually. */
      .mobile-menu__actions {
        display: flex;
        flex-direction: column;
        gap: 10px;
        /* Bottom padding clears the iPhone home indicator on notched
           phones (env() is 0 everywhere else). */
        padding: 16px var(--mm-gutter) calc(20px + env(safe-area-inset-bottom, 0px));
        /* Sticky so it stays pinned to the bottom of the screen while a
           long expanded section scrolls underneath it */
        position: sticky;
        bottom: 0;
        background: #FFFFFF;
        /* Hairline above the buttons, edge to edge (Relume reference,
           Max 2026-09-14): a lighter cousin of the Login outline's
           #D1C6C2 so it reads as a rule, not a border. */
        border-top: 1px solid rgba(226, 215, 210, 0.5);
      }

      /* The pointer over Get started. Anchored to the actions block
         (position:sticky is a containing block for absolutes). Sits to
         the right of the centred label with its fingertip on the button's
         top edge, pointing back at the words. Scale-pops in 350ms after
         the menu is visible (the menu's own fade is 240ms), then floats
         on the article CTA's 4.2s rhythm. Closing the menu drops
         .is-visible, which resets the pop, so it plays again next time. */
      @keyframes mm-hand-pop {
        from { transform: scale(0); }
        to   { transform: scale(1); }
      }
      @keyframes mm-hand-float {
        0%, 100% { transform: rotate(180deg) translate(0, 0); }
        50%      { transform: rotate(180deg) translate(0, -6px); }
      }
      /* Turned 180 so it points DOWN at the button from above (Max
         2026-09-14), 68px wide (up 25% from 54). The image's fingertip
         is top-right, so rotated it is bottom-left: the box is placed
         with that corner resting on the button's top edge, right of the
         centred label, the fist rising above it. */
      .mobile-menu__hand {
        position: absolute;
        left: calc(50% + 44px);
        top: -20px;               /* box is ~75px tall, the finger its bottom ~30px: box bottom at 55px puts the whole finger inside the button (16px to 64px), fist rising above */
        z-index: 2;
        width: 68px;
        pointer-events: none;
        transform: scale(0);
        transform-origin: 20% 85%;   /* grows out from the fingertip */
      }
      .mobile-menu__hand img {
        display: block;
        width: 100%;
        height: auto;
        image-rendering: pixelated;
        image-rendering: crisp-edges;
        transform: rotate(180deg);
      }
      .mobile-menu.is-visible .mobile-menu__hand {
        animation: mm-hand-pop 0.5s cubic-bezier(0.34, 1.56, 0.64, 1) 0.35s both;
      }
      .mobile-menu.is-visible .mobile-menu__hand img {
        animation: mm-hand-float 4.2s ease-in-out 0.85s infinite;
      }
      @media (prefers-reduced-motion: reduce) {
        .mobile-menu__hand { transform: none; }
        .mobile-menu.is-visible .mobile-menu__hand,
        .mobile-menu.is-visible .mobile-menu__hand img { animation: none; }
      }

      /* Login: full width under the CTA, outlined style */
      .mobile-menu__login {
        order: 2;
        width: 100%;
        display: flex;
        align-items: center;
        justify-content: center;
        /* Rendered size is 48px / 15px: button.css's touch block
           (<=1024px, !important) sizes every button family, this pair
           included, so it matches the 48px row rhythm above by design. */
        min-height: 48px;
        border: 1px solid #D1C6C2;
        font-family: var(--wp--preset--font-family--body);
        font-weight: 500;
        font-size: 0.9375rem;
        color: var(--wp--preset--color--ink);
        text-decoration: none;
      }

      /* Get started: full width, in the coral primary gradient (its own
         .btn--primary styling; the old dark-secondary override is gone). */
      .mobile-menu__cta {
        order: 1;
        width: 100%;
        justify-content: center;   /* .btn is inline-flex, start-aligned by default */
        min-height: 48px;      /* see .mobile-menu__login: button.css's touch block owns this */
        box-shadow: none !important;
        padding-inline: 1rem !important;
      }

      /* Page scrolls freely underneath the modal */
      /* Prevent horizontal scroll at mobile/tablet.
         MUST be `clip`, never `hidden` (fixed 2026-07-15): `hidden`
         forces overflow-y to `auto`, turning html/body into scroll
         containers — which silently kills position:sticky against the
         viewport for EVERYTHING below 1024px (it broke the pinned
         announce bar; base.css's body{overflow-x:clip} comment
         documents this exact trap, and this leaked source rule was
         overriding it). `clip` trims sideways overflow identically
         without creating a scroll container. */
      html,
      body {
        overflow-x: clip;
        max-width: 100%;
      }
      /* Page remains scrollable behind the modal */
    }

    @media (min-width: 1024px) {
      .mobile-menu { display: none !important; }
    }

/* ── MODES PAGE — transparent nav over the hero backdrop ─────────────
   WordPress adds body.page-id-97 automatically on the Modes page.
   The header stays transparent and keeps its place in flow, while the modes
   segment is pulled up by exactly the header's height — so the cream
   pixel-grain canvas (modes.js) runs up behind the nav and shows through it.
   .modes-hero adds the same 5.5rem back as top padding, which preserves the
   designed nav-to-badge gap. The announce bar above is untouched and keeps
   its own background.
   Nav elements are the sitewide ink/coral defaults here (NOT inverted like
   About below) — the backdrop behind them is cream now, not dark artwork, so
   white text would vanish. This block exists only to keep z-index/transparency
   scoped to this page; the colour values below just restate the defaults.
   Entirely scoped — zero effect on any other page.
   ──────────────────────────────────────────────────────────────────── */
body.page-id-97 .site-header {
  background: transparent;
  z-index: 30;            /* .site-header is position:relative, so this paints it above the canvas pulled up beneath */
}
/* -5.5rem = the header's RENDERED height (88px), which holds at every width.
   Do not switch this to 3.5rem below 640px to match the min-height there: that
   is only a floor and never binds — the logo/hamburger row measures 88px on
   mobile too, so a 3.5rem pull-up leaves a 32px strip at the top of the header
   with no canvas behind it. */
body.page-id-97 .kwb-segment--modes { margin-top: -5.5rem; }

body.page-id-97 .primary-nav__link,
body.page-id-97 .site-header__login { color: var(--wp--custom--color--nav-ink); }
body.page-id-97 .primary-nav__link:hover,
body.page-id-97 .site-header__login:hover { color: var(--wp--custom--color--nav-ink); }
body.page-id-97 .primary-nav__link--active { font-weight: 700; }
body.page-id-97 .primary-nav__item--active > .primary-nav__link { font-weight: 700; }
body.page-id-97 .primary-nav__chevron polygon { fill: var(--wp--custom--color--nav-ink); stroke: var(--wp--custom--color--nav-ink); }
body.page-id-97 .hamburger { color: var(--wp--custom--color--nav-ink); }

/* ── GRAIN-BACKED HEADERS — translucent hover highlight ───────────────
   Modes (body.page-id-97) and the blog hub / posts page (body.kwb-blog-hub,
   body.blog — blog-hub.css does the same transparent-header pull-up) both
   run an animated pixel-grain canvas up behind the nav. The sitewide solid
   #EEDED0 hover stamps an opaque cream block over those moving cells, which
   reads as a flat cut-out. Here the highlight is a warm tint at 16% alpha
   instead: rgba(160,110,80,.16) over the cream token (#FCF0E6) resolves to
   ≈#EDDBCE, i.e. the same tone as the sitewide highlight on a flat page, so
   nothing looks different at rest — but 84% of the grain shows through and
   keeps animating underneath the hover. Applies to the hover, the persistent
   active-parent highlight and the Log in link, so all three match.
   Entirely scoped — every other page keeps the solid #EEDED0.
   ──────────────────────────────────────────────────────────────────── */
body.page-id-97 .primary-nav__link:hover,
body.page-id-97 .site-header__login:hover,
body.page-id-97 .primary-nav__item--active > .primary-nav__link,
body.kwb-blog-hub .primary-nav__link:hover,
body.kwb-blog-hub .site-header__login:hover,
body.kwb-blog-hub .primary-nav__item--active > .primary-nav__link,
body.blog .primary-nav__link:hover,
body.blog .site-header__login:hover,
body.blog .primary-nav__item--active > .primary-nav__link {
  background-color: rgba(160, 110, 80, 0.16);
}

/* ── ABOUT PAGE — inverted nav (blood-orange bg, white elements) ──────
   WordPress adds body.page-id-115 automatically on the About page.
   Entirely scoped — zero effect on any other page.
   ──────────────────────────────────────────────────────────────────── */
body.page-id-115 .site-header {
  background: var(--wp--preset--color--blood-orange);
}

/* Logo: brightness(0) collapses everything to black, invert(1) flips to white.
   Most reliable cross-browser approach — no SVG internals targeting needed.
   The shadow layer disappears too, leaving a clean flat white wordmark. */
body.page-id-115 .site-logo { filter: brightness(0) invert(1); }

/* Nav links + login */
body.page-id-115 .primary-nav__link,
body.page-id-115 .site-header__login { color: rgba(255,255,255,0.92); }
body.page-id-115 .primary-nav__link:hover,
body.page-id-115 .site-header__login:hover {
  color: white;
  background-color: rgba(255,255,255,0.12);
}
body.page-id-115 .primary-nav__link--active { font-weight: 700; color: white; }
/* Active section title on the inverted header — translucent white, not cream */
body.page-id-115 .primary-nav__item--active > .primary-nav__link {
  background-color: rgba(255, 255, 255, 0.12);
  color: white;
}

/* Chevrons */
body.page-id-115 .primary-nav__chevron polygon {
  fill: white;
  stroke: white;
}

/* Hamburger (mobile) */
body.page-id-115 .hamburger { color: white; }

/* Touch: the .mobile-menu__cta hover lives inside a max-width media block
   (CSS can't nest @media), so kill its lingering "stuck" hover gradient on
   touch devices here at top level. The :active push-down (in that block)
   provides the real press feedback. */
@media (hover: none) {
  .mobile-menu__cta:hover {
    background: var(--wp--preset--gradient--btn-primary);
  }
}

/* ══════════════════════════════════════════════════════════════════
   FLOATING BURGER (< 1024px) — the mobile/tablet counterpart to the
   desktop fixed Get-started button, sharing its exact choreography.

   Three independent beats, each on its own <html> flag:

   1. .kwb-burger-ready (nav.js, once it has measured the burger's
      docked position and published --kwb-burger-top/--kwb-burger-right)
      — the burger becomes permanently position:fixed AT ITS OWN
      DOCKED COORDINATES. Pixel-identical swap, invisible. Being
      always-fixed is what lets `top` transition smoothly in BOTH
      directions later: there is no pin/unpin handoff left to snap.
      No JS → no flag → plain docked burger, gracefully.

   2. .kwb-nav-floating (any scroll, > 2px) — the translucent glass
      circle fades in behind the icon. Fades back out at the top.

   3. .kwb-scrolled (existing flag: real scrolling under way) — the
      burger GLIDES UP to sit tight under the PINNED offer strip
      (announce-bar.css keeps the strip at the viewport top at all
      times), and glides back down to settle into the header on
      return. Same 0.35s ease as the desktop CTA's motion family.

   It is the SAME button, not a second copy — every open/close, aria
   and panel behaviour in nav.js carries over untouched.

   The circle's translucent fill is load-bearing, not decoration: the
   bare ink bars would vanish over the blood-orange bands and the
   photo grids, and on Modes/About the burger is overridden to white,
   which would disappear the moment it floated onto a cream section.

   Everything animates via TRANSITIONS on the base state, never a
   keyframe: they run both directions, and if anything ever stops the
   animation clock the burger simply shows its resting style — it can
   never be stranded invisible or mid-flight.

   Selectors are (0,3,0) so they beat body.page-id-97/115 .hamburger
   (0,2,1) on specificity rather than source order.
   ══════════════════════════════════════════════════════════════════ */
@media (max-width: 1023px) {

  /* Resting state: the circle is already there, just fully transparent,
     so every fade/glide runs in both directions through this one
     transition. `top` matches the desktop CTA's rise timing exactly.

     The backdrop-filter MUST start at zero-strength and ride the same
     transition as the fill: applied instantly at full strength, the
     saturate() briefly showed the raw page behind the circle boosted
     to 160% before any white had built up — over coral content that
     read as a bright coral flash on fade-in (user saw it live).
     Ramping blur+saturate in step with the fill removes the window
     where the filter runs ahead of the white. Browsers that can't
     interpolate filter lists fall back to the old instant swap —
     never worse than before. */
  .site-header__actions .hamburger {
    border-radius: 50%;
    background: rgba(255, 255, 255, 0);
    backdrop-filter: blur(0px) saturate(100%);
    -webkit-backdrop-filter: blur(0px) saturate(100%);
    transition:
      top 0.35s var(--wp--custom--motion--ease-out),
      background-color 0.3s ease,
      backdrop-filter 0.3s ease,
      -webkit-backdrop-filter 0.3s ease,
      box-shadow 0.3s ease,
      color 0.3s ease;
  }
  /* QA finding, 2026-08 (Max): pressing OS back to a scrolled position visibly
     animated the burger UP into its risen state, instead of just being there.
     Root cause: Beats 2/3 (.kwb-nav-floating / .kwb-scrolled, below) are
     computed from window.scrollY in nav.js — correct on a genuine live scroll,
     but on arriving at a page already scrolled (any back/forward navigation,
     bfcache-restored or freshly reloaded) that computation can land a beat
     after first paint, so the burger briefly paints DOCKED, then the correct
     risen state applies and the transition above eases it up — visibly, and
     wrongly, since nothing the visitor did should have animated it.
     nav.js applies `.kwb-nav-instant` for one synchronous tick around EVERY
     "the page just became visible" moment (initial load AND `pageshow`,
     bfcache-restored or not) — suspending transitions here means whichever
     state Beats 1-3 land on is simply THERE, no animate-in, then this class is
     removed so normal scroll-driven motion is completely unaffected. (0,2,1)
     — the `html` type selector — beats the base rule above's (0,2,0) cleanly,
     no !important needed. */
  html.kwb-nav-instant .site-header__actions .hamburger {
    transition: none;
  }

  /* Beat 1 — pinned at its own measured docked position (invisible). */
  .kwb-burger-ready .site-header__actions .hamburger {
    position: fixed;
    top: var(--kwb-burger-top, 1rem);
    right: var(--kwb-burger-right, 10px);
    width: 44px;
    height: 44px;
    /* Above the .mobile-menu backdrop (900) so a tap while the menu is
       open lands on the real button and closes it, rather than being
       caught by the backdrop. Below the cookie modal + page loader. */
    z-index: 950;
  }

  /* Beat 2 — the glass circle fades in the moment scrolling begins.
     Same family as the cookie modal's liquid-glass panel, scaled
     down; the blur keeps the two ink bars legible over busy imagery
     without going to an opaque fill. */
  .kwb-nav-floating .site-header__actions .hamburger {
    background: rgba(255, 255, 255, 0.72);
    backdrop-filter: blur(14px) saturate(160%);
    -webkit-backdrop-filter: blur(14px) saturate(160%);
    box-shadow: 0 10px 30px rgba(255, 54, 35, 0.16);
    color: var(--wp--custom--color--nav-ink);
  }

  /* Beat 3 — once real scrolling is under way (.kwb-scrolled), rise to
     sit tight UNDER the pinned offer strip. The strip never leaves the
     viewport now (announce-bar.css), so the rise target is the bar's
     measured height + 8px, not the raw viewport top — the old 12px
     would park the circle on top of the offer. Must come after Beat 1
     in the file — equal (0,3,0) specificity, source order decides. */
  .kwb-scrolled .site-header__actions .hamburger {
    top: calc(var(--kwb-announce-h, 2.4375rem) + 8px);
  }

  /* MENU OPEN: the burger stays exactly where it was and morphs into
     the X itself (aria-expanded drives the bar animation above) — it
     IS the close control; the overlay has no X of its own.

     The overlay is z 900. On plain pages the burger's fixed z 950 sits
     above it on its own, but Modes and the blog hub give .site-header
     z-index:30 (a stacking context), which would trap the burger UNDER
     the overlay. So while the menu is open the whole header is lifted
     above the overlay on every page (one rule, no per-page list to
     forget), made transparent and click-through so it can't paint a
     cream bar over the panel or steal taps from the overlay's wordmark,
     with only the burger left tappable, and the header's own wordmark
     hidden so it can't double up on (or, on About, whiten out) the
     overlay's. All keyed on html.kwb-menu-open, so nothing here exists
     for a single frame while the menu is shut. */
  html.kwb-menu-open .site-header {
    z-index: 951;
    background: transparent;
    pointer-events: none;
  }
  html.kwb-menu-open .site-header .site-logo {
    visibility: hidden;
  }
  /* The pinned promo strip stays visible over the open menu (Max
     2026-09-14): lifted above the overlay (900) and the lifted header
     (951). It is sticky to the viewport, which is why the scroll lock
     above is root-only. Its offer link stays tappable. */
  html.kwb-menu-open .announce-bar {
    z-index: 952;
  }
  /* (0,3,1): beats the floating/scrolled beat rules (0,3,0) and the
     About/Modes colour overrides (0,2,1). The glass circle fades out
     through its own 0.3s transition, leaving the bare X on the white. */
  html.kwb-menu-open .site-header__actions .hamburger {
    pointer-events: auto;
    color: var(--wp--custom--color--nav-ink);
    background: rgba(255, 255, 255, 0);
    backdrop-filter: blur(0px) saturate(100%);
    -webkit-backdrop-filter: blur(0px) saturate(100%);
    box-shadow: none;
  }

  @media (prefers-reduced-motion: reduce) {
    .site-header__actions .hamburger { transition: none; }
  }
}

/* "Soon" badge on in-progress nav links (Tutorial, Academy). Mirrors the
   article category-label style (coral, 10% coral wash, uppercase). Pushed to
   the row's trailing edge in both the desktop dropdown and the mobile menu,
   which are flex rows. Temporary — remove when those pages go live. */
.nav-soon {
  /* Sit snug after the label. The dropdown/sublink rows are flex with a gap
     between items; pull the badge back so it hugs the text instead. Desktop
     dropdown gap is 12px → -6px leaves ~6px. */
  margin-left: -0.375rem;
  flex: 0 0 auto;
  font-family: var(--wp--preset--font-family--body);
  font-weight: 700;
  font-size: 0.5625rem; /* 9px */
  line-height: 1;
  letter-spacing: 0.05em;
  text-transform: uppercase;
  color: var(--wp--preset--color--coral);
  background: rgba(255, 54, 35, 0.10);
  padding: 0.1875rem 0.375rem;
  border-radius: 0;
}
/* Mobile/tablet hamburger menu rows use a wider 14px gap → pull back a touch
   more so the badge hugs the label as closely as it does on desktop. */
.mobile-menu__sublink .nav-soon {
  margin-left: -0.5rem;
}


/* assets/css/components/register-pub.css */
/* ==================================================================
   Register my pub: the pub-group registration funnel
   patterns/register-pub.php + assets/js/register-pub.js (Max, 2026-10-03)
   inc/assets.php segment "register-pub" = contact.css + this file.

   FRAME = THE CONTACT PAGE (Max, 2026-10-04: "better match the Contact page
   format, and keep the regular nav"). contact.css owns the section padding,
   the two columns, the headline + finger, the lead, the card (#FFFAF5 +
   white hairline + lift) and Back, plus the "Registering with" badge
   (.reg__group). This file only adds the funnel: progress head, step
   panels, fields tuned to contact's measurements, chips, kit packs,
   review, You're in. Every rule is scoped under .reg.
   ================================================================== */

/* No offer bar here: group landlords never pay. The page uses the "Header only"
   template; this stylesheet only loads on this page, so the scope is the page.
   The custom property keeps the nav's offsets at 0 before nav.js measures. */
html:has(.kwb-segment--register-pub) { --kwb-announce-h: 0px; }
body:has(.kwb-segment--register-pub) .announce-bar { display: none; }

.reg {
  --reg-ink: var(--wp--preset--color--ink);
  --reg-coral: var(--wp--preset--color--coral);
  --reg-label: #473833;
  --reg-muted: #8C7068;
  --reg-placeholder: #827571;
  --reg-field: #F6EEE7;
  --reg-line: #D7BAAF;
  --reg-error: #C4271A;
  overflow-x: clip;
}

.reg *, .reg *::before, .reg *::after { box-sizing: border-box; }
.reg fieldset { border: 0; margin: 0; padding: 0; min-width: 0; min-inline-size: 0; }
.reg legend { padding: 0; }
.reg [hidden] { display: none !important; }
.reg__vh {
  position: absolute; width: 1px; height: 1px; overflow: hidden;
  clip: rect(0 0 0 0); clip-path: inset(50%); white-space: nowrap;
}
.reg__dot { color: var(--reg-coral); }
.reg__card { min-width: 0; }
/* contact.css centres .contact__inner with auto margins inside a flex column (desktop),
   which shrinks it to its content. Contact's long form fills it anyway; a short step
   would not, so hold the full Contact width. */
.reg .contact__inner { width: 100%; }
/* Pinned to the top on desktop (Max, 2026-10-15). contact.css centres the page in the
   window from 1024; on a tall screen that re-centred everything whenever the form grew
   or shrank (a host pick, the next step), so the page jumped. Here the top stays put and
   only the bottom moves. */
@media (min-width: 1024px) {
  .reg.contact { justify-content: flex-start; padding-top: clamp(2.5rem, 7vh, 6rem); }
}
/* "Registering with <logo>": a band across the top of the form card, edge to edge
   (group links only; Max, 2026-10-04). Pulls out over the card's padding. */
.reg .reg__card > .reg__group {
  display: flex;
  align-items: center;
  gap: 1rem;
  margin: -2.25rem -2.25rem 1.75rem;
  padding: 0.875rem 2.25rem;
  background: var(--reg-field);
  border: 0;
}
.reg .reg__card > .reg__group[hidden] { display: none; }
@media (max-width: 640px) {
  .reg .reg__card > .reg__group { margin: -1.5rem -1.25rem 1.25rem; padding: 0.75rem 1.25rem; gap: 0.75rem; }
}
/* "Register / your pub." on two lines at every size (Max, 2026-10-04): the <br> sets the
   break, nowrap stops "your pub" splitting again. */
.reg .contact__headline { white-space: nowrap; }
/* The headline's coral full stop blinks like the homepage hero's (hero.css: 1.1s step-end). */
.reg .contact__headline-accent { animation: reg-cursor-blink 1.1s step-end infinite; }
@keyframes reg-cursor-blink {
  0%, 100% { opacity: 1; }
  50%      { opacity: 0; }
}

/* First load (Kev, 2026-10-12): the Contact page's lift, contact.css .sr-reveal
   (40px rise + fade, 0.65s, staggered by inline delays in the markup), triggered by
   register-pub.js on kwb:loaded. The headline rises without fading: that rule lives in
   contact.css now (it covers Contact too). Its blinking full stop is its own animation
   on the child span, so the two never touch. */

/* "Join thousands of quiz night hosts": the sign-up gateway's trust strip (gateway.css
   .gateway__trust), left-aligned under the lead (Max, 2026-10-04). */
.reg__trust { display: flex; flex-direction: column; align-items: flex-start; gap: 0.75rem; margin-top: -0.75rem; }
.reg__trust-label {
  margin: 0;
  font-family: var(--wp--preset--font-family--body);
  font-weight: 700;
  font-size: 0.8125rem;
  color: var(--wp--preset--color--ink);
}
.reg__trust-img { display: block; width: 300px; max-width: 100%; height: auto; }   /* was 330 (Max: a touch smaller) */

@media (max-width: 640px) {
  .reg__trust { margin-top: 0; }
  .reg__trust-img { width: 270px; }   /* was 300 */
}

/* Past step 1, phones and tablets fold the headline away so each step opens
   right under the nav. Desktop keeps it (it sits beside the card). */
@media (max-width: 1023px) {
  .reg.is-going .contact__left { display: none; }
  .reg.is-going .contact__card { margin-top: 0; }
}

/* The step map is the desktop progress indicator; phones get the bar in the card. */
.reg__map { display: none; }

/* ── Card head: Step x of 4 + Back, then the bar ─────────────── */
.reg__head { margin-bottom: 22px; }
.reg__head-row { display: flex; align-items: center; justify-content: space-between; gap: 12px; min-height: 28px; margin-bottom: 10px; }
.reg__bar { display: grid; grid-template-columns: repeat(4, 1fr); gap: 4px; }
.reg__bar span {
  position: relative;
  overflow: hidden;
  height: 6px;
  background: #EFE2D7;
  transition: background-color 300ms ease;
}
.reg__bar span.is-done { background: var(--reg-coral); }
/* The current step: solid coral, with a lighter coral pulse sweeping through it
   left to right on a loop (Max, 2026-10-04; was a pixel-stepped dashed fill). */
.reg__bar span.is-now { background: var(--reg-coral); }
.reg__bar span.is-now::after {
  content: "";
  position: absolute;
  top: 0;
  bottom: 0;
  left: 0;
  width: 60%;
  background: linear-gradient(90deg, rgba(255, 165, 144, 0) 0%, #FFA590 50%, rgba(255, 165, 144, 0) 100%);
  transform: translateX(-100%);
  animation: reg-bar-pulse 1.8s cubic-bezier(0.45, 0, 0.55, 1) infinite;
}
@keyframes reg-bar-pulse {
  from { transform: translateX(-100%); }
  to   { transform: translateX(167%); }
}
.reg__count {
  font-family: var(--wp--preset--font-family--pixel);
  font-size: 1rem;
  line-height: 1;
  letter-spacing: 0.04em;
  text-transform: uppercase;   /* STEP 1 OF 4, LAST LOOK (Max, 2026-10-04) */
  color: var(--reg-coral);
  margin: 0;
}
/* Back lives beside Next at the foot of the card (Max, 2026-10-04): a square
   chevron on phones, chevron + "Back" from 600. Field fill, like the chips. */
.reg__back {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  gap: 8px;
  flex: none;
  width: 46px;
  height: 46px;
  padding: 0;
  font-family: var(--wp--preset--font-family--body);
  font-weight: 700;
  font-size: 0.9375rem;
  color: var(--reg-ink);
  background: var(--reg-field);
  border: 0;
  border-radius: 0;
  cursor: pointer;
  transition: background-color 150ms ease;
}
.reg__back svg { width: 7px; height: 11px; }
.reg__back-label { position: absolute; width: 1px; height: 1px; overflow: hidden; clip-path: inset(50%); white-space: nowrap; }
@media (hover: hover) { .reg__back:hover { background: #EFE2D7; } }
.reg__back:focus-visible { outline: 2px solid var(--reg-coral); outline-offset: 2px; }

/* ── Panels ──────────────────────────────────────────────────── */
.reg__panel { animation: reg-in 320ms var(--wp--custom--motion--ease-out, ease-out); }
@keyframes reg-in {
  from { opacity: 0; transform: translateY(8px); }
  to   { opacity: 1; transform: none; }
}
.reg__legend { display: block; width: 100%; }
.reg__h2 {
  display: inline-flex;
  align-items: center;
  gap: 8px;
  font-family: var(--wp--preset--font-family--body);
  font-weight: 700;
  font-size: 1.25rem;
  line-height: 1.2;
  letter-spacing: -0.01em;
  color: var(--reg-ink);
  margin: 0 0 18px;
  outline: none;
}
.reg__box { width: 30px; height: 30px; image-rendering: pixelated; margin: -6px 0 -4px; }
.reg__sub {
  font-weight: 500;
  font-size: 0.9375rem;
  line-height: 1.4;
  color: var(--reg-label);
  margin: -10px 0 18px;
}

/* ── Fields ──────────────────────────────────────────────────── */
.reg__fields {
  display: grid;
  grid-template-columns: minmax(0, 1fr);
  gap: 0.875rem;              /* contact.css phone row gap */
}
.reg__field { display: flex; flex-direction: column; gap: 0.5625rem; min-width: 0; }   /* 9px, as contact */
.reg__label {
  font-weight: 500;
  font-size: 0.8125rem;
  line-height: 1;
  letter-spacing: 0.005em;
  color: var(--reg-label);
  margin: 0;
}
.reg__label--section {
  font-weight: 700;
  font-size: 1rem;
  color: var(--reg-ink);
  margin: 22px 0 12px;
}
.reg__optional { color: var(--reg-muted); }

.reg__input {
  font-family: var(--wp--preset--font-family--body);
  font-weight: 500;
  font-size: 16px;            /* 16px+ stops iOS zooming on focus */
  line-height: 1.4;
  color: var(--reg-ink);
  background: var(--reg-field);
  border: 0;
  border-radius: 0;
  padding: 0.8125rem 0.9375rem;   /* contact.css */
  width: 100%;
  min-height: 46px;
  outline: none;
  -webkit-appearance: none;
  appearance: none;
  transition: box-shadow var(--wp--custom--motion--dur-fast, 150ms) ease;
}
.reg__input::placeholder { color: var(--reg-placeholder); opacity: 1; }
.reg__input:focus { box-shadow: inset 0 0 0 1px var(--reg-line); }
.reg__input:focus-visible { box-shadow: inset 0 0 0 2px var(--reg-ink); }
.reg__input--caps { text-transform: uppercase; }

/* Phone with the international prefix (contact.css .contact__phone-*), sized to
   the funnel's 46px fields and 16px type. */
.reg .contact__phone-country { height: 46px; min-height: 46px; font-size: 16px; }
.reg .reg__phone-input { font-size: 16px; line-height: 1.4; min-height: 46px; padding-block: 0.8125rem; }
.reg .reg__phone:has(.reg__phone-input:focus-visible) { box-shadow: inset 0 0 0 2px var(--reg-ink); }
.reg .reg__phone:has([aria-invalid="true"]) { box-shadow: inset 0 0 0 1px var(--reg-error); }
.reg__input--caps::placeholder { text-transform: none; }
.reg__input--date { min-height: 46px; display: block; }
.reg__input--date::-webkit-date-and-time-value { text-align: left; }
.reg__textarea { resize: vertical; min-height: 92px; }
.reg__input[aria-invalid="true"],
.reg__radios[aria-invalid="true"] .reg__chip span,
.reg__radios[aria-invalid="true"] .reg__pack-card { box-shadow: inset 0 0 0 1px var(--reg-error); }

.reg__select-wrap { position: relative; }
.reg__select { padding-right: 36px; cursor: pointer; }
.reg__select:invalid,
.reg__select.is-empty { color: var(--reg-placeholder); }
.reg__chevron { position: absolute; right: 14px; top: 50%; transform: translateY(-50%); pointer-events: none; }

.reg__err {
  font-weight: 500;
  font-size: 0.8125rem;
  line-height: 1.3;
  color: var(--reg-error);
  margin: 0;
}
.reg__hint {
  font-weight: 500;
  font-size: 0.8125rem;
  line-height: 1.4;
  color: var(--reg-muted);
  margin: -4px 0 0;
}
.reg__hint.is-note { color: var(--reg-label); }
.reg__hint strong { font-weight: 700; color: var(--reg-label); }
.reg__hint--day { color: var(--reg-label); }
/* Helper line under a field (pub email): sits in the field's own 9px gap. */
.reg__hint--field { margin: 0; }
/* "Your area manager" sub-section inside step 1's grid (Kev, 2026-10-12). */
.reg__fields > .reg__label--section { margin: 0.625rem 0 -0.375rem; }
.reg__fields > .reg__hint--section { margin: -0.375rem 0 0.125rem; }
/* Step 2's reassurance (Kev, 2026-10-12): a tinted note under the "why we ask" line. */
.reg__note {
  font-weight: 500;
  font-size: 0.875rem;
  line-height: 1.4;
  color: var(--reg-label);
  background: var(--reg-field);
  padding: 0.75rem 0.9375rem;
  margin: -4px 0 18px;
}
/* Personal email: a nudge, not an error (Max: warn, don't block). Coral edge, ink copy. */
.reg__field.is-warn .reg__input[aria-invalid="true"] { box-shadow: inset 0 0 0 1px var(--reg-coral); }
.reg__field.is-warn .reg__err {
  color: var(--reg-label);
  border-left: 3px solid var(--reg-coral);
  padding-left: 0.625rem;
}

/* ── Chips (night, call slot) ────────────────────────────────── */
.reg__radios > .reg__label { margin-bottom: 0.5625rem; display: block; }
.reg__radios > .reg__label .reg__optional { margin-left: 4px; }
.reg__chips { display: grid; gap: 6px; }
.reg__chips--days { grid-template-columns: repeat(4, minmax(0, 1fr)); }
.reg__chips--slots { grid-template-columns: minmax(0, 1fr); }
.reg__chip { position: relative; display: block; cursor: pointer; }
.reg__chip input,
.reg__pack input {
  position: absolute; opacity: 0; width: 1px; height: 1px; margin: 0; pointer-events: none;
}
.reg__chip span {
  display: flex;
  align-items: center;
  justify-content: center;
  gap: 8px;
  min-height: 46px;
  padding: 8px 10px;
  background: var(--reg-field);
  font-weight: 700;
  font-size: 0.9375rem;
  line-height: 1.1;
  color: var(--reg-ink);
  text-align: center;
  transition: background-color 150ms ease, color 150ms ease, box-shadow 150ms ease;
}
.reg__chip small { font-weight: 500; font-size: 0.8125rem; color: var(--reg-label); }
.reg__chips--slots .reg__chip span { justify-content: space-between; padding-inline: 14px; }
.reg__slot-name { display: inline-flex; align-items: center; gap: 8px; font-weight: inherit; }
.reg__slot-ico { display: block; flex: none; width: 18px; height: 18px; }
@media (hover: hover) { .reg__chip:hover span { background: #EFE2D7; } }
.reg__chip input:checked + span {
  background: var(--reg-ink);
  color: #FFFFFF;
}
.reg__chip input:checked + span small { color: rgba(255, 255, 255, 0.72); }
.reg__chip input:focus-visible + span { outline: 2px solid var(--reg-coral); outline-offset: 2px; }
/* Night chips are white with an outline (Max, 2026-10-04); picked = ink, as before. */
.reg__chips--days .reg__chip span { background: #FFFFFF; box-shadow: inset 0 0 0 1px var(--reg-line); flex-direction: column; gap: 5px; min-height: 64px; padding: 9px 4px 8px; }
.reg__day-ico { display: block; flex: none; width: 21px; height: 18px; }   /* 3px per pixel, cropped to the features */
@media (hover: hover) { .reg__chips--days .reg__chip:hover span { background: #FFFFFF; box-shadow: inset 0 0 0 1px var(--reg-ink); } }
.reg__chips--days .reg__chip input:checked + span { background: var(--reg-ink); box-shadow: inset 0 0 0 1px var(--reg-ink); }
/* "Not sure yet" (Max, 2026-10-12): the eighth cell on phones (4 + 4), a full-width
   strip under the week from 600. Same white chip, puzzled face beside the words. */
.reg__chip--unsure span { line-height: 1.05; }
/* Its two-line label makes its row taller on phones: every chip in the row fills it. */
.reg__chips--days .reg__chip span { height: 100%; }
/* Smallest phones (under 360): "Not sure yet" would wrap to three lines in a cell,
   so it takes the full-width strip there too, as from 600. */
@media (max-width: 359px) {
  .reg__chip--unsure { grid-column: 1 / -1; }
  .reg__chips--days .reg__chip--unsure span { flex-direction: row; gap: 8px; min-height: 46px; padding: 8px 14px; }
}

/* ── Pub group tiles (no group link only, Max 2026-10-04) ────── */
/* Styled like the night chips WERE (Max, 2026-10-04): field fill, no outline,
   darker on hover, picked = ink with the logo knocked out to white.
   Two across on phones, four from 600; "My group isn't listed" opens a box below. */
.reg__gtiles { display: grid; grid-template-columns: repeat(2, minmax(0, 1fr)); gap: 6px; }
.reg__gtile { position: relative; display: block; cursor: pointer; }
.reg__gtile input { position: absolute; opacity: 0; width: 1px; height: 1px; margin: 0; pointer-events: none; }
.reg__gtile-card {
  position: relative;
  display: flex;
  align-items: center;
  justify-content: center;
  height: 64px;
  padding: 10px 14px;
  background: var(--reg-field);
  transition: background-color 150ms ease;
}
.reg__gtile-logo { display: flex; align-items: center; justify-content: center; width: 100%; height: 100%; }
.reg__gtile-logo svg,
.reg__gtile-logo img { display: block; width: auto; height: auto; max-width: 76%; max-height: 24px; transition: filter 150ms ease; }
/* Optical sizing: the logos carry very different weight at one height. Kept small
   on purpose, plenty of air round each one (Max, 2026-10-04). */
.reg__gtile[data-g="admiral"] .reg__gtile-logo img     { max-height: 30px; }
.reg__gtile[data-g="greene-king"] .reg__gtile-logo svg { max-height: 31px; }
.reg__gtile[data-g="craft-union"] .reg__gtile-logo svg { max-height: 23px; }
.reg__gtile[data-g="mitchells-butlers"] .reg__gtile-logo svg { max-height: 23px; }
.reg__gtile[data-g="marstons"] .reg__gtile-logo svg    { max-height: 17px; }
.reg__gtile[data-g="stonegate"] .reg__gtile-logo svg   { max-height: 21px; }
.reg__gtile[data-g="star-pubs"] .reg__gtile-logo svg   { max-height: 25px; }
.reg__gtile[data-g="punch"] .reg__gtile-logo img       { max-height: 13px; }
@media (hover: hover) { .reg__gtile:hover .reg__gtile-card { background: #EFE2D7; } }
.reg__gtile input:checked + .reg__gtile-card { background: var(--reg-ink); }
.reg__gtile input:checked + .reg__gtile-card .reg__gtile-logo svg,
.reg__gtile input:checked + .reg__gtile-card .reg__gtile-logo img { filter: brightness(0) invert(1); }
.reg__gtile input:focus-visible + .reg__gtile-card { outline: 2px solid var(--reg-coral); outline-offset: 2px; }
.reg__radios[aria-invalid="true"] .reg__gtile-card { box-shadow: inset 0 0 0 1px var(--reg-error); }
.reg__gpick > .reg__err { margin-top: 0.5625rem; }
/* "My group isn't listed": a full-width strip in the tiles' style (Max, 2026-10-04),
   ink while its box is open. */
.reg__notlisted {
  display: flex;
  align-items: center;
  justify-content: center;
  width: 100%;
  height: 46px;
  margin-top: -3px;   /* the field's 9px gap - 3 = the tiles' own 6px */
  padding: 0 14px;
  font-family: inherit;
  font-weight: 700;
  font-size: 0.9375rem;
  color: var(--reg-ink);
  background: var(--reg-field);
  border: 0;
  border-radius: 0;
  cursor: pointer;
  transition: background-color 150ms ease, color 150ms ease;
}
@media (hover: hover) { .reg__notlisted:hover { background: #EFE2D7; } }
.reg__notlisted.is-on { background: var(--reg-ink); color: #FFFFFF; }
.reg__notlisted:focus-visible { outline: 2px solid var(--reg-coral); outline-offset: 2px; }

/* ── Kit packs ───────────────────────────────────────────────── */
.reg__packs { display: grid; grid-template-columns: minmax(0, 1fr); gap: 10px; }
.reg__pack { position: relative; display: block; cursor: pointer; }
.reg__pack-card {
  position: relative;
  display: grid;
  grid-template-columns: 92px minmax(0, 1fr);
  gap: 14px;
  padding: 10px 12px 12px 10px;
  background: #FFFFFF;
  border: 1px solid #FFFFFF;
  box-shadow: inset 0 0 0 1px #EFE2D7;
  transition: box-shadow 150ms ease;
}
.reg__pack-img { display: block; aspect-ratio: 4 / 5; overflow: hidden; background: #EFE2D7; }
.reg__pack-img img { display: block; width: 100%; height: 100%; object-fit: cover; }
.reg__pack-body { display: flex; flex-direction: column; gap: 8px; min-width: 0; padding-top: 2px; }
.reg__pack-top { display: flex; align-items: baseline; justify-content: space-between; gap: 8px; padding-right: 26px; }
.reg__pack-name { font-weight: 700; font-size: 1.125rem; line-height: 1.1; }
.reg__pack-price {
  font-family: var(--wp--preset--font-family--pixel);
  font-size: 1rem;
  letter-spacing: 0.04em;
  color: var(--reg-label);
  white-space: nowrap;
}
.reg__pack-price--extra { color: var(--reg-coral); }
.reg__pack-list { display: flex; flex-direction: column; gap: 4px; }
.reg__pack-list > span {
  position: relative;
  padding-left: 14px;
  font-weight: 500;
  font-size: 0.8125rem;
  line-height: 1.3;
  color: var(--reg-label);
}
.reg__pack-list > span::before {
  content: "";
  position: absolute; left: 0; top: 0.42em;
  width: 6px; height: 6px;
  background: var(--reg-coral);   /* square pixel bullet */
}
.reg__pack-list > .reg__pack-lead { padding-left: 0; font-weight: 700; color: var(--reg-ink); }
.reg__pack-list > .reg__pack-lead::before { content: none; }
.reg__pack-tick {
  position: absolute; top: 10px; right: 10px;
  width: 20px; height: 20px;
  box-shadow: inset 0 0 0 1.5px var(--reg-line);
  background: #FFFFFF;
}
.reg__pack input:checked + .reg__pack-card { box-shadow: inset 0 0 0 2px var(--reg-coral); }
.reg__pack input:checked + .reg__pack-card .reg__pack-tick {
  box-shadow: none;
  background:
    url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='12' height='10' viewBox='0 0 12 10'%3E%3Cpolygon fill='%23FFF' points='4.321 9.075 0 4.753 1.496 3.258 4.321 6.083 10.404 0 11.9 1.496'/%3E%3C/svg%3E") center / 12px 10px no-repeat,
    var(--reg-coral);
}
.reg__pack input:focus-visible + .reg__pack-card { outline: 2px solid var(--reg-coral); outline-offset: 2px; }
.reg__packs > .reg__err { margin-top: 2px; }
/* "No kit for me, thanks": the third option, a strip like "My group isn't listed". */
.reg__nokit { position: relative; display: block; cursor: pointer; }
.reg__nokit input { position: absolute; opacity: 0; width: 1px; height: 1px; margin: 0; pointer-events: none; }
.reg__nokit-strip {
  display: flex; align-items: center; justify-content: center;
  height: 46px; padding: 0 14px;
  font-weight: 700; font-size: 0.9375rem; color: var(--reg-ink);
  background: var(--reg-field);
  transition: background-color 150ms ease, color 150ms ease;
}
@media (hover: hover) { .reg__nokit:hover .reg__nokit-strip { background: #EFE2D7; } }
.reg__nokit input:checked + .reg__nokit-strip { background: var(--reg-ink); color: #FFFFFF; }
.reg__nokit input:focus-visible + .reg__nokit-strip { outline: 2px solid var(--reg-coral); outline-offset: 2px; }
.reg__radios[aria-invalid="true"] .reg__nokit-strip { box-shadow: inset 0 0 0 1px var(--reg-error); }
/* The kit NOTE (moved here from step 2, Max 2026-10-04), hidden with the address for "no kit". */
.reg__hint--kit { margin: 14px 0 0; }

/* ── Step 4: book a call or skip it (Kev, 2026-10-12) ────────── */
/* The pack cards' look without the photo: white, hairline, picked = 2px coral + tick. */
.reg__callpick { display: grid; grid-template-columns: minmax(0, 1fr); gap: 10px; }
.reg__choice { position: relative; display: block; cursor: pointer; }
.reg__choice input { position: absolute; opacity: 0; width: 1px; height: 1px; margin: 0; pointer-events: none; }
.reg__choice-card {
  position: relative;
  display: flex;
  flex-direction: column;
  gap: 6px;
  height: 100%;
  padding: 16px 44px 16px 16px;
  background: #FFFFFF;
  box-shadow: inset 0 0 0 1px #EFE2D7;
  transition: box-shadow 150ms ease;
}
.reg__choice-name { font-weight: 700; font-size: 1.0625rem; line-height: 1.2; color: var(--reg-ink); }
.reg__choice-desc { font-weight: 500; font-size: 0.8125rem; line-height: 1.4; color: var(--reg-label); }
@media (hover: hover) { .reg__choice:hover .reg__choice-card { box-shadow: inset 0 0 0 1px var(--reg-line); } }
.reg__choice input:checked + .reg__choice-card { box-shadow: inset 0 0 0 2px var(--reg-coral); }
.reg__choice input:checked + .reg__choice-card .reg__pack-tick {
  box-shadow: none;
  background:
    url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='12' height='10' viewBox='0 0 12 10'%3E%3Cpolygon fill='%23FFF' points='4.321 9.075 0 4.753 1.496 3.258 4.321 6.083 10.404 0 11.9 1.496'/%3E%3C/svg%3E") center / 12px 10px no-repeat,
    var(--reg-coral);
}
.reg__choice .reg__pack-tick { top: 14px; right: 14px; }
.reg__choice input:focus-visible + .reg__choice-card { outline: 2px solid var(--reg-coral); outline-offset: 2px; }
.reg__radios[aria-invalid="true"] .reg__choice-card { box-shadow: inset 0 0 0 1px var(--reg-error); }
.reg__callpick > .reg__err { margin-top: 2px; }

/* ── Review ──────────────────────────────────────────────────── */
.reg__review { display: flex; flex-direction: column; gap: 10px; }
.reg__rv {
  background: #FFFFFF;
  box-shadow: inset 0 0 0 1px #EFE2D7;
  padding: 19px 14px 17px;   /* a touch more air top and bottom (Max, 2026-10-04) */
}
.reg__rv-head { display: flex; align-items: center; justify-content: space-between; gap: 10px; margin-bottom: 8px; }
.reg__rv-title { display: flex; align-items: baseline; gap: 8px; font-family: var(--wp--preset--font-family--body); font-weight: 700; font-size: 1rem; letter-spacing: 0; line-height: 1.2; margin: 0; }
.reg__rv-title .reg__map-num { font-size: 0.9375rem; }
.reg__rv-edit {
  font-family: inherit;
  font-weight: 700;
  font-size: 0.8125rem;
  color: var(--reg-coral);
  background: none;
  border: 0;
  padding: 8px 0 8px 12px;
  margin: -8px 0;
  cursor: pointer;
  text-decoration: underline;
  text-underline-offset: 3px;
}
.reg__rv dl { margin: 0; display: grid; grid-template-columns: minmax(0, 1fr); gap: 6px; }
.reg__rv-row { display: grid; grid-template-columns: 7.5em minmax(0, 1fr); gap: 10px; }
.reg__rv dt { font-weight: 500; font-size: 0.8125rem; line-height: 1.35; color: var(--reg-muted); }
.reg__rv dd { margin: 0; font-weight: 500; font-size: 0.875rem; line-height: 1.35; color: var(--reg-ink); overflow-wrap: anywhere; }

/* ── Nav row ─────────────────────────────────────────────────── */
.reg__nav { display: flex; gap: 6px; margin-top: 24px; }
.reg .reg__nav .reg__next { flex: 1 1 auto; width: auto; }
.reg .reg__next {
  width: 100%;
  height: 46px;
  min-height: 46px;
  padding: 0 1.75rem;
  justify-content: center;
  position: relative;
}
.reg__dots { display: none; gap: 4px; align-items: center; }
.reg__dots span {
  width: 5px; height: 5px; background: #FFFFFF;
  animation: reg-dot 1s ease-in-out infinite;
}
.reg__dots span:nth-child(2) { animation-delay: 0.15s; }
.reg__dots span:nth-child(3) { animation-delay: 0.3s; }
@keyframes reg-dot { 0%, 100% { opacity: 0.3; } 50% { opacity: 1; } }
.reg__next.is-sending { pointer-events: none; }
/* Required answers missing: looks disabled (the Contact page's 0.38), still
   pressable so a press can point at what's missing. */
.reg .reg__next.is-blocked { opacity: 0.38; cursor: not-allowed; transform: none; background: var(--wp--preset--gradient--btn-primary); }
.reg .reg__next { transition: opacity 200ms ease; }
.reg__next.is-sending .reg__next-label,
.reg__next.is-sending .btn__arrow { display: none; }
.reg__next.is-sending .reg__dots { display: inline-flex; }

.reg__send-error {
  font-weight: 500;
  font-size: 0.875rem;
  line-height: 1.4;
  color: var(--reg-error);
  margin: 16px 0 0;
}
.reg__hp { position: absolute; left: -9999px; width: 1px; height: 1px; overflow: hidden; }

/* ── You're in ───────────────────────────────────────────────── */
/* "You're in" takes the whole page (Max, 2026-10-04): the left column (headline,
   lead, avatars, step map) goes, one column, final state only. */
.reg.is-done .contact__left { display: none; }
.reg.is-done .contact__inner { grid-template-columns: minmax(0, 1fr); }
/* No white card behind it (Max, 2026-10-04): it sits straight on the page. */
.reg .reg__card.is-done,
.reg .reg__card.is-done:hover,
.reg .reg__card.is-done.is-focus {
  background: transparent;
  border-color: transparent;
  box-shadow: none;
  padding: 0;
}
.reg__done { text-align: left; max-width: 34rem; }
.reg__done-tick { width: 64px; height: 64px; display: block; margin: 4px 0 14px; }
/* The tick and the title pop in (with the confetti, register-pub.js), then
   everything below lifts in, one after the other. */
.reg__done-tick,
.reg__done-title { animation: reg-pop 560ms cubic-bezier(0.34, 1.56, 0.64, 1) both; transform-origin: left center; }
.reg__done-tick { transform-origin: center; }
.reg__done-title { animation-delay: 90ms; }
.reg__done-sub, .reg__next-steps, .reg__done-cta, .reg__done-help {
  animation: reg-lift 520ms var(--wp--custom--motion--ease-out, cubic-bezier(0.22, 1, 0.36, 1)) both;
}
.reg__done-sub     { animation-delay: 420ms; }
.reg__next-steps   { animation-delay: 540ms; }
.reg__done-cta     { animation-delay: 660ms; }
.reg__done-help    { animation-delay: 740ms; }
@keyframes reg-pop {
  0%   { opacity: 0; transform: scale(0.4); }
  60%  { opacity: 1; }
  100% { opacity: 1; transform: scale(1); }
}
@keyframes reg-lift {
  from { opacity: 0; transform: translateY(16px); }
  to   { opacity: 1; transform: none; }
}
.reg__done-cta { margin-top: 26px; }
/* Book chosen + Calendly set: the pubs-page link drops to a line under the Book button. */
.reg__done-more { font-weight: 500; font-size: 0.875rem; color: var(--reg-label); margin: 14px 0 0; animation: reg-lift 520ms var(--wp--custom--motion--ease-out, cubic-bezier(0.22, 1, 0.36, 1)) both; animation-delay: 700ms; }
.reg__done-more a { color: var(--reg-ink); font-weight: 700; text-underline-offset: 3px; }
.reg__confetti { position: fixed; inset: 0; width: 100vw; height: 100vh; pointer-events: none; z-index: 9999; }
.reg__done-title {
  font-family: var(--wp--preset--font-family--display);
  font-weight: 400;
  font-size: 2.5rem;
  line-height: 0.95;
  letter-spacing: -0.1em;
  margin: 0;
  outline: none;
}
.reg__done-sub { font-weight: 500; font-size: 1rem; line-height: 1.45; margin: 12px 0 20px; }
.reg__next-steps, .reg__map {
  list-style: none;
  margin: 0;
  padding: 0;
}
.reg__next-steps { display: flex; flex-direction: column; gap: 14px; }
.reg__next-steps li { display: grid; grid-template-columns: 2.25rem minmax(0, 1fr); align-items: baseline; }
.reg__next-steps li > span:last-child {
  display: block;   /* not flex: the filled-in dates are inline spans and must stay in the sentence */
  font-weight: 500; font-size: 0.875rem; line-height: 1.4; color: var(--reg-label);
}
.reg__next-steps strong { display: block; margin-bottom: 2px; font-weight: 700; font-size: 1rem; color: var(--reg-ink); }
.reg__map-num {
  font-family: var(--wp--preset--font-family--pixel);
  font-size: 1rem;
  letter-spacing: 0.06em;
  color: var(--reg-coral);
}
.reg__done-help { font-weight: 500; font-size: 0.875rem; color: var(--reg-label); margin: 18px 0 0; }
.reg__done-help a { color: var(--reg-ink); font-weight: 700; text-underline-offset: 3px; }

/* Narrow pack cards: the price drops under the name so "Promo pack" / "Premium pack"
   each stay on one line. */
@media (max-width: 599px) {
  .reg__pack-top { flex-direction: column; align-items: flex-start; gap: 4px; }
}
@media (max-width: 379px) {   /* smallest phones: a slimmer photo + 16px names */
  .reg__pack-card { grid-template-columns: 72px minmax(0, 1fr); gap: 12px; }
  .reg__pack-name { font-size: 1rem; }
}

/* ==================================================================
   Wider phones + tablets (600+): two-up fields, natural-width Next
   ================================================================== */
@media (min-width: 600px) {
  .reg .reg__next { width: auto; min-width: 9.5rem; }
  .reg .reg__nav .reg__next { flex: 0 0 auto; }
  .reg__back { width: auto; padding: 0 18px 0 16px; }
  .reg__back-label { position: static; width: auto; height: auto; overflow: visible; clip-path: none; }
  .reg__nokit { grid-column: 1 / -1; }
  .reg__fields { gap: 1.125rem 1rem; }
  .reg__fields { grid-template-columns: repeat(2, minmax(0, 1fr)); }
  .reg__field--full { grid-column: 1 / -1; }
  .reg__chips--days { grid-template-columns: repeat(7, minmax(0, 1fr)); }
  .reg__chip--unsure { grid-column: 1 / -1; }
  .reg__chips--days .reg__chip--unsure span { flex-direction: row; gap: 8px; min-height: 46px; padding: 8px 14px; }
  .reg__gtiles { grid-template-columns: repeat(4, minmax(0, 1fr)); }   /* eight groups = two rows of four */
  .reg__chips--slots { grid-template-columns: repeat(3, minmax(0, 1fr)); }
  .reg__callpick { grid-template-columns: repeat(2, minmax(0, 1fr)); }
  .reg__callpick > .reg__err { grid-column: 1 / -1; }
  .reg__chips--slots .reg__chip span { flex-direction: column; justify-content: center; gap: 2px; min-height: 60px; }
  .reg__packs { grid-template-columns: repeat(2, minmax(0, 1fr)); }
  .reg__pack-card { grid-template-columns: minmax(0, 1fr); height: 100%; align-content: start; padding: 10px 10px 14px; }
  .reg__pack-img { aspect-ratio: 16 / 9; }
  .reg__pack-img img { object-position: center 30%; }
  .reg__pack-body { padding: 0 4px; }
  .reg__pack-top { padding-right: 0; }
  .reg__pack-tick { top: 18px; right: 18px; }
  .reg__rv-row { grid-template-columns: 9em minmax(0, 1fr); }
}

/* ==================================================================
   Desktop (1024+): contact's two columns; the step map joins the left one
   ================================================================== */
@media (min-width: 1024px) {
  .reg__map { display: flex; flex-direction: column; gap: 4px; margin-top: -0.75rem; }
  .reg__map-btn {
    display: grid;
    grid-template-columns: 2.25rem minmax(0, 1fr);
    align-items: baseline;
    width: 100%;
    padding: 10px 12px 10px 0;
    background: none;
    border: 0;
    text-align: left;
    font-family: inherit;
    color: inherit;
    cursor: default;
  }
  .reg__map-copy {
    display: flex; flex-direction: column; gap: 2px;
    font-weight: 500; font-size: 0.8125rem; line-height: 1.4; color: var(--reg-label);
  }
  .reg__map-copy strong { font-weight: 700; font-size: 1rem; color: var(--reg-ink); }
  .reg__map-item { opacity: 0.45; transition: opacity 200ms ease; }
  .reg__map-item.is-now, .reg__map-item.is-done { opacity: 1; }
  .reg__map-item.is-done .reg__map-num { color: transparent; position: relative; }
  .reg__map-item.is-done .reg__map-num::before {
    content: "";
    position: absolute; left: 0; top: 50%;
    width: 14px; height: 12px; margin-top: -7px;
    background: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='12' height='10' viewBox='0 0 12 10'%3E%3Cpolygon fill='%23FF3623' points='4.321 9.075 0 4.753 1.496 3.258 4.321 6.083 10.404 0 11.9 1.496'/%3E%3C/svg%3E") left center / 14px 12px no-repeat;
  }
  .reg__map-btn:not(:disabled) { cursor: pointer; }
  .reg__map-btn:not(:disabled):hover strong { color: var(--reg-coral); }
}

@media (prefers-reduced-motion: reduce) {
  .reg .contact__headline-accent { animation: none; }
  .reg__done-more { animation: none; }
  .reg__panel, .reg__done,
  .reg__done-tick, .reg__done-title, .reg__done-sub, .reg__next-steps, .reg__done-cta, .reg__done-help { animation: none; }
  .reg__dots span { animation: none; opacity: 1; }
  .reg__bar span.is-now::after { animation: none; display: none; }
}

/* ==================================================================
   TRIAL MODE, a MOCKUP (Max, 2026-10-13): /register-my-pub/?trial=1
   A pub that pays for itself. html.kwb-reg-trial is set by a head
   script (functions.php) before first paint, so each mode's own copy
   shows from the first frame; register-pub.js then removes the other.
   ================================================================== */
html:not(.kwb-reg-trial) .reg [data-mode-trial],
html.kwb-reg-trial .reg [data-mode-group] { display: none !important; }
/* The all-hosts trial (/start-your-trial/, Kev 2026-10-15) is a trial too
   (.kwb-reg-trial + .kwb-reg-creator), with its own copy instead of the pubs'. */
html:not(.kwb-reg-trial) .reg [data-mode-pubtrial],
html.kwb-reg-creator .reg [data-mode-pubtrial],
html.kwb-reg-creator .reg [data-mode-pub],
html:not(.kwb-reg-creator) .reg [data-mode-creator] { display: none !important; }
/* /get-classic/ (Max, 2026-10-15): Classic's copy instead of the Pro trial's. */
html.kwb-reg-classic .reg [data-plan-pro],
html:not(.kwb-reg-classic) .reg [data-plan-classic] { display: none !important; }
/* The area manager block sits in step 1's grid as if it weren't wrapped. */
.reg__am { display: contents; }

/* The basket: a band across the top of the card, like "Registering with". */
.reg .reg__card > .reg__basket {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: 1rem;
  margin: -2.25rem -2.25rem 1.75rem;
  padding: 0.875rem 2.25rem;
  position: relative;
  overflow: hidden;
  isolation: isolate;
  /* A slow-drifting peach wash (Max, 2026-10-13: "a bit more special" than the cream),
     with a soft glow sweeping across it now and then (::after). */
  background: linear-gradient(115deg, #FFE7DA 0%, #FFCDB6 28%, #FFE1D1 52%, #FFC3A8 76%, #FFE7DA 100%);
  background-size: 300% 100%;
  animation: reg-basket-drift 9s ease-in-out infinite alternate;
}
.reg .reg__card > .reg__basket::after {
  content: "";
  position: absolute;
  inset: 0;
  z-index: -1;
  background: linear-gradient(105deg, rgba(255, 255, 255, 0) 30%, rgba(255, 255, 255, 0.55) 50%, rgba(255, 255, 255, 0) 70%);
  transform: translateX(-100%);
  animation: reg-basket-glow 5.5s cubic-bezier(0.45, 0, 0.55, 1) 1.2s infinite;
}
@keyframes reg-basket-drift {
  from { background-position: 0% 50%; }
  to   { background-position: 100% 50%; }
}
@keyframes reg-basket-glow {
  0%        { transform: translateX(-100%); }
  45%, 100% { transform: translateX(100%); }
}
.reg__basket-copy { min-width: 0; }
.reg__basket-ico { display: block; flex: none; width: 18px; height: 14px; }
.reg__basket-label {
  font-family: var(--wp--preset--font-family--pixel);
  font-size: 1rem;
  line-height: 1;
  letter-spacing: 0.04em;
  text-transform: uppercase;
  color: var(--reg-coral);
  margin: 0 0 5px;
  display: flex;
  align-items: center;
  gap: 7px;
}
.reg__basket-lines { font-weight: 500; font-size: 0.8125rem; line-height: 1.35; color: var(--reg-label); margin: 0; }
/* Items only, on one line, joined by a bold "+" (Max, 2026-10-15): the prices live on the right. */
.reg__basket-line { display: inline; }
.reg__basket-plus { font-weight: 700; color: var(--reg-ink); }
/* Price block on the right: the total (Roobert Medium, Max 2026-10-15; was Bold) with
   "for first 3 months" / "per month" under it. */
.reg__basket-sum { flex: none; text-align: right; }
.reg__basket-per { margin: 4px 0 0; font-weight: 500; font-size: 0.75rem; line-height: 1.2; color: var(--reg-label); }
.reg__basket-total {
  flex: none;
  font-weight: 500;
  font-size: 1.75rem;
  line-height: 1;
  letter-spacing: -0.02em;
  color: var(--reg-ink);
  margin: 0;
}
.reg__basket-total > span:last-child { display: inline-block; }
/* The full price, small coral and struck through, sitting on the total's baseline. */
.reg__basket-was {
  margin-right: 0.5rem;
  font-weight: 500;
  font-size: 0.875rem;
  letter-spacing: 0;
  color: var(--reg-coral);
  text-decoration: line-through;
  text-decoration-thickness: 1.5px;
  vertical-align: 0.15em;
}
.reg__basket-total .is-bump { animation: reg-bump 420ms cubic-bezier(0.34, 1.56, 0.64, 1); }
@keyframes reg-bump {
  0%   { transform: scale(1); }
  40%  { transform: scale(1.18); color: var(--reg-coral); }
  100% { transform: scale(1); }
}
@media (max-width: 640px) {
  .reg .reg__card > .reg__basket { margin: -1.5rem -1.25rem 1.25rem; padding: 0.75rem 1.25rem; gap: 0.75rem; }
  .reg__basket-total { font-size: 1.5rem; }
}

/* Kit step: the "why now" line sits under the heading like the other steps' subs. */
.reg [data-reg-kitwhen] { margin-bottom: 18px; }

/* Trial step 1: the pub name takes the full row, so the pub's address (line 1, line 2,
   then town + postcode side by side) reads as one block under it. */
@media (min-width: 600px) {
  html.kwb-reg-trial .reg [data-reg-pubname] { grid-column: 1 / -1; }
}

/* Trial step 3: "We'll send it to the pub", the pub's address as a white card,
   then the "Send it somewhere else" strip (the "My group isn't listed" toggle). */
.reg__sendto { display: flex; flex-direction: column; }
.reg__sendto-addr {
  font-weight: 500;
  font-size: 0.9375rem;
  line-height: 1.4;
  color: var(--reg-label);
  background: #FFFFFF;
  box-shadow: inset 0 0 0 1px #EFE2D7;
  padding: 14px 16px;
  margin: 0 0 6px;
  overflow-wrap: anywhere;
}
.reg__sendto-addr strong { display: block; font-weight: 700; color: var(--reg-ink); margin-bottom: 2px; }
.reg .reg__elsewhere { margin-top: 0; }
.reg__sendto + .reg__fields { margin-top: 14px; }

/* Checkout: the basket section of the review, total row in bold above a rule. */
.reg__rv--basket { background: var(--reg-field); box-shadow: none; }
.reg__rv--basket .reg__rv-row:last-child { padding-top: 8px; margin-top: 2px; border-top: 1px solid var(--reg-line); }
.reg__rv--basket .reg__rv-row:last-child dt,
.reg__rv--basket .reg__rv-row:last-child dd { font-weight: 700; font-size: 1rem; color: var(--reg-ink); }

/* MOCKUP note above "Continue to payment". */
.reg__mock {
  font-weight: 500;
  font-size: 0.8125rem;
  line-height: 1.4;
  color: var(--reg-label);
  border-left: 3px solid var(--reg-coral);
  padding: 2px 0 2px 10px;
  margin: 16px 0 0;
}
.reg__mock strong { font-weight: 700; color: var(--reg-ink); }

/* Trial step 3: the onboarding call choice under the packs (Max, 2026-10-13). */
.reg__callslot { margin-top: 6px; }
.reg__callslot > .reg__label--section { margin-bottom: 4px; }
.reg__callslot > .reg__hint { margin: 0 0 12px; }

@media (prefers-reduced-motion: reduce) {
  .reg__basket-total .is-bump { animation: none; }
  .reg .reg__card > .reg__basket { animation: none; }
  .reg .reg__card > .reg__basket::after { animation: none; display: none; }
}

/* ==================================================================
   ALL-HOSTS TRIAL, a MOCKUP (Kev, 2026-10-15): /start-your-trial/
   html.kwb-reg-trial.kwb-reg-creator. Same card, steps and basket as
   the pub trial; only the questions and the kit differ.
   ================================================================== */

/* Kind of host (Max, 2026-10-15): the pub group tiles (.reg__gtile: field fill,
   no outline, darker on hover, picked = ink), with the Hosts menu's icon above
   the name. The icon stays coral when picked; the name turns white. */
.reg__htile .reg__gtile-card {
  flex-direction: column;
  gap: 6px;
  height: 100%;
  min-height: 78px;
  padding: 12px 8px 11px;
  text-align: center;
}
.reg__htile-ico { display: block; flex: none; width: 24px; height: 24px; color: var(--reg-coral); }
/* Every name is two lines (a <br> in the markup), and the block holds two lines'
   height, so the icons sit level across each row (Max, 2026-10-15). 13px (was 15, then 14). */
.reg__htile-name { display: block; min-height: 2.3em; font-weight: 700; font-size: 0.8125rem; line-height: 1.15; color: var(--reg-ink); transition: color 150ms ease; }
.reg__htile input:checked + .reg__gtile-card .reg__htile-name { color: #FFFFFF; }

/* How often: the night chips' white outlined look, a small coral pixel face
   above the words (Max, 2026-10-15), picked = ink. Phones two-up, 600+
   four-up; "Not sure yet" is a full-width strip with the puzzled face. */
.reg__chips--freq { grid-template-columns: repeat(2, minmax(0, 1fr)); }
.reg__chips--outline .reg__chip span {
  background: #FFFFFF;
  box-shadow: inset 0 0 0 1px var(--reg-line);
  flex-direction: column;
  gap: 6px;
  height: 100%;
  min-height: 60px;
  padding: 9px 8px 8px;
  font-size: 0.875rem;
  line-height: 1.15;
}
.reg__px-ico { display: block; flex: none; }
@media (hover: hover) {
  .reg__chips--outline .reg__chip:hover span { background: #FFFFFF; box-shadow: inset 0 0 0 1px var(--reg-ink); }
}
.reg__chips--outline .reg__chip input:checked + span { background: var(--reg-ink); box-shadow: inset 0 0 0 1px var(--reg-ink); }
.reg__radios[aria-invalid="true"] .reg__chips--outline .reg__chip span { box-shadow: inset 0 0 0 1px var(--reg-error); }
.reg__chip--wide { grid-column: 1 / -1; }
.reg__chips--outline .reg__chip--wide span { flex-direction: row; gap: 8px; min-height: 46px; padding: 8px 14px; }
@media (min-width: 600px) {
  .reg__chips--freq { grid-template-columns: repeat(4, minmax(0, 1fr)); }
}

/* Under "Continue to payment" on Checkout, both paid trials (Max, 2026-10-15). */
.reg__handoff {
  margin: 10px 0 0;
  font-weight: 500;
  font-size: 0.8125rem;
  line-height: 1.4;
  color: var(--reg-coral);   /* coral, "kbit.tv" bold (Max, 2026-10-15) */
}
.reg__handoff strong { font-weight: 700; }

/* A quiet aside with the coral rule, the MOCKUP note's look: the pub pointer
   under the host chips, and the "printed packs are UK only" line in step 3. */
.reg__aside {
  font-weight: 500;
  font-size: 0.875rem;
  line-height: 1.4;
  color: var(--reg-label);
  border-left: 3px solid var(--reg-coral);
  padding: 2px 0 2px 10px;
  margin: 12px 0 0;
}
.reg__aside a { color: var(--reg-ink); font-weight: 700; text-decoration: underline; text-underline-offset: 2px; }
@media (hover: hover) { .reg__aside a:hover { color: var(--reg-coral); } }
.reg__packs > .reg__aside { margin: 0; grid-column: 1 / -1; }

/* "Download straight after sign-up" / "Posted to you, UK only" at the foot of each kit card. */
.reg__pack-when {
  margin-top: auto;
  padding-top: 2px;
  font-weight: 700;
  font-size: 0.75rem;
  line-height: 1.3;
  letter-spacing: 0.02em;
  color: var(--reg-ink);
}

/* Only the digital kit on offer (a streamer, or outside the UK): from 600 it
   takes the full row with the photo beside the list, as on phones, rather
   than a lone half-width card. */
@media (min-width: 600px) {
  .reg__packs.is-single .reg__pack-card { grid-template-columns: 132px minmax(0, 1fr); padding: 10px 12px 12px 10px; }
  .reg__packs.is-single .reg__pack { grid-column: 1 / -1; }
  .reg__packs.is-single .reg__pack-img { aspect-ratio: 4 / 5; }
  .reg__packs.is-single .reg__pack-top { padding-right: 26px; }
}

/* Printed pack photo: the orange box sits right of centre in a landscape shot, so
   aim the crop at it in both the phone (4:5) and wider (16:9) slots. */
.reg .reg__pack-img--box img { object-position: 62% 58%; }

/* "Let's get / you set up." + the "All done" screens' shadowed coral tick (Max, 2026-10-15):
   pops in like it does there, then floats (a copy of payment's badge-float, own name, keyframes
   are global). Zero-width anchor after "get" so it never moves the words; pulled left so it
   just overlaps the "t". */
.reg__verified { position: relative; display: inline-block; width: 0; height: 0; vertical-align: top; }
.reg__verified-badge {
  position: absolute;
  left: -0.1em;
  top: calc(-0.1em + 10px);
  width: 1.08em;   /* Max, 2026-10-15: 0.8em, then +50%, then -10% and 10px lower */
  height: auto;
  max-width: none;
  opacity: 0;
  transform: scale(0.6) translateY(10px);
  transition: transform 0.55s cubic-bezier(0.34, 1.56, 0.64, 1) 0.45s, opacity 0.4s ease 0.45s;
}
.contact__headline.is-visible .reg__verified-badge {
  opacity: 1;
  transform: scale(1) translateY(0);
  animation: reg-tick-float 3.5s cubic-bezier(0.65, 0, 0.35, 1) infinite 1.1s;
}
@keyframes reg-tick-float {
  0%   { transform: translateY(0px) rotate(-2deg); }
  25%  { transform: translateY(-7px) rotate(0deg); }
  50%  { transform: translateY(-12px) rotate(2deg); }
  75%  { transform: translateY(-6px) rotate(0deg); }
  100% { transform: translateY(0px) rotate(-2deg); }
}
@media (prefers-reduced-motion: reduce) {
  .reg__verified-badge, .contact__headline.is-visible .reg__verified-badge { animation: none; transition: none; opacity: 1; transform: none; }
}

/* assets/css/components/view-transitions.css */
/* ==================================================================
   View Transitions — persistent nav + offer strip (shared chrome)

   Opts the whole site into the browser's cross-document View Transitions
   API. On an internal navigation the browser snapshots the current page,
   loads the next one, and animates between them instead of hard-reloading
   — giving that "web-app" feel where the nav appears to stay put while the
   content below cross-fades.

   The offer strip + header are each given their own transition-name so the
   browser treats them as a single persistent element across the navigation:
   identical markup in the same position ⇒ they hold perfectly steady
   (pinned) while only the content beneath transitions.

   Graceful everywhere:
     • Browsers without the API ignore @view-transition entirely → normal
       navigation, page-loader as before. Nothing breaks.
     • Pages with no nav (gateway/contact, no-chrome template) simply
       cross-fade; the absent nav just isn't pinned.
     • Reduced-motion users navigate instantly (animations disabled below).

   The page-loader is suppressed during these transitions by an inline
   pagereveal hook in functions.php (wp_head) so it never flashes mid-morph.
   ================================================================== */

@view-transition {
  navigation: auto;
}

/* Pin the shared chrome so it stays put while content changes beneath it.

   IMPORTANT: the names are applied ONLY during an active transition (via the
   .kwb-vt-active class that JS toggles on pageswap/pagereveal and removes when
   the transition finishes). A persistent view-transition-name turns the header
   into a stacking context, which traps the absolutely-positioned dropdown menus
   beneath the page content. Scoping the names to the transition window keeps
   normal browsing — and the dropdowns — completely unaffected. */
html.kwb-vt-active .announce-bar {
  view-transition-name: kwb-offer;
}
html.kwb-vt-active .site-header {
  view-transition-name: kwb-nav;
}

/* Quick cross-fade for the page SWAP only (everything not pinned). The incoming
   hero + in-view reveals deliberately do NOT enter here — they stay primed and
   then play their real, per-element STAGGERED lift on the settled page once the
   cross-fade finishes (held until then by the pagereveal hook + page-loader.js).
   That keeps the charm of the original lift on navigation, not a whole-page slab. */
::view-transition-old(root),
::view-transition-new(root) {
  animation-duration: 0.25s;
  animation-timing-function: var(--wp--custom--motion--ease-out, cubic-bezier(0.22, 1, 0.36, 1));
}

/* Respect reduced-motion: navigate instantly, no transition animation */
@media (prefers-reduced-motion: reduce) {
  ::view-transition-group(*),
  ::view-transition-old(*),
  ::view-transition-new(*) {
    animation: none !important;
  }
}

/* style.css */
/*
Theme Name: Kwizzbit 3.0
Theme URI: https://kwizzbit.com
Author: Kwizzbit
Author URI: https://kwizzbit.com
Description: Block theme for Kwizzbit. Design tokens live in theme.json (single source of truth). Component CSS lives in assets/css/components/ and is enqueued per pattern. Reference docs: STYLEGUIDE.md and COMPONENTS.md in the source /HTML/ folder.
Version: 2.15.1
Requires at least: 6.4
Tested up to: 6.7
Requires PHP: 7.4
License: All rights reserved
License URI: https://kwizzbit.com
Text Domain: kwizzbit
Tags: block-theme, full-site-editing, one-column
*/

/* Theme metadata only — global styles live in assets/css/base.css.
   Per-pattern styles live in assets/css/components/{pattern}.css. */

