/*
 Theme Name:   Bricks Child Theme
 Theme URI:    https://bricksbuilder.io/
 Description:  Use this child theme to extend Bricks.
 Author:       Bricks
 Author URI:   https://bricksbuilder.io/
 Template:     bricks
 Version:      1.1
 Text Domain:  bricks
*/
/* ==========================================================================
   ⚠⚠ READ THIS BEFORE WRITING ANY RULE IN THIS FILE — THE CASCADE HERE IS
   NOT WHAT THE PER-BLOCK COMMENTS BELOW ASSUME.

   `functions.php` enqueues this stylesheet with `['bricks-frontend']`, and
   the blocks below all say that this makes it load "AFTER Bricks". That is
   HALF TRUE and the half that is false has cost real time twice.

   Bricks prints its CSS in THREE places, and the dependency only orders us
   after the first two. Measured runtime order of <head> on this host:

       4  LINK   bricks-frontend-css   frontend-layer.min.css  (@layer bricks)
       5  STYLE  bricks-frontend-inline-css
       6  LINK   bricks-child-css      <-- THIS FILE
       8  STYLE  bricks-frontend-inline-inline-css   <-- EVERY GLOBAL CLASS,
                                                         every element rule,
                                                         the whole page's CSS

   So against a GLOBAL CLASS — which is nearly everything on this site —
   THIS FILE COMES FIRST AND LOSES EVERY TIE. `@layer` (#72) rescues us from
   frontend-layer.min.css at line 4 and from nothing else. The only thing
   that wins at line 8 is SPECIFICITY.

   Bricks emits a native setting element-type-qualified, e.g.
   `.vds-rev-cards.brxe-div{…}` or `.vds-section.brxe-section{…}` — (0,2,0).
   A rule here must therefore be (0,3,0) or better, which is why so many
   selectors below double a class. `!important` is never the answer; adding
   a class the element already carries is.

   A LOST TIE IS SILENT. No error, the rule sits right there in DevTools,
   and the page quietly keeps Bricks' value. Two shipped defects came from
   exactly this: the pinned story's dead `padding-block:0` (112px of section
   padding left on a pinned 100svh box) and the carousel's dead
   `padding-top:0` on hidden-panel siblings.

   THE GATE: `build/scrape/audit-childtheme-cascade.py`. It walks every
   selector in this file, asks CDP which rule actually wins, and lists every
   declaration here that something else overrides. Run it after ANY change
   to this file. `--selftest` must pass.
   ========================================================================== */

/* ==========================================================================
   VDS — the floating chapter rail (`.vds-rail`).

   Built at runtime by `js/vds-service.js`, which clones the in-page
   "On this page" band (`.vds-otp`). Because the rail exists only after JS
   runs, its CSS has no element and no global class to hang off in Bricks —
   so it lives here, in the child theme's own stylesheet, which
   `functions.php` already enqueues with `['bricks-frontend']` as a
   dependency. That makes it load AFTER Bricks' own CSS and UNLAYERED, so it
   beats everything in `@layer bricks` with no `!important` (handoff #72).
   It is NOT in the theme style's `css.stylesheet`: that surface is for rules
   that belong to the design system on every page, and this is furniture for
   one page type.

   PORTED FROM the live GLP comp's `.rail-toc` (preview/assets/css/flair.css,
   re-scraped 2026-09-29 — SP-12), re-expressed in our palette tokens so it
   switches with the rest of the site. The comp's measurements are kept:

     --vds-rail-w  the RESTING width. Capped in px on purpose: its job is to
                   fit between the window edge and the first character of
                   copy at 1280, where there is only ~75px to work with at a
                   20px root. The content inside still scales.
     left          the smaller of (a) the window gutter, which is what we
                   actually want, and (b) a copy guard that walks the rail
                   back toward the glass as the page margin closes up, so it
                   can never reach the first character of body copy.
                   max(.5rem, ...) is the floor — the guard goes negative
                   under ~1350 and the rail must not leave the window.
     >=1280 only   below that the margin outside the 1200px container cannot
                   hold it, and the in-page band is the whole story.

   `visibility:hidden` in the resting state, not just `opacity:0`, so the
   links leave the TAB ORDER entirely rather than becoming invisible tab
   stops.

   Dark is native: every colour is a VDS 2026 palette row that already
   carries a dark value, so there is no `[data-brx-theme]` block here (#64).
   The one exception is the opened-state shadow, which is a composite and is
   given a dark tier under Bricks' own `:root[data-brx-theme="dark"]` — the
   attribute Bricks stamps from `localStorage['brx_mode']` (#65). NOT the
   reference's `data-theme`, which is never involved on this site.
   ========================================================================== */
.vds-rail {
  position: fixed;
  z-index: 80;
  top: 50%;
  --vds-rail-w: min(3.2rem, 54px);
  left: max(.5rem, min(
    clamp(1rem, 3.2vw, 3.4rem),
    calc(50vw - (var(--vds-container) / 2) - var(--vds-rail-w) - 1rem)
  ));
  transform: translateY(-50%);
  display: none;
  width: var(--vds-rail-w);
  overflow: hidden;
  padding: .55rem .5rem;
  border-radius: var(--vds-r-md);
  background: transparent;
  border: 1px solid transparent;
  opacity: 0;
  visibility: hidden;
  pointer-events: none;
  transition: opacity .3s ease, visibility .3s ease,
              width .34s cubic-bezier(.16,1,.3,1),
              background-color .28s ease, border-color .28s ease,
              box-shadow .28s ease;
}
.vds-rail.is-on {
  opacity: 1;
  visibility: visible;
  pointer-events: auto;
}

/* The heading belongs to the opened state only, so collapsed it takes no
   room at all. */
.vds-rail-head {
  margin: 0;
  height: 0;
  padding-left: .55rem;
  font-family: var(--vds-font-display);
  font-size: .6rem;
  font-weight: 700;
  letter-spacing: .16em;
  text-transform: uppercase;
  color: var(--vds-muted);
  white-space: nowrap;
  opacity: 0;
  transition: opacity .2s ease;
}

.vds-rail-list {
  position: relative;
  list-style: none;
  margin: 0;
  padding: 0;
  display: grid;
  gap: .06rem;
}
/* A hairline spine. Without it the collapsed state is nine numbers floating
   in the margin with nothing to say they are one control; with it, it reads
   as a chapter scrubber at a glance, and the brand bar for the current
   section sits right on top of it. */
.vds-rail-list::before {
  content: "";
  position: absolute;
  left: 0;
  top: .25rem;
  bottom: .25rem;
  width: 1px;
  border-radius: 1px;
  background: linear-gradient(180deg, transparent,
              var(--vds-border-strong) 14%, var(--vds-border-strong) 86%,
              transparent);
}
.vds-rail-list li { margin: 0; }

.vds-rail-list a {
  position: relative;
  display: grid;
  grid-template-columns: 1.35rem minmax(0, 1fr);
  align-items: center;
  gap: 0 .6rem;
  padding: .34rem .25rem .34rem .55rem;
  border-radius: var(--vds-r-sm);
  color: var(--vds-muted);
  text-decoration: none;
  white-space: nowrap;
  transition: color .2s ease, background-color .2s ease;
}
/* The marker: a brand bar in the row's left padding. No tick sticking out of
   the number — that is what forced the comp's rail wider than the margin. */
/* ⚠⚠ CENTRED WITH `translateY(-50%)`, NEVER A PERCENTAGE `margin-top`
   (ROUND 4, user: "when you hover over the rail, the red line hops up two
   items"). THE BAR USED `height:60%; margin-top:-30%` TO CENTRE ITSELF, AND
   THOSE TWO PERCENTAGES DO NOT RESOLVE AGAINST THE SAME AXIS. A percentage
   `height` on an absolutely positioned box resolves against the containing
   block's HEIGHT, but a percentage `margin` — top included — ALWAYS resolves
   against its WIDTH. The rail animates from `min(3.2rem,54px)` to 19rem on
   hover, so the link went 44px -> 286px wide and the marker's offset went
   -13.2px -> -85.8px while its height stayed 20.9px. MEASURED: on hover every
   row moved DOWN 16px (the head expands and the fixed rail re-centres) while
   the marker moved UP 56.6px — 72.6px of relative travel against a 35.8px row
   pitch, i.e. exactly the "two items" reported.
   `translateY(-50%)` resolves against the element's OWN height, which is what
   the centring always meant, and is immune to the width transition. */
.vds-rail-list a::before {
  content: "";
  position: absolute;
  left: 0;
  top: 50%;
  width: 2px;
  height: 0;
  transform: translateY(-50%);
  border-radius: 2px;
  background: var(--vds-grad-brand);
  opacity: 0;
  transition: height .28s cubic-bezier(.16,1,.3,1), opacity .2s ease;
}
.vds-rail-n {
  font-family: var(--vds-font-display);
  font-size: .66rem;
  font-weight: 700;
  letter-spacing: .04em;
  text-align: right;
  transition: color .2s ease;
}
.vds-rail-t {
  font-size: .78rem;
  line-height: 1.3;
  opacity: 0;
  transition: opacity .22s ease;
}
.vds-rail-list a:hover {
  color: var(--vds-accent-ink);
  background: var(--vds-surface-2);
}
.vds-rail-list a:focus-visible {
  outline: 2px solid var(--vds-accent-ink);
  outline-offset: 1px;
}

/* Current section: brand number and a brand bar, readable without opening. */
.vds-rail-list a[aria-current="true"] { color: var(--vds-ink); }
.vds-rail-list a[aria-current="true"] .vds-rail-n { color: var(--vds-accent-ink); }
.vds-rail-list a[aria-current="true"]::before {
  height: 60%;
  opacity: 1;
}

/* "it should stay with the row you are on, or slide to the one you are
   hovering over." It now does both: at rest it sits on the current section,
   and while the list is hovered the current bar steps back and the hovered
   row takes it. Because every bar shares one geometry and one easing on a
   single vertical line, the handoff reads as the bar moving rather than as
   two bars. Pure CSS — no JS, nothing to keep in sync.
   ⚠ `:hover` is on the LIST, not the rail, so merely opening the rail (which
   hovers the padding and the head) does not dim the marker — only pointing at
   an actual row does. */
.vds-rail-list:hover a[aria-current="true"]::before {
  opacity: .22;
}
.vds-rail-list a:hover::before {
  height: 60%;
  opacity: 1;
}

/* Opened: on hover, and identically on keyboard focus. */
.vds-rail:hover,
.vds-rail:focus-within {
  width: 19rem;
  background: var(--vds-surface);
  border-color: var(--vds-border-strong);
  box-shadow: 0 1px 2px rgba(10,10,20,.06),
              0 10px 24px rgba(10,10,20,.1),
              0 28px 60px rgba(10,10,20,.14);
}
.vds-rail:hover .vds-rail-head,
.vds-rail:focus-within .vds-rail-head {
  opacity: 1;
  height: auto;
  margin-bottom: .5rem;
}
.vds-rail:hover .vds-rail-t,
.vds-rail:focus-within .vds-rail-t { opacity: 1; }

/* Bricks' OWN dark attribute, not the reference's `data-theme` (#65). */
:root[data-brx-theme="dark"] .vds-rail:hover,
:root[data-brx-theme="dark"] .vds-rail:focus-within {
  box-shadow: 0 1px 2px rgba(0,0,0,.5),
              0 14px 30px rgba(0,0,0,.45),
              0 36px 80px rgba(0,0,0,.55);
}

/* Where it is allowed to exist. A 1200px container in a 1280px window leaves
   40px of page margin plus the gutter — the tightest case the rail clears. */
@media (min-width: 1280px) {
  .vds-rail { display: block; }
}
/* A short window would put a nine-item rail over the header. */
@media (max-height: 620px) {
  .vds-rail { display: none; }
}
@media (prefers-reduced-motion: reduce) {
  .vds-rail,
  .vds-rail-list a,
  .vds-rail-list a::before,
  .vds-rail-n,
  .vds-rail-t,
  .vds-rail-head { transition: none; }
}


/* ==========================================================================
   THE PINNED HORIZONTAL STORY  (.vds-hs-on)        added 2026-09-29
   The enhanced state of the service page's `journey` section.

   WHY THIS IS HERE AND NOT IN BRICKS, which is the same reason the rail
   above is here: `.vds-hs-on` is added at RUNTIME by vds-hscroll.js and
   appears nowhere in the page's HTML. A Bricks section document may only
   contain selectors that match its own markup — one that matches nothing
   becomes a `code` element and blocks the entire import (#45) — so there is
   no global class for these rules to hang off and no way to author them
   natively. This stylesheet is enqueued with `['bricks-frontend']`, so it
   is unlayered and beats `@layer bricks` with no `!important` (#72) — but
   ⚠ NOT the page's global-class CSS, which is printed AFTER this file. See
   the cascade warning at the top: against a global class, only specificity
   wins. Several selectors below are deliberately tripled for that reason.

   THE RESTING STATE IS NOT HERE. It is authored natively, in
   `build/service-page/documents/journey.css`, and it is the real content: a
   vertical stack of opaque cards that needs no JavaScript. Everything below
   is additive and scoped under `.vds-hs-on`. If you are looking for the card
   colours, the ghost numeral or the icon plate, they are in that document.

   NEVER add `opacity: 0` to a panel and never animate one in. Panels are
   content, and content is always visible.
   ========================================================================== */

/* ⚠⚠ TRIPLED, AND THE WHOLE SECTION DEPENDS ON IT.
   This was `.vds-sjourney.vds-hs-on` — (0,2,0) — which TIES with Bricks'
   `.vds-section.brxe-section{padding-top:var(--vds-section-y);…}` and
   therefore LOSES, because the page's global-class CSS is printed AFTER
   this stylesheet (see the cascade note at the top of the pinned-story
   block). The section kept its 112px block padding, GSAP pinned a 100svh
   box 112px BELOW the viewport top, and the result was ~220px of dead
   space above the eyebrow with the cards and the progress rail hanging
   112px off the bottom of a 900px screen. That — not the head margin and
   not the panel min-height — was F-16's "it does not fit" defect.
   `.vds-section` is on the element already, so naming it costs nothing and
   says what is being beaten. Re-run `audit-childtheme-cascade.py`. */
.vds-section.vds-sjourney.vds-hs-on {
  padding-block: 0;
}

/* The pinned box. GSAP wraps this in a pin-spacer and fixes it for the
   duration of the story, so it owns a full viewport height while pinned. */
.vds-sjourney.vds-hs-on .vds-sjourney-inner {
  height: 100vh;
  height: 100svh;
  display: flex;
  flex-direction: column;
  justify-content: center;
  padding-block: clamp(1.6rem, 4vh, 3.2rem);
}

/* QA-5 (2026-10-13), ROLLED OUT TO BOTH PAGES 2026-10-13 (SP round 1, item C1).
   It shipped scoped to `.vds-hhelp` because `.vds-sjourney-*` is a SHARED kit
   and 2793 was in its own open review. Juan's service-page review then raised
   the IDENTICAL defect on 2793's `journey` ("the horizontal scroll starts too
   low, leaving a lot of headroom above it"), so the scope came off and the
   shared kit now carries it. The values are NOT forked — one rule, both pages,
   which is what handoff §3 asked for. 2793's six gates re-run on this change.

   ⚠ QA-5's original note, still the reason the rule exists:
   `justify-content:center` splits the pinned box's slack EVENLY. On the
   homepage the head + cards + rail measure ~630px inside a 900px viewport,
   so centring parked 122px of dead space above the eyebrow and the same
   below — the user's "too much white space above, the top is jarring".
   Top-aligning moves that slack to the bottom, where it reads as the
   panel's own breathing room instead of a gap the page fell into.

   ⚠ SUPERSEDED IN PART, same day: `justify-content` is back to `center`.
   Top-aligning fixed the top and moved the whole 170px of slack to the
   bottom, which the user then flagged. With `center` AND a nav-aware top
   padding the visible gap is provably SYMMETRIC — padding cancels out of
   `(viewportH - navH - content) / 2` — so top and bottom are equal at every
   viewport height, and C1b above shrinks the number they are equal to.

   THE DOUBLED `.vds-hs-on` IS LOAD-BEARING, not a typo. The base pinned-box
   rule two blocks up is `.vds-sjourney.vds-hs-on .vds-sjourney-inner` —
   (0,3,0), identical to what this would otherwise be — so without the
   doubling the two rules TIE and the winner is decided by source order
   alone. Doubling a class the element already carries is the project's
   standing answer to a tie (never `!important`), and it makes the override
   explicit at (0,4,0). */
.vds-sjourney.vds-hs-on.vds-hs-on .vds-sjourney-inner {
  justify-content: center;
  /* ⚠ THE HEADER BAR IS PART OF THIS NUMBER, and it is the reason the first
     attempt at this put the eyebrow 11px under the nav. A pinned panel is
     laid out at the VIEWPORT TOP, and since QA-5 the nav bar is parked
     there permanently — so `padding-top` here buys viewport space the nav
     is already standing on. The var is measured by vds-service.js; the
     74px fallback is the desktop bar and is only ever the pre-JS paint.
     What the reader actually sees above the eyebrow is the clamp, not the
     sum: ~45px at a 900px viewport, down from the 122px that prompted this. */
  padding-block: calc(var(--vds-headerbar-h, 74px) + clamp(1.75rem, 5vh, 3.25rem))
                 clamp(1.6rem, 4vh, 3.2rem);
}

.vds-sjourney.vds-hs-on .vds-sjourney-viewport {
  /* EXPLICIT, NOT INHERITED FROM `stretch`. The pinned inner is a flex
     column and Bricks' own container default puts `align-items: flex-start`
     on it, so a block child sizes to its CONTENT rather than filling the
     column. Same family as SP-9: the assumption that a flex child stretches
     is the thing Bricks quietly takes away. Measured 2026-09-29. */
  width: 100%;
  overflow: hidden;          /* the track is wider than the box on purpose */
  margin-top: clamp(1.2rem, 3vh, 2.2rem);
  /* Vertical panning is what drives the pin, so hand every vertical gesture
     straight to the page. Claiming the horizontal axis stops a sideways
     thumb swipe from triggering overscroll back-navigation or fighting the
     pin. */
  touch-action: pan-y;
}

/* The viewport is the keyboard handle for the story (arrows / Home / End).
   vds-hscroll.js adds the tabindex, so this ring only ever appears when it
   is actually usable. */
.vds-sjourney.vds-hs-on .vds-sjourney-viewport:focus-visible {
  outline: 3px solid var(--vds-accent-ink);
  outline-offset: 5px;
  border-radius: var(--vds-r-lg);
}

.vds-sjourney.vds-hs-on .vds-sjourney-track {
  display: flex;
  flex-wrap: nowrap;
  width: max-content;
  align-items: stretch;
  gap: clamp(1rem, 1.6vw, 1.7rem);
  will-change: transform;
}

.vds-sjourney.vds-hs-on .vds-sjourney-panel {
  flex: 0 0 auto;
  width: clamp(300px, 46vw, 620px);
  /* 36vh -> 46vh, 2026-10-13 (SP round 1, C1b). The pinned box is a fixed
     100vh and the composition inside it was only ~73% of that, so ~170px had
     nowhere to go and piled up as dead space — top-aligned it all sat at the
     bottom, centred it split in two. The honest fix is not to re-shuffle the
     slack but to REMOVE it: the cards grow with the viewport until they run
     out of room. The 280px floor and the 480px ceiling keep phones and very
     tall screens where they were. */
  min-height: clamp(280px, 46vh, 480px);
  justify-content: flex-end;   /* copy sits low, the ordinal owns the top */
}

/* ==========================================================================
   ROUND 4 (user, 2026-10-14) — THE PINNED STORY'S VERTICAL BUDGET, 2793 ONLY
   --------------------------------------------------------------------------
   Three notes, one mechanism: "the side scrolling cards are too tall. and the
   row in general still has too much space on top. the spacing above and below
   the dark cta is also not equal."

   MEASURED FIRST (§0 rule 2), live, 1440x900, at the pin:
       pinned box      0 .. 900
       header bottom   73
       head          119 .. 369   (46px under the nav)
       panel         444 .. 858   box 414px holding 258px of content
       bottom slack  858 .. 900   42px
   and in page coordinates at the pin release:
       white ABOVE the dark proof card   98px
       white BELOW it                    56px

   ⚠⚠ ALL THREE ARE THE SAME 100vh BOX, AND THE THIRD IS NOT A `#proof-numbers`
   PROBLEM AT ALL. That section's own padding is a symmetric 56/56 and always
   was. The extra 42px above it is the pinned inner's TRAILING SLACK — its
   36px `padding-bottom` plus half of the centred leftover — which stays
   behind on the page when the pin releases and reads as part of the gap.
   Tuning `#proof-numbers` would have chased it forever.

   WHY C1b's ANSWER HAD TO BE REVERSED. C1b (2026-10-13) met the same slack by
   GROWING the cards into it (36vh -> 46vh), under "the honest fix is not to
   re-shuffle the slack but to REMOVE it". That removed the slack from the BOX
   and moved it INSIDE each card: a 414px panel around 258px of content, which
   is the void between the ghost ordinal and the copy that C1b logged as an
   "accepted side effect, most visible on 2793". The user has now declined to
   accept it. C1b's own note says "cap is 480px if it ever needs pulling back".

   THE SLACK HAS TO GO SOMEWHERE, so it goes where it costs nothing: the
   VIEWPORT (the card row's clipping box) becomes the flex column's only
   growing child. The head pins to the top, the cards keep their own height,
   the rail stays at the bottom, and the leftover lands as empty space inside
   the row region where there is nothing to read. Because the children now
   fill the box exactly, `padding-bottom` is the ONLY trailing white left —
   and it is set to 0, which is what makes the gap above the dark card equal
   the gap below WITHOUT touching `#proof-numbers`.

   ⚠ `align-items:stretch` ON THE TRACK IS LEFT ALONE ON PURPOSE. The track is
   a flex ROW inside a BLOCK viewport, so it stays content-height no matter how
   tall the viewport grows — the panels still equalise to the tallest of them
   and do not stretch to the viewport. Setting `align-items:flex-start` here
   would make the panels ragged for no gain.

   ⚠⚠ THE MEDIA WRAPPER IS LOAD-BEARING, NOT TIDINESS. These selectors are
   (0,4,0)/(0,5,0), and BOTH the `@media (max-width:767px)` block and the
   `prefers-reduced-motion:reduce` hard stop below restate the same properties
   at (0,3,0). Unwrapped, this block would outrank them and silently break the
   phone layout AND the reduced-motion stack — the one thing that file calls
   NOT NEGOTIABLE. Gating on `min-width:768px` AND `no-preference` means
   neither context can ever match it, so no counter-rules are needed.

   ⚠ SCOPED `:not(.vds-hhelp)` — `.vds-sjourney-*` IS A SHARED KIT (§5A) and
   2714's `how-we-help` is the same component. C1/C1b were deliberately ONE
   rule for BOTH pages; this one is not, because the user's instruction this
   session was to leave the homepage alone. The homepage panels also carry
   more copy, so they were never as empty. If the homepage should follow,
   delete the four `:not(.vds-hhelp)` and re-run 2714's gates.
   ========================================================================== */
@media (min-width: 768px) and (min-height: 760px) and (prefers-reduced-motion: no-preference) {

  /* ⚠⚠ `height:auto` IS THE WHOLE FIX, AND IT IS WHY NOTHING ELSE HAS TO BE
     RE-SHUFFLED. The base rule forces the pinned box to `100vh/100svh`, and
     this composition does not fill that at 1440x900 — head 250 + cards + rail
     is ~730px of a 900px screen. Every previous attempt (QA-5 top-align,
     C1b grow-the-cards, and the first pass of this round which grew the
     VIEWPORT) was a different answer to the question "where does the leftover
     ~170px go". Letting the box be its own height means there IS no leftover:
     the head sits under the nav, the rail sits under the cards, and the inner
     ends flush, so the trailing white that was inflating the gap above
     `#proof-numbers` is 0 by construction.
     ⚠⚠ THIS BOX'S HEIGHT IS NOW AN INPUT TO THE PIN — SUPERSEDED BY ROUND 5
     (2026-10-14). Round 4 wrote here that `vds-hscroll.js` "computes `end`
     from the TRACK WIDTH, never from the inner's height, so a shorter box
     changes nothing about the scroll distance". That is NO LONGER TRUE. The
     engine now measures `window.innerHeight - inner.offsetHeight` — the dead
     white this `height:auto` rule leaves under the rail — and releases the pin
     that many pixels EARLY, so `#proof-numbers` rises into the band while the
     last card finishes travelling. **Change this rule's height, padding or
     `justify-content` and you change where the pin releases.** The total
     scroll cost is still `span()` and is still track-width driven; only the
     split between pinned and unpinned moves. See the ROUND 5 block at the top
     of `js/vds-hscroll.js` for the measured numbers.
     ScrollTrigger's spacer is `inner height + pin distance`, so when the pin
     releases the inner still lands flush with the section bottom — measured.
     ⚠ Round 4 also wrote that the white below the rail "is the section's own
     white ground … there is nothing to see". THE USER DISPUTED EXACTLY THAT
     in round 5 ("the gap feels like too much whitespace"), and the measurement
     agreed: 170px of it at 1440x900, on screen for the whole pin, with
     `#proof-numbers` only entering at 89.9%. It is now 80% and the band
     closes as part of the motion.

     ⚠⚠ `min-height: 760px` IS LOAD-BEARING, NOT COSMETIC. With a
     content-height box a SHORT viewport could make the composition taller
     than the screen, and a pinned element taller than the viewport scrolls
     its own bottom off and never comes back. The head is a fixed ~250px and
     does not shrink, so the margin runs out somewhere near 600px. Below
     760px tall the base 100vh + centred rule stands unchanged — the same
     height-gate pattern D5 already uses. */
  .vds-sjourney.vds-hs-on.vds-hs-on:not(.vds-hhelp) .vds-sjourney-inner {
    height: auto;
    justify-content: flex-start;
    /* Nav-aware term kept verbatim from C1b — a pinned panel is laid out at
       the viewport top and the bar is standing there. The additive clamp
       drops from ~45px to ~27px at a 900px viewport ("too much space on
       top"), and `padding-bottom` is 0 so the box ends on the rail. */
    padding-block: calc(var(--vds-headerbar-h, 74px) + clamp(1.1rem, 3vh, 2.1rem)) 0;
  }

  /* 48px -> ~21px. Part of the same "space on top" note: this and the
     viewport's own 27px margin-top were together spending 75px between the
     lead and the first card. */
  .vds-sjourney.vds-hs-on:not(.vds-hhelp) .vds-sjourney-head {
    margin-bottom: clamp(1rem, 2.4vh, 1.6rem);
  }

  /* 46vh -> 34vh. The panels' content is ~258px inside 33.6px of padding, so
     306px at a 900px viewport is close to natural and the void between the
     ghost ordinal and the copy closes. C1b's own note said "cap is 480px if
     it ever needs pulling back" — this is that.
     ⚠ `align-items:stretch` on the track is LEFT ALONE: the track is a flex
     ROW in a BLOCK viewport, so panels still equalise to the tallest of them.
     Setting `flex-start` there would only make them ragged. */
  .vds-sjourney.vds-hs-on:not(.vds-hhelp) .vds-sjourney-panel {
    min-height: clamp(260px, 34vh, 400px);
  }
}

/* Progress rail. Built by vds-hscroll.js, so it only ever exists in this
   state and needs no resting-state rule to hide it. */
.vds-sjourney.vds-hs-on .vds-sjourney-rail {
  position: relative;
  /* THE RAIL IS 0px WIDE WITHOUT THIS, and it fails silently — the JS sets
     `fill.style.width` correctly the whole way (measured at 53.38% mid-pin)
     and nothing renders, because the rail's only child is absolutely
     positioned so it has no in-flow content to size against, and the flex
     column above it is `align-items: flex-start`. Gate 5g caught it; the
     rail fill ran 0% -> 0% across the entire pin. */
  width: 100%;
  height: 3px;
  border-radius: 3px;
  background: var(--vds-border);
  overflow: hidden;
  margin-top: clamp(1.1rem, 2.4vh, 1.8rem);
}
.vds-sjourney.vds-hs-on .vds-sjourney-rail-fill {
  position: absolute;
  inset: 0 auto 0 0;
  width: 0%;
  border-radius: 3px;
  background-image: var(--vds-grad-brand);
}

/* ---------- Narrow viewport tuning, NOT a hard stop ----------
   The pinned story runs on phones too. What changes here is proportion, not
   behaviour.

   PANEL WIDTH IS THE WHOLE POINT. A full-bleed panel on a 390px screen gives
   a thumb no clue that anything exists sideways, so the reader scrolls into a
   pinned section wondering why the page is stuck. Panels are sized so the
   NEXT one is visibly cut off at the trailing edge, and that sliver is the
   affordance. Keep it above ~30px if you retune: below that it reads as a
   rendering bug rather than an invitation. */

@media (max-width: 767px) {
  .vds-sjourney.vds-hs-on .vds-sjourney-inner {
    padding-block: clamp(.9rem, 2.4vh, 1.8rem);
  }
  .vds-sjourney.vds-hs-on .vds-sjourney-viewport {
    margin-top: clamp(.9rem, 2vh, 1.5rem);
  }
  .vds-sjourney.vds-hs-on .vds-sjourney-track {
    gap: .9rem;
  }
  .vds-sjourney.vds-hs-on .vds-sjourney-panel {
    width: min(82vw, 420px);
    min-height: clamp(280px, 48svh, 460px);
    padding: 1.25rem 1.2rem;
  }
  /* The head and four cards share one 100svh box. Trim the display sizes
     rather than dropping the words: the copy is still the crawlable content
     and the reader on a phone should read it too. */
  .vds-sjourney.vds-hs-on .vds-sjourney-head {
    margin-bottom: 0;
  }
  .vds-sjourney.vds-hs-on .vds-sjourney-head h2 {
    font-size: clamp(1.35rem, 5.4vw, 1.75rem);
  }
  .vds-sjourney.vds-hs-on .vds-sjourney-head .vds-lead {
    font-size: .88rem;
    line-height: 1.45;
  }
  .vds-sjourney.vds-hs-on .vds-sjourney-ghost {
    font-size: clamp(3.6rem, 16vw, 5.4rem);
  }
  .vds-sjourney.vds-hs-on .vds-sjourney-rail {
    margin-top: clamp(.8rem, 2vh, 1.4rem);
  }
}

/* ---------- The one hard stop: prefers-reduced-motion ----------
   Belt and braces against a stale `.vds-hs-on`. vds-hscroll.js already
   refuses to build the pin for these readers; this guarantees the stack even
   if the class somehow survives a media-query transition. NOT NEGOTIABLE —
   a pinned horizontal scroll is exactly what that setting exists to
   prevent, and the reader turned it on deliberately, often for a vestibular
   disorder. Do not "simplify" it away. */

@media (prefers-reduced-motion: reduce) {
  .vds-sjourney.vds-hs-on .vds-sjourney-inner {
    height: auto;
    display: block;
    padding-block: 0;
  }
  .vds-sjourney.vds-hs-on .vds-sjourney-viewport {
    overflow: visible;
  }
  .vds-sjourney.vds-hs-on .vds-sjourney-track {
    display: grid;
    grid-template-columns: 1fr;
    width: auto;
    transform: none !important;
  }
  .vds-sjourney.vds-hs-on .vds-sjourney-panel {
    width: auto;
    min-height: 0;
    justify-content: flex-start;
  }
  .vds-sjourney.vds-hs-on .vds-sjourney-rail {
    display: none;
  }
}


/* ==========================================================================
   VERA — the site-wide AI guide.    QA F-19 (launcher) + F-17 (callout hook)
                                                             added 2026-10-12

   Built at runtime by `js/vds-vera.js`, so — exactly like `.vds-rail` above —
   none of this markup exists in any Bricks document and there is no global
   class for it to hang off. It lives here, in the child theme's own
   stylesheet, which `functions.php` enqueues with `['bricks-frontend']` as a
   dependency: that makes it load AFTER Bricks and UNLAYERED, so it beats
   everything in `@layer bricks` with no `!important` (#72).

   PORTED FROM the approved GLP homepage comp (`qa-homepage/comp/styles.css`
   ".assistant" block + `flair.css` round 4), re-expressed in VDS palette
   tokens so it switches with the rest of the site.

   DARK IS NATIVE. Every colour below is a `VDS 2026` palette row that already
   carries a dark value (#64), so there is no `[data-brx-theme]` block except
   the two places that need one on principle: the presence dot's ring, which
   has to contrast against the page rather than the button, and the panel
   shadow, which is a composite. Those use Bricks' OWN `data-brx-theme`
   attribute (#65), NEVER the comp's `data-theme`.

   NO `--vds-font-display` / `--vds-font-body` HERE, ON PURPOSE. Both are
   referenced 31 times across the live site and DEFINED NOWHERE — measured
   2026-10-12 on the home page, the service page and two stubs. An undefined
   custom property in `font-family` is invalid at computed-value time, so
   those rules silently inherit; it is invisible today only because the site
   is a single family ("Montserrat VDS"). Weight and size do the work below
   instead of adding a 32nd dead reference.

   THE CARD CTA IS `.vds-vera-cta`, NOT the site's `.vds-btn` global class.
   Bricks emits global-class CSS per page and only for the classes that page
   uses, so `.vds-btn` is absent from most pages; reusing it would render an
   unstyled link wherever a page happens to have no buttons. Verified against
   /organic-seo-services/ 2026-10-12.
   ========================================================================== */

/* ---------- launcher ---------- */

.vds-vera-launch {
  position: fixed;
  right: clamp(1rem, 3vw, 2rem);
  bottom: clamp(1rem, 3vw, 2rem);
  z-index: 90;
  display: inline-flex;
  align-items: center;
  gap: .6rem;
  padding: .8rem 1.3rem .8rem .9rem;
  border: 0;
  border-radius: var(--vds-r-pill);
  cursor: pointer;
  color: #fff;
  background-image: var(--vds-grad-brand);
  font: inherit;
  font-weight: 600;
  line-height: 1;
  box-shadow: 0 16px 40px rgba(217, 33, 40, .5);
  transition: transform .2s ease, box-shadow .2s ease,
              opacity .2s ease, visibility .2s ease;
}
.vds-vera-launch:hover { transform: translateY(-3px) scale(1.02); }
.vds-vera-launch:focus-visible {
  outline: 3px solid var(--vds-accent-ink);
  outline-offset: 3px;
}
.vds-vera-launch .vds-vera-avatar {
  width: 34px;
  height: 34px;
  border-radius: 50%;
  background: rgba(255, 255, 255, .2);
  display: grid;
  place-items: center;
}
.vds-vera-avatar svg { width: 20px; height: 20px; color: #fff; }

/* The presence dot. Round 4 of the comp's own review settled this: a crimson
   dot on a brand-red pill is decoration where it registers at all, and reads
   as an alert where it does. Green is what every messaging product uses for
   present-and-available. The 2px ring is what guarantees the edge, so it
   takes the PAGE's colour, not the button's — which is the one thing here
   that genuinely needs a dark tier. */
.vds-vera-ping {
  position: absolute;
  top: -3px;
  right: -3px;
  width: 14px;
  height: 14px;
  border-radius: 50%;
  background: #16a34a;
  box-shadow: 0 0 0 2px #fff,
              0 0 0 4px rgba(22, 163, 74, .28),
              0 2px 6px rgba(0, 0, 0, .28);
}
:root[data-brx-theme="dark"] .vds-vera-ping {
  background: #22c55e;
  box-shadow: 0 0 0 2px #14141a,
              0 0 0 4px rgba(34, 197, 94, .3),
              0 2px 6px rgba(0, 0, 0, .5);
}
/* A slow breath, so it reads as a live status light and not a painted dot. */
@media (prefers-reduced-motion: no-preference) {
  .vds-vera-ping { animation: vdsVeraOnline 2.8s ease-in-out infinite; }
  @keyframes vdsVeraOnline {
    0%, 100% { box-shadow: 0 0 0 2px #fff, 0 0 0 3px rgba(22,163,74,.34), 0 2px 6px rgba(0,0,0,.28); }
    50%      { box-shadow: 0 0 0 2px #fff, 0 0 0 7px rgba(22,163,74,0),   0 2px 6px rgba(0,0,0,.28); }
  }
  :root[data-brx-theme="dark"] .vds-vera-ping { animation-name: vdsVeraOnlineDark; }
  @keyframes vdsVeraOnlineDark {
    0%, 100% { box-shadow: 0 0 0 2px #14141a, 0 0 0 3px rgba(34,197,94,.38), 0 2px 6px rgba(0,0,0,.5); }
    50%      { box-shadow: 0 0 0 2px #14141a, 0 0 0 7px rgba(34,197,94,0),   0 2px 6px rgba(0,0,0,.5); }
  }
}

/* ---- ON A PHONE THE LAUNCHER IS THE BUBBLE ALONE ----------------------
   It is `position: fixed`, so on a narrow viewport the "Ask Vera" pill —
   ~168 x 48 — permanently occupies the bottom-right corner of EVERY page.
   Caught in the visual pass of `reviews` at 390, where it sat squarely on
   a review card's byline and the actions row beneath it, but the section
   only revealed it: a fixed control covers whatever happens to be under
   it, so padding one section just moves the collision somewhere else.
   Dropping the label is the fix that actually shrinks the footprint — from
   ~8,000 px² to ~2,600 px², about a third.

   THE LABEL IS HIDDEN, NOT REMOVED. `.vds-visually-hidden` keeps it in the
   accessibility tree, so the button's accessible name stays "Ask Vera" for
   a screen reader and for voice control ("tap Ask Vera"); `display: none`
   would leave an unlabelled button, which is a WCAG 4.1.2 failure.

   600px and not the 768 used for the arrows: between them the pill still
   clears the content comfortably, and the label is worth keeping wherever
   it fits — it is what tells a first-time visitor the bubble is a chat. */
@media (max-width: 600px) {
  .vds-vera-launch {
    padding: .8rem;
    gap: 0;
  }
  .vds-vera-launch .vds-vera-launch-label {
    position: absolute;
    width: 1px;
    height: 1px;
    padding: 0;
    margin: -1px;
    overflow: hidden;
    clip: rect(0 0 0 0);
    clip-path: inset(50%);
    white-space: nowrap;
    border: 0;
  }
}

/* While the panel is up the launcher is redundant and sits under it. */
body.vds-vera-open .vds-vera-launch {
  opacity: 0;
  visibility: hidden;
  pointer-events: none;
}

/* ---------- panel ---------- */

.vds-vera-panel {
  position: fixed;
  right: clamp(1rem, 3vw, 2rem);
  bottom: clamp(1rem, 3vw, 2rem);
  z-index: 95;
  width: min(390px, calc(100vw - 2rem));
  height: min(620px, calc(100dvh - 2rem));
  display: flex;
  flex-direction: column;
  overflow: hidden;
  background: var(--vds-surface);
  border: 1px solid var(--vds-border);
  border-radius: var(--vds-r-lg);
  box-shadow: var(--vds-card-shadow-lg);
  /* `visibility:hidden`, not `opacity:0` alone, so the whole conversation
     leaves the TAB ORDER while it is closed rather than becoming a stack of
     invisible tab stops. Same reasoning as `.vds-rail`. */
  opacity: 0;
  visibility: hidden;
  transform: translateY(24px) scale(.98);
  transform-origin: bottom right;
  transition: opacity .28s ease, transform .28s ease, visibility .28s ease;
}
body.vds-vera-open .vds-vera-panel {
  opacity: 1;
  visibility: visible;
  transform: translateY(0) scale(1);
}

.vds-vera-head {
  display: flex;
  align-items: center;
  gap: .8rem;
  padding: 1.1rem 1.2rem;
  color: #fff;
  background-image: var(--vds-grad-brand);
}
.vds-vera-head .vds-vera-avatar {
  width: 40px;
  height: 40px;
  border-radius: 50%;
  background: rgba(255, 255, 255, .2);
  display: grid;
  place-items: center;
}
.vds-vera-id b { display: block; font-size: 1rem; font-weight: 700; line-height: 1.2; }
.vds-vera-id small {
  display: flex;
  align-items: center;
  gap: .35rem;
  font-size: .78rem;
  opacity: .85;
}
.vds-vera-id small::before {
  content: "";
  width: 7px;
  height: 7px;
  border-radius: 50%;
  background: #3ff0a0;
}
/* ⚠ QA-5 (2026-10-13): the glyph was NOT CENTRED — it sat flush against the
   left edge of the circle. Measured: the × box's left offset was 0px and
   its right offset 22.8px inside a 32px button.

   The cause is that the button computed `display:block` and
   `text-align:start`. A UA `<button>` centres its content, but something in
   the theme's form reset flattens both, and this rule set neither — it set
   a width, a height and a radius and assumed the browser default would
   still be doing the centring. It was not.

   `grid` + `place-items:center` rather than restoring `text-align:center`:
   it centres on BOTH axes from one declaration, and it does not depend on
   an inherited property that has already been overridden once here. The
   vertical was only accidentally right (a 24px line box in a 32px button
   splits 4/4), so it was one line-height change away from breaking too. */
.vds-vera-close {
  margin-left: auto;
  display: grid;
  place-items: center;
  width: 32px;
  height: 32px;
  padding: 0;
  border: 0;
  border-radius: 50%;
  cursor: pointer;
  color: #fff;
  background: rgba(255, 255, 255, .15);
  font: inherit;
  font-size: 1.1rem;
  line-height: 1;
}
.vds-vera-close:focus-visible { outline: 2px solid #fff; outline-offset: 2px; }

.vds-vera-body {
  flex: 1;
  overflow-y: auto;
  display: flex;
  flex-direction: column;
  gap: .9rem;
  padding: 1.2rem;
  background: var(--vds-bg-alt);
}

/* ---------- messages ---------- */

.vds-vera-msg {
  max-width: 85%;
  padding: .8rem 1rem;
  border-radius: 16px;
  font-size: .92rem;
  line-height: 1.5;
  animation: vdsVeraMsgIn .3s ease;
}
@keyframes vdsVeraMsgIn {
  from { opacity: 0; transform: translateY(8px); }
  to   { opacity: 1; transform: translateY(0); }
}
.vds-vera-msg.is-bot {
  align-self: flex-start;
  color: var(--vds-ink);
  background: var(--vds-surface);
  border: 1px solid var(--vds-border);
  border-bottom-left-radius: 4px;
}
.vds-vera-msg.is-user {
  align-self: flex-end;
  color: #fff;
  background-image: var(--vds-grad-brand);
  border-bottom-right-radius: 4px;
}

.vds-vera-options {
  display: flex;
  flex-direction: column;
  gap: .5rem;
  margin-top: .2rem;
}
.vds-vera-option {
  text-align: left;
  padding: .7rem .9rem;
  border: 1.5px solid var(--vds-border-strong);
  border-radius: 12px;
  cursor: pointer;
  color: var(--vds-ink);
  background: var(--vds-surface);
  font: inherit;
  font-size: .9rem;
  transition: border-color .18s ease, background-color .18s ease, transform .18s ease;
}
.vds-vera-option:hover {
  border-color: var(--vds-accent-ink);
  background: var(--vds-surface-2);
  transform: translateX(3px);
}
.vds-vera-option:focus-visible {
  outline: 2px solid var(--vds-accent-ink);
  outline-offset: 2px;
}

.vds-vera-typing { display: inline-flex; gap: 4px; padding: .9rem 1rem; }
.vds-vera-typing span {
  width: 7px;
  height: 7px;
  border-radius: 50%;
  background: var(--vds-muted);
  animation: vdsVeraBlink 1.2s infinite;
}
.vds-vera-typing span:nth-child(2) { animation-delay: .2s; }
.vds-vera-typing span:nth-child(3) { animation-delay: .4s; }
@keyframes vdsVeraBlink { 0%, 60%, 100% { opacity: .3; } 30% { opacity: 1; } }

/* ---------- the result card ---------- */

.vds-vera-msg-card { max-width: 92%; }
.vds-vera-result {
  margin-top: .3rem;
  padding: 1rem;
  background: var(--vds-surface);
  border: 1px solid var(--vds-border);
  border-radius: 14px;
}
.vds-vera-result h4 {
  display: flex;
  align-items: center;
  gap: .45rem;
  margin: 0 0 .3rem;
  font-size: 1rem;
  font-weight: 700;
  color: var(--vds-ink);
}
.vds-vera-result-icon { display: inline-flex; color: var(--vds-accent-ink); }
.vds-vera-result-icon svg { width: 18px; height: 18px; }
.vds-vera-result p {
  margin: 0 0 .8rem;
  font-size: .85rem;
  line-height: 1.5;
  color: var(--vds-ink-2);
}
.vds-vera-cta {
  display: inline-flex;
  align-items: center;
  gap: .4rem;
  padding: .5rem 1rem;
  border-radius: var(--vds-r-pill);
  color: #fff;
  background-image: var(--vds-grad-brand);
  font-size: .85rem;
  font-weight: 600;
  text-decoration: none;
}
.vds-vera-cta:hover { color: #fff; text-decoration: none; }
.vds-vera-cta:focus-visible { outline: 2px solid var(--vds-accent-ink); outline-offset: 2px; }
.vds-vera-arrow { transition: transform .18s ease; }
.vds-vera-cta:hover .vds-vera-arrow { transform: translateX(3px); }

/* ---------- composer ---------- */

.vds-vera-foot {
  padding: .75rem .85rem .85rem;
  border-top: 1px solid var(--vds-border);
  background: var(--vds-surface);
}
.vds-vera-form { display: flex; align-items: center; gap: .5rem; }
.vds-vera-input {
  flex: 1 1 auto;
  min-width: 0;
  padding: .58rem .95rem;
  border: 1.5px solid var(--vds-border-strong);
  border-radius: var(--vds-r-pill);
  color: var(--vds-ink);
  background: var(--vds-surface-2);
  font: inherit;
  font-size: .9rem;
}
.vds-vera-input::placeholder { color: var(--vds-muted); }
.vds-vera-input:focus-visible {
  outline: 3px solid var(--vds-accent-ink);
  outline-offset: 1px;
  border-color: var(--vds-accent-ink);
}
.vds-vera-input:disabled { opacity: .55; }
.vds-vera-send {
  flex: 0 0 auto;
  width: 38px;
  height: 38px;
  border: 0;
  border-radius: 50%;
  cursor: pointer;
  color: #fff;
  background-image: var(--vds-grad-brand);
  display: grid;
  place-items: center;
  transition: transform .18s ease, opacity .18s ease;
}
.vds-vera-send:hover:not(:disabled) { transform: scale(1.06); }
.vds-vera-send:disabled { opacity: .45; cursor: default; }
.vds-vera-send:focus-visible { outline: 2px solid var(--vds-accent-ink); outline-offset: 2px; }
.vds-vera-send svg { width: 17px; height: 17px; }
.vds-vera-note {
  margin: .55rem 0 0;
  font-size: .72rem;
  line-height: 1.45;
  color: var(--vds-muted);
  text-align: center;
}

/* ---------- small screens ---------- */

@media (max-width: 560px) {
  .vds-vera-launch {
    bottom: calc(1rem + env(safe-area-inset-bottom, 0px));
    padding: .7rem 1.05rem .7rem .7rem;
    font-size: .92rem;
  }
  .vds-vera-launch .vds-vera-avatar { width: 30px; height: 30px; }
  .vds-vera-panel {
    bottom: calc(.75rem + env(safe-area-inset-bottom, 0px));
    height: min(620px, calc(100dvh - 1.5rem));
  }
  .vds-vera-body { padding: 1rem .9rem; }
  .vds-vera-msg, .vds-vera-msg-card { max-width: 92%; }
}

@media (prefers-reduced-motion: reduce) {
  .vds-vera-launch,
  .vds-vera-panel,
  .vds-vera-option,
  .vds-vera-send,
  .vds-vera-arrow { transition: none; }
  .vds-vera-msg { animation: none; }
  .vds-vera-typing span { animation: none; opacity: .5; }
}


/* ==========================================================================
   THE OFFICES + REVIEWS CAROUSEL  (.vds-rev-on)
   added 2026-10-12 · REWRITTEN the same evening against the comp

   The enhanced state of the home page's `reviews` section (QA F-24).
   Comp: `qa-homepage/comp/` — `#vds-offices`, styles.css:1595-1685.

   WHY THIS IS HERE AND NOT IN BRICKS — `.vds-rev-on` is added at RUNTIME by
   `vds-reviews.js` and appears nowhere in the page's HTML. A Bricks section
   document may only contain selectors that match its own markup; one that
   matches nothing becomes a `code` element and blocks the entire import
   (#45).

   ⚠ READ THE CASCADE WARNING AT THE TOP OF THIS FILE. Against a Bricks
   global class this stylesheet loses every specificity tie, so the rules
   below that fight a native setting are deliberately doubled. Gate:
   `build/scrape/audit-childtheme-cascade.py`.

   THE RESTING STATE IS NOT HERE. It is authored natively in
   `build/documents/reviews.css` and it IS the real content: eight offices
   stacked, every rating, address, review and Google link as markup, the
   card rows already sideways-scrollable, working with no JavaScript.
   Everything below is additive.

   ⚠ MUCH LESS LIVES HERE THAN IN THE FIRST BUILD, ON PURPOSE. The card row
   is now `display:flex` + `overflow-x:auto` NATIVELY, exactly as the comp's
   `.off-track` is, so this file no longer has to flip `display` on it — and
   that single change removes the (0,2,0)-vs-(0,2,0) fight §5.3 was written
   about. The arrow gutters are reserved by `.vds-rev-viewport` in the
   document too, so the JS no longer wraps anything at runtime. If you are
   tempted to add a rule here, check first whether it belongs in the
   resting state instead.
   ========================================================================== */

/* One office at a time. `display:none` is stated explicitly rather than
   leaning on the UA default for `[hidden]`: Bricks sets `display` on a great
   many elements and a bare `[hidden]` loses to any of them. Doubled because
   `.vds-rev-loc.brxe-div` carries a native `display:block`. */
.vds-rev-on .vds-rev-loc.vds-rev-loc[hidden] {
  display: none;
}

/* ⚠ THE COMP PUTS THE RATING ROW ABOVE THE TAB STRIP AND WE CANNOT, IN THE
   DOM. The comp has ONE head that its JS rewrites per office; we author one
   head PER PANEL so that the resting state is real content, which forces
   tabs-then-panels in document order. In the CAROUSEL state exactly one
   panel is visible, so the shell can become a grid and the panel can hand
   its three children straight to it with `display:contents` — head into row
   1, the tab strip into row 2, cards into 3, actions into 4. That is the
   comp's order, with no duplicated markup and no DOM surgery.

   `display:contents` and ACCESSIBILITY: the old behaviour (Chrome <89,
   Firefox <69) dropped such elements from the accessibility tree, which
   would have taken `role="tabpanel"` with it. Current browsers keep an
   element that carries an explicit role. **This is asserted by
   `build/scrape/verify-reviews.py`, which reads the real a11y tree** — if
   that gate ever fails, the fallback is to drop this block and accept
   tabs-above-head, NOT to remove the role. */
/* ⚠ TRIPLED, AND IT IS THE WHOLE MECHANISM. `.vds-rev-on` alone is (0,1,0)
   and Bricks emits `.vds-rev-widget.brxe-div{display:block}` at (0,2,0), so
   the grid never engaged: `display:contents` and all four `grid-row`s
   applied correctly to children of a BLOCK, which does nothing at all, and
   the tab strip stayed above the rating row. Measured, not guessed — this
   is QA-7 for the third time in one session, which is why the gate exists. */
.vds-rev-widget.vds-rev-widget.vds-rev-on {
  display: grid;
  grid-template-columns: 1fr;
}
.vds-rev-on .vds-rev-locs.vds-rev-locs { display: contents; }
.vds-rev-on .vds-rev-loc.vds-rev-loc   { display: contents; }
/* ⚠ `min-width: 0` IS LOAD-BEARING ON ALL FOUR — §5.4, and it cost a
   sideways-scrolling phone AGAIN. A grid item's `min-width` defaults to
   `auto`, i.e. "never shrink below your content's min-content size". The
   card row inside `.vds-rev-viewport` is a nowrap flex row whose
   min-content width is the SUM of its cards, so at 390 the 1fr track blew
   out to 1138px inside a 359px widget: the page scrolled sideways, the tab
   strip ran 1116px off the screen, and the row's own `overflow-x` never
   engaged. Doubled to (0,3,0) per QA-7. The resting state has the same trap
   one level down and `reviews.css` carries `min-width:0` on
   `.vds-rev-loc` for it. */
.vds-rev-on .vds-rev-head.vds-rev-head          { grid-row: 1; min-width: 0; }
.vds-rev-on .vds-rev-tabs.vds-rev-tabs          { grid-row: 2; min-width: 0; }
.vds-rev-on .vds-rev-viewport.vds-rev-viewport  { grid-row: 3; min-width: 0; }
.vds-rev-on .vds-rev-actions.vds-rev-actions    { grid-row: 4; min-width: 0; }
/* The stack's separator rule is meaningless when only one panel shows. */
.vds-rev-on .vds-rev-loc.vds-rev-loc + .vds-rev-loc {
  border-top: 0;
  padding-top: 0;
}

/* The tab strip becomes a real tablist, so the selected tab must LOOK
   selected — `aria-selected` alone is invisible to a sighted reader.
   comp `.off-dot[aria-selected="true"]`. */
/* ⚠ (0,4,0), AND THE EXTRA CLASS IS NOT DECORATION. The document's own
   `.vds-rev-tab:hover{color:var(--vds-accent-ink)}` is emitted by Bricks
   element-type-qualified at (0,3,0), which TIED with the (0,3,0) this rule
   had, and Bricks is printed after this file (QA-7) — so the moment the
   pointer rested on the tab it had just selected, the label went dark red
   ON the red gradient and vanished. Caught by measuring the computed
   colour, not by looking: in a screenshot it reads as a blank red pill and
   is easy to mistake for a paint artifact. The `:hover` twin is declared
   explicitly for the same reason — selected beats hover, always. */
.vds-rev-on .vds-rev-tab.vds-rev-tab[aria-selected="true"],
.vds-rev-on .vds-rev-tab.vds-rev-tab[aria-selected="true"]:hover,
.vds-rev-on .vds-rev-tab.vds-rev-tab[aria-selected="true"]:focus-visible {
  color: #fff;
  background-color: transparent;
  background-image: var(--vds-grad-brand);
  border-color: transparent;
  box-shadow: 0 6px 16px rgba(217, 33, 40, .3);
}
.vds-rev-on .vds-rev-tab:focus-visible {
  outline: 3px solid var(--vds-accent-ink);
  outline-offset: 3px;
}

/* ---- Truncation ------------------------------------------------------
   comp `.rev-text` clamps to 6 lines and `.rev-more` opens it. BOTH are
   scoped to `.vds-rev-on` and the button is built by the script, because a
   clamp with no way to expand hides content from a reader with no JS — the
   trade SP-17 refuses. With no JS every review is simply shown in full. */
.vds-rev-on .vds-rev-text {
  display: -webkit-box;
  -webkit-line-clamp: 6;
  -webkit-box-orient: vertical;
  overflow: hidden;
}
.vds-rev-on .vds-rev-card.is-open .vds-rev-text {
  -webkit-line-clamp: unset;
  overflow: visible;
}
.vds-rev-more {
  align-self: flex-start;
  margin-top: .55rem;
  padding: 0;
  border: 0;
  background: transparent;
  color: var(--vds-accent-ink);
  font: inherit;
  font-weight: 600;
  font-size: .8rem;
  line-height: 1.3;
  cursor: pointer;
}
.vds-rev-more:hover { text-decoration: underline; }
.vds-rev-more:focus-visible {
  outline: 2px solid var(--vds-accent-ink);
  outline-offset: 2px;
}

/* ---- Arrows (comp `.off-arrow`) --------------------------------------
   RED, OUTLINED, AND IN THE GUTTER — not grey and not on top of the cards,
   which is what the first build shipped. `.vds-rev-viewport` already
   reserves 46px each side in the document, so `left:0` / `right:0` lands
   them beside the row rather than over it. `top:42%` is the comp's value,
   not 50%: the row has a 1rem bottom pad for the hidden scrollbar, so the
   optical centre of the CARDS sits above the box's centre.

   SP-9/#77: `align-items` + `justify-content`, never `place-items` — a
   native grid makes Bricks emit `align-items:initial` on a
   higher-specificity selector and the align half silently dies. These
   buttons have no Bricks element at all, but the rule is kept uniform so
   nobody has to re-derive which is safe.

   Hidden until `vds-reviews.js` measures a row that actually overflows: an
   office with two reviews on a wide screen needs no arrows, and a control
   that cannot do anything is noise. `.has-arrows` is set per ROW, because
   the eight rows hold 2 to 5 cards each. */
.vds-rev-arrow {
  position: absolute;
  top: 42%;
  z-index: 2;
  display: none;
  align-items: center;
  justify-content: center;
  width: 42px;
  height: 42px;
  transform: translateY(-50%);
  border-radius: 50%;
  border: 2px solid var(--vds-red);
  background-color: var(--vds-surface);
  background-image: none;
  box-shadow: var(--vds-card-shadow);
  color: var(--vds-accent-ink);
  cursor: pointer;
  transition: background-color .2s ease, color .2s ease, border-color .2s ease;
}
.vds-rev-arrow svg { width: 20px; height: 20px; }
.vds-rev-viewport.has-arrows .vds-rev-arrow { display: flex; }
.vds-rev-arrow:hover:not(:disabled) {
  background-image: var(--vds-grad-brand);
  border-color: transparent;
  color: #fff;
}
.vds-rev-arrow:focus-visible {
  outline: 3px solid var(--vds-accent-ink);
  outline-offset: 2px;
}
.vds-rev-arrow:disabled {
  opacity: .35;
  cursor: default;
}
.vds-rev-prev { left: 0; }
.vds-rev-next { right: 0; }

@media (max-width: 560px) {
  .vds-rev-arrow { width: 34px; height: 34px; }
  .vds-rev-arrow svg { width: 16px; height: 16px; }
}


/* ==========================================================================
   GROWTH ECOSYSTEM — RUNTIME STATE ONLY  (QA F-15, 2026-10-12)

   The whole resting diagram — stage, rings, core, the eight node pills,
   the three outcome tags, every orbit coordinate, the hover and
   focus-visible states — lives in `build/documents/growth.css` and is
   compiled into real global classes. ONLY two things are here, and both
   for the same reason: they never appear in `growth.html`, so a rule for
   either would be an ORPHAN SELECTOR, and under #45 one orphan turns the
   whole document into a `code` element and blocks the write.

     1. `.is-active`  — added by vds-eco.js to the open node.
     2. `.vds-eco-pop` and its children — the card itself, built by
        vds-eco.js at runtime.

   ⚠ SPECIFICITY, PER §5.0 / QA-7. `.is-active` fights real Bricks native
   settings: the node's background, colour, border and box-shadow are all
   emitted as `.vds-eco-node.brxe-div{…}` = (0,2,0). A rule here at (0,2,0)
   TIES and LOSES, silently, because this file is printed before the page's
   global-class block. So every `.is-active` selector below DOUBLES
   `.vds-eco-node` to reach (0,3,0). Do not "simplify" them back.

   The `.vds-eco-pop` rules need no such doubling — the card is not a
   Bricks element, has no global class and nothing competes with it — but
   they are scoped under `.vds-eco-stage` anyway so they cannot leak.
   ========================================================================== */

/* ---- the open node: the comp's hover state, held ---------------------- */
.vds-eco-stage .vds-eco-node.vds-eco-node.is-active{
  background:var(--vds-grad-brand);
  color:#fff;
  border-color:transparent;
  box-shadow:0 14px 30px color-mix(in srgb,var(--vds-red) 42%,transparent);
  z-index:6;
  transform:translate(-50%,-50%) scale(1.07);
}
.vds-eco-stage .vds-eco-node.vds-eco-node.is-active .vds-eco-node-i svg{
  color:#fff;
}
.vds-eco-stage .vds-eco-node.vds-eco-node.is-active::after{
  opacity:0;
}

/* ---- the card -------------------------------------------------------- */
.vds-eco-stage .vds-eco-pop{
  position:absolute;
  z-index:20;
  width:min(272px,74%);
  padding:.95rem 1rem 1rem;
  border-radius:var(--vds-r-lg);
  background:var(--vds-surface);
  border:1px solid var(--vds-border-strong);
  box-shadow:0 1px 2px rgba(10,10,20,.06),0 10px 24px rgba(10,10,20,.1),0 30px 60px rgba(10,10,20,.16);
  opacity:0;
  visibility:hidden;
  pointer-events:none;
  transform:translateY(6px) scale(.985);
  transition:opacity .2s ease,transform .3s cubic-bezier(.16,1,.3,1),visibility .2s;
  text-align:left;
}
.vds-eco-stage .vds-eco-pop.is-visible{
  opacity:1;
  visibility:visible;
  pointer-events:auto;
  transform:none;
}
/* the 2px brand rule across the top of the card */
.vds-eco-stage .vds-eco-pop::before{
  content:"";
  position:absolute;
  left:1rem;
  right:1rem;
  top:0;
  height:2px;
  border-radius:0 0 2px 2px;
  background:var(--vds-grad-brand);
}
.vds-eco-stage .vds-eco-pop-eyebrow{
  display:block;
  font-weight:700;
  font-size:.6rem;
  line-height:1;
  letter-spacing:.16em;
  text-transform:uppercase;
  color:var(--vds-muted);
}
.vds-eco-stage .vds-eco-pop-title{
  font-size:1.02rem;
  line-height:1.2;
  letter-spacing:-.014em;
  margin:.4rem 0 .4rem;
  color:var(--vds-ink);
}
.vds-eco-stage .vds-eco-pop-desc{
  font-size:.82rem;
  line-height:1.5;
  color:var(--vds-ink-2);
  margin:0 0 .75rem;
}
.vds-eco-stage .vds-eco-pop-links{
  display:grid;
  gap:.3rem;
}
.vds-eco-stage .vds-eco-pop-link{
  display:flex;
  align-items:center;
  justify-content:space-between;
  gap:.6rem;
  font-weight:600;
  font-size:.8rem;
  line-height:1.3;
  color:var(--vds-accent-ink);
  padding:.42rem .55rem;
  border-radius:9px;
  background:color-mix(in srgb,var(--vds-red) 7%,transparent);
  transition:background-color .2s ease,color .2s ease;
}
.vds-eco-stage .vds-eco-pop-link:hover,
.vds-eco-stage .vds-eco-pop-link:focus-visible{
  text-decoration:none;
  background:color-mix(in srgb,var(--vds-red) 15%,transparent);
}
.vds-eco-stage .vds-eco-pop-link:focus-visible{
  outline:3px solid color-mix(in srgb,var(--vds-red) 70%,transparent);
  outline-offset:2px;
}
.vds-eco-stage .vds-eco-pop-arrow{
  flex:none;
  width:6px;
  height:6px;
  border-top:1.8px solid currentColor;
  border-right:1.8px solid currentColor;
  transform:rotate(45deg);
  transition:transform .22s cubic-bezier(.2,.7,.2,1);
}
.vds-eco-stage .vds-eco-pop-link:hover .vds-eco-pop-arrow{
  transform:rotate(45deg) translate(2px,-2px);
}

/* ---- dark theme ------------------------------------------------------ */
:root[data-brx-theme="dark"] .vds-eco-stage .vds-eco-pop{
  border-color:color-mix(in srgb,#ffffff 13%,transparent);
  box-shadow:0 1px 2px rgba(0,0,0,.5),0 14px 30px rgba(0,0,0,.5),0 36px 74px rgba(0,0,0,.6);
}
:root[data-brx-theme="dark"] .vds-eco-stage .vds-eco-pop-link{
  background:color-mix(in srgb,var(--vds-red) 18%,transparent);
  color:#ff8f96;
}
:root[data-brx-theme="dark"] .vds-eco-stage .vds-eco-pop-link:hover,
:root[data-brx-theme="dark"] .vds-eco-stage .vds-eco-pop-link:focus-visible{
  background:color-mix(in srgb,var(--vds-red) 30%,transparent);
}

@media (prefers-reduced-motion:reduce){
  .vds-eco-stage .vds-eco-pop{transition:opacity .01s,visibility .01s;transform:none}
  .vds-eco-stage .vds-eco-pop-arrow{transition:none}
}

/* ---- under 768: the card pins below the stack ------------------------
   On the stacked layout the nodes are `position:static` (growth.css), so
   there is no ring for the card to float over and no coordinate to anchor
   it to. `left`/`top` are overridden with `!important` here and ONLY
   here, because vds-eco.js writes them as INLINE styles and an inline
   style outranks every selector in this file no matter how specific.
   That is the one case where !important is the correct tool rather than
   a shortcut past §5.0. */
@media (max-width:767px){
  .vds-eco-stage .vds-eco-pop{
    position:relative;
    left:auto !important;
    top:auto !important;
    width:100%;
    max-width:420px;
    margin:1rem auto 0;
    display:none;
  }
  .vds-eco-stage .vds-eco-pop.is-visible{
    display:block;
  }
  .vds-eco-stage .vds-eco-node.vds-eco-node.is-active{
    transform:scale(1.04);
  }
}


/* ==========================================================================
   VDS US MAP  (QA F-23, 2026-10-12)

   PORTED, NOT RE-AUTHORED, from the approved comp's "VDS US MAP" and
   "VDS US MAP POPUP" blocks (`qa-homepage/comp/styles.css:886-1214` plus
   the one overflow-clip rule from `flair.css:1794-1801`) by
   `scratch/port-usmap.py`. Re-run that script rather than hand-editing.

   IT IS IN THE CHILD THEME AND NOT IN `footprint.css` FOR ONE REASON:
   every element it styles is built at runtime by `js/vds-usmap.js`, so
   every selector here would be an ORPHAN in the section document and #45
   turns one orphan into a `code` element that blocks the entire write.

   ⚠ SPECIFICITY IS NOT AN ISSUE IN THIS BLOCK, AND THAT IS WORTH SAYING
   OUT LOUD GIVEN §5.0. Nothing below targets a Bricks global class —
   these are runtime classes on runtime elements, so there is no
   element-type-qualified native setting to tie with and no doubled class
   is needed. The ONE exception is the stage hook itself, which IS a
   Bricks element; its rules live in `footprint.css` where they belong.

   THEME TOKENS: the comp scopes its light values to
   `:root[data-theme="light"]`. Ours sit on bare `:root` so they apply in
   the default "system" state too, where Bricks stamps no attribute at
   all — under the comp's selector every map colour would have been
   undefined for any visitor who never touched the theme toggle.
   ⚠ THE DARK TIER BELOW WAS ON THE COMP'S `:root[data-theme="dark"]` AND
   HAD THEREFORE NEVER APPLIED — the national map painted its light
   `#e6e8ec` land on a near-black page from F-23 until 2026-10-15, when the
   user authorised the swap to Bricks' own `data-brx-theme` (#65). Light
   stays on bare `:root`, for the reason just given. Same specificity
   (0,2,0), same eleven tokens, nothing else changed.
   ========================================================================== */

/* ==========================================================================
   VDS US MAP  (appended 2026-07-21) - Local Knowledge Network / National Strength
   Accurate AlbersUSA base map (light gray land, red pulsing metro markers).
   Phoenix is the emphasized home market. Fully themed for light and dark.
   Markup is injected by main.js (search "VDS US MAP"). No em or en dashes.
   ========================================================================== */

/* Map theme tokens (kept in this block so the shared header tokens stay untouched) */
:root {
  --vds-map-land: #e6e8ec;
  --vds-map-land-stroke: #dfe2e6;
  --vds-map-border: #ffffff;
  --vds-map-dot: #d92128;
  --vds-map-dot-halo: #ffffff;
  --vds-map-panel: linear-gradient(160deg, #f6f7f9, #ffffff);
  /* Footprint shading. One brand red, three documentation tiers. */
  --vds-map-shade: #d92128;
  --vds-map-shade-strong: .50;
  --vds-map-shade-solid: .30;
  --vds-map-shade-light: .19;
  --vds-star-empty: #d7dae0;
}
:root[data-brx-theme="dark"] {
  --vds-map-land: #22222a;
  --vds-map-land-stroke: #2b2b34;
  --vds-map-border: #3a3a45;
  --vds-map-dot: #d92128;
  --vds-map-dot-halo: rgba(255,255,255,.22);
  --vds-map-panel: linear-gradient(160deg, #1c1c20, #141417);
  --vds-map-shade: #d92128;
  --vds-map-shade-strong: .60;
  --vds-map-shade-solid: .38;
  --vds-map-shade-light: .20;
  --vds-star-empty: #3a3a45;
}

/* ⚠ `.vds-usmap { width: 100% }` WAS HERE AND IS DELETED. The comp's
   `.us-map` sets it, but on our build `.vds-usmap` is an AUTHORED class
   in `footprint.html`, so it compiles to a global class and Bricks
   emits `.vds-usmap.brxe-div{width:100%}` at (0,2,0). The child-theme
   copy lost that tie with an identical value — invisible, but exactly
   the dead declaration `audit-childtheme-cascade.py` exists to find.
   One owner per property. */
.vds-usmap__stage {
  position: relative;
  border-radius: var(--vds-r-xl);
  border: 1px solid var(--vds-border);
  background: var(--vds-map-panel);
  box-shadow: var(--vds-card-shadow);
  padding: clamp(1rem, 2.2vw, 1.6rem);
}
/* The frame keeps the exact 960x600 aspect so percentage-placed markers
   land on their true projected coordinates with zero letterboxing. */
.vds-usmap__frame {
  position: relative;
  width: 100%;
  aspect-ratio: 960 / 600;
}
.vds-usmap__svg {
  position: absolute; inset: 0;
  width: 100%; height: 100%;
  overflow: visible;
}
.vds-usmap__land {
  fill: var(--vds-map-land);
  stroke: var(--vds-map-land-stroke);
  stroke-width: 1;
  stroke-linejoin: round;
}
.vds-usmap__state {
  fill: var(--vds-map-shade);
  stroke: none;
  pointer-events: none;
}
.vds-usmap__state.is-strong { fill-opacity: var(--vds-map-shade-strong); }
.vds-usmap__state.is-solid  { fill-opacity: var(--vds-map-shade-solid); }
.vds-usmap__state.is-light  { fill-opacity: var(--vds-map-shade-light); }

/* Legend swatches reuse the same three steps so the key is literal. */
/* ⚠ THE LEGEND IS NOT STYLED HERE. The comp's `.us-map__legend` /
   `.us-map__chip` rules were ported and then DELETED from this block on
   purpose: unlike everything else in this file, the legend is AUTHORED
   MARKUP in `build/documents/footprint.html`, so it compiles to real
   global classes (`vds-usmap-legend`, `vds-usmap-chip`, and one modifier
   per tier) and belongs in `footprint.css` with the rest of the section.
   Keeping a copy here as well would mean two sources for one component
   and a tie the child theme loses (§5.0).

   The swatches moved from the comp's empty `<i>` child to a `::before`
   at the same time, which is also why the rules could not be reused
   verbatim: an empty `<i>` in a document is an element with no content
   for the converter to carry, and it carried an accessible name it never
   had. */

.vds-usmap__borders {
  fill: none;
  stroke: var(--vds-map-border);
  stroke-width: 1;
  vector-effect: non-scaling-stroke;
  stroke-linejoin: round;
  stroke-linecap: round;
  opacity: .85;
}

.vds-usmap__markers { position: absolute; inset: 0; pointer-events: none; }
/* ⚠ THE 24px BOX IS OURS, NOT THE COMP'S, AND IT IS A HIT-TARGET FIX.
   The comp's marker is `width:0;height:0` with the dot, the pulse ring,
   the home ring and the tag all absolutely positioned off that zero-size
   origin. Everything LOOKS right, but the only thing a finger or a mouse
   can actually hit is the 10px dot — under WCAG 2.5.8's 24x24 minimum,
   on a phone, fifteen times over. (It also made the marker invisible to
   Playwright's actionability check, which is how it was noticed: a 0x0
   box is never "visible", so `.hover()` times out against something a
   screenshot shows plainly.)

   The box is centred on the coordinate exactly as the zero-size origin
   was — `margin:-12px 0 0 -12px` on a 24px square puts its CENTRE on the
   point — and every child is re-anchored from `left:0;top:0` to
   `left:50%;top:50%` so it lands in precisely the same place. Marker
   positions are byte-identical; only the hit area changed. If you ever
   re-run `scratch/port-usmap.py`, RE-APPLY THIS — the port reproduces
   the comp's zero-size original. */
.vds-usmap__marker {
  position: absolute;
  width: 24px; height: 24px;
  margin: -12px 0 0 -12px;
  transform: translateZ(0);
  pointer-events: auto;
}
/* ⚠ THE RE-ANCHORING IS DONE IN THE CHILD RULES THEMSELVES, further
   down, NOT as an override block here. First draft put it here and it
   silently lost: `.vds-usmap__dot{left:0;top:0}` appears LATER in this
   same file at equal specificity, so source order kept the old value and
   every one of the fifteen markers drew 12px up and to the left of its
   real coordinate. The map still looked plausible — which is the whole
   problem — and it was caught only by measuring the dot's centre against
   the marker's. Search for `left: 50%` below. */
.vds-usmap__dot {
  position: absolute; left: 50%; top: 50%;
  width: 10px; height: 10px;
  margin: -5px 0 0 -5px;
  border-radius: 50%;
  background: var(--vds-map-dot);
  box-shadow: 0 0 0 2px var(--vds-map-dot-halo), 0 1px 3px rgba(0,0,0,.35);
  z-index: 2;
}
/* Blip / pulse ring */
.vds-usmap__marker::before {
  content: "";
  position: absolute; left: 50%; top: 50%;
  width: 10px; height: 10px;
  margin: -5px 0 0 -5px;
  border-radius: 50%;
  background: var(--vds-map-dot);
  opacity: .5;
  z-index: 1;
  animation: usMapPulse 2.8s ease-out infinite;
}
/* Gentle stagger so the network breathes instead of blinking in unison */
.vds-usmap__marker:nth-of-type(3n)::before { animation-delay: .5s; }
.vds-usmap__marker:nth-of-type(3n+1)::before { animation-delay: 1s; }
.vds-usmap__marker:nth-of-type(4n)::before { animation-delay: 1.5s; }

/* City tag: hover / focus reveal (Phoenix stays pinned below) */
.vds-usmap__tag {
  position: absolute; left: 50%; top: calc(50% + 9px);
  transform: translateX(-50%);
  /* ⚠ QA-12: this was `font:700 .68rem/1`, which is INVALID — the `font`
     shorthand requires a family — so all three values were dropped and the
     tag rendered at the inherited 16px/400/24px. Longhands only. */
  font-size: .68rem;
  font-weight: 700;
  line-height: 1;
  letter-spacing: -.01em;
  color: var(--vds-ink);
  background: var(--vds-surface);
  border: 1px solid var(--vds-border);
  padding: .2rem .42rem;
  border-radius: 6px;
  white-space: nowrap;
  box-shadow: var(--vds-card-shadow);
  opacity: 0;
  transition: opacity .16s ease;
  pointer-events: none;
}
.vds-usmap__marker:hover .vds-usmap__tag,
.vds-usmap__marker:focus-within .vds-usmap__tag { opacity: 1; z-index: 5; }

/* Phoenix, the home market: larger dot, stronger double ring, pinned label */
.vds-usmap__marker.is-home .vds-usmap__dot {
  width: 15px; height: 15px; margin: -7.5px 0 0 -7.5px;
  box-shadow: 0 0 0 3px var(--vds-map-dot-halo), 0 2px 7px rgba(217,33,40,.5);
  z-index: 4;
}
.vds-usmap__marker.is-home::before {
  width: 15px; height: 15px; margin: -7.5px 0 0 -7.5px;
  opacity: .65; animation-duration: 2.4s; animation-delay: 0s;
}
.vds-usmap__marker.is-home::after {
  content: "";
  position: absolute; left: 50%; top: 50%;
  width: 15px; height: 15px; margin: -7.5px 0 0 -7.5px;
  border-radius: 50%;
  border: 2px solid var(--vds-map-dot);
  opacity: .5;
  z-index: 1;
  animation: usMapPulse 2.4s ease-out .7s infinite;
}
.vds-usmap__marker.is-home .vds-usmap__tag {
  /* ⚠ was `top:12px`. The marker is 24x24, so that put the tag's TOP edge
     exactly on the dot's CENTRE and the 15px home dot (plus its 3px halo)
     sat behind it. Positioned off the centre like every other tag. */
  opacity: 1; top: calc(50% + 13px);
  color: #fff; background: var(--vds-map-dot); border-color: var(--vds-map-dot);
  box-shadow: 0 3px 10px rgba(217,33,40,.4);
  z-index: 5;
}
/* Reduced motion (2026-09-18): 16 markers each ran usMapPulse on a
   pseudo-element, which the base `*` catch-all could not reach. Stopped here
   explicitly and left in the resting state rather than mid pulse. */
@media (prefers-reduced-motion: reduce) {
  .vds-usmap__marker::before,
  .vds-usmap__marker.is-home::after {
    animation: none !important;
    transform: none !important;
  }
  .vds-usmap__marker::before { opacity: .5; }
  .vds-usmap__marker.is-home::before { opacity: .65; }
  .vds-usmap__marker.is-home::after { opacity: .5; }
}

@keyframes usMapPulse {
  0%   { transform: scale(1);   opacity: .5; }
  70%  { transform: scale(4.2); opacity: 0; }
  100% { transform: scale(4.2); opacity: 0; }
}

/* Supporting labels around the network */
@media (max-width: 520px) {
  .vds-usmap__dot { width: 8px; height: 8px; margin: -4px 0 0 -4px; }
  .vds-usmap__marker::before { width: 8px; height: 8px; margin: -4px 0 0 -4px; }
}
/* --------------------------------------------------------------------------
   VDS US MAP POPUP  (appended 2026-07-21, rev5) - hover / tap office cards
   One shared card per stage. Self-contained per-city skyline banner (SVG,
   no external images), demo office address, and star reviews. Edge-aware:
   JS clamps left within the frame and flips above / below. No em or en dashes.
   -------------------------------------------------------------------------- */
.vds-usmap__pop {
  position: absolute; left: 0; top: 0; z-index: 40;
  width: 244px; max-width: 244px;
  background: var(--vds-surface);
  border: 1px solid var(--vds-border);
  border-radius: 14px;
  box-shadow: 0 14px 38px rgba(0,0,0,.22), 0 4px 12px rgba(0,0,0,.14);
  overflow: hidden;
  opacity: 0; visibility: hidden;
  transform: translateY(5px) scale(.98);
  transform-origin: center bottom;
  transition: opacity .16s ease, transform .16s ease;
  pointer-events: none;
  will-change: transform, opacity;
}
.vds-usmap__pop.is-visible {
  opacity: 1; visibility: visible; transform: none; pointer-events: auto;
}
.vds-usmap__pop.is-below { transform-origin: center top; }
/* Pointer nub toward the marker (JS sets --ax) */
.vds-usmap__pop::after {
  content: ""; position: absolute; left: var(--ax, 50%);
  width: 12px; height: 12px; margin-left: -6px;
  background: var(--vds-surface);
  transform: rotate(45deg);
  z-index: 1;
}
.vds-usmap__pop:not(.is-below)::after {
  bottom: -6px;
  border-right: 1px solid var(--vds-border);
  border-bottom: 1px solid var(--vds-border);
}
.vds-usmap__pop.is-below::after {
  top: -6px;
  border-left: 1px solid var(--vds-border);
  border-top: 1px solid var(--vds-border);
}

/* City skyline banner (pure SVG + gradient, renders fully offline) */
.vds-usmap__pop-banner {
  position: relative; height: 88px;
  background: linear-gradient(135deg, var(--g1, #b12025), var(--g2, #d92128));
  overflow: hidden;
}
.vds-usmap__pop-sky { position: absolute; inset: 0; width: 100%; height: 100%; display: block; }
.vds-usmap__pop-sky .b { fill: rgba(6,10,20,.30); }
.vds-usmap__pop-sky .sun { fill: rgba(255,255,255,.5); }
.vds-usmap__pop-banner::after {
  content: ""; position: absolute; inset: 0; pointer-events: none;
  background: linear-gradient(to top, rgba(0,0,0,.42), rgba(0,0,0,0) 58%);
}
.vds-usmap__pop-city {
  position: absolute; left: 12px; bottom: 8px; z-index: 2;
  color: #fff;
  font-size: 1.02rem; font-weight: 800; line-height: 1;   /* QA-12 */
  letter-spacing: -.01em; text-shadow: 0 1px 5px rgba(0,0,0,.45);
}
.vds-usmap__pop-city span { font-weight: 600; opacity: .88; font-size: .78em; }

/* Body: office, address, reviews, quote */
.vds-usmap__pop-body { padding: 10px 12px 12px; }
.vds-usmap__pop-office {
  display: flex; align-items: center; gap: 7px; flex-wrap: wrap;
  font-size: .84rem; font-weight: 700; line-height: 1.15;  /* QA-12 */
  color: var(--vds-ink);
}
.vds-usmap__pop-hq {
  font-size: .56rem; font-weight: 800; line-height: 1;     /* QA-12 */
  letter-spacing: .05em;
  text-transform: uppercase; color: #fff; background: var(--vds-map-dot);
  padding: 2px 6px; border-radius: 5px;
}
.vds-usmap__pop-addr {
  margin-top: 4px; font-size: .74rem; line-height: 1.35; color: var(--vds-ink-2);
}
.vds-usmap__pop-rev {
  margin-top: 9px; display: flex; align-items: center; gap: 7px;
  padding-top: 9px; border-top: 1px solid var(--vds-border);
}
.vds-usmap__pop-rating { font-size: .82rem; font-weight: 800; line-height: 1;
  color: var(--vds-ink); }  /* QA-12 */
.vds-usmap__pop-count { font-size: .7rem; color: var(--vds-muted); }
.vds-usmap__stars { position: relative; display: inline-flex; line-height: 0; flex: none; }
.vds-usmap__stars-base { display: inline-flex; }
.vds-usmap__stars-fill {
  position: absolute; left: 0; top: 0; display: inline-flex;
  overflow: hidden; white-space: nowrap;
}
/* ⚠ The fill row is `inline-flex` + `overflow:hidden` + an inline
   `width:<pct>%`. A flex item SHRINKS before it is clipped, so at any rating
   below 5.0 the fill's five stars narrowed (measured 12.2px vs the base's
   13px) and drifted out of register — two offset star rows, both visible.
   Only Phoenix and Denver showed it; every other office is 5.0 / width:100%. */
.vds-usmap__stars svg { display: block; flex: 0 0 auto; }
.vds-usmap__stars-base svg path { fill: var(--vds-star-empty); }
.vds-usmap__stars-fill svg path { fill: var(--vds-map-dot); }
.vds-usmap__quote {
  margin-top: 9px; font-size: .72rem; line-height: 1.4; color: var(--vds-ink-2);
  border-left: 2px solid var(--vds-map-dot); padding-left: 8px;
}
.vds-usmap__quote + .vds-usmap__quote { margin-top: 7px; }
.vds-usmap__quote b {
  display: block; margin-top: 3px; font-weight: 700;
  color: var(--vds-ink); font-size: .68rem;
}
@media (prefers-reduced-motion: reduce) {
  .vds-usmap__pop { transition: opacity .12s ease; transform: none; }
  .vds-usmap__pop.is-visible { transform: none; }
}
@media (max-width: 520px) {
  .vds-usmap__pop { width: 212px; max-width: 212px; }
  .vds-usmap__pop-banner { height: 78px; }
  .vds-usmap__pop-city { font-size: .94rem; }
}

/* ==========================================================================
   END VDS US MAP
   ========================================================================== */


/* Measured: the clip has to sit on .vds-usmap__frame, not .vds-usmap__stage. The
   frame is the absolutely positioned 960x600 plotting box that owns the
   markers, and clipping the stage leaves the overflow at 392px; clipping the
   frame takes it to exactly 390. */
.vds-usmap__frame,
.vds-phxmap__frame {
  overflow: clip;
  overflow-clip-margin: 1.25rem;
}


/* ==========================================================================
   FOOTER NEWSLETTER — GRAVITY FORM 5  (QA F-26, 2026-10-12)

   The footer's "Get growth insights in your inbox" signup is GF 5, dropped
   into `.vds-footer-news-slot` on template 2712 as a native Bricks
   `shortcode` element. Everything inside that slot is PLUGIN OUTPUT built
   at runtime, so it is styled here rather than in `footer.css`.

   ⚠ WHY NOT IN `footer.css`, GIVEN `audit.css` DOES EXACTLY THIS FOR GF 3.
   It could live there — a selector ROOTED in a class that exists in the
   document (`body .vds-x.vds-x .gform_button`) passes the orphan check
   even though `.gform_button` itself is runtime. The reason it is here is
   narrower and worth stating: the footer is a TEMPLATE, and the only way
   to change `footer.css` is to re-import the whole template with
   `replaceExisting`, which wipes the shortcode element and the five seal
   elements' cleared `_width`/`_height` along with it. One CSS rule is not
   worth that round trip. **On the next genuine footer re-author, move this
   block into `footer.css` beside the audit form's equivalent.**

   SPECIFICITY: `body .vds-footer-news-col.vds-footer-news-col …` is the
   same shape audit.css uses, and for the same reason — Gravity Forms ships
   its own `.gform_button` rules and the theme has button defaults. This is
   comfortably above both, and §5.0 does not bite because none of these
   elements carries a Bricks global class for Bricks to emit a native
   setting against.
   ========================================================================== */

/* The comp puts the field and the button on one row. Gravity Forms stacks
   `.gform_body` and `.gform_footer`, so the row is rebuilt here. */
/* ⚠ QA-5 (2026-10-13): the button is now UNDER the field, on the user's
   direction. It used to be beside it, which is what the comp does — the
   comment below this block said so and it is no longer what ships. The
   column is the narrowest of the five in the footer grid, so a one-row
   field+button left the input around 11rem wide and the pair read as
   cramped; stacked, the input gets the full column.
   `align-items:stretch` + `align-self:flex-start` on the footer is what
   keeps the INPUT full-width while the BUTTON stays its own size — a bare
   column would stretch the button across the whole column too. */
body .vds-footer-news-col.vds-footer-news-col .gform_wrapper form{
  display:flex;
  flex-direction:column;
  align-items:stretch;
  gap:.6rem;
}
body .vds-footer-news-col.vds-footer-news-col .gform_body{
  width:100%;
  flex:0 0 auto;
  min-width:0;
}
body .vds-footer-news-col.vds-footer-news-col .gform_footer{
  flex:0 0 auto;
  align-self:flex-start;
  margin:0;
  padding:0;
}
body .vds-footer-news-col.vds-footer-news-col .gform_fields{
  display:block;
  grid-template-columns:none;
}
body .vds-footer-news-col.vds-footer-news-col .gfield{
  margin:0;
}
/* ⚠ NO `.gfield_label` VISUALLY-HIDDEN BLOCK, AND NO HONEYPOT
   `display:none`. Both were written here and both were DEAD: the form is
   `labelPlacement: hidden_label`, and Gravity Forms' own theme CSS
   already applies the identical treatment at higher specificity
   (`.gform_wrapper.gravity-theme .gfield…hidden_label > .gfield_label`
   and `.gform_wrapper.gravity-theme .gform_validation_container`).
   `audit-childtheme-cascade.py` flagged seven declarations losing to
   rules that set the SAME values — harmless on the page, but seven
   lines pretending to do something. Deleted rather than made to win. */
/* ⚠ THE SELECTOR CARRIES `.gform_wrapper .gfield` FOR SPECIFICITY, NOT
   FOR SCOPE, AND IT IS THE ONE RULE HERE THAT WAS GENUINELY BROKEN.
   Gravity Forms' theme sets `.gform_wrapper.gravity-theme .gfield
   input.medium{width:calc(50% - 16px / 2)}` — (0,4,1). The first draft
   here was `body .vds-x.vds-x input[type="email"]` — (0,3,2) — which
   LOSES, so the email field rendered at half the column width with the
   Subscribe button stranded beside it. Found by
   `audit-childtheme-cascade.py`, not by eye: a narrow input looks like a
   design choice. This selector is (0,5,2) and wins. */
body .vds-footer-news-col.vds-footer-news-col .gform_wrapper .gfield input[type="email"],
body .vds-footer-news-col.vds-footer-news-col .gform_wrapper .gfield input[type="text"]{
  width:100%;
  font-size:.9rem;
  line-height:1.3;
  padding:.78rem .9rem;
  color:var(--vds-ink);
  background-color:var(--vds-surface);
  border:1px solid var(--vds-border);
  border-radius:var(--vds-r-pill);
  transition:border-color var(--vds-t-base),box-shadow var(--vds-t-base);
}
body .vds-footer-news-col.vds-footer-news-col .gform_wrapper .gfield input[type="email"]:focus{
  outline:none;
  border-color:var(--vds-accent-ink);
  box-shadow:0 0 0 3px color-mix(in srgb,var(--vds-red) 22%,transparent);
}
body .vds-footer-news-col.vds-footer-news-col .gform_button,
body .vds-footer-news-col.vds-footer-news-col button[type="submit"],
body .vds-footer-news-col.vds-footer-news-col input[type="submit"]{
  display:inline-flex;
  align-items:center;
  justify-content:center;
  font-weight:600;
  font-size:.9rem;
  line-height:1.2;
  padding:.78rem 1.4rem;
  border-radius:var(--vds-r-pill);
  border:1px solid transparent;
  background:var(--vds-grad-brand);
  color:#fff;
  box-shadow:0 8px 20px rgba(217,33,40,.32);
  cursor:pointer;
  width:auto;
  transition:transform var(--vds-t-base),box-shadow var(--vds-t-base);
}
body .vds-footer-news-col.vds-footer-news-col .gform_button:hover,
body .vds-footer-news-col.vds-footer-news-col button[type="submit"]:hover,
body .vds-footer-news-col.vds-footer-news-col input[type="submit"]:hover{
  transform:translateY(-1px);
  box-shadow:0 12px 26px rgba(217,33,40,.42);
  color:#fff;
}
body .vds-footer-news-col.vds-footer-news-col .gform_button:focus-visible,
body .vds-footer-news-col.vds-footer-news-col button[type="submit"]:focus-visible,
body .vds-footer-news-col.vds-footer-news-col input[type="submit"]:focus-visible{
  outline:3px solid var(--vds-accent-ink);
  outline-offset:2px;
}
/* ⚠ THE HONEYPOT IS GF'S OWN, VIA THE FORM'S `enableHoneypot`, AND IT
   NEEDS NO CSS HERE. The first draft of GF 5 shipped an explicit field
   of type `honeypot` instead — that is NOT how GF does it, and it
   rendered as an ordinary labelled text input ("Website") sitting in
   the middle of the footer. Fixed on the form, not in CSS: the field
   was removed and `enableHoneypot: true` set through the v2 API. */
@media (prefers-reduced-motion:reduce){
  body .vds-footer-news-col.vds-footer-news-col .gform_button,
  body .vds-footer-news-col.vds-footer-news-col button[type="submit"],
  body .vds-footer-news-col.vds-footer-news-col input[type="submit"],
  body .vds-footer-news-col.vds-footer-news-col .gform_wrapper .gfield input[type="email"]{
    transition:none;
  }
}


/* ==========================================================================
   FOOTER BOTTOM ROW vs THE VERA LAUNCHER  (QA F-26, 2026-10-12)

   MEASURED, not guessed: at 1440x900 scrolled to the end of the page the
   fixed launcher occupies [1257,808 - 1408,868] and `.vds-footer-strap`
   sits at [1045,838 - 1365,858]. That is **2,114 px² of the launcher
   sitting on top of "Privacy-first. Consent managed. Built for growth."**

   The collision is not new — the old footer's copyright line was in the
   same corner — but F-26 put a third item in that row and made it
   unmissable. The row is `justify-content:space-between`, so whatever is
   last always lands exactly where the launcher lives.

   ⚠ THE FIX IS A RIGHT GUTTER, NOT BOTTOM PADDING. Bottom padding would
   add 70-90px of dead space under the footer for every visitor at every
   width, to solve a problem that only exists in one corner. A right
   gutter costs nothing vertically and simply stops the row short of the
   launcher. It is applied from 768 up because below that the row is
   `flex-direction:column` (footer.css's raw 600px query) and the last
   item is left-aligned, where the launcher is not.

   The number: the launcher's left edge is 183px from the viewport's right
   edge (151px wide + its 32px margin). The footer inner already leaves
   ~75px of page gutter at 1440, so 120px closes it with room to spare and
   still clears at 768, where the inner's own gutter is smaller.

   ⚠ (0,3,0) IS REQUIRED — §5.0 / QA-7. `.vds-footer-bottom` is a live
   global class and Bricks emits its padding as
   `.vds-footer-bottom.brxe-div{…}` = (0,2,0). A two-class selector here
   TIES and LOSES SILENTLY, because this file is printed before the
   page's global-class block.
   ========================================================================== */
@media (min-width:768px){
  .vds-footer .vds-footer-bottom.vds-footer-bottom{
    padding-right:120px;
  }
}

/* ==========================================================================
   QA-5 (2026-10-13) — STICKY HEADER, WITHOUT THE ANNOUNCEMENT BAR
   --------------------------------------------------------------------------
   ⚠ `.vds-header-bar` has carried `position:sticky;top:0` since the header
   was built and it has NEVER stuck. The CSS was not the problem. A sticky
   box cannot outlive its CONTAINING BLOCK, and the bar's parent is
   `div#header.site-header`, which is 74px tall — exactly the bar's own
   height. There is nowhere for it to travel, so it scrolls off with its
   parent. Measured: after a 1500px scroll the bar's top was -1457px.

   So the sticky belongs on `#brx-header`, whose containing block is <body>
   (the full document). A NEGATIVE top equal to the announcement bar's
   height is what excludes the announce from the pinned state: the header
   box pins 43px above the viewport, the announce rides off the top, and
   `.vds-header-bar` lands exactly at y=0.

   The height is MEASURED by vds-service.js into `--vds-announce-h`, not
   assumed — the announce text wraps to two lines below ~520px and a
   hard-coded 43px would leave a 20px gap there. The fallback is the
   desktop value so the pre-JS paint is right on the common case.

   `#brx-header` is (1,0,0) so §5.0 does not apply — no global class can
   tie it. `.vds-header-bar`'s own sticky is left in place: inert inside a
   parent its own height, and harmless once the real one works.
   ========================================================================== */
#brx-header{
  position:sticky;
  top:calc(-1 * var(--vds-announce-h, 43px));
  z-index:200;
}

/* ==========================================================================
   QA-5 — MEGA PANEL: the comp's brand hairline along the top edge
   --------------------------------------------------------------------------
   Ported from the comp verbatim in geometry (`flair.css` .mega::after,
   left/right 8%, 2px, fading to transparent at both ends) with the comp's
   indigo/cyan swapped for the VDS brand reds, which is the whole of the
   difference between the two design systems here.

   ⚠⚠ ROUND 3 (2026-10-14) — `::after` WAS NOT FREE AFTER ALL, AND THIS RULE
   WAS PRINTING A HORIZONTAL SCROLLBAR ON ALL FOUR MEGA PANELS.
   The user reported it on Service Areas; MEASURED, it was all four, and only
   while the panel is OPEN. BRICKS OWNS `.brx-dropdown-content::after` TOO —
   its open-state dropdown CSS puts `width:100%` (plus `z-index:1` and a
   `--brx-dropdown-height-before` variable its JS writes inline) on the same
   pseudo for its own hover bridge. `width` + `left` + `right` is
   OVER-CONSTRAINED in LTR, so `right` is dropped: the 2px hairline was laid
   out at left 8% with a FULL-panel width and ran 94px (73px on the 920px
   panels) past the right edge. `.vds-mega` carries `overflow-y:auto`, which
   forces computed `overflow-x:auto`, so that 94px became a scrollbar.
   Measured 1440x900, open: clientW 1178 / scrollW 1272 on both wide panels,
   918 / 991 on both narrow ones; after this edit all four are scrollW ==
   clientW. `scratch/r3/mega9.py` is the before/after probe.
   ⚠ THE FIX IS GEOMETRY-PROOF, NOT A SPECIFICITY FIGHT. Setting `left:0;
   right:0` means Bricks' `width:100%` resolves to EXACTLY the padding-box
   width and cannot overflow whichever declaration wins. The 8% inset moved
   into the gradient's STOPS, so the hairline paints byte-identically to the
   comp's (transparent to 8%, brand through the middle, transparent from 92%).
   ⚠ Do NOT "simplify" the stops back to `transparent,#d92128,#ed4753,
   transparent` with left/right insets — that is the defect, restored.
   ⚠ Our `top:0;height:2px` already defeated Bricks' bridge on this pseudo
   before this edit and still does; the working bridge is
   `.vds-nav-item.has-mega.open > .brx-submenu-toggle::after` (header.css).
   ========================================================================== */
.vds-mega::after{
  content:"";
  position:absolute;
  left:0;
  right:0;
  top:0;
  height:2px;
  border-radius:0 0 2px 2px;
  background:linear-gradient(90deg,transparent 0,transparent 8%,#d92128 36%,#ed4753 64%,transparent 92%,transparent 100%);
  opacity:.85;
  pointer-events:none;
}

/* ==========================================================================
   QA-5 — keyframes for the primary button's sheen sweep
   --------------------------------------------------------------------------
   The RULE that uses this lives on the `vds-btn-primary` global class, not
   here, so it cannot lose a §5.0 tie to Bricks' own `.vds-btn-primary.brxe-*`
   emission. Only the @keyframes is here: a keyframes block has no selector
   and therefore no specificity, so its location in the cascade is irrelevant
   and the global class's `_cssCustom` stays free of an at-rule that the
   Bricks CSS writer has never been asked to round-trip.

   Ported from the comp (`flair.css` @keyframes flairSheen) unchanged: it
   rests off-screen for the first 55% of the cycle, so the sweep reads as an
   occasional highlight rather than a loop.
   ========================================================================== */
@keyframes vdsBtnSheen{
  0%,55%{transform:translateX(-130%)}
  100%{transform:translateX(130%)}
}


/* ==========================================================================
   QA-5 (2026-10-13) — AUDIT FORM FIELD HEIGHT  ("Find Out What's Costing
   You Leads", Gravity Form 3)
   --------------------------------------------------------------------------
   The boxes were 63px tall for a 15.2px face. The cause is NOT Gravity
   Forms: it is the Bricks theme stylesheet's own form reset,

       .input, input:not([type="submit"]), select, textarea{line-height:40px}

   — confirmed with CDP `CSS.getMatchedStylesForNode`, which is the only
   honest answer to "which rule actually wins" on this host (§8: the page's
   stylesheets are inlined and `document.styleSheets` is empty). 40px of
   line box plus 10.4px of padding top and bottom is the whole 63px.

   `line-height:1` on EVERY control, not just `input` — the user's words,
   and correct: the <select> carried the identical rule, so fixing only the
   text inputs would have left the one field that is already visually
   heaviest at the old height and made the card look misaligned rather
   than tall.

   ⚠ SCOPED TO THE AUDIT FORM ON PURPOSE. That reset is site-wide and the
   assessment form (GF 4) and the contact form (GF 2) have exactly the same
   oversized boxes. Rolling it out is a one-line change — drop the
   `.vds-audit-form` scope — but it is a site-wide design change of the kind
   B-7 is about, and it would need 2793's six gates re-run. Raised with the
   user rather than taken.

   Specificity: the theme's `input:not([type="submit"])` is (0,1,1) and
   `select` is (0,0,1); this is (0,4,1) and wins outright, so no tie for
   §5.0 to lose. The theme stylesheet is also printed BEFORE this file.
   ========================================================================== */
body .vds-audit-form.vds-audit-form .gform_wrapper input:not([type="submit"]),
body .vds-audit-form.vds-audit-form .gform_wrapper select,
body .vds-audit-form.vds-audit-form .gform_wrapper textarea{
  line-height:1;
}


/* ==========================================================================
   SERVICE-AREA LEAD CARD — GF 2's `.medium` fields, full width (2026-10-15)

   WHAT WAS WRONG, AND IT WAS FOUND BY LOOKING AT A SCREENSHOT (§0 rule 1),
   not by a gate: in 3036's lead card the Name, Email and Phone inputs
   rendered at HALF the card width while the Comments textarea filled it,
   which reads as a broken form rather than a design.

   THE CAUSE IS GRAVITY FORMS' OWN PER-FIELD CONFIG, NOT OUR CSS — measured
   on three pages before touching anything (§0 rule 2):
     · GF 3 (audit), on 2714 and 2793 .... `input.large`  -> 508w of 508
     · GF 2 (contact), on /contact-us/ ... `input.medium` -> 404w of 404
     · GF 2, in this 572px card .......... `input.medium` -> 246w of 508
   `.medium` is 50% in GF's `gravity-theme` stylesheet. At /contact-us/'s
   width that is a sensible two-up; inside a narrow card it is not.

   ⚠ SO THE FIX IS SCOPED TO THIS CARD AND MUST STAY THAT WAY. GF 2 is
   SHARED with /contact-us/, and changing the field widths in the Gravity
   Forms admin would move that page too — a cross-page edit nobody asked
   for. `.vds-sa-lead-form` exists on exactly one card on one page.
   ⚠ AND IT CANNOT LIVE IN THE SECTION DOCUMENT: `.gform_wrapper`,
   `.gfield` and `.medium` are all RUNTIME plugin output, so
   `css-orphan-check.py` would flag them and gotcha #45 would block the
   whole write. The child theme is the only surface left — same reason the
   `.gform_button` block further up lives here.

   Specificity: GF's own rule is
   `.gform_wrapper.gravity-theme .gfield input.medium` at (0,4,1). This is
   (0,5,2) with the class doubled per §5.2, so it wins outright rather than
   depending on source order — and §5.2's warning is that a lost tie here
   would be completely silent.
   ========================================================================== */
body .vds-sa-lead-form.vds-sa-lead-form .gform_wrapper .gfield input.medium,
body .vds-sa-lead-form.vds-sa-lead-form .gform_wrapper .gfield select.medium,
body .vds-sa-lead-form.vds-sa-lead-form .gform_wrapper .gfield input.small,
body .vds-sa-lead-form.vds-sa-lead-form .gform_wrapper .gfield select.small{
  width:100%;
}


/* ==========================================================================
   SERVICE-AREA LEAD CARD — the TEXTAREA. (2026-10-15)

   ⚠⚠ THE PORTED FORM STYLESHEET IS HALF A KIT, AND THIS IS WHERE IT SHOWED.
   `vds-audit-slot`'s `_cssCustom` styles `input[type=text|email|tel]` and
   `select` — and NOTHING ELSE. There is no `textarea` rule anywhere in it,
   and no `textarea` in its `:focus-visible` rule either. GF 3 (the audit
   form) has no textarea, so in two closed rounds the gap could not show.
   GF 2 HAS ONE, and the Comments field therefore fell through to the UA
   default: a WHITE box. In light mode that is invisible against a white
   card. IN DARK MODE IT IS A GLARING WHITE SLAB — which is exactly how it
   was found: by looking at a dark screenshot (§0 rule 1), not by a gate.
   Every gate was green: 0 console errors, no sideways scroll, every rule
   verified present on its global class.

   ⇨ THIS IS THE SAME SHAPE AS THE REVIEWS-KIT FIND (handoff §3): reusing a
   kit is not enough when part of it was never written. There the missing
   half was twelve classes that had no global class; here it is one element
   type the ported sheet never covered.

   WHY SCOPED HERE AND NOT ADDED TO `vds-audit-slot`. That class is SHARED —
   2714's audit, 2793's audit and 3036's cta-band all carry the kit. Editing
   it would be an A5-shaped change (a shared class edited to fix one page),
   `sa-guard check` would report it as CHANGED, and both closed pages would
   need re-gating for a field neither of them has. `.vds-sa-lead-form` is on
   one card on one page.
   ⚠ `textarea` is runtime plugin output, so this cannot live in the section
   document either (gotcha #45 — orphan selector blocks the whole write).

   Declarations MIRROR the ported input rule exactly so the Comments box and
   the three inputs cannot diverge. `var(--vds-font-body)` is deliberately
   NOT restated: the ported sheet references it and IT DOES NOT EXIST on
   this site (§5.4 — measured MISSING on the live root, along with
   `--vds-ink-3`, `--vds-font-display` and `--vds-line`). The inputs inherit
   the body font through that dead declaration and so does this; adding a
   second reference to a token that does not exist would only make the next
   person think it does.
   ========================================================================== */
/* ⚠ THE CLASS IS TRIPLED, AND THAT IS LOAD-BEARING — §5.2, a lost tie is
   SILENT. The `.vds-audit-form` reset above matches a textarea too
   (`…gform_wrapper textarea{line-height:1}`) at (0,3,2), and this card
   carries BOTH classes. `line-height:1` is right for a single-line input
   and WRONG for a multi-line textarea — the lines touch. Doubling would
   only tie at (0,3,2) and leave the outcome to source order; tripling
   takes it to (0,4,2) and wins outright. Measured after upload: 1.5. */
body .vds-sa-lead-form.vds-sa-lead-form.vds-sa-lead-form .gform_wrapper textarea{
  width:100%;
  font-size:.95rem;
  line-height:1.5;
  color:var(--vds-ink);
  background:var(--vds-surface);
  border:1px solid var(--vds-border);
  border-radius:var(--vds-r-sm);
  padding:.65rem .8rem;
}
body .vds-sa-lead-form.vds-sa-lead-form.vds-sa-lead-form .gform_wrapper textarea:focus-visible{
  outline:2px solid var(--vds-accent-ink);
  outline-offset:1px;
  border-color:var(--vds-accent-ink);
}


/* ==========================================================================
   GROWTH-FLOW WEAVE — the SVG beam layer  (plan item B3, 2026-10-14)

   Styles the nodes that `js/vds-gflow.js` CREATES at runtime: the svg host
   and the veil / beam / comet paths it fills with. Ported from the comp's
   flair.css 173-198 and 395-402.

   WHY THESE LIVE HERE AND NOT ON A GLOBAL CLASS. Every element this block
   styles is built by JavaScript, so there is no Bricks element to hang a
   global class on and nothing for `create_global_classes` to emit. There is
   also no inline svg in any document to style instead: gotcha #5 blocks one
   from ever entering a Bricks document, which is the whole reason the host
   is created in JS. The child theme is the only surface left.

   SPECIFICITY — §5.0 does NOT bite here, and this is the one place on the
   site where that is true. The child theme loses every tie because Bricks
   prints the page's global-class block AFTER style.css and emits native
   settings element-type-qualified at (0,2,0). But Bricks emits NOTHING for
   a node it never rendered, so these single-class selectors compete with
   nothing and a plain (0,1,0) is enough. Do not "harden" them by doubling
   the class: it would read as if a tie existed and send the next person
   hunting for one. `audit-childtheme-cascade.py` has no live rule to
   compare these against for the same reason.

   `stroke` and `fill` are deliberately ABSENT. Both are url(#...) references
   to gradients whose ids carry a per-instance suffix (see the script header:
   SVG gradient ids are document-global and two flows on one page would
   otherwise share one set of defs), so only the script knows the id and it
   sets those two properties inline.

   `overflow:visible` matters: the comets overshoot the viewBox by design at
   the end of their run, and the default `overflow:hidden` on an svg would
   clip the tail mid-flight.
   ========================================================================== */
.vds-gfw{
  position:absolute;
  inset:0;
  width:100%;
  height:100%;
  z-index:0;
  pointer-events:none;
  overflow:visible;
}

.vds-gfw-veil{opacity:0;transition:opacity .9s ease .25s}
[data-growthflow].is-flowing .vds-gfw-veil{opacity:1}

.vds-gfw-line{
  fill:none;
  stroke-width:1.25;
  stroke-linecap:round;
  vector-effect:non-scaling-stroke;
}

.vds-gfw-comet{
  fill:none;
  stroke-width:2.75;
  stroke-linecap:round;
  vector-effect:non-scaling-stroke;
  filter:drop-shadow(0 0 4px color-mix(in srgb, var(--vds-red-mid) 75%, transparent));
}

/* The script already returns before animating under reduce; this is the
   static end state it leaves behind, so the graphic still reads as a funnel
   with the beams drawn and nothing in motion. */
@media (prefers-reduced-motion: reduce){
  .vds-gfw-comet{display:none}
  .vds-gfw-veil{opacity:1;transition:none}
}


/* ==========================================================================
   B1 (2026-10-14) — HERO FLAIR: the motion the comp has and we did not
   --------------------------------------------------------------------------
   MEASURED FIRST (§0 rule 2), and the plan's claim held this time. On the
   live pages before this block:

     .vds-hero::after / .vds-shero::after  animation-name: none  (static wash)
     .vds-hero::before / .vds-shero::before  content: none        (no 2nd bloom)
     .vds-grad-text                        background-size: auto, animation none
     .vds-eyebrow::before/::after          bars present (25.6x2px), animation none
     .vds-gf-engine-core                   animation: none

   Ported from the comp's `flair.css` lines 25-73. TIMINGS ARE VERBATIM
   (17s / 21s / 6.5s / 7.5s / 3.4s / 3.6s). THE BLOOM INTENSITIES ARE NOT,
   and that is deliberate:

     comp  ::before rgba(217,33,40,.45) + blur(72px)
     comp  ::after  rgba(237,71,83,.34) + blur(72px)
     ours  ::after  rgba(237,71,83,.16) (home) / --vds-grad-brand-soft .12 (service)

   Porting the comp's alphas would be a REDESIGN of the hero ground, not the
   missing motion B1 asks for. Our wash values were tuned on purpose —
   `hero.css` documents why the service blob is smaller and higher than the
   homepage's — and A2 ("hero gradient is too white") is still open and is
   explicitly a MEASURE-FIRST item. Changing the ground here would pre-empt
   it and make A2's measurement read against a surface we had just moved.
   So: animate what is there, add the comp's SECOND bloom at OUR alpha.

   ⚠ OUR `::after` IS THE COMP'S `::before` SLOT. Both our heroes draw their
   existing wash top-RIGHT; the comp's `::before` is the top-right one and
   its `::after` is the bottom-left. Mapping drift1 onto our `::after` and
   adding the bottom-left bloom as a NEW `::before` is therefore the port
   that keeps the composition, not a transposition of the pseudo-names.
   A naive verbatim port would have put two blooms in the same corner and
   left the other empty.

   ⚠ SPECIFICITY (§5.2 — the child theme loses every tie). These selectors
   are all class-doubled. The rules they must outrank are emitted from the
   page's global-class block, which Bricks prints AFTER style.css:
     `.vds-shero::after`              (0,1,1) -> ours (0,2,1)
     `.vds-eyebrow::before/::after`   (0,1,1) -> ours (0,2,1)
     `.vds-shero-flow`                (0,1,0) -> ours (0,2,0)
     `.vds-gf-engine-core`            (0,1,0) -> ours (0,3,0)
   No `!important` anywhere, per the same rule.

   ⚠ `isolation:isolate` IS DELIBERATELY NOT PORTED. The comp needs it
   because its blooms sit at `z-index:-1`; ours sit at `z-index:0` under an
   inner box that is already `position:relative;z-index:1`, so the stacking
   works without opening a new context that the header, the Vera widget and
   the theme toggle would then have to be reasoned about against.

   ⚠ `overflow:hidden` on both hero sections is LOAD-BEARING for this block —
   the bottom-left bloom is placed outside the section's box on two sides and
   the section is the only clipper. Verified live before writing: both
   `.vds-hero` and `.vds-shero` compute `overflow: hidden`.

   SCOPE, and where the line is drawn against the homepage freeze (§4):
   items 1-4 are hero GROUND and TYPE and run on both pages, exactly as the
   button sheen (B2) already does — the plan asks for one design across the
   two heroes. Items 5 and 6 are the growth-flow GRAPHIC, which on 2714 is
   the right column the user froze pending a replacement option, so they are
   scoped `.vds-shero` and touch 2793 only. ⚠ When that option is chosen,
   revisit: `.vds-shero-flow` is service-only by name, but
   `vds-gf-engine-core` is SHARED (§5A) and the `.vds-shero ` prefix is the
   only thing keeping the homepage engine still.

   ⚠ The whole block is inside `prefers-reduced-motion: no-preference`, so
   there is nothing to switch off in the `reduce` blocks above: with no
   declaration there is no animation to cancel. That is the comp's own
   structure and it is why `flairPulse`'s rest value had to equal the
   element's real one — `.vds-gf-engine-core` ships
   `box-shadow:0 12px 30px rgba(217,33,40,.3)` and the 0%/100% keyframe is
   byte-identical, so a reader with `reduce` sees the same card as one
   without it at rest.
   ========================================================================== */
@media (prefers-reduced-motion: no-preference){

  /* 1 — BOTH blooms drift, and the pseudo names now map 1:1 onto the comp's
     (ROUND 4). B1 wrote "OUR ::after IS THE COMP'S ::before SLOT" and mapped
     drift1 onto `::after` to keep the composition. That note is now WRONG and
     has been unwound: the ground was re-cut verbatim in round 4, so
     `::before` IS the comp's top-right bloom and `::after` IS its top-left
     one. drift1 -> ::before, drift2 -> ::after, exactly as flair.css has it. */
  .vds-hero.vds-hero::before,
  .vds-shero.vds-shero::before{
    animation:vdsHeroDrift1 17s ease-in-out infinite alternate;
    will-change:transform;
  }
  .vds-hero.vds-hero::after,
  .vds-shero.vds-shero::after{
    animation:vdsHeroDrift2 21s ease-in-out infinite alternate;
    will-change:transform;
  }

  /* 2 — THE SECOND BLOOM IS BACK, AND IT WAS NEVER A BOTTOM-LEFT ONE
     (ROUND 4, user: "the hero gradient pseudos are not matching glp's design").
     ⚠⚠ THIS IS THE REAL MECHANISM AND IT RESOLVES ROUND 3 RATHER THAN
     REVERSING IT. flair.css declares `.hero::after{bottom:-18%;left:-8%}`,
     which is what B1 ported — but `styles.css` line 1797 ALREADY declared
     `.hero::after{top:-20%;right:-6%;height:620px}` on the same pseudo at the
     same (0,1,1), and flair.css never overrides `top` or `height`. Absolute
     positioning is then OVER-CONSTRAINED on both axes, so in LTR the browser
     drops `right` (keeping left) and drops `bottom` (keeping top + height).
     MEASURED on the live comp at 1440x900 (hero 1440x666), not read off the
     stylesheet: `::after` resolves to top -133.188px (-20% of 666), left
     -115.188px (-8% of 1440), 430px wide x 620px TALL — a tall ellipse in the
     TOP-LEFT corner. The comp has NO bottom bloom at all.
     So round 3 was right that the bottom-left blob had to go; it was a port
     artefact that the comp's own cascade never produces. What was missing was
     the top-left ellipse that belongs there instead, and the top-right
     `::before`. Both are now cut verbatim into the `vds-hero` / `vds-shero`
     global classes (`_cssCustom`), alphas included — .20 crimson and .14
     #ed4753, blur(72px) on both, which B1 had deliberately declined to port.
     ⚠ THE ROUND 3 SEAM CANNOT COME BACK FROM THIS. Both blooms are anchored
     to `top`, so neither reaches the hero's bottom edge where `#the-short-answer`
     (2714) and `#on-this-page` (2793) butt up against it. Re-measured after
     the write at 1440 and 390 on both pages.
     ⚠ `filter:none` under `prefers-reduced-motion:reduce` WAS REMOVED from
     `vds-shero`. A blob authored for blur(72px) renders as a hard-edged
     circle without it, and a static blur is not motion — there is nothing
     for the reduce query to switch off. The animations are already inside
     `no-preference`, which is the comp's own structure. */

  /* 3 — shimmer sweep across the gradient headline (comp: flairShimmer).
     `background-size` is the mechanism, not decoration: the ramp is clipped
     to the glyphs, so an animated `background-position` only reads if the
     image is wider than the box. Scoped to the two heroes rather than every
     `.vds-grad-text` on the site (the comp animates them all) — B1 is the
     HERO item, and a shimmering h2 in every band is a different decision
     that should be taken on its own. Rolling it out is one selector edit. */
  .vds-hero .vds-grad-text.vds-grad-text,
  .vds-shero .vds-grad-text.vds-grad-text{
    background-size:220% 100%;
    animation:vdsHeroShimmer 6.5s ease-in-out infinite;
  }

  /* 4 — the eyebrow accent bars breathe (comp: flairBar). Site-wide, as the
     comp has it: `.vds-eyebrow` is one component and a hero-only variant
     would be the only eyebrow on the site that moves. `transform-origin` is
     load-bearing — the default 50% is already centre, but the bars are
     `flex:none` children and restating it keeps the scaleX symmetric if the
     rule is ever re-scoped onto a differently-aligned head. */
  .vds-eyebrow.vds-eyebrow::before,
  .vds-eyebrow.vds-eyebrow::after{
    transform-origin:center;
    animation:vdsEyebrowBar 3.6s ease-in-out infinite;
  }

  /* 5 — THE WHOLE-GRAPHIC FLOAT IS DELETED (ROUND 4, user: "why is it
     floating up and down when theirs does not??").
     ⚠⚠ IT WAS A PORTING GAP, NOT A PREFERENCE — the FOURTH of this exact
     shape (round 2's card panel, round 3's `.gf-cap`, now this). B1 ported
     flair.css's FIRST block (lines 25-73) and never read its SECOND, the
     `[data-growthflow]` layer at lines 145-400, which overrides nearly all
     of it. That layer opens by setting `animation:none` on BOTH
     `.growth-flow` and `.gf-engine-core`, under its own comment: "the old
     whole-graphic bob fought the new beam geometry, so the float moves to
     the engine alone where it reads as the engine running".
     MEASURED on the live comp before the write: `.growth-flow`
     animationName `none`. We were running the bob the comp had retired, on
     a graphic whose beams are measured from live child boxes.
     `vdsHeroFloat` went with it (no other users). */

  /* 6 — the engine breathes instead (comp: gfEngineBreathe 4.2s, which
     REPLACED flairPulse 3.4s in the same override). SERVICE ONLY — see the
     header note: `vds-gf-engine-core` is a SHARED class (§5A) and the
     `.vds-shero ` prefix is all that keeps 2714's frozen right column still.
     The rest value is byte-identical to the element's own resting shadow
     (written in the static block below), so a `reduce` reader sees the same
     card at rest as one without it — the same reasoning B1 used. */
  .vds-shero .vds-gf-engine-core.vds-gf-engine-core{
    animation:vdsGfBreathe 4.2s ease-in-out infinite;
  }

  /* 7 — the engine's rotating halo and diagonal sheen (ROUND 4, user:
     "its missing the shimmer in the middle"). The comp draws these as two
     real `<i>` children of `.gf-engine-core`; we draw them as the core's own
     two pseudo-elements instead. SAME RENDER, and it costs NO element churn
     on 2793 and cannot reach 2714 — adding two elements would have meant a
     page write, a new element count and an SP-19-shaped risk for pure
     decoration. The core's `overflow:hidden` clips both to the rounded card,
     exactly as it does on the comp. Geometry is in the static block below;
     only the motion is here. */
  .vds-shero .vds-gf-engine-core.vds-gf-engine-core::before{
    animation:vdsGfSpin 14s linear infinite;
  }
  .vds-shero .vds-gf-engine-core.vds-gf-engine-core::after{
    animation:vdsGfSheen 6.5s ease-in-out infinite;
  }

  /* 8 — the channel chips' signal dots pulse (comp: gfSignal 2.6s), staggered
     by `--gfi`, the per-chip index `vds-gflow.js` now writes (round 4). With
     no `--gfi` the `var(--gfi,0)` fallback makes every dot fire together,
     which is a graceful degradation, not a break. */
  .vds-shero .vds-gf-chip.vds-gf-chip i{
    animation:vdsGfSignal 2.6s ease-in-out infinite;
    animation-delay:calc(var(--gfi,0) * .32s);
  }

  /* 9 — THE STAGGERED ENTRANCE, AND IT IS THE ANSWER TO "IT LAGS ON LOAD"
     (ROUND 4). ⚠ THE STATED CAUSE WAS WRONG AGAIN (§0 rule 2) — it is not a
     performance problem and there was nothing to make faster.
     MEASURED, polling every frame from navigation on both pages:
       comp  beams drawn t=156ms, chips at opacity 0 until then, fading
             0 -> 1 across 308-932ms. Nothing is visible before it is whole.
       ours  beams drawn t=1479ms, chip opacity 1 THE ENTIRE TIME.
     So our graphic painted complete-but-beamless the instant the hero did,
     and 13 beam paths snapped into it a frame later. That pop IS the "lag".
     Our JS is not slow: domInteractive was 1417ms on that same load (staging
     TTFB ~1.27s) and `arm()` ran 62ms after it, before `load`. The comp only
     looks instant because it is a local file AND because nothing shows until
     the weave is already drawn.
     The fix is therefore the choreography, not the clock: hold cap, chips,
     engine and tiles at opacity 0 until `vds-gflow.js` adds `.is-flowing`
     (which it already did — only the CSS half was missing), then cascade them
     in. Verbatim from flair.css lines 371-392.
     ⚠ EXPOSURE, ACCEPTED AND THE COMP'S OWN: if the script never runs the
     graphic stays invisible. Gated on `[data-growthflow]`, which only our
     migrated markup carries, and on `no-preference`; under `reduce` the
     block below restores everything to opacity 1 with no transition. */
  .vds-shero .vds-shero-flow[data-growthflow] .vds-gf-cap,
  .vds-shero .vds-shero-flow[data-growthflow] .vds-gf-chip,
  .vds-shero .vds-shero-flow[data-growthflow] .vds-gf-out-item{
    opacity:0;
    transform:translateY(14px);
  }
  .vds-shero .vds-shero-flow[data-growthflow] .vds-gf-engine-core{
    opacity:0;
    transform:translateY(14px) scale(.94);
  }
  .vds-shero .vds-shero-flow.is-flowing .vds-gf-cap,
  .vds-shero .vds-shero-flow.is-flowing .vds-gf-chip,
  .vds-shero .vds-shero-flow.is-flowing .vds-gf-engine-core,
  .vds-shero .vds-shero-flow.is-flowing .vds-gf-out-item{
    opacity:1;
    transform:none;
    transition:opacity .62s cubic-bezier(.16,1,.3,1),
               transform .62s cubic-bezier(.16,1,.3,1);
  }
  .vds-shero .vds-shero-flow.is-flowing .vds-gf-cap{transition-delay:.05s}
  .vds-shero .vds-shero-flow.is-flowing .vds-gf-chip{
    transition-delay:calc(.14s + var(--gfi,0) * .075s);
  }
  .vds-shero .vds-shero-flow.is-flowing .vds-gf-engine-core{transition-delay:.68s}
  .vds-shero .vds-shero-flow.is-flowing .vds-gf-out-item{
    transition-delay:calc(.94s + var(--gfi,0) * .09s);
  }
}

/* --------------------------------------------------------------------------
   ROUND 4 — the STATIC half of the comp's `[data-growthflow]` engine layer.
   Geometry and colour, so it belongs outside `no-preference`: a reader with
   `reduce` must still get the comp's card, just motionless.
   ALL `.vds-shero`-scoped (§5A) — `vds-gf-*` is SHARED with 2714's frozen
   right column and NOTHING here edits a shared global class.
   Specificity: Bricks emits the kit's own rules from the page's global-class
   block AFTER style.css at (0,1,0)/(0,2,0), so every selector below doubles
   a class to reach (0,3,0) or better (§5.2). No `!important`.
   `--indigo` and `--cyan` on the comp resolve to #d92128 and #ed4753, i.e.
   our `--vds-red` and `--vds-red-light`; every `color-mix(... X%, transparent)`
   below is written as the equivalent rgba, which is what the browser computes.
   -------------------------------------------------------------------------- */

/* the engine card itself */
.vds-shero .vds-gf-engine-core.vds-gf-engine-core{
  position:relative;
  isolation:isolate;
  overflow:hidden;
  padding:.95rem 1.5rem;
  border-radius:18px;
  box-shadow:
    0 2px 4px rgba(0,0,0,.12),
    0 14px 34px rgba(217,33,40,.38),
    inset 0 1px 0 rgba(255,255,255,.28);
}
/* ⚠ LOAD-BEARING: the ring and the sheen are the core's pseudo-elements, so
   the real children must be lifted above them or the sheen washes the type. */
.vds-shero .vds-gf-engine-core.vds-gf-engine-core b,
.vds-shero .vds-gf-engine-core.vds-gf-engine-core span{
  position:relative;
  z-index:2;
}
.vds-shero .vds-gf-engine-core.vds-gf-engine-core b{
  font-size:1.04rem;
  letter-spacing:-.012em;
}
.vds-shero .vds-gf-engine-core.vds-gf-engine-core span{
  font-size:.715rem;
  letter-spacing:.06em;
  opacity:.92;
  margin-top:.22rem;
}
/* ::before = the comp's `<i class="gf-engine-ring">` — a conic halo that
   spins behind the core and is clipped to it by the card's overflow. */
.vds-shero .vds-gf-engine-core.vds-gf-engine-core::before{
  content:"";
  position:absolute;
  z-index:0;
  inset:-48%;
  border-radius:50%;
  opacity:.5;
  pointer-events:none;
  background:conic-gradient(from 0deg,
    rgba(255,255,255,0) 0deg,
    rgba(255,255,255,.55) 42deg,
    rgba(255,255,255,0) 110deg,
    rgba(255,255,255,0) 250deg,
    rgba(255,255,255,.3) 300deg,
    rgba(255,255,255,0) 360deg);
}
/* ::after = the comp's `<i class="gf-engine-sheen">` — THE SHIMMER. The
   resting transform is load-bearing: it parks the band off the left edge so
   the card does not ship with a bright diagonal burnt across it when motion
   is off. */
.vds-shero .vds-gf-engine-core.vds-gf-engine-core::after{
  content:"";
  position:absolute;
  z-index:1;
  inset:0;
  pointer-events:none;
  transform:translateX(-130%);
  background:linear-gradient(115deg,
    transparent 34%,
    rgba(255,255,255,.3) 50%,
    transparent 66%);
}

/* the chips and the outcome tiles: the comp's glass, which B1 never reached.
   Ours were flat white on a flat border with no shadow. */
.vds-shero .vds-gf-chip.vds-gf-chip,
.vds-shero .vds-gf-out-item.vds-gf-out-item{
  background:rgba(255,255,255,.82);
  border:1px solid rgba(209,213,219,.7);
  box-shadow:0 1px 2px rgba(0,0,0,.04), 0 6px 18px rgba(20,20,35,.06);
  -webkit-backdrop-filter:blur(10px) saturate(1.3);
  backdrop-filter:blur(10px) saturate(1.3);
}
.vds-shero .vds-gf-out-item.vds-gf-out-item{
  padding:.8rem .6rem;
  border-radius:16px;
  box-shadow:0 1px 2px rgba(0,0,0,.04), 0 10px 26px rgba(20,20,35,.07);
}
.vds-shero .vds-gf-chip.vds-gf-chip i{
  width:7px;
  height:7px;
  box-shadow:0 0 0 3px rgba(217,33,40,.14);
}
/* ⚠ THE RED "RANKINGS THAT HOLD" (ROUND 4, user: "its missing ... some red
   text for rankings that hold"). The comp clips the brand ramp to the glyphs:
   `.gf-out-rev b{background:var(--grad-brand);background-clip:text;
   color:transparent}`. Measured on the comp: color rgba(0,0,0,0) over
   linear-gradient(120deg,#b12025,#d92128 50%,#ed4753). Ours was flat
   rgb(17,17,20) — the base `.gf-out-item b{color:var(--ink)}` with nothing
   on top of it, because this override lives in flair.css's second layer.
   ⚠ `color:transparent` with a clipped background is INVISIBLE if the
   background ever fails to paint, so the tile keeps its own tint underneath
   and the accessible name is unaffected (the text node is untouched). */
.vds-shero .vds-gf-out-rev.vds-gf-out-rev{
  background:linear-gradient(160deg,
    rgba(217,33,40,.16),
    rgba(237,71,83,.07));
  border-color:rgba(217,33,40,.34);
}
.vds-shero .vds-gf-out-rev.vds-gf-out-rev b{
  background:var(--vds-grad-brand);
  -webkit-background-clip:text;
  background-clip:text;
  color:transparent;
}

/* dark: the comp gives the glass a darker, cooler base so it stays readable.
   Our dark is `html[data-brx-theme="dark"]`, Bricks' own attribute, not the
   comp's `:root[data-theme]`. */
html[data-brx-theme="dark"] .vds-shero .vds-gf-chip.vds-gf-chip,
html[data-brx-theme="dark"] .vds-shero .vds-gf-out-item.vds-gf-out-item{
  background:rgba(255,255,255,.06);
  border-color:rgba(255,255,255,.12);
  box-shadow:0 1px 2px rgba(0,0,0,.4), 0 12px 30px rgba(0,0,0,.45);
}
html[data-brx-theme="dark"] .vds-shero .vds-gf-out-rev.vds-gf-out-rev{
  background:linear-gradient(160deg,rgba(217,33,40,.30),rgba(255,255,255,.04));
  border-color:rgba(217,33,40,.46);
}

/* `reduce`: the comp kills the sheen outright and leaves everything resting
   and visible. Without this the entrance rules above never fire (they are in
   `no-preference`) but the opacity:0 rules do not either, so the graphic is
   already correct — this only removes the sheen band and the halo, which
   are pure motion artefacts when they cannot move. */
@media (prefers-reduced-motion:reduce){
  .vds-shero .vds-gf-engine-core.vds-gf-engine-core::after{display:none}
  .vds-shero .vds-gf-engine-core.vds-gf-engine-core::before{opacity:.28}
}

/* Keyframes live outside the query on purpose: a @keyframes block has no
   selector and so no specificity or cascade position to lose (the same
   reasoning as vdsBtnSheen above), and keeping them out of the media query
   means a future `reduce` rule can still name one if it ever needs a static
   end state. Values are the comp's, unchanged. */
@keyframes vdsHeroDrift1{ to{transform:translate3d(-42px,30px,0) scale(1.12)} }
/* vdsHeroDrift2 is BACK (round 4) — the comp's top-left bloom uses it. */
@keyframes vdsHeroDrift2{ to{transform:translate3d(38px,-26px,0) scale(1.16)} }
@keyframes vdsHeroShimmer{
  0%,100%{background-position:0% 50%}
  50%{background-position:100% 50%}
}
/* vdsHeroFloat and vdsHeroPulse removed in round 4: the comp's
   `[data-growthflow]` layer sets `animation:none` on both of their targets
   and replaces the pulse with gfEngineBreathe. No users left. */
/* ⚠ The 0%/100% shadow below is byte-identical to the element's own resting
   `box-shadow` in the static block, so `reduce` and `no-preference` agree at
   rest. If you change one, change both. */
@keyframes vdsGfBreathe{
  0%,100%{box-shadow:0 2px 4px rgba(0,0,0,.12),
                     0 14px 34px rgba(217,33,40,.38),
                     inset 0 1px 0 rgba(255,255,255,.28)}
  50%    {box-shadow:0 2px 4px rgba(0,0,0,.12),
                     0 20px 52px rgba(217,33,40,.60),
                     inset 0 1px 0 rgba(255,255,255,.34)}
}
@keyframes vdsGfSpin{ to{transform:rotate(360deg)} }
@keyframes vdsGfSheen{
  0%,62%{transform:translateX(-130%)}
  100%  {transform:translateX(130%)}
}
@keyframes vdsGfSignal{
  0%,100%{box-shadow:0 0 0 3px rgba(217,33,40,.12)}
  50%    {box-shadow:0 0 0 6px rgba(217,33,40,0)}
}
@keyframes vdsEyebrowBar{
  0%,100%{opacity:.7;transform:scaleX(.8)}
  50%{opacity:1;transform:scaleX(1.25)}
}

/* ==========================================================================
   A2 (2026-10-14) — "THE HERO GRADIENT IS TOO WHITE"
   --------------------------------------------------------------------------
   ⚠⚠ THE ITEM'S STATED CAUSE WAS WRONG, FOR THE FIFTH TIME THIS BUILD
   (§0 rule 2). A2 says to measure `--vds-hero-bg` against the comp's
   `--hero-bg` and raise the brand presence to match. Measured, both themes,
   off the LIVE computed root against `comp/styles.css` lines 73 and 98:

     light  radial-gradient(1200px 600px at 80% -10%,rgba(237,71,83,.10),transparent 60%),
            radial-gradient(900px 500px at 10% 10%,rgba(217,33,40,.09),transparent 55%), #ffffff
     dark   ... same geometry at .22 / .28 over #0a0a0b

   **OURS IS BYTE-IDENTICAL TO THE COMP'S, IN BOTH THEMES.** There was
   nothing to raise. Do not "fix" that token.

   The hero really did read cooler than the comp's, and the difference is the
   FLAIR LAYER painted on top of the identical token, not the token. Measured
   as pixels — mean redness (R - avg(G,B)) over six horizontal bands of the
   hero, ours vs the re-hosted comp at 1440x900:

     comp    15.6  14.5  15.3  22.6  14.2   0.6
     before  14.2  11.7  10.2  18.1  13.4   4.6     mean gap -1.77
     after   14.2  11.8  10.6  20.1  15.0   6.6     mean gap -0.75

   ⚠⚠ AND THE COMP'S OWN BLOOM VALUES DO NOT REPRODUCE THE COMP'S RESULT
   HERE — PORTING THEM VERBATIM WOULD HAVE MADE IT WORSE. Swept on the live
   page: the comp's top-right `::before` (rgba(217,33,40,.45), blur 72px)
   scored **-2.05**, worse than the -1.77 we already had, because a radial
   that falls to transparent concentrates its colour in a corner that OUR
   blob does not occupy — ours sits at `top:-40%` (hero.css explains why: this
   band is half the comp's height, so the comp's placement would read as a
   hard edge). Alpha was never the lever. The lever is the BOTTOM-LEFT bloom,
   which is what paints band 3, the biggest single gap.
   Swept four candidates there and took the conservative one: .16 -> **.24**,
   blur 28 -> **48px**, min(36vw,480px) -> **min(42vw,560px)**.
   ⚠ NOT the hotter candidates (.30/blur56 hit band 3 almost exactly at 22.5,
   and .34/blur72 at 23.0) — both push band 5 to 8.3-8.9 against the comp's
   **0.6**. Our hero is 699px tall to the comp's 666 and the bloom's centre
   lands lower, so the bottom edge overshoots before the middle matches.
   Chasing band-3 parity means visibly over-warming the bottom, which is a
   worse page than a 2-point shortfall in the middle. Band 5 at 6.6 is
   already the accepted cost of matching band 3 this far.
   SHARED: this moves BOTH heroes, which is what the item asks for ("same
   token drives the homepage hero — confirm the homepage still reads right").
   Both re-shot and looked at, light and dark.
   ========================================================================== */


/* ==========================================================================
   MOBILE DRAWER (2026-10-14) — the real vds2026 drill-down, ported
   --------------------------------------------------------------------------
   SYMPTOM: below 1200 the burger opened but the nav rendered in a 64px-tall
   box with its items overflowing; all the user saw was that box's horizontal
   scrollbar under the header.

   CAUSE (measured, and it is ours but NOT Phase F): `.vds-header-bar` carries
   `backdrop-filter:blur(14px) saturate(150%)` (header.css:218), the glass
   ported with the original header in Phase A/B. **A `backdrop-filter` makes
   the element the containing block for every `position:fixed` descendant**,
   so Bricks' off-canvas panel (`position:fixed;inset:0`) resolved against the
   bar's 390x64 box instead of the viewport. Byte-identical in
   `scratch/sp-round3/header.css.pre-phasef` — Phase F was simply the first
   time anyone opened the menu.

   ⚠ A FIRST PASS RESTYLED BRICKS' OWN PANEL AND THE USER REJECTED IT
   ("looks like ass"). It is gone. This is the reference drawer instead:
   `.vds-drawer` / `.vds-dd-*` from vds26-shell.css 384-500, with the
   drill-down driven by `js/vds-drawer.js`.

   ⚠ ONE SOURCE, NO SYNC (user's requirement). vds2026 renders both
   presentations from one WP menu via VDS26_Mega_Walker; the Bricks nav is
   not a menu, so `vds-drawer.js` BUILDS the drawer from the mega already in
   the DOM. Bricks stays the single source of truth. Do not reintroduce a
   WP menu or a sync script for this.

   The glass-on-a-pseudo fix is KEPT even though the drawer is now a body
   child and no longer a descendant of the bar: it is correct on its own
   terms and stops the next `position:fixed` descendant hitting the same wall.
   ========================================================================== */
@media (max-width:1199px){
  .vds-header-bar.vds-header-bar.vds-header-bar{
    -webkit-backdrop-filter:none;
    backdrop-filter:none;
    background-color:transparent;
  }
  .vds-header-bar.vds-header-bar.vds-header-bar::before{
    content:"";
    position:absolute;
    inset:0;
    z-index:-1;
    background-color:var(--vds-nav-bg);
    -webkit-backdrop-filter:blur(14px) saturate(150%);
    backdrop-filter:blur(14px) saturate(150%);
    pointer-events:none;
  }
  /* Bricks' native off-canvas is replaced wholesale by .vds-drawer. */
  .vds-nav-primary .brx-nav-nested-items.brx-nav-nested-items{
    display:none;
  }
}

/* ==========================================================================
   NAV FIT, 1200-1365px — QA round 2 Wave D (F-10, 2026-11-02)
   ==========================================================================
   ⚠ THIS EXISTS BECAUSE WAVE D ADDED A SIXTH TOP-LEVEL NAV ITEM
   ("Industries"). It is not cosmetic tuning — without it the primary nav
   WRAPS TO TWO ROWS between 1200px and 1365px, which changes the header's
   height and is plainly broken. Every other Wave D assertion was green
   while this was happening; only measuring the <li> tops caught it.

   THE ARITHMETIC, measured live, not estimated. `.vds-header-inner` is a
   flex row of three children and only the nav is allowed to shrink:
     brand 115px + nav-cta 374px + 2 gaps, inside the bar's own padding.
     available for the nav :  596px @1200 · 673px @1280 · 753px @1365
     six items need        :  690px   -> short by 94px @1200, 17px @1280
   At 1366+ the bar hits its 1360px max-width and there is +63px of slack,
   so the band deliberately STOPS at 1365 and the default nav is untouched
   above it. Below 1200 the nav is display:none and the drawer takes over
   (the block directly above), so 1200-1365 is the whole exposure.

   WHAT THIS CHANGES: horizontal padding on the trigger parts, 0.94rem ->
   0.90rem on the label (15.04px -> 14.4px), and the bar's own flex gap
   24px -> 16px. Measured result: need 587px against 612px available at
   1200 — **+25px of slack**, one row at every width in the band.

   ⚠ WHY NOT THE OBVIOUS ALTERNATIVE: hiding `.vds-nav-phone` (154px) in
   this band would also fix it, with no type change at all. It is NOT done
   here because removing the header's click-to-call from a whole class of
   laptop widths is a business decision, not a layout fix. If someone wants
   that trade instead, this entire block can be replaced by one
   `display:none` — flag it to the client first.

   ⚠ SPECIFICITY IS DELIBERATE AND LOAD-BEARING (handoff §3 item 2). Bricks
   emits a global class's `selectors[]` entries element-type-qualified, so
   `vds-nav-item`'s own rule lands as
   `.vds-nav-item.brxe-dropdown .brx-submenu-toggle > a` = (0,3,1). The
   child theme is printed BEFORE that block, so a (0,3,1) rule here would
   TIE AND SILENTLY LOSE. Each selector below is doubled or parent-scoped
   to sit one class ABOVE its target. Do not "simplify" them.
   ========================================================================== */
@media (min-width:1200px) and (max-width:1365px){
  /* (0,3,0) — beats `.vds-header-inner.brxe-div` (0,2,0) */
  .site-header .vds-header-inner.vds-header-inner{
    gap:16px;
  }
  /* (0,4,1) — beats `.vds-nav-item.brxe-dropdown .brx-submenu-toggle > a` */
  .vds-nav-primary .vds-nav-item.vds-nav-item > .brx-submenu-toggle > a{
    padding-left:.4rem;
    padding-right:.3rem;
    font-size:.90rem;
  }
  .vds-nav-primary .vds-nav-item.vds-nav-item > .brx-submenu-toggle > button{
    padding-left:.2rem;
    padding-right:.4rem;
  }
  /* Contact is a text-link, not a dropdown: (0,3,0) beats
     `.vds-nav-link.brxe-text-link` (0,2,0) */
  .vds-nav-primary .vds-nav-link.vds-nav-link{
    padding-left:.4rem;
    padding-right:.4rem;
    font-size:.90rem;
  }
}

.vds-drawer{
  /* ⚠ ABOVE the header, which is z-index 200 (the bar inside it is 100).
     At 130 the panel painted UNDER the header, and because the open
     transition starts at translateY(-6px) it visibly slid out from behind
     it. Do not lower this below the header's own z-index. */
  position:fixed; left:0; right:0; z-index:300;
  top:calc(var(--vds-drawer-top,120px) + var(--vds-drawer-nudge,-2px));
  height:calc(100dvh - (var(--vds-drawer-top,120px) + var(--vds-drawer-nudge,-2px)));
  display:flex; flex-direction:column;
  padding:.5rem var(--vds-gutter) 1.25rem;
  background:var(--vds-bg);
  /* ⚠ NO border-top. `.vds-header-bar` already ships
     `border-bottom-width:1px` (header.css:220); a border here too painted
     the seam twice, which the user rejected. The header's edge IS the
     seam. If you re-add this, drop --vds-drawer-nudge to -2px or the
     double line comes back. */
  overflow-y:auto; overscroll-behavior:contain;
  opacity:0; transform:translateY(-6px);
  transition:opacity var(--vds-t-base) ease,transform var(--vds-t-base) ease;
}
body.vds-drawer-open .vds-drawer{opacity:1;transform:translateY(0)}
body.vds-drawer-open{overflow:hidden}
.vds-drawer[hidden]{display:none}
@media (min-width:1200px){
  .vds-drawer{display:none}
}

/* ⚠ THE DRAWER'S TOP EDGE IS MEASURED, NOT AUTHORED — and this value is
   ONLY the pre-JS fallback. Do not tune the drawer by editing it.

   WHY NO CONSTANT CAN BE RIGHT: the WP admin bar is 32px, so the header's
   bottom is ~138 logged IN and ~106 logged OUT (the user measured both).
   An authored 138 leaves a 32px gap for every logged-out visitor, which is
   everyone who actually uses the site. `getBoundingClientRect().bottom` is
   viewport-relative and so already includes the admin bar's offset — one
   measurement covers both states, which is exactly why vds-drawer.js owns
   this value at runtime.

   ⚠ Its own variable, NOT `--vds-header-h`: that one is already defined as
   120px elsewhere on this site and used by other things. Do not merge them.

   ⚠ Headless measures 120.16 where the user's real browser measures ~106
   logged out — the announce bar wraps differently because the real
   Montserrat VDS is not the face headless renders (gotcha #36). So do NOT
   "correct" the runtime value to match a local screenshot. */
:root{
  --vds-drawer-top:120px;

  /* ⚠ THE 2px NUDGE IS THE ONLY HAND-TUNED NUMBER HERE, and it is the
     user's (2026-10-14: "it still needs to move up by 2px in both logged
     in and out states"). Separate from --vds-drawer-top ON PURPOSE:
     that one is measured per-state at runtime, this is a constant applied
     to both, so neither can quietly absorb the other.

     It is almost certainly a DOUBLED BORDER: `.vds-header-bar` ships
     `border-bottom-width:1px` (header.css:220) and `.vds-drawer` ships its
     own `border-top:1px`, so the seam paints 2px of line. The tidier fix
     WHAT THE 2px WAS, from the user: 1px closing a real gap + 1px hiding
     the doubled border. The border has since been removed from
     `.vds-drawer` outright, so ONLY THE GAP PIXEL REMAINS and this is now
     -1px. ⚠ The gap is real and survives the border fix: the measured
     header bottom is fractional (120.16) and `Math.ceil` lands the panel
     at 121, leaving 0.84px of daylight. This closes it. */
  --vds-drawer-nudge:-1px;
}

/* The viewport clips the sliding pages. Its height is set inline by the JS
   to the active page's height, so the panel grows and shrinks with the page
   instead of holding the tallest one's height. */
.vds-dd-viewport{position:relative;overflow:hidden;transition:height var(--vds-t-base) ease}
.vds-dd-page{
  display:flex; flex-direction:column;
  transition:transform .3s cubic-bezier(.4,0,.2,1);
}
/* Only the root is in flow; sub-pages are stacked over it and slid in.
   Nesting means a page can be BEHIND the active one rather than ahead of it,
   so there are three states, not two. */
.vds-dd-sub{position:absolute;inset:0 0 auto 0;transform:translateX(100%);background:var(--vds-bg)}
.vds-dd-sub[hidden]{display:none}
.vds-dd-page.is-active{transform:translateX(0)}
.vds-dd-page.is-behind{transform:translateX(-100%)}

.vds-dd-row{
  width:100%; display:flex; align-items:center; justify-content:space-between; gap:.5rem;
  padding:1rem .3rem; background:none; border:0; border-bottom:1px solid var(--vds-border);
  font-family:var(--vds-font-display); font-weight:600; font-size:1.05rem;
  color:var(--vds-ink); text-decoration:none; text-align:left; cursor:pointer;
}
.vds-dd-row:hover{color:var(--vds-accent-ink)}
.vds-dd-chevron{flex:0 0 auto;opacity:.55}

.vds-dd-back{
  display:inline-flex; align-items:center; gap:.5rem; align-self:flex-start;
  padding:.7rem .3rem; background:none; border:0; cursor:pointer;
  font-family:var(--vds-font-display); font-weight:600; font-size:.82rem;
  letter-spacing:.08em; text-transform:uppercase; color:var(--vds-muted);
}
.vds-dd-back:hover{color:var(--vds-accent-ink)}
.vds-dd-title{
  margin:0 0 .25rem; padding:0 .3rem;
  font-family:var(--vds-font-display); font-weight:700; font-size:1.35rem; color:var(--vds-ink);
}
.vds-dd-link{
  display:block; padding:.6rem .3rem;
  color:var(--vds-ink-2); font-size:.98rem; text-decoration:none;
}
.vds-dd-link:hover{color:var(--vds-accent-ink)}
.vds-dd-overview{font-weight:600;color:var(--vds-accent-ink);border-bottom:1px solid var(--vds-border);padding-bottom:.7rem}

/* Burger -> X, authored here because BRICKS NEVER DRAWS ONE. The toggle
   carries `is-active` when open (vds-drawer.js keeps that in step with our
   state — see below) but `.brxa-inner` measured `transform:none` in both
   states, so the X had to be written.

   MEASURED geometry of Bricks' burger: `.brxa-inner` IS the middle bar
   (16x2 at top:7px) and the outer two are its `::before` (top:-6px) and
   `::after` (top:+6px). So the middle fades and the outer two meet in the
   centre — translate by their own 6px offset, then rotate.
   ⚠ Driven off `body.vds-drawer-open`, not the button's `is-active`:
   Bricks also writes that class from its own handler, and the body class is
   the one OUR state owns. (0,3,0) to clear Bricks' own rules.

   Reference parity note: vds2026's `.vds-burger span:nth-child()` markup
   does NOT exist here — Bricks renders
   `button.brxe-toggle > span.brxa-wrap > span.brxa-inner` instead. */
.vds-drawer-toggle .brxa-inner,
.vds-drawer-toggle .brxa-inner::before,
.vds-drawer-toggle .brxa-inner::after{
  transition:transform .22s ease,background-color .22s ease;
}
body.vds-drawer-open .vds-drawer-toggle .brxa-inner{
  background-color:transparent;
}
body.vds-drawer-open .vds-drawer-toggle .brxa-inner::before{
  transform:translateY(6px) rotate(45deg);
}
body.vds-drawer-open .vds-drawer-toggle .brxa-inner::after{
  transform:translateY(-6px) rotate(-45deg);
}

/* The X above replaces what the reference did. The reference's `.vds-burger` markup does
   NOT exist here: Bricks renders the toggle as
   `button.brxe-toggle > span.brxa-wrap > span.brxa-inner` and animates the
   X off its own `is-active` class. So there is nothing to style — the fix
   is to keep `is-active` in step with OUR state, which vds-drawer.js now
   does explicitly. It cannot be left to Bricks' own handler: closing via
   Escape or by tapping a link never fires it, and the burger stuck as an X.

   Screen-reader-only text for the Back buttons. Named `vds-dd-sr`, NOT
   `vds-visually-hidden` — that class already exists on this site and the
   collision put 33 identical-value rules in audit-childtheme-cascade's DEAD
   list. Different name, zero contention. */
.vds-dd-sr{
  position:absolute; width:1px; height:1px; padding:0; margin:-1px;
  overflow:hidden; clip:rect(0 0 0 0); white-space:nowrap; border:0;
}


/* ==========================================================================
   BUTTON SHEEN, ROLLED OUT (2026-10-14, user request) — the megamenu's red
   CTAs and the Gravity Forms submit buttons
   --------------------------------------------------------------------------
   Reuses the EXISTING `@keyframes vdsBtnSheen` above (QA-5) and the exact
   gradient/duration the `vds-btn-primary` global class already ships, so all
   three surfaces sweep identically. No new keyframes.

   TARGETS, confirmed live: `.vds-mega-cta-btn.primary` x4 (the red pill; the
   two plain `.vds-mega-cta-btn` are the SECONDARY pills and are deliberately
   left alone) and `.gform_button` x2 on 2793 (Free Revenue Audit GF 3,
   newsletter GF 5) — GF renders a real <button>, not <input type=submit>,
   which is the only reason a pseudo-element is possible here at all.

   Both needed `position:relative` + `overflow:hidden`: measured static/
   visible, and without the clip the band sweeps outside the pill.
   ⚠ Specificity is (0,3,0) by doubling — §5.0, the child theme loses ties.
   ⚠ Wrapped in `prefers-reduced-motion: no-preference`, which the original
   `vds-btn-primary` sheen is NOT. Deliberate: new motion should respect the
   setting. Flagged so the inconsistency is a decision, not drift.
   ========================================================================== */
.vds-mega-cta-btn.vds-mega-cta-btn.primary,
.gform_button.gform_button.gform_button{
  position:relative;
  overflow:hidden;
}
@media (prefers-reduced-motion: no-preference){
  .vds-mega-cta-btn.vds-mega-cta-btn.primary::after,
  .gform_button.gform_button.gform_button::after{
    content:"";
    position:absolute;
    inset:0;
    background:linear-gradient(120deg,transparent 38%,rgba(255,255,255,.42) 50%,transparent 62%);
    transform:translateX(-130%);
    animation:vdsBtnSheen 3.6s ease-in-out infinite;
    pointer-events:none;
  }
}

/* ==========================================================================
   SERVICE AREA round (2026-10-14) — keyframes for the hero map's pulse rings
   --------------------------------------------------------------------------
   The ring's resting state is declared entirely in
   `build/service-area/src/hero.css` (as `.vds-geo-rings .vds-geo-ring` —
   `vds-geo-ring` is not a global class, see below); ONLY the keyframes are
   here, for
   the same reason `vdsBtnSheen` above is: a @keyframes block has no
   selector, so the html-to-bricks converter cannot attach it to an element
   and collects it into a `code` element with `executeCode:true` instead —
   code-sensitive, omitted silently, `partial:true`. The hero's first preview
   did exactly that.

   ⚠ THIS ADDS NO SELECTOR, SO IT CANNOT MOVE 2714 OR 2793. A keyframes
   block with a name nothing else references has no specificity and no
   cascade position; the only page that can see it is the one whose elements
   name `vdsGeoRing`. `audit-childtheme-cascade.py` and `sa-guard.py` are
   still run after this write — the point is that there was never a tie for
   the child theme to lose (QA-7).

   Ported from the comp's `@keyframes geoRing` (styles.css:516), with the
   SVG `r` / `stroke-width` pair re-expressed as a DOM box:
     comp        r: 2 -> 14          stroke-width: .9 -> .12
     here        4.2% -> 28%         border-width: 3px -> .5px
   The viewBox is 0 0 100 100, so one user unit is one per cent of the
   square stage and `2r` is the box side. Per cent, not pixels: a px keyframe
   would be right at exactly one stage width. The ring thins as it expands,
   which is the comp's own behaviour and the reason a plain `scale()` is not
   used — scaling multiplies the border instead of thinning it.
   ========================================================================== */
@keyframes vdsGeoRing{
  0%   { width:4.2%; height:4.2%; border-width:3px;  opacity:.6; }
  100% { width:28%;  height:28%;  border-width:.5px; opacity:0;  }
}

/* The three rings themselves. THIS IS ALSO HERE BY NECESSITY, not to keep
   the motion together with its keyframes: `@media
   (prefers-reduced-motion:reduce)` and `no-preference` CANNOT TRAVEL
   THROUGH THE IMPORTER AT ALL. A width query maps onto a Bricks
   breakpoint; a feature query has none to map onto, so the converter turns
   the at-rule into a `code` element with `executeCode:true` and omits it
   silently as code-sensitive (`partial:true`, no other complaint). Bisected
   on 2026-10-14: of hero.css's 22 rules, the reduce block was the ONLY one
   that failed on its own.

   `no-preference`, not `reduce`, for the same reason `vds-btn-primary`'s
   sheen is: a visitor who has asked for less motion then gets no animation
   declared at all, rather than one declared and switched off. The rings
   rest at `opacity:0` in hero.css, so with no motion the panel shows the
   halo and the marker and nothing else — the honest static reading of a
   pulse, not three stacked circles parked on the dot.

   ⚠ (0,3,0), DELIBERATELY ONE STEP ABOVE THE RESTING RULE ABOVE. There is
   no tie to lose TODAY — `vds-geo-rings` carries no `.vds-geo-ring` rule
   in any of its three stores (checked, not assumed). The margin exists so
   that if a page block ever does gain one, it is emitted at (0,2,0) and
   this still wins: Bricks prints the page's global-class block AFTER this
   stylesheet, so an equal-specificity rule here would lose on source order
   and the rings would silently stop animating (QA-7).
   The delays are the comp's own (`geoRing` 3.2s, +1.06s, +2.13s).
   ⚠ `:nth-child` still counts 1/2/3: the wrapper's `::before` (the metro
   marker) and `::after` (the leader stem) are pseudo-elements and
   `:nth-child` does not count them. */
/* THE RESTING STATE IS HERE TOO, SO THE WHOLE RING TREATMENT — rest,
   keyframes, motion — is in one block. The keyframes and the
   `prefers-reduced-motion` gate are FORCED here (neither a selectorless
   @keyframes nor a feature query survives the importer); the resting state
   joins them by choice.
   ⚠ It could equally live in `hero.css` — a descendant rule DOES compile,
   into `vds-geo-rings`'s `selectors[]`. An earlier note claimed the
   importer drops such rules; that was wrong. Do not propagate it.
   `opacity:0` at rest is what makes the `no-preference` gate honest: a
   visitor who has asked for less motion sees the halo and the marker and
   no rings, rather than three circles parked on the dot.
   ⚠ NO TIE TO LOSE, AND THAT IS CHECKED, NOT ASSUMED: `vds-geo-rings`'s
   `_cssCustom` carries `.vds-geo-rings`, `::before` and `::after` only —
   nothing that names `.vds-geo-ring`. (0,2,0) is therefore uncontested.
   The animation below stays (0,3,0) so it still wins if a page block ever
   does gain one. */
.vds-geo-rings .vds-geo-ring{
  position:absolute;
  left:47.95%;
  top:60.59%;
  width:4.2%;
  height:4.2%;
  border-top-width:3px;
  border-right-width:3px;
  border-bottom-width:3px;
  border-left-width:3px;
  border-style:solid;
  border-color:var(--vds-red);
  border-radius:50%;
  opacity:0;
  transform:translate(-50%,-50%);
}
@media (prefers-reduced-motion:no-preference){
  .vds-geo-rings .vds-geo-ring.vds-geo-ring{
    animation: vdsGeoRing 3.2s ease-out infinite;
  }
  .vds-geo-rings .vds-geo-ring.vds-geo-ring:nth-child(2){ animation-delay: 1.06s; }
  .vds-geo-rings .vds-geo-ring.vds-geo-ring:nth-child(3){ animation-delay: 2.13s; }
}
/* VDS-GEOMAP-RUNTIME:BEGIN — generated, do not hand-edit */
/* =======================================================================
   VDS METRO COVERAGE MAP — the RUNTIME half of the service-area map.
   GENERATED by build/service-area/port-geomap.py between the two markers.
   DO NOT HAND-EDIT: the next run overwrites everything between them.

   Every selector in here matches something js/vds-geomap.js builds at
   runtime — the SVG, the six geography layers, the coverage wash, the scale
   bar, the markers and the city-list <li>. None of it can live in the
   section document: it would match nothing there, and one orphan selector
   becomes a `code` element and blocks the entire write (#45). The AUTHORED
   half — the wrapper, the frame, the legend swatches and the city-list
   frame — is in build/service-area/src/coverage.css, and that file carries
   the same note from the other side.

   ⚠ SPECIFICITY IS NOT AN ISSUE IN MOST OF THIS BLOCK, for the reason the
   US-map block above gives: runtime classes on runtime elements have no
   Bricks global class to tie with. The exceptions are the rules scoped
   `.vds-geomap .vds-usmap__*` — `.vds-geomap` IS a global class, but it is
   the SCOPE and not the target, and nothing Bricks emits for it reaches a
   `.vds-usmap__marker` that does not exist in any document.

   ⚠ THE DARK PALETTE USES `data-brx-theme`, WHICH IS BRICKS' OWN ATTRIBUTE
   (#65), AND SO DOES THE US-MAP BLOCK ABOVE AS OF 2026-10-15. That block
   was on the comp's `data-theme` and had never applied — measured on the
   live homepage, the national map painted light land on a dark page from
   F-23 onward. The user authorised the swap; both maps now follow the
   toggle. Never reach for `data-theme` on this site: it is the reference's
   attribute and nothing here ever sets it.
   ======================================================================= */
/* ============================================================
   GREATER PHOENIX COVERAGE MAP  (2026-09-18)
   Replaces the national AlbersUsa map that used to sit in section 2 of
   this page. The national map is untouched and still runs on the
   homepage. This file is loaded ONLY by geolocation/index.html, and
   every selector below is prefixed .vds-geomap, so nothing here can reach
   another page or the homepage map.

   The markers deliberately reuse the shared .vds-usmap__* vocabulary from
   styles.css (same dot, same pulse, same hover tag, same reduced motion
   handling at styles.css "Reduced motion (2026-09-18)"), so the metro
   map reads as the same family as the national one. Nothing in
   styles.css was edited to make that work.
   No em or en dashes.
   ============================================================ */
/* Frame aspect MUST match the builder viewBox (960 x 710), otherwise the
   percentage placed markers drift off their projected coordinates. */
.vds-geomap__svg {
  position: absolute; inset: 0;
  width: 100%; height: 100%;
  overflow: visible;
}
/* The shaded footprint: one soft disc per covered city, overlapped and
   blurred into a cloud. It follows the cities we actually cover rather
   than drawing a straight sided polygon over the empty desert between
   them, and it sits denser where the Valley is denser. Same shade token
   as the national map's state shading, so the key means the same thing. */
.vds-geomap__area {
  fill: var(--vds-map-shade);
  /* Toned down now that it washes over a real map instead of white paper.
     The token sits with the rest of the map palette further down. */
  fill-opacity: var(--vds-geomap-cover-op, .11);
  filter: blur(14px);
  pointer-events: none;
}
/* The scale bar now sits on terrain, so the label carries a halo drawn
   behind the glyphs (paint-order) to stay readable over a hillshade edge. */
.vds-geomap__scale { fill: none; stroke: var(--vds-ink-2); stroke-width: 2.5; opacity: .55; }
.vds-geomap__scale-txt {
  fill: var(--vds-ink-2); opacity: .85; font-weight: 700; font-size: 21px;
  letter-spacing: .02em;
  paint-order: stroke; stroke: var(--vds-geomap-halo, transparent); stroke-width: 5px;
  stroke-linejoin: round;
}
/* Labels. The builder measures each tag and pins only the ones that
   clear every tag already pinned and every other dot, re-running on
   resize, so a 390px phone simply keeps fewer of them. Phoenix is
   always pinned (shared .is-home rule). */
.vds-geomap .vds-usmap__marker.is-labeled .vds-usmap__tag { opacity: 1; }
.vds-geomap .vds-usmap__marker.is-cued .vds-usmap__tag { opacity: 1; z-index: 7; }
/* Tap targets. The shared marker is a 0 x 0 anchor point, so on a phone the
   only thing you can hit is the 8px dot. Here the marker gets a real 18px
   box centred on the same point (negative margins put the point back in the
   middle), and everything that used to hang off the marker's top left corner
   is re-anchored to its centre instead. The projected position does not
   move: left/top stay the percentage the builder wrote, and the box is
   centred on it. Phoenix is raised so its bigger dot always wins the
   overlap in the dense middle of the Valley. */
.vds-geomap .vds-usmap__marker {
  width: 18px; height: 18px;
  margin: -9px 0 0 -9px;
}
.vds-geomap .vds-usmap__marker.is-home { z-index: 5; }
.vds-geomap .vds-usmap__dot,
.vds-geomap .vds-usmap__marker::before,
.vds-geomap .vds-usmap__marker.is-home::after { left: 50%; top: 50%; }
/* Label anchoring, measured from the marker centre. The builder tries below,
   above, right then left and keeps the first position that clears every
   label already placed, every other dot, and the edge of the frame. Phoenix
   always keeps "below". These offsets must stay in step with placeLabels(). */
.vds-geomap .vds-usmap__tag { left: 50%; top: calc(50% + 9px); transform: translateX(-50%); }
.vds-geomap .vds-usmap__marker.is-home .vds-usmap__tag { top: calc(50% + 12px); }
.vds-geomap .vds-usmap__marker.lbl-t .vds-usmap__tag { left: 50%; top: calc(50% - 9px); transform: translate(-50%, -100%); }
.vds-geomap .vds-usmap__marker.lbl-r .vds-usmap__tag { left: calc(50% + 9px); top: 50%; transform: translateY(-50%); }
.vds-geomap .vds-usmap__marker.lbl-l .vds-usmap__tag { left: calc(50% - 9px); top: 50%; transform: translate(-100%, -50%); }
.vds-geomap .vds-usmap__dot { transition: transform .18s ease; }
.vds-geomap .vds-usmap__marker.is-cued .vds-usmap__dot { transform: scale(1.4); z-index: 6; }
/* Keyboard focus. The marker itself is a 0x0 anchor point, so the ring
   has to go on the dot or it would be invisible. */
.vds-geomap .vds-usmap__marker:focus { outline: none; }
.vds-geomap .vds-usmap__marker:focus-visible .vds-usmap__dot {
  outline: 3px solid var(--vds-accent-ink);
  outline-offset: 3px;
}
/* Legend swatches mirror the real markers: a big ringed dot for the one
   office, a small plain dot for a served market, the light shade for the
   covered area. */
/* The text list. It is the accessible representation of the map and it
   is built from the same array, so it can never drift from the pins. */
.vds-geomap__chips li {
  font-weight: 600;
  font-size: .8rem;
  line-height: 1;
  color: var(--vds-ink-2);
  background: var(--vds-surface);
  border: 1px solid var(--vds-border);
  border-radius: var(--vds-r-pill);
  padding: .45rem .8rem;
  transition: color .2s ease, border-color .2s ease, background .2s ease;
}
.vds-geomap__chips li:hover,
.vds-geomap__chips li.is-cued {
  color: var(--vds-ink);
  border-color: rgba(217, 33, 40, .45);
  background: var(--vds-surface-2);
}
.vds-geomap__chips li.is-home {
  color: var(--vds-ink);
  border-color: rgba(217, 33, 40, .45);
  display: inline-flex; align-items: center; gap: .45rem;
}
.vds-geomap__chips li.is-home::before {
  content: "";
  width: 8px; height: 8px; border-radius: 50%;
  background: var(--vds-map-dot);
  box-shadow: 0 0 0 1.5px var(--vds-map-dot-halo);
  flex: none;
}
@media (max-width: 479px) {
  .vds-geomap__scale-txt { font-size: 26px; }
  .vds-geomap__chips li { font-size: .74rem; padding: .38rem .65rem; }
  .vds-geomap .vds-usmap__tag { font-size: .62rem; padding: .18rem .34rem; }
}
/* ============================================================
   REAL GEOGRAPHY UNDER THE PHOENIX PINS  (2026-09-18, round 2)
   Juan: "let's just make it look like a map, a nice map with some
   terrain, and have the little dots there. Right now it is white
   and red dots in the middle of nothingness in the void."

   So the pins now sit on an actual map of the Valley. Everything under
   them is vector geometry generated from open data and projected by the
   SAME equirectangular math the pin builder uses, then inlined in the
   page as path data. There is no runtime fetch and no map tile service:

     county lines   US Census TIGER/Line cartographic boundaries 2023
     freeways       US Census TIGER/Line primary and secondary roads 2023
     rivers         US Census TIGER/Line area hydrography 2023 (Maricopa)
     urban footprint US Census 2020 urban areas
     relief         NASA SRTM 1 arc second elevation, contoured locally

   All four Census layers and SRTM are US federal works in the public
   domain. The map credits them anyway, bottom right.

   Draw order, back to front: ground, elevation tint, urban footprint,
   hillshade, rivers, county lines, freeway casing, freeway, coverage
   wash, range names, shields, scale bar, credit. The markers are a
   separate HTML layer above all of it, untouched: their left and top
   percentages are exactly what they were before this layer existed.
   No em or en dashes.
   ============================================================ */
:root {
  --vds-geomap-ground: #ece3d1;          /* open Sonoran desert */
  --vds-geomap-terrain: #a98f63;
  --vds-geomap-shade: #6d5c3e;
  --vds-geomap-shade-op: .115;
  --vds-geomap-urban: #f5f5f2;           /* the built up Valley reads pale and clean */
  --vds-geomap-urban-line: #e2e3de;
  --vds-geomap-water: #62a1c1;
  --vds-geomap-road: #f0a44f;
  --vds-geomap-road-case: #ffffff;
  --vds-geomap-county: #b5a992;
  --vds-geomap-label: #6f6557;
  --vds-geomap-halo: rgba(255, 255, 255, .85);
  --vds-geomap-shield-bg: #ffffff;
  --vds-geomap-shield-line: #c0743a;
  --vds-geomap-frame: rgba(0, 0, 0, .07);
  --vds-geomap-cover-op: .055;
}
:root[data-brx-theme="dark"] {
  /* Not the light map inverted. Dark cartography: a near black desert,
     the built up Valley lifted a step out of it, cool blue grey relief,
     and the freeways carrying the only warm colour on the map. */
  --vds-geomap-ground: #101317;
  --vds-geomap-terrain: #6d809b;
  --vds-geomap-shade: #000000;
  --vds-geomap-shade-op: .26;
  --vds-geomap-urban: #232a35;
  --vds-geomap-urban-line: #2e3744;
  --vds-geomap-water: #35708f;
  --vds-geomap-road: #c2874a;
  --vds-geomap-road-case: #0b0d10;
  --vds-geomap-county: #454e5c;
  --vds-geomap-label: #949cab;
  --vds-geomap-halo: rgba(0, 0, 0, .55);
  --vds-geomap-shield-bg: #171b22;
  --vds-geomap-shield-line: #8a5f30;
  --vds-geomap-frame: rgba(255, 255, 255, .08);
  --vds-geomap-cover-op: .055;
}
/* The whole geography is clipped to the frame, so nothing (blur included)
   paints outside the map panel. That is why .vds-geomap__svg can keep
   overflow visible for the marker tags without the map bleeding. */
.vds-geomap__ground { fill: var(--vds-geomap-ground); stroke: var(--vds-geomap-frame); stroke-width: calc(1.5 * var(--vds-geomap-k, 1)); }
/* Elevation tint. Six stacked bands from SRTM: 430, 520, 640, 800, 1050
   and 1400 m, each at the same low opacity, so the higher a range is the
   more layers cover it and the darker it gets. That is what separates the
   Estrellas and the White Tanks from the valley floor. */
.vds-geomap__terr { fill: var(--vds-geomap-terrain); fill-opacity: .05; }
/* Hillshade, sun at north west 45 degrees. This is what makes South
   Mountain and Camelback read INSIDE the urban footprint, where the
   elevation tint alone is buried under the city. */
.vds-geomap__shade { fill: var(--vds-geomap-shade); fill-opacity: var(--vds-geomap-shade-op); }
/* Every stroke below is multiplied by --vds-geomap-k, which the builder sets to the
   inverse of the frame scale. A 2.6 unit freeway is 2.4 screen px at 1440 AND
   2.2 screen px at 390, instead of thinning to under a pixel on a phone. */
.vds-geomap__urban { fill: var(--vds-geomap-urban); stroke: var(--vds-geomap-urban-line); stroke-width: calc(1 * var(--vds-geomap-k, 1)); }
.vds-geomap__water { fill: var(--vds-geomap-water); fill-opacity: .9; stroke: var(--vds-geomap-water); stroke-width: calc(1.8 * var(--vds-geomap-k, 1)); stroke-opacity: .5; }
.vds-geomap__county {
  fill: none; stroke: var(--vds-geomap-county); stroke-opacity: .85;
  stroke-width: calc(1.4 * var(--vds-geomap-k, 1));
  stroke-dasharray: calc(8 * var(--vds-geomap-k, 1)) calc(6 * var(--vds-geomap-k, 1));
}
.vds-geomap__road-case { fill: none; stroke: var(--vds-geomap-road-case); stroke-width: calc(5.6 * var(--vds-geomap-k, 1)); stroke-linecap: round; stroke-linejoin: round; stroke-opacity: .75; }
.vds-geomap__road { fill: none; stroke: var(--vds-geomap-road); stroke-width: calc(2.6 * var(--vds-geomap-k, 1)); stroke-linecap: round; stroke-linejoin: round; }
/* Range names and shields are re-scaled by the builder on every resize so
   they stay the same PHYSICAL size at 1440 and at 390. The halo is a
   stroke drawn behind the glyphs (paint-order), which is what keeps them
   readable where they cross a freeway or a hillshade edge. */
.vds-geomap__range {
  fill: var(--vds-geomap-label); fill-opacity: .72; font-style: italic; font-weight: 500;
  paint-order: stroke; stroke: var(--vds-geomap-halo); stroke-width: calc(5px * var(--vds-geomap-k, 1)); stroke-linejoin: round;
}
.vds-geomap__shield rect {
  fill: var(--vds-geomap-shield-bg); stroke: var(--vds-geomap-shield-line);
  stroke-width: 1.5; stroke-opacity: .85;
}
.vds-geomap__shield text {
  fill: var(--vds-geomap-label); font-weight: 700;
  letter-spacing: .01em;
}
.vds-geomap__credit {
  fill: var(--vds-geomap-label); fill-opacity: .45; font-weight: 500;
  paint-order: stroke; stroke: var(--vds-geomap-halo); stroke-width: calc(4px * var(--vds-geomap-k, 1)); stroke-linejoin: round;
}
/* ---- The panel, on an attribute that actually applies ---------------- */
:root{
  --vds-geomap-panel: linear-gradient(160deg, #f6f7f9, #ffffff);
}
:root[data-brx-theme="dark"]{
  --vds-geomap-panel: linear-gradient(160deg, #1c1c20, #141417);
}
.vds-geomap .vds-usmap__stage{ background: var(--vds-geomap-panel); }
/* VDS-GEOMAP-RUNTIME:END */


/* =====================================================================
   VDS-HQ-RUNTIME:BEGIN — hero router, QA F-37 (2026-10-22)

   WHY THESE RULES ARE HERE AND NOT IN THE SECTION DOCUMENT. Three reasons,
   each one a trap this build has already paid for:

   1. `css-orphan-check.py` ABORTS THE WHOLE WRITE on a selector whose class
      is not in the section's own HTML (#45). `.vds-hq-idle` does not exist
      in the document — vds-hq.js injects it — so it can only live here.
   2. `@media (prefers-reduced-motion:…)` CANNOT ENTER A BRICKS DOCUMENT. A
      WIDTH query maps onto a Bricks breakpoint; a FEATURE query has none, so
      the at-rule degrades to a `code` element and is dropped SILENTLY.
   3. ⚠⚠ THE CHILD THEME LOSES EVERY TIE (QA-7). Bricks prints the page's
      global-class block AFTER style.css and emits native settings
      element-type-qualified — `.vds-hq-a.brxe-div` is (0,2,0). EVERY RULE
      BELOW DOUBLES A CLASS to reach (0,3,0) or better. A lost tie is
      SILENT: it is in DevTools, greyed out, and nothing fails.

   ⚠ `html.vds-js` IS SET BY vds-hq.js IN THE <head>, SYNCHRONOUSLY, and the
   enqueue is deliberately NOT deferred and NOT in the footer. Every other
   script on this site is `defer`+footer; this one cannot be. The module is
   ABOVE THE FOLD, so a deferred upgrade paints all five answers expanded and
   then collapses them — a visible flash on the most-viewed block of the
   site. Do not "optimise" this enqueue to match the others.

   NO-JS IS A REAL STATE, NOT A FALLBACK: with no `vds-js` class none of the
   hiding below applies and the page is a plain, readable, crawlable list of
   five question/answer pairs carrying eight internal links.
   ================================================================== */

/* The hero's right column was DESKTOP-ONLY (`vds-hero-visual` carries
   `_display:none` natively with a `min-width:768px` override in its own
   `_cssCustom`). F-37 ships the router ON MOBILE, which the growth-flow
   graphic never was.

   ⚠ DONE HERE, NOT BY EDITING `vds-hero-visual`. The class is homepage-only
   today, so editing it would have been defensible — but `sa-guard.py` would
   then report a changed class, and "0 shared classes changed" has held for
   three rounds precisely because that number is never noise. Reverting this
   is deleting a block; reverting a class edit is a readback-and-patch. */
.vds-hero .vds-hero-visual.vds-hero-visual{ display: block; }

/* Rows are interactive only once the script has run. With no JS a <dt> is
   not a control and must not pretend to be one. */
html.vds-js .vds-hq .vds-hq-q.vds-hq-q{
  cursor: pointer;
  transition: border-color var(--vds-t-base), background var(--vds-t-base),
              color var(--vds-t-base);
}
/* ⚠ `background-color`, NOT `background`. Since 2026-10-22 the row carries a
   tinted disc behind the glyph as a background-IMAGE, and the shorthand resets
   background-image — hovering a row made its disc vanish. Nothing fails; the
   disc just blinks out under the cursor. Same trap as the section document. */
html.vds-js .vds-hq .vds-hq-q.vds-hq-q:hover{
  border-color: var(--vds-border-strong);
  background-color: var(--vds-surface-2);
  color: var(--vds-ink);
}
html.vds-js .vds-hq .vds-hq-q.vds-hq-q:hover::after{
  background-color: var(--vds-ink-2);
}

/* ---- THE CHEVRON (2026-10-22) ---------------------------------------
   The module shipped with NO affordance at all that a row opened — the
   user's words were that it "doesn't feel like I'm opening an accordion".
   This is that affordance.

   ⚠ IT IS DELIBERATELY JS-ONLY, AND THAT IS NOT THE USUAL SPLIT-REASON.
   Everything else here is JS-gated because it would be WRONG before the
   script runs; this would be a LIE. With no JavaScript every answer is
   already open and the row is not a control, so a "click to expand"
   chevron would promise behaviour the page does not have. It must never
   be moved into `hero-router.css` to "keep the glyphs together".

   ⚠ `margin-left:auto` IS WHAT RIGHT-ALIGNS IT. The row is a flex box
   whose middle item is an anonymous text run, so there is nothing to
   `justify-content` against — the auto margin is the only lever.

   ⚠⚠ EVERY `"` IN THE DATA URI MUST BE `%22`, AND NOTHING FAILS IF IT IS
   NOT. This shipped once with raw quotes in the SVG's own attributes; they
   closed the `url("…")` string early, the declaration was dropped, and what
   rendered was a 14px SOLID GREY SQUARE in every row — computed `maskImage`
   read `none` and no gate said a word. If you regenerate this URI, assert
   the computed `mask-image` is NOT `none`, not just that the rule is
   present. The five glyph URIs in `hero-router.css` are encoded the same
   way for the same reason. */
html.vds-js .vds-hq .vds-hq-q.vds-hq-q::after{
  content: "";
  margin-left: auto;
  flex: 0 0 14px;
  width: 14px;
  height: 14px;
  background-color: var(--vds-muted);
  -webkit-mask-image: url("data:image/svg+xml,%3Csvg%20xmlns=%22http://www.w3.org/2000/svg%22%20viewBox=%220%200%2024%2024%22%20fill=%22%23000%22%3E%3Cpath%20d=%22M12%2015.4%204.6%208l1.6-1.6L12%2012.2l5.8-5.8L19.4%208z%22/%3E%3C/svg%3E");
  mask-image: url("data:image/svg+xml,%3Csvg%20xmlns=%22http://www.w3.org/2000/svg%22%20viewBox=%220%200%2024%2024%22%20fill=%22%23000%22%3E%3Cpath%20d=%22M12%2015.4%204.6%208l1.6-1.6L12%2012.2l5.8-5.8L19.4%208z%22/%3E%3C/svg%3E");
  -webkit-mask-position: center;
  mask-position: center;
  -webkit-mask-repeat: no-repeat;
  mask-repeat: no-repeat;
  -webkit-mask-size: 14px 14px;
  mask-size: 14px 14px;
  transition: transform var(--vds-t-base) ease,
              background-color var(--vds-t-base) ease;
}
html.vds-js .vds-hq .vds-hq-q.vds-hq-q[aria-expanded="true"]::after{
  transform: rotate(180deg);
  background-color: var(--vds-accent-ink);
}

/* ---- ROW RHYTHM, AND WHY THE LIST GAP HAS TO GO ----------------------
   ⚠ A COLLAPSED ANSWER IS STILL A FLEX ITEM. It used to be `display:none`,
   which removed it from the flex flow entirely; it now stays in the DOM at
   `max-height:0` so it can be animated — and `.vds-hq-list`'s `gap:.4rem`
   therefore starts paying out FIVE gaps for five invisible boxes, i.e. 2rem
   of dead space inside the panel. The gap is replaced by a margin on the
   ROWS, which collapsed answers do not trigger.
   ⚠ `margin-top:.5rem` + the row's `.4rem` reproduces the `.9rem` the list
   shipped with — change one and change the other. */
html.vds-js .vds-hq .vds-hq-list.vds-hq-list{
  gap: 0;
  margin-top: .5rem;
}
html.vds-js .vds-hq .vds-hq-q.vds-hq-q{
  margin-top: .4rem;
}
html.vds-js .vds-hq .vds-hq-q.vds-hq-q:focus-visible{
  outline: 2px solid var(--vds-red);
  outline-offset: 2px;
}

/* SELECTED. The marker keeps the question's OWN glyph and turns red; it does
   NOT swap to a tick. A tick would need the circle filled AND a white glyph
   on top, and a masked pseudo-element can only paint ONE of those — the mask
   clips the background to the glyph, so the fill has nowhere to go. That
   would mean a second node, and an empty inline element is DROPPED or FOLDED
   by the importer and carries no class (handoff §3.5). Keeping the glyph is
   also the better read: the icon stays meaningful instead of becoming five
   identical ticks. */
/* ⚠ TWO BACKGROUND LAYERS, DISC FIRST. --vds-grad-brand-soft is a real
   linear-gradient (verified live, not assumed), so it is an IMAGE and the disc
   can sit on top of it as a second layer rather than being replaced by it.
   Written as the `background-image` longhand for the same reason as the hover
   rule above. Layer order is paint order: first listed is nearest the viewer. */
html.vds-js .vds-hq .vds-hq-q.vds-hq-q[aria-expanded="true"]{
  background-image: radial-gradient(circle at calc(.8rem + 12px) 50%, color-mix(in srgb, var(--vds-accent-ink) 13%, transparent) 0 14px, transparent 15px), var(--vds-grad-brand-soft);
  border-color: var(--vds-red);
  color: var(--vds-ink);
  font-weight: 600;
}
/* ⚠ THE `::before` OVERRIDE THAT USED TO SIT HERE IS GONE ON PURPOSE. It
   turned the selected glyph red — but since 2026-10-22 the glyph is brand
   red AT REST (it was a faint 12px grey mark and read as a "+"), so the
   override selected nothing. The selected state is now carried by the row's
   gradient, its red border, the rotated chevron and the open panel. Do not
   "restore" it: re-adding it changes nothing and reads as a live rule. */

/* ---- THE SLIDE (2026-10-22) ------------------------------------------
   Answers collapse only when the script is there to open them again. This
   WAS `display:none` / `display:flex`, which snapped — the open read as the
   page jumping rather than a drawer sliding.

   ⚠ THE HEIGHT IS SET BY vds-hq.js, NOT BY THIS FILE. `max-height` cannot
   animate to `auto`, and a guessed cap (`max-height:40rem`) makes the OPEN
   look snappy and the CLOSE look broken: 70% of the duration elapses before
   anything visibly moves. The script measures the panel and writes the exact
   pixel height, which is what jQuery's slideToggle does and the only way to
   get a true ease in BOTH directions. If the inline height ever stops being
   written, the panel will not open at all — it is load-bearing, not polish.

   ⚠ `overflow:hidden` + `max-height:0` COLLAPSES THE PADDING AND BORDER TOO,
   because the site is `box-sizing:border-box`. Only the MARGINS live outside
   that box, which is why they are the one thing zeroed by hand here.

   ⚠⚠ `visibility` IS AN ACCESSIBILITY REQUIREMENT, NOT A VISUAL ONE. A
   `max-height:0` box still contains eight real links; without
   `visibility:hidden` a keyboard user tabs into a collapsed panel and the
   focus ring goes somewhere invisible. The `0s linear .28s` delay is what
   keeps the content on screen for the length of the CLOSING animation —
   drop the delay and the answer vanishes instantly and only the box
   animates. */
html.vds-js .vds-hq .vds-hq-a.vds-hq-a{
  display: flex;
  overflow: hidden;
  visibility: hidden;
  /* ⚠⚠ `min-height:0` IS NOT TIDYING — WITHOUT IT `max-height:0` DOES
     NOTHING. The answer is a flex ITEM in a column flex container, so its
     `min-height` resolves to `auto`, i.e. the automatic minimum size — and
     that floor INCLUDES padding and borders and OUTRANKS `max-height`. The
     panel collapsed to 27.6px, not 0 (25.6px of padding + 2px of border),
     and five of those stacked up as ~28px of mystery dead space between the
     closed rows. It measured as `max-height: 0px` in DevTools the whole
     time. If the gaps ever look wrong again, measure the CLOSED panel's
     `getBoundingClientRect().height` — do not trust the computed value. */
  min-height: 0;
  max-height: 0;
  opacity: 0;
  margin-top: 0;
  margin-bottom: 0;
  /* ⚠⚠ THE PADDING AND THE BORDER HAVE TO COLLAPSE TOO, AND THIS IS THE
     SECOND TIME THIS BOX REFUSED TO REACH ZERO. `box-sizing:border-box`
     FLOORS A BORDER-BOX HEIGHT AT padding + border — the content box cannot
     go negative — so `max-height:0` on a panel with .8rem of padding and a
     1px border settles at 27.6px, not 0, and computed style still reads
     `max-height: 0px` while it does it. Five of those are ~138px of dead
     space inside the panel. `min-height:0` above is also required (a column
     flex item's automatic minimum size otherwise outranks max-height) —
     they are two different bugs with the same symptom, and BOTH fixes have
     to stay. ⇨ Measure the closed panel's bounding rect, never its
     computed max-height. */
  padding-top: 0;
  padding-bottom: 0;
  border-top-width: 0;
  border-bottom-width: 0;
  transition: max-height .28s cubic-bezier(.4, 0, .2, 1),
              opacity .16s ease,
              padding .28s cubic-bezier(.4, 0, .2, 1),
              border-width .28s cubic-bezier(.4, 0, .2, 1),
              margin .28s cubic-bezier(.4, 0, .2, 1),
              visibility 0s linear .28s;
}
html.vds-js .vds-hq .vds-hq-a.vds-hq-a[data-open="1"]{
  visibility: visible;
  opacity: 1;
  margin-top: .35rem;
  margin-bottom: .1rem;
  padding-top: .8rem;
  padding-bottom: .8rem;
  border-top-width: 1px;
  border-bottom-width: 1px;
  transition: max-height .32s cubic-bezier(.16, 1, .3, 1),
              opacity .26s ease .06s,
              padding .32s cubic-bezier(.16, 1, .3, 1),
              border-width .32s cubic-bezier(.16, 1, .3, 1),
              margin .32s cubic-bezier(.16, 1, .3, 1),
              visibility 0s;
}

/* Injected by vds-hq.js, so it is absent from the section document and
   `css-orphan-check.py` would have aborted the write on it. */
html.vds-js .vds-hq .vds-hq-idle.vds-hq-idle{
  margin: .9rem 0 0;
  font-size: .82rem;
  line-height: 1.5;
  color: var(--vds-muted);
}
html.vds-js .vds-hq .vds-hq-idle.vds-hq-idle[hidden]{ display: none; }

/* §0.1 RESERVED THE RIGHT TO FALL BACK TO COMPACT CHIPS if the rich answer
   reads busy — "a single class swap, not a rebuild". THIS IS THAT SWAP:
   add `vds-hq-compact` to `.vds-hq` and the service links become pills with
   their descriptor hidden. Nothing in the markup changes. */
.vds-hq.vds-hq-compact .vds-hq-tags.vds-hq-tags{ flex-direction: row; flex-wrap: wrap; gap: .35rem; }
.vds-hq.vds-hq-compact .vds-hq-tag.vds-hq-tag{ border-radius: var(--vds-r-pill); font-size: .73rem; font-weight: 500; padding: .3rem .6rem; }
.vds-hq.vds-hq-compact .vds-hq-tag-d.vds-hq-tag-d{ display: none; }

/* ---- THE ATTRACT PULSE (2026-10-22) ----------------------------------
   §12c listed this as CONSIDERED AND LEFT OUT. The user asked for it on
   2026-10-22, so it ships — but every objection recorded against it then is
   still true, and each one is answered by a specific decision here:

   "ambient motion on a five-item list reads cheap fast"  -> THE REST IS IN
     THE KEYFRAMES. The motion occupies 26% of a 4s cycle; the other 2.96s is
     a flat line. It loops, but it is a periodic invitation, not continuous
     motion. (It SHIPPED on 2026-10-22 as a finite two-beat greeting and the
     user's verdict was "it pulses twice and just stops, what a waste" — that
     is why it loops now. Do not quietly put the cap back.)
   "it needs a stop-on-first-interaction rule"            -> `.vds-hq-seen`,
     added by vds-hq.js on the first pointer or focus that reaches the module
     (and on any toggle). A pulse still running at someone who is already
     reading the thing is the failure mode.
   "it needs its own reduced-motion handling"             -> named in the
     block at the end of this file, like every other motion here.

   ⚠ IT PULSES THE GLYPH, NOT THE ROW. Five rows breathing in unison is the
   "cheap" failure; one 18px mark growing is a pointer at the affordance. The
   glyph is also already the eye-catch — it was made brand red for exactly
   this job on 2026-10-22 — so this amplifies a decision instead of adding a
   competing one.

   ⚠⚠ THIS LOOPS FOREVER, SO WCAG 2.2.2 IS IN SCOPE AND YOU SHOULD KNOW
   WHAT IT IS RESTING ON. 2.2.2 wants a mechanism to pause, stop or hide
   motion that starts automatically and runs past five seconds. This module
   has two: `prefers-reduced-motion`, which removes it entirely, and
   stop-on-first-interaction, which ends it for the life of the page the
   moment a pointer or focus reaches the module. Neither is a labelled
   control, which is the honest caveat — the first is the de facto standard
   for decorative motion and the second is undiscoverable.
   ⇨ THE EARLIER VERSION SIDESTEPPED THIS by capping the run at 3.68s, under
   the five-second line. The user asked for a pulse that does not stop, so
   the cap is gone and the tradeoff is explicit instead of hidden. If this
   ever needs to be airtight, the cheap fix is a real control, not a shorter
   loop. (The comp's 6s review rotator was dropped for failing 2.2.2 with no
   mechanism at all — that is a different case, not a precedent against this
   one: it moved CONTENT, this moves a decorative mark.)

   ⚠⚠ THESE ARE LONGHANDS ON PURPOSE — DO NOT "TIDY" THEM INTO THE
   `animation:` SHORTHAND. The shorthand RESETS `animation-delay` to 0, and
   this rule outranks the five stagger rules below it (6 classes vs 5), so
   folding it up would silently flatten the cascade into one simultaneous
   flash. Nothing would fail. With longhands, `animation-delay` is set by
   nobody here, so the stagger applies at any specificity. */
/* ⚠⚠ THE REST IS INSIDE THE KEYFRAMES, AND THAT IS THE WHOLE TRICK. The
   cycle is 4s but the motion occupies only the first 26% of it (~1.04s) —
   a double beat, then 2.96s of stillness. That is why this can loop forever
   without reading as a twitch: `animation-iteration-count: infinite` on a
   keyframe set that is mostly a flat line is a PERIODIC INVITATION, not
   continuous motion. Shortening the cycle without shortening the beat turns
   it straight back into a throb.
   ⚠ THE DOUBLE BEAT IS DELIBERATE — a big beat at 5% and a smaller echo at
   18%. A single throb reads mechanical; the second, smaller one is what makes
   it read as alive. Keep both or drop to one and re-look; do not add a third. */
@keyframes vds-hq-pulse{
  0%   { transform: scale(1); }
  /* ⚠ THE AMPLITUDE WAS CHOSEN BY LOOKING, NOT BY TASTE. At 1.25 the true
     peak frame was indistinguishable from the resting frame in a screenshot
     (glyph 18px -> 22.5px); 1.55 reads chunky against the row text. ~1.4
     peaks at ~25.2px and still clears the row's .65rem gap and .8rem left
     padding with ~8px to spare, so nothing collides and nothing is clipped —
     the row sets no `overflow`. The disc behind it is 30px, so the glyph
     stays inside its own chip at peak.
     ⇨ Comparison render: scratch/shots/hq-pulse/amplitude.png. If this is
     ever retuned, re-render it rather than guessing: a still under-reports
     motion and the arithmetic does not tell you when it starts looking
     cheap. */
  5%   { transform: scale(1.42); }
  14%  { transform: scale(1); }
  18%  { transform: scale(1.18); }
  26%  { transform: scale(1); }
  100% { transform: scale(1); }
}
html.vds-js .vds-hq.vds-hq:not(.vds-hq-seen) .vds-hq-q.vds-hq-q::before{
  animation-name: vds-hq-pulse;
  animation-duration: 4s;
  animation-timing-function: cubic-bezier(.4, 0, .2, 1);
  animation-iteration-count: infinite;
}
/* ⚠ STAGGERED BY `data-k`, NOT BY `:nth-child`. The rows are <dt> elements
   interleaved with their <dd> answers, so the question rows are children
   1,3,5,7,9 — and `:nth-of-class` does not exist, which is the same trap
   that makes `vds-bento-item`'s card order load-bearing. `data-k` is already
   on every row, is unique, and does not care what order they sit in. */
html.vds-js .vds-hq .vds-hq-q.vds-hq-q[data-k="conv"]::before { animation-delay: .12s; }
html.vds-js .vds-hq .vds-hq-q.vds-hq-q[data-k="loc"]::before  { animation-delay: .24s; }
html.vds-js .vds-hq .vds-hq-q.vds-hq-q[data-k="roi"]::before  { animation-delay: .36s; }
html.vds-js .vds-hq .vds-hq-q.vds-hq-q[data-k="reach"]::before{ animation-delay: .48s; }

/* ⚠ THIS TRANSITION IS THE GRACEFUL STOP, NOT DECORATION. When vds-hq.js
   adds `.vds-hq-seen` the animation is removed mid-flight and the computed
   transform SNAPS from scale(1.25) back to scale(1). A transition on the
   same property catches that jump and eases it out instead. Without it,
   clicking a row during the first 3.7s makes every other glyph visibly
   twitch at the moment you interact — which is worse than no pulse. */
html.vds-js .vds-hq .vds-hq-q.vds-hq-q::before{
  transition: transform .22s cubic-bezier(.4, 0, .2, 1);
}

/* ⚠ EVERY MOTION ADDED ON 2026-10-22 MUST BE LISTED HERE TOO. The slide,
   the chevron rotation and the row hover are all new since this block was
   written, and a motion rule that is not named below is simply not covered
   — nothing fails, it just moves for people who asked it not to. */
@media (prefers-reduced-motion: reduce){
  html.vds-js .vds-hq .vds-hq-q.vds-hq-q{ transition: none; }
  html.vds-js .vds-hq .vds-hq-q.vds-hq-q::after{ transition: none; }
  html.vds-js .vds-hq .vds-hq-a.vds-hq-a,
  html.vds-js .vds-hq .vds-hq-a.vds-hq-a[data-open="1"]{
    transition: visibility 0s;
  }
  .vds-hq .vds-hq-cta.vds-hq-cta .vds-arrow{ transition: none; }
  /* THE ATTRACT PULSE AND ITS GRACEFUL STOP. ⚠ THESE TWO SELECTORS ARE
     CHARACTER-FOR-CHARACTER THE ONES ABOVE, SO SPECIFICITY IS IDENTICAL
     BY CONSTRUCTION AND SOURCE ORDER DECIDES — which this block wins,
     being last in the file. Do not "simplify" either one: a shorter
     selector loses the tie and loses it SILENTLY (QA-7), and the result
     is a module that still pulses at someone who asked for no motion.
     `animation: none` is the shorthand on purpose here — it clears the
     stagger delays as well as the name. */
  html.vds-js .vds-hq.vds-hq:not(.vds-hq-seen) .vds-hq-q.vds-hq-q::before{ animation: none; }
  html.vds-js .vds-hq .vds-hq-q.vds-hq-q::before{ transition: none; }
}
/* VDS-HQ-RUNTIME:END */

/* ==========================================================================
   HEADER TICKER — QA round 2 Wave E (F-11, 2026-11-02)
   ==========================================================================
   Replaces the static press banner in the `vds26-announce` band above
   `.site-header` on template 2710. The band wrapper is still a Bricks
   element carrying the global class `vds26-announce` (background, bottom
   border, theme transition) — none of that changed. Everything INSIDE it is
   now printed by the `[vds_ticker]` shortcode in functions.php.

   ⚠ WHY THESE RULES ARE HERE AND NOT IN A GLOBAL CLASS. The ticker markup
   is rendered by PHP, so Bricks has never heard of it. Bricks only emits a
   global class's CSS when that class is attached to an element in a
   document it renders — a `vds-ticker` global class would therefore sit in
   the design system emitting nothing, and the band would render unstyled.
   The child theme is the only store that reaches this markup.

   ⚠ NOTHING HERE CONTESTS A BRICKS RULE. Every selector below targets a
   `.vds-ticker*` class that exists only in the PHP output, so there is no
   element-type-qualified `.x.brxe-y` (0,2,0) twin to tie with (handoff §3
   item 2). The ONE exception is the band-hide rule at the end, which does
   target `.vds26-announce` and is doubled to (0,3,0) on purpose.

   ⚠ `span{font-size:16px;line-height:24px;letter-spacing:0;
   text-transform:none}` ships site-wide at (0,0,1) (handoff §3 item 3), and
   a matched declaration beats an inherited one. It would strip the ticker's
   uppercase AND its letter-spacing, not just its size, so the label span
   restates all four rather than inheriting them.
   ========================================================================== */
.vds-ticker{
  position:relative;
  max-width:var(--vds-container);
  margin-left:auto;
  margin-right:auto;
  /* Symmetric reserve. The pause button is absolutely positioned into the
     right-hand reserve so it never overlays moving text, and the matching
     left reserve keeps the run of items optically centred whether or not
     JavaScript has added the button. Reserving it in CSS rather than with a
     flex sibling also means no layout shift when the deferred script runs. */
  padding:.5rem calc(var(--vds-gutter) + 1.75rem);
}

.vds-ticker-viewport{
  display:flex;
  /* Load-bearing twice over: it is what hides the second track until its
     turn, and it is what keeps the translated track from ever becoming
     document overflow (the standing "no horizontal scroll whatsoever"
     requirement — hscan skips anything with a clipping ancestor). */
  overflow:hidden;
}

.vds-ticker-track{
  display:flex;
  flex:0 0 auto;
  align-items:center;
  /* `min-width:100%` + `space-around` is what makes the loop seamless with
     no JS and no measurement. Each track is at least a viewport wide, so
     translating it by -100% OF ITS OWN WIDTH lands the second copy exactly
     where the first started. With few items the spare room is spread
     between them instead of leaving a blank half-lap; with many, the track
     is wider than the viewport and space-around has nothing to do. */
  min-width:100%;
  justify-content:space-around;
  margin:0;
  padding:0;
  list-style:none;
}

.vds-ticker-item{
  display:flex;
  align-items:center;
  white-space:nowrap;
}

/* The separator is a pseudo-element, not an empty inline tag. It follows
   EVERY item on purpose, including the last: at the seam between the two
   tracks the final dot is what keeps the rhythm unbroken through the loop.
   (It is suppressed in the reduced-motion block below, where only one
   track renders and a trailing dot would just dangle.)
   The red dot is the retired press banner's own `vds26-announce-dot`,
   carried forward so the band reads as the same furniture it replaced. */
.vds-ticker-item::after{
  content:"";
  flex:0 0 auto;
  width:4px;
  height:4px;
  margin-left:1.4rem;
  margin-right:1.4rem;
  border-radius:50%;
  background-color:var(--vds-red);
  opacity:.55;
}

.vds-ticker-item .vds-ticker-label,
.vds-ticker-item .vds-ticker-link{
  /* (0,2,0) — comfortably over the site-wide bare `span` at (0,0,1), and
     restating all four of the properties that rule sets. */
  font-size:.72rem;
  line-height:1.4;
  letter-spacing:.14em;
  text-transform:uppercase;
  font-weight:600;
  color:var(--vds-ink-2);
}

.vds-ticker-item .vds-ticker-link{
  color:var(--vds-accent-ink);
  text-decoration:none;
  transition:opacity var(--vds-t-base);
}

.vds-ticker-item .vds-ticker-link:hover{
  text-decoration:underline;
}

@media (max-width:480px){
  .vds-ticker{
    padding-top:.42rem;
    padding-bottom:.42rem;
  }
  .vds-ticker-item .vds-ticker-label,
  .vds-ticker-item .vds-ticker-link{
    font-size:.65rem;
    letter-spacing:.1em;
  }
  .vds-ticker-item::after{
    margin-left:.9rem;
    margin-right:.9rem;
  }
}

/* --- the motion itself -------------------------------------------------
   Both the @keyframes and the animation live inside `no-preference`, so a
   user who asked for less motion is never served either. Wrapping the
   keyframes too (rather than only the animation) keeps the whole mechanism
   in one place — there is no orphan animation definition to wonder about.
   The duration comes from the settings page as an inline custom property;
   the 45s fallback is only reached if that attribute is ever missing. */
@media (prefers-reduced-motion: no-preference){
  @keyframes vds-ticker-scroll{
    from{ transform:translateX(0); }
    to{ transform:translateX(-100%); }
  }

  .vds-ticker-track{
    animation:vds-ticker-scroll var(--vds-ticker-dur,45s) linear infinite;
  }

  /* Soften both ends. Without this an item is CHOPPED mid-letter at the
     viewport edge on every lap, which reads as a rendering fault rather
     than as motion — it was plainly visible against the pause button at
     1440 and at both edges at 390. The mask is inside `no-preference`
     ON PURPOSE: with reduced motion the list is static and wrapped, so
     nothing ever scrolls out and a fade would just dim real content. */
  .vds-ticker-viewport{
    -webkit-mask-image:linear-gradient(to right,
      transparent 0, #000 2.5rem, #000 calc(100% - 2.5rem), transparent 100%);
    mask-image:linear-gradient(to right,
      transparent 0, #000 2.5rem, #000 calc(100% - 2.5rem), transparent 100%);
  }

  @media (max-width:480px){
    /* 2.5rem each side would eat 80px of a 390px band. */
    .vds-ticker-viewport{
      -webkit-mask-image:linear-gradient(to right,
        transparent 0, #000 1.1rem, #000 calc(100% - 1.1rem), transparent 100%);
      mask-image:linear-gradient(to right,
        transparent 0, #000 1.1rem, #000 calc(100% - 1.1rem), transparent 100%);
    }
  }

  /* Hover is the convenience; `.is-paused` is the WCAG 2.2.2 mechanism and
     is set by the button vds-ticker.js adds. */
  .vds-ticker:hover .vds-ticker-track,
  .vds-ticker.is-paused .vds-ticker-track{
    animation-play-state:paused;
  }

  /* Separate rule ON PURPOSE: `:has()` in the list above would invalidate
     the whole list wherever it is unsupported, taking hover and the pause
     button down with it. Keyboard focus on a ticker LINK stops the band so
     it can actually be clicked; focus on the toggle button deliberately
     does NOT, or pressing "play" would appear to do nothing while the
     button still held focus. */
  .vds-ticker:has(.vds-ticker-link:focus-visible) .vds-ticker-track{
    animation-play-state:paused;
  }
}

@media (prefers-reduced-motion: reduce){
  /* Nothing moves, so the duplicate track is pure noise — and with it gone
     the items wrap onto as many rows as they need instead of being clipped
     by the viewport. No horizontal overflow is introduced either way. */
  .vds-ticker-track[aria-hidden="true"]{
    display:none;
  }
  .vds-ticker-track{
    flex-wrap:wrap;
    justify-content:center;
    row-gap:.2rem;
    /* ⚠ `flex-wrap:wrap` ALONE DOES NOTHING HERE AND LOOKS LIKE IT WORKED.
       The track is a flex ITEM of `.vds-ticker-viewport` carrying
       `flex:0 0 auto` + `min-width:100%`, so it sizes to its CONTENT and
       refuses to shrink — it simply grew wider than the viewport and was
       clipped by `overflow:hidden`, losing the last item and half of the
       one before it. Wrapping only has something to act on once the track
       is held to the viewport's width. Reading back `flex-wrap:wrap` is
       NOT the check; the check is that nothing is clipped. */
    flex-shrink:1;
    flex-basis:100%;
    max-width:100%;
  }
  .vds-ticker-item:last-child::after{
    display:none;
  }
}

/* --- the pause/play button --------------------------------------------
   Injected by vds-ticker.js, and only when motion is actually running.
   The glyph is drawn with borders rather than set in a font so it cannot
   be hit by an emoji-font substitution: two bars while playing, a triangle
   once paused. */
.vds-ticker-toggle{
  position:absolute;
  top:50%;
  right:var(--vds-gutter);
  transform:translateY(-50%);
  display:flex;
  align-items:center;
  justify-content:center;
  width:22px;
  height:22px;
  padding:0;
  border:0;
  border-radius:50%;
  background:transparent;
  color:var(--vds-ink-2);
  cursor:pointer;
  opacity:.65;
  transition:opacity var(--vds-t-base),background-color var(--vds-t-base);
}

.vds-ticker-toggle:hover{
  opacity:1;
  background-color:var(--vds-surface-2);
}

.vds-ticker-toggle:focus-visible{
  opacity:1;
  outline:2px solid var(--vds-red);
  outline-offset:2px;
}

/* playing -> the "pause" glyph: two bars */
.vds-ticker-toggle::before{
  content:"";
  display:block;
  width:8px;
  height:9px;
  border-left:3px solid currentColor;
  border-right:3px solid currentColor;
}

/* paused -> the "play" glyph: a triangle, drawn from borders */
.vds-ticker.is-paused .vds-ticker-toggle::before{
  width:0;
  height:0;
  margin-left:2px;
  border-left:8px solid currentColor;
  border-right:0;
  border-top:5px solid transparent;
  border-bottom:5px solid transparent;
}

/* --- the band collapses when the ticker is switched off ----------------
   The settings page can disable the ticker, in which case the shortcode
   prints nothing and the Bricks band wrapper would otherwise be left as a
   bare 1px bottom border across every page.
   ⚠ (0,3,0) IS LOAD-BEARING. Bricks emits `.vds26-announce.brxe-div
   {display:block}` at (0,2,0) and the child theme is printed BEFORE it, so
   a (0,2,0) rule here would tie and silently lose (handoff §3 item 2).
   `:not()` and `:has()` each take the specificity of their argument, so
   `.vds26-announce.vds26-announce:not(:has(.vds-ticker))` is 2 classes plus
   the 1 inside, = (0,3,0). Kept in its own rule because an unsupported
   `:has()` invalidates the whole selector list it appears in. */
.vds26-announce.vds26-announce:not(:has(.vds-ticker)){
  display:none;
}
