/* ============================================================
   LINK-IN-BIO LANDING PAGE — COMPONENT LAYER
   ------------------------------------------------------------
   Design tokens, the reset, the type scale, .container and
   .section all live in _template.css and load before this file.
   Nothing here declares a colour, a font size, or a raw pixel
   margin. Components consume semantic tokens only.

   To retint the whole page, edit --brand-base and --accent-base
   at the top of _template.css. Nothing in this file changes.
   ============================================================ */

:root {
  /* Section rhythm override. A link-in-bio page wants to be
     denser than the system default of 96px / 64px. Overriding a
     token in the consuming layer is allowed; referencing a
     primitive is not. */
  --section-y: var(--space-9);            /* 64px */

  /* Component dimensions, not spacing. The 8pt rule governs
     margins, padding, and gaps — not the height of a banner or
     the height of a control. */
  /* THE FULL SCREEN, at both breakpoints. This was a clamp — 544 to
     768px on a phone, 608 to 928 on a desktop — which left a strip
     of the next section showing under the hero on most screens. The
     client build runs it to the fold: the photograph is the first
     screen and the page starts under it.

     svh, not vh: on a phone the URL bar takes a share of vh, and a
     100vh hero puts the form under it until the bar collapses.

     min-height, not height, so the copy block can still outgrow the
     screen on a short landscape phone instead of being clipped. */
  --hero-min:     100svh;
  --hero-min-lg:  100svh;
  /* HOW MUCH SCROLL THE REVEAL IS SPENT OVER, on top of the screen
     the hero already occupies. One screen is the figure that reads as
     deliberate: the corners are still moving when the reader's thumb
     is, so the effect is legibly tied to their own scrolling rather
     than playing at them. Half a screen and it is over before it has
     registered; two and the page feels stuck.

     It buys the length honestly — the hero is two screens of scroll
     now instead of one, and everything below starts that much lower.
     Take it to 0svh to keep the pinning and lose the movement, or
     drop the height gate on .hero-offer to remove both. */
  --hero-runway:  100svh;
  --hero-seam:     7rem;                  /* 112px — photo-to-page fade */
  --hero-seam-lg: 10rem;                  /* 160px */
  /* The other half of that fade, on the far side of the hero's bottom
     edge. --hero-seam takes the footage down to --color-bg-primary;
     this takes --color-bg-primary back out again into whatever ground
     the next section has. The two are a pair and the second is the
     longer of them: the hero's own ramp is hidden work over a
     photograph, this one is out in the open over flat colour, where
     the eye finds a boundary much more easily. */
  --seam-in:       9rem;                  /* 144px */
  --seam-in-lg:   16rem;                  /* 256px */
  /* A HEIGHT, NOT A BOX: the logo keeps its own aspect ratio, so the
     max-widths below only bite on a wide wordmark.

     80/120, up from 64/88. The smaller pair was set against a
     wordmark of roughly 8:1, where 88px tall is 700px wide and the
     cap is what you see. A near-square mark at 88px is a small badge
     in the corner; at 120px it has the presence the thing naming the
     brand needs. A wide wordmark still hits the cap first. */
  --hero-logo:      5rem;                 /* 80px  */
  --hero-logo-lg:  7.5rem;                /* 120px */
  --hero-logo-max:  15rem;                /* 240px */
  --hero-logo-max-lg: 20rem;              /* 320px */
  /* ---- section 5, the stays rail -------------------------------
     The card's own corner. --radius-lg is 16px and correct on a
     control; on a 420px picture it reads as a square with the edges
     filed off. 24px is the 8pt step that matches the reference's
     25px and stays on the grid. */
  --stay-radius:  1.5rem;                 /* 24px */

  /* The card floats over the section rather than sitting on it, and
     a long soft shadow with a negative spread is what reads as float
     rather than as a drop shadow.

     0.35, not the 0.8 this was while the section was pinned dark. A
     near-black shadow is invisible on a dark ground and needs the
     weight; on the light ground this section now takes, the same
     alpha prints a grey bruise under every card. */
  --stay-lift: 0 1.5rem 3rem -1.875rem rgba(0, 0, 0, 0.35);

  /* THE CARD SCRIM, as its own stop set for the same reason the hero
     has one: a multi stop ramp is not something a flat overlay token
     can express. Nothing happens for the top 30% of the picture and
     it is nearly solid by the bottom, which is the shape that buys
     the panel its contrast without greying the photograph.

     THE COLOUR COMES FROM THE THEME, ONLY THE ALPHAS LIVE HERE. The
     stops compose --color-overlay-scrim-rgb, which is white on a light
     page and blue-black on a dark one — so the same five alphas paint a
     pale wash under dark type or a dark wash under light type, and
     nothing in this section names either. See the OVERLAY note in
     _template.css for why that works and where it stops working.

     The alphas were tuned for the dark wash and hold for the light one
     without change, because a white wash is the more forgiving of the
     two: at 0.92 it lands near-white over any photograph, dark or
     bright, and gray-950 ink on near-white clears 4.5:1 by a mile.
     Measured figures for both polarities are in README.md under the
     stays section. The placeholder is a flat mid grey — RE-MEASURE
     against real photography, and if a client's pictures are dark at
     the foot of the frame on a LIGHT build (or bright on a dark one),
     --stay-scrim-3 and -4 are the two stops to raise. */
  --stay-scrim-0: rgba(var(--color-overlay-scrim-rgb), 0);
  --stay-scrim-1: rgba(var(--color-overlay-scrim-rgb), 0.15);
  --stay-scrim-2: rgba(var(--color-overlay-scrim-rgb), 0.55);
  --stay-scrim-3: rgba(var(--color-overlay-scrim-rgb), 0.88);
  --stay-scrim-4: rgba(var(--color-overlay-scrim-rgb), 0.92);

  /* The diagonal sheen over the top of that. Warm white rather than
     plain white — a neutral sheen over a photograph reads as haze,
     a warm one reads as light. */
  --stay-sheen-1: rgba(228, 213, 196, 0.40);
  --stay-sheen-0: rgba(255, 255, 255, 0.05);
  --stay-sheen-2: rgba(228, 213, 196, 0.12);

  /* The pill on the card: a pane of the photograph, tinted and
     blurred, the same device the hero's form uses. */
  --stay-btn-bg: rgba(var(--color-overlay-scrim-rgb), 0.55);

  /* A hard edge at the glyph, under both strings in the panel. The
     scrim is what buys them their contrast and the figures over
     --stay-scrim-0 are measured WITHOUT this — so it is margin on
     top of a pass, not the thing carrying it. It matters most where
     a bright detail in a photograph lands under a counter. */
  --stay-text-shadow: 0 1px 2px rgba(var(--color-overlay-scrim-rgb), 0.55);

  /* THE GLOW behind the section: the first card's photograph at rest
     and the hovered card's while the pointer is on one (see the glow
     block in script.js). Taken from the Cabin Collective build
     (2026-10-15, kept on Gooseberry), where at 70px and 30% the change
     on hover was too subtle to notice. 24px keeps the photograph's
     shapes — treeline, sky, roofline — readable as that property
     rather than reducing it to a colour, and 55% makes the change
     obvious as the pointer moves between cards.

     The tint went up with it, 0.22 to 0.30, and that is a contrast
     call rather than a taste one. A lighter blur averages less, so a
     bright sky stays bright behind the heading; worked through for a
     white patch (brightness 0.6, this tint, 55% over the brand-950
     ground) the gray-300 subtitle still clears 4.5:1. Re-check if
     either number goes up again. */
  --stay-glow-blur:      24px;
  --stay-glow-opacity:   0.55;
  --stay-glow-tint:      rgba(9, 11, 14, 0.30);

  /* The filled buttons' --btn-* tokens are in their own rule below the
     dark-scope ramps — see "the filled buttons" there. */

  /* ---- section 8, the testimonials deck ------------------------
     The card's corner. Larger than --radius-lg for the reason the
     stay card's is: this is a 540px object, and 16px on it reads as
     a square with the edges filed off. */
  --tm-radius: 1.5rem;                    /* 24px */

  /* The centre card's width and the arrow's size, as tokens, because
     the arrows are placed off the card's edge and the two numbers have
     to agree. 42vw between 300 and 540px is the card; the arrow is a
     48 to 56px disc. */
  --tm-card-w: clamp(18.75rem, 42vw, 33.75rem);
  --tm-arrow:  clamp(3rem, 3.4vw, 3.5rem);

  /* THE CARD'S TWO STATES. A pale surface with dark type beside you,
     and a brand-dark surface with light type when it is the one you
     are reading. No semantic token pair says "this inverts on a
     class", so the defaults are here and .is-center overrides them.

     These are the ORDINARY tokens now the section follows the page.
     They were pinned to raw grays while the band was forced dark,
     which meant a light build got a light card on a light band — no
     separation at all. --primary rather than --secondary so the card
     is a step ABOVE the band it sits on, which is what the hairline
     and the shadow are then drawing. */
  --tm-card-bg:    var(--color-bg-primary);
  --tm-card-edge:  var(--color-border-subtle);
  --tm-card-text:  var(--color-text-primary);
  --tm-card-muted: var(--color-text-secondary);

  /* THE ACCENT IS PART OF THE CARD'S SET, not a section-level colour,
     and that is the whole reason this token exists. The stars and the
     Read more link are accent-coloured, and they sit INSIDE a card
     that inverts — so on the pale card they need the dark-on-light
     step and on the brand-dark centre card they need the light-on-
     dark one. Reaching for --color-text-accent in both places put
     Read more at 1.80:1 on the centre card. */
  --tm-accent: var(--color-text-accent);

  /* The avatar disc. Brand on the pale card; the centre card
     overrides it to accent, so the disc stays the warmest thing in
     whichever card you are reading. */
  --tm-avatar-bg:   var(--brand-700);
  --tm-avatar-text: var(--color-text-on-solid);

  /* THE GROUND IS A SKY (2026-10-07, folded back from a client build).
     A pale brand tint at the top easing to the page's own ground at the
     foot, three soft white blooms drifting over it like cloud, and one
     warm bloom in the accent low behind the deck — late light the
     tinted side cards and the hairline pick up. The testimonials band
     paints it on itself; What We Offer and Selected Stays wear it as a
     .sky layer (see "the sky as a layer" beside .section--testimonials).
     All of it is token-derived, so it follows /brand.

     It replaced a wash whose comment closed one paragraph early: the
     parser swallowed the --tm-wash declaration with it, which made the
     band's whole `background` invalid, so the band had been painting no
     ground at all. If a band ever goes blank again, look for that. */
  --tm-sky-top:   color-mix(in oklab, var(--brand-100) 62%, var(--color-bg-primary));
  --tm-sky-mid:   var(--brand-25);
  --tm-sky-foot:  var(--color-bg-primary);
  --tm-cloud:     rgba(255, 255, 255, 0.78);
  --tm-sun:       color-mix(in oklab, var(--accent-100) 52%, transparent);   /* the 200 step read as a wash of the accent */

  /* THE PATTERN, optional and off by default. The sky can carry a faint
     repeating line pattern taken from the client's mark — one build
     drew a hexagon lattice from its logo — masked away behind the deck
     and faded out toward the foot. It is client artwork, so the
     template ships none. To add one, set --tm-pattern to an SVG data
     URI with a BLACK stroke (the dark scope inverts it to white; var()
     cannot reach inside a data URI, so the colour has to be fixed) and
     --tm-pattern-size to its tile, e.g.
       --tm-pattern: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='84' height='144'%3E…stroke='%23000'…%3C/svg%3E");
       --tm-pattern-size: 84px 144px;
     --tm-lattice-alpha is its strength: 0.05 to 0.09 reads as texture
     on a second look, which is the point. */
  --tm-pattern:      none;
  --tm-pattern-size: auto;
  --tm-lattice-alpha: 0.085;

  /* The inactive dot — dark on a light band, and it follows the page
     rather than being a fixed white alpha. */
  --tm-dot: var(--color-border-strong);

  /* Long and soft: the centre card is lifted toward the reader, so
     the shadow has to read as distance rather than as an outline. */
  --tm-lift: 0 2.5rem 5rem -2.25rem color-mix(in oklab, var(--brand-950) 42%, transparent),
             0 0.5rem 1.5rem -1rem color-mix(in oklab, var(--brand-950) 26%, transparent);
  --tm-arrow-lift: 0 0.625rem 1.75rem -0.875rem color-mix(in oklab, var(--brand-950) 40%, transparent);

  /* ---- section 3, what we offer -------------------------------- */
  --offer-radius:    1.5rem;              /* 24px, as the stay card */

  /* The pagination dot. Same 8px the testimonials deck uses, and it
     reads from the same --tm-dot ink, so the two rails on the page
     are one control rather than two. */
  --offer-dot-size:  0.5rem;              /* 8px */

  /* The card's float. Softer than the stay card's because this one
     sits on a pale band rather than a dark one. */
  --offer-lift: 0 1.875rem 4rem -2rem rgba(0, 0, 0, 0.28);

  /* The card's own foot gradient, under the index, title and line
     that sit on the picture. Composed from the theme's scrim triplet
     like the stay card's, so it is a pale wash on a light page and a
     dark one on a dark page — only the alphas are this section's. */
  --offer-scrim-0: rgba(var(--color-overlay-scrim-rgb), 0);
  --offer-scrim-1: rgba(var(--color-overlay-scrim-rgb), 0.18);  /* the run-out above the
                                             caption (2026-10-23), see .offer__scrim */
  --offer-scrim-2: rgba(var(--color-overlay-scrim-rgb), 0.50);  /* was 0.34; the
                                             12px index sits at this stop on a phone
                                             and measured 3.87:1 in the dark wash.
                                             0.44 got it to 4.46 — still short of
                                             the 4.5 bar — so 0.50, which lands 5.3 */
  --offer-scrim-3: rgba(var(--color-overlay-scrim-rgb), 0.72);
  --offer-scrim-4: rgba(var(--color-overlay-scrim-rgb), 0.90);

  /* The hairline inside the card's corner. */
  --offer-edge-1: rgba(22, 36, 46, 0.18);
  --offer-edge-2: rgba(22, 36, 46, 0.05);

  /* The dotted connector, unfilled and filled. */
  --offer-conn:    rgba(60, 76, 78, 0.26);
  --offer-conn-on: var(--brand-700);

  --field-h:      3.5rem;                 /* 56px  — one control row */
  --field-h-lg:     4rem;                 /* 64px  */
  --claim-radius:   2rem;                 /* 32px  — the closing panel's own
                                             corner. --radius-lg is 16px and
                                             correct on a 373px card; on a
                                             1200px plate the same 16px reads
                                             as a square with the edges filed
                                             off. The radius is a proportion
                                             of the object, so a much larger
                                             object gets its own. */

  /* Where a landscape photo should sit inside the hero crop.
     Slightly above centre keeps horizons out of the copy. */
  --hero-focal: 50% 42%;

  /* MOTION
     The built in CSS easings are too weak to read as intentional.
     These are the two curves the page uses; nothing else. */
  --ease-out:      cubic-bezier(0.23, 1, 0.32, 1);
  --ease-in-out:   cubic-bezier(0.77, 0, 0.175, 1);
  --dur-press:     160ms;
  --dur-ui:        200ms;
  --dur-reveal:    560ms;
  --dur-breathe:  3600ms;   /* the amount's glow. Slow enough to read as
                               breathing rather than blinking. */
  --dur-crossfade: 1200ms;   /* editorial, not UI — allowed to be slow */
  /* THE TWO SCROLL-SCRUB TWEENS. Both bridge the gap between the
     positions script.js writes and continuous motion, so neither is
     a UI duration and neither should be tuned by eye against one.
     --dur-clip is paired with the 24 steps of the hero reveal and
     --dur-fill with the 100 steps of the line; the finer the steps,
     the shorter the tween needs to be. */
  /* The deck's turn. Long because the card is travelling in three
     dimensions and a 3D rotation at UI speed reads as a glitch — the
     eye needs time to accept it as one object turning. */
  --dur-deck:      800ms;
  --dur-push:     1400ms;   /* the camera push on a card photograph. Editorial,
                               not UI — at UI speed a zoom this small reads as
                               a twitch rather than as movement. */
  /* WHERE YOU'LL STAY's stage (Dunya, 2026-11-01). Both are answers to a
     hover or a click on the list, something a visitor does over and over
     in one visit, so both are UI timings on --ease-out: they move from
     the first frame. The wipe was 700ms on --ease-in-out and read as
     slow when hovering down the list: that curve barely starts for its
     first third, so 300ms after the pointer landed only 4% of the new
     photograph showed. At 400ms on ease-out it is half across about
     140ms after the pointer lands (with script.js's 80ms wait) and all
     but done by 300ms. The glide is the bar arriving at the row, a touch
     quicker than the picture it announces. */
  --dur-glide:     280ms;
  --dur-wipe:      400ms;
  --dur-clip:      450ms;
  --dur-fill:      300ms;

  /* HERO SCRIM STOPS
     The overlay tokens in _template.css cover flat scrims. A hero
     needs a multi stop ramp, which no single token can express, so
     the stops live here as one component owned set. Near black with
     a blue cast rather than #000 — pure black reads cheap over a
     photograph. */
  --hero-scrim-1: rgba(9, 11, 14, 0.40);
  --hero-scrim-2: rgba(9, 11, 14, 0.18);
  --hero-scrim-0: rgba(9, 11, 14, 0);

  /* THE FLAT WASH. The two ramps above are weighted to the top and
     bottom edges and have both faded out by the middle of the frame,
     which is where a centred column puts its copy. This covers that
     middle at one strength everywhere.

     0.30, down from 0.50. At 0.50 it carried the whole contrast story
     alone and the picture paid for it — over a flat placeholder
     poster the frame read as one dark slab rather than as a
     photograph. The copy scrim below took that load, so this is now a
     grade on the picture rather than a floor under the type.

     The two are MEASURED TOGETHER. Moving either one moves every
     figure in the table over --hero-scrim-copy-1. */
  --hero-scrim-wash: rgba(9, 11, 14, 0.30);

  /* THE BRAND TINT (2026-10-23, from the Cabin Collective build by way
     of Gooseberry). There the hero runs under a left-to-right gradient
     of the client's deep teal from 85% to 69% alpha. Here the ink is
     derived rather than typed: --brand-950 taken down to that teal's
     lightness (oklch L 0.21) by mixing in black, so the tint is the
     same weight on any brand and takes its hue from /brand.
     color-mix rather than oklch(from …) so the no-relative-colour
     fallback ramp in brand-contrast.js still feeds it.

     It is the ONLY thing .hero-offer__scrim paints, on both pages. The
     top ramp, foot ramp and flat wash above (--hero-scrim-1, -2,
     -wash, -foot) are no longer drawn: stacked under this they took
     the footage to near black, and at 0.69 or more this is heavier
     than all three composited anywhere they sat. Worst case, pure
     white footage under the tint's lightest edge, the hero's 96% white
     text holds about 6:1 against a 4.5:1 bar (worked on the Gooseberry
     build for this template's moss brand, #5E7444). The old tokens
     stay so the stack can be put back, and the table over
     --hero-scrim-copy-1 was measured on that stack, not on this one.

     A LIGHT HERO is .hero-offer--light — see "the light hero" after
     the hero's copy rules. It swaps this ink for a pale one. */
  --hero-tint-ink: color-mix(in oklab, var(--brand-950) 79%, #000);
  --hero-tint: linear-gradient(90deg,
    color-mix(in oklab, var(--hero-tint-ink) 85%, transparent) 0%,
    color-mix(in oklab, var(--hero-tint-ink) 69%, transparent) 100%);

  /* The halo behind every string in the hero. The 2px layer is a hard
     edge against whatever footage is directly behind a glyph, the
     12px layer the pad that catches a bright patch drifting under a
     counter. A token since 2026-10-23 so the light hero can turn it
     to a pale halo under dark type: same geometry, opposite colour. */
  --hero-text-halo: 0 1px 2px rgba(9, 11, 14, 0.55), 0 2px 12px rgba(9, 11, 14, 0.75);

  /* The frosted hero form's own tint, behind its blur. It is a
     separate token rather than a reuse of the tint because it sits
     ON TOP of the frame scrim (the wash then, --hero-tint now) and
     composites with it — the two numbers are solving different
     problems and moving one to fix the other is how this gets away
     from you.

     0.60, up from 0.28 (Cabin Collective, 2026-10-15; kept on
     Gooseberry): over real footage the field read as see-through
     rather than as a control. */
  --hero-form-tint: rgba(9, 11, 14, 0.60);

  /* THE SAME RAMP, SIZED FOR BRIGHT FOOTAGE, and used by the desktop
     diagonal alone — see the note over it in the 1024px block.

     Why it is a separate pair rather than a heavier --hero-scrim-1:
     that token is also the welcome page's hero and the mobile ramp,
     and neither of those has this problem. Mobile paints TWO scrims
     that composite well past this weight, and the welcome hero is not
     over client footage at all. Raising the shared token to fix one
     layout would darken three.

     The numbers are measured, not chosen. The hero clip is a sunset:
     its sky is around #E6D2B4 where the headline sits, and at the old
     0.40 the title measured 1.96:1 against a 3:1 floor — a real
     failure, not a thin pass. Solving white text to 4.5:1 over a
     ~230 channel source needs about 0.50 of near black, so the
     plateau is 0.56: enough to clear the body text bar rather than
     the large text one, which is the margin that lets the client
     swap the clip for another bright one without this breaking. */
  --hero-scrim-lg-1: rgba(9, 11, 14, 0.56);
  --hero-scrim-lg-2: rgba(9, 11, 14, 0.30);

  /* THE COPY SCRIM, and it is back after being deleted once. It went
     when the hero became a centred column, on the argument that a
     band behind centred copy is only a second frame scrim. That was
     right about a BAND and wrong about the need: with the wash down
     to 0.30 the type had nothing under it.

     The answer is a scrim shaped like the COPY rather than like the
     frame — an ellipse, soft on all four sides, densest where the
     headline and lede sit and gone by the edges of the picture. That
     is what lets the corners of the frame stay bright while the
     middle still carries white text.

     MEASURED AT THE GLYPH over the placeholder poster, text-shadow
     off, with the wash and this ellipse composited:

                          1440    390     bar
       headline           5.08    3.73    3.0   (large text)
       lede               7.05    4.93    4.5
       input value       10.01    8.33    4.5
       input placeholder  7.25    6.17    4.5
       featured label     4.99    5.66    4.5

     The tightest is the lede on a phone, at 4.93. Two things failed
     on the way here and are worth not re-breaking: the press row came
     in at 4.13 when the wash first dropped, which --hero-scrim-foot
     fixed; and the ellipse's first geometry printed a visible
     rectangle across the picture, which closest-side fixed. RE-MEASURE
     if you change any of the three layers, or if the footage is
     brighter than the placeholder. */
  --hero-scrim-copy-1: rgba(9, 11, 14, 0.50);
  --hero-scrim-copy-2: rgba(9, 11, 14, 0.28);

  /* THE FOOT, heavier than the head. The press row sits on the bottom
     edge of the frame, below the copy ellipse's reach, so when the
     wash came down it was the one string left with nothing under it —
     it measured 4.13 against a 4.5 bar. This is the bottom ramp's own
     start value, separate from --hero-scrim-1 so raising it does not
     also darken the top of the picture, where nothing is written. */
  --hero-scrim-foot: rgba(9, 11, 14, 0.56);

  /* The closing card's own ground — its top veil and its offer plate
     — over a client photo nobody has vetted. (The Local Favourites
     description panel used it too, until that panel went on
     2026-09-23.) Composed from the
     theme's scrim triplet, so it is a pale pane with dark type on a
     light page and a dark pane with light type on a dark one.

     0.82 rather than _template.css's flat --color-overlay-scrim at
     0.50, and the number holds in both polarities. Dark wash: the
     worst case is a blown out white sky, where 0.50 blends to
     #8A8A8A and light --color-overlay-fg lands at 3.4:1 — a fail for
     caption sized text — while 0.82 blends to #363636 and puts it at
     8.3:1. Light wash: the worst case flips to a near-black photo,
     where 0.82 of white blends to about #D1D1D1 and the dark ink
     clears 10:1. The edge is the ink at low alpha rather than the
     wash, so it stays a hairline against the pane in either theme. */
  --card-panel:      rgba(var(--color-overlay-scrim-rgb), 0.82);
  --card-panel-edge: rgba(var(--color-overlay-ink-rgb), 0.14);

  /* THERE WAS A --card-panel-soft HERE, at 0.50, and it is worth
     one paragraph rather than a silent deletion.

     It existed for one consumer: the amenity deck's description,
     which used to be printed on the pinned photograph. Where
     --card-panel is defensive — 0.82 holds AA against a blown out
     white sky, so it is safe under a photo nobody has looked at —
     0.50 was measured against the four files actually in assets/img
     and bottomed out at 5.30:1 on the water shot, which meant it
     could not survive one of those photographs being replaced.

     That description is now in the left column, on the section's own
     ground, where it needs no panel at all and measures 7.4:1. So
     the token has no consumer and the tie to those four files is
     gone with it. --card-panel is untouched and still carries Local
     Favourites, which is over photos of places nobody here shot and
     wants the defensive number.

     If a panel over an amenity photograph is ever wanted again,
     start from --card-panel and re-measure downward against the
     photographs of the day — do not restore 0.50 from git on the
     strength of a measurement taken against a different set. */

  
  /* The closing panel's top lip. Raw white alpha rather than a
     palette step, for the same reason the scrims above are: it is
     a light source catching the edge of the plate, so it has to
     hold the same value whatever hue the client's brand is. A
     gray-800 border would go invisible against the panel's own
     gray-800 top and visible against its gray-900 bottom, which
     is a hairline that fades out halfway down the box. */
  --claim-lip: rgba(255, 255, 255, 0.08);

  /* THE AMOUNT'S GLOW, tinted from the client's brand.
     --color-brand-identity is the token meant for "the recognisable
     brand colour", which is the right source for a bloom that is
     supposed to feel like the brand rather than like a generic neon.
     Because the hex is client supplied, the alphas are deliberately
     low: a brand set to something bright has to stay subtle, and a
     bloom sitting behind white text eats into its contrast. */
  --glow-core: color-mix(in oklab, var(--color-brand-identity) 68%, transparent);
  --glow-mid:  color-mix(in oklab, var(--color-brand-identity) 22%, transparent);

  /* Lift for objects that float on a photograph. Black tinted is
     correct here — the ground is a photo, not a light surface. */
  --lift-lg: 0 1.5rem 3.5rem rgba(8, 10, 13, 0.42), 0 0.125rem 0.5rem rgba(8, 10, 13, 0.24);
  /* drop-shadow, not box-shadow: it follows the logo's alpha channel
     instead of drawing a rectangle around a transparent PNG or SVG.
     Delete it if the logo already has its own plate or backdrop. */
  --lift-logo: drop-shadow(0 0.25rem 1rem rgba(8, 10, 13, 0.55));
}

/* THE SAME RAMPS, RE-DECLARED FOR A DARK SCOPE.
   The tokens above compose rgba(var(--color-overlay-scrim-rgb), a),
   and a custom property resolves its var() where it is DECLARED — on
   :root — not where it is used. So an element pinned data-theme="dark"
   on a light page (the closing card, which paints --card-panel as its
   top veil and its offer plate) was reading the light theme's white
   wash and printing a near-white pane under near-white type.

   Declaring the same tokens again on the dark scope makes them resolve
   THERE, against the dark triplet _template.css sets on the same
   selector. It is the pattern that file uses for every semantic token
   and it costs one line per ramp stop. The alphas are repeated rather
   than referenced on purpose: a token cannot read its own :root value
   from inside a scope that redefines it, so there is nothing to
   reference. Keep the two lists identical — if you retune a stop
   above, retune it here. */
[data-theme="dark"] {
  --stay-scrim-0: rgba(var(--color-overlay-scrim-rgb), 0);
  --stay-scrim-1: rgba(var(--color-overlay-scrim-rgb), 0.15);
  --stay-scrim-2: rgba(var(--color-overlay-scrim-rgb), 0.55);
  --stay-scrim-3: rgba(var(--color-overlay-scrim-rgb), 0.88);
  --stay-scrim-4: rgba(var(--color-overlay-scrim-rgb), 0.92);
  --stay-btn-bg:  rgba(var(--color-overlay-scrim-rgb), 0.55);
  --stay-text-shadow: 0 1px 2px rgba(var(--color-overlay-scrim-rgb), 0.55);

  --offer-scrim-0: rgba(var(--color-overlay-scrim-rgb), 0);
  --offer-scrim-1: rgba(var(--color-overlay-scrim-rgb), 0.18);
  --offer-scrim-2: rgba(var(--color-overlay-scrim-rgb), 0.50);
  --offer-scrim-3: rgba(var(--color-overlay-scrim-rgb), 0.72);
  --offer-scrim-4: rgba(var(--color-overlay-scrim-rgb), 0.90);

  --card-panel:      rgba(var(--color-overlay-scrim-rgb), 0.82);
  --card-panel-edge: rgba(var(--color-overlay-ink-rgb), 0.14);
}

/* THE FILLED BUTTONS. Every filled control on the page — .btn--primary,
   the stay card's hover, the deck's arrows, the welcome page's Copy
   stub — reads its fill, its hover fill and its ink from these three,
   so a build that wants a different button changes three lines here
   and nothing else.

   THE DEFAULTS ARE THE CONTRAST-SOLVED SEMANTIC PAIR: the brand solid
   with the ink _template.css already solves against it, in every
   theme. That pairing is what brand-contrast.js guarantees, so it is
   safe for any two hexes /brand writes. Declared on every theme scope,
   not only on :root, for the reason the ramps above are re-declared: a
   var() resolves where it is declared, and the solid swaps steps under
   data-theme="dark" (the hero, the closing card, the stays band).

   TO USE THE ACCENT AS THE FILL — a build whose brand kit asks for an
   accent-coloured button — point --btn-fill at --accent-base and
   --btn-ink at whatever the kit pairs with it, then MEASURE. Those are
   raw tokens brand-contrast.js never touches, so nothing guarantees
   the pair: one client's accent fill with brand ink measured 10:1, and
   the same two tokens on this template's own brand measure 1.45:1. A
   hover of "one step darker" only holds for a light accent, too —
   re-measure the hover. Raw tokens resolve the same in every scope, so
   that build may move the three back into :root. */
:root, [data-theme] {
  --btn-fill:       var(--color-bg-brand-solid);
  --btn-fill-hover: var(--color-bg-brand-hover);
  --btn-ink:        var(--color-text-on-solid);

  /* Walden Retreats, 2026-09-23: the filled button is the accent's 400 step
     on both themes, per the client. accent-400 sits at L 0.75, so the label
     is the dark text token rather than white, 6.7:1 against it; the hover
     stays in the accent ramp (accent-300, 8.81:1 against the same ink)
     because the brand hover token is indigo-800, dark on dark here. */
  --btn-fill:       var(--accent-400);
  --btn-fill-hover: var(--accent-300);
  --btn-ink:        var(--gray-950);
}

@media (max-width: 767px) {
  :root { --section-y: var(--space-7); }  /* 48px */
}

body {
  background: var(--color-bg-primary);
  color: var(--color-text-primary);
}

a { color: inherit; text-decoration: none; }

:focus-visible {
  outline: 2px solid var(--color-border-focus);
  outline-offset: 2px;
}

.center { text-align: center; }

/* ============================================================
   SECTION MODIFIERS
   .container and .section themselves come from _template.css.
   ============================================================ */
.section--tight { padding-block: var(--space-4) var(--section-y); }
/* brand-900, a raw rung rather than a semantic surface, and it does
   NOT follow the page's theme. That is deliberate and it was briefly
   changed and changed back, so the reason is worth writing down.

   The one section still using this is Amenities, and Amenities is
   not a tinted band — it is a section whose ground is PHOTOGRAPHY.
   Four blurred backdrop images fill it, cross-fading as the reader
   moves through the steps, and every string in it is reversed out
   over them. This colour is only what shows at the edges where the
   backdrop fades out, so it has to agree with the photographs, not
   with the page.

   Swapping it for --color-bg-brand-subtle made the edges light while
   the backdrop stayed dark, and the heading went with the page to
   dark ink: 1.10:1 on the section's own ground. Making this section
   genuinely light means removing its backdrop photography, which is
   a different change from recolouring a band.

   The section carries data-theme="dark" in the markup for the same
   reason — see the note there. */
.section--alt   { background: var(--brand-900); }
/* The band's ground while the map loads: brand-50 on the light band
   the template ships, and the dark scope's brand-950 if the section is
   given data-theme="dark". See THE DARK BAND in section 7. */
.section--map   { background: var(--color-bg-brand-subtle); }

/* THE STAYS SECTION HAS NO LIGHT VARIANT ANY MORE, and the rule that
   used to give it one is deleted rather than adjusted.

   It painted the section --brand-25 on any page that was not dark,
   because the cards were white plates and the ground had to be a
   tint they could sit on. The cards are photographs now and the
   section supplies its own dark ground in every theme — everything
   in it is reversed out, including the heading.

   Left in place it was a live bug, not a stale nicety: it selected
   :root:not([data-theme="dark"]) .section--stays, which out-specifies
   the plain .section--stays rule that sets the new ground, so a
   client build flipping the page to light got a near-white band with
   white type on it. If a tinted ground is ever wanted again, it has
   to be argued from what the cards are now, not restored. */

/* ============================================================
   SECTION HEADINGS
   Size and line height come from the .type-* class on the
   element. Only colour and rhythm live here.
   ============================================================ */
.eyebrow { color: var(--color-text-tertiary); margin-bottom: var(--space-2); }
.heading { color: var(--color-text-primary); margin-bottom: var(--space-3); }

.subhead {
  color: var(--color-text-secondary);
  max-width: 46ch;
  margin-bottom: var(--space-5);
}
.center .subhead { margin-inline: auto; }

/* ============================================================
   BUTTONS
   Pressed is a treatment, not a colour — steps 700/800/900 are
   visually bunched, so there is no third step to reach for.
   ============================================================ */
.btn {
  display: inline-block;
  padding: var(--space-3) var(--space-5);
  border: 0;
  /* A PILL, AND EVERY BUTTON CARRYING A FILL IS ONE. That is the
     standing rule, not one button's number: a 999px radius on a
     52px tall button is already rounded past meeting, so
     --radius-pill says the same thing without a magic number.

     It sits on .btn and not on .btn--primary because a family that
     changes shape with its fill reads as two components. Neither
     page uses the outline or ghost variants today; when one does,
     it should be the same shape as the filled button beside it. */
  border-radius: var(--radius-pill);
  text-align: center;
  /* A PILL'S LABEL IS ONE LINE. Every label on both pages is two or
     three short words, and a pill that wraps to two rows stops reading
     as a button. The label is rem-sized, so a phone's larger text
     setting can push CHECK AVAILABILITY past a 320px screen's content
     width — this is what stops it stacking there. */
  white-space: nowrap;
  cursor: pointer;
  touch-action: manipulation;             /* kills the 300ms tap delay */
  transition: background-color var(--dur-ui) ease,
              filter var(--dur-ui) ease,
              transform var(--dur-press) var(--ease-out);
}

/* Scale, not translate. A button that moves down looks like it
   slipped; a button that shrinks looks pressed. */
.btn:active { filter: brightness(0.92); transform: scale(0.98); }

/* The fill, the ink and the hover are the three --btn-* tokens — see
   "the filled buttons" near the top of this file for the defaults and
   what to measure before changing them. The hover is in the gated
   block below. */
.btn--primary { background: var(--btn-fill); color: var(--btn-ink); }

.btn--outline,
.btn--ghost {
  background: transparent;
  color: var(--color-text-primary);
  border: 1px solid var(--color-border-default);
}

/* A filled button that is not the brand colour. It reads as the
   obvious next step inside a card without competing with the one
   primary action on the page. Tertiary rather than secondary
   because gray-50 on a white card is not visible as a shape. */
.btn--soft {
  background: var(--color-bg-tertiary);
  color: var(--color-text-primary);
}

/* Touch devices fire :hover on tap and then keep it. Gate it. */
@media (hover: hover) and (pointer: fine) {
  .btn--primary:hover { background: var(--btn-fill-hover); }   /* see --btn-* */
  .btn--outline:hover,
  .btn--ghost:hover   { background: var(--color-bg-brand-subtle); }
  .btn--soft:hover    { background: var(--color-bg-brand-muted); }
}

.btn--sm    { padding: var(--space-2) var(--space-4); }
.btn--block { display: block; width: 100%; }

/* ============================================================
   ICONS
   ------------------------------------------------------------
   One box, many glyphs. The base class owns the size and takes
   its fill from currentColor, so an icon is always the colour of
   the text it sits beside and never carries a colour of its own.
   A modifier only swaps --icon.

   Masks rather than <img> or inline <svg>: a mask discards the
   file's own colour, which is what lets one file serve a light
   brand and a dark one. The glyphs are Lucide, 24x24, 2px stroke.

   The sizes are dimensions, not spacing — an icon box is an
   object, so it is exempt from the 8pt rule the same way the
   field heights and the logo caps are.
   ============================================================ */
:root {
  --icon-phone: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='black' stroke-width='2' stroke-linecap='round' stroke-linejoin='round'%3E%3Cpath d='M22 16.92v3a2 2 0 0 1-2.18 2 19.79 19.79 0 0 1-8.63-3.07 19.5 19.5 0 0 1-6-6 19.79 19.79 0 0 1-3.07-8.67A2 2 0 0 1 4.11 2h3a2 2 0 0 1 2 1.72 12.84 12.84 0 0 0 .7 2.81 2 2 0 0 1-.45 2.11L8.09 9.91a16 16 0 0 0 6 6l1.27-1.27a2 2 0 0 1 2.11-.45 12.84 12.84 0 0 0 2.81.7A2 2 0 0 1 22 16.92z'/%3E%3C/svg%3E");
  --icon-mail:  url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='black' stroke-width='2' stroke-linecap='round' stroke-linejoin='round'%3E%3Crect width='20' height='16' x='2' y='4' rx='2'/%3E%3Cpath d='m22 7-8.97 5.7a1.94 1.94 0 0 1-2.06 0L2 7'/%3E%3C/svg%3E");
  --icon-car:   url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='black' stroke-width='2' stroke-linecap='round' stroke-linejoin='round'%3E%3Cpath d='M19 17h2c.6 0 1-.4 1-1v-3c0-.9-.7-1.7-1.5-1.9C18.7 10.6 16 10 16 10s-1.3-1.4-2.2-2.3c-.5-.4-1.1-.7-1.8-.7H5c-.6 0-1.1.4-1.4.9l-1.4 2.9A3.7 3.7 0 0 0 2 12v4c0 .6.4 1 1 1h2'/%3E%3Ccircle cx='7' cy='17' r='2'/%3E%3Cpath d='M9 17h6'/%3E%3Ccircle cx='17' cy='17' r='2'/%3E%3C/svg%3E");
  --icon-train: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='black' stroke-width='2' stroke-linecap='round' stroke-linejoin='round'%3E%3Crect width='16' height='16' x='4' y='3' rx='2'/%3E%3Cpath d='M4 11h16'/%3E%3Cpath d='M12 3v8'/%3E%3Cpath d='m8 19-2 3'/%3E%3Cpath d='m18 22-2-3'/%3E%3Cpath d='M8 15h.01'/%3E%3Cpath d='M16 15h.01'/%3E%3C/svg%3E");
  --icon-route: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='black' stroke-width='2' stroke-linecap='round' stroke-linejoin='round'%3E%3Cpath d='M3 11l19-9l-9 19l-2-8l-8-2z'/%3E%3C/svg%3E");
  --icon-pin:   url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='black' stroke-width='2' stroke-linecap='round' stroke-linejoin='round'%3E%3Cpath d='M21 10c0 7-9 13-9 13s-9-6-9-13a9 9 0 0 1 18 0z'/%3E%3Ccircle cx='12' cy='10' r='3'/%3E%3C/svg%3E");
  --icon-clock: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='black' stroke-width='2' stroke-linecap='round' stroke-linejoin='round'%3E%3Ccircle cx='12' cy='12' r='10'/%3E%3Cpath d='M12 6v6l4 2'/%3E%3C/svg%3E");
  --icon-peak:  url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='black' stroke-width='2' stroke-linecap='round' stroke-linejoin='round'%3E%3Cpath d='m8 3 4 8 5-5 5 15H2L8 3z'/%3E%3C/svg%3E");
  --icon-home:  url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='black' stroke-width='2' stroke-linecap='round' stroke-linejoin='round'%3E%3Cpath d='M3 9l9-7l9 7v11a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2z'/%3E%3Cpath d='M9 22V12h6v10'/%3E%3C/svg%3E");
  --icon-star:  url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='black' stroke='black' stroke-width='2' stroke-linecap='round' stroke-linejoin='round'%3E%3Cpath d='M11.525 2.295a.53.53 0 0 1 .95 0l2.31 4.679a2.123 2.123 0 0 0 1.595 1.16l5.166.756a.53.53 0 0 1 .294.904l-3.736 3.638a2.123 2.123 0 0 0-.611 1.878l.882 5.14a.53.53 0 0 1-.771.56l-4.618-2.428a2.122 2.122 0 0 0-1.973 0L6.396 21.01a.53.53 0 0 1-.77-.56l.881-5.139a2.122 2.122 0 0 0-.611-1.879L2.16 9.795a.53.53 0 0 1 .294-.906l5.165-.755a2.122 2.122 0 0 0 1.597-1.16z'/%3E%3C/svg%3E");
}

.icon {
  flex: 0 0 auto;
  display: inline-block;
  width:  1.25rem;                        /* 20px */
  height: 1.25rem;
  background: currentColor;
  -webkit-mask: var(--icon) center / contain no-repeat;
          mask: var(--icon) center / contain no-repeat;
}
.icon--sm { width: 1rem;   height: 1rem;   }   /* 16px — inside a chip or a button */
.icon--lg { width: 1.5rem; height: 1.5rem; }   /* 24px — the lead mark on a tile  */

.icon--phone { --icon: var(--icon-phone); }
.icon--mail  { --icon: var(--icon-mail);  }
.icon--car   { --icon: var(--icon-car);   }
.icon--train { --icon: var(--icon-train); }
.icon--route { --icon: var(--icon-route); }
.icon--pin   { --icon: var(--icon-pin);   }
.icon--clock { --icon: var(--icon-clock); }
.icon--peak  { --icon: var(--icon-peak);  }
.icon--home  { --icon: var(--icon-home);  }
.icon--star  { --icon: var(--icon-star);  }

/* ============================================================
   1 + 2 · HERO OFFER
   ------------------------------------------------------------
   The old hero and the old offer card are one section now. The
   photograph is the ground, the offer is the content, and on
   desktop the copy and the form sit on top of the photo.

   Three layers, back to front:
     __media   the background video
     __scrim   the gradient that buys the white copy its contrast
     __seam    the bottom fade that dissolves the photo into the
               page ground, so section 3 starts with no hard edge
   ============================================================ */
/* THE FLAT BANNER, which is still what welcome.html is. The reveal
   below is an opt-in on top of it, switched on by data-clip-reveal in
   the markup, so a hero without the attribute behaves exactly as it
   did before any of this existed. */
.hero-offer {
  position: relative;
  isolation: isolate;                     /* keeps the layers out of the page stack */
  display: flex;
  /* CENTRED, not flex-end. The copy used to sit low with the photo
     breathing above it; now that the hero is a full 100svh, low means
     the block is pinned to the fold with a screen of empty photograph
     over it. Centred, the copy sits on the optical middle and the
     photograph gets an even margin top and bottom.

     This moves the strings up out of the heaviest part of both
     scrims, so it is a contrast change as well as a layout one. The
     client build re-measured at the glyph and passed at every width,
     with 390px the tight one for the offer line — re-measure here
     once a real photograph replaces the placeholder poster. */
  align-items: center;
  min-height: 100vh;                      /* fallback for anything without svh */
  min-height: var(--hero-min);
  overflow: hidden;
  background: var(--color-bg-primary);    /* the ground the reveal pulls back to */
}

/* ---- the pinned reveal ----------------------------------------- */
/* With the attribute, the hero stops being a banner and becomes a
   TRACK: one screen of hero plus --hero-runway of scroll spent
   underneath it, with the stage held still at the top of the viewport
   for the whole of it. That travel is what the clip-path is animated
   over — the footage pulls in from the four edges and rounds its
   corners as the runway is consumed, so the banner lifts off the page
   and becomes a card without the reader losing sight of it.

   The track has to be block flow and it must not clip. A flex track
   would size the sticky stage to its content and centre it, which
   leaves it nothing to travel through; an ancestor with overflow
   other than visible becomes the stage's scroll container, and it
   silently stops sticking. Both are the kind of failure that looks
   like the JavaScript is broken. The clipping lives on the stage. */
.hero-offer[data-clip-reveal] {
  display: block;
  overflow: visible;
}

/* The stage is the flex context the copy centres in — the job
   .hero-offer does itself on a hero without the attribute. Declared
   outside the gate so the centring and the clipping both survive on
   a short viewport, where the stage is simply a static box one
   screen tall. */
.hero-offer__stage {
  position: relative;
  display: flex;
  align-items: center;
  min-height: inherit;
  overflow: hidden;
}

/* TWO GATES, AND THE RUNWAY NEEDS BOTH.

   .reveal-on is the same class the scroll reveals hang off, and it
   is here for the same reason — read the long note over that block
   before changing this one. It goes on <html> from the inline script
   in <head>, and only where there is an IntersectionObserver for
   script.js to drive this with and the visitor has not asked for
   less motion. Without it the runway would still be in the page with
   nothing animating over it: a hero that holds still for an extra
   screen and then lets go, on exactly the browsers least able to
   explain why. The extra height is the hidden state here, so it does
   not get written into a plain selector either.

   THE HEIGHT GATE. Below 640px of viewport the pin is off and the
   hero is the flat banner above — the same gate the amenities deck
   uses, for the same reason. A sticky stage is exactly one screen
   tall by definition, and on a short landscape phone the logo,
   headline, offer line and form together are taller than that;
   pinning there would clip the form rather than let the section
   grow. script.js makes the same call independently, by asking the
   stage what position it actually ended up with rather than by
   re-testing this number, so the two cannot drift apart. */
@media (min-height: 640px) {
  .reveal-on .hero-offer[data-clip-reveal] {
    height: calc(100vh + 100vh);
    height: calc(var(--hero-min) + var(--hero-runway));
  }

  .reveal-on .hero-offer[data-clip-reveal] .hero-offer__stage {
    position: sticky;
    top: 0;
    height: 100vh;
    height: var(--hero-min);
  }

  .reveal-on .hero-offer[data-clip-reveal] .hero-offer__clip {
    position: absolute;
    inset: 0;
    /* STARTS AT THE SCRIPT'S NUMBER (2026-10-23, from the Gooseberry
       build). Pinned is exactly when script.js runs the reveal, and it
       then writes this as 22px below 640px wide and 40px above
       (INSET_MAX and INSET_NARROW there; keep the two in step). The
       copy's padding adds it, so when the first frame was painted
       before script.js had run, the column laid out 44px wider, then
       narrowed and rewrapped under the reader: Lighthouse measured that
       as up to 0.16 of layout shift on a phone. Set here, the script's
       write changes nothing. */
    --clip-inset-max: 22px;
  }
}
@media (min-height: 640px) and (min-width: 640px) {
  .reveal-on .hero-offer[data-clip-reveal] .hero-offer__clip { --clip-inset-max: 40px; }
}

/* THE PANE THE SCROLL ANIMATES.
   script.js writes --clip-inset and --clip-round here, forty times
   across the runway, and clip-path turns them into a rounded
   rectangle pulling in from the edges. The radius is twice the inset
   throughout, which is what keeps the corner reading as a corner
   rather than as a nick out of the frame: at 40px in, an 80px radius
   is the arc a card that size would actually have.

   All three custom properties start at zero, so a hero with no
   attribute, no JavaScript, or a reader who asked for reduced motion
   gets the full bleed rectangle it has always been — and the padding
   on __inner, which adds --clip-inset-max, stays exactly where it
   was. The script sets the real maximum only once it has decided it
   is running.

   The transition is what smooths the steps between the twenty-four
   positions the script writes, and 450ms is paired with that count:
   long enough that a step is never seen as a step, short enough that
   a fast scroll is caught up with rather than trailed. Changing
   either one without the other is what makes this stutter.

   will-change and the translateZ are not superstition: clip-path on
   a full screen element is a compositor job or it is a repaint of
   the whole viewport, and contain keeps the rest of the page out of
   that work. */
.hero-offer__clip {
  --clip-inset: 0px;
  --clip-round: 0px;
  --clip-inset-max: 0px;

  /* IN FLOW until the hero is pinned. Taking it out of flow is what
     lets it fill a stage of a fixed height, but it also means the
     copy inside it stops contributing any height at all — and on a
     short viewport, where the gate has turned the pin off, that is
     the difference between a hero that grows to fit its form and one
     that quietly crops the bottom of it. So the absolute positioning
     is part of the pin and lives in the gate with it. */
  position: relative;
  width: 100%;
  min-height: inherit;
  display: flex;
  align-items: center;
  clip-path: inset(var(--clip-inset) round var(--clip-round));
  will-change: clip-path;
  transform: translateZ(0);
  contain: layout paint;
  transition: clip-path var(--dur-clip) var(--ease-out);
  background: var(--color-bg-primary);
}

/* Held still for a visitor who asked for reduced motion. The script
   stands down as well, so this is belt and braces rather than the
   only thing stopping it — but _template.css has already zeroed the
   transition above by this point, and a clip-path that jumps between
   forty positions with no tween is worse than one that never moves. */
@media (prefers-reduced-motion: reduce) {
  .hero-offer__clip {
    clip-path: none;
    will-change: auto;
    position: relative;
    inset: auto;
  }

  /* AND THE TRACK GOES WITH IT. Leaving the runway in place would
     hand a reader who asked for less motion a hero that does nothing
     for a screen and a half — the effect is off, so the scroll it was
     going to be spent on has nothing left to buy. Back to the flat
     banner, at its own height. */
  .reveal-on .hero-offer[data-clip-reveal] {
    height: auto;
  }
  .reveal-on .hero-offer[data-clip-reveal] .hero-offer__stage {
    position: static;
    height: auto;
  }
}

.hero-offer__media  { position: absolute; inset: 0; z-index: 0; }
.hero-offer__slides { position: absolute; inset: 0; }

/* The footage is 788x516 and the hero is far wider than that on a
   desktop, so cover is doing real scaling here. That is the trade for
   full bleed: it crops rather than letterboxes, and the scrims and the
   copy sit over the part that stays sharp enough. object-position is
   the same --hero-focal the photographs used, so re-aiming the crop is
   still a one line change up in the tokens.

   Explicit width and height, not just object-fit: a <video> keeps its
   intrinsic aspect ratio otherwise and would sit in the middle of the
   frame at its native size. */
.hero-offer__poster,
.hero-offer__video {
  position: absolute; inset: 0;
  width: 100%; height: 100%;
  object-fit: cover;
  object-position: var(--hero-focal);
}
/* THE POSTER IS AN <img> UNDER THE VIDEO (2026-10-23), so it can carry
   a srcset; see index.html. The ground moved from the video to the
   picture: under the image, a file that has not arrived yet is the page
   ground rather than a transparent hole with the scrims over it. The
   video has to stay see-through until it has a frame, or it would hide
   the picture. */
.hero-offer__poster { display: block; background: var(--color-bg-primary); }

/* Kept for a hero that goes back to stills — see the notes in
   index.html and the slideshow block in script.js, which both still
   work if the markup is swapped back. */
.hero-offer__slide {
  position: absolute; inset: 0;
  opacity: 0;
  transition: opacity var(--dur-crossfade) var(--ease-in-out);
}
.hero-offer__slide.is-active { opacity: 1; }

.hero-offer__slide img {
  width: 100%; height: 100%;
  object-fit: cover;
  object-position: var(--hero-focal);
}

/* Stills only — the video moves on its own, and a Ken Burns push on
   top of footage that is already moving reads as a wobble.

   The drift is the reason a still photograph does not read as a
   dead background, and it makes the crossfade legible as a change
   of scene rather than a flicker. It restarts on every slide
   because the script re-adds .is-active. Linear because the motion
   is continuous — any easing would visibly land mid slide.
   Scale runs 1.01 -> 1.09 so neither end can expose an edge.

   Suppressed under reduced motion — and so is the rotation itself,
   in script.js. The usual rule is that reduced motion means gentler
   rather than none, so an opacity crossfade would normally survive.
   It cannot here: _template.css zeroes every transition-duration
   with !important, which would turn each slide change into a hard
   flash-cut every six seconds. A static hero is the better answer,
   and moving content that runs longer than five seconds with no way
   to stop it is a WCAG 2.2.2 problem regardless of the preference. */
@media (prefers-reduced-motion: no-preference) {
  .hero-offer__slide.is-active img { animation: hero-drift 8s linear forwards; }
}
@keyframes hero-drift {
  from { transform: scale(1.01); }
  to   { transform: scale(1.09); }
}

/* ACCESSIBILITY, NOT DECORATION.
   The scrims below exist so white copy clears its contrast bar over
   footage nobody has vetted. They are about half the weight they used
   to be, and the text shadow further down is what paid for it: the
   shadow buys contrast at the glyph edge, where it is actually read,
   instead of across the whole frame, where it only costs you the
   picture. Measured at the glyph — the worst 2% of the pixels the
   letters actually sit on, over seven frames spread across the clip —
   the title holds 6.4:1 and the offer line 4.9:1 at 1440, and 7.1:1
   and 8.3:1 at 390. Both are large text, so the bar is 3:1; both
   clear the 4.5:1 body bar as well. Taking the scrim down without the
   shadow puts the desktop pair at 3.25:1 and 3.08:1, which is inside
   the standard and too close to the edge of it to ship.

   There are two scrims because one is not enough. This first is
   sized to the FRAME, which is the wrong shape on a narrow viewport:
   the copy block is most of the hero's height there, so its top sits
   where a bottom weighted ramp has already faded out. Measured at
   390px before the second scrim existed, the brand strip came in at
   1.65:1. The frame scrim handles the overall grade; the copy scrim
   below handles legibility. */
/* ONE LAYER, THE BRAND TINT (2026-10-23, after the Cabin Collective
   and Gooseberry builds). This used to be three — a top ramp, a
   bottom ramp and a flat wash, all near black — and the figures above
   were measured on that stack. A single left-to-right tint of the
   brand's darkest step replaced them; see --hero-tint for why that is
   a contrast gain everywhere, not a loss. The copy scrim on
   .hero-offer__inner still sits over it. To put the old stack back:
     linear-gradient(to bottom, var(--hero-scrim-1) 0%, var(--hero-scrim-0) 34%),
     linear-gradient(to top,    var(--hero-scrim-foot) 0%, var(--hero-scrim-0) 58%),
     linear-gradient(var(--hero-scrim-wash), var(--hero-scrim-wash)); */
.hero-offer__scrim {
  position: absolute; inset: 0;
  background: var(--hero-tint);
}

/* Two ramps, not one. A single linear fade to the page colour has
   a visible waist about a third of the way up.

   INTO THE TINT'S GREEN, NOT THE PAGE GROUND (2026-11-01). This was
   --color-bg-primary, written when the fade took the footage down to
   the white page. Since data-theme="dark" moved onto the clip, that
   token resolves inside the pane to the dark scope's neutral ground,
   #25282D, a blue-grey (hue 240, chroma 0.008): the hero ran from the
   brand's green wash into a slate band under the "Featured in" row, a
   colour that is neither the photograph's nor the brand's. Fading into
   --hero-tint-ink instead ends the hero in the same deep green the wash
   is made of, the way the stays band and the footer end on the brand's
   darkest step rather than a neutral. A light hero swaps that ink for
   a pale one, so its foot follows. */
.hero-offer__seam {
  position: absolute; inset: auto 0 0 0;
  height: var(--hero-seam);
  background:
    linear-gradient(to top, var(--hero-tint-ink) 0%, transparent 100%),
    linear-gradient(to top, var(--hero-tint-ink) 0%, transparent 55%);
}

.hero-offer__inner {
  position: relative;
  z-index: 1;
  width: 100%;
  max-width: var(--container-max);
  margin-inline: auto;

  /* ONE CENTRED STACK. Everything in the hero sits on the middle
     axis and stays there at every width — the desktop block no
     longer moves this to the left, and the diagonal scrim that used
     to buy that layout its contrast has gone with it.

     The gap is what spaces the four children, so none of them carry
     their own bottom margin any more. Changing the rhythm of the
     hero is one number here rather than four scattered ones. */
  display: flex;
  flex-direction: column;
  align-items: center;
  gap: var(--space-4);
  text-align: center;
  /* Not .container — a hero over a photo wants a wider gutter than
     a text section, and it has no left edge to align to.

     --clip-inset-max is added to both axes so the copy keeps its full
     gutter against the pane's edge at the deepest point of the
     reveal, rather than against the viewport edge the pane has by
     then pulled away from. It is 0 until script.js sets it, so a page
     with the effect off pads exactly as it did before. */
  /* THE VERTICAL PADDING IS A CLEARANCE, NOT A RHYTHM. The column is
     centred in a stage that is exactly one screen tall and cannot
     grow, so centring is what puts air above and below it — and any
     padding on top of that is height the content has to give back.
     This pair is only what keeps the copy off the pane's edge at
     full reveal: one step of spacing plus the inset.

     It was --space-12 (and --space-16 on desktop) while the column
     was in normal flow and could push the section taller. Kept at
     those figures it overflowed a pinned stage at 1280x800, 1024x768
     and 360x740 — clipped top and bottom equally, because a centred
     flex item overflows both ways. */
  padding:
    calc(var(--space-4) + var(--clip-inset-max, 0px))
    calc(var(--space-4) + var(--clip-inset-max, 0px));

  /* NO COPY SCRIM ANY MORE. There used to be a second scrim here, a
     band sized to the copy rather than to the frame, and it existed
     because the old layout put the copy in a left column that the
     frame-wide ramp did not cover evenly.

     The column is centred now, so a band behind it is a band across
     the whole middle of the picture — which is not a scrim sized to
     the copy, it is a second frame scrim with soft ends. The frame
     scrim carries the whole job instead. That held while the wash was
     at 0.50; it does not at 0.30, so the copy scrim is back — as an
     ELLIPSE sized to this box rather than a band across the frame.

     Painted here rather than on a layer of its own because this box
     is already exactly the size and position of the thing it has to
     cover, at every viewport, for free. It has no other background,
     so there is nothing to composite against, and it sits under the
     copy and over the picture by z-index alone. */
  /* closest-side, NOT a percentage pair. A sized ellipse is measured
     against the box but its colour stops are measured against the
     RADIUS, so `75% 60%` put the transparent stop 702px from centre
     inside a box only 600px wide — the gradient was still at about
     0.11 alpha when the box ran out, and it printed a visible
     rectangle across the picture. closest-side ties the radius to the
     box's own edges, so 100% IS the edge and the fade always
     completes exactly where the box does. */
  background: radial-gradient(
    ellipse closest-side at 50% 48%,
    var(--hero-scrim-copy-1)  0%,
    var(--hero-scrim-copy-1) 38%,
    var(--hero-scrim-copy-2) 70%,
    var(--hero-scrim-0)     100%);
}

/* ---- logo ------------------------------------------------------ */
/* No crop and no frame — the logo is shown as it is. It is sized by
   HEIGHT with width left to follow, so a square mark and a wide
   wordmark both drop in without editing anything but the token. */
.hero-offer__logo {
  display: block;
  width: fit-content;
  /* No bottom margin — the column's gap spaces this now. The desktop
     block used to raise that margin to --space-7 and no longer does,
     for the same reason. */
}
.hero-offer__logo img {
  /* SIZED AGAINST THE VIEWPORT'S HEIGHT, not its width, and that is
     the point: the hero is one screen tall, so the mark's share of
     the frame is what should stay constant. A fixed 120px mark is a
     large part of what a 768px-tall window has to give, and the
     column underneath pays for it.

     The two tokens are still the floor and the ceiling, so the
     client's knobs still work — 11vh only decides where between
     them the mark lands. */
  height: clamp(var(--hero-logo), 11vh, var(--hero-logo-lg));
  width: auto;
  max-width: min(var(--hero-logo-max), 100%);
  object-fit: contain;                    /* honours the ratio if both cap */
  /* Held back a little. The mark names the brand, it is not the
     headline — at full strength a light logo over a dark scrim is
     the first and loudest thing in the frame. */
  opacity: 0.8;
  filter: var(--lift-logo);
}

/* Every string in this hero uses --color-overlay-text. Dimming
   secondary copy with --color-overlay-fg measures ~4.0:1 against
   the scrim's worst case and fails AA, so the hierarchy is carried
   by size and weight instead of by opacity. */

/* THE SHADOW IS LOAD BEARING NOW, on both strings below.
   It used to be a single wide 24px glow doing an atmospheric job the
   scrim had already done. Two layers instead, and both are contrast:
   the 2px one is a hard edge that separates a letter from whatever is
   immediately behind it, the 12px one is the pad that catches a
   bright patch of footage drifting under a counter or a serif. That
   pair is what let the scrim come down by half — see the measurements
   over the frame scrim. If you soften these, put the scrim back. */

/* ---- headline: the one liner, first in the hierarchy ------------ */
/* 16px under the headline, not the 32px it was. The offer line
   below is 16px body copy now rather than a 36px second string,
   and a satellite that small needs to sit close to what it is
   attached to — at 32px it floated exactly halfway between the
   headline and the form and stopped belonging to either. The
   welcome page's title keeps the old figure; it is followed by
   the coupon plate rather than by a subline. */
.hero-offer__title {
  /* 38rem, and NOT the 20ch the reference uses. ch is the width of
     the zero glyph in whatever face is loaded, so a character measure
     moves with the client's display font — in the placeholder serif
     here, 20ch computes to 1010px, which is most of a 1440 window and
     nothing like the two tight lines it is supposed to give. A
     headline measure has to be a distance.

     44rem is 704px, which holds the placeholder headline to two lines
     in the face this ships with — a system serif, which is a WIDE
     one. The reference gets the same two lines out of 580px because
     its display face is much narrower per character. So this number
     is not portable: it is the width that fits about sixteen
     characters of the CURRENT font at 72px.

     RE-CHECK IT WHEN YOU CHANGE THE DISPLAY FONT. Two lines is the
     ceiling, and the fix for a third is fewer words first and a
     wider column second. The old cap was 34rem, solved against a
     left column that had to stay inside a diagonal scrim — that
     constraint is gone, and the extra width is the centred column
     taking back what the diagonal used to cost it.

     FLUID SIZE, AND A DELIBERATE DEPARTURE FROM THE TYPE SCALE.
     .type-hero steps once at 767px — 72px above, 48px below — which
     is the system's rule and is right for a heading in normal flow.
     It is wrong for this one. The hero is pinned to exactly one
     screen and cannot grow, so through the middle of the range a
     flat 72px headline runs to three lines and crowds the lede and
     the form against the frame. Sizing it against the viewport keeps
     it to two lines the whole way down, which is what the reference
     layout does and the only reason it holds at every width.

     36px to 72px, so it still lands on the scale's own two figures
     at the ends and only interpolates between them. To go back to
     the stepped role, delete these two declarations and the matching
     pair on the lede. */
  font-size: clamp(2.25rem, 6vw, 4.5rem);
  line-height: 1.04;
  max-width: 44rem;
  color: var(--color-overlay-text);
  text-wrap: balance;
  text-shadow: var(--hero-text-halo);
}

/* THE SECOND CLAUSE. Italic and in the brand accent — the only
   decoration in the headline, and the reason it reads as a written
   line rather than a slab of display type.

   --accent-200, NOT --color-text-accent, and the difference is
   measured. The semantic token is --accent-300 under this section's
   dark scope, which is the step solved to pass against a dark PAGE
   GROUND — a flat, known colour. This headline's ground is a
   photograph behind a scrim, which is lighter and far less
   predictable, and 300 came in at 2.97:1 there against a 3:1 bar.
   That is a real failure, not a thin pass. One step lighter measures
   3.81:1 at 1440 and 3.25:1 at 390 over the same placeholder — a
   pass with margin.

   The same argument the hero's scrim tokens make applies here: a
   string over client footage cannot borrow a figure solved against a
   theme surface. Re-measure this one too if the footage changes.

   White would be safest of all and is not the point — the accent is
   what makes the line read as written rather than set. The two-layer
   text-shadow the rest of the headline carries is inherited and is
   NOT counted in the figure above; it is margin on top of a pass. */
/* UPRIGHT, colour only. The second clause used to be italic as well as
   accent-coloured; the italic went (2026-09-22) and the colour alone now
   carries it. Two things stopped being a reason to keep it: a client
   brand whose one webfont has no italic gets a synthesised oblique that
   looks wrong, and on the brands that do, the colour was already doing
   the work. The same call is made on the stays and reviews headings. */
.hero-offer__title em {
  font-style: normal;
  color: var(--accent-200);
}

/* ---- the lede: second in the hierarchy -------------------------- */
/* This replaced a bare "Sign up and receive [10% OFF]". A single
   short line under a 72px headline reads as a caption on it; a
   sentence or two that says what the place actually is reads as the
   thing the headline was promising. The offer was folded into the end
   of this sentence for a while; it is its own line in the signup group
   below now (2026-10-07), because at the end of the description it
   read as more description rather than as the reason to use the form.

   The step does the hierarchy either way: 72px to 16px leaves no
   question what is read first. 16px is also the floor this can take
   — it is white type over a photograph, and below 16px the scrim
   under it would have to be re-measured against the 4.5:1 small text
   bar rather than the 3:1 large text one it was solved for.

   52ch is about two lines here. Past three it stops being a lede. */
.hero-offer__lede,
.hero-offer__prompt {
  /* 16px at every width, the body size — it was fluid to 18px on a
     wide screen until 2026-10-06, when the client set every section
     description to 16px on both. 16px is also the floor the contrast
     under it was measured at, so nothing there moves. */
  font-size: var(--fs-text-md);
  line-height: var(--lh-text-md);
  max-width: 52ch;
  color: var(--color-overlay-text);
  text-shadow: var(--hero-text-halo);

  /* Regular, not the role's own semibold. The amount inside it is
     bold, and 600 against 700 is a step you cannot see — the
     emphasis was landing on nothing. 400 against 700 reads
     immediately, and it makes the sentence around it behave like
     the running copy it is. */
  font-weight: var(--fw-regular);
}

/* ---- the signup group: the offer line and the form -------------- */
/* LAW OF PROXIMITY. The offer line is the form's lead-in, not the
   lede's last sentence, so it is grouped with the field by space
   alone: 8px down to the pill, and 40px up to the lede (the column's
   24px gap plus the 16px margin here). Those are line-box edges; to
   the eye, with the half-leading, it is about 16px against 48px.

   THE HERO IS ONE PINNED SCREEN AND CANNOT GROW, so every pixel here
   is height the column has to find. The extra line and this spacing
   were checked at 1440x900, 1280x800, 1280x680, 1024x768, 390x844,
   360x740 and 390x667; 1280x680 is the tight one, with the form a few
   pixels clear of the "Featured in" row. Widen these and re-check
   that size first. Same size, weight and colour as
   the lede — the amount's <strong> and its glow already make it the
   loudest thing in the line, and a bigger line would be a second
   headline. width: 100% so the form keeps its own min(30rem, 100%)
   against the column, as it did when it was the column's child. The
   form is still the last thing in the column, so its error chip still
   hangs below it with nothing to land on but the press row (see
   "the row steps aside for an error"). */
.hero-offer__signup {
  display: flex;
  flex-direction: column;
  align-items: center;
  gap: var(--space-2);
  width: 100%;
  margin-top: var(--space-3);
}

.hero-offer__amount {
  display: inline-block;                  /* so the bloom below has a box to
                                             sit in; an inline span does not
                                             give ::before a reliable one */
  white-space: nowrap;                    /* and so it never splits mid amount */
  position: relative;
  isolation: isolate;                     /* keeps ::before above the photo */

  /* Georgia, still in --font-display's stack behind the re-measured Times
     New Roman fallback, has OLDSTYLE numerals, which render "10%" with an
     x-height zero. The discount is the loudest glyph on the page and it does
     not get to depend on which face happens to be drawing it. */
  font-variant-numeric: lining-nums;
}
/* Walden, 2026-09-23: the one bold on the page, by request. A literal 700
   because every weight token on this build resolves to regular, and the
   Typekit kit serves Proxima Nova 700 so it is a real face. */
.hero-offer__amount { font-weight: 700; }

/* THE GLOW.
   A soft brand tinted bloom BEHIND the text, not a halo traced around
   each glyph. Two reasons. A per glyph outline is the neon tell that
   reads cheap on a hospitality page, and animating text-shadow or
   filter repaints 72px type every frame, where a pseudo element only
   needs opacity and transform — both of which the compositor handles.

   The dark text-shadow above is now doing double duty: it keeps a
   dark separation at the glyph edges, which is what stops a bright
   client brand colour from washing the contrast out. Removing one
   without the other is what breaks this. */
.hero-offer__amount::before {
  content: "";
  position: absolute;
  /* RE-SCALED WITH THE TYPE. These were 16px/24px, set against a
     36px offer line standing on its own. The amount is inline inside
     16px running copy now, and a bloom that size around it reads as a
     smudge across the words either side rather than as a light behind
     the number. In ems so it tracks the text it is set in, which is
     also what keeps it right after a client changes the type scale. */
  inset: -0.5em -0.75em;
  z-index: -1;
  border-radius: 50%;
  background: radial-gradient(58% 58% at 50% 50%,
    var(--glow-core)  0%,
    var(--glow-mid)  46%,
    transparent      74%);
  opacity: .42;                           /* the still state */
  pointer-events: none;
}

/* The one perpetual animation on the page, and it is on the one
   element the whole hero exists to sell. Under reduced motion the
   bloom above simply holds at .42, which looks deliberate rather
   than broken. */
@media (prefers-reduced-motion: no-preference) {
  .hero-offer__amount::before {
    animation: amount-breathe var(--dur-breathe) var(--ease-in-out) infinite;
  }
}
@keyframes amount-breathe {
  0%, 100% { opacity: .30; transform: scale(0.96); }
  50%      { opacity: .66; transform: scale(1.04); }
}

/* ---- entrance -------------------------------------------------- */
/* Six elements, 70ms apart. First load only, so it is allowed to
   be slower than a UI transition. */
@media (prefers-reduced-motion: no-preference) {
  .hero-offer__logo,
  .hero-offer__title,
  .hero-offer__lede,
  .hero-offer__prompt,
  .offer-form--hero,
  .hero-offer__featured {
    animation: hero-rise var(--dur-reveal) var(--ease-out) both;
  }
  .hero-offer__logo   { animation-delay:  40ms; }
  .hero-offer__title  { animation-delay: 110ms; }
  .hero-offer__lede   { animation-delay: 180ms; }
  .hero-offer__prompt { animation-delay: 250ms; }
  .offer-form--hero   { animation-delay: 320ms; }
  .hero-offer__featured { animation-delay: 390ms; }
}
/* 0.01, NOT 0 (from the Cabin Collective build, 2026-10-15). With the
   hero pinned in its 200vh track (data-clip-reveal), Chrome recorded NO
   Largest Contentful Paint at all when the headline and lede were first
   painted at opacity 0 — measured there: Lighthouse reported NO_LCP
   and a Performance score of 0 on /booknow, and every real Chrome
   visit would have reported no LCP to Core Web Vitals either. Starting
   at 1% is invisible to the eye and counts as painted, so the text is
   an LCP candidate from the first frame. Do not "tidy" it back to 0. */
@keyframes hero-rise {
  from { opacity: 0.01; transform: translateY(0.5rem); }
  to   { opacity: 1; transform: none; }
}

/* ---- the light hero --------------------------------------------- */
/* A PALE TINT WITH DARK TYPE, from the Gooseberry build (2026-10-21,
   the client's call: a cream tint over the footage rather than a dark
   one). Two changes in the markup, made together or the type ends up
   the same lightness as its ground:
     1. class="hero-offer hero-offer--light" on the <header>, on both
        pages — this block;
     2. data-theme="light" instead of "dark" on the content scope:
        .hero-offer__clip on index.html, .hero-offer__inner.welcome on
        welcome.html — so the copy, the form and the logo take the
        light token set and go dark.

   THE INK. Gooseberry used its accent, --accent-base, because that
   accent IS a cream (#F9EDD1, oklch L 0.948). The template defaults to
   --brand-50, the palest step of any brand; any ink at L 0.94 or
   lighter carries the figures below. Same 85% to 69% sweep as the
   dark tint. Worked on Gooseberry over pure BLACK footage, the hard
   case now, under the tint's thin 0.69 edge with no copy ellipse:
   the 96% overlay ink held 5.5:1 (bar 4.5) and the accent clause at
   --accent-800 3.3:1 (bar 3.0, large text); inside the ellipse 6.9
   and 4.2. White footage only raises them. RE-MEASURE with the
   client's accent: 800 is a step solved for a navy-and-cream brand.

   Everything else here follows from "dark type wants a light halo":
   the text halo, the copy ellipse and the form's frost turn pale; the
   amount's bloom goes white (a brand bloom behind brand-dark type
   takes contrast away from the one number the hero sells); the logo
   loses --lift-logo, whose dark shadow under dark line art on a light
   frame reads as a smudge; and the error state inverts. Swap the
   logo for the client's dark version, and the press logos too. */
.hero-offer--light {
  --hero-tint-ink: var(--brand-50);
  --hero-tint: linear-gradient(90deg,
    color-mix(in oklab, var(--hero-tint-ink) 85%, transparent) 0%,
    color-mix(in oklab, var(--hero-tint-ink) 69%, transparent) 100%);
  --hero-text-halo:
    0 1px 2px color-mix(in oklab, var(--hero-tint-ink) 60%, transparent),
    0 2px 12px color-mix(in oklab, var(--hero-tint-ink) 80%, transparent);
  --hero-scrim-copy-1: color-mix(in oklab, var(--hero-tint-ink) 50%, transparent);
  --hero-scrim-copy-2: color-mix(in oklab, var(--hero-tint-ink) 28%, transparent);
  --hero-form-tint: rgba(255, 255, 255, 0.60);
  --glow-core: rgba(255, 255, 255, 0.90);
  --glow-mid:  rgba(255, 255, 255, 0.35);
}
.hero-offer--light .hero-offer__title em { color: var(--accent-800); }
.hero-offer--light .hero-offer__logo img { filter: none; }

/* The error state, inverted: near-opaque WHITE under the invalid pill
   and its ring, and a light chip under the message. On Gooseberry the
   pill's error-600 edge held 3.3:1 over black footage (bar 3.0), and
   error-700 on the chip about 4.9:1 over black and 5.9:1 over white
   (bar 4.5 for the 14px line). See the dark versions further down,
   under "validation state", for why each one exists. */
.hero-offer--light .offer-form--hero.is-invalid { background: rgba(255, 255, 255, 0.92); }
.hero-offer--light .offer-form--hero.is-invalid:focus-within {
  box-shadow: 0 0 0 6px rgba(255, 255, 255, 0.90);
}
.hero-offer--light .offer-form--hero .offer-form__error {
  background: rgba(255, 255, 255, 0.92);
  color: var(--error-700);
}

/* ---- featured in ------------------------------------------------ */
/* Social proof, pinned to the foot of the frame rather than stacked
   in the column. It is positioned against the pane, and the pane is
   what pulls in as the hero reveals — so the offset carries
   --clip-inset-max the same way the column's padding does, and the
   row travels in with the edge instead of being left behind by it.

   pointer-events:none because nothing in it is clickable. A row of
   logos that shows a text cursor reads as broken links.

   THE COLUMN MAKES ROOM FOR IT rather than this floating over the
   form: see the padding-bottom on .hero-offer__inner:has(~ ...)
   below. Delete the markup and the room goes with it. */
.hero-offer__featured {
  position: absolute;
  left: 0;
  right: 0;
  bottom: calc(var(--space-7) + var(--clip-inset-max, 0px));
  z-index: 1;
  display: flex;
  flex-direction: column;
  align-items: center;
  gap: var(--space-3);
  padding-inline: var(--space-4);
  pointer-events: none;
  transition: opacity var(--dur-ui) var(--ease-out),
              visibility 0s linear var(--dur-ui);
}
/* THE ROW STEPS ASIDE FOR AN ERROR. The hero form's validation message
   hangs below the pill out of flow (see "validation state"), and on a
   short screen — 1280 x 680 measured — that chip landed 14px over this
   row. Rather than reserve the chip's height under the form for good,
   the quietest thing in the hero fades out for as long as the message
   shows and comes back when the field is edited. A browser without
   :has() keeps the row, and on a short screen the two can touch. */
.hero-offer:has(.offer-form--hero.is-invalid) .hero-offer__featured {
  opacity: 0;
  visibility: hidden;
  transition: opacity var(--dur-ui) var(--ease-out), visibility 0s;
}

/* The quietest string in the hero, and deliberately so. Caps at
   11px with a lot of letterspacing reads as a label rather than as
   copy, which is what stops it competing with the lede above it.

   --color-overlay-fg, not --color-overlay-text: this is the one
   string in the hero that is allowed to be dimmer than the rest,
   because it is a label on a row of logos rather than something
   anybody needs to read. */
.hero-offer__featured-label {
  font-family: var(--font-body);
  font-size: var(--fs-text-xs);
  line-height: var(--lh-text-xs);
  letter-spacing: var(--ls-wider);
  text-transform: uppercase;
  color: var(--color-overlay-fg);
  text-shadow: var(--stay-text-shadow);
}

.hero-offer__featured-row {
  display: flex;
  flex-wrap: wrap;
  align-items: center;
  justify-content: center;
  gap: var(--space-6);
  margin: 0;
  padding: 0;
  list-style: none;
}

/* SIZED BY HEIGHT, width left to follow. Publication wordmarks have
   wildly different proportions — a square masthead and a long serif
   nameplate have nothing in common but their cap height — and
   matching on height is the only thing that makes a row of them look
   like a row rather than a pile.

   The opacity is what keeps three competing logos from reading as
   louder than the client's own mark at the top of the same frame. */
.hero-offer__featured-logo {
  display: block;
  /* 14px to 22px. The floor is what keeps three logos on ONE row at
     360px: at the flat 20px this used to be they measured 273px
     against 312px of room once the gaps were paid for, wrapped to
     two rows, and grew the block into the form above it. */
  height: clamp(0.875rem, 1.6vw, 1.375rem);
  width: auto;
  max-width: 100%;
  opacity: 0.72;
}

/* ---- room for it ------------------------------------------------ */
/* The column is centred in the frame and the row is pinned to the
   bottom of it, so on a short window the form and the logos meet in
   the middle. This pushes the column up by the height of the row
   plus its offset.

   :has() rather than a modifier class, so deleting the markup is the
   only thing a client has to do — there is no second edit to
   remember, and no state where the padding is reserved for a row
   that is not there. A browser without :has() simply keeps the
   column centred, which is the layout without the row. */
.hero-offer__inner:has(~ .hero-offer__featured) {
  /* The column's own bottom clearance plus 5rem, which is the row's
     label, gap and logos together with a little air. An addition to
     the base rather than a replacement for it, so changing the
     clearance above moves this with it. */
  padding-bottom: calc(var(--space-4) + var(--clip-inset-max, 0px) + 5rem);
}


/* ============================================================
   THE LINE  —  one statement, filled in by the scroll
   ------------------------------------------------------------
   The back half of the hero's opening movement. On this build an
   ordinary block about two thirds of a screen tall, and the words
   ink in as the statement rises from the fold to the middle of the
   screen.

   NOT PINNED HERE (Walden Retreats, 2026-10-02). The template pins
   the line: a sticky stage one screen tall, held for most of a second
   screen while the scroll past it fills the words in. The client read
   that held screen, a sentence alone on white with nothing moving
   under it, as the end of the page. Shorter than a screen and in
   flow, the next section is already arriving underneath by the time
   the line is read. The fill itself is the template's; what drives it
   is the statement's own travel up the screen (script.js, SCROLL
   FILL), not a track's.

   Each word is painted by a gradient clipped to its own glyphs,
   and script.js moves the gradient's stop across the word by
   writing --fill from 0 to 1. Below the stop the word is text
   colour, above it the ghost, so the fill reads as the word being
   inked in from the left rather than as it fading up. --rise runs
   the same way but faster, and carries the small lift and the
   un-blur that stop eight words filling in a row from reading as
   a loading bar.

   Everything here degrades to a plain centred statement: no
   JavaScript, no @property support, no background-clip support and
   reduced motion all land on fully inked words on a static stage.
   ============================================================ */

/* --fill and --rise have to be REGISTERED or none of this moves.
   An unregistered custom property is a string as far as the engine
   is concerned, so it has no interpolable value and the transition
   on .line__word below is silently a no-op — the words would snap
   between the forty positions the script writes instead of running
   between them. Registering them as <number> is what makes them
   animatable, and the initial values are the effect's rest state.

   They are declared at the top level because @property always is;
   inherits:false keeps them from leaking down into anything nested
   inside a word. */
@property --fill {
  syntax: "<number>";
  inherits: false;
  initial-value: 1;
}
@property --rise {
  syntax: "<number>";
  inherits: false;
  initial-value: 1;
}

:root {
  /* THE AIR ABOVE AND BELOW THE STATEMENT. About a quarter of the
     screen each side on a laptop, which puts the next section's top
     at the fold once the line has reached the middle of the screen.
     The floor keeps a phone from closing up around four lines of 32px
     type; the ceiling keeps a tall monitor from opening back out into
     a blank field. */
  --line-air: clamp(var(--space-16), 24svh, 16rem);
}

.line {
  position: relative;
  z-index: 1;
  /* Pulls the track up by a hairline onto the hero's bottom edge.
     Two full bleed sections on the same ground still print a seam
     between them at some device pixel ratios; overlapping them by
     less than a pixel is the cheapest way to never see it. */
  margin-top: -1px;
  background: var(--color-bg-primary);
}

/* No height of its own: the air token above and the statement
   inside are the whole of it, so the block grows with the type and
   never reaches a full screen at any width. */
.line__stage {
  position: relative;
  display: flex;
  align-items: center;
  justify-content: center;
  padding: var(--line-air) var(--space-4);
}

/* THE WATERMARK.
   Masked rather than placed, so the client's mark takes the page's
   text colour instead of bringing its own — which is what lets the
   same file sit behind light and dark ground without a second
   asset. Only the silhouette survives a mask; see the note in the
   file itself.

   5% is the whole point of it. It is meant to be the thing you
   notice on the second read, and anything heavier turns the words
   in front of it into type over a pattern. If the client's mark is
   a thin wordmark rather than a solid shape it will disappear
   entirely at this weight — that is a sign to use the solid mark,
   not a sign to raise the number.

   THE MARK IS THE HERO'S LOGO (2026-11-01). script.js (THE LINE'S
   WATERMARK) reads the logo off the hero, or the file named in
   data-mark on the span, and hands it over as --line-mark when the
   section is near; until then, and without JavaScript, the span is
   display: none, which also stops the file loading early. Every
   build used to repoint this by hand, and one shipped with the
   template's placeholder still behind the words. */
.line__mark {
  display: none;
  position: absolute;
  left: 50%;
  top: 50%;
  translate: -50% -50%;
  z-index: 0;
  /* Sized against the block rather than the screen (the line is not
     pinned on this build): as tall as the section less a margin,
     capped so the silhouette never outgrows the statement it is
     behind. The mask is contain, so a box wider than the glyph only
     adds transparent space around it. */
  width: min(84vw, 26rem);
  height: min(32rem, calc(100% - var(--space-9)));
  opacity: 0.05;
  pointer-events: none;
  background-color: var(--color-text-primary);
  -webkit-mask: var(--line-mark) center / contain no-repeat;
          mask: var(--line-mark) center / contain no-repeat;
}
.line__mark.has-mark { display: block; }

/* A WIDE LOGO, any wider than it is tall (script.js adds the class
   and --line-mark-ratio, width over height). contain sizes it by
   width, so a landscape lock-up in the box above would come out as a
   strip; the box widens by the logo's ratio instead. Walden's mark
   is the lantern alone (data-mark), taller than wide, so this is
   here for the day the mark changes. */
.line__mark--wide { width: min(96vw, 56rem, calc(26rem * var(--line-mark-ratio, 1))); }

/* A browser with no mask support would paint the rectangle above as
   a flat block of text colour across the middle of the line. Hiding
   it is the correct fallback — the watermark is decoration, and
   decoration that fails should leave nothing rather than a bar. */
@supports not ((-webkit-mask-image: none) or (mask-image: none)) {
  .line__mark.has-mark { display: none; }
}

/* Type comes from .type-hero in the markup — 72px down to 48px on a
   phone — so nothing here sets a size. The measure is what is set
   here instead: about four words a line is the shape the stagger
   was tuned against, and a statement that runs to five or six lines
   fills from the top left corner of a paragraph rather than across
   a headline. */
.line__text {
  position: relative;
  z-index: 1;
  margin: 0;
  /* Fluid, for the same reason the hero's headline is: a flat 72px
     statement runs to five lines through the middle of the range.
     32px to 68px. */
  font-size: clamp(2rem, 5.4vw, 4.25rem);
  line-height: 1.14;
  max-width: min(22ch, 100%);
  text-align: center;
  text-wrap: balance;
  color: var(--color-text-primary);
}

.line__word {
  /* How far past each end of the word the gradient's two stops are
     pushed. Without it the stop is a hard vertical edge sitting
     inside a letter at the moment it crosses one; with it the
     transition is always wider than the glyph it is passing over,
     so a word inks in rather than wiping. In ems so it scales with
     the type. */
  --edge: 0.4em;
  /* NOT currentColor. The element sets color:transparent two rules
     down — that is what turns the glyphs into a window onto the
     gradient — so currentColor here resolves to transparent and the
     inked half of every word paints nothing at all. It has to be the
     token itself. */
  --line-ink: var(--color-text-primary);

  /* THE GHOST IS MEASURED, not picked for looks. A word that has not
     filled in yet is still a word on the screen, and a reader who
     stops scrolling mid line is looking at it — so the unfilled end
     has to clear a contrast bar on its own rather than borrow the
     inked end's. At 72px down to 48px this is large text, so the bar
     is 3:1.

     --color-text-tertiary measures 3.90:1 on the light ground and
     7.04:1 on the dark one, against an inked 9.50:1 and 13.67:1.
     --color-text-disabled is the more dramatic fill and was the
     first choice, but it comes in at 2.10:1 on light, which is a
     real failure rather than a thin pass. If you want more
     separation, take the ink up — do not take the ghost down. */
  --line-ghost: var(--color-text-tertiary);

  /* DECLARED HERE AS WELL AS REGISTERED ABOVE, and both are load
     bearing. @property makes them animatable; these two make them
     exist. A browser without @property ignores that block entirely,
     which leaves --fill with no value at all — and an undefined
     custom property inside the calc below takes the whole
     background-image down with it, leaving color:transparent and a
     line of invisible words. With these, the worst that browser
     gets is a statement that does not animate.

     1, not 0, for the same reason the registered initial values are:
     inked is the rest state, and script.js zeroes them itself on the
     frame it takes over. */
  --fill: 1;
  --rise: 1;

  display: inline-block;

  /* The gradient is the word's colour and the text is the window
     cut out of it. Both --fill positions are expressed against the
     word's width plus the two overshoots, which is what keeps the
     ends reaching true 0 and true 1 rather than stopping --edge
     short at each end. */
  background-image: linear-gradient(90deg,
    var(--line-ink)   calc(var(--fill) * (100% + var(--edge) * 2) - var(--edge) * 2),
    var(--line-ghost) calc(var(--fill) * (100% + var(--edge) * 2)));
  -webkit-background-clip: text;
          background-clip: text;
  color: transparent;

  /* Both driven off --rise, not --fill, so the word has finished
     arriving by the time it is a third inked — the movement
     introduces the word, the fill reads it. */
  transform: translate3d(0, calc((1 - var(--rise)) * 0.2em), 0);
  filter: blur(calc((1 - var(--rise)) * 2.5px));

  /* Bridges the hundred steps the script writes into continuous
     motion. Same trick, and same reason, as the hero's clip — a
     shorter tween than the clip's because the steps are finer. */
  transition:
    --fill var(--dur-fill) var(--ease-out),
    --rise var(--dur-fill) var(--ease-out);
}

/* background-clip:text is what makes a word transparent in the
   first place. Where it is unsupported the declaration above is
   dropped but color:transparent is not, and the line would be
   invisible — so the ink is restored the moment the clip is not
   available. */
@supports not ((-webkit-background-clip: text) or (background-clip: text)) {
  .line__word {
    background-image: none;
    color: var(--line-ink);
  }
}

/* The rest state is INKED, not empty — see the initial values on the
   two registered properties above. That is the whole no-JavaScript
   story: the line is simply a headline. script.js takes the words
   back to zero itself, on the same frame it starts driving them, so
   there is no flash of a finished line first.

   Which also means this block is doing nothing under reduced motion
   except making sure of it: the script stands down, the words are
   never zeroed, and the stage never pins. */
@media (prefers-reduced-motion: reduce) {
  .line__word {
    --fill: 1;
    --rise: 1;
    transform: none;
    filter: none;
  }

  /* Nothing to collapse: the block is the same size animated or not. */
}

/* A SHORT PHONE TIGHTENS THE STACK (2026-11-01). Holding the logo row
   48px off the hero's foot (below) costs a 640px-tall screen 12px
   between the form and "Featured in", which left 5px there at 360 x
   640. The column's gap drops a step instead, 24px to 16px, which
   buys back exactly what the floor took: 17px at 360 x 640 and 30px
   at 375 x 667, the same as before it. A phone over 700px tall has
   the room and keeps 24px, and a hero with no logo row (welcome.html)
   is left alone. */
@media (max-width: 640px) and (max-height: 700px) {
  .hero-offer__inner:has(~ .hero-offer__featured) { gap: var(--space-3); }
}

@media (max-width: 640px) {
  /* The row is tighter on a phone, and it has to be: three logos, a
     32px gap and a 24px gutter do not fit across 360px, and a row
     that wraps to three lines grows past the space the column above
     reserved for it and is landed on by the form. */
  .hero-offer__featured-row { gap: var(--space-4); }
  /* The row keeps the base 48px off the hero's foot here too, the page's
     floor for a section's edge (2026-11-01). It used to drop to 24px
     on a phone; the column reserves the extra 24px with it. */
  .hero-offer__inner:has(~ .hero-offer__featured) {
    padding-bottom: calc(var(--space-7) + var(--clip-inset-max, 0px) + 4rem);
  }

  /* A narrower measure on a phone: three or four words a row rather
     than one long one, which is the shape the stagger reads as. */
  .line__text { max-width: min(15ch, 100%); }
}

/* ============================================================
   OFFER FORM  —  used by the hero and by section 9
   ------------------------------------------------------------
   One component in two settings. In the hero it is a white
   surface floating on a photograph, so it carries its own fill
   and shadow. In the closing panel it is a dark well cut into a
   dark plate, so it carries a hairline instead. Both run their
   control row inline once there is width for it; the base is the
   stacked phone layout.

   The control carries data-theme="light" in the hero — a light
   surface on a dark page, the same trick the cards use. The
   closing panel inverts that: the panel itself is pinned dark
   and the control simply inherits it.
   ============================================================ */

/* Hidden from view, kept for assistive tech. The 1px box and the
   negative margin are the canonical visually-hidden recipe, not
   layout spacing, which is why they sit off the 8pt scale.
   display:none and visibility:hidden would both take the label out
   of the accessibility tree with it, leaving the input unnamed. */
.offer-form__label {
  position: absolute;
  width: 1px;
  height: 1px;
  margin: -1px;
  padding: 0;
  overflow: hidden;
  clip-path: inset(50%);
  white-space: nowrap;
  border: 0;
}

.offer-form__control {
  display: flex;
  flex-direction: column;
  gap: var(--space-1);
  padding: var(--space-1);
  border: 1px solid var(--color-border-default);
  /* HALF A FIELD ROW, which is a pill exactly when the control is
     one row and a concentric 28px when it is two. --radius-pill
     cannot do both: CSS scales an over-large radius down against
     the SHORTER side, so on the stacked layout 999px turned the
     control into a lozenge and the full width button inside it
     pushed straight out through the corners.

     Derived instead. The button is one row less its own share of
     the padding, so its pill radius is (--field-h - 8) / 2 = 24,
     and 4px of padding around it puts this at 28 — concentric in
     both directions, and a true pill in the row case because 28 is
     already half of the 56 the row measures. The 1024 breakpoint
     bumps the rows to --field-h-lg and re-derives it there. */
  border-radius: calc(var(--field-h) / 2);
}

/* The ring goes on the container, not the input. The input has no
   edge of its own, so a ring drawn on it would float in the middle
   of a white box. */
.offer-form__control:focus-within {
  outline: 2px solid var(--color-border-focus);
  outline-offset: 2px;
}

.offer-form__field {
  display: flex;
  align-items: center;
  gap: var(--space-2);
  min-height: calc(var(--field-h) - var(--space-2));
  padding-inline: var(--space-3);
}

.offer-form__icon {
  flex: 0 0 auto;
  width: 1.5rem; height: 1.5rem;
  color: var(--color-fg-secondary);
}
.offer-form__icon svg { width: 100%; height: 100%; }

.offer-form__input {
  flex: 1;
  min-width: 0;
  border: 0;
  outline: 0;                             /* the container shows focus */
  background: transparent;
  color: var(--color-text-primary);
}

/* gray-700, not gray-600. The lighter step measures 3.9:1 on white
   and fails AA for placeholder text. */
.offer-form__input::placeholder { color: var(--color-text-secondary); }

.offer-form__control .btn {
  display: flex;
  align-items: center;
  justify-content: center;
  min-height: calc(var(--field-h) - var(--space-2));
  padding-block: 0;
  /* The pill again, restated because this rule used to hold a
     smaller radius derived from the control's old 16px corner. The
     control is now half a row, so a pill inside it is concentric
     by construction — see .offer-form__control. */
  border-radius: var(--radius-pill);
}


/* ---- validation state ------------------------------------------ */
/* script.js adds .is-invalid to the form AND to the control and fills
   the .offer-form__error line when an address is refused — either by
   its own shape check or by the function's 400. Both use the semantic
   error tokens, which _template.css already re-points per theme
   (error-700 on light, error-400 on dark). Both forms on this page
   sit inside data-theme="dark" — the hero clip and the closing
   plate — so both resolve to error-400. Nothing new is defined here.

   The focus ring goes red too. Left alone it would draw a red edge
   inside a brand-coloured halo, which reads as two messages at once. */
/* Prefixed with .offer-form so these outrank `.offer-form--claim
   .offer-form__control`, which sets the closing field's resting border
   further down the file at the same two-class weight and would
   otherwise win on source order — that left the closing field's edge
   grey while its message said it was wrong. Measured, then fixed. */
.offer-form .offer-form__control.is-invalid { border-color: var(--color-border-error); }
.offer-form .offer-form__control.is-invalid:focus-within { outline-color: var(--color-border-error); }

/* THE HERO CARRIES ITS EDGE AND ITS RING ON THE FORM, not on the
   control — the frosted pill is the form (see the hero variant
   below) and the control inside it is deliberately transparent. So
   the red goes on the form's hairline and on the ring, and the
   control stays transparent rather than drawing a second ring one
   pixel in. */
.offer-form--hero.is-invalid { border-color: var(--color-border-error); }
.offer-form--hero.is-invalid .offer-form__control { border-color: transparent; }
/* A TWO-COLOUR FOCUS RING (WCAG technique C40). The red ring sits on
   moving footage, and no single red clears 3:1 against every frame:
   measured 2.45:1 at 1440 and 1.87:1 at 390 over the brighter ones.
   A dark halo painted behind it — a box-shadow spread past the ring —
   gives the red line a dark neighbour on both sides at every frame:
   worst case, the halo over pure white still holds 6.3:1 against the
   red. The ring itself stays an `outline`, not a shadow, because
   Windows' forced-colours mode removes box-shadows and keeps
   outlines; there the halo vanishes and the system ring remains. */
.offer-form--hero.is-invalid:focus-within {
  outline-color: var(--color-border-error);
  box-shadow: 0 0 0 6px rgba(9, 11, 14, 0.85);
}

/* OVER FOOTAGE, THE PILL GOES DARK IN THE ERROR STATE. The hero form
   is a frost (--hero-form-tint, 0.28 when this was measured and 0.60
   since 2026-10-23) laid on moving footage, so a red hairline and a
   red focus ring on it are measured
   against whatever frame is behind them — and over a bright frame the
   thin red line drops under the 3:1 WCAG 1.4.11 floor. Deepening the
   tint to 0.82 only while invalid gives the red edge and the ring a
   dark ground to sit against at every frame, and does the same for
   the white input text. It is a transient state, so the darker pill
   is only ever seen with an error showing. */
.offer-form--hero.is-invalid {
  background: rgba(9, 11, 14, 0.82);
}

.offer-form__error {
  margin-top: var(--space-2);                /* 8px — one grid step */
  color: var(--color-text-error);
}

/* The hero's line hangs BELOW the pill rather than inside it. The
   form is the frosted pill, so a child in normal flow would sit
   inside the frost, under the control, and stretch the pill around
   it. Taken out of flow and pinned to the pill's bottom edge, the
   pill keeps its shape and the line reads as a caption under it,
   centred like the rest of the hero column. The form is the last
   thing in that column, so nothing below can collide with it. */
.offer-form--hero { position: relative; }
.offer-form--hero .offer-form__error {
  position: absolute;
  top: 100%;
  left: 50%;
  transform: translateX(-50%);
  width: max-content;
  max-width: 100%;
  /* 16px clear of the pill: the focus ring reaches 4px below it and its
     dark halo 6px, so the chip reads as its own thing rather than
     merging into the halo. */
  margin-top: var(--space-3);
  /* ITS OWN DARK CHIP. The line hangs below the pill over raw footage,
     with no frost behind it, and the light-red text alone fell under the
     4.5:1 floor over the brighter frames. A near-opaque chip of the
     hero's own 9,11,14 scrim under the words puts error-400 on a fixed
     dark ground at every frame: measured 8.55:1 at 1440 and at 390 over a
     full loop, and 7.0:1 even composited over pure white. It reads as a
     small error toast under the field. The raw ramp step is named
     directly because the semantic token resolves per theme, not per
     background. Full table in the README, under the email forms. */
  padding: var(--space-1) var(--space-3);
  background: rgba(9, 11, 14, 0.88);
  border-radius: var(--radius-pill);
  color: var(--error-400);
  text-align: center;
}

/* While the function is checking the address. Same muted treatment the
   rail arrows use when they cannot go any further. */
.offer-form__control .btn[aria-busy="true"] {
  cursor: progress;
  opacity: 0.7;
}


/* ---- the hero variant ------------------------------------------ */
/* No margin-top — the hero column's gap spaces this now. */
.offer-form--hero {
  width: min(30rem, 100%);
  /* THE FROST LIVES HERE, ON THE <form>, NOT ON THE CONTROL INSIDE IT
     (2026-10-02). The same three declarations sat on
     .offer-form__control and never rendered: measured with a striped
     test card behind the pill, the backdrop-filter changed nothing —
     not at blur(10px), not at blur(30px) with an invert on top — in
     the headless shell and in full Chromium alike, while the identical
     rule on a plain page blurred at once. Bisected by dropping a fresh
     blurred probe into each ancestor: it blurs inside .hero-offer,
     the stage, the clip and the column, and goes dead the moment it is
     a child of this form, with every property on the form neutralised.
     Lifted one level, to the form itself, it renders. The control keeps
     its box and its 1px edge (transparent) so nothing moves; this
     border sits just outside it with a radius one pixel larger, so the
     two stay concentric. The 1024 breakpoint re-derives both below. */
  background: var(--hero-form-tint);
  border: 1px solid var(--color-overlay-border);
  border-radius: calc(var(--field-h) / 2 + 1px);
  backdrop-filter: blur(10px);
  -webkit-backdrop-filter: blur(10px);
}
/* The ring moves out with the frost: drawn on the form, which is now
   the visible pill, rather than 1px inside it on the control. */
.offer-form--hero:focus-within {
  outline: 2px solid var(--color-border-focus);
  outline-offset: 2px;
}
.offer-form--hero .offer-form__control:focus-within { outline: none; }

/* FROSTED, NOT SOLID. The hero form used to be a solid panel of page
   colour sitting on the footage; it is a pane of the footage itself
   now, tinted and blurred, with a hairline of light around it.

   That is a real change and it is worth saying why. A solid card in
   the middle of a centred hero cuts the picture in half — it reads as
   a dialog that has opened over the photograph rather than as part of
   it. Blurring what is already behind it keeps the frame whole, and
   the control still reads as a control because of the hairline and
   the solid button inside it.

   THE INPUT TEXT IS WHAT PAYS FOR THIS. It is now white over
   footage rather than dark over a panel, so it depends on the scrim
   like every other string in the hero — which is why the blur is
   backed by a tint rather than being blur alone. Measured at the
   glyph over the placeholder poster, the typed value holds 8.69:1
   and the placeholder 6.41:1 against a 4.5:1 bar; see the table over
   --hero-scrim-wash for the method and the narrow-viewport figures.
   If you take the tint out, re-measure — blur on its own does
   nothing for contrast over a light frame, it only softens the edges
   of what is already there.

   The backdrop-filter is progressive. Without support the tint alone
   is left, which is a darker pane rather than a broken one. */
.offer-form--hero .offer-form__control {
  /* Transparent, not removed: the 1px keeps the control's geometry
     exactly as it was while the form around it carries the frost. */
  background: transparent;
  border-color: transparent;
  box-shadow: none;
}

/* Reversed out, like everything else in this hero. */
.offer-form--hero .offer-form__input {
  color: var(--color-overlay-text);
}
.offer-form--hero .offer-form__input::placeholder {
  color: var(--color-overlay-fg);
}
.offer-form--hero .offer-form__icon {
  color: var(--color-overlay-fg);
}

/* Field and button share a row once there is width for it. Below
   this the button drops under the field and fills it. */
@media (min-width: 768px) {
  /* 24px of gutter against a full bleed photograph leaves the copy
     hugging the edge once the viewport is this wide. */
  .hero-offer__inner { padding-inline: calc(var(--space-7) + var(--clip-inset-max, 0px)); }

  .offer-form--hero .offer-form__control { flex-direction: row; align-items: center; }
  .offer-form--hero .offer-form__field   { flex: 1; min-width: 0; }
  .offer-form--hero .offer-form__control .btn { flex: 0 0 auto; }
}


/* ---- the closing variant --------------------------------------- */

/* Inset, not raised. The plate around it is already the lifted
   object, so a second shadow here would give the section two
   things floating at once. bg-primary under the panel's pinned
   dark theme is gray-950 — one step below the darkest part of the
   plate's own gradient, which is what makes the field read as cut
   into the surface rather than laid on top of it. */
.offer-form--claim { margin-top: var(--space-5); }

.offer-form--claim .offer-form__control {
  background: var(--color-bg-primary);
  border-color: var(--color-border-default);
}

/* 640, not 768. The hero's copy column is capped at 34rem and the
   row only fits past 768; this one has the whole panel width on a
   tablet, so it can go inline a breakpoint earlier. */
@media (min-width: 640px) {
  .offer-form--claim .offer-form__control { flex-direction: row; align-items: center; }
  .offer-form--claim .offer-form__field   { flex: 1; min-width: 0; }
  .offer-form--claim .offer-form__control .btn { flex: 0 0 auto; }
}

/* ============================================================
   9 · CLOSING OFFER PANEL
   ------------------------------------------------------------
   A photograph and a card laid over it. The card straddles the
   photo's edge rather than sitting beside it, which is the whole
   idea: two panels side by side read as two things, one card
   overlapping a picture reads as one object with depth.

   The plate carries data-theme="dark" in the markup, so every
   token inside it resolves to its dark value whichever theme the
   page is set to. That is deliberate and it is the opposite of
   what the cards above do. The cards are light islands because
   they hold content you read through; this is the last thing
   before the footer and its job is to land, so it is the one
   block on the page that goes darker than the page.
   ============================================================ */
.claim {
  position: relative;
  overflow: hidden;                       /* the photo takes the plate's
                                             corners, so it has to be clipped
                                             by them */
  border-radius: var(--claim-radius);
  color: var(--color-text-primary);

  /* Two layers, and a frame of the clip covers both of them. The
     linear is the plate:
     gray-800 down to gray-900, which separates it from the
     gray-950 page without needing an edge. The radial on top is
     the light falling into the corner the card sits in.
     --glow-mid is the brand tinted bloom the hero's amount
     already uses, at 22%, so the plate picks up the client's hue
     instead of being a neutral box. */
  background:
    radial-gradient(120% 90% at 100% 0%, var(--glow-mid) 0%, transparent 62%),
    linear-gradient(160deg, var(--color-bg-tertiary) 0%, var(--color-bg-secondary) 58%);
  /* Nothing above is visible once a frame lands — the photograph
     covers the plate at every width now. It is the ground the
     video loads onto, and the ground the phone layout shows above
     the card if the clip is ever swapped for a shorter file. */
}

/* The lip. Inset rather than a border so it does not take a pixel
   off the photo's edge, and top only — a hairline all the way
   round reads as a stroked box, one along the top reads as light.
   Above the card, so the highlight is not cut in half where the
   card reaches the plate's top corner. */
.claim::after {
  content: "";
  position: absolute;
  inset: 0;
  z-index: 2;
  border-radius: inherit;
  box-shadow: inset 0 1px 0 var(--claim-lip);
  pointer-events: none;
}

/* ---- the footage ----------------------------------------------- */

/* A band across the top here, the whole plate at 1024. Sized the
   same whether the child is an <img> or a <video> — the rule below
   covers both. */
.claim__media {
  position: relative;

  /* Explicit, not the block default. A box carrying both an
     aspect-ratio and a max-height resolves the clamp by taking
     width off instead of height unless the width is definite —
     at 900px the band came out 651px wide inside an 868px plate,
     with the ratio preserved and a quarter of the plate left
     bare. Pinned to 100%, the clamp lands on the height and
     object-fit below crops the difference, which is the intent. */
  width: 100%;

  /* 4:3, not a wider strip. The card overlaps the bottom 56px of
     it, so the ratio has to buy back what the overlap takes —
     16:11 left 180px of photograph showing on a 390px phone,
     which is a letterbox, not a picture. */
  aspect-ratio: 4 / 3;

  /* The ratio alone is a phone rule. At 900px the same ratio is
     600px of photograph before the offer is reachable, so the
     height caps and the ratio gives way — object-fit below crops
     it. A cap rather than a second ratio at a breakpoint: it is
     one number and it holds at every width in between. */
  max-height: 22rem;                      /* 352px */
}

.claim__media img,
.claim__media video {
  width: 100%;
  height: 100%;
  object-fit: cover;
}

/* Same aim as the hero, so both crops of the one clip frame the same
   point. The phone crop is the tight one — a 4:3 band taken out of
   landscape footage loses the sides — which is why the framing is a
   token and not a number typed in twice. */
.claim__poster,
.claim__media video {
  object-position: var(--hero-focal);
}
/* The poster <img> lies under the video (2026-10-23), as in the hero:
   pinned to the figure, with the video positioned so it paints over it
   once it has a frame and see-through until then. The plate colour moved
   to the picture, for the moment before the file lands. */
.claim__poster {
  position: absolute;
  inset: 0;
  display: block;
  background: var(--color-bg-tertiary);   /* the plate, until the picture lands */
}
.claim__media video { position: relative; }

/* A vignette, not a legibility device — see the chip below, which
   carries its own ground. Top weighted, stopping at 42%, so the
   plate's top corners and the lip highlight along them have
   something to sit against whatever the photograph is doing up
   there, and the rest of the picture is untouched. */
.claim__veil {
  position: absolute;
  inset: 0;
  background: linear-gradient(to bottom, var(--card-panel) 0%, transparent 42%);
  pointer-events: none;
}

/* ---- the card that overlaps it ---------------------------------- */

/* The negative top margin is the overlap. It pulls the card up
   onto the bottom of the photograph, so the two are one stacked
   object rather than a picture with a box under it. On a desktop
   the same job is done by absolute placement.

   --card-panel again, and for the third time the same reason: it
   is the one ground on this page measured to hold text over a
   photograph nobody has vetted. The blur is what makes it read
   as glass rather than as a hole cut in the picture, and
   --lift-lg is the black tinted shadow meant for exactly this —
   an object floating on a photo. */
.claim__card {
  position: relative;
  z-index: 1;
  /* Flush left, right and bottom. Inset by --space-3 the card left a
     band of bare plate down both sides and along the floor, which
     read as a box dropped on the picture; taking it to the edges
     is what makes the bottom of the plate the card. Only the top
     margin is left, and it is the overlap.

     The bottom corners are --claim-radius, not --radius-lg: the
     card's edge IS the plate's edge here, so its corners have to
     be the plate's corners or the plate clips a square one. */
  margin: calc(-1 * var(--space-8)) 0 0;
  padding: var(--space-5) var(--space-4) var(--space-6);
  border: 1px solid var(--card-panel-edge);
  border-radius: var(--radius-lg) var(--radius-lg)
                 var(--claim-radius) var(--claim-radius);
  background: var(--card-panel);
  -webkit-backdrop-filter: blur(1.25rem);
  backdrop-filter: blur(1.25rem);
  box-shadow: var(--lift-lg);
}

.claim__title { margin-bottom: var(--space-3); }
/* Centred on a phone (Brandon, 2026-11-04), over the full-width field
   and button; balanced lines keep the two halves even. */
@media (max-width: 767px) {
  .claim__title { text-align: center; }
}

/* The amount is colour and weight, not a size jump and not a
   second glow. The hero already spends a breathing bloom on this
   number; doing it twice on one page turns a highlight into a
   tic. text-accent is the 300 step in dark, so it stays legible
   on the card whatever the client's secondary hex is.

   nowrap because "[10% off]" breaking across two lines is the one
   thing in the headline that must not happen. */
.claim__amount {
  white-space: nowrap;
  color: var(--color-text-accent);
  font-weight: var(--fw-bold);
}

/* ============================================================
   RAIL HEADER + ARROWS
   A rail's affordance on a phone is the cut off card plus the
   swipe. With a mouse the cut off card is still there but the
   gesture is not, so the arrows carry it — and they are the
   keyboard route as well. Tab still reaches every card link on
   its own (focusing an offscreen link scrolls it into view), so
   these are an improvement on the interaction, not the only way
   through it.
   ============================================================ */
/* .rail-head and its intro went with the stays rebuild — that
   section's header is .stays__head now and it is left aligned, for
   the reasons written over it. .rail-actions stayed: the call to
   action under the rail is still there and still centred. */
.rail-actions { text-align: center; }

/* LIFTED OVER THE GLOW, like .stays__inner and .stays__rail (Cabin
   Collective, 2026-10-15). The glow is positioned at z-index 0, so a
   static .rail-actions painted under it, and once the glow went to a
   55% blurred photograph and tint the button came out dimmed. */
.section--stays .rail-actions {
  position: relative;
  z-index: 1;
}

/* Hidden on phones: the swipe is the obvious gesture there, and
   two more tap targets in the header would only crowd it. */
.rail-nav { display: none; }

/* Needed because the desktop rule sets display:flex, which beats
   the browser's own [hidden] styling on specificity. script.js
   sets the attribute when the rail has nothing left to scroll.

   One class, and it has to keep winning: [hidden] is (0,2,0) and
   every rule that turns a nav on below is a single class at
   (0,1,0), so "the rail has nothing to scroll" always beats "this
   breakpoint shows arrows". Add a two-class selector that turns a
   nav on and you break that. */
.rail-nav[hidden] { display: none; }

/* CENTRED UNDER ITS RAIL rather than hung beside a heading, because
   both headers that use it are centre aligned and arrows off to one
   side would be the only thing in the block that is not. Reviews
   and Featured Stays both wear it; Stays' nav used to sit in the
   section header, which is why the header went two-column at
   1024px, and neither is true any more.

   GATED ON A POINTER, NOT ON A WIDTH. It replaced the reviews'
   self-scrolling animation, and that animation ran wherever there
   was a mouse, including in a 900px-wide window; gating on width
   instead would leave a narrow desktop window with neither the
   animation it used to have nor the arrows that replaced it. A
   touchscreen gets no arrows and swipes the row, as before — which
   is also the behaviour Stays' nav had from its own display: none
   base rule, so moving it here changed nothing on a phone. */
.rail-nav--center { display: none; }

@media (hover: hover) and (pointer: fine) {
  .rail-nav--center {
    display: flex;
    justify-content: center;
    gap: var(--space-3);
    margin-top: var(--space-5);
  }
}

.rail-nav__btn {
  display: grid;
  place-items: center;
  width: 3rem;
  height: 3rem;
  padding: var(--space-0);
  /* Strong, not default, unlike .btn--outline. That button is
     identified by its text label, so a soft edge costs it
     nothing. This one is a bare glyph, so the ring is what says
     "control" — and WCAG 1.4.11 wants 3:1 for that. Default
     measures 2.52:1 on the dark ground; strong measures 3.79:1. */
  border: 1px solid var(--color-border-strong);
  border-radius: 50%;
  background: transparent;
  color: var(--color-text-primary);
  cursor: pointer;
  touch-action: manipulation;
  transition: background-color var(--dur-ui) ease,
              border-color var(--dur-ui) ease,
              opacity var(--dur-ui) ease,
              transform var(--dur-press) var(--ease-out);
}
.rail-nav__btn svg { width: 1.25rem; height: 1.25rem; }
.rail-nav__btn:active { transform: scale(0.94); }

/* Dimmed rather than removed. A control that disappears at the
   end of the rail takes its neighbour's position with it, and
   the pair jumping sideways mid-interaction is worse than a
   button that is visibly spent. */
.rail-nav__btn[disabled] {
  cursor: default;
  opacity: 0.35;
  color: var(--color-text-disabled);
  border-color: var(--color-border-subtle);
}

@media (hover: hover) and (pointer: fine) {
  .rail-nav__btn:not([disabled]):hover {
    background: var(--color-bg-tertiary);
    border-color: var(--color-border-strong);
  }
}

/* ============================================================
   SLIDERS — swipe on phones, tidy rows on desktop
   Used by: Featured Stays, Amenities, Reviews
   ============================================================ */
.slider { position: relative; }

.slider__track {
  display: flex;
  gap: var(--space-3);
  overflow-x: auto;
  scroll-snap-type: x mandatory;
  scroll-padding-left: var(--container-x);
  scroll-behavior: smooth;
  padding: var(--space-0) var(--container-x) var(--space-4);
  scrollbar-width: none;
  -ms-overflow-style: none;
}
.slider__track::-webkit-scrollbar { display: none; }
/* "none start", not "start". The one word shorthand sets BOTH
   axes, so every card in every rail was quietly declaring itself
   a vertical snap position as well as a horizontal one. That
   costs nothing while the page does not snap vertically, which it
   no longer does — but it cost plenty while it did: scrolls
   ending anywhere near the foot of the page jumped a couple of
   hundred pixels to land on a card. Kept explicit so the next
   thing to turn on vertical snapping does not inherit the same
   surprise. Block axis off, inline axis start. */
.slider__track > * { scroll-snap-align: none start; flex: 0 0 auto; }

/* ============================================================
   5 · SELECTED STAYS
   ------------------------------------------------------------
   One horizontal rail of portrait cards that deliberately runs
   off the right edge of the screen, under a left aligned
   heading, with a drawn scrollbar under it and a wash of the
   hovered card's photograph behind the whole thing.

   PINNED DARK, on a brand-950 ground. The section carries
   data-theme="dark" in the markup, so every token inside it resolves
   to its dark value whatever the page is set to: the heading and the
   line under it go light, and the card scrims compose the dark ink
   triplet — a dark gradient at the foot of each photograph with light
   type and a light-on-dark pill sitting on it. That has been the
   template's call since 2026-09-22, folded back from the first client
   build off it: the pale wash the light theme painted on a photo card
   read as a haze over the pictures.

   THE GROUND IS THE DARKEST BRAND STEP, not --color-bg-primary, which
   under the dark scope would be the neutral gray-950. brand-950 is the
   same near-black with the brand hue still in it, so the band
   belongs to the brand rather than to the template — the same choice
   the footer makes, and the two now match.
   ============================================================ */
.section--stays {
  position: relative;
  isolation: isolate;
  overflow: hidden;
  background: var(--brand-950);

  /* Fills the screen, and centres what is in it. The rail is the
     only thing in the section and a rail floating in the middle of
     a much taller box reads as unfinished. min-height rather than
     height so a long property name can still grow the section. */
  min-height: 100svh;
  display: flex;
  flex-direction: column;
  justify-content: center;
  padding-block: clamp(var(--space-6), 5vh, var(--space-9));
}

/* ---- the glow --------------------------------------------------
   Two layers and a tint. script.js paints the hovered card's
   picture onto whichever layer is behind, then swaps which one is
   at full opacity — so moving between cards crossfades rather than
   cuts. The blur is what turns a photograph into light.

   Hidden by default in BOTH axes: opacity for the fade and
   visibility so it is out of the way entirely when off. Without
   JavaScript nothing ever sets the images, so this stays empty and
   invisible forever, which is the correct fallback.
------------------------------------------------------------------ */
.stays__glow {
  position: absolute;
  inset: 0;
  z-index: 0;
  overflow: hidden;
  opacity: 0;
  visibility: hidden;
  pointer-events: none;
  transition: opacity var(--dur-crossfade) var(--ease-out),
              visibility var(--dur-crossfade);
}
.stays__glow.is-on {
  opacity: var(--stay-glow-opacity);
  visibility: visible;
}

/* inset is negative so the blur has material to work with past the
   edges — a blurred layer sized to its box fades to transparent at
   the corners and prints a visible vignette. */
.stays__glow-layer {
  position: absolute;
  inset: -14%;
  background-size: cover;
  background-position: 50% 50%;
  filter: blur(var(--stay-glow-blur)) brightness(0.6) saturate(1.06);
  transform: scale(1.15);
  opacity: 0;
  transition: opacity var(--dur-reveal) var(--ease-out);
}
.stays__glow-layer.is-front { opacity: 1; }

.stays__glow-tint {
  position: absolute;
  inset: 0;
  background: var(--stay-glow-tint);
}

/* A hairline along the top edge, drawn on a phone only — see the
   media query at the end of this block. */
.stays__rule {
  position: absolute;
  top: 0; left: 0; right: 0;
  z-index: 1;
  display: none;
  height: 2px;
  background: linear-gradient(90deg,
    transparent, var(--color-border-strong) 18%,
    var(--color-border-strong) 82%, transparent);
  pointer-events: none;
}

/* THE FOOT, the seam with Local Favourites below (2026-11-01), drawn at
   every width. The band and the page's ground used to meet on a bare
   cut. This closes the band the way the offer and reviews bands close,
   on the page's one divider: the accent hairline, fading out at 18%
   and 82%. A shaped edge was tried here (an arc) and taken out, because
   the template has to suit every client's brand, and a curve brings a
   shape the brand may not have; a straight line in the client's own
   accent brings nothing but their colour. */
.stays__rule--bottom {
  top: auto;
  bottom: 0;
  display: block;
  background: linear-gradient(90deg,
    transparent, var(--color-border-accent) 18%,
    var(--color-border-accent) 82%, transparent);
}

/* ---- the header ------------------------------------------------ */
/* LEFT ALIGNED, and aligned to the same gutter the row starts at.
   The row runs off the right edge of the screen, so its only
   readable edge is the left one — a centred heading over it would
   share no edge with anything. */
.stays__inner {
  position: relative;
  z-index: 1;
  width: 100%;
  max-width: var(--container-max);
  margin-inline: auto;
  padding-inline: var(--container-x);
}

.stays__head { margin-bottom: clamp(var(--space-3), 2.6vh, var(--space-5)); }

.stays__eyebrow {
  color: var(--color-text-accent);
  margin-bottom: var(--space-3);
}

.stays__title {
  color: var(--color-text-primary);
  margin: 0;
}
.stays__title em {
  font-style: normal;         /* upright, colour only — see .hero-offer__title em */
  color: var(--color-text-accent);
}

.stays__desc {
  margin-top: clamp(var(--space-2), 2vh, var(--space-3));
  max-width: 33rem;
  color: var(--color-text-secondary);
}

/* ---- the rail -------------------------------------------------- */
.stays__rail {
  position: relative;
  z-index: 1;
  /* Room under the drawn bar. The reference ends the section on the
     bar; this template keeps a call to action under it, and a 2px
     rule sitting directly on top of a button reads as part of it. */
  margin-bottom: var(--space-6);
}

/* THE ROW RUNS OFF THE EDGE ON PURPOSE.
   It starts at the container's left gutter and is not capped on the
   right, so the last visible card is always cut — which is the only
   honest way to say "there is more" without drawing a control that
   says it. The mask is the polish on that: the cut edge fades
   instead of ending on a hard vertical line.

   --fade-r is switched to 0 by script.js once the row is scrolled to
   the end, because a fade still sitting there when there is nothing
   left to reach is a lie about the content.

   scroll-padding-left keeps a snapped card off the screen edge: the
   row's own padding is the container gutter, and without this a
   snap would put the card's left edge flush against the viewport. */
.stays__row {
  --gap: clamp(var(--space-3), 2vw, var(--space-4));
  --edge-fade: clamp(var(--space-4), 5vw, var(--space-7));
  --fade-l: 0px;
  --fade-r: var(--edge-fade);

  position: relative;
  display: flex;
  gap: var(--gap);
  overflow-x: auto;
  scroll-snap-type: x proximity;
  -webkit-overflow-scrolling: touch;
  scrollbar-width: none;
  padding: var(--space-2) 0 var(--space-5) max(var(--container-x), calc((100% - var(--container-max)) / 2 + var(--container-x)));
  scroll-padding-left: max(var(--container-x), calc((100% - var(--container-max)) / 2 + var(--container-x)));
  -webkit-mask-image: linear-gradient(to right,
    transparent 0, #000 var(--fade-l),
    #000 calc(100% - var(--fade-r)), transparent 100%);
          mask-image: linear-gradient(to right,
    transparent 0, #000 var(--fade-l),
    #000 calc(100% - var(--fade-r)), transparent 100%);
}
.stays__row::-webkit-scrollbar { display: none; }

/* ---- the drawn scrollbar --------------------------------------- */
/* The native bar is hidden above and this is drawn instead, for one
   reason: the native one is a different object on every platform and
   on a Mac it is not there at all until you scroll. A rail that runs
   off the edge needs something permanently visible saying how far
   along it you are.

   IT IS A POINTER AFFORDANCE AND NOTHING ELSE, which is what
   role="presentation" in the markup says. The keyboard path through
   this rail is Tab: every card is a link, they are in DOM order, and
   focusing one that is off screen scrolls it into view. The row
   itself is NOT focusable — it carries no tabindex, and giving a
   scroll container one when it already holds focusable children adds
   a tab stop that lands on nothing.

   Worth knowing what that replaced: the old rail had a pair of arrow
   buttons under it, which were operable by keyboard. They are gone,
   and the reference this was rebuilt from never had them. If the
   arrows are wanted back, .rail-nav--center is still in this file,
   still styled, and still driven by script.js — the reviews rail
   uses it. */
.stays__bar {
  position: relative;
  margin: var(--space-1) auto 0;
  width: min(100% - var(--container-x) * 2, var(--container-max) - var(--container-x) * 2);
  height: 2px;
  border-radius: var(--radius-pill);
  background: var(--color-border-subtle);
  cursor: pointer;
  touch-action: none;
  /* HIDDEN UNTIL THE SCRIPT HAS MEASURED. Nothing here can position
     the thumb, so without JavaScript this would be a full width track
     with a 64px thumb stuck at the left — a control that looks broken
     rather than one that is simply absent. script.js turns it visible
     in measure(), and turns it back off when everything already fits
     and there is nothing to scroll. */
  visibility: hidden;
}

.stays__thumb {
  position: absolute;
  top: 50%;
  left: 0;
  height: 2px;
  width: 4rem;                            /* replaced by script.js */
  border-radius: var(--radius-pill);
  background: var(--color-bg-brand-solid);
  transform: translateX(0);
  translate: 0 -50%;
  cursor: grab;
  touch-action: none;
  will-change: transform, width;
}
.stays__thumb:active { cursor: grabbing; }

/* ---- the card ---------------------------------------------------
   A PHOTOGRAPH WITH A PANEL ON IT, not a photograph with a caption
   under it. The card used to be a square picture over a white
   block carrying the name, a bed count and an arrow disc; it is one
   portrait frame now, filled edge to edge by the photograph, with
   the name and the button sitting on the bottom of the picture
   behind a gradient.

   That is the whole reason for every rule below. There is no solid
   surface any more, so the card no longer carries data-theme="light"
   in the markup — everything in it sits over a picture, which is why
   the type here uses the overlay tokens rather than the text ones.
   Those tokens follow the theme (dark ink on a light page, light ink
   on a dark one), so the card needs no attribute of its own. If you
   put the solid block back, give it a theme attribute again.
------------------------------------------------------------------ */
.stay-card {
  position: relative;
  flex: 0 0 auto;

  /* SIZED BY HEIGHT, with the width following from the ratio. The
     row is horizontal, so height is the dimension that has to agree
     with the viewport and width is the one that can be whatever the
     picture needs. 60vh keeps the card a constant share of the
     screen between the two bounds; the bounds stop it becoming a
     postage stamp on a laptop or a poster on a tall monitor. */
  height: clamp(23.75rem, 60vh, 35rem);   /* 380px - 560px */
  aspect-ratio: 3 / 4;

  border-radius: var(--stay-radius);
  /* --default, not --subtle. The card's ground and the section's are
     the same token, so a subtle border is invisible between them —
     and the border is what gives the photograph an edge on the two
     sides the scrim never reaches. It has to be a step LIGHTER than
     the section, not a step darker. */
  border: 1px solid var(--color-border-default);
  overflow: hidden;
  isolation: isolate;                     /* keeps the scrim off the page stack */
  scroll-snap-align: start;
  background: var(--color-bg-secondary);  /* the ground until the photo lands */
  box-shadow: var(--stay-lift);

  /* The panel is pushed to the bottom by the column rather than
     positioned there, so a two line property name grows upward into
     the picture instead of off the bottom edge of the card. */
  display: flex;
  flex-direction: column;
  justify-content: flex-end;
  padding: var(--space-3);
}

/* Held at 1.02 rather than 1, so the zoom on hover has somewhere to
   come from and the edges never expose the card's ground mid
   transition. 1.4s is a long transition by this page's standards and
   is meant to be: it is a camera push on a photograph, not a UI
   state change, and at UI speed it reads as a twitch.

   --stay-focal is set per card in the markup, the same way as
   --offer-focal (style="--stay-focal: 50% 80%"). A tall photo in the
   3:4 desktop card loses part of its height to the crop, and a house
   that sits low in its frame ends up behind the name panel when the
   crop is centred. */
.stay-card__img {
  position: absolute;
  inset: 0;
  width: 100%;
  height: 100%;
  object-fit: cover;
  object-position: var(--stay-focal, 50% 50%);
  border-radius: inherit;
  transform: scale(1.02);
  transition: transform var(--dur-push) var(--ease-out);
}

/* THE PARALLAX (from the Arca build, 2026-10-31). script.js writes
   --stay-drift on the row, -1 as the section comes up from under the
   fold to 1 as it leaves over the top, and the photograph rides it
   12.5% of the card's height either way, so it moves a little slower
   than the page. Arca ran it at 6% for a day and nobody could see it:
   most of a linear pass is spent with the card half off the screen,
   so while a card was fully in view its picture moved about 10px
   across a screen of scrolling.

   The picture is cut 25% taller than the card, 12.5% past each edge,
   so the travel never shows the card's ground at either end of it. The
   percentage in translate is of the image's own height, which is 125%
   of the card's: 12.5 / 125 = 10%. translate is a property of its own
   rather than part of transform, so the hover zoom's 1.4s transition
   above does not tween the scroll into a lag. More travel than this
   means a tighter crop and a softer picture: the ingest cuts stays
   1200px tall, which the 25% leaves at about 1.7x on a 560px card.

   Behind .reveal-on like every other scroll effect: a reader who asked
   for less motion, or a browser the script cannot drive, gets the
   still crop at the card's own height. -1 is the fallback because it
   is where a row below the fold belongs, so nothing moves when the
   script's first answer arrives. */
.reveal-on .stay-card__img {
  top: -12.5%;
  height: 125%;
  translate: 0 calc(var(--stay-drift, -1) * 10%);
}

/* TWO GRADIENTS, AND BOTH ARE DOING A JOB.
   The first is the contrast: a vertical ramp that is nothing across
   the top two thirds of the picture and near solid where the panel
   sits, so the name and the button have something to be read
   against without the photograph being darkened as a whole.

   The second is the light: a soft diagonal sheen that catches the
   top left corner and falls away. It is what stops the card reading
   as a photograph with a black bar on it — it gives the frame an
   edge and a direction, the way a print has. Take it out and the
   card goes flat immediately. */
.stay-card__scrim {
  position: absolute;
  inset: 0;
  z-index: 1;
  border-radius: inherit;
  background:
    linear-gradient(to bottom,
      var(--stay-scrim-0)   30%,
      var(--stay-scrim-1)   52%,
      var(--stay-scrim-2)   74%,
      var(--stay-scrim-3)   92%,
      var(--stay-scrim-4)  100%),
    linear-gradient(140deg,
      var(--stay-sheen-1)    0%,
      var(--stay-sheen-0)   45%,
      var(--stay-sheen-2)  100%);
}

.stay-card__panel {
  /* NO position HERE, and it is load bearing. The button's ::after is
     what makes the whole card clickable, and an absolutely positioned
     box resolves against its nearest POSITIONED ancestor — so the
     moment this box is positioned, that overlay shrinks from the card
     to the panel and the top two thirds of the photograph stop being
     a link. z-index works without it: this is a flex item of the
     card, and flex items take z-index while staying static. */
  z-index: 2;
  width: 100%;
  display: flex;
  flex-wrap: wrap;
  align-items: center;
  gap: var(--space-3) var(--space-4);
  padding: var(--space-3) var(--space-2);
}

/* min-width is what makes the wrap happen at the right moment. The
   text block refuses to be squeezed below a readable measure, so on
   a narrow card the button drops to its own line instead of the
   property name being hyphenated down to one word a line. */
.stay-card__text {
  flex: 1 1 0;
  min-width: 13rem;
  display: flex;
  flex-direction: column;
  align-items: flex-start;
  gap: var(--space-2);
  text-align: left;
}

.stay-card__name {
  font-family: var(--font-display);
  font-size: var(--fs-display-xs);
  line-height: var(--lh-display-xs);
  letter-spacing: var(--ls-tight);
  font-weight: var(--fw-medium);
  color: var(--color-overlay-text);
  text-shadow: var(--stay-text-shadow);
}

/* Uppercase and widely letterspaced, which is what makes a line this
   small read as a specification rather than as a sentence. --ls-wider
   is 0.2em and this is 14px type, so the tracking lands at 2.8px.

   It is the one string in the card allowed to be quieter than white —
   it is a label on the name above it, not information anybody is
   hunting for. Measured over the scrim's plateau it still holds
   10.33:1, well past the 4.5:1 bar; see --stay-scrim-0 for the
   method and the other two figures. */
.stay-card__guests {
  font-family: var(--font-body);
  font-size: var(--fs-text-sm);
  line-height: var(--lh-text-sm);
  letter-spacing: var(--ls-wider);
  text-transform: uppercase;
  color: var(--color-overlay-fg);
  text-shadow: var(--stay-text-shadow);
}

/* THE BUTTON IS THE WHOLE CARD. The ::after below stretches to the
   card's edges, so a click anywhere on the picture follows this
   link — which is why the card is an <article> with one link in it
   rather than a giant <a> wrapping a heading. Nesting the name
   inside the link would make a screen reader read the property twice
   and would stop the h3 being a heading it can navigate to.

   The card is the ::after's containing block because the card is the
   nearest positioned ancestor. If you ever give this button its own
   position, the overlay collapses to the button and the rest of the
   card stops being clickable. */
.stay-card__btn {
  flex: 0 0 auto;
  display: inline-flex;
  align-items: center;
  justify-content: center;
  padding: var(--space-2) var(--space-3);
  border-radius: var(--radius-pill);
  background: var(--stay-btn-bg);
  border: 1px solid var(--color-overlay-border);
  font-family: var(--font-body);
  font-size: var(--fs-text-xs);
  line-height: var(--lh-text-xs);
  color: var(--color-overlay-text);
  white-space: nowrap;
  /* NO backdrop-filter, and this is the trap that cost an hour.
     A backdrop-filter — like filter, transform, contain and
     will-change — makes an element a CONTAINING BLOCK for absolutely
     positioned descendants. Blurring this pill therefore re-anchored
     the ::after below to the pill itself, which silently shrank the
     card's click target from the whole photograph to an 87x34 button
     and left the comment above this one describing something that
     was no longer true.

     The tint alone carries the look; a translucent background creates
     no containing block. If you ever want the frost back, the overlay
     has to move to a different element first. */
  transition: background var(--dur-ui) var(--ease-out),
              border-color var(--dur-ui) var(--ease-out);
}
.stay-card__btn::after {
  content: "";
  position: absolute;
  inset: 0;
  border-radius: inherit;
}
/* The label flips to the on-solid ink with the fill. Under the dark
   scope the solid is brand-400, a light blue, and the overlay text the
   pill rests in is white — white on that measures about 2:1. On a light
   page the same rule was putting near-black overlay ink on brand-700,
   which was just as wrong the other way. --color-text-on-solid is the
   token that already knows which ink sits on the solid in each theme. */
.stay-card__btn:hover {
  /* The same --btn-* set every filled button on the page uses, so a
     build that changes the button fill changes this with it. */
  background: var(--btn-fill);
  border-color: var(--btn-fill);
  color: var(--btn-ink);
}

/* The focus ring has to be drawn on the CARD, not on the button.
   The button is a 100px pill in the corner but its hit area is the
   whole card, so ringing the pill would put the outline somewhere
   the keyboard user is not actually about to activate. */
/* Both halves are inside the @supports, and that is the point. The
   ring is MOVED from the button to the card, so taking it off the
   button unconditionally would leave a browser without :has() with no
   focus indicator at all — the ring would be removed from the one
   element that could still draw it. Where :has() is missing, neither
   rule applies and the button keeps its own default ring. */
@supports selector(:has(*)) {
  .stay-card:has(.stay-card__btn:focus-visible) {
    outline: 2px solid var(--color-border-focus);
    outline-offset: 3px;
  }
  .stay-card__btn:focus-visible { outline: none; }
}

/* The arrow is the phone's version of this button and is not drawn
   until the media query below asks for it. */
.stay-card__btn-arrow { display: none; }

/* The push on hover, and the pointer test is the whole gate: a
   touchscreen has no hover state, and without this the zoom fires on
   tap and stays there. */
/* The no-preference guard is in the QUERY, not in a later override.
   A reduced-motion block would have to out-specify `.stay-card:hover
   .stay-card__img`, and a media query adds no specificity — so the
   plain `.stay-card__img { transform: none }` that used to sit in the
   reduce block below lost to this rule and a reader who asked for
   less motion still got the zoom. Gating the query is the pattern
   the rest of this file already uses seven times over. */
@media (hover: hover) and (pointer: fine) and (prefers-reduced-motion: no-preference) {
  .stay-card:hover .stay-card__img { transform: scale(1.07); }
}

/* ---- the phone ---------------------------------------------------
   A CAROUSEL, NOT A RAIL. Below 640px the row stops being something
   you drag past and becomes one card at a time: the snap goes from
   proximity to mandatory.

   IT STAYS LEFT ALIGNED. The card used to be centred in the snapport
   with a sliver of both neighbours showing, which left the first card
   starting somewhere around 15vw in and sharing no edge with the
   heading above it. Everything in this section now starts on the same
   line — the --container-x gutter, 16px — the header, the first card,
   and every card a snap lands on. Only the right edge is cut, and the
   next card peeking past it is what says there is more.

   The card also stops being a fixed height and stretches to the row
   instead, so the section fills the screen rather than leaving a band
   of ground under a 380px card.
------------------------------------------------------------------- */
@media (max-width: 640px) {
  .section--stays {
    min-height: 0;
    height: 100svh;
    padding-block: var(--space-9);
  }

  /* Only drawn here. On a desktop the section's own ground against
     the section above it is separation enough; on a phone the rail
     fills the screen and the two grounds meet with nothing between
     them. */
  .stays__rule { display: block; }

  /* The rail takes the height the header does not, so the card can
     stretch into it. */
  .stays__rail {
    flex: 1 1 auto;
    min-height: 0;
    display: flex;
    flex-direction: column;
    /* Tighter than the desktop's 40px. Together with the row's smaller
       bottom pad this hands about 48px back to the card, which stretches
       to fill it — the gap to CHECK AVAILABILITY was reading as dead
       ground. */
    margin-bottom: var(--space-4);
  }

  /* The header keeps the desktop's left alignment — eyebrow, title and
     the line under it all start on the gutter the cards start on. It
     is .stays__inner's padding-inline that puts it there, so there is
     nothing to set here beyond the tighter eyebrow gap.

     The centred block used to ask for text-wrap: balance here. It is
     gone rather than swapped: every <p> now gets text-wrap: pretty
     from _template.css, and script.js binds the last three words on
     top of that, so saying it again in this one place would only
     suggest the rule is local when it is not. */
  .stays__eyebrow { margin-bottom: var(--space-2); }

  /* The description goes on a phone. The section is one screen tall
     here and the card stretches into whatever the header leaves, so
     four lines of body copy were coming straight out of the card's
     height. The eyebrow and title still say what the row is. */
  .stays__desc { display: none; }

  .stays__row {
    flex: 1 1 auto;
    min-height: 0;
    align-items: stretch;
    /* The left pad IS the gutter, and scroll-padding-left repeats it so
       a snapped card lands on that same line rather than flush against
       the screen edge. The right pad is the last card's breathing room
       at the end of the scroll. */
    /* Bottom pad is only room for the card's shadow; the rail's margin
       above does the separating. */
    padding: var(--space-2) var(--container-x) var(--space-2);
    scroll-snap-type: x mandatory;
    scroll-padding-left: var(--container-x);
    /* No mask. --edge-fade is 24px at this width and the sliver it
       would be softening is 40px, so the fade would eat most of the
       one thing saying the row carries on. */
    -webkit-mask-image: none;
            mask-image: none;
  }

  .stay-card {
    /* The gutter it starts on, the gap after it, and the 40px sliver of
       the next card, all taken off the screen — so the card is as wide
       as it can be while still leaving that sliver showing. It is the
       sliver, not a mask, that says the row carries on. */
    flex-basis: calc(100vw - var(--container-x) - var(--gap) - 2.5rem);
    height: auto;
    aspect-ratio: auto;
    scroll-snap-align: start;
  }

  /* One row, name left and button right, pinned to the bottom. The
     desktop layout wraps the button under the text on a narrow card;
     here there is no room for that and no need — the button is a
     disc. */
  .stay-card__panel {
    flex-wrap: nowrap;
    align-items: flex-end;
    justify-content: space-between;
    gap: var(--space-3);
    padding-inline: var(--space-2);
  }
  .stay-card__text {
    min-width: 0;
    gap: var(--space-1);
  }
  /* 18/28 on a phone. The 24px desktop rung wrapped a three word name
     onto three lines over a 70vw card. */
  .stay-card__name {
    font-size: var(--fs-text-lg);
    line-height: var(--lh-text-lg);
  }
  .stay-card__guests { white-space: nowrap; }

  /* THE BUTTON BECOMES A DISC. A 100px pill next to a property name
     on a 70vw card leaves the name about nine characters; the disc
     gives it the row. The label is still in the markup and still
     read out — only the drawing changes — and the aria-label on the
     link is what a screen reader announces either way. */
  .stay-card__btn-label { display: none; }
  .stay-card__btn-arrow {
    display: block;
    width: 1rem;
    height: 1rem;
  }
  .stay-card__btn {
    width: 2.5rem;                        /* 40px — a real touch target */
    height: 2.5rem;
    padding: 0;
    border-radius: 50%;
  }

  /* Nothing to drag, and 2px is not a touch target. The row snaps
     card to card here, which is its own position indicator. */
  .stays__bar { display: none; }
}

/* The push and the crossfade are motion for its own sake, so they go
   entirely. _template.css has already zeroed every transition
   duration with !important by this point, which would turn the
   glow's crossfade into a hard cut between photographs every time
   the pointer moved between cards — so the glow is switched off
   rather than left to flash. script.js stands down as well. */
@media (prefers-reduced-motion: reduce) {
  .stay-card__img { transform: none; }
  .stays__glow { display: none; }
}


/* ============================================================
   5 · WHERE YOU'LL STAY  —  the alternative to the stays rail
   One photograph at a time beside a list of what the place has. The
   markup is snippets/stays-highlights.html, to swap in over the rail
   for a client who books everything through one engine; these rules
   and the driver (script.js, WHERE YOU'LL STAY) do nothing until it is
   on a page. First built for Walden Retreats and Gooseberry (folded in
   2026-10-23), reworked on the Dunya build and folded back 2026-11-01.

   Dunya's rework replaced a version that put a dark scrim and white
   type over every photograph, which read as one more photo-card
   section between the deck above and Local Favourites below. This is
   a band of its own: pinned data-theme="dark" on brand-950 under the
   night sky (.sky, the reviews band's ground turned over, the same
   layer the stays rail wears), and the words sit OFF the photographs,
   so no picture needs a scrim to carry them.

   DESKTOP, from 1100px, once script.js has run (.is-staged on the
   grid): one 4:5 photograph on the left, the stage, and beside it the
   heading, the client's summary, the features as a list, the
   facts and the one button. Every feature's name and line is on the
   list at once. Choosing one (a click, the keyboard, or resting the
   pointer on it) wipes its photograph up over the last one, or down
   when the choice is higher up the list, and the bar on the list's
   track glides to it. script.js writes the list from the figcaptions,
   so the captions are the only copy of the words in the markup.

   PHONE, TABLET (an iPad on its side included: at 1024px the column
   beside the frame was 400px of wrapping lines, and a touch screen is
   better served by the swipe), AND ANY WIDTH WITHOUT script.js: the
   photographs
   swipe as a row with the next one showing at the edge, each with its
   name and line underneath; then the facts, two by two, and a
   full-width button. Nothing here needs the script at that size.

   BUILT FOR ANY COUNT of features, three to five reading best: the
   stage stacks however many there are, and the list is written from
   whatever is in the markup.
   ============================================================ */
.stay {
  position: relative;
  isolation: isolate;               /* the .sky layer sits at z-index -1 inside it */
  overflow: hidden;
  background: var(--brand-950);     /* the darkest brand step, as the footer and the rail use */

  /* THE LIFT under the photograph (2026-11-01). --lift-lg is the page's
     lift for a card over a photograph, which this is (the glow is the
     photograph), and the recipe is the same: one long soft layer and
     one short close one, in near-black. On a dark band --lift-lg's 42%
     barely parts the card from the ground, so both layers are darker
     and the long one longer. Near-black, not the brand's 950: that is
     the ground, and a shadow in it would vanish. */
  --stay-lift-stage: 0 1.75rem 4rem -0.5rem rgba(8, 10, 13, 0.62),
                     0 0.25rem 0.75rem rgba(8, 10, 13, 0.38);
}
/* THE GLOW (2026-11-01) is the rail's .stays__glow, unchanged: the
   photograph that is showing, blurred, darkened and tinted, at 55% over
   the sky, so the band takes the colour of whatever is on the frame.
   Its blur, opacity and tint are the --stay-glow-* tokens, already
   tuned for type over brand-950; on Dunya this band's type was
   measured over each of its four photographs. The glow sits at
   z-index 0, so the content steps up over it. */
.stay > .container { position: relative; z-index: 1; }
/* BELOW 1100PX THE GLOW RISES FROM THE FOOT. A phone's band is tall and
   narrow, so the cover-scaled photograph shows nearly whole behind it,
   sky and all, and a bright sky landed right behind the eyebrow and
   the summary: 4.0:1 over one of Dunya's photographs, measured. Faded
   in from the top, the heading keeps the night sky and the
   photograph's colour comes up behind the row, the pills and the
   button. On a desktop only a middle band of the photograph shows and
   the heading cleared 5:1 over all four of Dunya's, so it keeps the
   glow whole. Re-measure over a client's own photographs. */
@media (max-width: 1099px) {
  .stay .stays__glow {
    -webkit-mask-image: linear-gradient(180deg, transparent 12%, #000 50%);
    mask-image: linear-gradient(180deg, transparent 12%, #000 50%);
  }
}
.stay__grid { display: grid; gap: var(--space-6); }

/* The eyebrow in the secondary ink, not the tertiary .eyebrow gives it:
   it is 14px, so small text with a 4.5:1 bar, and the tertiary over the
   glow measured 4.2:1 at its worst pixel on a desktop (the template's
   placeholders, 2026-11-01). Dunya made the same change page-wide. */
.stay__head .eyebrow { color: var(--color-text-secondary); }
.stay__head .heading { margin-bottom: var(--space-4); }
.stay__head .heading em {
  font-style: normal;               /* upright, colour only — see .hero-offer__title em */
  color: var(--color-text-accent);
}
.stay__head .subhead { margin-bottom: 0; }

/* THE ROW: phone, tablet, and the fallback. */
.stay__frames {
  display: flex;
  gap: var(--space-3);
  overflow-x: auto;
  scroll-snap-type: x mandatory;
  /* Snap to the CONTENT box, not the scrollport. Without this the first
     card snaps flush to the screen edge on load, because the padding
     below is inside the scrollport and snapping ignores it. */
  scroll-padding-inline: var(--container-x);
  -webkit-overflow-scrolling: touch;
  scrollbar-width: none;
  margin: 0 calc(-1 * var(--container-x));      /* bleeds to the screen edge, like the other rails */
  padding: 0 var(--container-x);
  /* Room for the photographs' lift. A scroll container clips what hangs
     out of it, and the shadow hangs above and below the cards; the
     negative margin gives the room back, so nothing moves. */
  padding-block: var(--space-3) var(--space-5);
  margin-block: calc(-1 * var(--space-3)) calc(-1 * var(--space-5));
}
.stay__frames::-webkit-scrollbar { display: none; }
.stay__frame {
  flex: 0 0 min(82%, 24rem);        /* capped, so a tablet shows the next one rather than one poster */
  /* The same, rounded down to a multiple of 4px, so the 4:5 frame is a
     whole number of pixels both ways and its edge line never lands
     between two. A browser without round() keeps the line above. */
  flex-basis: round(down, min(82%, 24rem), 4px);
  display: grid;
  align-content: start;
  gap: var(--space-3);
  margin: 0;
  scroll-snap-align: start;
}
.stay__shot {
  position: relative;
  aspect-ratio: 4 / 5;
  border-radius: var(--radius-lg);
  overflow: hidden;
  background: var(--color-bg-accent-subtle);    /* accent tint, while the photograph loads */
  box-shadow: var(--stay-lift-stage);
}
/* THE FRAME'S EDGE: a half-pixel line in accent-300 (Dunya,
   2026-11-01), the accent the bar and the band's hairline are in, so
   the photograph sits in a fine light edge against the dark ground
   rather than ending on it.

   A SHADOW ON A LAYER OVER THE PHOTOGRAPH, NOT A BORDER. Measured at 2x,
   a 0.5px border came out uneven: Chrome rounds a border under 1px UP
   to a whole pixel (two device pixels), and an edge that fell between
   device pixels smeared to one blended pixel and one solid, so one side
   read thinner than the rest; which side depended on the window. A
   shadow's spread is not rounded, so this is a true half pixel, one
   device pixel on a high-density screen, and as a layer over the
   picture it is drawn the same on every edge whatever the photograph
   does under it. The sizes it sits on are kept to whole pixels (the
   frame's width below and the stage's height further down) so no edge
   lands between two. */
.stay__shot::after {
  content: "";
  position: absolute;
  inset: 0;
  z-index: 1;
  border-radius: inherit;
  box-shadow: inset 0 0 0 0.5px var(--accent-300);
  pointer-events: none;
}
/* --stay-focal is set per frame in the markup. The frame is 4:5, so a
   taller photograph loses height and none of its width (a 9:16 phone
   shot, as Dunya's all were, loses about a third), and then only the
   second number does anything. */
.stay__img {
  display: block;
  width: 100%; height: 100%;
  object-fit: cover;
  object-position: var(--stay-focal, 50% 50%);
}
.stay__caption {
  position: relative;               /* painted after the photograph, so its lift falls UNDER the words, not over them */
  display: grid;
  gap: var(--space-1);
  padding-right: var(--space-2);
}
.stay__name { color: var(--color-text-primary); }
.stay__line { color: var(--color-text-secondary); max-width: 34ch; }
/* pretty, so no line ends on one word (on Dunya, "stargaze." sat on a
   row of its own). A browser without it wraps as usual. */
.stay__line,
.stay__head .subhead { text-wrap: pretty; }

/* THE FACTS ARE PILLS (Dunya, 2026-11-01), each led by its glyph. A
   hairline grid was tried first and read as more of the list above
   it; the template's facts were always a shape of their own, set apart
   from the copy, and this keeps that. Outlined in the accent over a
   faint wash of it, never filled, so they read as facts and not as
   buttons beside the one filled button. They wrap as a row, as many
   to a line as fit: two and two in the desktop column, two, one and
   one on a phone. The glyphs are Phosphor's at its bold weight
   (phosphoricons.com), as the coupon's and the favourites' arrows are,
   in the accent ink; decorative, since each pill's words say it all. */
.stay__detail { display: grid; gap: var(--space-6); }
.stay__facts {
  list-style: none;
  margin: 0;
  padding: 0;
  display: flex;
  flex-wrap: wrap;
  gap: var(--space-2);
  color: var(--color-text-primary);
  font-weight: var(--fw-medium);
}
.stay__facts li {
  display: inline-flex;
  align-items: center;
  gap: var(--space-2);
  min-height: 2.75rem;                          /* 44px, the page's touch height, so the pills sit level with the button below */
  padding: var(--space-2) var(--space-3) var(--space-2) calc(var(--space-2) + var(--space-1));
  border-radius: var(--radius-pill);
  border: 1px solid color-mix(in oklab, var(--accent-300) 30%, transparent);
  background: color-mix(in oklab, var(--accent-300) 8%, transparent);
  white-space: nowrap;
}
.stay__facts svg {
  flex: none;
  width: 18px; height: 18px;
  color: var(--color-text-accent);
}

.stay__cta { width: 100%; display: inline-flex; align-items: center; justify-content: center; gap: var(--space-2); }
.stay__cta svg { width: 20px; height: 20px; }
/* Full width is for a thumb on a phone. From 600px a full-width button
   is a bar across a tablet, so it takes its label's width. */
@media (min-width: 600px) {
  .stay__cta { width: auto; justify-self: start; }
}

/* The list script.js writes. Never shown below 1100px: there the
   captions under the photographs carry the same words. */
.stay__picks { display: none; }

@media (min-width: 1100px) {
  /* THE STAGE AND THE COLUMN. The stage's width follows its height (a
     share of the window between two ends, at 4:5), and the column
     takes what is left. The two 1fr rows centre the column's content
     on the stage when it is the shorter of the two. */
  .stay__grid.is-staged {
    grid-template-columns: auto minmax(0, 1fr);
    grid-template-rows: 1fr auto auto 1fr;
    grid-template-areas:
      "stage ."
      "stage head"
      "stage detail"
      "stage .";
    gap: 0 clamp(3rem, 7vw, 7.5rem);
  }
  .is-staged .stay__head   { grid-area: head; }
  .is-staged .stay__detail { grid-area: detail; margin-top: var(--space-5); gap: var(--space-5); }

  /* svh, not vh, as on the deck above, so a mobile browser's toolbar
     cannot resize it. Under about 690px of window the frame stops
     shrinking with it; over about 950px it stops growing. At 84% the
     column beside it (heading to button, about 725px with Dunya's copy
     and four features) fits inside the frame's height on a 900px laptop
     window, so the photograph is the taller of the two and the column
     centres on it. A longer summary or a fifth feature can make the
     column the taller one; the 1fr rows then simply go to nothing. */
  /* align-self: start, not center: centred in a column taller than
     itself, the stage could land on a half pixel and its edge line
     would smear. When the stage is the taller of the two, the 1fr rows
     still centre the column on it. The height is rounded down to a
     multiple of 5px, so the 4:5 width is a whole number too (a browser
     without round() keeps the first height). */
  .is-staged .stay__frames {
    grid-area: stage;
    align-self: start;
    position: relative;
    display: block;
    height: clamp(36rem, 84svh, 50rem);
    height: round(down, clamp(36rem, 84svh, 50rem), 5px);
    border-radius: var(--radius-lg);                  /* so the lift follows the frame's corners */
    box-shadow: var(--stay-lift-stage);
    aspect-ratio: 4 / 5;
    overflow: visible;              /* not a scroll container here, so the drift below can see the page scroll */
    margin: 0;
    padding: 0;
  }
  .is-staged .stay__frame {
    position: absolute;
    inset: 0;
    display: block;
    visibility: hidden;
    clip-path: inset(0);
  }
  /* THE LIFT MOVES TO THE STAGE here. Each frame is clipped to its own
     box for the wipe, and that clip would cut a photograph's shadow
     off at its edge; the stage holds still under every wipe, so one
     shadow on it stays put while the pictures change on top. */
  .is-staged .stay__shot { height: 100%; aspect-ratio: auto; box-shadow: none; }
  .is-staged .stay__caption { display: none; }

  /* THE WIPE. The chosen frame comes in on top of the last one, and the
     last one stays whole underneath it until the wipe is over (script.js
     then hides it). The start of the wipe is a class script.js puts on
     for one frame and takes off again; it comes AFTER .is-active in
     this file, because the two weigh the same and it has to win
     while it is on. Choosing again mid-wipe drops the half-wiped frame
     underneath, whole: .is-leaving declares no transition, so its
     clip goes straight to the end. A camera push rides with the wipe,
     the photograph settling from 104% as it uncovers, over twice the
     wipe's length: long enough to read as the picture settling, short
     enough that it has stopped before the next hover. (It was --dur-push,
     the deck's 1400ms, and kept the photograph moving for a second after
     every choice.) Ease-out, not ease-in-out, for the reason at
     --dur-wipe: this answers the pointer, so it moves at once. */
  .is-staged .stay__frame.is-active {
    z-index: 2;
    visibility: visible;
    transition: clip-path var(--dur-wipe) var(--ease-out);
  }
  .is-staged .stay__frame.is-leaving { z-index: 1; visibility: visible; }
  .is-staged .stay__frame.is-from-below { clip-path: inset(100% 0 0 0); transition: none; }
  .is-staged .stay__frame.is-from-above { clip-path: inset(0 0 100% 0); transition: none; }

  .is-staged .stay__img { transform: scale(1.04); }
  .is-staged .is-active .stay__img {
    transform: none;
    transition: transform calc(var(--dur-wipe) * 2) var(--ease-out);
  }
  .is-staged .is-leaving .stay__img { transform: none; }

  /* THE LIST. A hairline track down its left edge, and a 2px bar in the
     accent that script.js moves to the chosen row: one bar travelling,
     not four switching, so the eye follows the choice down the list.
     It is drawn 1px tall and stretched with scaleY, so the glide is a
     transform and never a layout. */
  .stay__picks {
    display: block;
    position: relative;
    padding-left: var(--space-5);
  }
  .stay__picks::before {
    content: "";
    position: absolute;
    left: 0; top: 0; bottom: 0;
    width: 1px;
    background: var(--color-border-default);
  }
  .stay__picks-bar {
    position: absolute;
    left: -0.5px; top: 0;
    width: 2px; height: 1px;
    background: var(--color-text-accent);
    transform-origin: 0 0;
    transform: scaleY(0);
    transition: transform var(--dur-glide) var(--ease-out);
  }
  .stay__picks ul { list-style: none; margin: 0; padding: 0; }
  .stay__pick {
    display: grid;
    gap: var(--space-1);
    width: 100%;
    padding: calc(var(--space-2) + var(--space-1)) 0;    /* 12px: four rows and the facts fit beside the frame */
    border: 0;
    background: none;
    color: inherit;
    font: inherit;
    text-align: left;
    cursor: pointer;
  }
  /* THE CHOSEN ROW IS LIT WHOLE, its name AND its line in the primary
     ink, and every other row sits in the secondary. With only the name
     lit, the chosen row's line was the same grey as the rest and the
     row did not hold the eye (Dunya, 2026-11-01): the name is already
     the brightest ink the dark scope has, so the focus has to come
     from lighting more of the row, not a brighter name. Nothing drops
     below secondary: an unchosen row is still text someone may read,
     and it is still a button. */
  .stay__pick .stay__name,
  .stay__pick .stay__line {
    color: var(--color-text-secondary);
    transition: color var(--dur-ui) ease;
  }
  .stay__pick[aria-current="true"] .stay__name,
  .stay__pick[aria-current="true"] .stay__line { color: var(--color-text-primary); }
  /* The caption's 34ch cap is for a line under a 384px photograph. In
     the column the column is the measure, and a capped line broke
     "stargaze." onto a row of its own. */
  .stay__pick .stay__line { max-width: none; }
}
@media (min-width: 1100px) and (hover: hover) and (pointer: fine) {
  .stay__pick:hover .stay__name { color: var(--color-text-primary); }
}

/* THE DRIFT. The photograph on the stage moves a few percent against
   the scroll as the band passes, which gives a still picture some
   depth without anything being hijacked. A scroll-driven animation,
   so it runs on the compositor and costs no script; a browser without
   animation-timeline keeps the picture still, which is the whole
   fallback. Desktop only: on a phone the row moves sideways under a
   finger and a vertical drift inside it would fight that. scale and
   translate are the individual properties, so they compose with the
   wipe's push on transform instead of replacing it. 1.1 leaves 5%
   spare on every side and the drift spends 4% of it.

   THE TIMELINE IS NAMED ON THE STAGE, not view() on the picture.
   view() follows the nearest scroll container, and a .stay__shot with
   overflow: hidden IS one, so the picture never moves inside it and
   the drift would sit frozen at its first frame. */
@supports (animation-timeline: view()) {
  @media (min-width: 1100px) and (prefers-reduced-motion: no-preference) {
    .is-staged .stay__frames { view-timeline-name: --stay-frame; }
    .is-staged .stay__img {
      scale: 1.1;
      animation: stay-drift linear both;
      animation-timeline: --stay-frame;
    }
  }
}
@keyframes stay-drift {
  from { translate: 0 -4%; }
  to   { translate: 0 4%; }
}

/* REDUCED MOTION: no wipe, no push, no glide. The chosen photograph
   fades in over the last one instead, which keeps the change visible
   without anything travelling. */
@media (min-width: 1100px) and (prefers-reduced-motion: reduce) {
  .is-staged .stay__frame {
    clip-path: none !important;
    opacity: 0;
    transition: opacity var(--dur-ui) ease !important;
  }
  .is-staged .stay__frame.is-active,
  .is-staged .stay__frame.is-leaving { opacity: 1; }
  .is-staged .stay__img { transform: none !important; }
  .stay__picks-bar { transition: none; }
}

/* LEGACY · Amenities — numbered steps beside a pinned photo
   (No page uses this component and its driver, AMENITY STEPS, left
   script.js on 2026-10-07; What We Offer, section 3, replaced it.
   Kept for reference — delete it with the block headed "LEGACY ·
   AMENITIES, THE PINNED LAYOUT" further down if you never want it.)
   ------------------------------------------------------------
   Two columns on a wide screen: the left pins itself with
   position: sticky and carries the heading and the photo, the
   right is an ordinary <ol> that scrolls past it. Whichever step
   is nearest the middle of the viewport is the active one, and
   the photo swaps to match — script.js picks it with an
   IntersectionObserver.

   Mobile keeps the photo. The design this came from drops the
   pinned column entirely below 1024px, heading and all five
   photos with it, leaving a phone a text-only list. On a page
   whose whole job is to sell a rental that is the wrong half to
   throw away, so here the column stays and the photo pins above
   the list instead, still swapping as you read down.
   ------------------------------------------------------------ */
/* 48px top and bottom, where a normal section takes --section-y
   (64px on a desktop, 48px on a phone). Set on both edges rather
   than only the top so the section keeps the same air above and
   below it whatever the width. */
/* NOT overflow: hidden, however much the scaled blur below looks
   like it wants it here. The aside pins with position: sticky at
   1024px and up, and an ancestor with overflow: hidden becomes the
   scroll container it sticks inside — a box the same height as its
   own contents, which never scrolls, so the pin silently never
   engages and the column just scrolls away with the list. Measured
   with it on: the aside reached -1656px by the fourth amenity
   instead of holding at 48. The clip belongs on the backdrop, which
   is absolutely positioned and so is nobody's offset parent. */


/* The section's own ground stays underneath everything here and is
   what the contrast below was measured against — the backdrop only
   ever tints it, it never replaces it. If the images fail to load,
   or color-mix is unsupported and the veil falls back to opaque,
   the section is exactly the flat --color-bg-secondary it was. */


/* brightness() is doing the accessibility work, not the blur.
   A blur spreads a bright area out but does not dim it, and the
   worst patch across these four photos blurs to #E2D5C6 — light
   enough that a veil weak enough to be worth having would put the
   dimmed step copy under 4.5:1. Darkening the photograph first
   means the wash contributes hue and not lightness, which is also
   the effect that was wanted: the ground goes warm for the
   restaurant and cold for the marina without going pale.

   Measured on that worst patch, at brightness 0.65 under a veil of
   0.80: body copy 8.15:1, an inactive step at its 0.68 dim 4.81:1,
   the numeral in --color-text-brand 5.23:1. The binding number is
   the 4.81 — every step of this was chosen to keep it over 4.5.

   THE SCALE IS DOING TWO JOBS. The first is the old one: a blur
   samples past the element's edge, finds nothing there, and leaves
   a soft transparent border, so the image is grown past the box to
   push that border outside the section where the clip removes it.
   115% is the figure that does it.

   The second is cost, and it is the reason the box is 25% and the
   scale is 4.6 rather than the box being 100% and the scale 1.15.
   A filter has to rasterise the layer it applies to, and on the
   desktop layout below this box is the height of a four screen
   scroll track — around 1440x3400, which is 20MB of raster per
   photograph and four photographs in the section. Blurring a
   quarter-size copy and scaling the RESULT up costs a sixteenth of
   that, and scaling an already blurred layer is free on the GPU.
   Nothing is lost: the output is a 48px blur either way, and the
   detail a blur that heavy throws away is exactly the detail the
   downscale threw away first.

   The two numbers are tied — 25% x 4.6 = 115%, and the blur is
   divided by the same 4.6 (10.5 x 4.6 = 48) — so if either moves
   the other has to move with it. transform-origin at the top left
   rather than the centre, because the box is a quarter of the
   section pinned to its corner and the scale has to grow it back
   over the whole of it, not outwards from its middle. */



/* Same reasoning as the frame below: nothing has run yet, or
   script.js never arrived, so show the one that matches the first
   step rather than an empty tint. */


/* The veil. --color-bg-secondary is the ground the section would
   have had on its own; mixing the brand into it is what makes the
   wash read as the deep teal rather than as a grey haze, and
   because the brand hex is darker than the ground it also buys
   back contrast rather than spending it.

   The opaque declaration first is the fallback: a browser without
   color-mix drops the second line, gets a solid ground, and loses
   the photograph — which is the right way for this to fail. */


/* THE COPY SCRIM — the layer that pays for the fade further down.

   It exists for one reason: the inactive amenities are faded to
   0.45, and 0.45 of near-white does not clear 3:1 on the ground
   the veil above leaves behind. See the long note over the fade
   for the numbers. This is not decoration and it cannot be taken
   out without putting that fade back to 0.68.

   A FLAT BLACK rather than more veil, because the veil's own
   colour is the ceiling on how dark the veil can get — measured,
   and pushing its opacity and the photograph's brightness
   together barely moved the ground. Black has no such ceiling. It
   costs some of the photograph's colour coming through, which is
   what the wash is for, and that is the trade: the wash is
   decorative and the text is not.

   IT IS ON THE SECTION AND NOT ON THE BACKDROP, and that is the
   whole reason it is a separate element rather than another
   background layer on the veil. The backdrop is masked — it fades
   out over 8rem at the section's top and bottom edges so the wash
   dissolves rather than stopping on a line — and a scrim riding
   that mask fades out with it. Which is exactly the wrong place
   for it to fade: the pinned frame sits AT the top of the section
   for the whole first screen of the track, so the readability
   scrim was thinnest precisely where the copy first appears.
   Measured there, an inactive title came out at 2.49:1. On the
   section, unmasked, the scrim is even the whole way down.

   z-index 0 and last in paint order. The backdrop is also 0 but
   comes first in the DOM, so this lands on top of it, and .process
   is 1, so the copy lands on top of this. */


/* Above the backdrop. */


/* display: contents, so on a phone the wrapper stops being a box
   at all and the heading, the photo and the list become siblings
   in one column. That is what lets the photo pin: a sticky
   element can only travel inside its own parent, and boxed in the
   aside it would come unstuck the moment the aside ended — which
   is immediately, since the aside ends where the list begins.
   Dissolved, its parent is .process, which runs the height of the
   section, so the photo can hold while the whole list goes past.

   The heading is left out of the pin deliberately. Pinning the
   aside whole was the first attempt and it took 414px of a 664px
   phone screen — 62%, with the list reading through the slot left
   over. The heading is read once and does not need to stay. */
/* Both of these dissolve on a phone. The column wrapper only
   exists to hold the two blocks together as ONE grid item in the
   pinned layout; here there is no grid and no second column, and
   a box around them would be a box for nothing — worse than
   nothing, because .process__aside below has to be able to
   dissolve too, and a sticky or a grid rule can only see one
   level up. Contents all the way down, the heading, the list and
   the per-step photos are direct children of .process. */



/* THE DECK — a stage, not a frame.

   Every card is out of flow, so the stage has to carry its own
   height or the box collapses to nothing. What it must NOT carry
   is a radius, a fill, or an overflow clip: those belonged to the
   frame when the frame was the picture, and here the picture is
   the card. A clip in particular would cut the lift off at the
   top edge, which is the one part of this that has to be seen
   leaving.

   The three deck numbers are component dimensions, not spacing —
   how far one card sits behind the next — so they are set here in
   rem rather than taken from the space scale.

   --stack-shrink is unitless on purpose: it is multiplied by the
   depth and fed to scale(), which takes a number and not a
   length. */


/* The card. inset leaves --stack-peek clear at the bottom, so the
   front card is the stage minus that strip and the cards behind
   have somewhere to be.

   transform-origin at the bottom centre is what makes the deck
   read as a deck. Scaled from the centre, a card behind would
   pull its bottom edge UP and away from the peek strip the inset
   just made for it; scaled from the bottom, the bottom edges stay
   put and the shrink shows as the card being narrower — which is
   what "further away" looks like.

   z-index descends with depth so the front card is on top. 20 is
   an arbitrary ceiling with room under it for four; .is-spent
   below goes above the whole deck, because a card being lifted
   off passes over the ones it was sitting on.

   opacity is the depth cutoff. calc goes negative at depth 4 and
   the browser clamps it, so this holds for a deck of any size:
   depth 0-2 fully on, 3 and deeper off. A card fades in as the
   deck moves under it, which is the deck replenishing itself. */


/* Spent — the card for an amenity you have already read, lifted
   up and off the front of the deck.

   The distance is a percentage of the card's own height, so it
   holds at every viewport the pinned stage gets clamped to. It is
   deliberately short of a full card height: the opacity below
   takes the card out long before the transform finishes, so the
   travel only has to be far enough to read as a lift, and a
   longer one would send a still-visible card up over the section
   above.

   The rotation is the whole reason this reads as a hand lifting a
   card rather than a div sliding on a rail. It has to stay under
   about two degrees — past that it is a gesture, and a gesture
   repeated four times down a page becomes a mannerism. */




/* The shade that puts a card behind the front one. A photograph
   at full strength does not read as being further back however
   small you scale it — the eye takes brightness as distance
   before it takes size.

   A pseudo element at a transitioning opacity rather than
   filter: brightness() on the card, because opacity composites
   and brightness repaints, and this is riding a scroll. Tied to
   --depth, so it deepens with each card back and lifts to nothing
   on the front one without needing a class of its own.

   0.34 per step of depth, against a scrim that is itself 50%
   black, so a card one back is under 17% black and two back under
   34%. It was 0.45 while the deck offset was still 16px and the
   shade was carrying most of the "further away" on its own; with
   the offset at 24px the geometry does that work, and 0.45 took
   the second card down to 45% black — a shadow rather than a
   photograph. The shade only has to help now. */


/* Nothing has run yet, or nothing ever will because script.js did
   not load. Either way the first photo is the one to show, flat
   and on its own — without this the stage is four cards at depth
   0 on top of each other and the last one in the DOM wins.

   The deck is the enhancement; a single photograph is the thing
   it enhances. Same fallback the crossfade had. */



/* THE DOT RAIL IS NOT THERE AT ALL until script.js has run, which
   is a stronger fallback than lighting the first dot and the right
   one now that the dots are buttons. Nothing has a state to
   indicate — the deck is one flat photograph and no amenity is lit
   — and pressing one would do nothing, because the scroll
   arithmetic that makes them work lives in the file that did not
   load. Four dead controls is worse than no rail.

   The rail is otherwise styled in the pinned block below, which is
   the only width it exists at. */


/* And the same case for the description in the left column. With
   nothing running, no step is .is-active, so on desktop all four
   would be folded shut with no way to open one — the pinned layout
   has no tap target. The first amenity is the one whose photograph
   is showing, so it is the one whose line should be open. */


/* THE PHONE LAYOUT: the frame is off and each amenity carries its
   own photo.

   The pinned version was written for a phone and it does work,
   but it spends a third of a short screen on a picture that is
   holding still while the thing it illustrates scrolls past it —
   the pairing has to be inferred from the timing. One photo per
   amenity says the same thing by adjacency, which is the version
   that needs no inference, and it costs nothing: the four files
   are the ones the frame was already loading.

   Both are in the DOM at every width and the display switch picks
   one, rather than the markup differing per breakpoint. Below
   1024px the frame is off and these are on; the desktop block
   swaps them back. */


/* Row 2, column 1 — the same cell the title takes, so the title
   lands on the photograph rather than under it.

   No margin-bottom any more: it used to be the gap between the photo
   and the name below it, and there is no longer anything below it to
   clear. The space between two amenities is .process__step's own
   padding-block and always was.

   The cap that used to live here is on the step's grid column now, so
   the photo and the title are measured by one number instead of two.
   It is for one case and it is not a phone: a desktop-width window
   too short for the pinned layout falls back to here, and width: 100%
   of a 1200px container is a 1200x900 photograph per amenity. 32rem
   matches the cap .process__media already carries for the same
   reason. A phone is narrower than this, so nothing changes there. */




/* The CTA, phone version: full width under the last amenity, at
   the bottom of the section.

   Full width because every other block in this layout is —
   each amenity is a full-width photograph with its name under it
   — and an auto-width button under a run of those reads as a
   loose fragment. It is also the friendlier tap target.

   The 32rem cap is the same one .process__step-photo carries and
   it is there for the same case: a desktop-width window too short
   for the pinned layout falls back to here, and a 1200px-wide
   button is not a button. A phone is narrower than the cap, so
   nothing changes there.

   margin-top rather than relying on a gap: this is the phone
   layout, where .process__col has dissolved and there is no flex
   container left to own the spacing. */


/* THE PHONE STEP: a numeral, then the photograph with the name laid
   over the foot of it.

   A grid rather than a wrapper element, because the overlay is a
   phone-only arrangement and the pinned layout below needs these two
   to be separate boxes in separate columns — a div around them would
   have to be dissolved again up there, and the markup would carry a
   box that exists for one breakpoint. Two rows: the numeral takes the
   first, and the photo and the title SHARE the second, which is what
   stacks them without either one leaving the flow.

   The column is capped rather than the photo, so the title's scrim
   ends exactly where the photograph does. --process-photo-w is the
   one number both read, and it is the same 32rem the photo used to
   carry alone — see the note on .process__step-photo for the case
   that cap is actually for, which is not a phone. */


/* Drawn by CSS, not typed into the markup, so adding or deleting
   a step renumbers the rest on its own. An explicit counter
   rather than the list-item one <ol> already keeps: list-item
   only increments on elements still at display: list-item, and
   these <li>s are not. */


/* The brand hue is the active step's badge now rather than every
   step's decoration, which is a better use of it: four teal
   numerals said "these are numerals", one says "you are here".

   NOT --color-text-brand itself, though, and the reason is
   measured. That token is defined as the first brand step that
   passes AA, so it sits on its floor by construction and has
   nothing in hand — on the worst patch of this section's wash it
   comes out at 3.04:1 against a 48px numeral's 3:1. Passing, and
   passing by 0.04, which is not a margin.

   Mixed halfway into --color-text-primary it renders #D4E1E4 and
   measures 3.85:1 on the same patch. That keeps the hue shift that
   does the actual signalling — the numeral reads visibly cooler
   than the white beside it — and buys back most of the headroom.
   The fallback declaration above it is for a browser without
   color-mix, which gets the plain near-white and loses only the
   tint.

   in oklab rather than srgb so the mix stays on a perceptual
   ramp: in srgb a light desaturated teal mixed with a near-white
   dips through a duller middle, and half the point of this is
   that the hue reads cleanly at a glance. */


/* THE TAP TARGET — phone layout only, and it is the photograph.

   It takes the photo's own grid cell, so it is exactly the picture
   and never a hair more; nothing about its size is typed twice. It
   sits UNDER the caption in z-order and the caption is
   pointer-events: none, which is what lets a tap on the name pass
   through to the button behind it — the alternative is a control
   with a dead strip across its bottom third.

   No fill and no border of its own. The affordance is the picture
   plus the name laid over it, which is already a card, and a phone
   reader tries tapping a card. :focus-visible is the global rule
   from the top of this file, so a keyboard user gets the page's own
   ring here without it being restated.

   Above 1024px the pinned deck is back and the per-step photo is
   off, so this button changes what it is the face of rather than
   going with it: up there it is the whole row, numeral and name,
   and pressing it goes to that amenity. Same element, same one
   meaning — press this amenity — see the desktop block. */


/* THE NAME AND THE LINE, ON THE PHOTOGRAPH — phone layout only.
   The pinned layout below puts the name back to a plain line in
   the left column, where there is no photograph under it to clear.

   IT IS ONLY AS TALL AS ITS WORDS. The whole point of the request
   this answers is that the picture stays a picture: the scrim is a
   band at the foot of the frame sized by the caption's own padding,
   not a wash over the image. Both stops of the ramp are therefore
   inside the band — 0.72 at the bottom edge easing to nothing at the
   top of it — so the band has no visible upper edge either, and what
   the reader sees is the photograph darkening into the last line.

   Closed, that is one line. Open, the description unfolds inside
   this same box and the band grows upward with it, which is why the
   band lives here and not on the title: one box, one scrim, one
   height, whatever state it is in.

   align-self: end puts the band on the bottom edge and nowhere else;
   the grid row is the photo's height, so "end" is the foot of the
   picture at any width — and it is also why the box can grow without
   moving anything: it grows into the picture, not down the page.

   RADIUS ON THE BOTTOM CORNERS ONLY, matching the photo's own, or a
   square scrim corner prints outside a rounded photo corner.

   pointer-events: none so the whole picture stays one tap target —
   see .process__toggle above.

   The literal near-black rather than an overlay token: this is a
   light level measured against a photograph, and it has to hold
   that level whatever hue the client's brand is set to. */


/* THE SHADOW IS THE SECOND LINE, NOT THE FIRST — same as
   .tall-card__title. WCAG's contrast maths ignores text-shadow
   entirely, so it earns nothing on paper; it is here for the case a
   band cannot flatten, which is a small bright hotspot directly
   under the words. The band is what the contrast rests on: over the
   worst patch these four photographs blur to, 0.72 of near-black
   puts near-white text over 4.5:1, and the title is large text at a
   3:1 floor besides. */


/* THE DESCRIPTION, FOLDED AWAY — phone layout only.

   grid-template-rows: 0fr to 1fr, not height or max-height, and
   that is the whole reason this is a grid with one child. A height
   animation needs a number to animate to and the number is the
   text's own wrapped height, which nothing in CSS can be told
   without measuring it in script; 0fr to 1fr means "none of your
   content" to "all of it" and the browser does the measuring. The
   child carries overflow: hidden and min-height: 0, which is what
   makes the 0fr row actually clip — a grid item's automatic minimum
   size would otherwise hold it open at its content height.

   A browser without interpolable grid tracks (anything before
   Chrome 107 / Safari 16 / Firefox 120) gets the same two states
   with no tween between them. The line still opens and closes.

   The opacity is a second channel on purpose rather than a
   duplicate of the fold: unfolding alone reads as the text being
   pushed out from behind the title, which is a slightly comic
   effect at this size, and fading it over the same time turns that
   into the line arriving. */


/* overflow on the CHILD, not on the .process__desc grid itself:
   the grid is the thing whose row is collapsing, and clipping it
   instead would clip the row rather than the content inside it. */




/* THE PICTURE DIMS AND STAYS A PICTURE, which is what the request
   asks for and what rules out a scrim. brightness() is a multiply:
   every pixel keeps its hue and its detail and only its level comes
   down, so what the reader sees is the same photograph turned down.
   A black overlay at the same apparent strength washes the whole
   frame towards one grey and the picture stops being a picture.

   0.62 IS SET BY THE LOOK AND CHECKED AGAINST THE CONTRAST, in that
   order, and the check passes with room to spare because the
   description is inside the caption's band and not out on the open
   photograph. Worst case is a blown-out white highlight directly
   under the words: multiplied by 0.62 and then under the 0.52 of
   near-black the band is carrying at that height, it lands at a
   relative luminance of about 0.072, and --color-overlay-text over
   that measures ~7.5:1 against a 4.5:1 floor. Real pixels are darker
   than that and the text-shadow is spare change on top.

   Which means the number to be careful with is not this one. It is
   the band's — take a stop out of .process__caption and the floor
   moves; this only has to stay dark enough to read as a state
   change, and 0.62 is comfortably that. */





/* Pinned flush to the top rather than inset by a gutter. An
   offset leaves a strip of section background above the photo,
   and the list scrolling underneath shows through it — a band of
   sliced text riding along above the picture. At 0 the photo's
   own top edge is the screen's and there is no strip. */


/* Dimming the inactive steps is an enhancement, so it is scoped
   to the class script.js adds. Without JS every step stays at
   full strength and the section is a plain numbered list, which
   is the correct thing for it to fall back to.

   0.50, AND IT COST SOMETHING TO GET THERE. The fade was 0.68 for
   one reason: that was the floor the section's ground allowed.

   The measurement that matters is against the ground actually
   BEHIND THE GLYPHS, not against --color-bg-secondary. The flat
   token is #41464E, but the section's blurred wash sits on top of
   it, and with the veil alone the worst patch the copy crossed
   composited to #68706F — light enough that near-white at 0.68
   measured 3.11:1 and at 0.65 measured 2.99:1 and failed. There
   was no room in it.

   What bought the room was .section--process::after, the copy
   scrim, which is why that layer is not optional. With it the
   worst ground behind the copy is around #2D3234 and the numbers
   are these:

     --color-text-primary  full     11.96:1
                           at 0.50   4.13:1
     the active numeral    full     10.22:1
       (#D4E1E4, the 50% brand mix)
     the inactive numeral  at 0.50   4.33:1 pinned,
                                     3.93:1 unpinned
     the eyebrow           full      5.33:1  (4.5 floor — 14px)
     the subhead           full      7.25:1  (4.5 floor)

   Both the numeral and the title are WCAG large text — the
   numeral at 28-48px, the title at 24px/400 — so the floor they
   clear is 3:1 and not 4.5. 0.50 clears it by 1.13.

   THE FADE STOPS AT 0.50 BY CHOICE, not by the ceiling: there is
   now room for 0.45, which measured 3.13:1 before the scrim's
   ramp was lengthened and would sit near 3.6:1 today. It is held
   back because the margin is worth more than the extra 5%. The
   inputs here are a photograph, a webfont and a browser's
   antialiasing, none of which this file controls, and a fade
   sitting 0.1 above a legal floor is one font substitution away
   from being under it. If a deeper fade is ever wanted, re-run
   the sampler below before taking it — do not reason about it.

   ALL OF THESE ARE READ OFF RENDERED PIXELS, not computed: 303
   samples, seven viewports from 390x844 to 1920x1080 covering the
   pinned layout, the phone layout and the short-window fallback,
   six positions along the scroll track, all four steps, comparing
   the brightest pixel of each glyph against the brightest pixel
   of the ground behind it — with the copy hidden for the second
   half of each pair, so the ground is the real composite of
   section, wash, veil and scrim rather than a token.

   Two traps if you re-run it. The numeral is a ::before and has no
   box to measure, so it has to be sampled as a band — and on the
   phone layout that band is ABOVE the per-step photograph, not
   directly above the title the way it is up here; aim it at the
   title and you measure the photograph against itself and get a
   meaningless 1:1. And a step scrolled off the edge returns bare
   ground for both halves of the pair, which also reads as 1:1 —
   discard any sample whose glyph is not brighter than its ground
   rather than counting it as a failure.

   That last part is why the figures here are trustworthy and the
   ones this comment used to carry were not. The original numbers
   were computed against --color-bg-secondary, the flat token, and
   overstated every result by two to three stops: the dimmed title
   was documented at 5.08:1 and was in fact shipping at 3.11:1.
   The ground in this section is a photograph. Measure it.

   The numeral is IN the fade, which it was not originally. That
   needed the colour swap above: brand at 3.04:1 on the old ground
   had no headroom to dim into, primary did, and the brand hue
   moved to the active step where it reads as a position marker.
   The numerals fading with their titles is what makes an inactive
   step read as one dim block rather than a bright number with
   faint text under it.

   opacity on the ::before rather than on the <li>, because
   opacity on a parent cannot be undone by a child — dimming the
   step itself would take the active row's numeral down with it. */


/* THE NUMERAL FADES ONE STEP LESS THAN ITS TITLE, and the two
   numbers differ for a reason that is not aesthetic.

   The numeral is 16px. The title is 24px. 24px is the WCAG
   large-text threshold, so the title clears a 3:1 floor and the
   numeral has to clear 4.5:1 — a harder target on the same
   ground, at the same colour, in the same row. Measured on the
   worst patch the copy crosses:

     16px numeral at 0.50   4.03:1 unpinned   <- fails 4.5
                    at 0.55   4.53:1          <- clears, barely
                    at 0.58   4.85:1
     24px title   at 0.50   4.13:1            <- clears 3:1

   0.58 is the first value with a real margin at every viewport,
   pinned and unpinned. It is close enough to the title's 0.50
   that the row still reads as one dim block — the gap is about
   8% of white, well under what the eye separates at this size —
   and it is the difference between the number being legible and
   not.

   If the numeral is ever put back above 24px, delete this rule:
   it goes back under the 3:1 floor and can share the 0.50. */




/* A STEP THE READER HAS OPENED IS LIT, wherever it happens to be on
   screen. The dim above answers "which amenity are you level with",
   which is a scroll position and a guess; a tap is a statement. So
   an open step's name comes up to full with its description rather
   than sitting at 0.50 over a picture that has just been darkened
   for the sake of the line under it.

   Phone-only in effect, because .is-open is only ever set at that
   width — see the toggle in script.js. */


@media (prefers-reduced-motion: no-preference) {
  /* --dur-reveal, not --dur-crossfade. The crossfade token is 1200ms
     and it was right for a dissolve, where the eye has nothing to
     track and a slow one reads as editorial. A card being lifted is
     a movement with a start and an end, and 1200ms of it reads as
     the page being slow rather than the card being heavy. 560ms is
     long for UI and correct here: this is explanatory motion, seen
     three times in a section, not a control being operated.

     Named properties rather than `all`, so the ::after shade and
     the box-shadow are not dragged into the same timing. */
  

  /* The one asymmetry, and it is what keeps the lift on the stage.
     The transform still runs the full 560ms, but the fade is over
     in about 310ms — so the card is gone well before the travel
     finishes and never gets far enough up the page to be seen
     crossing the section above.

     Derived from the token rather than typed as 310ms, so retuning
     --dur-reveal keeps the two in proportion. */
  

  
  /* The dots ride --dur-ui rather than the deck's --dur-reveal. A
     560ms dot is a dot arriving late: the indicator's whole job is to
     have already answered by the time the eye reaches it, and it is
     the one thing in this section that is not explanatory motion. */
  
  

  /* THE HIGHLIGHT IS ASYMMETRIC, and it is worth saying why
     rather than leaving it as two numbers that happen to differ.

     Symmetrically, both at --dur-reveal, the outgoing amenity
     fades down while the incoming one fades up over the same
     560ms — and for most of that half second neither of them is
     lit. Caught at 150ms into a step change the whole list read
     as uniformly dim, which is the one state it is supposed to
     never be in: the highlight exists to answer "where am I", and
     for half a second it answered "nowhere".

     So lighting up is quick — --dur-ui, the page's control-
     feedback duration — and fading back is unhurried. The list
     always has something clearly lit, and the amenity you have
     left dims away behind you rather than trading places.

     This works by specificity and not by a second property: the
     `.is-active` rules below are the destination when a step
     lights up, so their duration is the one that runs; the rules
     here are the destination when it stops being active, so
     theirs runs on the way out. */
  

  /* The numeral has two things changing at once and they want
     different curves. The fade is a state arriving, so it takes
     the page's --ease-out with everything else; the hue is a
     colour change and colour changes take `ease`, because there
     is no motion in one for a curve to characterise. */
  

  

  

  /* THE FOLD — --dur-ui, not --dur-reveal, and the distinction is
     the one the deck's note above draws. Everything else in this
     section animates because the page is scrolling past it, which
     is explanatory motion and gets the long duration. This is a
     button being pressed, and a control that takes 560ms to answer
     reads as a slow page rather than a considered one.

     grid-template-rows is named explicitly. `all` here would drag
     the caption's background gradient into the same transition, and
     an interpolating gradient on top of a photograph is a repaint
     per frame for no visible gain.

     The photograph's brightness rides the same clock, so the dim and
     the line arrive together — two halves of one gesture rather than
     a flash followed by some text. */
  

  
}

/* Reduced motion keeps the pairing and loses the movement, which
   is what the setting actually asks for — not "no animation".
   The deck stops being a deck: no lift, no offset, no shrink, no
   shade. The cards go back to a plain opacity crossfade, so
   reaching an amenity still changes the picture beside it and the
   section still says what it says. Only the travel is gone.

   This is a change from the old behaviour, which froze on the
   first photograph. Freezing was over-cautious: an opacity
   transition is not motion, and the cost of it was that a
   motion-sensitive reader got one picture for four amenities.

   The wash is the exception and still holds on the first. It is
   the whole section's ground going a new colour, which is a much
   larger area of change than a card inside a column, and the
   crossfade that carries it is 1200ms of the page shifting hue
   underneath the copy being read. */
@media (prefers-reduced-motion: reduce) {
  
  
  
  

  
  

  /* THE DIM STAYS. It used to be undone here along with the deck's
     movement, and that was over-broad: a difference in opacity
     between two elements is a static state, not motion, and taking
     it out left a motion-sensitive reader with a list in which
     nothing said which amenity was up. The transitions are already
     off — this block is inside prefers-reduced-motion, so the
     highlight changes instantly instead of fading — which is the
     part the setting is actually asking about. Only the chips, which
     have no active state of their own, come back to full. */
  
}

/* ============================================================
   3 · WHAT WE OFFER
   ------------------------------------------------------------
   A pinned stage showing one amenity at a time. The section is a
   TRACK taller than the screen; the stage inside it sticks, and
   the scroll spent getting past the track is divided evenly
   between the amenities. Same device as the hero and the line.

   The card holds the middle of the stage, the text sits to one
   side of it and alternates, and a rail of icons along the bottom
   says where you are. Everything is stacked in one grid cell and
   only the active item is drawn.

   BELOW 900px, AND UNDER REDUCED MOTION, none of that happens —
   see the end of this block. The stage unpins and the amenities
   become four ordinary cards with their text over the foot of
   their own photograph, which is the whole fallback.
   ============================================================ */
.section--offer {
  position: relative;
  isolation: isolate;
  padding-block: 0;
  background: var(--color-bg-brand-subtle);

  /* NO overflow HERE. An ancestor with overflow other than visible
     becomes the scroll container for a sticky descendant, and the
     stage below silently stops sticking — it scrolled straight past
     and the section rendered as an empty band. The blurred backdrop
     is the only thing that needs clipping and it clips itself. */
}

/* Hairlines top and bottom. The band has its own ground, so these
   are what give it two edges rather than one soft change of tone. */
.offer__rule {
  position: absolute;
  left: 0; right: 0;
  z-index: 2;
  height: 2px;
  pointer-events: none;
  background: linear-gradient(90deg,
    transparent, var(--color-border-accent) 18%,
    var(--color-border-accent) 82%, transparent);
}
.offer__rule--top    { top: 0; }
.offer__rule--bottom { bottom: 0; }

/* ---- the sky --------------------------------------------------- */
/* THE REVIEWS BAND'S GROUND, worn here too (2026-10-07, folded back
   from a client build). It replaced a blurred, cross-fading wash of
   the card photographs. The layer is the shared .sky — see "the sky as
   a layer" beside .section--testimonials, where the box and the paint
   both live, so the bands that wear it cannot drift apart.

   INSIDE THE STAGE, NOT ON THE SECTION, and that is the one thing
   about it particular to this band. The section is a track several
   screens tall; a gradient painted on it would be stretched over all
   of them, and the pattern's masked hole would sit screens away from
   the card. Pinned, the stage is exactly one screen, so the sky is the
   same composition the reviews band shows. Off the pin it covers the
   header, carousel and rail, as the reviews sky covers that band.
   The stage is positioned with a z-index, which makes it the
   stacking context .sky's z-index -1 needs. */

/* ---- the stage ------------------------------------------------- */
.offer__stage {
  position: relative;
  z-index: 1;
  padding-inline: var(--container-x);
}

/* CENTRED — eyebrow, heading and intro on one axis, the way the
   Local Favorites, Location and Reviews headers are. It was left
   aligned on the carousel's gutter for a while; it went back to centred
   on 2026-09-22 (folded back from a client build), and with the card
   centred under it the two now share an axis rather than an edge.

   The block is capped at --container-max and centred as a block too,
   so the intro's own measure cap (on .offer__intro) has something to
   centre within at every width. */
.offer__head {
  /* width: 100% IS LOAD-BEARING, not belt and braces. Under the pinned
     layout this is a flex item in a column, and an auto margin on the
     cross axis CANCELS the stretch that would otherwise size it — so
     with max-width and margin-inline alone the block shrank to the
     width of the longest line and centred itself, which is the exact
     thing being removed here. An explicit width gives the auto margins
     something definite to centre. */
  width: 100%;
  max-width: var(--container-max);
  margin-inline: auto;
  text-align: center;
  /* The bottom pad is the gap to the card on a phone: 40px here plus
     the 8px of shadow room the carousel carries above its cards makes
     48. The pinned layout sets its own 48 — see the override there. */
  padding-block: clamp(var(--space-7), 7vh, var(--space-10)) var(--space-6);
}
/* The accent, not the shared eyebrow colour. That colour is solved
   against the page's own ground; this eyebrow sits on the band's own
   ground (a blurred photograph washing under it when this was
   measured, the pale-blue sky now), and there the shared one came in
   at 3.46:1 against a 4.5 bar. This is 14px uppercase, so it is small
   text and gets the small text bar. */
.offer__head .eyebrow { color: var(--color-text-accent); }

.offer__intro {
  max-width: 36rem;
  margin: var(--space-3) auto 0;
  color: var(--color-text-secondary);
}

.offer__items { position: relative; }

/* ---- the card and its text ------------------------------------- */
.offer__card {
  position: relative;
  width: 100%;
  aspect-ratio: 3 / 2;
  border-radius: var(--offer-radius);
  overflow: hidden;
  isolation: isolate;
  background: var(--color-bg-inverse, var(--gray-950));
  /* THE POSTER IS A <picture> UNDER THE VIDEO, not a CSS background
     and not poster="". poster="" takes one image, so a phone would
     fetch the wide frame only to cover it; a background cannot be lazy,
     and on the client build that first tried one, five first frames
     (about 400 KB) were fetched during the first paint for cards two
     screens down. .offer__poster picks the shape with the same media=""
     test the clip's <source>s use, with loading="lazy" on the <img>, so
     nothing is fetched until the deck is near. The video paints over it
     the moment it has a frame, and since that frame IS the poster,
     nothing visibly changes. A card with no clip keeps the <picture>
     and drops the <video>; everything else is the same. */
  box-shadow: var(--offer-lift);
}
.offer__poster {
  position: absolute;
  inset: 0;
  z-index: 0;                             /* the video, later in the DOM, paints over it */
}
/* --offer-focal is set per card in the markup (2026-10-23, from the
   Gooseberry build), e.g. style="z-index:4; --offer-focal: 50% 85%".
   IT AIMS THE PHONE CROP ONLY. The 16:9 wide cut is wider than its 3:2
   card, so cover trims its sides and the second number has nothing to
   move there. The 9:16 vertical cut is TALLER than the phone's 4:5 card
   and shows about 70% of its height, and the caption sits over the foot
   of the card: a higher second number lifts a subject low in the frame
   clear of the caption, at the cost of the sky. Video and poster read
   the same value, so the frame does not jump when the clip starts. */
.offer__poster img {
  display: block;
  width: 100%; height: 100%;
  object-fit: cover;
  object-position: var(--offer-focal, 50% 50%);
}
.offer__media {
  position: absolute;
  inset: 0;
  width: 100%; height: 100%;
  object-fit: cover;
  object-position: var(--offer-focal, 50% 50%);
  z-index: 0;
}
/* Bottom-weighted, because the caption sits on the foot of the card at
   every width and lands exactly here.

   SIZED IN rem, NOT PERCENT (2026-10-23, from the Gooseberry build,
   where the client said the dark was covering the whole clip). The
   stops used to be 22/48/72% of the card, so the ramp grew with the
   card and a 600px desktop card was dimmed two thirds of the way up,
   half dark at the middle. The caption is the same few lines whatever
   size the card is, so the ramp is now the caption's height plus a
   run-out: 0.72 at 7rem, 0.50 at 11.5rem, a breath at 14.5rem, clear
   by 17rem (272px). On a desktop card the top half or more of the
   clip is untouched.

   0.50 AT 11.5rem IS THE NUMBER THAT MATTERS. The 12px index is the
   top of the caption and the string with the 4.5:1 bar. Measured on
   Gooseberry off the card's foot: 8.75rem on a desktop card with a
   one-line name, 11.15rem where the name wraps to two (1280x720),
   6.2-7.7rem on a phone. So it always sat on 0.52 or more, above the
   0.50 --offer-scrim-2 was solved for. A caption that grows a third
   line needs the ramp moved up with it. */
.offer__scrim {
  position: absolute;
  inset: 0;
  z-index: 1;
  background: linear-gradient(0deg,
    var(--offer-scrim-4) 0, var(--offer-scrim-3) 7rem,
    var(--offer-scrim-2) 11.5rem, var(--offer-scrim-1) 14.5rem,
    var(--offer-scrim-0) 17rem);
}
/* THE PHONE'S OWN RAMP (Gooseberry, 2026-10-22: the client asked for
   the same treatment there). The 4:5 card is only 350-440px tall, so
   the 17rem ramp above still darkened 62-78% of it. The phone caption
   is smaller (20px name, body-size lead): its index measured
   6.1-7.7rem off the card's foot at 360, 375, 390 and 430 wide, the
   high figure where a name wraps to two lines. So 0.50 at 8.25rem and
   clear by 12rem (192px), 44-55% of the card; the index sits on 0.53
   or more. 600px and up (the 3:2 tablet card, index 8.1-10.6rem)
   keeps the ramp above. */
@media (max-width: 599px) {
  .offer__scrim {
    background: linear-gradient(0deg,
      var(--offer-scrim-4) 0, var(--offer-scrim-3) 4.5rem,
      var(--offer-scrim-2) 8.25rem, var(--offer-scrim-1) 10rem,
      var(--offer-scrim-0) 12rem);
  }
  /* The light variant on a phone — see the desktop rule for why. */
  .offer__item[data-offer-scrim="light"] .offer__scrim {
    background: linear-gradient(0deg,
      rgba(var(--color-overlay-scrim-rgb), 0.70) 0,
      rgba(var(--color-overlay-scrim-rgb), 0.54) 4.5rem,
      rgba(var(--color-overlay-scrim-rgb), 0.30) 8.25rem,
      var(--offer-scrim-0) 11rem);
  }
}
/* A wash of the band's own colour over the picture, so a card that
   is not the active one sits back into the section instead of
   staying a bright rectangle. The script clears it on the active
   card. Never drawn on a phone, where there is only ever one card
   on screen at a time. */
/* The inactive-card veil's colour, declared on the section so it follows
   the page theme and not the card's pinned-dark scope — see the note on
   .offer__veil. Light page: the sky's middle stop, which is the ground
   behind the deck. Dark page: the theme's brand-subtle surface, which is
   the band's dark ground. */
.section--offer { --offer-veil-color: var(--tm-sky-mid); }
[data-theme="dark"] .section--offer { --offer-veil-color: var(--color-bg-brand-subtle); }

.offer__veil {
  position: absolute;
  inset: 0;
  z-index: 3;
  pointer-events: none;
  border-radius: inherit;
  /* THE COLOUR IS DECIDED ON THE SECTION, two rules up, not here. The
     card is pinned data-theme="dark" in the markup (for the dark scrim
     and light type on the photograph), and any semantic token read
     INSIDE that scope resolves to its dark value — --color-bg-brand-subtle
     came out brand-950 and dropped a dark veil on every card behind the
     front one, a stack of shadows on a pale band. Reading a literal
     (the old wash's pale tint) fixed the light page and broke the dark one: a pale
     wash on a near-black band. So the veil reads --offer-veil-color,
     which .section--offer declares from the PAGE's theme and the card's
     scope never redefines, so it inherits through untouched. The job
     has not changed: sit an inactive card back into the band. */
  background: var(--offer-veil-color);
  opacity: 0.45;
  transition: opacity var(--dur-reveal) var(--ease-out);
}
/* Off for the front card AND for a card on its way out. The veil is for
   the cards waiting behind the front one; a departing card is in the
   open now — it travels up over the stage rather than being clipped —
   and a wash of band colour on it read as a greyed-out card flying off.
   script.js writes .is-spent on every item whose turn is over. */
.offer__item.is-active .offer__veil,
.offer__item.is-spent  .offer__veil { opacity: 0; }

/* A hairline INSIDE the corner. Painted as a padding-box mask rather
   than a border so it follows the radius exactly and costs the card
   no layout size. */
.offer__edge {
  position: absolute;
  inset: 0;
  z-index: 3;
  pointer-events: none;
  border-radius: inherit;
  padding: 1px;
  background: linear-gradient(140deg,
    var(--offer-edge-1), var(--offer-edge-2) 42%, var(--offer-edge-1));
  -webkit-mask: linear-gradient(#000 0 0) content-box, linear-gradient(#000 0 0);
  -webkit-mask-composite: xor;
          mask-composite: exclude;
}

.offer__index {
  display: block;
  font-family: var(--font-body);
  font-size: var(--fs-text-xs);
  letter-spacing: var(--ls-wider);
  color: var(--color-text-accent);
  margin-bottom: var(--space-2);
}
/* THE LEAD AND THE NAME (2026-10-07, folded back from a client build):
   "Soak in the" over "HOT TUB", inside one <h3> so the heading still
   reads as the whole phrase. There is no description line — the lead
   does the inviting a description used to.

   The lead is the quiet half: the body face at reading size and the
   softer overlay white, so it reads as the start of a sentence rather
   than as a label. The name carries the card — display face, capitals,
   tracked open the way an uppercase line has to be. The capitals are
   text-transform, not typed: a word typed in capitals can be spelled
   out letter by letter by a screen reader, and it is the one place to
   change if a name ever wants to be set in ordinary case.

   SMALLER THAN IT LOOKS LIKE IT SHOULD BE, and on purpose: capitals,
   tracked and semibold, read about a size larger than the same pixels
   in ordinary case. At 24px on a phone and 36px on a landscape card
   the names took over the card. So --fs-text-xl (20) on a phone, set
   solid at a 24px line because two lines of capitals have no
   descenders to clear, and --fs-display-sm (32) from 600px, where the
   card turns 3:2 and roughly doubles in width. A three-word name takes
   two lines on a phone and one on a computer. The lead stays at
   reading size: smaller over moving footage stops being legible, and
   the change of case already says which line is which. */
.offer__title {
  margin: 0;
  color: var(--color-text-primary);
}
.offer__lead {
  display: block;
  font-family: var(--font-body);
  font-size: var(--fs-text-md);
  line-height: var(--lh-text-md);
}
.offer__name {
  display: block;
  font-family: var(--font-display);
  font-size: var(--fs-text-xl);           /* 20px */
  line-height: var(--lh-text-md);         /* 24px */
  font-weight: var(--fw-semibold);
  letter-spacing: var(--ls-wide);
  text-transform: uppercase;
}
@media (min-width: 600px) {
  .offer__lead {
    font-size: var(--fs-text-lg);
    line-height: var(--lh-text-lg);
  }
  .offer__name {
    font-size: var(--fs-display-sm);      /* 32px */
    line-height: var(--lh-display-sm);
  }
}

/* THE SENTENCE UNDER THE NAME (Walden Retreats). The template's card
   caption is a lead and a name; this build keeps a sentence on each
   card, which the client edits. Hidden on a phone, where the caption
   sits on a 4:5 card and three more lines would cover the picture;
   shown from 600px. It makes the caption about a third taller than
   the template's, so the desktop scrim ramp is moved up to match —
   see the Walden note on .offer__scrim in the pinned block. */
.offer__desc {
  font-family: var(--font-body);
  font-size: var(--fs-text-md);
  line-height: var(--lh-text-md);
  color: var(--color-text-secondary);
  margin: 0;
  max-width: 500px;
}
@media (max-width: 599px) {
  .offer__desc { display: none; }
}

/* ---- the dot rail ----------------------------------------------
   PLAIN DOTS. This was a row of four 48px illustrated icons joined
   by dotted connector lines that filled as you scrolled. Two things
   were wrong with it: the icons sat on a blurred photograph and had
   to fight it to stay legible, and a filling progress line is a lot
   of apparatus for four cards. The dot says which one of four you
   are on, which is all the rail was ever for.

   It is the SAME dot as .testimonials__dot — same 8px, same ink,
   same accent when lit, same invisible hit area. Two rails on one
   page that behave alike should look alike, so if you retune one,
   retune both.
------------------------------------------------------------------ */
/* CENTRED, unlike the heading above it. The heading is copy and copy
   is read from the left; the rail is a position indicator for a strip
   that runs off both edges, and centring is what keeps it from
   reading as the start of another column of text.

   The top pad is small because .offer__items below already carries
   64px of shadow room under the card — the visible gap between card
   and rail is those two added together. The pinned layout zeroes that
   room and puts the space back here; see the override in its block. */
.offer__dots {
  display: flex;
  align-items: center;
  justify-content: center;
  /* 16px between dots, not 8 (2026-10-05). An 8px dot is far below the
     24px AA target, and the exemption for small targets is SPACING: a
     24px circle centred on each must not touch the next target. At 8px
     apart those circles overlapped and Lighthouse's target-size audit
     failed every dot; at 16px apart they exactly meet. The invisible
     ::after hit areas below land edge to edge for the same reason. */
  gap: var(--space-4);
  width: 100%;
  max-width: var(--container-max);
  margin-inline: auto;
  /* 48px under the rail at every height, the page's floor for the space
     inside a section's edge (2026-11-01). It was clamp(40px, 4vh,
     48px), which gave 40px on a 900px window. */
  padding-block: var(--space-2) var(--space-7);
}

.offer__dot {
  position: relative;
  flex: none;
  width: var(--offer-dot-size);
  height: var(--offer-dot-size);
  padding: 0;
  border: 0;
  border-radius: 50%;
  background: var(--tm-dot);
  cursor: pointer;
  transition: background var(--dur-ui) var(--ease-out),
              transform var(--dur-ui) var(--ease-out);
}

/* THREE STATES, NOT TWO. The pinned desktop deck walks through the
   amenities in order, so which ones you have already passed is real
   information there; the carousel only ever has one dot lit and the
   is-done rule simply never matches more than the ones behind it.
   Both classes are written by script.js. */
.offer__dot.is-done { background: var(--color-text-secondary); }
.offer__dot.is-on {
  background: var(--color-text-accent);
  transform: scale(1.3);
}

.offer__dot:focus-visible {
  outline: 2px solid var(--color-border-focus);
  outline-offset: 4px;
}
@media (hover: hover) and (pointer: fine) {
  .offer__dot:hover { background: var(--color-text-accent); }
}

/* The dot is 8px, which is nowhere near a touch target. This
   pseudo-element is the real hit area and it is invisible — drawing
   44px circles instead would make the rail four times as wide as the
   thing it is indicating. inset is -0.5rem rather than the
   testimonials' -1rem because these dots sit 16px apart: -1rem would
   overlap the neighbour's hit area and the wrong amenity would
   answer the tap. 8 + 16 = 24px square, which is the AA target, and
   with the 16px gap the squares meet without overlapping. */
.offer__dot::after {
  content: "";
  position: absolute;
  inset: -0.5rem;
}

/* ---- the phone / no-pin layout, which is the BASE -------------- */
/* Written first and unconditionally, so it is what a narrow screen,
   a reduced-motion reader and a page with no JavaScript all get.

   A SLIDING CAROUSEL, not a column: one card at a time, snapping to
   the 16px gutter with a sliver of the next one showing past the
   right edge. Same shape as the stays rail, and deliberately so —
   both sections start on the same line and both say there is more
   the same way, with a peek rather than a control.

   It is a plain scroll container, which is the point: it works with
   no JavaScript at all. The script only lights the rail underneath
   to say where you are. */
.offer__items {
  display: flex;
  gap: var(--space-4);
  overflow-x: auto;
  scroll-snap-type: x mandatory;
  -webkit-overflow-scrolling: touch;
  scrollbar-width: none;

  /* FULL BLEED, with its own 16px gutter.
     The stage already pads its contents by --container-x, so a
     carousel laid out inside that padding starts 16px in and then
     adds its own — which read as a cropped gap down both sides. The
     negative margin cancels the stage's padding so the scroller spans
     the whole screen, and the padding here is the only gutter left.

     scroll-padding matches it, so a snapped card lands on the 16px
     line rather than flush against the edge of the screen. */
  margin-inline: calc(var(--container-x) * -1);
  /* THE BLOCK PADDING IS SHADOW ROOM, not spacing. overflow-x: auto
     computes overflow-y to auto as well, so this scroller clips its
     children vertically whether or not it ever scrolls that way — and
     --offer-lift reaches 62px below the card (30px down, 64px blur,
     32px pulled back by the spread) and 2px above it. At the 32px
     this used to carry, the shadow was cut off mid-fade and drew a
     hard horizontal line across the full width of the section.

     If you retune --offer-lift, retune these two numbers with it:
     below = offset + blur + spread, above = blur - offset + spread. */
  padding: var(--space-2) var(--space-3) var(--space-9);
  scroll-padding-inline: var(--space-3);
}
.offer__items::-webkit-scrollbar { display: none; }
.offer__item {
  /* The gutter it starts on, the gap after it, and the 40px sliver of
     the next card, all taken off the screen — the same three terms
     and the same 40px as .stay-card, so the two carousels cut their
     right edge on the same line.

     100vw rather than a percentage on purpose: the scroller is full
     bleed, so a percentage would resolve against its content box and
     the gutter would be counted twice. */
  flex: 0 0 calc(100vw - var(--container-x) - var(--space-4) - 2.5rem);
  /* START, not centre. The card lands on the gutter the heading above
     it starts on; centring it put the first card adrift of everything
     else in the section. scroll-padding-inline above is what keeps the
     snap off the screen edge. */
  scroll-snap-align: start;
}
.offer__item { position: relative; }
.offer__text {
  position: absolute;
  inset: auto 0 0 0;
  z-index: 2;
  padding: clamp(var(--space-3), 5vw, var(--space-5));
  pointer-events: none;
}
/* Reversed out, because here the text is ON the photograph. The
   desktop layout puts it beside the card instead and takes these
   back off — see the pinned block. */
.offer__text .offer__index { color: var(--color-overlay-fg); }
.offer__text .offer__title { color: var(--color-overlay-text); }
.offer__text .offer__lead  { color: var(--color-overlay-fg); }
.offer__text .offer__desc  { color: var(--color-overlay-text); }
.offer__card { aspect-ratio: 4 / 5; }
.offer__veil { display: none; }
/* The rail stays on the carousel: with one card on screen at a time
   it is the only thing saying how many there are and which one you
   are on. script.js lights it from the scroll position. Its icons are
   still buttons, and they scroll the carousel. */

@media (min-width: 600px) {
  .offer__card {
    aspect-ratio: 3 / 2;
  }
}

/* ---- the pinned stage ------------------------------------------ */
/* THE GATE IS FOUR THINGS AT ONCE: wide enough for a card with text
   beside it, tall enough for a pinned stage to be worth pinning,
   .reveal-on (the class the inline script in <head> only adds where
   there is an IntersectionObserver and the reader has not asked for
   less motion), and .is-live, which script.js adds only once the
   driver has actually started.

   THE LAST ONE IS NOT BELT AND BRACES. These rules hold every item
   at opacity 0 and let the driver reveal one — so without it, a page
   whose script failed to run would show an empty section with
   nothing but the icon rail in it. That happened. Read the long note over the scroll reveals
   before changing any of them — the extra track height is a hidden
   state and must not be written into a plain selector. */
@media (min-width: 900px) and (min-height: 640px) {
  .reveal-on .section--offer.is-live {
    /* The track. --offer-pace screens per amenity, and --offer-count
       is written by script.js from the number of items it finds, so
       adding a fifth <article> lengthens the track on its own.

       1.25, not 1. At one screen each the hand-over has to happen in
       the same scroll the reader spends reading the card, and the
       deck feels hurried — the reference gives each amenity about
       1.45. This is the compromise: slower than one, and short of
       the reference, because this page already opens with two pinned
       full-screen sections before it. Raise it if the deck still
       feels rushed; it costs page length and nothing else. */
    height: calc(var(--offer-screen, 100svh) * var(--offer-count, 4) * var(--offer-pace, 1.25));
  }

  .reveal-on .section--offer.is-live .offer__stage {
    position: sticky;
    top: 0;
    height: var(--offer-screen, 100svh);
    display: flex;
    flex-direction: column;
    overflow: hidden;
  }

  /* ABOVE THE DECK, and it has to be now the card is large enough to
     reach it. A card flying off the top passes BEHIND the heading
     rather than across it — which is both what the reference does and
     the only way the heading keeps a ground it can be read against.

     The deck is CLIPPED to its own box rather than the heading being
     veiled, which was the first attempt. Clipping is the honest
     version: a card leaving does not fade out behind a wash, it
     travels up and is cut off at the line where the heading's space
     begins — so the heading never has a photograph behind it at all,
     at any scroll position. See overflow on .offer__items. */
  .reveal-on .section--offer.is-live .offer__head {
    position: relative;
    z-index: 2;
    flex: 0 0 auto;
    /* 48px BELOW, AND THAT IS THE WHOLE GAP TO THE CARD. The items box
       under this has no top padding in the pinned layout and the card
       sits at the top of it rather than floating in the middle, so
       this one number is the distance from the intro's last line to
       the photograph at every window height. It was 32 plus 8 plus
       whatever the centring left over, which was a different gap on
       every monitor.

       ABOVE, 48px at the least, the page's floor for a section's edge
       (2026-11-01). The floor was 40px, which a window under 800px
       tall reached (41px at 1280 x 680). */
    padding-block: clamp(var(--space-7), 6vh, var(--space-9)) var(--space-7);

    /* FADED OUT BY THE SCROLL, not by a class. script.js writes --head-o
       on the stage from the deck position: 1 while the reader is
       arriving and reading the first card, down to 0 over the first
       40% of the first hand-over, and back up again when they scroll
       up to the start. It is the price of letting a card leave over
       the heading rather than being clipped under it — the heading
       gets out of the way first. No transition: the scroll IS the
       timeline, as with everything else in this deck. Unset outside
       the pinned layout, so the phone carousel keeps its heading. */
    opacity: var(--head-o, 1);
    will-change: opacity;
  }


  /* Every item in the same grid cell, and the card is now the WHOLE
     item rather than the middle of three columns. The text used to
     sit beside it, which capped the card at about half the frame;
     moving the text onto the card frees the other half and the card
     grows into it. */
  .reveal-on .section--offer.is-live .offer__items {
    position: relative;
    flex: 1 1 auto;
    min-height: 0;
    display: grid;
    /* No padding on either edge. The base rule's 8px of shadow room
       above the carousel would add to the head's 48 and make it 56;
       the bottom is clipped on purpose — see clip-path below. */
    padding-block: 0;

    /* OPEN AT THE TOP, CLOSED AT THE BOTTOM AND SIDES. This was
       overflow: hidden, which clipped a departing card at the top edge
       of this box — the line where the heading's space begins — so the
       card was sliced in half on its way out and never actually left.
       It read as a glitch, and it was one.

       The card is meant to sail up over the heading and out of the top
       of the screen now. A clip-path with a negative top inset gives
       it the whole stage to travel through while still cutting the
       bottom exactly where overflow did, which is what keeps the two
       cards stacked behind the front one from spilling onto the dot
       rail. clip-path creates no scroll container and no containing
       block, so the sticky stage and the absolutely placed captions
       are untouched.

       The heading's contrast problem that the old clip solved is
       solved differently: script.js fades .offer__head out before the
       first card starts to leave — see --head-o on it below. */
    overflow: visible;
    clip-path: inset(-100vh 0 0 0);

    /* Its own stacking context, ABOVE the heading. The cards carry
       z-index 6 down to 1 in the markup; without this the first four
       would pass over the heading and the last two under it. With it,
       every card crosses on top, which is the reading the motion wants:
       the card leaves over everything, and the heading simply dissolves
       beneath it. */
    z-index: 3;

    /* EXPLICIT WIDTH, because the base rule gives this box
       margin-inline: auto and an auto cross-axis margin stops a flex
       child stretching — it becomes content-sized instead, and since
       everything inside it is width:100% the percentage had nothing
       to resolve against and the whole stack computed to zero. With
       a definite width the auto margins go back to doing what they
       were for, which is centring what is left over. */
    width: 100%;
  }
  .reveal-on .section--offer.is-live .offer__item {
    grid-area: 1 / 1;
    /* FLEX, not grid with place-items:center. Under centred grid
       items the card's width is content-based, and the card's only
       children are absolutely positioned — so `width: min(100%, …)`
       had nothing definite to resolve the percentage against and the
       card computed to 0 x 0. In a flex row the percentage resolves
       against the container's content box, which is definite. */
    display: flex;
    /* TOP, not centre. The card used to be centred in whatever the
       items box had left over, which put a different gap under the
       heading on every monitor. Pinned to the top, the gap is the
       heading's own 48px bottom pad and nothing else, and any leftover
       height falls below the card, above the dot rail, where it costs
       nothing. .offer__text below is positioned to match. */
    align-items: flex-start;
    justify-content: center;
    max-width: var(--container-max);
    margin-inline: auto;
    width: 100%;
    pointer-events: none;

    /* EVERY ITEM IS DRAWN AT ONCE. This used to fade one in and the
       rest out, which is not what the deck does — the cards are a
       physical stack: the ones behind sit smaller and lower so their
       top edges peek out beneath the front one, and the front one
       flies UP and off as the next rises into its place. Nothing
       fades except the text.

       z-index comes from the markup, descending, so an exiting card
       passes OVER the one taking its place rather than under it. */
  }
  .reveal-on .section--offer.is-live .offer__item.is-active {
    pointer-events: auto;
  }

  /* THE TWO NUMBERS THE DECK IS MADE OF. --card-s and --card-y are
     written by script.js on the ITEM on every frame the section is on
     screen, continuously rather than in steps — the card travels a
     long way and a quantised version reads as a stutter, unlike the
     hero's clip which only moves a few pixels. They are on the item
     rather than the card so the caption below can read the same two
     values and move with it.

     No transition, for the same reason: the scroll IS the timeline.
     A transition here would fight it and lag behind the thumb. */
  /* SIZED BY BOTH AXES, and it has to be. aspect-ratio alone with a
     width would overflow a short viewport; max-height alone would
     leave a wide window half empty. Given both, the browser takes
     whichever binds first and the ratio survives either way — so the
     card is as large as the stage allows at every size, which is the
     point of moving the text onto it. */
  .reveal-on .section--offer.is-live .offer__card {
    flex: 0 0 auto;
    /* THE WIDTH IS BOUNDED BY THE AVAILABLE HEIGHT, which is why
       there is a viewport calc in here rather than a plain cap.

       A 3:2 box sized by width gets its height from the ratio, and
       max-height cannot rein that back in without breaking the ratio
       — the browser clamps the height and leaves the width alone. So
       the height limit has to be expressed as a width limit instead:
       the stage is one screen, the header and the rail take about
       520px of it between them, and a 3:2 card in what is left is at
       most 1.5 x (100vh - 520px) wide.

       520, UP FROM 460, and the difference is measured. The header
       grew by 16px when its gap to the card was fixed at 48, and with
       the intro showing (windows over 820px tall) it runs to about
       250px; the dot rail is about 90. At 1440x900 the old figure put
       the card's bottom edge 19px under the rail, where the clip cut
       its rounded corners off. 520 leaves 21px there, 11px at
       1440x1000 and 1600x1000, and 60 or more everywhere else that
       was tried. Re-measure if the header gains a line.

       The 64rem cap is what stops it running the full width of a very
       wide, very tall monitor. The reference does the same thing with
       the same shape of calc, for the same reason. */
    width: min(100%, 64rem, calc(150vh - 560px));   /* 560 on Walden: the two-line intro, see README */
    aspect-ratio: 3 / 2;
    transform: translateY(var(--card-y, 0px)) scale(var(--card-s, 1));
    transform-origin: center center;
    will-change: transform;
    backface-visibility: hidden;
  }

  /* Nothing fades in this deck any more — the caption rides its card
     at full strength; see the note in script.js. Its transform is set
     once, in the rule further down that also centres it. */
  .reveal-on .section--offer.is-live .offer__text {
    will-change: transform;
  }
  .reveal-on .section--offer.is-live .offer__veil { display: block; }

  /* The text is on the photograph now, so the scrim is carrying its
     contrast rather than just giving the picture a foot. Same stops
     as the rem ramp on the base .offer__scrim rule, which this
     restates so the two cannot drift apart unseen. */
  .reveal-on .section--offer.is-live .offer__scrim {
    background: linear-gradient(0deg,
      var(--offer-scrim-4) 0, var(--offer-scrim-3) 7rem,
      var(--offer-scrim-2) 11.5rem, var(--offer-scrim-1) 14.5rem,
      var(--offer-scrim-0) 17rem);
  }
  /* WALDEN: THE CAPTION HAS A SENTENCE, so it is a third taller than
     the template's and the 12px index, the string with the 4.5:1 bar,
     tops out higher. The ramp keeps the template's spacing and moves
     up with it; the figures were measured off the card's foot on this
     build and are recorded beside the index height in the README. */
  .reveal-on .section--offer.is-live .offer__scrim {
    background: linear-gradient(0deg,
      var(--offer-scrim-4) 0, var(--offer-scrim-3) 11.5rem,
      var(--offer-scrim-2) 16rem, var(--offer-scrim-1) 19rem,
      var(--offer-scrim-0) 21.5rem);
  }
  /* A LIGHTER FOOT FOR ONE CARD. data-offer-scrim="light" on an item
     swaps in a thinner ramp for a clip whose action sits low in the
     frame: the Event Lodge dinner (Brandon, 2026-10-02: "too dark, I
     can't see what's happening in the video"). 0.70 at the foot and
     0.54 under the index against the standard 0.90 and 0.72, which is
     as far as that pale room allows; measured on this build, see the
     README. */
  .reveal-on .section--offer.is-live .offer__item[data-offer-scrim="light"] .offer__scrim {
    background: linear-gradient(0deg,
      rgba(var(--color-overlay-scrim-rgb), 0.70) 0,
      rgba(var(--color-overlay-scrim-rgb), 0.54) 12.5rem,
      rgba(var(--color-overlay-scrim-rgb), 0.34) 15rem,
      var(--offer-scrim-0) 17.5rem);
  }

  /* ON THE CARD, at its foot — the same place the phone puts it, so
     both layouts read the same way and there is one set of overlay
     colours rather than two. It is positioned against the ITEM rather
     than nested in the card, so the card's overflow clip and its
     stacking never touch the type — but it is LOCKED to the card's
     motion: it is the same box, and it takes the same translateY and
     scale from the same two custom properties, so wherever the deck
     maths sends the photograph, the caption goes with it. It used to
     hold still and rely on its crossfade to hide the mismatch; once a
     departing card travelled the full height of the stage, the caption
     was left hanging in the air with the card sliding out from under
     it. A client build caught it.

     --left and --right are the horizontal end it hangs off. That is
     all the alternation does now; it used to decide which side of
     the frame the text column took. */
  .reveal-on .section--offer.is-live .offer__text {
    position: absolute;
    left: 50%;
    top: 0;
    /* THE SAME BOX AS THE CARD, so "the foot of the card" is a place
       this element can actually find. Both start at the top of the
       item, both are centred across it, and both are min(100%, 64rem)
       at 3:2 capped by height, so the two boxes coincide at every
       viewport. Matching the card's geometry is what lets the text
       hang off its bottom edge without being a child of it. */
    width: min(100%, 64rem, calc(150vh - 560px));   /* 560 on Walden: the two-line intro, see README */
    aspect-ratio: 3 / 2;
    display: flex;
    flex-direction: column;
    justify-content: flex-end;
    padding: clamp(var(--space-4), 3vw, var(--space-6));
    max-width: none;

    /* The centring translate and the card's own motion are ONE
       declaration. translate(-50%, 0) puts this box exactly where the
       flex-centred, top-aligned card is; translateY and scale are the
       card's transform verbatim, read from the same --card-y and
       --card-s the item carries. Translations commute with the origin
       shift and the scale is about the box's own centre in both, so
       the two boxes coincide at every frame. Set transform in two
       rules and the second silently wins — keep it here. */
    transform: translate(-50%, 0) translateY(var(--card-y, 0px)) scale(var(--card-s, 1));
    transform-origin: center center;
  }
  .reveal-on .section--offer.is-live .offer__text--right { align-items: flex-end; text-align: right; }

  /* padding-block-start replaces the shadow room the base layout puts
     under the card — the pinned deck sets .offer__items padding-bottom
     to 0 because it clips the deck there on purpose. */
  .reveal-on .section--offer.is-live .offer__dots {
    display: flex;
    flex: 0 0 auto;
    padding-block-start: var(--space-6);
  }

  /* The intro is the first thing to go on a short window — it is the
     one string in the header the section can be read without. */
  @media (max-height: 820px) {
    .reveal-on .section--offer.is-live .offer__intro { display: none; }
  }
}

/* 6 · Local favourites — an editorial spread
   ------------------------------------------------------------
   (2026-10-31.) It was four equal portrait cards in one even row,
   each with a near solid black band across its foot: the same block
   four times over, and the most generic shape on the page. Now it is
   laid out like a magazine spread. On a desktop the heading is a
   column of its own on the left, sticky, so it stays beside the
   photographs while they pass; the photographs run in two columns on
   the right, the second set lower than the first and drifting
   against it as the page scrolls. It is the one left aligned header
   on the page, which is the point: every other section opens
   centred, and the stays rail above is a row and the map below is a
   band, so a staggered gallery is a third shape rather than a repeat.

   ANY NUMBER OF PLACES. Odd places take the left column and even ones
   the right, in reading order, so three, four, five or six all lay
   themselves out and nothing is placed by count. A lone place takes
   the full width.

   On a phone it is a plain stack under a centred heading, the same as
   every other section there: two columns at 375px would be two
   160px photographs with a 24px name across each. */
.local {
  display: grid;
  gap: var(--space-6);
}
.local__intro { text-align: center; }
.local__intro .subhead { margin-inline: auto; margin-bottom: 0; }

.local__grid {
  display: grid;
  gap: var(--space-3);

  /* How far the right column sits below the left, and how far it
     drifts either side of that as the section is scrolled past (see
     THE DRIFT below). Both only apply from 640px, where there are two
     columns to offset. */
  --local-stagger: clamp(5rem, 11vw, 9rem);
  --local-travel:  clamp(1.5rem, 3vw, 3rem);
}

/* THE CARD. A photograph with its name on it, clipped to the page's
   one corner radius. The card holds the clip, not the picture, so the
   linked card's hover zoom stays inside the corners. The ground is
   what shows while the photograph loads.

   SCOPED data-theme="dark" IN THE MARKUP, as the stay cards are, which
   is what makes the gradient dark and the name light whatever the
   page is set to: the gradient composes the theme's overlay triplet,
   and under that scope it is the dark set. */
.tall-card {
  position: relative;
  display: block;
  border-radius: var(--radius-lg);
  overflow: hidden;
  isolation: isolate;
  background: var(--color-bg-tertiary);
}

/* A fixed height on the phone stack, because at full width the 4:5
   below would make each photograph ~430px tall and put four of them
   over 1700px of scrolling. --tall-focal on a card aims its crop
   (style="--tall-focal: 50% 66%"), the same way as --stay-focal: the
   stack crops every photograph to a landscape band, and a portrait
   one wants its subject aimed at. */
.tall-card__img {
  display: block;
  width: 100%;
  height: 18rem;                          /* 288px */
  object-fit: cover;
  object-position: var(--tall-focal, 50% 50%);
}

/* THE NAME, AND WHAT IT IS READ AGAINST. It was a band, near solid
   black for the height of the words and fading through 48px above
   them, which read as a black bar across every card. It is a long
   ease now, clear at the top of an 80px run up and darkening all the
   way to the foot, so the photograph shows through it and the eye
   reads light falling off rather than a strip.

   Contrast is measured where the TOP of the words sits, the lightest
   point under them. The caption box is the run up plus the words plus
   16px, so a one line name's top is about 42% of the way up the box
   and a two line name's about 53%; the ramp still holds about 0.63
   of the near black there. Measured 2026-10-31 over a pure white
   photograph, at the top of the words: a one line name 6.6:1, a two
   line name 5.5:1. The text shadow is a second line, not the first: it
   catches a hot spot the gradient cannot flatten.

   The name is the display face now, at the subsection role's 24px,
   and it may wrap to a second line, balanced. It used to be held to
   one line and sized per build with a container query factor so the
   widest name would fit; at these widths no name needs that, and a
   two line name simply raises the gradient with it. Two lines is the
   cap, and an ellipsis the net beyond it. */
/* A grid rather than a row: the name in the first column and a
   linked card's arrow in the second, both on the bottom row, and the
   row above the name left for the rule that answers the index on a
   desktop (THE SPOTLIGHT, below). With no rule drawn, that row has
   nothing in it and takes no height. */
.tall-card__caption {
  position: absolute;
  inset: auto 0 0 0;
  display: grid;
  grid-template-columns: minmax(0, 1fr) auto;
  align-items: end;
  column-gap: var(--space-3);
  padding: var(--space-10) var(--space-4) var(--space-4);   /* 80px run up, 24px around the words */
  background: linear-gradient(to top,
      rgba(var(--color-overlay-scrim-rgb), 0.80) 0%,
      rgba(var(--color-overlay-scrim-rgb), 0.72) 30%,
      rgba(var(--color-overlay-scrim-rgb), 0.62) 55%,
      rgba(var(--color-overlay-scrim-rgb), 0.38) 75%,
      rgba(var(--color-overlay-scrim-rgb), 0.14) 90%,
      rgba(var(--color-overlay-scrim-rgb), 0)    100%);
}

.tall-card__title {
  grid-column: 1;
  grid-row: 2;
  display: -webkit-box;
  -webkit-box-orient: vertical;
  -webkit-line-clamp: 2;
  overflow: hidden;
  color: var(--color-overlay-text);
  text-align: left;
  text-wrap: balance;
  text-shadow: 0 1px 2px rgba(var(--color-overlay-scrim-rgb), 0.4);
}

/* A LINKED CARD SAYS SO. A favourite is a <figure> and goes nowhere
   unless the client gave a link for that place (2026-10-23; see
   index.html), so nothing on a figure suggests a click. An <a> gets
   an arrow at the foot of its caption, Phosphor's arrow-up-right at
   its bold weight (phosphoricons.com) drawn as a mask so it takes the
   name's colour, and on a pointer that can hover, the photograph
   leans in and the arrow nudges toward where it goes. The press is on
   the card, on `scale`, so it never fights the drift's `translate`.
   The ring is drawn outside the card: an outline is not clipped by
   the card's own overflow. */
a.tall-card .tall-card__caption::after {
  content: "";
  grid-column: 2;
  grid-row: 2;
  width: 1.25rem;
  height: 1.25rem;
  margin-bottom: var(--space-1);
  background: var(--color-overlay-text);
  -webkit-mask: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 256 256' fill='none' stroke='%23000' stroke-width='24' stroke-linecap='round' stroke-linejoin='round'%3E%3Cline x1='64' y1='192' x2='192' y2='64'/%3E%3Cpolyline points='88 64 192 64 192 168'/%3E%3C/svg%3E") center / contain no-repeat;
          mask: url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 256 256' fill='none' stroke='%23000' stroke-width='24' stroke-linecap='round' stroke-linejoin='round'%3E%3Cline x1='64' y1='192' x2='192' y2='64'/%3E%3Cpolyline points='88 64 192 64 192 168'/%3E%3C/svg%3E") center / contain no-repeat;
  transition: translate var(--dur-ui) var(--ease-out);
}
a.tall-card { transition: scale var(--dur-press) var(--ease-out); }
a.tall-card:active { scale: 0.98; }
a.tall-card .tall-card__img { transition: scale 700ms var(--ease-out); }
a.tall-card:focus-visible { outline-offset: 3px; }

@media (hover: hover) and (pointer: fine) {
  a.tall-card:hover .tall-card__img { scale: 1.04; }
  a.tall-card:hover .tall-card__caption::after { translate: 2px -2px; }
}

/* ---- two columns, from 640px -----------------------------------
   The heading goes left aligned over the photographs, and the
   photographs go two up at 4:5, the right column set --local-stagger
   lower than the left. The offset is a translate, so it moves the
   picture and not the grid, and the grid's own bottom padding gives
   it the room back: without it the last right hand card would hang
   over the section below. */
@media (min-width: 640px) {
  .local__intro { text-align: left; }
  .local__intro .subhead { margin-inline: 0; }

  .local__grid {
    grid-template-columns: repeat(2, minmax(0, 1fr));
    column-gap: var(--space-4);
    row-gap: var(--space-6);
  }
  .local__grid:has(> :nth-child(2)) { padding-bottom: var(--local-stagger); }
  .local__grid > :nth-child(even) { translate: 0 var(--local-stagger); }
  .local__grid > :only-child { grid-column: 1 / -1; }

  .tall-card__img {
    height: auto;
    aspect-ratio: 4 / 5;
  }
  .local__grid > :only-child .tall-card__img { aspect-ratio: 3 / 2; }
}

/* THE DRIFT. script.js writes --local-drift on the grid, -1 as the
   section comes up from under the fold to 1 as it leaves over the
   top, the same reading the stay rail's parallax takes, and the right
   column rides it --local-travel either side of its offset. It moves
   up a little faster than the page, so it reads as the nearer of two
   layers and the spread has depth without anything pinning or taking
   over the scroll. The rail above drifts its photographs inside their
   frames; this drifts whole cards, so the two sections do not move
   the same way twice running.

   The grid's padding is NOT grown by the travel, although at -1 the
   column sits a full travel below its offset. By the time the foot of
   the section is on screen the drift is past 0 (the gallery is taller
   than the screen, so its bottom edge only arrives once more than
   half of it has gone by), and the column is back above the padding
   line; with the travel added as well, it left 100-130px of white
   under the gallery on a desktop. A two place gallery shorter than
   the screen can hang a few px into the section's own padding, which
   is 64px. Measured 2026-10-31 with four places: 57-89px under the
   lowest card at 1440, 1024 and 768, depending on the scroll.

   Behind .reveal-on like every other scroll effect: a reader who
   asked for less motion gets the still offset. -1 is the fallback,
   because it is where a section below the fold belongs, so nothing
   jumps when the script's first answer arrives. */
@media (min-width: 640px) {
  .reveal-on .local__grid > :nth-child(even) {
    translate: 0 calc(var(--local-stagger) - var(--local-drift, -1) * var(--local-travel));
  }
}

/* ---- the spread, from 1024px -----------------------------------
   The heading takes a column of its own, 20rem at most, which is the
   index's longest name with room either side of it, and the
   photographs take the rest: a third of the container left the column
   mostly air and the cards smaller than they need be. The column
   holds still beside the photographs while they pass. Sticky
   rather than pinned: it rides inside its own grid cell, so it lets
   go on its own when the gallery ends and takes no scroll from the
   page. align-self: start, or the cell stretches to the gallery's
   height and there is nothing for it to stick within. */
@media (min-width: 1024px) {
  .local {
    grid-template-columns: minmax(0, 20rem) minmax(0, 1fr);
    column-gap: var(--space-10);
    align-items: start;
  }
  .local__intro {
    position: sticky;
    top: var(--space-12);
  }
}

/* THE INDEX. A heading and one line would leave the sticky column
   a short block over a screen of white, so the column carries the
   places' names as well: the text half of the spread, and every name
   on the page at a glance before the photographs have scrolled past.
   script.js writes it from the cards' own titles, so there is nothing
   to keep in step, and only a desktop shows it; below 1024px the
   heading sits over the gallery and a list of the names under it
   would only say them twice.

   The name whose card is nearest the middle of the screen is lit
   (data-active, set by script.js as the page scrolls): full ink, and
   its circle fills. The rest are the secondary ink, 5.9:1, so the
   column reads as a list that something is moving down rather than
   four loose lines. Colour only: a weight change would re-set the
   name's width every time the light moved. A click brings that
   place's card to the middle of the screen (script.js). Each row is
   44px tall, the target size, not the text's.

   THE CIRCLES (2026-11-01) replaced a rule ahead of each name, a stub
   that ran out to full length when lit. Each holds the place's glyph
   (index.html, THE GLYPH). At rest it is the stays facts' pill in a
   circle, the accent's faint wash and outline, with the glyph in the
   name's own ink so four glyphs do not outweigh four names. Lit, it
   fills with the solid accent and the glyph turns white, which is the
   full-length rule's job: one row plainly the one being pointed at. */
.local__index { display: none; }

@media (min-width: 1024px) {
  .local__index {
    display: grid;
    gap: var(--space-2);                  /* 8px, so 40px circles in 44px rows do not touch */
    margin: var(--space-7) 0 0;
    padding: 0;
    list-style: none;
  }
  /* The display face at its regular weight, the same face as the
     names on the photographs, so the column reads as a contents list
     for the spread rather than a menu. Regular, not the face's
     semibold, or four names would outweigh the heading over them. */
  .local__index a {
    position: relative;
    display: flex;
    align-items: center;
    gap: var(--space-3);                  /* 16px, circle to name */
    min-height: 2.75rem;                  /* 44px */
    font-family: var(--font-display);
    font-size: var(--fs-text-xl);
    font-weight: var(--fw-regular);
    line-height: var(--lh-text-xl);
    color: var(--color-text-secondary);
    text-decoration: none;
    transition: color var(--dur-ui) ease;
  }
  .local__mark {
    flex: none;
    display: grid;
    place-items: center;
    width: 2.5rem;                        /* 40px */
    height: 2.5rem;
    border-radius: 50%;
    border: 1px solid color-mix(in oklab, var(--accent-300) 30%, transparent);
    background: color-mix(in oklab, var(--accent-300) 8%, transparent);
    transition: background-color 320ms var(--ease-out),
                border-color 320ms var(--ease-out),
                color 320ms var(--ease-out);
  }
  .local__mark svg {
    width: 1.25rem;                       /* 20px */
    height: 1.25rem;
  }
  .local__index a[data-active] { color: var(--color-text-primary); }
  .local__index a[data-active] .local__mark {
    border-color: var(--color-bg-accent-solid);
    background: var(--color-bg-accent-solid);
    color: var(--color-text-on-solid);
  }
  .local__index a:focus-visible { outline-offset: 2px; border-radius: var(--radius-sm); }
}

/* THE SPOTLIGHT. The index and the gallery light together: whichever
   place is lit in the index is lit in the gallery too, so the eye can
   go from a name to its photograph without reading. script.js marks
   the pair data-active (the card nearest the middle of the screen, or
   the one a pointer or keyboard focus is resting on, by name or by
   photograph) and sets data-spotlight on the gallery once it has
   built the index; without the index there is nothing to answer, so
   none of this applies below 1024px or without the script.

   Two things say it on the card. The rule: every caption carries a
   32px rule, a stub at rest and run out to full length when lit,
   over the same 320ms on the same curve as the index's circle fills,
   so the two hand over at the same moment. (The index had the same
   rule until its circles, 2026-11-01.) And the light: the other photographs fall back
   under a wash of the near black at 0.4, so the lit one is the
   brightest thing in the gallery. The wash is a layer between the
   photograph and the caption, so the names on the unlit cards keep
   their full ink and their contrast only goes up. Opacity on a layer
   rather than a filter on the photograph, so the change is the
   compositor's and costs no repaint. An ease, not the ease-out: this
   is light changing, not something arriving. */
@media (min-width: 1024px) {
  .local__grid[data-spotlight] .tall-card::before {
    content: "";
    position: absolute;
    inset: 0;
    background: rgba(var(--color-overlay-scrim-rgb), 0.4);
    pointer-events: none;
    transition: opacity 400ms ease;
  }
  .local__grid[data-spotlight] .tall-card[data-active]::before { opacity: 0; }

  .local__grid[data-spotlight] .tall-card__caption::before {
    content: "";
    grid-column: 1;
    grid-row: 1;
    width: var(--space-5);
    height: 1px;
    margin-bottom: var(--space-3);
    background: var(--color-overlay-text);
    transform: scaleX(0.35);
    transform-origin: left center;
    transition: transform 320ms var(--ease-out);
  }
  .local__grid[data-spotlight] .tall-card[data-active] .tall-card__caption::before { transform: none; }
}

@media (min-width: 1024px) and (hover: hover) and (pointer: fine) {
  .local__index a:hover { color: var(--color-text-primary); }
}


/* ============================================================
   8 · TESTIMONIALS
   ------------------------------------------------------------
   A coverflow deck: one card facing you, its two neighbours
   pushed back and turned away in 3D, everything further out
   hidden. The section FOLLOWS THE PAGE — a light band on a light
   build, a dark one on a dark build. It was pinned dark for a
   while, which made it the odd section out on a light page.

   THE CARD HAS TWO STATES: plain when it is the one you are reading
   — the page's own surface, an accent hairline and the lift — and
   accent-tinted when it is beside you, turned, dimmed and blurred.
   The geometry is what marks the active card; the colour only
   confirms it. (Until 2026-10-07 it was the other way round, a tinted
   centre between plain neighbours; a client build reversed it and the
   reversal read better — the sharp card is the clean one.) No
   semantic token pair expresses "this element changes on a class", so
   the card's colours are component-owned below. Everything else is
   on ordinary tokens.

   MEASURED 2026-10-07 over the sky, at 1440 (390 within 0.1), on the
   template's own brand: text colour against the WORST pixel of each
   element's box with its text hidden — stricter than at the glyph.

       heading          8.86   bar 3.0  (large text)
       eyebrow          5.90   bar 4.5
       intro            5.52   bar 4.5
       proof number     9.07   bar 4.5
       proof label      5.63   bar 4.5
       centre quote     9.50   bar 4.5
       centre name      9.50   bar 4.5
       centre source    5.86   bar 4.5
       read more        6.38   bar 4.5

   The old figures (heading 7.35 … intro 4.70) were taken over the
   tinted wash this band had before the sky, and over a tinted centre
   card; a new brand moves all of these, so re-measure after /brand.

   THE SIDE CARDS ARE NOT IN THAT TABLE and measure about 1.1:1,
   which is deliberate rather than an oversight. They are blurred
   and held at half opacity — a peek at what is next, not text
   anybody is asked to read. Their content is fully present in the
   accessibility tree and a reader brings one forward to read it,
   which is the point of the deck. If you ever un-blur them, they
   become readable content and have to be measured.
   ============================================================ */
.section--testimonials {
  position: relative;
  isolation: isolate;
  overflow: hidden;
}

/* THE SKY AS A LAYER. The same ground, worn by other
   bands as an element rather than on the section itself:
   <div class="sky"><div class="sky__glow"></div></div>, aria-hidden.
   The amenities band carries it inside its pinned stage and the stays
   band directly inside the section — see each for why.

   z-index -1 puts it under its parent's content without touching any
   of it, positioned or not, so the parent MUST be a stacking context
   (isolation: isolate, or positioned with a z-index); without one it
   drops behind the parent's own background and vanishes. It clips
   itself, because the glow overhangs by 30% on every side. */
.sky {
  position: absolute;
  inset: 0;
  z-index: -1;
  overflow: hidden;
  pointer-events: none;
}

/* THE SKY. Deeper at the top, the page's own white at the foot, so
   the band opens like a sky over the deck and closes on the hairline
   below without a hard step into the next section.

   SHARED WITH .sky. Every paint rule from here to the drift is
   written for both, so retuning the sky here retunes every band that
   wears it — which is the point. On a dark scope it inverts: the
   brand's 950 for the pale gradient, brand-tinted cloud for white,
   the pattern (if there is one) in light ink. The stays band is
   always that version, because it is pinned dark. */
.section--testimonials,
.sky {
  background: linear-gradient(180deg,
    var(--tm-sky-top)  0%,
    var(--tm-sky-mid)  52%,
    var(--tm-sky-foot) 100%);
}

/* THE PATTERN — off unless --tm-pattern is set (see the token's note).
   A repeating line image at a few percent, masked twice: a radial
   hole behind the deck so the cards sit on calm ground, and a fade
   through the lower half so it never meets the hairline. A static
   image, not a filter, so it costs nothing to scroll. With the
   default `none` this layer paints nothing. */
.section--testimonials::before,
.sky::before {
  content: "";
  position: absolute;
  inset: 0;
  z-index: 0;
  pointer-events: none;
  opacity: var(--tm-lattice-alpha);
  background-image: var(--tm-pattern);
  background-size: var(--tm-pattern-size);
  background-position: center top;
  -webkit-mask-image:
    radial-gradient(ellipse 52% 56% at 50% 60%, transparent 26%, #000 74%),
    linear-gradient(to bottom, #000 0, #000 62%, transparent 98%);
  -webkit-mask-composite: source-in;
  mask-image:
    radial-gradient(ellipse 52% 56% at 50% 60%, transparent 26%, #000 74%),
    linear-gradient(to bottom, #000 0, #000 62%, transparent 98%);
  mask-composite: intersect;
}
[data-theme="dark"] .section--testimonials,
[data-theme="dark"] .sky {
  background: linear-gradient(180deg, var(--brand-950) 0%, var(--color-bg-primary) 100%);
  --tm-cloud: color-mix(in oklab, var(--brand-800) 55%, transparent);
  /* 32, pulled back from 55 when the stays band put this version in
     front of people. At 55 it moved a dark foot by +20 red on a base
     near 40 — about twice as loud as the day sky's bloom moves white —
     and read as a brown smudge under the cards. */
  --tm-sun:   color-mix(in oklab, var(--accent-900) 32%, transparent);
}
[data-theme="dark"] .section--testimonials::before,
[data-theme="dark"] .sky::before { filter: invert(1); }

/* A hairline along the bottom edge, so the band closes on a line
   rather than just stopping. */
.testimonials__rule {
  position: absolute;
  bottom: 0; left: 0; right: 0;
  z-index: 3;
  height: 2px;
  background: linear-gradient(90deg,
    transparent, var(--color-border-accent) 18%,
    var(--color-border-accent) 82%, transparent);
  pointer-events: none;
}

/* CLOUD AND LATE LIGHT, drifting. Three soft white blooms over the
   sky and one warm bloom in the accent low behind the deck — it is
   what stops the band reading as a flat gradient, and the warm one is
   what ties the accent-tinted side cards and the hairline to the
   ground they sit on. inset is negative so the drift never exposes an
   edge.

   It holds still under reduced motion. A 26 second loop is well past
   the five seconds WCAG 2.2.2 allows for unstoppable motion, so this
   is one of the few places on the page where the preference is load
   bearing rather than polite. */
.testimonials__glow,
.sky__glow {
  position: absolute;
  inset: -30%;
  z-index: 0;
  pointer-events: none;
  background:
    radial-gradient(38% 46% at 28% 30%, var(--tm-cloud), transparent 70%),
    radial-gradient(42% 50% at 76% 24%, var(--tm-cloud), transparent 72%),
    radial-gradient(30% 36% at 54% 44%, var(--tm-cloud), transparent 70%),
    radial-gradient(38% 20% at 50% 70%, var(--tm-sun),   transparent 72%);
}
@media (prefers-reduced-motion: no-preference) {
  .testimonials__glow,
  .sky__glow {
    animation: testimonials-drift 26s var(--ease-in-out) infinite alternate;
    will-change: transform;
  }
}
/* WHERE THE MAP FADES INTO IT (2026-11-01). The location band above
   ends in a wash of --tm-sky-top (THE FOOT, in section 7), and the
   drifting clouds here whiten the band's top edge, so the two met on
   a step from green-white to white. A short run of the plain sky
   colour over the clouds, fading out downward, makes this band's top
   edge exactly the colour the map ends on. Only when the map is
   directly above: elsewhere the clouds reach the top as they always
   have. Above the clouds and the pattern, under the heading. */
.section--map + .section--testimonials::after {
  content: "";
  position: absolute;
  inset: 0 0 auto 0;
  z-index: 0;
  height: clamp(6rem, 14vh, 9rem);
  background: linear-gradient(to bottom, var(--tm-sky-top), transparent);
  pointer-events: none;
}

@keyframes testimonials-drift {
  from { transform: translate3d(-3%, -2%, 0) scale(1.05) rotate(0deg); }
  to   { transform: translate3d(3%, 2%, 0) scale(1.12) rotate(4deg); }
}

/* ---- the header ------------------------------------------------ */
.testimonials__head {
  position: relative;
  z-index: 1;
  text-align: center;
  margin-bottom: var(--space-7);
}

.testimonials__head .heading em {
  font-style: normal;         /* upright, colour only — see .hero-offer__title em */
  color: var(--color-text-accent);
}

/* The semantic accent, which brand-contrast.js keeps at AA against
   the page. It was --accent-200 while this band was pinned dark —
   the step solved against near-black — and that is a pale khaki on
   the light band the section carries now. */
.testimonials__head .eyebrow { color: var(--color-text-accent); }

.testimonials__intro {
  max-width: 56ch;
  margin: var(--space-3) auto 0;
  color: var(--color-text-secondary);
}

/* ---- the proof strip ------------------------------------------- */
/* A review platform's logo and one to three stats, centred under the
   intro (2026-10-07, folded back from a client build; the panel this
   deck replaced carried the same pair). Use the platform's own
   full-colour lockup when the band is light, the reversed one when the
   build is dark.

   SIZED BY HEIGHT, NOT WIDTH. A wordmark capped by width ends up as
   tall as its proportions allow: a 4.7:1 lockup under a 7rem cap had
   letters about 11px high. Height is what keeps a wordmark legible, so
   height is set — 32px, then 36px from 900px — and the width follows,
   whatever shape the replacement logo is.

   ONE TO THREE STATS. A wrapping row, so the logo and its stats share
   one line wherever they fit, which on a 360px phone is the logo and
   ONE stat (about 250px together). With two or three, the logo takes
   its own row on a phone and the stats sit side by side under it —
   otherwise the last stat would wrap onto a line by itself. A browser
   without :has() just wraps, which is untidy rather than broken. */
.stats {
  display: flex;
  flex-wrap: wrap;
  justify-content: center;
  align-items: center;
  gap: var(--space-4) var(--space-5);
  margin-top: var(--space-5);
}
.stats__badge { flex: none; }
.stats__badge img { display: block; height: 2rem; width: auto; }
.stat { text-align: center; }
.stat__number { margin-bottom: var(--space-1); font-variant-numeric: tabular-nums; }
.stat__label  { color: var(--color-text-secondary); }
@media (max-width: 639px) {
  .stats:has(.stat + .stat) .stats__badge {
    flex-basis: 100%;
    display: flex;
    justify-content: center;
  }
}
@media (min-width: 900px) {
  .stats { column-gap: var(--space-7); }
  .stats__badge img { height: 2.25rem; }
}

/* ---- the deck -------------------------------------------------- */
.testimonials__stage { position: relative; z-index: 1; }

/* The perspective lives on the viewport, not the deck, so the two
   turned cards share one vanishing point with the centre one. Put it
   on the deck instead and each card gets its own, which reads as
   three unrelated rotations rather than one object. */
.testimonials__viewport {
  position: relative;
  perspective: 2000px;
}

/* WITHOUT JAVASCRIPT THIS IS A COLUMN. Every card is in normal flow,
   every quote is open, and the arrows and dots are not drawn. The
   deck below only exists once the script has added .is-live, which is
   also what stops a no-JS visitor meeting five cards stacked on top
   of each other in one grid cell. */
.testimonials__deck {
  display: flex;
  flex-direction: column;
  align-items: center;
  gap: var(--space-5);
  max-width: var(--container-max);
  margin-inline: auto;
  padding-inline: var(--container-x);
}

/* NO min-height (2026-10-23, from the Gooseberry build). It was
   clamp(340px, 40vw, 440px), sized for long six-line quotes; with
   reviews of one to three lines each ~240px card sat centred in a
   440px box and left about 95px of empty band above and below it. The
   box does not need a floor: every card shares the one grid cell, so
   the deck is already as tall as the tallest review and holds that
   height between them. */
.testimonials__deck.is-live {
  display: grid;
  padding-inline: 0;
  transform-style: preserve-3d;
}

/* ---- the card -------------------------------------------------- */
.testimonial {
  position: relative;
  display: flex;
  flex-direction: column;
  width: min(100%, 33.75rem);
  padding: clamp(var(--space-5), 2.6vw, var(--space-6)) clamp(var(--space-4), 2.4vw, var(--space-6));
  border-radius: var(--tm-radius);
  background: var(--tm-card-bg);
  border: 1px solid var(--tm-card-edge);
  color: var(--tm-card-text);
}

.is-live .testimonial {
  /* Every card in the same grid cell, stacked — the transforms below
     are what separate them again. */
  grid-area: 1 / 1;
  justify-self: center;
  align-self: center;
  width: var(--tm-card-w);
  transform-origin: center center;
  transition:
    transform var(--dur-deck) var(--ease-out),
    opacity   var(--dur-deck) var(--ease-out),
    filter    var(--dur-deck) var(--ease-out),
    background-color var(--dur-reveal) var(--ease-out),
    border-color     var(--dur-reveal) var(--ease-out),
    color            var(--dur-reveal) var(--ease-out);
  will-change: transform, opacity;
}

/* THE ONE YOU ARE READING. Pulled forward, fully opaque, and PLAIN:
   the page's own surface with an accent hairline and the lift. Until
   2026-10-07 this card carried a brand-200 to brand-100 tint and its
   neighbours were plain; a client build reversed that and the
   reversal reads better — the sharp card is the clean one and the
   turned, blurred pair carry the colour.

   The hairline is accent-300 and the wash on the two beside it is the
   same accent ramp (see below), so the whole deck reads in the
   brand's accent. The hairline is a soft line on the card rather than
   a strong one, which is the point of a hairline; what says "this
   one" is still the geometry — the neighbours are turned, pushed
   back, dimmed and blurred.

   Read more on this card uses the semantic accent, which is solved
   against the page ground — and this card IS the page ground, so the
   4.5:1 bar it carries as 12px bold holds. The side cards keep a raw
   step, for the reason given over the old tinted card: the semantic
   step put Read more at 3.70:1 on a 200-step tint. */
.is-live .testimonial.is-center {
  --tm-card-bg: var(--color-bg-primary);
  --tm-card-edge: var(--accent-300);
  --tm-accent: var(--color-text-accent);

  /* NO translateZ, and that is a legibility fix rather than a taste
     one. The viewport above carries perspective: 2000px, so pulling
     this card 40px toward the reader magnifies it by 2000/1960 —
     about 2%. The browser rasterises the card at its layout size and
     then scales that bitmap, so every glyph on the one card anybody
     is actually reading came out softly blurred.

     The depth is already being carried by the other two: they are
     pushed BACK 210px, turned 42 degrees and blurred. This one only
     has to be the sharp, square, un-dimmed one. z-index puts it in
     front; nothing needs to move it in Z to say so.

     will-change is dropped here too — it promotes the card to its
     own layer and compounds the same rounding. */
  transform: none;
  opacity: 1;
  z-index: 3;
  filter: none;
  will-change: auto;
  box-shadow: var(--tm-lift);
}
/* THE WASH, on the two beside it, in the accent: accent-200 to
   accent-100 on a light build, accent-800 to accent-950 on a dark one.
   Their type reads the overlay tokens so it follows the tint's
   polarity, though at 0.5 opacity behind a blur it is a peek at what
   is next rather than text anybody reads. To tint them in the brand
   instead, swap the accent steps for the same brand steps. */
.is-live .testimonial.is-side {
  --tm-card-bg: linear-gradient(160deg, var(--accent-200) 0%, var(--accent-100) 100%);
  --tm-card-text: var(--color-overlay-text);
  --tm-card-muted: var(--color-overlay-fg);
  --tm-accent: var(--accent-800);
}
[data-theme="dark"] .is-live .testimonial.is-side {
  --tm-card-bg: linear-gradient(160deg, var(--accent-800) 0%, var(--accent-950) 100%);
  --tm-accent: var(--accent-200);
}

/* THE TWO BESIDE IT. Turned away, pushed back, dimmed and softly
   blurred — far enough to read as "not this one" and close enough
   that you can see there is more. They are buttons: clicking one
   brings it to the centre. */
.is-live .testimonial.is-side {
  opacity: 0.5;
  z-index: 1;
  filter: blur(2px);
  cursor: pointer;
}
.is-live .testimonial.is-prev { transform: translateX(-74%) translateZ(-210px) rotateY(42deg); }
.is-live .testimonial.is-next { transform: translateX(74%)  translateZ(-210px) rotateY(-42deg); }

.is-live .testimonial.is-side:hover { opacity: 0.72; filter: blur(0.5px); }
.is-live .testimonial.is-side:focus-visible {
  outline: 2px solid var(--color-border-focus);
  outline-offset: 4px;
  opacity: 0.85;
}

/* Everything further out than a neighbour. Kept in the DOM so the
   deck does not reflow as it turns, but taken out of the tree and
   out of reach. */
.is-live .testimonial.is-back {
  opacity: 0;
  z-index: 0;
  pointer-events: none;
  transform: translateZ(-380px) scale(0.82);
  box-shadow: none;
}

/* ---- inside the card ------------------------------------------- */
.testimonial__stars {
  display: flex;
  gap: var(--space-1);
  color: var(--tm-accent);
  margin-bottom: clamp(var(--space-3), 1.8vw, var(--space-4));
}
.testimonial__star { width: 1rem; height: 1rem; flex: 0 0 auto; }

.testimonial__quote {
  font-family: var(--font-body);
  font-size: var(--fs-text-lg);
  line-height: var(--lh-text-lg);
  color: var(--tm-card-text);
  margin: 0 0 var(--space-3);
}

/* SIX LINES, then the button opens the rest. line-clamp needs the
   -webkit- box model even in browsers that support the unprefixed
   property, which is why both are here and why display is box rather
   than block. The clamp is removed by script.js, not by CSS, because
   the button has to be able to put it back. */
.testimonial__quote.is-clamped {
  display: -webkit-box;
  -webkit-box-orient: vertical;
  -webkit-line-clamp: 6;
          line-clamp: 6;
  overflow: hidden;
}

.testimonial__more {
  align-self: flex-start;
  margin-bottom: clamp(var(--space-4), 2vw, var(--space-5));
  padding: 0;
  border: 0;
  background: none;
  font-family: var(--font-body);
  font-size: var(--fs-text-xs);
  font-weight: var(--fw-semibold);
  letter-spacing: var(--ls-wide);
  text-transform: uppercase;
  color: var(--tm-accent);
  text-decoration: underline;
  text-underline-offset: 4px;
  cursor: pointer;
  transition: color var(--dur-ui) var(--ease-out);
}
/* NOT DRAWN UNTIL THE DECK IS LIVE. Without JavaScript the quotes are
   never clamped, so there is nothing for this to open — and a button
   that does nothing is worse than no button. */
.testimonial__more { display: none; }
.is-live .testimonial__more { display: block; }

/* Only the centre card's button does anything; the others are hidden
   from the accessibility tree by script.js and made unclickable here,
   so the deck does not hand a keyboard five identical buttons. */
.is-live .testimonial:not(.is-center) .testimonial__more {
  pointer-events: none;
  visibility: hidden;
}

/* And none at all under a quote that fits its six lines: script.js
   marks the card .is-whole when the clamp cut nothing (2026-10-23).
   display, not visibility, so the card is that much shorter on every
   side of the deck and does not change height as it turns to the
   front. */
.is-live .testimonial.is-whole .testimonial__more { display: none; }

.testimonial__attrib {
  display: flex;
  align-items: center;
  gap: clamp(var(--space-2), 1.2vw, var(--space-3));
  margin-top: auto;
}

/* The guest's initial in a disc. An <img> dropped in its place is
   cropped to the same circle by the overflow. */
.testimonial__avatar {
  flex: 0 0 auto;
  width: clamp(3rem, 4vw, 3.5rem);
  height: clamp(3rem, 4vw, 3.5rem);
  border-radius: 50%;
  overflow: hidden;
  display: grid;
  place-items: center;
  background: var(--tm-avatar-bg);
  color: var(--tm-avatar-text);
  font-family: var(--font-display);
  font-weight: var(--fw-medium);
  font-size: var(--fs-text-lg);
  line-height: 1;
}
.testimonial__avatar img { width: 100%; height: 100%; object-fit: cover; }

.testimonial__ident { display: flex; flex-direction: column; gap: var(--space-1); min-width: 0; }
.testimonial__name {
  margin: 0;
  font-weight: var(--fw-semibold);
  line-height: 1.1;
  color: var(--tm-card-text);
}
/* The source line under the name — "Google review", "Airbnb guest".
   Optional: a build that drops it deletes the <p> from every card
   and leaves this rule, which then matches nothing. */
.testimonial__source {
  margin: 0;
  font-size: var(--fs-text-sm);
  line-height: var(--lh-text-sm);
  color: var(--tm-card-muted);
}

/* ---- arrows and dots ------------------------------------------- */
/* Drawn only once the deck is live — with no script there is nothing
   for them to drive. */
.testimonials__arrow { display: none; }

.is-live-stage .testimonials__arrow {
  position: absolute;
  top: 50%;
  transform: translateY(-50%);
  z-index: 6;
  display: grid;
  place-items: center;
  width: var(--tm-arrow);
  height: var(--tm-arrow);
  border-radius: 50%;
  border: 1px solid var(--color-border-default);
  background: var(--color-bg-primary);
  color: var(--color-text-primary);
  cursor: pointer;
  box-shadow: var(--tm-arrow-lift);
  transition: background var(--dur-ui) var(--ease-out),
              color var(--dur-ui) var(--ease-out),
              border-color var(--dur-ui) var(--ease-out),
              transform var(--dur-press) var(--ease-out);
}
.is-live-stage .testimonials__arrow svg { width: 44%; height: 44%; }
.is-live-stage .testimonials__arrow:hover {
  background: var(--btn-fill);            /* the filled-button set — see --btn-* */
  border-color: var(--btn-fill);
  color: var(--btn-ink);
}
.is-live-stage .testimonials__arrow:active { transform: translateY(-50%) scale(0.93); }
/* FLANKING THE CENTRE CARD, 16px off its edge, not parked at the
   screen edge. They were 2vw in from the viewport, which on a wide
   monitor put them 370px from the card they step: too far. Measured
   from the centre line rather than from the
   edge: half the card, then the gap, then the arrow's own width, so
   the disc ends 16px short of the card at every width the arrows are
   drawn at. They sit over the turned, blurred side cards, which is
   fine — those are a peek at what is next, not text, and the arrow
   carries its own solid ground and shadow. */
/* Walden: 48px off the card's edge rather than the template's 16px, which
   read as clipped to the card (Brandon, 2026-09-23). */
.testimonials__arrow--prev { left:  calc(50% - var(--tm-card-w) / 2 - var(--space-7) - var(--tm-arrow)); }
.testimonials__arrow--next { right: calc(50% - var(--tm-card-w) / 2 - var(--space-7) - var(--tm-arrow)); }

/* 16px between dots, the same retune the amenities rail had (see
   .offer__dots): an 8px dot is far below the 24px AA target, and the
   exemption for a small target is SPACING — a 24px circle centred on
   each must not touch the next target. At 8px apart those circles
   overlapped and Lighthouse's target-size audit failed every dot; at
   16px apart they exactly meet. The gap and the ::after inset below
   are one decision — retune them together. */
.testimonials__dots {
  display: flex;
  justify-content: center;
  gap: var(--space-4);
  margin-top: clamp(var(--space-4), 3vw, var(--space-5));
}
.testimonials__dot {
  width: 0.5rem;
  height: 0.5rem;
  padding: 0;
  border: 0;
  border-radius: 50%;
  background: var(--tm-dot);
  cursor: pointer;
  transition: background var(--dur-ui) var(--ease-out),
              transform var(--dur-ui) var(--ease-out);
}
.testimonials__dot.is-on {
  background: var(--color-text-accent);
  transform: scale(1.3);
}
/* The dot itself is 8px, which is nowhere near a touch target. The
   pseudo-element is the real hit area and it is invisible — the
   alternative is drawing 44px circles, which would make the rail four
   times as wide as the thing it is indicating. -0.5rem: 8 + 16 = 24px
   square, the AA target, and with the 16px gap above the squares meet
   without overlapping. It was -1rem at an 8px gap, and the neighbours'
   hit areas overlapped, so a tap between two dots could answer for
   the wrong review. */
.testimonials__dot::after {
  content: "";
  position: absolute;
  inset: -0.5rem;
}
.testimonials__dot { position: relative; }

@media (max-width: 760px) {
  /* No room beside the heading, and no room for arrows outside a card
     that is already 80vw. The swipe and the dots carry it here. */
  .testimonials__wreath,
  .is-live-stage .testimonials__arrow { display: none; }
  .testimonials__viewport { touch-action: pan-y; }
  .is-live .testimonial { width: min(80vw, 21.25rem); }
  .is-live .testimonial.is-prev { transform: translateX(-58%) translateZ(-150px) rotateY(38deg); }
  .is-live .testimonial.is-next { transform: translateX(58%)  translateZ(-150px) rotateY(-38deg); }
}

/* ============================================================
   4 · MARQUEE
   ============================================================ */
.marquee {
  overflow: hidden;
  background: var(--color-bg-secondary);
  border-top: 1px solid var(--color-border-subtle);
  border-bottom: 1px solid var(--color-border-subtle);
  padding-block: var(--space-3);
}
.marquee__track {
  display: flex;
  align-items: center;
  gap: var(--space-5);
  width: max-content;
  /* 40s, up from 30s. The keyframe travels -50% of the track, and
     script.js doubles the seed until one half covers the viewport,
     so the DISTANCE per cycle is content width rather than a fixed
     number — which makes this a duration, not a speed. Each time
     the doubling lands one more copy, the half doubles and the same
     40s covers twice the ground, so the strip runs faster on a wide
     monitor than on a phone. See the note in script.js if that ever
     needs to be a constant px/s instead. */
  animation: marquee-scroll 40s linear infinite;  /* raise the seconds to slow it down */
}
.marquee__item, .marquee__dot { white-space: nowrap; color: var(--color-text-primary); }
.marquee__dot { opacity: .5; }

@keyframes marquee-scroll { to { transform: translateX(-50%); } }


/* ============================================================
   6 · LOCAL FAVOURITES
   Its rules sit with the photo cards further up, under "6 · Local
   favourites — an editorial spread".
   ============================================================ */

/* ============================================================
   7 · LOCATION — the map is the ground
   ------------------------------------------------------------
   Four layers, back to front, at every width:

     .location-map        the live Google embed, edge to edge, in
                          Google's own colours
     .location-map__veil  the fades over it — white across the top,
                          deep enough for the heading to sit on, and
                          a soft vignette that keeps the eye on the
                          pin
     .location-head       the section heading, centred over the map
                          like every other heading on the page
     .location-panel      the town, the drive times and the route
                          button on frosted glass. Across the foot of
                          the band with the open map between it and
                          the heading; on the container's left edge
                          from 1024px (that media block below), with
                          the pin in the open to its right.

   The frame is a flex column — the heading, then the stage that
   holds the panel — and the stage takes whatever height is left, so
   the open map between the two is what grows when the band does.
   The section is the frame's track: on a phone the frame pins and
   the section is the frame plus a runway (the block at the end of
   this section), so the section itself must never clip — a sticky
   child of an overflow: hidden box has nothing to stick to.

   The map is cropped at the top by --map-bleed. Google's "View
   larger map" card sits in the embed's top-left corner and there is
   no parameter to remove it; cutting the frame's first rows off
   hides it, and because only the top is cut the pin — which Google
   puts at the frame's centre — moves up by half the bleed, which
   the halo's top: accounts for. The bottom is never cropped: the
   attribution and the Google logo live there and stay visible, in
   the strip the section's bottom padding leaves under the panel.
   ============================================================ */
.section--map {
  position: relative;
  padding: 0;                             /* the frame carries the band's padding */

  --map-bleed: 3.5rem;                    /* 56px — clears the small pill a narrow embed draws */

  /* What the heading's fade fades from: the page's ground, so a light
     band has no seam with the white section above it. */
  --map-ground: var(--color-bg-primary);
  --location-show: 1;                     /* 1 = heading and its fade in place; script.js lowers it */

  /* A brand-tinted lift, not --lift-lg: that one is a 42% black built
     for a card over a photograph, and on this pale map it prints a
     grey bruise. The brand's 950 at 18% reads as the panel's own
     shadow on the paper — mixed from the ramp, like --tm-lift, so it
     follows /brand. */
  --location-lift: 0 1.5rem 3rem -1rem color-mix(in oklab, var(--brand-950) 18%, transparent),
                   0 0.125rem 0.375rem color-mix(in oklab, var(--brand-950) 8%, transparent);
}

/* From 600px the embed draws its full address card in that corner,
   about 90px tall, so the crop grows to clear it. Measured on
   2026-10-05 at 600, 700, 768, 900 and 1023; 390 draws the pill. */
@media (min-width: 600px) {
  .section--map { --map-bleed: 7rem; }   /* 112px */
}

/* THE DARK BAND (2026-11-01). The band is light again (taken back the
   same day, as on Dunya), so the rules scoped to [data-theme="dark"]
   here do nothing until the section is given data-theme="dark" in the
   markup; the hairline below is drawn either way. When it is, as the
   stays band is, the heading goes light, the
   accent word takes the dark scope's accent, and the panel's frosted
   plate composes the dark ink set on its own. Two things are set by
   hand here. The ground the heading's fade starts from is the brand's
   darkest step, the stays band's and the footer's, rather than the
   dark scope's neutral page ground, so the band belongs to the brand.
   And the band opens on the page's accent hairline, the way the offer
   band does, because a dark band under a white section has a hard
   edge to mark. It does not close on one: the map fades into the
   reviews band below instead (THE FOOT, with the map).

   THE MAP STAYS IN GOOGLE'S OWN COLOURS. A dark rendition of it
   (inverted, tinted to the brand, lifting on a click) was tried and
   taken out the same day: the band is dark, the map is the real place
   and stays light. So the band reads as a dark heading that fades
   into the map, with the dark panel standing on the map below it. */
/* The section's own ground only ever shows in a gap: the frame and the
   map cover it, but on a phone the pinned frame's edges land on
   fractional pixels and leave a hairline of it at the foot. Dark there,
   against the map's foot running out into the sky, that hairline drew a
   black rule across the seam, so the ground is split: the band's dark
   in the top half, where a gap sits against the dark heading, and the
   sky colour the map ends on in the bottom half. */
.section--map[data-theme="dark"] {
  --map-ground: var(--brand-950);
  background: linear-gradient(to bottom,
    var(--brand-950) 50%, var(--map-foot-to) 50%);
}

/* The band's top edge, drawn on the light band too (Dunya, 2026-11-01):
   Local Favourites above and the light band's white heading fade are
   the same white, so without it the two sections ran together with
   nothing between them. The page's one divider, the same hairline as
   .offer__rule. */
.location__rule {
  position: absolute;
  left: 0; right: 0;
  z-index: 2;
  height: 2px;
  pointer-events: none;
  background: linear-gradient(90deg,
    transparent, var(--color-border-accent) 18%,
    var(--color-border-accent) 82%, transparent);
}
.location__rule--top    { top: 0; }

/* THE FRAME is the band as the reader sees it: everything in the
   section, with the map as its ground. */
.location-frame {
  position: relative;
  isolation: isolate;
  overflow: hidden;
  display: flex;
  flex-direction: column;
  /* A screen's worth on a phone: the heading, the open map with the
     pin in it, the panel, and the attribution strip under it. Plus
     --map-foot under all of it, the gap the map melts into below its
     credit (THE FOOT), so the panel and the credit sit exactly where
     they did over the map. */
  min-height: calc(100svh + var(--map-foot));
  padding-block: var(--space-7) calc(var(--space-7) + var(--map-foot));
}

/* ---- the map ----------------------------------------------------
   The frame's whole box, under everything in it. */
.location-map {
  position: absolute;
  inset: 0;
  z-index: -1;
  overflow: hidden;
  background: var(--color-bg-brand-subtle);  /* holds the band's colour while the embed loads */
}
.location-map > iframe {
  position: absolute;
  left: 0;
  top: calc(-1 * var(--map-bleed));
  width: 100%;
  height: calc(100% + var(--map-bleed) - var(--map-foot));   /* THE FOOT, below */
  border: 0;
  display: block;
}
/* GOOGLE'S OWN COLOURS, from the start (since 2026-10-07). The map
   used to be greyscale until hovered, with a note about inverting it
   for a dark brand; a client build asked for the colour and the
   template followed. It is the one thing on the page not in the
   brand's palette and that is the point of a map: it has to be read
   as the real place. Nothing changes in the frame when the gate goes
   — the halo fading is the only visible answer to the click. */

/* THE GATE — created by script.js, see the MAP GATE note there. It
   is a <button> the size of the frame, with no fill and no border.
   Above the veil and the halo (neither takes pointer events); the
   heading and the panel sit in front of it in the stacking order,
   and the heading lets the pointer through to it. */
.location-map__gate {
  position: absolute;
  inset: 0;
  z-index: 3;
  width: 100%;
  height: 100%;
  margin: 0;
  padding: 0;
  border: 0;
  background: transparent;
  cursor: pointer;
  touch-action: pan-y;                    /* a vertical swipe on it is the page's */
}
.location-map__gate:focus-visible { outline-offset: -2px; }

/* THE VEIL. A fade and a vignette, in one paint. The fade is the
   white the heading sits on: solid along the top edge, so the band
   has no seam with the white section above, held near solid through
   the heading, and gone by the time the pin arrives — the pin is
   at the frame's centre and has to be in clear map. The vignette
   is a wash of the section ground that gathers toward the corners
   and leaves the middle clean; light enough that the map's colour
   reads as the map's colour. It stops short of the frame's foot so
   the attribution under it stays legible. */
.location-map__veil {
  position: absolute;
  inset: 0;
  z-index: 1;
  pointer-events: none;
  opacity: var(--location-show);
  transition: opacity var(--dur-ui) linear;
  --map-vignette: 32%;
  background:
    linear-gradient(to bottom,
      var(--map-ground) 0,
      var(--map-ground) 4rem,
      color-mix(in oklab, var(--map-ground) 86%, transparent) 18rem,
      transparent 28rem),
    radial-gradient(70% 62% at 50% 52%,
      transparent 42%,
      color-mix(in oklab, var(--color-bg-brand-subtle) var(--map-vignette), transparent) 100%);
}

/* No vignette on the dark band. It is a wash of the band's ground
   gathering in the corners, which on the light band is brand-50 and
   reads as the paper the map is printed on; on the dark band it would
   be the brand's 950 over Google's light map, and read as dirt. The
   strength is a variable so the two widths' figures and this can be
   set apart. */
.section--map[data-theme="dark"] .location-map__veil { --map-vignette: 0%; }

/* THE FOOT (2026-11-01). The band used to stop on a hard edge where
   the reviews band starts, the map's last row against the sky. Now
   the map flows into that sky, BELOW Google's logo and credit rather
   than over them.

   Google draws its logo, its credit line and two buttons along the
   bottom of the embed, inside its own frame where the page cannot move
   them, and requires the logo and credit to stay visible, so nothing
   may be laid over that row. So the embed ends --map-foot short of
   the frame's foot, the row sits whole above that gap, and the gap is
   a gradient from Google's own land colour into the reviews band's top
   colour. The map's detail stops under its credit but its colour runs
   on, and becomes the next section's ground.

   --map-land is Google's, not the brand's: the map's land colour
   along its bottom row, a fixed colour on purpose, the same way the
   pin's label is Google's red. It is NOT the same on every build.
   The template's #F5F0E5 (245,240,229) is the beige Google draws for
   open land, sampled at five points across the band at 1440. Around
   the Dunya build the land is woods, which Google draws green, and
   the beige under it read as a hard step from green to cream right
   along the map's edge (2026-11-01); Dunya sets #DCF5E5 (220,245,229),
   sampled along the last 4px of the embed at 1440 and at 390. A new
   build samples its own: screenshot the band, read the row just above
   the gap, and set --map-land below. The gradient runs in oklab so a
   green turns into the sky without passing through grey.

   Two other ways in were tried the same day and taken out. A fade
   that stopped just above the credit row left a strip of plain map
   between the fade and the sky. And a blurred mirror of the map in the
   gap (-webkit-box-reflect under a backdrop blur) came through crisp:
   Chrome paints a reflected iframe where a backdrop filter cannot
   reach it, so the mirrored credit text read upside down under the
   real one.

   The colour it ends on is the REVIEWS band's. If a build moves or
   drops that section, set --map-foot-to to whatever ground now
   follows. */
.section--map {
  --map-foot:    clamp(6rem, 14vh, 9rem);   /* 96-144px */
  --map-foot-to: var(--tm-sky-top);
  --map-land:    #F5F0E5;                   /* Google's default land; sample the client's map, see above */
}
.location-map::before {
  content: "";
  position: absolute;
  left: 0;
  right: 0;
  bottom: 0;
  z-index: 1;
  height: var(--map-foot);
  pointer-events: none;
  background: linear-gradient(in oklab to bottom, var(--map-land), var(--map-foot-to));
}

/* THE HALO. A soft bloom of the accent at the pin, with two rings
   that grow out of it and fade, 1.4s apart — the sonar shape, which
   is the oldest way of saying "here". The rings animate transform
   and opacity only. Under reduced motion _template.css runs the
   animation once in 0.01ms, which parks the rings at their faded
   end; the bloom is static and stays, so the place is still marked. */
.location-map__halo {
  position: absolute;
  z-index: 2;
  left: 50%;
  top: calc(50% - var(--map-bleed) / 2 - var(--map-foot) / 2);
  width: 7rem;
  height: 7rem;
  margin: -3.5rem 0 0 -3.5rem;
  border-radius: 50%;
  pointer-events: none;
  background: radial-gradient(circle,
    color-mix(in oklab, var(--accent-base) 32%, transparent) 0,
    transparent 62%);
  transition: opacity var(--dur-crossfade) var(--ease-out);
}
.location-map__halo::before,
.location-map__halo::after {
  content: "";
  position: absolute;
  inset: 0.5rem;
  border-radius: 50%;
  border: 1.5px solid var(--accent-base);
  opacity: 0;
  transform: scale(0.16);
  animation: location-ping 2800ms var(--ease-out) infinite;
}
.location-map__halo::after { animation-delay: 1400ms; }

@keyframes location-ping {
  0%        { transform: scale(0.16); opacity: 0.9; }
  70%, 100% { transform: scale(1);    opacity: 0;   }
}

/* THE PIN'S NAME, written by the page — OPTIONAL, and dormant until
   a <span class="location-map__label"> is in the markup (from the
   Gooseberry build, 2026-10-22; see the note on the map in
   index.html). For a property whose Google listing carries the wrong
   name: the embed is keyed on coordinates instead, so Google's pin
   comes with no label, and this puts the right name where Google
   draws a place name — anchored on the pin's point, the same spot
   the halo is centred on, 16px to its right and lifted level with the
   pin's head. Measured against Google's own label at three times scale
   and set to match it: regular weight, 13px, its red, its thin white
   halo. In px, not rem, because Google's pin and labels do not scale
   with the page's type. */
.location-map__label {
  position: absolute;
  z-index: 2;
  left: calc(50% + 16px);
  top: calc(50% - var(--map-bleed) / 2 - var(--map-foot) / 2);
  margin-top: -11px;
  transform: translateY(-100%);
  font: 400 13px/1 Roboto, "Helvetica Neue", Arial, sans-serif;
  color: #b31412;
  white-space: nowrap;
  text-shadow:
    -1px -1px 0 #fff, 0 -1px 0 #fff, 1px -1px 0 #fff,
    -1px  0   0 #fff,               1px  0   0 #fff,
    -1px  1px 0 #fff, 0  1px 0 #fff, 1px  1px 0 #fff;
  pointer-events: none;
  transition: opacity var(--dur-crossfade) var(--ease-out);
}

/* Awake, the halo and the name go: the reader can pan the map, the
   pin moves with it, and neither can follow. Google's pin stays. */
.location-map.is-live .location-map__halo,
.location-map.is-live .location-map__label { opacity: 0; }


/* ---- the heading ------------------------------------------------
   .container.center with the page's own .eyebrow / .heading /
   .subhead, so it is the same stack as the two sections either side
   of it. The one addition is the accent word, in the colour and
   upright, the way the testimonials heading does it.

   pointer-events: none because the heading is in front of the gate
   and a click on the map through a gap in the words should still
   be a click on the map. The words themselves are not interactive. */
.location-head {
  pointer-events: none;
  /* The phone scrub lowers this as the frame is scrolled through;
     everywhere else it is 1 and these two lines do nothing. The
     children's own reveal fades multiply with it. The transition
     is what makes twenty-four written steps read as one movement. */
  opacity: var(--location-show);
  transition: opacity var(--dur-ui) linear;
}
/* Gone, it also stops taking the pointer, or an invisible heading
   would still be sitting on the map's gate. */
.section--map.is-faded .location-head { visibility: hidden; }
/* The text blocks take the pointer back: the gate under them is a
   button, and its pointer cursor showing over a heading says the
   words are clickable. Clicks in the gaps between the blocks still
   reach the map. */
.location-head > * {
  pointer-events: auto;
  cursor: default;
}
/* A place name is one word to the eye; the lead's bold one does not
   break across a line. */
.location-head strong { white-space: nowrap; }
.location-head .heading em {
  font-style: normal;
  color: var(--color-text-accent);
}
/* 600px rather than the 46ch default, the width the lead had when
   it was the old centred intro; the stage under it supplies the gap. */
.location-head .subhead {
  max-width: 37.5rem;
  margin-bottom: 0;
}

/* ---- the stage and the panel ------------------------------------
   The stage is the rest of the band under the heading. It grows to
   take it, and keeps the panel at its foot with at least 14rem of
   open map above — the room the pin needs, since the pin is at the
   band's centre and the heading has the top of it. Like the heading
   it lets the pointer through; the panel takes it back. */
.location-stage {
  flex: 1 0 auto;
  display: flex;
  flex-direction: column;
  justify-content: flex-end;
  width: 100%;
  padding-top: 14rem;                     /* 224px */
  pointer-events: none;
}

/* Frosted, like the hero's form and the closing card — the same
   plate the page uses whenever copy sits on a picture. Centred and
   capped under the overlay layout so a tablet gets a column, not a
   plate the width of the band. */
.location-panel {
  pointer-events: auto;
  width: 100%;
  max-width: 30rem;
  margin-inline: auto;
  padding: var(--space-5);
  border: 1px solid var(--card-panel-edge);
  border-radius: var(--stay-radius);      /* 24px, the photo cards' corner */
  background: var(--card-panel);
  -webkit-backdrop-filter: blur(1.25rem);
  backdrop-filter: blur(1.25rem);
  box-shadow: var(--location-lift);
}
@media (prefers-reduced-transparency: reduce) {
  .location-panel {
    background: var(--color-bg-primary);
    -webkit-backdrop-filter: none;
    backdrop-filter: none;
  }
}

/* The hub the rows are measured from, on a hairline. The pin is the
   brand's 600, a glyph in the ink's own family rather than the
   accent's — the accent is spent on the heading's word and the halo. */
.location-panel__place {
  display: flex;
  align-items: center;
  gap: var(--space-2);
  padding-bottom: var(--space-3);
  border-bottom: 1px solid var(--color-border-subtle);
  color: var(--color-text-primary);
}
.location-panel__place .icon { color: var(--color-fg-brand); }

/* The drive times as a timetable: the time first and in the weight,
   the city after it in the quieter colour, a hairline between rows
   and none above the first or below the last — the place line and
   the button close the list. It was a two-by-two grid of figures
   with a hairline each way, and the cross read as a spreadsheet. */
.location-panel__list {
  list-style: none;
  margin: 0 0 var(--space-4);
  padding: 0;
}
/* Two columns, the first fixed: 5.5rem holds "40 mins" in the
   semibold with room, so every city starts on the same line
   whatever the time before it says. Baseline alignment, because
   the two spans share a size and should share a line. */
.location-panel__row {
  display: grid;
  grid-template-columns: 5.5rem minmax(0, 1fr);
  column-gap: var(--space-3);
  align-items: baseline;
  padding: var(--space-2) 0;
}
.location-panel__row + .location-panel__row {
  border-top: 1px solid var(--color-border-subtle);
}
.location-panel__time {
  color: var(--color-text-primary);
  font-weight: var(--fw-semibold);
  font-variant-numeric: tabular-nums;
}
.location-panel__from {
  color: var(--color-text-secondary);
  white-space: nowrap;                    /* the column is sized to hold it, see the grid */
}

/* The route button is the section's one filled control. Inline, its
   own width: a pill stretched the width of the panel reads as a
   form's submit, and this is a link out. */
.location-panel .btn {
  display: inline-flex;
  align-items: center;
  gap: var(--space-2);
}

/* ---- the phone: the heading gives way ---------------------------
   Under 768px the frame pins and the section is the frame plus a
   runway, and script.js (LOCATION SCRUB) lowers --location-show from
   1 to 0 across that runway. The heading and the white fade under it
   go, and the map they were covering comes forward; the panel sits
   under the fold, past the first screen, and scrolls into view once
   the frame lets go. Three beats: the heading over the map, the map
   on its own with the pin in it, the panel over the map.

   TWO GATES, AND THE RUNWAY NEEDS BOTH — the same two the hero's
   runway has, for the same reasons (read the note over its block).
   .reveal-on is the class the inline script in <head> adds only
   where there is an IntersectionObserver to drive this and the
   visitor has not asked for less motion. The height gate keeps a
   short landscape phone on the plain column: the first screen holds
   the heading and has to leave room under it for the pin.

   The runway is a spacer after the frame (the section's ::after)
   rather than a height on the section, because the frame's own
   height is not a number the stylesheet knows — a screen plus the
   panel. It is not a margin on the frame either, and that was
   tried: a sticky element is constrained by its margin box, so a
   margin on it is counted as part of it and leaves it no room to
   stick. script.js measures the section less the frame. */
@media (max-width: 767px) and (min-height: 560px) {
  .reveal-on .section--map[data-map-scrub] {
    --location-runway: 60svh;
  }
  .reveal-on .section--map[data-map-scrub]::after {
    content: "";
    display: block;
    height: var(--location-runway);
  }
  .reveal-on .section--map[data-map-scrub] .location-frame {
    position: sticky;
    top: 0;
  }
  /* The first screen is the heading's: its box runs to the fold, and
     the room under its words is the open map with the pin in it. */
  .reveal-on .section--map[data-map-scrub] .location-head {
    min-height: calc(100svh - var(--space-7));
  }
  .reveal-on .section--map[data-map-scrub] .location-stage {
    flex: none;
    padding-top: 0;
  }
}

/* The panel's type at 16px on a phone: the place line, the times and
   the cities, down from 20 and 18, so the panel sits in the band
   without crowding it. The time column narrows with it. */
@media (max-width: 767px) {
  .location-panel__place,
  .location-panel__time,
  .location-panel__from {
    font-size: var(--fs-text-md);
    line-height: var(--lh-text-md);
  }
  .location-panel__row { grid-template-columns: 5rem minmax(0, 1fr); }

  /* The route button centred in the panel on a phone, at its own
     width: the panel is the width of the screen here, and a
     left-aligned pill leaves its right half empty. Desktop keeps it
     on the left edge, under the timetable. */
  .location-panel .btn {
    display: flex;
    width: fit-content;
    margin-inline: auto;
  }
}

/* ============================================================
   8 · TESTIMONIAL PANEL — brand-800 on the section's brand-900
   ============================================================ */
/* brand-800 on the section's brand-900, with a brand-700 hairline —
   one ramp, three steps. 0.5px so the edge stays a hairline on a
   retina screen instead of reading as a drawn frame. */
/* ============================================================
   10 · FOOTER
   ============================================================ */
/* THE DARKEST STEP OF THE BRAND RAMP, not a neutral. --brand-950 is
   --gray-950's near-black with the client's hue still in it, so the
   band the page ends on belongs to the brand rather than to the
   template. Swap it for --gray-950 if a client's brand hue goes muddy
   at this lightness; nothing else here depends on which it is.

   THE BORDER IS GONE WITH IT. It was separating a white footer from a
   white section above; a near-black band against that section is its
   own edge, and under the data-theme="dark" this element now carries,
   --color-border-subtle flips to a dark grey that would be invisible
   on this ground anyway.

   THE GLOW IS THE SAME HUE, ONE STEP UP. brand-800 mixed thin into the
   top centre, so the band reads as a lit surface rather than a flat
   fill. It never gets near brand-800 itself and it is gone well before
   the bottom edge, so the label and the logo still sit on 950. */
/* The bottom padding is 16px short of the top on purpose: the logo
   link's own padding makes up the difference, so the space above the
   label and below the wordmark come out equal. 48px each on a phone,
   the page's floor for a section's edge (2026-11-01; it was 40px), and
   56px on a desktop. */
.footer {
  padding: var(--space-7) var(--container-x) var(--space-5);
  text-align: center;
  background:
    radial-gradient(ellipse 70% 120% at 50% 0%,
      color-mix(in oklab, var(--brand-800) 40%, transparent), transparent 70%),
    var(--brand-950);
}

/* THE RULE-AND-LABEL EYEBROW, both sides. The label is the accent and
   so are the two hairlines that frame it, fading out away from the
   word, the same gradient that closes the testimonials band. The
   hairlines are a fixed width so they frame the label the same way
   on every screen instead of running out to the edges. */
.footer__label {
  --footer-rule: var(--space-7);          /* 48px each side */
  display: flex;
  align-items: center;
  justify-content: center;
  gap: var(--space-3);
  color: var(--color-text-accent);
}
.footer__label::before,
.footer__label::after {
  content: "";
  flex: none;
  width: var(--footer-rule);
  height: 1px;
}
.footer__label::before {
  background: linear-gradient(90deg, transparent, var(--color-border-accent));
  transform-origin: right;
}
.footer__label::after {
  background: linear-gradient(90deg, var(--color-border-accent), transparent);
  transform-origin: left;
}

/* THE LINK IS THE TAP TARGET, the image is what moves. Padding gives
   the link a 54px target around a 22px-tall wordmark, which is also
   most of the space between it and the label.

   The dimming and the press both go on the img, not the link, because
   the link is a direct child of the reveal group and .is-revealed sets
   opacity and transform on it with three classes of weight. */
.footer__logo {
  display: inline-block;
  margin-top: var(--space-2);
  padding: var(--space-3) var(--space-4);
  border-radius: var(--radius-sm);
}
.footer__logo img {
  max-width: 11.5rem;
  margin-inline: auto;
  opacity: 0.8;
  transition: opacity var(--dur-ui) ease,
              transform var(--dur-press) var(--ease-out);
}
.footer__logo:focus-visible img { opacity: 1; }
.footer__logo:active img { transform: scale(0.97); }

@media (hover: hover) and (pointer: fine) {
  .footer__logo:hover img { opacity: 1; }
}

@media (min-width: 768px) {
  .footer { padding-block: var(--space-8) var(--space-6); }
  .footer__label { --footer-rule: var(--space-9); }   /* 64px */
}

/* THE HAIRLINES DRAW OUTWARD after the label has landed, from the word
   towards the edges. 0.4, not 0: a line that grows out of a point
   reads as loading. The delay lets the label settle first so the two
   do not arrive as one lump. Under reduced motion the gate in <head>
   never opens and they are simply there. */
.reveal-on .footer__label::before,
.reveal-on .footer__label::after {
  opacity: 0;
  transform: scaleX(0.4);
  transition: opacity   var(--dur-reveal)    var(--ease-out) 240ms,
              transform var(--dur-crossfade) var(--ease-out) 240ms;
}
.reveal-on .footer__label.is-revealed::before,
.reveal-on .footer__label.is-revealed::after {
  opacity: 1;
  transform: none;
}
@media (prefers-reduced-motion: reduce) {
  .reveal-on .footer__label::before,
  .reveal-on .footer__label::after { opacity: 1; transform: none; }
}

/* ============================================================
   11 · WELCOME  ·  the post sign-up page (welcome.html)
   ------------------------------------------------------------
   A modifier on .hero-offer, not a second hero. The video, both
   scrims, the seam, the logo and the entrance animation are the
   components section 1 already ships; only three things differ,
   and each is here for a reason that is written next to it.

   THE ONE THING TO KNOW BEFORE EDITING: the copy is CENTRED on
   this page and left aligned on the marketing hero, and that is
   what the scrim override at the bottom of this block is about.
   The desktop scrim in the breakpoint block is a diagonal,
   weighted into the left third because that is where the
   marketing hero's copy lives. Centred copy runs straight out of
   it and into the bright side of the frame. The override is two
   classes deep so it beats that rule wherever it sits in the
   file, and it carries all three of this page's scrim layers —
   including the copy band, which cannot live on the inner here.
   The reason why is written over layer 2.
   ============================================================ */
.hero-offer.hero-offer--welcome {
  align-items: center;
  /* Shorter than the marketing hero at both breakpoints. That one
     is a banner and wants the room; this one has a job, and the
     code has to be reachable without a scroll. The content is
     taller than this number on every viewport anyway — it is a
     floor that stops a short frame, not a height. */
  min-height: clamp(28rem, 80svh, 38rem);
}

/* Centred, and narrower than the frame. The padding is the
   marketing hero's stepped down: that one pads for a banner, and
   96px of air above a back link only pushes the code further from
   the fold. */
.hero-offer__inner.welcome {
  display: flex;
  flex-direction: column;
  align-items: center;
  text-align: center;
  padding-block: var(--space-9);
}

/* Every string on this page is --color-overlay-text, for the same
   reason the marketing hero's are: dimming secondary copy to
   --color-overlay-fg measures ~4.0:1 against the scrim's worst
   case and fails AA. Hierarchy is carried by size and weight.

   The shadow pair is load bearing and is the same pair, for the
   same reason — see the note over the hero's title. The 2px layer
   is a hard edge against whatever is immediately behind a glyph;
   the 12px layer is the pad that catches a bright patch of
   footage drifting under a counter. */
.welcome__title,
.welcome__lead,
.welcome__note,
.back-link {
  color: var(--color-overlay-text);
  text-shadow: var(--hero-text-halo);
}

/* max-width is inherited from .hero-offer__title, which caps at
   34rem and 38rem. Centred, that is the right measure for a
   greeting; the auto margins are new. The bottom margin is the
   hero title's OLD figure: that one dropped to 16px when its offer
   line became body copy, and this title is followed by the coupon
   plate, which wants the 32px back. */
.welcome__title { margin-inline: auto; margin-bottom: var(--space-5); }

/* The sign off, and it sits at the FOOT of the copy now rather
   than over the plate. It keeps body-lg: it is the warmest line
   on the page and the one that should still read at a glance
   from across a room, and a full step of space above it is what
   separates a sign off from the housekeeping it follows. */
.welcome__lead {
  max-width: 34rem;
  margin-inline: auto;
  margin-top: var(--space-4);
}

.welcome__note { max-width: 34rem; }
/* The housekeeping line. One rung down and no dimming — see the
   colour note above. It belongs to the card (where else is my code),
   so it sits 16px under it: the hero's column gap is 24px, and the
   margin takes 8px of it back. */
.welcome__note--fine { margin-top: calc(var(--space-3) - var(--space-4)); }

/* ---- the back link --------------------------------------------
   Top left of the copy column rather than pinned to the frame's
   corner: pinned, it would sit on the brightest part of an
   unvetted photograph with no scrim under it, and it would drift
   away from everything it belongs to as the viewport widened.
   align-self pulls it out of the centred column without needing
   a wrapper.

   The 44px min-height is the WCAG 2.5.8 target size, met by
   padding rather than by a fixed box so the label can grow. The
   negative inline margin pulls the glyph's own padding back to
   the column's left edge, so the chevron optically aligns with
   the copy below instead of the label's leading edge.
---------------------------------------------------------------- */
.back-link {
  align-self: flex-start;
  display: inline-flex;
  align-items: center;
  gap: var(--space-2);
  min-height: 2.75rem;                    /* 44px — a target, not spacing */
  padding: var(--space-2) var(--space-3);
  margin-left: calc(var(--space-3) * -1);
  margin-bottom: var(--space-5);
  border-radius: var(--radius-md);
  transition: background-color var(--dur-ui) ease,
              transform var(--dur-press) var(--ease-out);
}
.back-link svg { width: 1rem; height: 1rem; flex: 0 0 auto; }
.back-link:active { transform: scale(0.98); }

@media (hover: hover) and (pointer: fine) {
  .back-link:hover { background: var(--color-overlay-fill); }
}

/* ---- the code plate -------------------------------------------
   The one thing this page exists to deliver, so it is the one thing
   on it that does not trust the photograph behind it: the ground is
   opaque, and no frame drifting underneath can take the code's
   contrast with it.

   A CARD WITH TWO FACES (2026-10-31). It was a ticket first: a pale
   ground, a dashed edge, a notch bitten out of each end and a
   brand-green Copy stub, which is a supermarket voucher's language.
   Then, for a day, a dark key card, which sat on the dark hero as
   one more dark thing. Now it is a card of warm paper inside a
   gilded rim with a second hairline just inside it, the double rule
   of engraved stationery: the code is set large in the display face
   in the brand's darkest ink, and Copy is ink on the card behind a
   hairline, not a coloured button. Over the footage the paper is the
   brightest thing in the frame, which is where the eye should land;
   on a light hero (.hero-offer--light) the rim and the shadow are
   what lift it.

   The dark face is still here, as the card's OTHER side: a copy
   turns the card over to it (see "the claimed state").

   ON BRAND FOR ANY CLIENT because it is built from the two ramps and
   names no hue: a navy brand gets navy ink and a navy claimed face,
   and a brand whose accent ramp is grey gets a platinum rim instead
   of a gold one.

   26rem, not the 34rem the copy runs to. A code is eight characters;
   a card three times wider than its contents reads as an empty field
   waiting to be filled in.

   NO BOTTOM MARGIN. The line under the card answers the question the
   card raises (where else is this code), so it sits 16px under it and
   sets that itself: see .welcome__note--fine.
---------------------------------------------------------------- */
.code {
  width: 100%;
  max-width: 26rem;
  margin-top: var(--space-6);

  /* The card's own palette, in one place. The claimed face re-binds
     the first three on .code__claim, so everything drawn in them
     turns over with it. Measured 2026-10-31 on the template's ramps
     at the worst point of each ground (the paper's darker bottom
     right, the face's lit top left): on the paper the code 14.0:1
     and Copy 5.8:1; on the claimed face the code 9.6:1 and Copy
     8.2:1. A /brand build re-measures them; Copy on the paper is the
     one with the least room. */
  --code-ink:     var(--brand-950);      /* the code */
  --code-action:  var(--brand-700);      /* Copy */
  --code-rule:    color-mix(in oklab, var(--accent-500) 45%, transparent);
  --code-paper:   var(--accent-25);
  --code-paper-2: var(--accent-50);
  --code-face:    var(--brand-950);
}

/* THE RIM IS A BACKGROUND, NOT A BORDER COLOUR. Two layers on one
   box: the paper clipped to the padding box, and a diagonal metallic
   ramp clipped to the border box, so the 1px transparent border shows
   only the ramp. Light catches the top left corner and the bottom
   right edge falls away, which is what makes it read as a gilded edge
   rather than a yellow line. The paper is lit from the same corner.

   The shadow is the brand's darkest step and never black, long and
   soft, so the card lies on the scene rather than floating over it.
   The inset shade along the bottom edge is the card's thickness.

   align-items: stretch so the Copy half runs the card's full height
   and its whole height is the tap target. overflow: hidden is the
   window the claimed face floods through.

   THE PRESS IS ON THE WHOLE CARD, and only once the script has made
   the code clickable: a tap anywhere on it copies, so all of it gives
   a little under the finger. On `scale`, a property of its own, so it
   never fights a transform. */
.code__plate {
  position: relative;
  display: flex;
  align-items: stretch;
  border: 1px solid transparent;
  border-radius: var(--radius-lg);
  background:
    linear-gradient(150deg,
      var(--code-paper) 0%, var(--code-paper-2) 60%) padding-box,
    linear-gradient(135deg,
      var(--accent-200) 0%, var(--accent-500) 30%,
      var(--accent-300) 55%, var(--accent-700) 100%) border-box;
  box-shadow:
    inset 0 -1px 0 color-mix(in oklab, var(--accent-500) 20%, transparent),
    0 var(--space-4) var(--space-9) calc(-1 * var(--space-3))
      color-mix(in oklab, var(--brand-950) 60%, transparent);
  overflow: hidden;
  transition: scale var(--dur-press) var(--ease-out);
}
.code__plate[data-copy-ready]:active { scale: 0.985; }

/* THE SECOND RULE, one --space-1 inside the rim, over the code and
   Copy and under the claimed face, which draws its own copy of it in
   the same place in its own gold (--code-rule is re-bound there), so
   the rule changes colour exactly where the face has reached.
   pointer-events: none so it never takes a click meant for Copy. */
.code__plate::after,
.code__claim::after {
  content: "";
  position: absolute;
  inset: var(--space-1);
  z-index: 1;
  border: 1px solid var(--code-rule);
  border-radius: calc(var(--radius-lg) - var(--space-1) - 1px);
  pointer-events: none;
}

/* user-select: all so one click takes the whole code and never half
   of it, and with the script a click on the code copies it as well
   (see [data-copy-ready] below). The value is real selectable text,
   not a background image or a ::before, because that is the path a
   visitor with no JavaScript gets.

   The tracking is the engraving. A redemption code is read one
   character at a time, not as a word, and at 0.26em the letters
   stand apart like a card's embossed number. Tracking adds space
   after the LAST letter too, which pushes centred text left by half
   of it; the matching text-indent puts it back on the card's axis.
   (It read 0.14em here until 2026-10-31, but the per-letter spans of
   the old animation each took the text-indent as well, so what
   shipped was nearer 0.28em. 0.26em keeps that look, and the widths
   measured under "narrow cards", without the spans.)

   A BLOCK, centred with align-content, and not a flex container
   (from the Gooseberry build, 2026-10-22): the code used to be split
   into one span per letter, and a flex container made every letter
   its own item, so a hand selection came out with line breaks in it.
   nowrap so a narrow card never breaks a code across two lines. The
   side padding gives way on a narrow card: see "narrow cards". */
.code__value {
  position: relative;
  z-index: 1;
  flex: 1 1 auto;
  display: block;
  align-content: center;
  text-align: center;
  white-space: nowrap;
  min-height: calc(var(--field-h) + var(--space-4));
  padding: var(--space-3) var(--space-4);
  color: var(--code-ink);
  letter-spacing: 0.26em;
  text-indent: 0.26em;
  -webkit-user-select: all;
          user-select: all;
}
.code__plate[data-copy-ready] .code__value { cursor: pointer; }

/* A hand selection in the rim's gold rather than the browser's
   blue. */
.code__value::selection {
  background: color-mix(in oklab, var(--accent-300) 55%, transparent);
  color: var(--code-ink);
}

/* COPY IS INK ON THE CARD. No fill: a saturated block is what made
   the old stub read as a coupon's tear-off. It is the brand's ink
   with Phosphor's "copy" glyph, behind a hairline that fades out at
   both ends, so the card still reads as two halves without a
   perforation. The extra right padding balances the inner frame,
   which eats into that side.

   A grid of one cell, so the two labels stack in it and the button
   is always as wide as the wider one: swapping them can never move
   the code. overflow: hidden is the window the labels pass through. */
.code__copy {
  position: relative;
  z-index: 1;
  flex: 0 0 auto;
  display: grid;
  place-items: center;
  overflow: hidden;
  padding: var(--space-2) var(--space-5) var(--space-2) var(--space-4);
  border: 0;
  background: none;
  color: var(--code-action);
  cursor: pointer;
  touch-action: manipulation;
  transition: color var(--dur-ui) ease;
}
.code__copy::before {
  content: "";
  position: absolute;
  left: 0;
  top: var(--space-3);
  bottom: var(--space-3);
  width: 1px;
  background: linear-gradient(to bottom,
    transparent, var(--code-rule) 50%, transparent);
}

/* Inset, because the card's overflow: hidden would cut an outside
   ring off on three sides. The radius is the card's, not the
   button's own (it has none to show): an inset outline's corners are
   the radius MINUS the offset, so --radius-sm here came out square.

   The claimed face lies over the real button, ring and all, so while
   focus is on Copy the face's stub draws the same ring in the face's
   colours. Its own rule: a browser without :has() drops the whole
   selector list it sits in. */
.code__copy:focus-visible {
  outline-color: var(--code-action);
  outline-offset: calc(-1 * var(--space-2));
  border-radius: var(--radius-lg);
}
.code__plate:has(.code__copy:focus-visible) .code__claim .code__copy {
  outline: 2px solid var(--code-action);
  outline-offset: calc(-1 * var(--space-2));
  border-radius: var(--radius-lg);
}

/* The button ships hidden and script.js reveals it. An author
   display beats the UA sheet's [hidden] rule whatever its
   specificity, so .code__copy's own display: grid would quietly
   un-hide it without this. */
.code__copy[hidden] { display: none; }

/* Hover deepens the ink a step; nothing moves and nothing fills. */
@media (hover: hover) and (pointer: fine) {
  .code__copy:hover { color: var(--brand-900); }
}

/* ---- the claimed state ----------------------------------------
   [data-copied] on the plate, set by script.js for two seconds and
   restarted by every copy. The whole card answers rather than one
   corner of it, so a visitor whose eye is on the CODE still sees it.

   THE CARD TURNS OVER. Its dark face, the brand's darkest step with
   the code in champagne inside a lit gold rule, floods across the
   paper in a circle from wherever the visitor touched it (a keyboard
   press starts from Copy's centre), so the answer starts under the
   finger and runs out to the rim. The face is a second, aria-hidden
   copy of the card's contents that script.js lays exactly over the
   first, so the edge of the circle is a clean line between two
   faces, the code half ink and half champagne as it passes, rather
   than a dark wash sliding over the letters. Meanwhile "Copy" hands
   over to a check that draws itself and "Copied" on both faces at
   once: the face's stub carries the button's classes, so every label
   rule below drives the two in step.

   The flood itself is script.js's (WAAPI, so a second copy restarts
   it from the new touch); this rule only shows and hides the face.
   The way back is a plain fade with no flood: the arrival is the
   news, the return is housekeeping. Under reduced motion there is no
   flood and the face simply appears. */
.code__claim {
  --code-ink:    var(--accent-100);
  --code-action: var(--accent-200);
  --code-rule:   color-mix(in oklab, var(--accent-300) 75%, transparent);

  position: absolute;
  inset: 0;
  z-index: 2;
  display: flex;
  align-items: stretch;
  background: linear-gradient(150deg,
    color-mix(in oklab, var(--brand-900) 70%, var(--code-face)) 0%,
    var(--code-face) 55%);
  box-shadow: inset 0 1px 0
    color-mix(in oklab, var(--accent-100) 14%, transparent);
  opacity: 0;
  pointer-events: none;
  transition: opacity 320ms ease;
}
.code__plate[data-copied] .code__claim {
  opacity: 1;
  transition: none;
}
/* The face's code is drawn from an attribute rather than written as
   text (script.js), so a hand selection across the hero, or find in
   page, meets the code once, on the paper. user-select: none was not
   enough: a selection serialises text it does not paint. */
.code__claim .code__value::before { content: attr(data-face); }

/* "Copy" and "Copied" share one grid cell. Claimed, "Copy" lifts half
   a rem and blurs out in 160ms; the check and "Copied" rise the same
   half rem into place over 240ms, 60ms behind it so the two never sit
   on top of each other. Exit faster than entry, both on the house
   ease-out. The blur is what makes the hand-off read as one label
   turning rather than two crossing.

   The return transitions sit on the resting rules, and they differ
   per label on purpose: "Copy" snaps back into position at once (it
   is invisible when it does) and fades in; "Copied" fades out first
   and only then drops back below the window, so neither is ever seen
   travelling the wrong way.

   The press is on the labels and on `scale`, a property of its own,
   so it neither shrinks the hairline nor fights the labels' own
   transforms; the second rule presses the face's stub with the real
   button. Under reduced motion _template.css takes every duration to
   zero and the labels simply swap. */
.code__copy-label {
  grid-area: 1 / 1;
  display: inline-flex;
  align-items: center;
  gap: var(--space-2);
  transition: opacity var(--dur-ui) ease,
              filter var(--dur-ui) ease,
              scale var(--dur-press) var(--ease-out);
}
.code__copy:active .code__copy-label { scale: 0.96; }
.code__plate:has(.code__copy:active) .code__claim .code__copy-label { scale: 0.96; }

.code__copy-label--done {
  opacity: 0;
  filter: blur(4px);
  transform: translateY(0.5rem);
  transition: opacity 160ms ease,
              filter 160ms ease,
              transform 0s linear 160ms,
              scale var(--dur-press) var(--ease-out);
}

.code__plate[data-copied] .code__copy-label:first-child {
  opacity: 0;
  filter: blur(4px);
  transform: translateY(-0.5rem);
  transition: opacity 160ms var(--ease-out),
              filter 160ms var(--ease-out),
              transform 160ms var(--ease-out),
              scale var(--dur-press) var(--ease-out);
}
.code__plate[data-copied] .code__copy-label--done {
  opacity: 1;
  filter: none;
  transform: none;
  transition: opacity 240ms var(--ease-out) 60ms,
              filter 240ms var(--ease-out) 60ms,
              transform 240ms var(--ease-out) 60ms,
              scale var(--dur-press) var(--ease-out);
}

/* Both glyphs are Phosphor at its bold weight (phosphoricons.com),
   1.125em so they sit on the caps' height. The check draws itself as
   it lands: pathLength="1" in the markup makes the dash maths 1
   whatever the glyph's real length, and the reset waits out the fade
   so the tick never un-draws in view. */
.code__copy-label svg {
  width: 1.125em;
  height: 1.125em;
  flex: 0 0 auto;
}
.code__copy-label--done polyline {
  stroke-dasharray: 1;
  stroke-dashoffset: 1;
  transition: stroke-dashoffset 0s linear var(--dur-ui);
}
.code__plate[data-copied] .code__copy-label--done polyline {
  stroke-dashoffset: 0;
  transition: stroke-dashoffset var(--dur-fill) var(--ease-out) 140ms;
}

/* ---- narrow cards ----------------------------------------------
   Sized off the card, not the viewport, because the card's width is
   what runs out: hence the container on .code. Measured 2026-10-31
   against WELCOME10 in the template's fonts. The code wants 230px at
   22px with this tracking, and "Copied" with its check 121px at the
   desktop paddings, which spilled the button 11px off a 390 phone's
   card and 26px off a 375's.

     Under 24rem (every phone from 375 to 430): a 20px code with 8px
     side padding, and a tighter button (109px). At 375, the
     tightest, that leaves 16px clear.
     Under 20rem (360 and 320): both labels drop their word and keep
     the glyph, 48px, so the 20px code still has 22px clear at 320.
     The button's accessible name is its aria-label, so nothing is
     lost to a screen reader.

   The desktop card is the tightest of all: the 24px code leaves 9px
   clear beside "Copied" (re-measured 2026-10-31 at the 0.26em
   tracking, claimed state, nothing overflowing at 1440, 430, 390,
   375, 360 or 320). A LONGER CODE than nine characters needs
   these re-measured, and so does a /brand display face that sets
   wider than this one. Check the claimed state at 1440, 375 and 320
   after /brand. */
.code { container-type: inline-size; }

@container (max-width: 24rem) {
  .code__value      { padding-inline: var(--space-2); font-size: 1.25rem; }
  .code__copy       { padding-inline: var(--space-3); }
  .code__copy-label { gap: var(--space-1); }
}
@container (max-width: 20rem) {
  .code__copy-word { display: none; }
}

/* The status line. role="status" in the markup makes it a polite
   live region, so the same string that appears here is announced.

   min-height, not a margin that appears with the text: the line
   holds its own room from first paint so a message never moves
   anything when it lands.

   UNDER THE HOUSEKEEPING LINE, not between it and the card
   (2026-10-31). Its reserved room, almost always empty, was holding
   that line 80px off the card it belongs to. The hero's column gap
   is 24px; the margin takes this back to 8px under the line. */
.code__status {
  min-height: 1.5rem;
  margin-top: calc(var(--space-2) - var(--space-4));
  color: var(--color-overlay-text);
  text-shadow: var(--hero-text-halo);
}

/* A successful copy is said by the card, so its sentence here is
   for screen readers only: clip-path hides the text and keeps both
   the box (the reserved line, so nothing below moves) and the
   live-region announcement. A FAILED copy is never quiet: that is
   the one message a sighted visitor still has to read here. */
.code__status[data-quiet] { clip-path: inset(50%); }

/* NO SCRIM OF ITS OWN ANY MORE (2026-10-23, as on the Cabin
   Collective and Gooseberry builds). This page used to repaint
   .hero-offer__scrim with four layers — a radial under the copy, a
   band, a top vignette for the back link and a bottom ramp for the
   two reassurance lines — because its strings sit in places the
   marketing hero's old stack never reached. The brand tint replaced
   all of that on both pages; see --hero-tint. Every string in this
   hero is 96% white, the smallest is the 14px back link and the
   junk-mail line, and under the tint alone the worst case is about
   6:1 against their 4.5:1 bar, so the base rule serves this page
   unchanged.

   And the inner carries no copy scrim of its own at any width: the
   tint is already the floor. Two classes, so it also beats the
   .hero-offer__inner rule that paints one on index.html. */
.hero-offer__inner.welcome { background: none; }

/* NO SEAM ON THIS PAGE. On index.html the seam dissolves the footage
   into the white page the hero sits on. This hero sits over the pale
   amenities band instead, and the ramp across the foot of the footage
   read as a gradient laid on a dark hero — first white, then briefly
   dark; it went entirely on 2026-09-22 (folded back from a client
   build). So the footage runs to the hero's bottom edge and the
   band below starts on its own hairline, .offer__rule--top. The
   element stays in the markup so both pages share one hero; it is
   simply not drawn here. Two classes deep so it beats the base seam
   wherever it sits in the file. */
.hero-offer--welcome .hero-offer__seam { display: none; }

/* The entrance, extending the hero's four-element stagger to the
   two elements this page adds. Same curve, same duration, same
   70ms step, so the two pages open the same way. */
@media (prefers-reduced-motion: no-preference) {
  .welcome .back-link,
  .welcome .welcome__lead,
  .welcome .code,
  .welcome .welcome__note {
    animation: hero-rise var(--dur-reveal) var(--ease-out) both;
  }
  /* The logo and the title are already in the hero's own stagger
     at 40ms and 110ms — .welcome__title carries .hero-offer__title.
     These four continue the same 70ms step from there.

     THE ORDER HERE IS DOCUMENT ORDER, and it has to stay that
     way. The lead used to run at 180ms because it used to sit
     above the plate; now that it signs off at the foot it takes
     the last slot, or the page opens with its bottom line
     arriving before the coupon it is talking about. */
  .welcome .back-link           { animation-delay:   0ms; }
  .welcome .code                { animation-delay: 180ms; }
  .welcome .welcome__note       { animation-delay: 250ms; }
  .welcome .welcome__note--fine { animation-delay: 320ms; }
  .welcome .welcome__lead       { animation-delay: 390ms; }
}

/* ============================================================
   DESKTOP — everything above is the phone layout
   Type steps itself at 767px inside _template.css. This
   breakpoint is layout only.
   ============================================================ */
@media (min-width: 1024px) {
  /* ---- 1 + 2 · hero offer ---- */
  .hero-offer        { min-height: var(--hero-min-lg); }
  /* The inset is added on both axes for the reason given on the base
     rule: at full reveal the pane has pulled away from the viewport
     edge, and the copy keeps its gutter against the pane. */
  /* Side gutter only. The vertical clearance is set once on the base
     rule and does not grow with the viewport — see the note there. */
  .hero-offer__inner {
    padding-inline: calc(var(--space-9) + var(--clip-inset-max, 0px));
  }
  .hero-offer__seam  { height: var(--hero-seam-lg); }
  /* Both halves of the seam grow together — the hero's own ramp and
     the one continuing it into the next section. A fade is a fixed
     distance in the eye rather than a fraction of the page, but the
     distance the eye will accept scales with how much of the page it
     is taking in at once, and up here that is a great deal more. */
  :root               { --seam-in: var(--seam-in-lg); }
  /* Only the cap moves up here — the height itself is the clamp on
     the base rule, which already reaches --hero-logo-lg on a tall
     enough window. */
  .hero-offer__logo img {
    max-width: min(var(--hero-logo-max-lg), 100%);
  }

  /* NO LEFT COLUMN AND NO DIAGONAL UP HERE ANY MORE.
     What used to live in this block: a 38rem/42vw cap on the title
     and offer, a background:none that switched the copy scrim off,
     and a diagonal frame scrim whose plateau was solved so a left
     hand column stayed inside it while the right of the photograph
     stayed bright.

     All three were one layout decision — copy left, picture right —
     and that decision is gone. The column is centred at every width,
     the measures are character based and set once on the base rules,
     and the frame scrim is the three layer ramp that covers the
     middle. A diagonal would now be darkest where there is no text
     and lightest under half the headline.

     If you want the left aligned hero back, it is those three rules
     plus text-align:left and align-items:flex-start on
     .hero-offer__inner — not a change to anything above. */

  /* No max-width and no margin here — the base rule caps this at
     30rem and the column's gap spaces it. */
  .offer-form--hero .offer-form__field,
  .offer-form--hero .offer-form__control .btn {
    min-height: calc(var(--field-h-lg) - var(--space-2));
  }
  /* Re-derived against the taller row — see .offer-form__control. */
  .offer-form--hero .offer-form__control { border-radius: calc(var(--field-h-lg) / 2); }
  .offer-form--hero { border-radius: calc(var(--field-h-lg) / 2 + 1px); }   /* the frosted form around it, re-derived with the same row height */

  /* ---- 9 · closing offer ----
     Both children come out of flow, so the plate's height is this
     number and nothing else. */
  .claim { min-height: 38rem; }

  /* The whole plate, not three quarters of it. The photograph runs
     edge to edge and the card floats on it — so the picture
     continues past the card to the plate's right corner instead of
     dissolving into a gradient behind it. No mask: there is no
     seam to hide once the photo has no edge inside the plate. The
     plate's own gradient is still under all of this and still
     earns its place, as the ground the video sits on until a frame
     lands. */
  .claim__media {
    position: absolute;
    inset: 0;
    width: 100%;
    aspect-ratio: auto;
    max-height: none;
  }


  /* Pinned to the right and centred, which puts roughly a third
     of it on the photograph at 1024 and still a quarter of it on
     a 1600px monitor: the plate grows, the card does not, and the
     photo's 72% edge moves right with the plate. So the overlap
     holds at every width without a second breakpoint.

     min() rather than a flat width — at exactly 1024 a fixed
     27rem card leaves 88px of plate showing to its right, and the
     percentage is what keeps that from happening. */
  .claim__card {
    position: absolute;
    top: 50%;
    right: var(--space-7);
    translate: 0 -50%;
    width: min(30rem, 46%);
    margin: 0;
    padding: var(--space-6);
    /* One radius all round again — off the plate's edges, the card
       is a free floating object and the corner pairing the base
       rule needs does not apply. */
    border-radius: var(--claim-radius);
  }

  /* Back to stacked, and this is the one place the form reverses
     a rule it picked up at a smaller width. Everywhere else the
     control gets wider as the page does; here it gets narrower,
     because the card is a fixed 480px rail whatever the monitor
     is. Inline, the field had 210px left after the button and the
     first client to write a longer label than "CLAIM 10% OFF"
     would have pushed it out of the card. Stacked, the button is
     the full width of the card, which is also the stronger call
     to action of the two. */
  .offer-form--claim .offer-form__control { flex-direction: column; align-items: stretch; }

  .offer-form--claim .offer-form__field,
  .offer-form--claim .offer-form__control .btn {
    min-height: calc(var(--field-h-lg) - var(--space-2));
  }
  .offer-form--claim .offer-form__control { border-radius: calc(var(--field-h-lg) / 2); }

  /* Cards wrap into rows instead of swiping */
  .slider__track {
    flex-wrap: wrap;
    justify-content: center;
    overflow-x: visible;
    column-gap: var(--space-4);
    row-gap: var(--space-6);
  }

  /* 384px, and the reason the rail needs five cards rather than
     three: five at this width overrun the 1200px panel, so the
     seam between the two halves of the loop is always off screen.
     Three would leave a hole in it on a wide monitor. */


  /* Twice as wide once the rail is 1104px instead of 343px — the
     same proportion of it, not a bigger fade. */

  /* ---- LOCATION, the overlay layout -------------------------------
     The panel leaves the foot of the band for the container's left
     edge, with the pin in the open to its right. The band is a full
     screen, as it is on a phone: it was 70svh, and with the white
     fade over its top (below) taking a quarter of that, the map
     showed in under half the screen and the band read as a strip
     (a client build, 2026-10-06). At 100svh the open map is about 70% of the
     screen. A floor, so a panel taller than a short screen grows the
     band instead of being clipped. At 1024 the container is 992 wide
     and the pin at 512; the panel's narrow end, 24rem plus the
     gutter, ends at 400. The 27rem cap is for 1440 and up. */
  .location-frame {
    min-height: calc(100svh + var(--map-foot));
  }
  .location-stage {
    justify-content: center;
    align-items: flex-start;
    padding-top: var(--space-4);
  }
  .location-panel {
    width: clamp(24rem, 30vw, 27rem);
    max-width: none;
    margin-inline: 0;
  }
  /* The fade is shallower: the heading is shorter on a wide screen.
     Full width on purpose — a pane of white sized to the heading was
     tried and taken out (2026-10-06); the heading reads as sitting at
     the top of the page with the map rising out of it, not on a
     patch.

     92% held to 13.5rem, just under the lead's last line, then clear
     by 18rem, above the pin. It was 85% at 12rem, which let map labels
     behind the lead's last line through at 3.5:1; held to 13.5rem the
     lead measures 5.1:1 or better against every pixel under it at
     1918x961, 1440x900 and 1024x768 (2026-10-06, on a client build
     whose lead ran to two lines at 1440).

     THE STOPS ARE TUNED TO THE HEADING'S HEIGHT. A lead that runs a
     line or two longer puts its last line in the part of the fade
     where map labels show through: move the 13.5rem stop down by the
     extra height and re-measure the lead against the map under it. */
  .location-map__veil {
    background:
      linear-gradient(to bottom,
        var(--map-ground) 0,
        var(--map-ground) 3rem,
        color-mix(in oklab, var(--map-ground) 92%, transparent) 13.5rem,
        transparent 18rem),
      radial-gradient(60% 70% at 56% 52%,
        transparent 38%,
        color-mix(in oklab, var(--color-bg-brand-subtle) var(--map-vignette), transparent) 100%);
  }
  .location-map__veil { --map-vignette: 40%; }
  .section--map[data-theme="dark"] .location-map__veil { --map-vignette: 0%; }



}

/* ============================================================
   LEGACY · AMENITIES, THE PINNED LAYOUT  (see the LEGACY note on
   the .process block above: no page uses it)
   ------------------------------------------------------------
   Its own media query, and the height half of it is a hard
   requirement rather than a nicety.

   The frame is exactly one screen and it is PINNED, so anything
   that does not fit inside it is not merely tight — it is off the
   bottom of the window with no scroll available to reach it,
   because scrolling moves the highlight and not the page. The
   list has to fit, and whether it fits is a question about the
   window's HEIGHT, which a min-width query cannot see: the case
   that broke was a wide short window, 1280x700 and 1100x620, an
   ordinary laptop once the browser chrome comes off a 768px
   screen. The fourth amenity was cut off and unreachable.

   720px is measured, not guessed, and re-measured after every
   change to what the column holds. As it stands, at 1024x720 — the
   corner of this query, and the worst case, because a narrower
   column wraps more — the frame offers 648px and the column's
   TALLEST STATE needs 630px. Tallest state matters and it is not
   the same as "the column": one amenity's description is open at a
   time and they are not the same length, so the figure to measure
   is the maximum over the four, not whatever happens to be up when
   you look. The four measure 630/621/612/603.

   18px of clearance, and it is 18 rather than 11 because the
   numeral's vh coefficient was trimmed from 6.6 to 6.2 for it —
   see the note on --process-num. Clearance grows by about half a
   pixel per pixel of window from there: 29px at 740, 40px at 760.

   Webfonts turn out to cost nothing here, which is a change from
   what this note used to claim. Substituting the fallback stacks
   (Georgia for Fraunces, the system sans for Spectral) and
   re-measuring gives byte-identical column heights at every window
   size in the sweep — the two pairs wrap the same and their line
   boxes match at these sizes. The 26px allowance the old note
   carried for that case was never verified and is not needed.
   Browser text zoom needs no allowance either — zoom shrinks the
   reported viewport height along with everything else, so a zoomed
   window falls below this gate on its own and takes the fallback.

   THIS NUMBER HAS MOVED AND EVERY MOVE WAS A MEASUREMENT, which is
   the point of this note:

     640px  numeral at 48px on a vh clamp; break 601
     600px  numeral flat 16px; break 532
     680px  the Check Availability button added ~100px; break 670,
            then 633 once the intro was let off its 46ch cap
     720px  the intro capped at 430px and back to five lines
     720px  the numeral moved to the side of the step at display
            size and the description moved off the pinned card into
            the left column. The two nearly cancel: the list went
            from 289px to 278px, because the description now unfolds
            inside a row the numeral had already made tall. Held at
            720 rather than moved; 630px worst case in 648px.

   The figures the 680 and 720 rows used to carry for their break
   points did not reproduce when this was re-measured, so they are
   not repeated. Trust the clearance figures above, which were
   measured against the file as it stands.

   The Check Availability button was once added AFTER the gate had
   been lowered to 600 and the gate was not re-measured — which left
   a 70px band of window heights where the pinned layout was on and
   the button was off the bottom of the screen with no way to scroll
   to it. RE-MEASURE AFTER ANY CHANGE TO THE LEFT COLUMN'S CONTENT.
   Adding a line of copy to the intro is enough to invalidate this,
   and so is lengthening one of the four descriptions.

   UNDER 720px the section falls back to the layout the phone
   uses: one column, no pin, and a photograph above each amenity's
   name. That is not a degraded version of this one, it is the
   other one this section already ships, and it cannot clip
   anything because nothing is pinned.

   script.js gates its scroll-progress driver on this exact query.
   IF THIS CHANGES, CHANGE IT THERE TOO — they have to agree, or
   one layout ends up with the other's driver and the highlight
   stops matching the deck. */
@media (min-width: 1024px) and (min-height: 720px) {
  /* ---- 5 · amenities, the pinned two column version ----
     The section is a SCROLL TRACK now, not a block of content. It
     is several screens tall and the grid inside it pins for the
     whole way down, so what you see is one still frame: the whole
     list of amenities on the left, the deck of photographs on the
     right, and scrolling moves which amenity is lit rather than
     moving the page.

     WHY THIS RATHER THAN THE 60vh-PER-STEP VERSION IT REPLACES.
     That version gave each amenity two thirds of a screen and let
     them scroll past a pinned photo, which reads perfectly well
     but shows you exactly one amenity at a time: on a 900px
     monitor, standing on 01, the other three are below the fold.
     The list could not do the one job a numbered list is for,
     which is to say how many there are and where in them you are.
     Pinned, all four are on screen, the lit one is the answer to
     "where am I", and the deck beside it says the same thing a
     second way — three cards left to go.

     The cost is honest and worth naming: the page gets four
     screens longer, and for four amenities that is the trade. It
     would not be at ten. */

  /* One screen to arrive in, then one dwell per amenity. The last
     dwell is what stops the section releasing the moment 04 lights
     up — without it the fourth amenity would flash and be gone.

     --process-count HAS TO MATCH the number of <li>s, and it is
     the one number in this section that cannot be derived in CSS.
     script.js overwrites it from the real count on load, so a
     mismatch only costs the pre-JS paint — but it is still worth
     keeping right, because a no-JS visitor gets what is written
     here and nothing else. */
  

  /* The copy scrim, angled. Up here every word is in the left
     column and the right half of the section is under the deck,
     which is a photograph in its own card and needs no help — so
     the scrim is spent where the text is and released where it is
     not, and the wash keeps most of its colour around the deck
     where it still reads as one.

     THE STOPS ARE ANCHORED TO THE COLUMN, NOT TO THE VIEWPORT,
     and that is the difference between this working and nearly
     working. Written as plain percentages the ramp is a fraction
     of the SCREEN, but the copy's position is set by a centred
     1200px container — so as the window widens the container's
     left edge moves right and the copy slides down the ramp into
     the falloff. Measured: at 1440 an inactive title sat at
     3.68:1 and the same title at 1920 sat at 3.00:1, on identical
     CSS, purely because the window was wider.

     50% is the one figure that does hold, because the container
     is centred and so its midline is the viewport's at every
     width. The left column runs from the container's left edge to
     half a column-gap short of that midline, so holding full
     strength to `50% - space-8` covers the whole column with a
     little to spare, whatever the window is doing.

     THE FALLOFF THEN RUNS ALL THE WAY TO THE RIGHT EDGE, and the
     length of it is the point. An earlier version was out by
     `50% + space-7`, which is a 112px ramp on a 1440px window —
     short enough that the eye reads it as the edge of a dark
     panel rather than as a vignette, and there was a visible seam
     down the middle of the section. Spread across the whole right
     half it is a gradient nobody notices, which is what a scrim
     doing structural work should be. It costs nothing to spend
     the extra distance there: everything past the midline is
     either the deck, which is opaque, or ground.

     0.07 rather than 0 at the far edge, so the ramp does not
     arrive at exactly the unscrimmed wash on the last pixel. */
  

  /* The frame that pins. sticky rather than fixed, so it releases
     itself at both ends of the track instead of needing anything
     to tell it when the section is over.

     height, not min-height. The deck below sizes its cards off a
     percentage of this box, and a percentage of min-height is
     indefinite — the cards would collapse to their content, which
     for an absolutely positioned <img> is nothing.

     The padding is on the frame and not on the section, because
     the section's own padding is now spread over four screens of
     track where it does nothing, and what actually needs a margin
     is the pinned screen. clamp against vh rather than a flat
     --space-7: at 1024x768, the shortest window this layout runs
     at, 96px of padding plus the intro plus four amenities does
     not fit, and the padding is the part that can give. */
  

  /* The left column's own rhythm, and now the ONLY thing between
     the intro and the list. */
  

  /* display: block undoes the display: contents the phone layout
     needs. Dissolved, the intro is not a box at all and its three
     children become siblings of the list — which is the phone
     layout and wrong in here, where the intro has to be one flex
     item of the column above. */
  

  /* The subhead's own bottom margin is double spacing in here: the
     column's flex gap already separates the intro from the list, so
     the two stack and the space comes out 32px wider than it reads
     as. Worth naming rather than just deleting, because it is not
     cosmetic — that 32px is 32px the list does not have inside a
     frame it is not allowed to overflow, and it is the single
     cheapest thing in this column. */
  

  /* THE INTRO'S MEASURE, SET BY HAND at 430px.

     This overrides the global max-width: 46ch, which in this column
     binds at about 414px — near enough to the same place that the two
     wrap identically. Both put the intro on five lines.

     THAT FIFTH LINE IS THE THING TO KNOW ABOUT. This rule used to be
     max-width: none, letting the intro use the whole ~536px column
     and wrap to four, and the note that stood here recorded why: the
     line it saves is ~28px, the pinned frame cannot be scrolled, and
     so every pixel the left column spends is a pixel off the margin
     the height gate below is built on. Putting the cap back spends
     it again.

     The gate was re-measured after this change rather than left to
     chance — see its note for the new numbers. Short version: the
     column now overflows the frame at a taller window than it used
     to, so the gate moved up with it, and the min-height in the
     media query above is the result. If this measure changes again,
     re-measure the gate again.

     430px rather than 26.875rem is deliberate here: it is a fixed
     measure the client asked for, not one that should stretch when
     the root font size does. */
  

  /* Column 2 by hand rather than left to auto-flow, for the same
     reason .location-grid above places its two children by hand:
     auto-placement starts guessing the day a third child turns up
     in here. No grid-row any more — there is one row now, and the
     note on .process explains why spanning two was the problem. */
  

  /* The deck is CAPPED, not stretched, and the cap is the front
     card's height rather than the stage's.

     It used to be height: 100%, which filled whatever the pinned
     frame had — fine at 900px of window, wrong above it: at 1080
     the card came out 936px against a 784px source, so the crop
     opened up top and bottom and the deck read as a column rather
     than as a card. 786px is the source's own height, so at that
     size and above the photograph is shown uncropped and the deck
     keeps a card's proportions on any monitor.

     min(), so short windows are unaffected — there the frame is
     the smaller of the two and the cap never engages. The peek is
     added back on top for the same reason as before: it is room
     for the cards behind, not part of the front one.

     No aspect-ratio, still: the height is stated here and asking
     for a ratio as well would drive the WIDTH off it and take the
     deck out of its column. Width is the grid's business.

     A definite height also means the stage no longer stretches to
     its grid area, so it sits at the top of it — which puts the
     deck's top edge on the eyebrow's, the one alignment the two
     columns share. */
  

  /* The card gives up the rail; everything else about it is
     unchanged, including the peek at the bottom. Stated here rather
     than in the base rule because the rail only exists up here — on
     a phone there is no deck to take it out of. */
  

  /* THE DOTS: four of them down the right of the front card, saying
     how many amenities there are and which one is up.

     Centred on the CARD and not on the stage. The stage is the card
     plus --stack-peek, the strip the cards behind show through at the
     bottom; centring on that would push the rail down by half the
     peek and leave it visibly low against the photograph it belongs
     to. Subtracting the peek first puts the middle dot on the middle
     of the picture.

     right: 0 is the stage's own right edge, which is the outer edge
     of the rail the card just gave up — so the dots sit in that strip
     and never over the photograph. */
  

  /* THE BUTTON IS THE TARGET, THE ::before IS THE DOT, and the two
     are deliberately different sizes. A 6px dot is the right mark
     and a 6px control is not one — the rail is 40px wide and the
     dots are 22px apart, so the button takes all of that and the
     visible dot floats in the middle of it. Nothing about the look
     changes; what changes is that the thing you are aiming at is
     40x22 rather than 6x6.

     display: block on the ::before plus margin: auto centres the
     mark in a button that is much larger than it. */
  

  /* 6px, and it is scaled rather than resized for the active state.
     A width/height change relayouts the rail and nudges every dot
     under it by a pixel or two on each step; a transform is composited
     and moves nothing. The mark is centred in its button either way,
     so the growth reads as it should — from the middle out.

     0.30 for an inactive dot is a decorative level and deliberately
     below any text floor. The dots duplicate what the <ol> already
     announces and each button carries its amenity's name for a
     screen reader, so nothing rests on the mark itself being
     legible — it is a shape you glance at, and four dots at a text
     contrast beside a photograph read as a row of bullet points. */
  

  

  /* A dot the pointer is over comes halfway up, which is the whole
     affordance: these look like an indicator, and the hover is what
     says the indicator is also a control. Not on the active one —
     it is already at full and there is nowhere for it to go.

     :focus-visible is the page's own ring from the top of this file
     and is not restated here, but the ring has to have something to
     draw around: an outline on a 6px pseudo element inside a 40px
     button would be a ring floating in the middle of nothing, so it
     goes on the button and gets a radius that suits the box. */
  
  

  /* The pinned deck is back, so the per-step copies would be the
     same four photographs a second time, down the other column. */
  

  /* THE BUTTON STAYS, AND CHANGES WHAT IT IS THE FACE OF. On a
     phone it is the photograph, and pressing it opens the
     description. Up here there is no photograph in this column, so
     it becomes the WHOLE ROW — numeral and name — and pressing it
     goes to that amenity. One control per amenity at both widths,
     one meaning at both widths, and the only thing that differs is
     what "go to this one" costs: a fold on a phone, a scroll here.
     script.js carries the branch.

     grid-column: 1 / -1 rather than a width, because the row is a
     two-track grid and the button is meant to be the row. It sits
     UNDER the caption in z-order and the caption is pointer-events:
     none, so a press on the name passes through to the button
     behind it — the same arrangement the phone uses, and for the
     same reason: the alternative is a control with a dead patch
     wherever there happens to be text.

     The radius is for the focus ring, which is the page's own from
     the top of this file and needs a box worth drawing around. */
  

  /* THE LIST, COMPACT. This is what the pin bought: the steps stop
     being 60vh scroll boxes and go back to being list items, so
     all four fit on one screen with the deck beside them.

     A grid with a gap rather than padding on each step, so the
     space between two amenities is one number in one place — and
     so it can shrink on a short window without also shrinking the
     space above the first one, which is the row gap's job.

     align-self: start packs the list under the intro rather than
     stretching it down the column: at four items the leftover
     space belongs below the list, not spread through it. */
  

  /* THE STEP: A NUMERAL DOWN THE SIDE, the name and its line beside
     it. On a phone the numeral sits above the photograph; up here
     there is no photograph in this column and the number goes where
     a chapter number goes, in the margin of the thing it numbers.

     --process-num is the numeral's size and it is ALSO THE HEIGHT OF
     A CLOSED STEP, which is the reason it is on a vh clamp rather
     than a flat size. The description below unfolds inside this row,
     so the taller the numeral the less an amenity lighting up costs
     the list. Measured at 1024x720: a closed step is 40px, an open
     one 88px, and the column measures 630/621/612/603px with the
     first/second/third/fourth amenity up — a 27px spread end to end,
     and the reason it is not the full 48px difference between a
     closed step and an open one is that 40px of the open step's
     height was already there as the numeral. Take the numeral back
     to the 16px the phone uses and the whole 48px lands on the
     column instead.

     THE vh COEFFICIENT IS PART OF THE HEIGHT GATE'S ARITHMETIC. It
     was 6.6 and is 6.2 because the gate's clearance at its own floor
     was 11px, which is inside the noise; 6.2 buys 9 of that back and
     costs nothing above about 900px of window, where the 4.25rem cap
     is what binds anyway. Re-measure the gate if this moves.

     The first track is stated in the numeral's own units rather than
     left to `auto`, so every title starts at the same x whatever
     digit is beside it — `auto` is the width of the glyph, and a 1 is
     narrower than a 4. 0.62em is a comfortable body over the widest
     digit in this serif at any size the clamp reaches.

     align-items: center hangs the numeral against the middle of the
     name-and-line block, which is where it sits in the design: above
     the title on a closed step, spanning title and line on an open
     one, without either being told about the other. */
  

  /* The numeral, at display size and without its leading zero.

     `/ ""` IS NOT DECORATION — it is what takes the generated text
     out of the accessibility tree. The count and the position in it
     are already announced by the <ol> this sits in, so a screen
     reader reading "one Lodging two Hull and Hearth" is the same
     information twice. A browser that does not support the alt
     syntax ignores the whole `content` value rather than half of it,
     which is why the fallback declaration above it is there: it gets
     the numeral, announced, which is the behaviour this always had.

     THE CONTRAST RULE CHANGES WITH THE SIZE, and this is the case
     the note on the base rule flagged. At 16px the numeral was
     ordinary text at a 4.5:1 floor and had to be held at 0.58 to
     clear it. At 44px and up it is not being read as text at all —
     it is aria-hidden by the line above, it duplicates the list
     ordinal, and it is a rule of the layout the way a hairline is.
     That is what buys the level below, and it is the whole reason
     the design can have a ghost numeral rather than a legible one. */
  

  /* Both halves of the step in the second column, stacked by the
     flow. The caption is not a grid item's grid — it is the box the
     phone layout needs for its scrim, and up here it is just a
     wrapper that keeps the name and the line together in one cell. */
  

  /* The name is a line in the left column again, with the deck
     carrying the photographs. Everything the phone overlay needed —
     the band, the padding, the corners, the shadow — comes off,
     because there is nothing under it to be read against.

     The band is on .process__caption, so that is where most of it is
     undone. Its pointer-events: none STAYS, though — that used to
     come off here on the grounds that the name up here was ordinary
     copy rather than the face of a button, and it is the face of a
     button again: the whole row is the target now. See
     .process__toggle above. */
  

  

  /* THE LINE, UNDER THE NAME OF THE AMENITY IT DESCRIBES, and only
     on the one the reader is level with.

     It used to be printed on the pinned photograph instead, and the
     note that stood here gave the reason: four descriptions open at
     once in a frame that cannot be scrolled is about 200px the
     column does not have. That reason does not survive the design it
     was written for — ONE is open at a time now, not four, and it
     unfolds inside a row the numeral beside it has already made
     tall. The measured cost to the column is the difference between
     a 44-68px numeral and a title plus two lines, which is about ten
     pixels, not two hundred.

     Same 0fr-to-1fr fold as the phone, and for the same reason —
     see the base rule. What changes is only what it is being read
     against: there it is white-on-photograph inside a scrim, here it
     is copy on the section's own ground, so the overlay colour and
     the text-shadow that goes with it both come off.

     :not(.is-active) is stated rather than left to the base rule
     because .is-open can survive a rotate or a resize from the phone
     layout, and a stale one would leave a second description hanging
     open under a dimmed name. Active is the only thing that opens a
     line up here. */
  

  

  

  /* THE DIM, RESTATED FOR THE BIG NUMERAL. The base pair — 0.50 on
     the title, 0.58 on the numeral — was two numbers because the two
     were on opposite sides of the 24px large-text threshold and had
     different contrast floors. Up here the numeral is 44px and up,
     aria-hidden, and duplicating an ordinal the <ol> already carries,
     so it is out of that argument entirely and free to sit where the
     design wants it: a ghost in the margin, present enough to count
     and quiet enough that the name beside it is what you read. 0.08
     against 0.38 on the active step is a far wider spread than the
     title's, on purpose: a numeral four times the size of a title
     carries four times the ink at the same level, and matched levels
     would make it the louder half of the row.

     THE TITLE IS AT 0.40 AND THAT IS THE FLOOR, not a preference. It
     was 0.50 and was asked to fade further. Measured on the worst
     patch of this section's wash, across three viewports and six
     scroll positions, with the copy hidden for each sample so the
     ground under the words is the real one rather than a token:

       opacity   worst ratio
       0.50        4.44:1     where it was
       0.44        3.75:1
       0.40        3.36:1     <- here, +12% on the floor
       0.36        3.00:1     exactly on it, nothing in hand
       0.32        2.67:1     fails
       0.28        2.37:1     fails

     The floor is 3:1 rather than 4.5:1 because the title is large
     text, and it is large text BY NOTHING: it computes to exactly
     24px at every viewport, which is the threshold for non-bold type.
     SHRINK THIS TITLE AND THE WHOLE TABLE MOVES UP A FLOOR. At 4.5:1
     nothing in it passes, 0.50 included, and the dim would need
     re-deriving rather than re-tuning. If the type scale is ever
     retuned, re-run the sweep before trusting any of these figures.

     :not(.is-active) rather than leaning on the base rule and undoing
     it, so a stale .is-open left over from the phone layout cannot
     light a step the reader is not on. */
  

  

  /* HOVER IS THE WHOLE AFFORDANCE. A dim row with a ghost numeral
     beside it looks like a list, because up until now it was one —
     nothing about the arrangement says the row can be pressed. The
     lift on hover is what says it, and it is the same move the dots
     make for the same reason.

     Halfway rather than all the way: at full the hovered row is
     indistinguishable from the active one and the section briefly
     claims you are somewhere you are not. 0.70 against 0.40 is
     plainly a response and plainly not the highlight.

     :not(.is-active) because the active row is already at full and
     has nowhere to go — and a hover that visibly does nothing reads
     as a control that is broken rather than one that is current.

     The numeral comes up with its title. It is decorative and out of
     the contrast argument either way, so the only question is
     whether the row lifts as one block, and it should — a title
     brightening beside a numeral that does not reads as two things
     in a row rather than one row. */
  

  

  /* And the active one. No hue swap up here, unlike the 16px version
     in the base rules: that teal was doing the work of saying "you
     are on this one" when the numeral was small and the title beside
     it only 0.50 away from its neighbours. At this size the jump from
     0.08 to 0.38 — nearly five times the ink — is the signal on its
     own, and a tint at 38% of white is a colour nobody can see. */
  

  /* The CTA, pinned version: back to hugging its own text and
     sitting on the list's left edge.

     align-self, not text-align. The column is a flex container up
     here, so a stretched item is the default and the button would
     run the full width of the column — 536px of brand fill next
     to a 16px numeral. align-self: flex-start plus width: auto is
     what takes it back to its content width; text-align would
     only move the label inside a box still 536px wide.

     And NOT display: inline-block, which was the first thing
     written here and does nothing: a flex container blockifies
     its items, so the declaration is discarded and the computed
     value comes back "block" either way. The width and the
     alignment are the whole mechanism.

     The margin-top goes because the column's own gap now owns
     that space, and the two would otherwise stack. */
  


  /* Reduced motion turns the deck back into a crossfade, so the two
     cards that were peeking out at the bottom are not there any
     more and the strip they needed would be bare stage under the
     photograph. Zeroed, the front card fills the frame. */
  @media (prefers-reduced-motion: reduce) {
    
  }

  /* The steps are not scroll boxes any more, so there is nothing
     for a snap point to snap to — the page scrolls past a pinned
     frame and every position in the track is a legitimate place to
     stop. The document-level scroll-snap-type this section used to
     set has gone with them, which also gives the nav anchors their
     ordinary behaviour back on the way past. */
}

/* ============================================================
   SCROLL REVEAL  —  a section arrives as you reach it
   ------------------------------------------------------------
   Everything below the hero starts a little low and a little
   transparent and settles as it comes into view. Once. Scrolling
   back up does not replay it: a page that re-animates on every
   pass stops being a page and starts being a toy.

   THE HIDDEN STATE IS GATED ON .reveal-on, and that gate is the
   whole safety story. The class goes on <html> from the inline
   script in <head>, and only ever where there is an
   IntersectionObserver to take it off again and the visitor has
   not asked for less motion. So the page with no JavaScript, the
   page whose JavaScript failed, and the page whose visitor wants
   it still are all the same page: everything visible, nothing
   waiting on an event that is never coming. Never write the
   hidden state into a plain selector.

   TWO SHAPES IN THE MARKUP:

     [data-reveal]         one element, on its own.
     [data-reveal-group]   a parent whose direct children come in
                           one after another. Nothing goes on the
                           children — the selectors below reach
                           them — so adding a sixth stay card is
                           still just adding a sixth stay card.

   THREE WAYS IN, and which one an element gets is not taste, it
   is what that element can safely be transformed by:

     (default)   RISE     translateY + fade. Ordinary blocks.
     "settle"    SETTLE   scale 0.98 -> 1 + fade. Cards inside a
                          rail. A downward translate inside a
                          scroll container adds real scrollable
                          height to it; a scale down cannot.
     "fade"      FADE     opacity alone. Anything already moving
                          (the review rail) or pinned with
                          position: sticky, where a transform is a
                          containing block waiting to happen.

   Written on the group as data-reveal-group="settle" to set the
   default for its children, or on one element as
   data-reveal="fade" for that element alone. A child's own
   attribute wins, which is what the ordering of the two variant
   blocks below is for — do not reorder them.
   ============================================================ */
:root {
  --reveal-lift:    var(--space-3);   /* 16px. The hero rises 8px, but a
                                         whole section is a bigger object
                                         and reads as stuck at that
                                         distance. */
  --reveal-stagger: 70ms;             /* the hero's interval, kept, so the
                                         page has one rhythm and not two */
}

/* --dur-reveal, not --dur-ui: this is a first-time entrance, the
   category the 300ms ceiling for UI does not apply to. And the
   same two properties the rest of the page animates — transform
   and opacity are the two a compositor can do without going back
   through layout. */
.reveal-on [data-reveal],
.reveal-on [data-reveal-group] > * {
  opacity: 0;
  transform: translate3d(0, var(--reveal-lift), 0);
  transition: opacity   var(--dur-reveal) var(--ease-out),
              transform var(--dur-reveal) var(--ease-out);
  transition-delay: calc(var(--reveal-i, 0) * var(--reveal-stagger));
}

/* The ladder, in CSS rather than counted out in the script,
   because a child that is handed its delay after first paint has
   already been painted without one. It stops climbing at the
   seventh child: past there the delay holds, so a client shipping
   twelve stays does not leave the last one waiting most of a
   second — long after the eye has moved on and the run has
   stopped reading as one movement. */
.reveal-on [data-reveal-group] > *:nth-child(2)    { --reveal-i: 1; }
.reveal-on [data-reveal-group] > *:nth-child(3)    { --reveal-i: 2; }
.reveal-on [data-reveal-group] > *:nth-child(4)    { --reveal-i: 3; }
.reveal-on [data-reveal-group] > *:nth-child(5)    { --reveal-i: 4; }
.reveal-on [data-reveal-group] > *:nth-child(6)    { --reveal-i: 5; }
.reveal-on [data-reveal-group] > *:nth-child(n+7)  { --reveal-i: 6; }

/* 0.98, not 0. Nothing in the world appears out of nothing, and a
   card that grows from a point reads as a notification rather
   than as a photograph that was always there. */
.reveal-on [data-reveal-group="settle"] > * { transform: scale(0.98); }
.reveal-on [data-reveal-group="fade"]   > * { transform: none; }

/* Second, and deliberately: these weigh the same as the group
   rules above, so it is source order that lets one child opt out
   of what its group does. */
.reveal-on [data-reveal="settle"] { transform: scale(0.98); }
.reveal-on [data-reveal="fade"]   { transform: none; }

.reveal-on [data-reveal].is-revealed,
.reveal-on [data-reveal-group] > .is-revealed {
  opacity: 1;
  transform: none;
}

/* The gate is read once, at load. This is for the visitor who
   turns the preference on mid-session — without it every block
   still below them stays at opacity 0 for good, because
   _template.css has just collapsed the transition that was going
   to bring it back. */
@media (prefers-reduced-motion: reduce) {
  .reveal-on [data-reveal],
  .reveal-on [data-reveal-group] > * { opacity: 1; transform: none; }
}

/* ============================================================
   WALDEN RETREATS  ·  the four tent types
   The first Where You'll Stay line names the four climate-controlled
   tent types in <strong>. The brand has no bold (strong inherits, see
   _template.css), so these take Proxima Nova Medium, which the Typekit
   kit serves, and the primary ink in place of the line's secondary:
   "bold them subtly" (Brandon, 2026-10-02). script.js clones the
   figcaption into the feature list, so the same rule reaches both.
   ============================================================ */
.stay__line strong {
  font-weight: 500;
  color: var(--color-text-primary);
}

/* ============================================================
   5b · WEDDINGS AT WALDEN  ·  the invitation
   (Walden Retreats; not in the template.) Ninth pass, 2026-11-03. The
   markup note in index.html says what it is; this is how it is drawn.

   THE PAPER is the client's ivory floral pattern on a layer that starts
   one tear-height ABOVE the section, so its torn top edge lies over the
   foot of the stays band (the weddings section comes later in the page,
   so it paints over it; stays sets no z-index). The tear is
   wedding-tear.svg as a mask over that top strip, the rest of the layer
   solid page colour; a drop shadow on the parent takes the torn shape
   and is clipped to it. The pattern fades into that page colour over
   the section's last 30%, so Local Favorites follows with no seam.

   THE ARCH is a semicircle over a 4:5 film. Its top radius is half its
   width, written in cqw against the arch, not 999px: CSS scales every
   corner down together when two radii overrun a side, and 999px would
   have shrunk the 16px bottom corners to almost nothing. The fine sage
   rule 12px outside it is the stationery border, concentric with it.

   THE OPENING: --open, 0 to 1, written by script.js (WEDDINGS STAGE) at
   twenty-four steps. The film's clip takes in up to 16% of the width
   from each side, its top radius following, so it reads as a slender
   doorway widening into the full arch; the 450ms transition runs
   between the steps (the hero's clip reveal works the same way). 1 is
   the rest state: without the script or under reduced motion the arch
   is simply open.

   CONTRAST, measured with the glyphs hidden and the worst pixel kept:
   see the README.
   ============================================================ */
/* ONE SCREEN (Brandon, 2026-11-03: "100vh so no additional scrolling
   needs to be done to see all of the information"). The section is at
   least the screen's height and the arch is sized to what the screen
   leaves: stacked, its width is the height that remains after the words
   (measured: 34.5rem of them on a tablet, 24rem on a phone, where the
   gaps are tighter and the details' rings overlap the film) times the
   box's width over its height (0.9226 with a 4:5 film, 0.8128 with a
   phone's 7:10), and never under 16rem; on a desk, its height is the
   screen less the padding.
   Stacked, it is measured against 100lvh, the screen with the browser's
   toolbars tucked away, which is how a phone shows the page while its
   reader scrolls down to this section. A very short phone (an SE)
   still runs a little past the screen rather than shrink the film to a
   stamp. */
.section--weddings {
  --wed-pad: clamp(var(--space-4), 4vw, var(--space-9));
  --wed-tear: clamp(2.25rem, 4vw, 3.5rem);
  --wed-word: clamp(3rem, 9vw, 5rem);
  --wed-film: 0.8;
  --wed-arch-w: min(calc(100vw - 0.5rem), max(16rem, min(32rem, calc((100lvh - 34.5rem) * 0.9226))));
  position: relative;
  isolation: isolate;
  overflow-x: clip;
  min-height: 100svh;
  display: grid;
  align-content: center;
  padding: var(--space-8) var(--wed-pad);
}

/* ---- the paper ----------------------------------------------------- */
.weddings__paper {
  position: absolute;
  inset: calc(-1 * var(--wed-tear)) 0 0;
  z-index: -1;
  pointer-events: none;
  filter: drop-shadow(0 -4px 12px rgba(9, 11, 14, 0.3));
  /* The shadow is for the torn edge only: clipped at the sides and the
     foot (clip-path applies after the filter), open above. The 2px at
     the foot takes the anti-aliased sliver of shadow a fractional
     section height leaves; what it cuts is page colour on page colour. */
  clip-path: inset(calc(-2 * var(--wed-tear)) 0 2px 0);
}
.weddings__ground {
  position: absolute;
  inset: 0;
  display: block;
  /* The page colour under the pattern, solid, so the paper is there
     before the image arrives and the pattern's fade ends in the page
     colour, not in nothing: a paper that faded to transparent let its
     own drop shadow show through as a grey haze. */
  background: var(--color-bg-primary);
  /* The torn strip on top, solid below it (1px of overlap so no hairline
     opens between the two). */
  -webkit-mask:
    url("assets/img/wedding-tear.svg") left top / auto var(--wed-tear) repeat-x,
    linear-gradient(#000 0 0) left calc(var(--wed-tear) - 1px) / 100% 100% no-repeat;
          mask:
    url("assets/img/wedding-tear.svg") left top / auto var(--wed-tear) repeat-x,
    linear-gradient(#000 0 0) left calc(var(--wed-tear) - 1px) / 100% 100% no-repeat;
}
.weddings__ground img {
  display: block;
  width: 100%;
  height: 100%;
  object-fit: cover;
  object-position: 50% 0;
  -webkit-mask-image: linear-gradient(180deg, #000 0%, #000 70%, transparent 100%);
          mask-image: linear-gradient(180deg, #000 0%, #000 70%, transparent 100%);
}

/* ---- the invitation ------------------------------------------------ */
.weddings__card { display: none; }
.weddings__invite {
  display: flex;
  flex-direction: column;
  align-items: center;
  /* The full width, not shrink-to-fit: as a grid item with auto margins
     it would take its content's width, and the arch's 100% would then
     resolve against the title. */
  width: 100%;
  max-width: 64rem;
  margin-inline: auto;
  text-align: center;
}

/* The eyebrow over the title, and the section's heading: the wide
   eyebrow style in the accent, so it reads apart from the line under
   the title, which is grey between rules. */
.weddings__kicker {
  margin: 0 0 var(--space-3);
  color: var(--color-text-accent);
}

.weddings__word {
  font-family: var(--font-display);
  font-weight: var(--fw-display);
  font-size: var(--wed-word);
  line-height: 1;
  letter-spacing: -0.01em;
  white-space: nowrap;
  color: var(--color-text-primary);
  /* The face's descenders hang about 0.16em below a line-height of 1,
     so the gap to the line under it is sized in em, with the title,
     plus a step of the scale; it holds whatever the title is. */
  margin: 0 0 calc(0.18em + var(--space-3));
}

/* The entrance: each letter from blurred to sharp, one after another.
   Hidden only behind .reveal-on, so without the script, or under
   reduced motion, the title is simply there. The letters stay inline
   so the face's kerning holds across them. */
.reveal-on .weddings__word > span {
  transition: opacity 900ms var(--ease-out), filter 900ms var(--ease-out);
  transition-delay: calc(var(--i) * 70ms);
}
.reveal-on .section--weddings:not(.is-in) .weddings__word > span {
  opacity: 0;
  filter: blur(12px);
}

/* The line under the title, between two short sage rules. */
.weddings__eyebrow {
  display: flex;
  align-items: center;
  gap: var(--space-3);
  margin: 0;
  color: var(--color-text-secondary);
}
.weddings__eyebrow::before,
.weddings__eyebrow::after {
  content: "";
  width: var(--space-7);
  height: 1px;
  background: var(--accent-400);
}

/* ---- the arch ------------------------------------------------------ */
/* THE ARCH is the garland's box: the photographed garland fills it and
   the film sits inside at the place the garland was drawn round
   (2026-11-03). The garland was generated over a template of this exact
   arch, a 4:5 film with a semicircular top, so its curve and the film's
   meet; the numbers below are where that film fell in the cropped
   photograph (measured along the stem): 7.86% in from the left, 0.0585
   of the box's width down, 82.03% of the width, down to the box's foot.
   --wed-arch-w is the whole box's width.

   THE FILM'S SHAPE is --wed-film, width over height: 4:5 (0.8), the
   garland's own, except on a phone, where it is 7:10 (Brandon,
   2026-11-03: "extend the height of the video"). The box's height
   follows from it; the garland keeps its own shape at the top of the
   box, so on a phone the film simply runs on below where the garland's
   stems end, as an arch is dressed over the top and partway down. */
.weddings__arch {
  --open: 1;
  --wed-in: calc((1 - var(--open)) * 0.16);
  position: relative;
  width: var(--wed-arch-w);
  height: calc(var(--wed-arch-w) * (0.0585 + 0.8203 / var(--wed-film)));
  margin-top: var(--space-6);
  /* On a phone the garland may reach past the gutters; a flex item wider
     than its column starts at the left, so equal negative margins centre
     it instead. */
  margin-inline: min(0px, calc((100% - var(--wed-arch-w)) / 2));
}
/* The film's soft shadow, on a wrapper of its own (a drop shadow takes
   the clipped film's shape). It is also the container the film's cqw
   radii are measured against, not the arch: a size container is its own
   stacking context, and on the arch it would trap the garland under the
   invitation card. */
.weddings__lift {
  position: absolute;
  left: 7.86%;
  top: calc(var(--wed-arch-w) * 0.0585);
  width: 82.03%;
  bottom: 0;
  container-type: inline-size;
  filter: drop-shadow(0 24px 32px rgba(9, 11, 14, 0.16));
}

/* THE GARLAND (Brandon, 2026-11-03: real flowers that "follow the arch
   outline", after a line-drawn vine and then two separate sprays that
   read as cut-outs; then "a more thin floral outline", so a single stem
   of eucalyptus and olive with small roses and one cluster at the
   upper-left shoulder, its cut-out rim cleaned of the dark backdrop).
   Over the film, and on a desk behind the card
   (Brandon: "behind the card, not in front"): z-index 0 paints it after
   the film, which comes first in the arch, and under the card at 1.
   It settles in once the arch has opened (.is-in); behind .reveal-on
   only, so without the script or under reduced motion it is simply
   there. */
.weddings__garland {
  position: absolute;
  inset: 0 0 auto;
  aspect-ratio: 1692 / 1834;   /* its own shape, whatever the film's */
  z-index: 0;
  pointer-events: none;
}
.reveal-on .weddings__garland {
  opacity: 0;
  translate: 0 12px;
  transition: opacity 800ms var(--ease-out) 300ms, translate 1000ms var(--ease-out) 300ms;
}
.reveal-on .section--weddings.is-in .weddings__garland { opacity: 1; translate: 0 0; }

/* THE BREEZE (Brandon, 2026-11-03: "the leaves subtly move"). The
   garland is ten overlapping sprigs, each placed in the box and pivoting
   on the point of the arch's line at its middle (inline, from
   snippets/wedding-garland-split.py). Each rocks a degree either way,
   and each a little behind the one before it along the arch (--k), so
   the movement travels round the garland like a breeze, neighbours
   nearly in step so their soft seams never part. A degree is a pixel or
   two at the leaf tips. rotate only, so it runs on the compositor. It
   runs only while the section is on screen (.is-seen) and not at all
   under reduced motion.

   SHARPNESS (Brandon: "it just looks blurry now"). A rotating layer is
   resampled every frame, so the sprigs are full size, finer than any
   screen shows them, and they carry no filter: a drop shadow on each
   cost a fifth of their sharpness, measured. The shadow is one still,
   pre-blurred image under them instead (.weddings__garland-shadow), a
   shadow that soft having no need to move. */
.weddings__garland-shadow {
  position: absolute;
  height: auto;
  max-width: none;
  translate: 0 1%;
}
.weddings__sprig {
  --sway: 1deg;
  position: absolute;
  height: auto;
  max-width: none;
  will-change: rotate;
  animation: weddings-sway 5.6s ease-in-out infinite alternate;
  animation-delay: calc(var(--k) * -0.5s);
  animation-play-state: paused;
}
.section--weddings.is-seen .weddings__sprig { animation-play-state: running; }
@keyframes weddings-sway {
  from { rotate: calc(-1 * var(--sway)); }
  to   { rotate: var(--sway); }
}
.weddings__film {
  position: absolute;
  inset: 0;
  overflow: hidden;
  background: var(--brand-950);
  border-radius: 50cqw 50cqw var(--radius-lg) var(--radius-lg);
  clip-path: inset(0 calc(var(--wed-in) * 100%)
    round calc((0.5 - var(--wed-in)) * 100cqw) calc((0.5 - var(--wed-in)) * 100cqw) var(--radius-lg) var(--radius-lg));
  transition: clip-path 450ms var(--ease-out);
}
/* The 0.5px accent-300 hairline Brandon asked for on the picture, and
   under it a soft inner shadow, so the film reads as seen through an
   opening (Brandon, 2026-11-03: "looking in"): deeper from the top, as
   light falls, and a faint falloff all round. Inset shadows follow the
   arch's curve, and this layer is over the film, so it shades the
   playing video too. */
.weddings__film::after {
  content: "";
  position: absolute;
  inset: 0;
  z-index: 2;
  border-radius: inherit;
  box-shadow:
    inset 0 0 0 0.5px var(--accent-300),
    inset 0 18px 36px -10px rgba(9, 11, 14, 0.42),
    inset 0 0 48px rgba(9, 11, 14, 0.2);
  pointer-events: none;
}
.weddings__arch.is-settling .weddings__film { transition: none; }

/* The stage reaches 6% past the arch at each end, the room the drift
   uses. */
.weddings__stage {
  position: absolute;
  inset: -6% 0;
  container-type: size;
  will-change: transform;
}
.weddings__poster,
.weddings__video {
  position: absolute;
  inset: 0;
  width: 100%;
  height: 100%;
}
.weddings__poster { object-fit: cover; object-position: 50% 50%; }
.weddings__video {
  overflow: hidden;
  opacity: 0;
  transition: opacity 900ms var(--ease-out);
}
.section--weddings.is-playing .weddings__video { opacity: 1; }
/* Cover the stage with a 16:9 film whatever the stage's shape. */
.weddings__video iframe {
  position: absolute;
  top: 50%;
  left: 50%;
  width: max(100cqw, 177.78cqh);
  height: max(100cqh, 56.25cqw);
  transform: translate(-50%, -50%);
  border: 0;
  pointer-events: none;
}

/* ---- the details and the button ------------------------------------ */
/* What the day holds, as the order of events on a wedding program
   (Brandon, 2026-11-03: the boxed panel "needs to be designed better"):
   three moments in sequence, each a fine sage glyph in a thin ring, its
   name in small sage capitals and its detail in the display face. One
   hairline runs behind the three rings, joining them in order; the
   rings are filled with the page colour so the line stops at each.
   Kept to one line a value, so "in the Lodge" stays off the dinner.
   They rise in one after another (a reveal group). */
.weddings__details {
  --wed-ring: 2.75rem;
  position: relative;
  list-style: none;
  display: grid;
  grid-template-columns: repeat(3, minmax(0, 1fr));
  width: min(100%, 30rem);
  margin: var(--space-7) 0 0;
  padding: 0;
}
.weddings__details::before {
  content: "";
  position: absolute;
  top: calc(var(--wed-ring) / 2);
  left: calc(100% / 6);
  right: calc(100% / 6);
  height: 1px;
  background: var(--accent-300);
}
.weddings__details li {
  display: flex;
  flex-direction: column;
  align-items: center;
  padding-inline: var(--space-2);
}
.weddings__details-icon {
  position: relative;
  display: grid;
  place-items: center;
  width: var(--wed-ring);
  height: var(--wed-ring);
  margin-bottom: var(--space-3);
  border: 1px solid var(--accent-300);
  border-radius: 50%;
  background: var(--color-bg-primary);
  color: var(--color-text-accent);
}
.weddings__details-icon svg {
  width: 1.375rem;
  height: 1.375rem;
  filter: drop-shadow(0 0 3px color-mix(in oklch, var(--accent-400) 70%, transparent));
}
/* THE GLOW (Brandon, 2026-11-04: "have those icons glow a bit", then
   "not yellow, same color as the button"): a soft halo round each ring
   in the button's sage (accent-400, as the button's own glow), close in
   and stronger, then wider and fainter, with a thin white rim between
   ring and glow where it sits over the film. Sage, not white, so it
   shows on the white paper too. It is the box-shadow of an empty layer the
   ring's size, so nothing paints inside the ring, and only that layer's
   opacity moves: a slow breath, each ring out of step with the next,
   while the section is on screen (.is-seen, as the garland's breeze),
   and held still under reduced motion. The glyph has a faint sage
   light of its own. */
.weddings__details-icon::after {
  content: "";
  position: absolute;
  inset: -1px;
  border-radius: 50%;
  box-shadow:
    0 0 0 3px rgba(255, 255, 255, 0.5),
    0 0 16px 4px color-mix(in oklch, var(--accent-400) 70%, transparent),
    0 0 34px 10px color-mix(in oklch, var(--accent-400) 32%, transparent);
  opacity: 0.8;
  pointer-events: none;
  animation: weddings-glow 4.8s ease-in-out infinite alternate;
  animation-delay: calc(var(--glow-i, 0) * -1.6s);
  animation-play-state: paused;
}
.weddings__details li:nth-child(2) .weddings__details-icon { --glow-i: 1; }
.weddings__details li:nth-child(3) .weddings__details-icon { --glow-i: 2; }
.section--weddings.is-seen .weddings__details-icon::after { animation-play-state: running; }
@keyframes weddings-glow {
  from { opacity: 0.55; }
  to   { opacity: 1; }
}
.weddings__details-label {
  font-family: var(--font-body);
  font-size: var(--fs-text-xs);
  line-height: var(--lh-text-xs);
  letter-spacing: var(--ls-wide);
  font-weight: var(--fw-semibold);
  text-transform: uppercase;
  color: var(--color-text-accent);
}
.weddings__details-value {
  margin-top: var(--space-1);
  font-family: var(--font-display);
  font-weight: var(--fw-display);
  font-size: clamp(1.125rem, 1.7vw, 1.6rem);
  line-height: 1.2;
  color: var(--color-text-primary);
  white-space: nowrap;
}
.weddings__actions {
  display: flex;
  margin-top: var(--space-6);
}
/* THE BUTTON: the page's sage pill, given more presence for the one ask
   in the section (Brandon, 2026-11-02: "more attractive"). The arrow
   sits in its own dark chip at the right end; a highlight along the top
   edge and a faint sage glow lift it off the film. On hover the arrow
   slides out of the chip and a second one slides in behind it, as
   transitions so a quick pass in and out reverses cleanly. As the
   section arrives, one sweep of light crosses it, once. */
.weddings__cta {
  position: relative;
  isolation: isolate;
  overflow: hidden;
  display: inline-flex;
  align-items: center;
  gap: var(--space-4);
  padding: 6px 6px 6px var(--space-6);
  box-shadow:
    inset 0 1px 0 rgba(255, 255, 255, 0.45),
    inset 0 -1px 0 rgba(9, 11, 14, 0.12),
    0 14px 34px -14px color-mix(in oklch, var(--accent-400) 75%, transparent);
}
.weddings__cta-chip {
  position: relative;
  display: grid;
  place-items: center;
  flex: none;
  width: 40px;
  height: 40px;
  overflow: hidden;
  border-radius: 999px;
  background: var(--gray-950);
  color: var(--accent-200);
}
.weddings__cta-arrow {
  grid-area: 1 / 1;
  width: 18px;
  height: 18px;
  transition: transform 260ms var(--ease-out);
}
.weddings__cta-arrow + .weddings__cta-arrow { transform: translateX(-200%); }
@media (hover: hover) and (pointer: fine) {
  .weddings__cta:hover .weddings__cta-arrow { transform: translateX(200%); }
  .weddings__cta:hover .weddings__cta-arrow + .weddings__cta-arrow { transform: translateX(0); }
}
/* The sweep: behind the label and the chip, over the fill (the
   button's isolation keeps the negative z-index inside it). Off to the
   left and out of sight until the actions are revealed, so without the
   reveal, or under reduced motion, it never shows. */
.weddings__cta::after {
  content: "";
  position: absolute;
  inset: 0;
  z-index: -1;
  background: linear-gradient(105deg, transparent 35%, rgba(255, 255, 255, 0.4) 50%, transparent 65%);
  transform: translateX(-110%);
}
.reveal-on .weddings__actions.is-revealed .weddings__cta::after {
  transform: translateX(110%);
  transition: transform 1200ms var(--ease-in-out) 450ms;
}

/* ---- a phone: the stack, the button full width ---------------------- */
@media (max-width: 767px) {
  .section--weddings {
    --wed-word: clamp(3rem, 14.5vw, 4.5rem);
    --wed-film: 0.7;
    /* 0.8128 = the box's width over its height with a 7:10 film. */
    --wed-arch-w: min(calc(100vw - 0.5rem), max(16rem, min(30rem, calc((100lvh - 24rem) * 0.8128))));
    padding-block: var(--space-5);
  }
  .weddings__arch { margin-top: var(--space-4); }
  /* The details' rings sit on the film's foot, half over it (the
     reference Brandon sent), above it in the stacking order. */
  .weddings__details {
    --wed-ring: 2.5rem;
    position: relative;
    z-index: 1;
    margin-top: calc(var(--wed-ring) / -2);
  }
  .weddings__details li { padding-inline: var(--space-1); }
  .weddings__details-icon { margin-bottom: var(--space-2); }
  .weddings__details-value { font-size: min(1.125rem, 4.6vw); }
  .weddings__actions { margin-top: var(--space-5); }
  .weddings__actions { align-self: stretch; }
  .weddings__cta { flex: 1; justify-content: space-between; }
}

/* ---- a desk: the arch the screen's height, the words beside it -------
   Centred in one column the invitation left most of a wide screen as
   bare paper (Brandon, 2026-11-03). Here the arch stands on the left as
   tall as the screen allows and the words are centred in a column on
   its right, between two flexible rows so they sit on the arch's middle. */
@media (min-width: 880px) {
  .section--weddings {
    /* One line in the words' 30rem column: "Tie the Knot" is 5.43em
       wide in the display face, so 5.25rem at most. */
    --wed-word: clamp(3.25rem, 5.4vw, 5.25rem);
    --wed-arch-h: clamp(26rem, calc(100svh - 2 * var(--space-7)), 56rem);
    --wed-card-x: var(--space-10);
    /* As tall as the screen allows, but never so wide that the words'
       column drops under 20rem: a tall, narrow window would otherwise
       push the page sideways. */
    --wed-arch-w: min(calc(var(--wed-arch-h) * 0.9226), calc(100vw - 2 * var(--wed-pad) - var(--wed-card-x) - 20rem));
    padding-block: var(--space-7);
  }
  /* Three tracks: the arch, the words, and the card's margin beyond
     them. The card spans the last two and reaches the same distance back
     over the arch, so the words are centred on it. */
  .weddings__invite {
    display: grid;
    max-width: 82rem;
    grid-template-columns: auto minmax(0, 30rem) var(--wed-card-x);
    grid-template-rows: 1fr auto auto auto auto auto 1fr;
    grid-template-areas:
      "arch .       ."
      "arch kicker  ."
      "arch word    ."
      "arch line    ."
      "arch details ."
      "arch actions ."
      "arch .       .";
    justify-content: center;
    justify-items: center;
  }
  .weddings__card {
    display: block;
    grid-row: 2 / 7;
    grid-column: 2 / 4;
    position: relative;
    z-index: 1;
    margin: calc(-1 * var(--space-9)) 0 calc(-1 * var(--space-9)) calc(-1 * var(--wed-card-x));
    align-self: stretch;
    justify-self: stretch;
    pointer-events: none;
    /* Clean straight-edged paper (the deckled top and foot went,
       Brandon, 2026-11-03); the rip stays only at the section's top. */
    background: var(--color-bg-primary);
    box-shadow: 0 18px 40px -12px rgba(9, 11, 14, 0.18), 0 2px 6px rgba(9, 11, 14, 0.06);
  }
  /* The printed border. */
  .weddings__card::after {
    content: "";
    position: absolute;
    inset: var(--space-4);
    border: 1px solid var(--accent-300);
  }
  .weddings__kicker,
  .weddings__word,
  .weddings__eyebrow,
  .weddings__details,
  .weddings__actions { position: relative; z-index: 2; }
  .weddings__kicker { grid-area: kicker; }
  .weddings__word { grid-area: word; }
  .weddings__eyebrow { grid-area: line; }
  .weddings__arch { grid-area: arch; margin: 0; }
  .weddings__details { grid-area: details; margin-top: var(--space-8); }
  .weddings__actions { grid-area: actions; margin-top: var(--space-8); }
}
@media (prefers-reduced-motion: reduce) {
  .reveal-on .section--weddings:not(.is-in) .weddings__word > span { opacity: 1; filter: none; }
  .reveal-on .weddings__garland { opacity: 1; translate: 0 0; }
  .weddings__sprig { animation: none; }
  .weddings__details-icon::after { animation: none; }
}

/* ============================================================
   THE RESERVE SHEET (Walden build, 2026-11-05; not in the template)
   The 10% offer, raised from the foot of the screen when a visitor
   who has not signed up presses RESERVE YOUR STAY. Markup and the
   why at the foot of index.html; behaviour in script.js, THE
   RESERVE SHEET.

   The <dialog> fills the screen and paints nothing itself: the
   scrim and the panel inside it carry the motion, both keyed off
   .is-open, so opening and closing are plain transitions.

   THE MOTION. In on the iOS sheet curve (fast start, long soft
   landing), 560ms; out quicker, 300ms on an ease-in, so the panel
   leaves under its own weight rather than drifting. The scrim is a
   55% of the brand's darkest step, not a blackout: the page
   should still read as the page, with the sheet over it. While a
   finger pulls the panel down, --sheet-pull (0-1) thins the scrim
   with it.

   PHONE (the base): flush to the bottom edge, full width, 24px top
   corners, the photograph as a band across the top under a grab
   bar. FROM 768px: a floating card 24px off the foot, photograph on
   the left inset 8px (16px corners, concentric with the card's 24),
   words on the right.
   ============================================================ */
html.has-sheet { overflow: hidden; scrollbar-gutter: stable; }

.reserve-sheet {
  --sheet-lift: 0px;
  --sheet-pull: 0;
  --sheet-radius: 1.5rem;                 /* 24px */
  position: fixed;
  inset: 0;
  width: 100%;
  height: 100%;
  max-width: none;
  max-height: none;
  margin: 0;
  padding: 0;
  border: 0;
  background: transparent;
  overflow: hidden;
  color: var(--color-text-primary);
}
.reserve-sheet::backdrop { background: transparent; }

.reserve-sheet__scrim {
  position: absolute;
  inset: 0;
  background: color-mix(in oklab, var(--brand-950) 55%, transparent);   /* 38% until Brandon asked for darker, 2026-11-05 */
  opacity: 0;
  transition: opacity 300ms var(--ease-out);
}
.reserve-sheet.is-open .reserve-sheet__scrim {
  opacity: calc(1 - var(--sheet-pull));
  transition-duration: 480ms;
}

.reserve-sheet__panel {
  position: absolute;
  left: 0;
  right: 0;
  bottom: var(--sheet-lift);
  max-height: calc(100% - var(--sheet-lift) - var(--space-4));
  overflow-y: auto;
  overscroll-behavior: contain;
  background: var(--color-bg-primary);
  border-radius: var(--sheet-radius) var(--sheet-radius) 0 0;
  box-shadow: 0 -0.75rem 3rem -1rem color-mix(in oklab, var(--brand-950) 50%, transparent);
  padding-bottom: env(safe-area-inset-bottom, 0px);
  transform: translate3d(0, calc(100% + 2rem), 0);
  transition: transform 300ms cubic-bezier(0.4, 0, 1, 1);
  outline: none;
}
.reserve-sheet.is-open .reserve-sheet__panel {
  transform: translate3d(0, 0, 0);
  transition: transform 560ms cubic-bezier(0.32, 0.72, 0, 1);
}
/* A finger is moving it: no easing between pointer events. */
.reserve-sheet.is-dragging .reserve-sheet__panel,
.reserve-sheet.is-dragging .reserve-sheet__scrim { transition: none; }

/* THE GRAB BAR, over the photograph's top edge. Its row is the
   touch target (28px tall, full width); the bar itself is 40x5. */
.reserve-sheet__grab {
  position: absolute;
  top: 0;
  left: 0;
  right: 0;
  z-index: 2;
  height: 1.75rem;
  touch-action: none;
}
.reserve-sheet__grab::before {
  content: "";
  position: absolute;
  top: 0.625rem;
  left: 50%;
  width: 2.5rem;
  height: 0.3125rem;
  margin-left: -1.25rem;
  border-radius: var(--radius-pill);
  background: rgba(255, 255, 255, 0.9);
  box-shadow: 0 1px 4px rgba(9, 11, 14, 0.3);
}

/* THE PHOTOGRAPH. A band on a phone, 17% of the screen tall within
   6-10rem, so the words and the form still fit an SE without the
   sheet having to scroll. touch-action: none because it is the
   pull-to-dismiss handle as well. */
.reserve-sheet__photo {
  position: relative;
  margin: 0;
  height: clamp(6rem, 17svh, 10rem);
  overflow: hidden;
  border-radius: var(--sheet-radius) var(--sheet-radius) 0 0;
  background: var(--brand-900);
  touch-action: none;
}
.reserve-sheet__photo img {
  position: absolute;
  inset: 0;
  width: 100%;
  height: 100%;
  object-fit: cover;
  object-position: 50% 55%;
}
/* The phone keyboard is up: fold the photograph away so the field
   and the button stay on screen, and the grab bar goes grey on the
   white it now sits over. */
.reserve-sheet.is-typing .reserve-sheet__photo { display: none; }
.reserve-sheet.is-typing .reserve-sheet__grab::before {
  background: var(--gray-300);
  box-shadow: none;
}

.reserve-sheet__body {
  padding: var(--space-5) var(--space-4) var(--space-4);
}

/* THE CLOSE BUTTON, a 44px frosted disc in the top right corner:
   over the photograph on a phone, over the white on a desktop. */
.reserve-sheet__close {
  position: absolute;
  top: var(--space-3);
  right: var(--space-3);
  z-index: 3;
  display: grid;
  place-items: center;
  width: 2.75rem;
  height: 2.75rem;
  padding: 0;
  border: 1px solid color-mix(in oklab, var(--gray-900) 10%, transparent);
  border-radius: 50%;
  background: rgba(255, 255, 255, 0.88);
  -webkit-backdrop-filter: blur(8px);
  backdrop-filter: blur(8px);
  color: var(--gray-900);
  cursor: pointer;
  transition: background-color var(--dur-ui) ease, transform var(--dur-press) var(--ease-out);
}
.reserve-sheet__close svg { width: 1.25rem; height: 1.25rem; }
.reserve-sheet__close:active { transform: scale(0.94); }
.reserve-sheet__close:focus-visible {
  outline: 2px solid var(--color-border-focus);
  outline-offset: 2px;
}
@media (hover: hover) and (pointer: fine) {
  .reserve-sheet__close:hover { background: var(--gray-100); }
}

.reserve-sheet__eyebrow {
  margin: 0 0 var(--space-2);
  color: var(--color-text-secondary);
}
.reserve-sheet__title {
  margin: 0 0 var(--space-2);
  color: var(--color-text-primary);
  text-wrap: balance;
  outline: none;
}
.reserve-sheet__title em {
  font-style: normal;                     /* upright, colour only, as every heading here */
  color: var(--color-text-accent);
}
.reserve-sheet__text {
  margin: 0;
  max-width: 34ch;
  color: var(--color-text-secondary);
}

/* THE FORM: the closing panel's field (white well, grey hairline),
   stacked on a phone with the button the full width. */
.offer-form--sheet { margin-top: var(--space-4); }
.offer-form--sheet .offer-form__control {
  background: var(--color-bg-primary);
  border-color: var(--color-border-default);
}
.offer-form--sheet .offer-form__error {
  margin: var(--space-2) 0 0;
  color: var(--color-text-error);
}

/* THE WAY OUT. As easy to see as the form, not greyed into the
   fine print: primary ink, an underline and the same arrow as the
   Reserve button, 44px tall. */
.reserve-sheet__skip {
  display: flex;
  align-items: center;
  justify-content: center;
  gap: var(--space-2);
  min-height: 2.75rem;
  margin-top: var(--space-3);
  color: var(--color-text-primary);
  text-decoration: underline;
  text-decoration-color: color-mix(in oklab, currentColor 35%, transparent);
  text-underline-offset: 0.3em;
  transition: text-decoration-color var(--dur-ui) ease;
}
.reserve-sheet__skip svg { width: 1.125rem; height: 1.125rem; flex: 0 0 auto; }
.reserve-sheet__skip:focus-visible {
  outline: 2px solid var(--color-border-focus);
  outline-offset: 2px;
  border-radius: var(--radius-sm);
}
@media (hover: hover) and (pointer: fine) {
  .reserve-sheet__skip:hover { text-decoration-color: currentColor; }
}

/* STEP 2: the code card from /welcome (styles.css, "the code
   plate"), its status line re-coloured for white paper (it is set
   for footage there), and the booking button under it. */
.reserve-sheet__code { margin-top: var(--space-4); max-width: none; }
.reserve-sheet .code__status {
  margin-top: var(--space-1);
  color: var(--color-text-secondary);
  text-shadow: none;
}
.reserve-sheet__go {
  display: flex;
  align-items: center;
  justify-content: center;
  gap: var(--space-2);
  width: 100%;
  min-height: var(--field-h);
  margin-top: var(--space-2);
}
.reserve-sheet__go svg { width: 20px; height: 20px; }

/* FROM 768px: THE FLOATING CARD. */
@media (min-width: 768px) {
  .reserve-sheet__panel {
    left: 0;
    right: 0;
    bottom: calc(var(--space-4) + var(--sheet-lift));
    width: min(56rem, 100% - 2 * var(--space-5));
    max-height: calc(100% - 2 * var(--space-4));
    margin-inline: auto;
    display: grid;
    grid-template-columns: minmax(0, 2fr) minmax(0, 3fr);
    border-radius: var(--sheet-radius);
    padding-bottom: 0;
    box-shadow:
      0 1.5rem 4rem -1.5rem color-mix(in oklab, var(--brand-950) 55%, transparent),
      0 2px 8px color-mix(in oklab, var(--brand-950) 10%, transparent);
    transform: translate3d(0, calc(100% + 3rem), 0);
  }
  .reserve-sheet__grab { display: none; }
  .reserve-sheet__photo {
    height: auto;
    min-height: 20rem;
    margin: var(--space-2);
    border-radius: calc(var(--sheet-radius) - var(--space-2));
    touch-action: auto;
  }
  .reserve-sheet__body {
    align-self: center;
    padding: var(--space-7) var(--space-7) var(--space-6) var(--space-5);
  }
  .reserve-sheet__close { top: var(--space-4); right: var(--space-4); }
  .reserve-sheet__title {
    font-size: var(--fs-display-sm);
    line-height: var(--lh-display-sm);
  }
  .offer-form--sheet { margin-top: var(--space-5); }
  .offer-form--sheet .offer-form__control { flex-direction: row; align-items: center; }
  .offer-form--sheet .offer-form__field   { flex: 1; min-width: 0; }
  .offer-form--sheet .offer-form__control .btn { flex: 0 0 auto; }
  .reserve-sheet__skip { justify-content: flex-start; }
  .reserve-sheet__code { margin-top: var(--space-5); }
}
/* The plate's long shadow is set for footage on /welcome; on white
   paper it read as a grey smear under the card. A shorter, lighter
   one here; the inset edge (the card's thickness) stays. */
.reserve-sheet .code__plate {
  box-shadow:
    inset 0 -1px 0 color-mix(in oklab, var(--accent-500) 20%, transparent),
    0 0.5rem 1.5rem -0.75rem color-mix(in oklab, var(--brand-950) 35%, transparent);
}
