/* ============================================================================
   v9-header-hero.css — homepage header + hero (2026-08-08)

   Loaded after styles.css and home-refresh.css, same specificity, so it wins
   on order — the same convention home-refresh.css established.

   Two things live here:

   1. The header. A white bar at rest that contracts into a floating dark-glass
      tab the moment the purple hero slides under it. Links left, wordmark
      centred, Start now right. Only max-width / background / blur / padding
      animate, so nothing reflows.

   2. The hero. A 115deg diagonal ramp — black at the far left, up through
      navy and mauve into pink, coral-red hottest low and right — with two
      elongated lobes rotated onto that axis drifting along it, and the left
      and right edges pulled to black.

   The drift is a CONTINUOUS ORBIT and it runs for everyone (2026-08-10). It was
   an alternating band that read as a bounce, and it was damped under Reduce
   Motion; both are gone. The trade that leaves is written out in full beside
   the reduce-motion block further down — read it before restoring a guard.
   ========================================================================= */
/* ---- trust band, relocated out of the hero -------------------------------
   It now sits at the top of the results section, and it gets a rule beneath it
   so it reads as its own band rather than crowding the Real results heading.

   The ink is WHITE, not the dark set this block briefly used: the results
   section stopped being pale when it got the dark purple sweep (see .proof in
   styles.css), and dark ink on that field made both lines invisible — the
   heading and the sub beside the avatars had all but disappeared. Stated in
   plain white here rather than left to --ink-40/--ink-60, because those tokens
   are what flipped underneath this block the last time the section's
   background changed. */
.trust-band{
  padding: 0 0 clamp(28px,3.5vw,44px);
  margin-bottom: clamp(28px,3.5vw,44px);
  border-bottom: 1px solid rgba(255,255,255,.12);
}
.trust-band .hero-trust{ margin-top: 0; }
.trust-band .hero-trust-line{ color: #FFFFFF; }
.trust-band .hero-trust-sub{ color: rgba(255,255,255,.88); }
.trust-band .hero-avatars img{ border-color: #F5F4F1; }
.trust-band .hero-avatar-more{
  background: linear-gradient(140deg,#EDEAF6 0%,#E2DCF0 100%);
  color: #4B3A7A;
  border-color: #F5F4F1;
}

/* -------- slimmer white bar ----------------------------------------------
   Driven through --nav-h rather than a one-off height, because styles.css
   sizes .nav, .nav-inner and the mobile menu offset from the same variable —
   overriding just .nav would desync them. Live is 88; 72 read too thin, so
   80 — still 18px of air above and below the 44px CTA, everything centred. */
:root{ --nav-h: 80px; }
@media (max-width: 960px){ :root{ --nav-h: 70px; } }

/* -------- layout: links left, wordmark centred, CTA right ---------------- */
.nav .nav-inner{
  position: relative;                 /* anchor for the centred wordmark */
  display: flex;
  align-items: center;
  justify-content: space-between;
  width: 100%;
  max-width: var(--container);
  margin: 0 auto;
}
/* margin-left:auto, not justify-content — below 960px styles.css hides
   .nav-links and the wordmark is positioned, so space-between would be left
   with a single in-flow child and park the burger on the LEFT. */
.nav .nav-right{ display: flex; align-items: center; gap: 18px; margin-left: auto; }

/* The wordmark is taken OUT of the flex flow and centred on the bar itself.
   Letting it sit in a flex/grid cell drags it off-centre, because the left
   link group and the right CTA are different widths and neither will shrink
   below its content. Centring on the bar — which is itself centred in the
   viewport — holds true in both the wide bar and the narrow tab. */
.nav .nav-wordmark{
  position: absolute;
  left: 50%;
  top: 50%;
  transform: translate(-50%, -50%);
  white-space: nowrap;
  line-height: 1;
}
/* Thicker wordmark. Satoshi ships Regular/Medium/Bold only, so 700 is already
   the heaviest FILE available — asking for 800/900 renders identically (or
   worse, triggers inconsistent synthetic bolding). Two levers actually work:
     1. -webkit-text-stroke fattens the real glyph outlines;
     2. pulling the very wide 0.34em tracking in, which is what makes a
        wordmark read dense rather than airy.
   Strapline is gone from the markup entirely. */
.nav .logo-name{
  font-weight: 700;
  letter-spacing: .05em;    /* was .34em on the live site, then .20em */
  -webkit-text-stroke: .7px currentColor;
}

/* The monogram is PHONE ONLY — switched on inside the 960px block further
   down. On a desktop the left of the bar belongs to .nav-links, and putting a
   mark there as well would double the branding beside a centred wordmark. */
.nav-mark{ display: none; }

/* -------- AT REST: unchanged white bar, ink type ------------------------- */
.nav{
  display: flex;
  align-items: center;
  transition:
    background-color .5s cubic-bezier(.16,1,.3,1),
    backdrop-filter  .5s cubic-bezier(.16,1,.3,1),
    border-color     .5s cubic-bezier(.16,1,.3,1),
    box-shadow       .5s cubic-bezier(.16,1,.3,1);
}

/* Pill radius is always on — invisible until a background appears behind it.
   Only max-width / background / blur / padding animate, so nothing reflows. */
.nav .nav-inner{
  border-radius: 999px;
  background: rgba(13,13,13,0);
  -webkit-backdrop-filter: blur(0px) saturate(100%);
  backdrop-filter: blur(0px) saturate(100%);
  box-shadow: 0 0 0 rgba(28,28,26,0);
  transition:
    max-width        .95s cubic-bezier(.16,1,.3,1),
    height           .95s cubic-bezier(.16,1,.3,1),
    padding          .95s cubic-bezier(.16,1,.3,1),
    background-color .55s cubic-bezier(.16,1,.3,1),
    backdrop-filter  .55s cubic-bezier(.16,1,.3,1),
    box-shadow       .55s cubic-bezier(.16,1,.3,1);
}
.nav .logo-name,
.nav .nav-links a{ transition: color .5s cubic-bezier(.16,1,.3,1); }
.nav .nav-burger span{ transition: background .5s cubic-bezier(.16,1,.3,1); }

/* -------- SCROLLED: the floating glass tab ------------------------------- */
.nav.is-tab{
  background: transparent !important;
  -webkit-backdrop-filter: none !important;
  backdrop-filter: none !important;
  border-bottom-color: transparent !important;
  box-shadow: none !important;
  pointer-events: none;               /* only the tab stays clickable */
}
/* LEAVE THIS TRANSPARENT AND LEAVE THE SATURATE ABOVE 1.

   On 2026-08-09 this was flattened to a neutral dark frost — rgba(16,16,18,.66) with
   saturate(38%) — to stop the pill taking on the purple of the comparison section. It
   worked, and Alec asked for it to be put straight back: draining the backdrop also
   drains the life out of the bar, and over the white page it stopped reading as glass
   and started reading as a flat grey slab.

   So the colour pickup is deliberate. saturate(170%) amplifies whatever is behind the
   pill instead of merely blurring it, and that is the effect — the bar is supposed to
   take a tint from the section it is flying over. The comparison card next door went
   the other way (neutral frost, saturate 30%) and that one is staying that way; the two
   are different on purpose, so do not "fix" this one to match it. */
.nav.is-tab .nav-inner{
  pointer-events: auto;
  max-width: 940px;
  height: 56px;
  padding: 0 6px 0 24px;
  background: rgba(13,13,13,.62);
  -webkit-backdrop-filter: blur(22px) saturate(170%);
  backdrop-filter: blur(22px) saturate(170%);
  box-shadow: 0 12px 38px rgba(28,28,26,.20);
}

/* ink flips to white on the dark tab */
.nav.is-tab .logo-name{ color:#fff; }
.nav.is-tab .nav-links a{ color: rgba(255,255,255,.88); }
.nav.is-tab .nav-links a:hover{ color:#fff; }
.nav.is-tab .nav-links .nav-cta,
.nav.is-tab .nav-links .nav-cta:hover{ color: var(--warm-white); }
.nav.is-tab .nav-burger span{ background:#fff; }

.nav.is-tab .nav-links{ gap: 22px; }
.nav.is-tab .nav-cta{ padding: 11px 20px; font-size: 15px; }
.nav.is-tab .logo-name{ font-size: 17px; letter-spacing: .04em; -webkit-text-stroke: .6px currentColor; }

/* Book now is phone-only, and .btn already sets display:inline-flex — without
   this it would render on the desktop bar as an unstyled full-size pill. */
.nav .nav-cta-m{ display: none; }

/* Below 960px styles.css hides .nav-links. The CTA used to live inside that
   group, so it disappeared with it — keep that behaviour now it sits outside. */
@media (max-width: 960px){
  .nav .nav-cta{ display: none; }
  .nav.is-tab .nav-inner{ max-width: calc(100% - 24px); padding: 0 10px 0 14px; }

  /* -------- phone header: TWO LAYOUTS, one per state (Alec, 2026-08-10) ----
     AT REST, at the top of the page: the MH monogram hard left, the wordmark
     centred, burger on the right, no Book now.

     SCROLLED, in the glass tab: the monogram fades out, the wordmark moves
     hard left, Book now appears on the right — that is the point at which the
     hero's own CTA has left the screen and the tab has to carry one.

     The wordmark's centring lives on the base rule (position:absolute /
     left:50%), so at rest it needs no override at all — it is only the tab
     state that undoes it. Undoing it takes all four properties: leaving
     `left:50%` behind with position:static offsets it by half the bar. */
  .nav.is-tab .nav-wordmark{
    position: static;
    left: auto;
    top: auto;
    transform: none;
    margin-right: auto;
  }

  /* -------- the monogram, phone only (2026-08-11) --------------------------
     Alec wants the MH letter mark on the left of the white bar, gone once the
     bar becomes the glass tab. It sits BESIDE the wordmark rather than
     replacing it — the name stays exactly as it was in both states.

     images/logo-mark-charcoal.svg was already built and already in
     make-deploy.sh's allowlist (it was the v8 nav mark) but referenced
     nowhere, so this costs no new asset and cannot silently fail to deploy.

     Charcoal is correct because this only ever shows on the white bar: by the
     time the field goes dark, the mark has faded out.

     It COLLAPSES rather than merely fading. Fading alone left its ~20px box in
     the flow, and in the tab state the wordmark is a static flex item sitting
     directly after it — so the name was indented by the width of a mark that
     was no longer visible. Width carries the collapse and overflow clips the
     glyph, the same mechanism the burger beside it already uses, so the two
     leave the bar on matching easing rather than one snapping.

     visibility is what removes it from the accessibility tree, delayed by the
     length of the fade so the transition still runs. */
  .nav-mark{
    display: flex;
    align-items: center;
    flex: 0 0 auto;
    overflow: hidden;
    transition:
      opacity .28s cubic-bezier(.16,1,.3,1),
      width .3s cubic-bezier(.16,1,.3,1),
      visibility 0s linear 0s;
  }
  .nav-mark img{ display: block; width: auto; height: 26px; }
  .nav.is-tab .nav-mark{
    width: 0;
    opacity: 0;
    visibility: hidden;
    transition:
      opacity .28s cubic-bezier(.16,1,.3,1),
      width .3s cubic-bezier(.16,1,.3,1),
      visibility 0s linear .28s;
  }

  /* Book now belongs to the tab. .nav-cta-m is display:none by default and is
     switched on here rather than in the shared block below, so the at-rest bar
     never shows it. */
  .nav.is-tab .nav-cta-m{ display: inline-flex; }
  .nav .nav-right{ gap: 12px; }

  /* Book now — a fixed slice of the hero ramp, near-black through indigo and
     mauve into the dusty pink, stopping before the ramp turns coral. The
     desktop Start now pill sweeps 13s through the FULL ramp; a 100px pill in a
     56px tab spends half that cycle looking orange, so this one holds the one
     frame instead of animating. */
  .nav .nav-cta-m{
    /* No `display` here — visibility is the tab state's business, set above. */
    padding: 10px 15px;
    font-size: 13px;
    font-weight: 500;
    letter-spacing: .01em;
    color: #FFFFFF;
    background-image: linear-gradient(105deg,
      #08080A 0%, #131327 20%, #2B2848 42%, #5B5179 64%, #8E6C93 83%, #C55E8C 100%);
    /* The border stays for the box metrics; background-origin is what stops
       its 1px ring being painted with the wrapped end of the ramp — see the
       note on .nav-cta. This ramp ends in dusty pink, so the seam showed as a
       pink sliver down the left edge (Alec, 2026-08-10). */
    background-origin: border-box;
    border: 1px solid transparent;
    box-shadow: 0 4px 14px rgba(28,28,26,.18);
  }
  .nav .nav-cta-m .arrow{ color: #FFFFFF; }
  .nav .nav-cta-m:hover{ color: #FFFFFF; }
  /* On the dark glass the drop shadow does nothing but muddy the pill's edge. */
  .nav.is-tab .nav-cta-m{ box-shadow: none; }
  /* Burger is 26px of bar + 8px padding all round; the right padding above
     already provides the air, so drop its own or the pill sits too far in. */
  .nav .nav-burger{ padding: 8px 4px; }

  /* -------- the burger goes away once the bar becomes the glass tab -------
     Collapsed rather than display:none'd, so Book now slides out to the edge
     on the same easing the tab uses to shrink instead of snapping across the
     gap the burger leaves behind. width + padding carry the collapse (the
     26px bars are clipped by overflow), opacity and scale carry the fade.

     visibility is what actually takes it out of the accessibility tree —
     opacity:0 alone leaves a focusable, screen-reader-visible button — and it
     is delayed by the length of the fade so the flip out still animates.

     NOTE: this leaves no menu at all while scrolled. .nav-links are hidden
     below 960px, so the tab is Book now and the wordmark (home) only; the
     menu comes back the moment the bar returns to white at the top of the
     page. Deliberate, per Alec 2026-08-10. The body is overflow:hidden while
     the menu is open (main.js), so the burger can never vanish mid-menu. */
  .nav .nav-burger{
    overflow: hidden;
    transition:
      opacity    .3s cubic-bezier(.16,1,.3,1),
      transform  .3s cubic-bezier(.16,1,.3,1),
      width      .5s cubic-bezier(.16,1,.3,1),
      padding    .5s cubic-bezier(.16,1,.3,1),
      visibility 0s;
  }
  .nav.is-tab .nav-burger{
    width: 0;
    padding: 0;
    opacity: 0;
    transform: scale(.8);
    visibility: hidden;
    pointer-events: none;
    transition-delay: 0s, 0s, 0s, 0s, .3s;
  }
  /* With the burger gone the pill is the right-most thing in the tab, so it
     needs the air the burger's own padding used to provide. */
  .nav.is-tab .nav-inner{ padding-right: 8px; }
}

/* Narrow phones: 375px leaves ~323px of usable tab. Wordmark + pill + burger
   have to live inside that, so the wordmark steps down and the tracking pulls
   in — it is the only element here with slack. */
@media (max-width: 600px){
  .nav .logo-name{ font-size: 15px; letter-spacing: .04em; }
  .nav.is-tab .logo-name{ font-size: 15px; letter-spacing: .03em; }
  .nav .nav-cta-m{ padding: 9px 13px; font-size: 12.5px; gap: 7px; }
  .nav .nav-right{ gap: 10px; }
}

/* Below ~360px the arrow is the first thing that can go without the label
   losing meaning. styles.css also shrinks .logo-name here for the OLD lockup
   (13.5px / .22em); this page's wordmark is its own rule, so it is set again. */
@media (max-width: 380px){
  .nav .nav-cta-m .arrow{ display: none; }
  .nav .nav-cta-m{ padding: 9px 12px; font-size: 12px; }
  .nav .logo-name,
  .nav.is-tab .logo-name{ font-size: 13.5px; letter-spacing: .02em; }
}

/* The header morph is the design too, so it is no longer suppressed under
   Reduce Motion either — see the note on the hero bands below. */

/* ==========================================================================
   FIRST SECTION — gradient field
   Rebuilt in CSS rather than shipped as an image: it stays sharp at any
   viewport, weighs nothing, and every stop stays tunable. Hue runs
   near-black -> indigo -> violet -> magenta -> orange along the diagonal,
   with the warm hot-spot low and right, matching the reference.
   ========================================================================== */
/* Re-hues the gradient home-refresh.css already established (option D,
   2026-08-05) rather than inventing a new composition: same 99deg axis, same
   near-black left end so the white copy keeps its contrast, same pale-to-warm
   right end for the two cut-out models to stand on. Only the back half of the
   ramp changes — lavender/off-white becomes magenta then orange. */
/* Periwinkle palette. Composition is no longer a left-to-right ramp: the
   field is near-black and BOTH edges are pulled down with vignettes, so the
   bloom sits inboard. Bloom is centred at 57% rather than dead centre — the
   copy occupies the left ~52%, and putting the bright core mid-frame would
   push the headline onto it and cost contrast.

   Every layer is a gradient, so the field is resolution-independent: there is
   no bitmap to soften on a retina display, and it costs no download. */
.hero{
  background:
    /* --- edge vignettes: left and right corners fall to black --- */
    /* NOTE: edge darkening is NOT here — see .mh-hero-vig. On the section
       background it paints below the glow layers and has no effect. */
    /* --- the diagonal ramp itself. The reference is a BAND sweeping from the
           black lower-left up to the warm lower-right, not a bloom sitting in
           the middle, so the structure is a 115deg linear ramp and the moving
           layers are elongated lobes rotated onto that same axis. --- */
    linear-gradient(115deg,
      #08080A 0%,
      #0B0B11 14%,
      #131327 27%,
      #2B2848 39%,
      #5B5179 50%,
      #8E6C93 60%,
      #C55E8C 70%,
      #F0576F 80%,
      #FF5A57 88%,
      #F2679F 95%,
      #3A1F3E 100%) !important;
  /* The ramp is deliberately STATIC. It briefly animated background-position
     across a 260%-wide gradient, which slid the dark end of the ramp over the
     frame — the hero went near-black and colourless at parts of the cycle.
     The composition stays put; only the soft bands above it move. It also
     costs nothing: no per-frame repaint of the whole section. */
}

/* Phone keeps home-refresh.css's ROTATED composition — the same journey runs
   top-to-bottom instead of left-to-right — so its 176deg gradient needs the
   same re-hue. Without this the desktop !important above would flatten the
   phone hero back to a horizontal ramp. */
@media (max-width: 900px){
  /* Phone: the same idea rotated. Copy sits on the dark top, the bloom sits
     in the middle behind the models, and both the top and bottom edges fall
     to black — the vertical equivalent of the left/right vignettes.

     Retuned 2026-08-09 (Alec), in two passes on the same day.

     First: the top third read as flat black on a phone rather than as the dark
     end of a ramp. The top cap came down from 34% to 22% tall and from .94 to
     .88 at its core, falling off by 84% instead of 78%; the wide navy wash grew
     from 52% to 70% tall and moved up from 56% to 44%, with the indigo bloom
     enlarged and lifted to the middle to match.

     Second: even lifted, the light was a single column straight up the centre.
     A fourth lobe now sits ON the right edge (centred at 100% 34%, so half of
     it is off-frame) and carries the glow out to that side, which is what makes
     it read as a field rather than a spotlight. It is deliberately dimmer than
     the central bloom — .44 against .70 — so the composition still has a centre.

     The colour stops themselves are untouched throughout; this is all placement
     and falloff. The cap is softened, not removed, and still seats the eyebrow
     and headline: measured after the change, white copy sits at 18.5:1 over the
     headline band and 17.4:1 over the sub-copy, so there is plenty of headroom
     if this ever needs to go brighter still. */
  .hero{
    background:
      radial-gradient(ellipse 106% 22% at 50% 0%,
        rgba(2,2,6,.88) 0%, rgba(2,2,6,.38) 48%, transparent 84%),
      radial-gradient(ellipse 108% 30% at 50% 100%,
        rgba(2,2,6,.92) 0%, rgba(2,2,6,.52) 46%, transparent 76%),
      radial-gradient(ellipse 42% 22% at 54% 50%,
        rgba(216,196,234,.52) 0%, rgba(180,166,238,.28) 46%, transparent 72%),
      /* the right-edge lobe */
      radial-gradient(ellipse 54% 28% at 100% 34%,
        rgba(112,92,232,.44) 0%, rgba(72,60,190,.21) 50%, transparent 78%),
      radial-gradient(ellipse 82% 44% at 54% 50%,
        rgba(92,88,236,.70) 0%, rgba(60,52,186,.40) 46%, transparent 78%),
      radial-gradient(ellipse 116% 70% at 50% 44%,
        rgba(28,24,92,.80) 0%, transparent 78%),
      linear-gradient(180deg, #06060F 0%, #050509 50%, #020205 100%) !important;
  }
}

/* ---- movement ------------------------------------------------------------
   A drifting light layer on .hero::before, which nothing else uses. Three
   soft blobs, heavily blurred, on an oversized box (150%) so the edges never
   swing into view — .hero already clips with overflow:hidden.

   Animated with TRANSFORM only, deliberately: transforms are composited on
   the GPU, so this costs no repaint. Animating background-position instead
   would repaint a ~1280x760 gradient every frame and can visibly jank on
   lower-end machines. Slow (34s) and low-contrast, so it reads as the light
   breathing rather than something sliding about behind the copy. */
.hero::before,
.hero .mh-hero-fx{
  position: absolute;
  z-index: 0; pointer-events: none;
  will-change: transform, opacity;
}
/* Both moving layers are oversized and ROTATED onto the ramp's 115deg axis, so
   their flat ellipses read as BANDS sweeping along the diagonal rather than
   circles pulsing in place. Large enough that the rotation never swings an
   edge into view; .hero clips with overflow:hidden regardless. */
/* 220%, up from 180% (2026-08-08). Two reasons, one visual and one technical.
   Visually, translate percentages resolve against the element's OWN box, so a
   bigger box turns the same percentage into more travel across the hero.
   Technically, it buys the room for the scale trick below: the swell now runs
   0.86 -> 1.00 instead of 1.00 -> 1.18, so the layer is never drawn larger
   than the size it was rasterised at. */
.hero::before,
.hero .mh-hero-fx{ left: -60%; top: -60%; width: 220%; height: 220%; }

/* ---- edge darkening, ABOVE the glow ------------------------------------
   This is the layer that actually makes the edges dark. Its predecessors sat
   on .hero's background, which paints beneath every child — so the bloom and
   the drifting lobe (which spans well past both edges with 64px of blur)
   simply repainted over them. As an element ordered after both, it darkens
   the glow itself; ordered before .hero-photo, it leaves the models alone. */
.hero .mh-hero-vig{
  position: absolute; inset: 0; z-index: 0; pointer-events: none;
  background:
    linear-gradient(90deg,
      rgba(0,0,2,.98) 0%, rgba(0,0,2,.90) 8%, rgba(0,0,2,.62) 20%,
      rgba(0,0,2,.24) 34%, transparent 48%),
    linear-gradient(270deg,
      rgba(0,0,2,.98) 0%, rgba(0,0,2,.88) 7%, rgba(0,0,2,.58) 18%,
      rgba(0,0,2,.22) 32%, transparent 46%);
}
/* layer A — magenta and indigo, sweeping one way */
/* THE BLOOM. One large soft glow that swells and contracts behind the models
   — the reference's move is a single breathing radial, not a drifting mesh,
   so scale does the heavy lifting here and the travel is deliberately small.
   Human Purple at the core, falling through deep violet to nothing. */
/* Read from the outside in, the reference runs black -> blue -> dark purple
   -> purple -> pink, so the bloom is built in that order with pink hottest at
   the core and electric blue as the last thing before it meets the black. */
/* WARM BAND — the coral-red and pink that sit low and right in the reference.
   A flat ellipse (76% x 22%), not a circle, rotated onto the ramp's axis. */
.hero::before{
/* content:'' — WITHOUT THIS THE WHOLE LAYER IS INERT. A pseudo-element with no
   content property generates no box, so it never painted and never animated,
   however carefully mh-band-a was tuned. This band was dead from the day it
   was written (2026-08-08): the warm coral and pink you could see in the hero
   was the static 115deg ramp underneath, which happens to run through the same
   colours, so nothing looked obviously missing and every retiming pass landed
   on an element that was not there. .hero::after carries the same line for the
   grain; this block was simply never given one. */
  content: '';
/* The stop list carries the softness now, and blur() only takes the edge off.
   A radial-gradient is vector: the compositor redraws it at full device
   resolution every frame, so it cannot band or step however far the layer
   moves. filter: blur() is the opposite — it rasterises, often at reduced
   resolution on a layer this large, and THAT is what was reading as pixelated
   in the colour. Extra intermediate stops give the same falloff the 38px blur
   was providing, for free and at full resolution. */
  background:
    radial-gradient(ellipse 76% 24% at 62% 62%,
      rgba(255,92,88,.80) 0%,      /* coral-red, the hot point */
      rgba(248,94,132,.68) 24%,
      rgba(242,96,160,.52) 42%,    /* pink */
      rgba(160,86,148,.24) 64%,
      transparent 84%);
  filter: blur(22px);
  /* 8.5s -> 4.25s (2026-08-19, Mishy's call). Exactly 2x, and .mh-hero-fx below
     is halved in the same pass: the two bands only look alive because they run
     on DIFFERENT periods in opposite directions, so the ratio between them is
     the thing to preserve. Scale one and not the other and the field collapses
     back into the symmetrical pulsing circle band B exists to break up.

     Second retiming. 13s/21s -> 8.5s/11.5s on 2026-08-08 because nothing legible
     happened inside the few seconds anyone looks at a hero; this continues that
     direction rather than reversing it. 1.5x was offered and 2x was chosen from
     a side-by-side of all three. */
  animation: mh-band-a 4.25s linear infinite;
}
/* layer B — ember and violet, counter-rotating so the two never move as a
   rigid block; that opposition is what makes the field look alive rather
   than like one picture sliding about */
/* Secondary accent: a rose-violet lobe on a longer, opposing cycle. Its only
   job is to stop the bloom looking like a symmetrical pulsing circle — it
   pulls the glow slightly off-round as it drifts. Kept faint to hold the
   dark-purple reading. */
/* COOL BAND — the mauve/navy stretch that runs up-left of the warm one.
   Same flat-ellipse trick, offset along the axis, drifting the other way. */
.hero .mh-hero-fx{
  background:
    radial-gradient(ellipse 82% 22% at 46% 46%,
      rgba(150,116,178,.52) 0%,    /* mauve */
      rgba(110,92,156,.42) 28%,
      rgba(72,66,124,.30) 48%,     /* slate violet */
      rgba(24,26,58,.14) 70%,
      transparent 86%);
  filter: blur(30px);
  /* 11.5s -> 5.75s. Halved in lockstep with mh-band-a above -- see the note
     there. `reverse` is load-bearing and stays: it is what makes this band
     counter-rotate against the warm one. */
  animation: mh-band-b 5.75s linear infinite reverse;
}
/* The swell. Scale and opacity together, both composited, so it costs no
   repaint. 17s and ease-in-out means it never reads as a loop — it just
   seems to be breathing. */
/* The rotation is carried in EVERY keyframe — a transform is replaced whole,
   so leaving it out of one step would snap the band flat mid-animation.
   Translation happens after the rotation, so it slides ALONG the diagonal:
   the colour sweeps up and down the band instead of a circle inflating. */
/* Gentle. An earlier pass ran these at 0.65 -> 1.65, which stretched a blurred
   band far enough that you could see it DEFORMING rather than drifting. A
   ~1.25x swing reads as the light breathing.

   Retimed 2026-08-08: 13s/21s was slow enough that nothing legible happened
   inside the few seconds anyone actually looks at the hero — the motion was
   real but you had to wait for it. Now 7s/10s, and the travel is what does
   most of the work: 15% of a box that is itself 220% of the hero is ~33% of
   the hero's width, against ~12% before, so the colour crosses a visible
   distance rather than breathing in place.

   THE SCALE RUNS DOWNWARD ON PURPOSE — 0.86 -> 1.00, never above 1. A
   composited layer is rasterised once at its layout size; scaling it ABOVE 1
   stretches that bitmap, which is exactly how a smooth gradient acquires
   visible steps. Ending at 1.00 means the largest frame is the one drawn at
   native resolution and every other frame is a downscale, which is always
   clean. The swell is the same ~1.16x either way — only the direction of the
   rounding error changes. Keep the peak at 1. */
/* CONTINUOUS ORBITS, replacing the alternating bands (2026-08-10). Alec asked for the
   footer's movement here: the same closed circle, the same `linear`, the same lack of a
   reversal. `alternate` plays the timeline forwards then backwards, and on a drift that
   reads as a bounce — the field visibly reaches a limit and comes back.

   Eight steps on a circle, x = r(cos t - 1) and y = r sin t, so the path starts and closes
   at 0,0 and `infinite` has no seam. r is 10% of a box that is itself 220% of the hero,
   so the colour crosses about 22% of the hero's width per half-turn.

   THE ROTATION IS IN EVERY KEYFRAME on purpose — a transform is replaced whole, so
   leaving it out of one step snaps the band flat mid-animation. Scale is a constant 1
   rather than a swell: a composited layer is rasterised once at its layout size, and the
   old 0.86 -> 1 swing was there to keep the largest frame at native resolution. Holding
   it at exactly 1 achieves the same thing outright, and removes the one part of the old
   animation that could not be made to loop without a reversal.

   Opacity is likewise constant. It used to run 0.62 -> 1 with the bounce; on a closed
   loop it would have to return to its start, which makes it a pulse rather than a drift.
   The layers now sit at their full strength and only move. */
@keyframes mh-band-a{
  0%    { transform: rotate(-19deg) translate3d(  0.00%,  0.00%, 0) scale(1); }
  12.5% { transform: rotate(-19deg) translate3d( -2.93%,  7.07%, 0) scale(1); }
  25%   { transform: rotate(-19deg) translate3d(-10.00%, 10.00%, 0) scale(1); }
  37.5% { transform: rotate(-19deg) translate3d(-17.07%,  7.07%, 0) scale(1); }
  50%   { transform: rotate(-19deg) translate3d(-20.00%,  0.00%, 0) scale(1); }
  62.5% { transform: rotate(-19deg) translate3d(-17.07%, -7.07%, 0) scale(1); }
  75%   { transform: rotate(-19deg) translate3d(-10.00%,-10.00%, 0) scale(1); }
  87.5% { transform: rotate(-19deg) translate3d( -2.93%, -7.07%, 0) scale(1); }
  100%  { transform: rotate(-19deg) translate3d(  0.00%,  0.00%, 0) scale(1); }
}
@keyframes mh-band-b{
  0%    { transform: rotate(-19deg) translate3d( 0.00%,  0.00%, 0) scale(1); }
  12.5% { transform: rotate(-19deg) translate3d( 3.51%, -8.49%, 0) scale(1); }
  25%   { transform: rotate(-19deg) translate3d(12.00%,-12.00%, 0) scale(1); }
  37.5% { transform: rotate(-19deg) translate3d(20.49%, -8.49%, 0) scale(1); }
  50%   { transform: rotate(-19deg) translate3d(24.00%,  0.00%, 0) scale(1); }
  62.5% { transform: rotate(-19deg) translate3d(20.49%,  8.49%, 0) scale(1); }
  75%   { transform: rotate(-19deg) translate3d(12.00%, 12.00%, 0) scale(1); }
  87.5% { transform: rotate(-19deg) translate3d( 3.51%,  8.49%, 0) scale(1); }
  100%  { transform: rotate(-19deg) translate3d( 0.00%,  0.00%, 0) scale(1); }

/* ---- Reduce Motion: calmer, not frozen ------------------------------------
   The guard was removed entirely on 2026-08-08 because switching the drift OFF
   made the hero look like a broken still image to anyone with Reduce Motion
   enabled. That was the right diagnosis and the wrong cure: it left people who
   set that preference for vestibular reasons getting the full-strength version,
   which since the retiming travels ~33% of the hero's width every 7 seconds.

   So the motion is neither full nor absent here — it is genuinely reduced. The
   travel drops to about a fifth, the scale barely moves, and the cycles run
   four to five times longer. The field still breathes, so nothing reads as
   broken, but the per-second movement that actually triggers discomfort is
   largely gone. Same reasoning for the CTA sweep. */
/* SUPERSEDED 2026-08-10. The two hero lines are gone from this block: Alec asked for the
   hero to move "no matter what the settings are", the same call already taken on the
   footer field, and a damped variant here was landing back in the range that reads as a
   still image on his machine.

   The trade is stated rather than buried: someone who set Reduce Motion for vestibular
   reasons now gets the full hero drift. What makes it defensible is that the drift is
   low-contrast, unparallaxed, not scroll-coupled and does not flash — the mild end of
   what the setting exists to suppress — and that it is now a constant-velocity orbit with
   no reversal, which is gentler again than the accelerating bounce it replaces. The
   -calm keyframes are kept below, so restoring a damped variant is two lines.

   The CTA sweep keeps its damping: that one is a small, high-contrast element and slowing
   it costs nothing. */
@media (prefers-reduced-motion: reduce){
  .nav .nav-cta,
  .nav .nav-links .nav-cta,
  .nav.is-tab .nav-links .nav-cta{ animation-duration: 44s; }
}
@keyframes mh-band-a-calm{
  0%   { transform: rotate(-19deg) translate3d(-3%,  1%, 0) scale(.97); opacity: .74; }
  100% { transform: rotate(-19deg) translate3d( 3%, -2%, 0) scale(1);   opacity: .96; }
}
@keyframes mh-band-b-calm{
  0%   { transform: rotate(-19deg) translate3d( 3%, -1%, 0) scale(.96); opacity: .94; }
  100% { transform: rotate(-17deg) translate3d(-3%, -1%, 0) scale(1);   opacity: .80; }
}
}
/* The prefers-reduced-motion guard was REMOVED here on purpose (2026-08-08):
   the ambient drift is the design, and with the guard in place anyone with
   Reduce Motion enabled — including the people who signed this off — saw a
   still gradient and assumed the site was broken.
   It is a slow, low-contrast, non-parallax effect on a 13s/21s cycle, which
   is the mild end of what that setting exists to suppress. Restoring it is a
   two-line change if that trade stops being worth it. */
/* ---- hero copy: everything white, sub-headline stepped right down --------
   Four things in the hero were not white:
     .hero-badge      #DCCFFF  (home-refresh.css)
     .hero-title em   #9B6CFF  the purple accent word (now "More.")
     .hero-sub        rgba(255,255,255,.62)
     .hero-trust-line #DCCFFF  (home-refresh.css)
   All four are named explicitly rather than blanketing .hero * , which would
   also repaint the buttons and the avatar chips. */
.hero .hero-badge,
.hero .hero-trust-line,
.hero .hero-trust-sub,
.hero .hero-avatar-more,
.hero .hero-sub{ color: #FFFFFF; }
.hero .hero-title em{ color: #FFFFFF; }

/* 21px -> 15px. The sub was competing with the 92px headline; at 15px it
   reads as supporting copy and lets the headline carry the section. */
.hero .hero-sub{
  font-size: 15px;
  line-height: 1.55;
}

/* PHONES: smaller again (2026-08-11). The copy is longer than the line this
   replaced, and at 15px it filled most of the first screen before Book a
   consultation came into view. 13.5px with tighter leading brings the whole
   block plus the button back above the fold.

   It has to live here, not in styles.css: that file loads FIRST, so an
   identical-specificity `.hero .hero-sub` there is overruled by the 15px rule
   above and silently does nothing — which is exactly what happened on the
   first attempt. */
@media (max-width: 600px){
  .hero .hero-sub{ font-size: 12.5px; line-height: 1.5; margin-top: 12px; }
  .hero .hero-sub strong{ font-size: 13.5px; }
}

/* Headline 700 -> 500. Satoshi's Medium is the next weight down that actually
   ships in fonts/ (there is no 600 file), so this is a real weight rather
   than a synthesised one. */
.hero .hero-title{ font-weight: 500; }

/* ---- CTAs go white ------------------------------------------------------
   Both the hero button and the header's Start now. Text flips to ink, since
   the brand warm-white would be invisible on a white fill. The `.is-tab`
   selector is listed explicitly because the glass-tab rules set the CTA
   colour themselves and would otherwise win. */
/* NOTE: ink is written literally, NOT var(--charcoal). styles.css re-declares
   --charcoal as #F2F0F7 inside .hero (it is one of the deliberate dark bands),
   so var(--charcoal) here resolves to near-WHITE and the label vanishes on a
   white fill. The token names on this site do not describe their colours. */
.hero .btn-primary,
.nav .nav-cta,
.nav .nav-links .nav-cta,
.nav.is-tab .nav-links .nav-cta{
  background: #FFFFFF;
  color: #1C1C1A;
}
.hero .btn-primary:hover,
.nav .nav-cta:hover,
.nav .nav-links .nav-cta:hover,
.nav.is-tab .nav-links .nav-cta:hover{
  background: #EFEDF6;
  color: #1C1C1A;
}
.hero .btn-primary .arrow,
.nav .nav-cta .arrow{ color: inherit; }

/* ---- CTAs stepped down in size ---- */
.hero .btn-primary{ padding: 14px 26px; font-size: 15px; }
.hero .hero-learn{ font-size: 12.5px; padding: 5px 2px; }
.nav .nav-cta{ padding: 11px 20px; font-size: 14px; }

/* the Learn more rule was brand purple at 65% — white to match the rest */
.hero .hero-learn{ border-bottom-color: #FFFFFF; }
.hero .hero-learn:hover{ border-bottom-color: #FFFFFF; }

/* ---- Start now carries the hero's gradient ------------------------------
   Same 115deg ramp and the same tones as the section behind it, sized to
   220% of the pill so only a slice shows at any moment — a full ramp squeezed
   into 125px would read as muddy stripes rather than a gradient.

   This one animates background-position rather than transform. Transform is
   the right call on the hero because it is a huge layer and compositing keeps
   it free; here the element is 125x38, so the repaint is trivial and shifting
   the position is the only way to move the gradient WITHIN a fixed pill. */
.nav .nav-cta,
.nav .nav-links .nav-cta,
.nav.is-tab .nav-links .nav-cta{
  background-image: linear-gradient(115deg,
    #08080A 0%, #131327 16%, #2B2848 31%, #5B5179 46%,
    #8E6C93 58%, #C55E8C 71%, #F0576F 83%, #FF5A57 92%, #F2679F 100%);
  background-size: 220% 220%;
  background-position: 0% 50%;
  /* border-box, so the gradient paints the FULL box including under the 1px
     border. This was padding-box to stop a pink fringe bleeding through the
     rgba(255,255,255,.26) hairline the glass tab used to carry — but that
     hairline is now transparent in both states, so the clip was no longer
     protecting anything and was instead leaving a 1px unpainted ring. Against
     the near-black left end of the ramp that ring read as a white line, which
     is the seam this fixes; on the pink right end it was invisible, which is
     why it only ever showed on one side. */
  background-clip: border-box;
  /* THE PINK SEAM (fixed 2026-08-10). background-clip alone was only half the
     job: it says where the gradient is PAINTED (the full border box), while
     background-origin says where it is SIZED AND POSITIONED FROM — and that
     still defaulted to the padding box. So the tile was laid out 1px in from
     each edge, and background-repeat (repeat, by default) filled the leftover
     1px ring with the WRAP of the ramp: the hot coral #F2679F 100% end landing
     hard against the near-black 0% start on the left edge.
     At 220% background-size the wrapped sliver is vivid rather than subtle,
     which is why it read as a pink line peeking out from behind the pill.
     Sizing from the border box means one tile covers the whole element and
     there is no second tile to see. Same fix on .doctor-cta and
     .news-form .btn-primary in styles.css, which share this ramp and border. */
  background-origin: border-box;
  color: #FFFFFF;
  border: 1px solid transparent;
  box-shadow: none;
  animation: mh-cta-sweep 13s ease-in-out infinite alternate;
}
.nav .nav-cta:hover,
.nav .nav-links .nav-cta:hover,
.nav.is-tab .nav-links .nav-cta:hover{ color: #FFFFFF; }
.nav .nav-cta .arrow{ color: #FFFFFF; }

/* This used to give the tab state a rgba(255,255,255,.26) hairline. It was
   already being cancelled by the border-color:transparent rule further down,
   so it only survived as a misleading comment — removed rather than left to
   suggest the pill still has an edge treatment. */

@keyframes mh-cta-sweep{
  0%   { background-position: 0% 50%; }
  100% { background-position: 100% 50%; }
}
/* Guard removed here too — see the note on the hero bands above. */
/* The hairline and shadow here date from when this button was WHITE, which on
   an rgba(255,255,255,.85) bar genuinely would have disappeared. It carries the
   hero's ramp now — near-black at one end, hot pink at the other — so it holds
   its own edge against the bar with nothing added, and the added ring was the
   white line. Both states are now edgeless; the 1px transparent border stays
   only so the pill's box size is identical in each. */
.nav:not(.is-tab) .nav-cta,
.nav.is-tab .nav-cta{
  border: 1px solid transparent;
  box-shadow: none;
}

/* Grain. styles.css disables .hero::after with `content: none`, so it is free
   to reuse — overlay blending keeps the noise in the midtones instead of
   greying out the blacks. z-index 0 keeps it above the gradient but BELOW the
   cut-out subjects and the copy. */
.hero::after{
  content: '' !important;
  position: absolute; inset: 0; z-index: 0; pointer-events: none;
  opacity: .26; mix-blend-mode: overlay;
  /* 96px tile at a high baseFrequency: a finer, denser grain that still looks
     like grain on a 2x display instead of visible speckle. */
  background-image: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='96' height='96'%3E%3Cfilter id='n'%3E%3CfeTurbulence type='fractalNoise' baseFrequency='1.1' numOctaves='4' stitchTiles='stitch'/%3E%3C/filter%3E%3Crect width='96' height='96' filter='url(%23n)'/%3E%3C/svg%3E");
  background-size: 96px 96px;
}
/* .hero-photo is home-refresh.css's own positioning layer — absolute, pinned
   left:50%/right:0/top:0/bottom:0, with the cut-outs sized by HEIGHT off it.
   Forcing position:relative collapses it to 0px and the models vanish, so it
   is left completely alone here. Only the copy is lifted above the grain. */
/* .hero-photo is absolute inset:0 and the cut-outs are sized as a percentage
   of IT — but styles.css:427 makes .hero-inner position:relative, so the photo
   layer resolves against the padded inner box, not the section. That was fine
   while the trust row lived in .hero-inner and kept it tall. Moving the row
   out dropped it 699px -> 536px, taking the models down with it and leaving
   them floating short of the section's bottom edge.

   Making .hero-inner static hands the containing block back to .hero (already
   position:relative), so the photo layer spans the full section again and the
   models stand on its bottom edge as designed. Its z-index:1 is lost with
   static positioning, so the copy is lifted explicitly instead. */
.hero .hero-inner{ position: static; }
.hero .hero-copy{ position: relative; z-index: 3; }

/* ==========================================================================
   TRIAL — PHONE HERO, FLIPPED (2026-08-11, Alec: "just want to see how it
   looks"). NOT a settled decision. Delete this whole block to revert; nothing
   above it was edited, so removing it restores the previous hero exactly.

   Two changes, phones only:

   1. THE FIELD IS MIRRORED TOP-TO-BOTTOM, so the warm end lands at the top of
      the section instead of behind the model. The composition is built from
      radial gradients positioned with `at X% Y%`, so mirroring it is Y -> 100-Y
      on every layer and reversing the base linear. The X values are untouched —
      this is a vertical flip, not a rotation.

      The two animated layers are mirrored the same way. Their drift is carried
      by transforms in the keyframes, which are unchanged; only the centre each
      one orbits around moves.

   2. THE RIGHT-EDGE BLACK WASH IS DROPPED. .mh-hero-vig paints two washes, a
      90deg one pulling the left edge down and a 270deg one doing the right.
      Only the left survives here, so the field runs off the right edge at full
      colour instead of falling into black.

   Consequence worth watching in the preview: those washes were what guaranteed
   contrast for the white copy near the edges, and the eyebrow now sits over the
   brighter end of the ramp rather than the dark end. If this direction is kept,
   the copy contrast needs measuring before it ships.
   ========================================================================== */
@media (max-width: 900px){
  .hero{
    background:
      /* was `at 50% 0%` — the dark cap now sits at the BOTTOM */
      radial-gradient(ellipse 106% 22% at 50% 100%,
        rgba(2,2,6,.88) 0%, rgba(2,2,6,.38) 48%, transparent 84%),
      /* was `at 50% 100%` — this one caps the TOP */
      radial-gradient(ellipse 108% 30% at 50% 0%,
        rgba(2,2,6,.92) 0%, rgba(2,2,6,.52) 46%, transparent 76%),
      /* centred, so unchanged by a vertical mirror */
      radial-gradient(ellipse 42% 22% at 54% 50%,
        rgba(216,196,234,.52) 0%, rgba(180,166,238,.28) 46%, transparent 72%),
      /* the right-edge lobe, was 34% */
      radial-gradient(ellipse 54% 28% at 100% 66%,
        rgba(112,92,232,.44) 0%, rgba(72,60,190,.21) 50%, transparent 78%),
      radial-gradient(ellipse 82% 44% at 54% 50%,
        rgba(92,88,236,.70) 0%, rgba(60,52,186,.40) 46%, transparent 78%),
      /* the wide navy wash, was 44% */
      radial-gradient(ellipse 116% 70% at 50% 56%,
        rgba(28,24,92,.80) 0%, transparent 78%),
      /* base ramp reversed: 180deg -> 0deg */
      linear-gradient(0deg, #06060F 0%, #050509 50%, #020205 100%) !important;
  }

  /* layer A — the coral/pink lobe. Was `at 62% 62%`. */
  .hero::before{
    background:
      radial-gradient(ellipse 76% 24% at 62% 38%,
        rgba(255,92,88,.80) 0%,
        rgba(248,94,132,.68) 24%,
        rgba(242,96,160,.52) 42%,
        rgba(160,86,148,.24) 64%,
        transparent 84%) !important;
  }

  /* layer B — the mauve/slate lobe. Was `at 46% 46%`. */
  .hero .mh-hero-fx{
    background:
      radial-gradient(ellipse 82% 22% at 46% 54%,
        rgba(150,116,178,.52) 0%,
        rgba(110,92,156,.42) 28%,
        rgba(72,66,124,.30) 48%,
        rgba(24,26,58,.14) 70%,
        transparent 86%) !important;
  }

  /* Left wash only — the 270deg right-edge one is gone. */
  .hero .mh-hero-vig{
    background:
      linear-gradient(90deg,
        rgba(0,0,2,.98) 0%, rgba(0,0,2,.90) 8%, rgba(0,0,2,.62) 20%,
        rgba(0,0,2,.24) 34%, transparent 48%) !important;
  }
}
