/* Modular Maison — homepage.
   Register: architectural monograph. Dark throughout, full-bleed imagery,
   pinned chapters, mono technical annotation. Aimed at the horyx.studio
   reference — not the AI brand board. */

/* Palette rebuilt 2026-09-06 to the client's own brand values
   (spec/products.json -> brand.palette), lifted from the dark horyx.studio
   register to the warm paper + technical-drawing register the client showed
   as the target look. Worth recording why this ISN'T a reversal of the
   earlier "the AI brand board is the outlier" call: that board paired this
   exact palette with garbled type and eco-boutique botanical clutter and was
   rightly rejected. The values were never the problem. This reference pairs
   the same clay/charcoal/off-white with an architectural-document sensibility
   instead - real section-cut conventions, a title block, coded annotations -
   which is the register the whole site already speaks in. Same palette,
   correct execution. */
:root{
  --bar:51.2px;
  --ink:#2b2b2a;
  /* The site went through --ink-2/--ink-3 as two lighter reading tiers for
     body copy, labels and captions, tuned step by step for contrast. Each
     step individually passed AA, and each one still got reported back as
     "grey text" - lede paragraphs, card copy, footer links, one at a time,
     across several rounds of fixes. The tiers were the actual problem, not
     any one component: text you're meant to read is full --ink now, full
     stop. --ink-4 stays a genuinely separate thing - decorative oversized
     numerals and inactive UI states, never body copy. */
  --ink-2:var(--ink);
  --ink-3:var(--ink);
  --ink-4:rgba(43,43,42,.62);   /* 3.79:1 - inactive UI and the oversized page numerals */
  /* DO NOT give any text rule its own rgba(...,<1) or hex opacity to make it
     "secondary" - that is exactly how --ink-2/--ink-3 ended up grey in the
     first place, and it will happen again one component at a time if it's
     hand-rolled instead of reached for as a variable. Body copy, labels,
     links: var(--ink) (or the local --ink in a dark scope - see .hero,
     .fx-stage, .foot). --ink-4 is the ONLY sanctioned muted tier, and only
     for decorative numerals or a genuinely inactive/pending state, never
     anything meant to be read. */
  /* Clay is the brand accent and stays exactly as Andrew's board has it for
     fills, rules and dots. As TEXT on paper it measures 3.07:1, so small type
     uses this darkened variant instead (5.57:1 on --bg, 5.05:1 on --bg-2,
     ~4.6:1 on --sand - the figure below is that worst case).
     There is no olive/sage any more (was --olive #7a8b6f, --olive-t #5a6652):
     client call 2026-09-29 - sage is AJP Constructions' colour and was all
     over this site; clay is Modular Maison's. Every rule, tint and label that
     used it is clay now. Don't bring a green accent back. */
  --clay-t:#935134;             /* 4.64:1 */
  /* Foreground for anything filled with --ink. --ink flips cream in the dark
     chapters, so this has to flip with it - see the overrides below. */
  --on-ink:#f7f5f2;
  --bg:#f7f5f2;
  --bg-2:#efeae1;
  --line:rgba(43,43,42,.14);
  --clay:#c47a5a;
  --walnut:#6b4f3a;
  --sand:#e8e1d9;
  /* Montserrat is Andrew's named heading font (brand board, 2026-09).
     Geist Mono stays for labels/figures/section numbers - the board has no
     mono equivalent, and that technical-drawing register is our own device
     layered on top, not a substitution for what he asked for. Italianno
     carries the wordmark's script half; the board's own script ("Gistesy")
     isn't a hosted Google Font, so this is the closest free stand-in, not
     an exact match - flagged, not silently swapped. */
  /* Andrew's brand board specified two faces: Montserrat, and a script called
     Gistesy. Gistesy is real (Creatype Studio) but it is personal-use only -
     a commercial licence has to be bought before it can ship on a business
     site, so Dancing Script stands in: the nearest free-for-commercial match
     to Gistesy's casual connected handwriting. Everything else, including the
     technical labels that used to be Geist Mono, is Montserrat, so the page
     carries the two faces Andrew asked for and nothing else. The labels keep
     their wide tracking, which is what made them read as drafting callouts -
     that came from the letterspacing, not from the monospace. */
  --mono:"Montserrat","Inter",system-ui,-apple-system,sans-serif;
  --display:"Montserrat","Inter",system-ui,-apple-system,sans-serif;
  --sans:"Montserrat","Inter",system-ui,-apple-system,sans-serif;
  --script:"Dancing Script","Brush Script MT",cursive;
  --pad:clamp(16px,3.68vw,60.8px);
  /* The site's content-column lines. --content is the shared reading column
     every ordinary section (.sect .wrap, .page, .weeks) sits on: 1500px.
     --stage is the wider cap the staged chapters (.fx, .rooms) still run at.
     The two disagreed visually on monitors past ~1560px (the Process chapter
     drifted off the FAQ's line before 2026-09-29, then off About's after
     2026-10-05). Since 2026-10-07 (Radin: "fix this section's alignment")
     they are the same number, so every homepage section - finishes, rooms,
     Process, About, FAQ, Gallery, Contact - starts and ends on one pair of
     lines at every width. Keep them equal. .plan-page's 1900px override is
     its own deliberate thing (wide drawing pages) and stays literal. */
  --content:1500px;
  --stage:var(--content);
}

/* Paper grid - the faint drafting-sheet backdrop behind every light section.
   Two hairline gradients, not an image: cheap, crisp at any zoom, and it
   tints with --line so it never fights dark text. */
.paper-grid{
  background-color:var(--bg);
  background-image:
    linear-gradient(var(--line) 1px,transparent 1px),
    linear-gradient(90deg,var(--line) 1px,transparent 1px);
  background-size:56px 56px;
  background-position:-1px -1px;
}

/* Section-cut marker - a real drafting convention, not decoration: this is
   literally how Ana's own sheet C (Sections) marks where a cut is taken on
   the plan. Used at chapter transitions, each pin labelled with the sheet
   code it corresponds to, e.g. A-A against A.01. */
.cut-mark{display:flex;flex-direction:column;align-items:center;gap:0;color:var(--clay)}
.cut-mark .pin{
  width:24px;height:24px;border-radius:50%;border:1.5px solid currentColor;
  display:flex;align-items:center;justify-content:center;
  font-family:var(--mono);font-size:11px;letter-spacing:0;background:var(--bg);
}
.cut-mark .stem{width:0;flex:1 1 auto;min-height:40px;border-left:1.5px dashed currentColor}
.cut-mark .arrow{width:5.6px;height:5.6px;border-right:1.5px solid currentColor;border-bottom:1.5px solid currentColor;transform:rotate(45deg);margin-top:-3.2px}
.cut-mark.up .arrow{transform:rotate(225deg);margin-top:0;margin-bottom:-3.2px}

*{box-sizing:border-box}
html{scroll-behavior:smooth;background:var(--bg)}
/* Someone who has asked the OS to stop animation means it for a 9000px jump
   down the page more than for anything else on the site. */
@media (prefers-reduced-motion:reduce){html{scroll-behavior:auto}}
/* Belt and braces with js/nav.js: this catches an anchor followed before the
   script is parsed, and a browser that restores a #hash position on reload. */
[id]{scroll-margin-top:calc(var(--bar) + 12px)}
html.menu-open,html.menu-open body{overflow:hidden}
body{
  margin:0;background:var(--bg);color:var(--ink);
  /* 400, not 300. Montserrat is a geometric sans and its Light is genuinely
     thin at body sizes - an audit across seven pages found every paragraph,
     link, dd and span on the site rendering in it, which reads as grey type
     however black the ink actually is. The big display runs keep their
     explicit 300; that contrast against the 600 half of each headline is
     deliberate and still reads at 40-80px. */
  font-family:var(--sans);font-weight:400;font-size:12.8px;line-height:1.65;
  -webkit-font-smoothing:antialiased;overflow-x:hidden;
}
/* height:auto matters as much as max-width here. Every <img> on the site carries
   width/height attributes so the browser reserves the right box before the file
   arrives; without height:auto, any rule that sets width alone leaves the
   attribute height as the used height and the image stretches. The plates that
   genuinely want a fixed height (.fx-plate, .rm-plate) set it themselves and
   out-specify this. */
img{display:block;max-width:100%;height:auto}
a{color:inherit;text-decoration:none}
/* Montserrat sets lighter than the mono it replaced at label sizes - same
   nominal size reads noticeably fainter - so the weight comes up to hold the
   drafting-callout presence these labels are carrying. */
/* 11px is the floor for every label on the site (2026-10-02, client OK):
   tracked caps any smaller rendered grey however black the ink. Was 8px. */
.mono{font-family:var(--mono);font-size:11px;font-weight:500;letter-spacing:.18em;text-transform:uppercase}
/* Units stay as written inside capitalised labels: m², not M² (mega-). */
.unit{text-transform:none}

/* Film grain over the whole viewport, photographs included. At .05 it was
   reading as noise on the renders rather than as texture on the paper - part
   of why the imagery looked soft and unclean. Halved, so it still breaks up
   the flat cream without sanding detail off a photograph. */
.grain{
  position:fixed;inset:0;z-index:60;pointer-events:none;opacity:.025;mix-blend-mode:overlay;
  background-image:url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='160' height='160'%3E%3Cfilter id='n'%3E%3CfeTurbulence type='fractalNoise' baseFrequency='.9' numOctaves='4'/%3E%3C/filter%3E%3Crect width='160' height='160' filter='url(%23n)'/%3E%3C/svg%3E");
}

/* ------------------------------------------------------------ chrome */
/* Paper repaint changed what sits under the fixed nav: it used to be either
   sky or a dark chapter, so light text plus a drop shadow read everywhere.
   Now most of the page is cream paper and only the opening walkthrough is
   dark - a fixed bar can't know which one is behind it at any given scroll
   position. Giving it its own paper backing plate (small, blurred, always the
   same colour) fixes that at the source: it reads identically over the night
   hero and over the light chapters, because it never actually sits on either. */
.nav{
  position:fixed;top:0;left:0;right:0;z-index:50;isolation:isolate;
  display:flex;align-items:center;justify-content:space-between;gap:19.2px;
  padding:12.8px var(--pad);
  /* Pure black nav type, not the warm --ink (Radin, 2026-10-28: "nav bar
     looks brown make it black"). Covers the solid plate and interior pages;
     the hero-state rules below repeat it. The wordmark keeps its clay
     lockup (client, 2026-11-03). */
  color:#000;
}
/* The plate comes back, but only past the opening.

   Earlier attempts made it always-on and it read as a pale haze over the
   photograph. The fix is not a better haze, it is not painting one while the
   nav is over the hero: the links carry their own pill up there, which is
   legible against anything on its own, and the full-width plate only fades in
   once you have scrolled past the section the nav opened over. See js/nav.js
   for where that line is drawn. */
/* Solid, not translucent (client 2026-10-04: the scrolled bar read as
   see-through). Same paper colour as the page background, no blur. */
.nav-plate{
  position:absolute;inset:0;z-index:-1;opacity:0;
  background:var(--bg);
  border-bottom:1px solid var(--line);
  transition:opacity .32s ease;
}
.nav.nav-solid .nav-plate{opacity:1}
/* Radin, 2026-11-04: keep the bar TRANSPARENT over the hero as before -
   the plate still only arrives with the solid bar on scroll. */
/* Radin, 2026-11-04: on the home hero the wordmark reads 25% larger while
   the page is at the top; once the solid bar is up on scroll (.nav-solid)
   it returns to its standard size. Transform only - the bar's height never
   changes, and it is scoped wide so the links never crowd on mid widths. */
@media (min-width:1200px){
  body:has(.hero) .nav .wm-logo{transform-origin:left center;transition:transform .3s ease}
  body:has(.hero) .nav:not(.nav-solid) .wm-logo{transform:scale(1.25)}
}
@media (prefers-reduced-motion:reduce){
  .nav-plate{transition:none}
}
.wordmark{position:relative;display:flex;flex-direction:column;gap:1.6px;line-height:1}
/* No dark glow behind the logo, and no halo around its letters (client,
   2026-10-01: "remove the black thing around and in the logo"). Both dated
   from the black/white lockup, which had to fight the photo for contrast.
   The radial glow's fade was cut off at the edge of its own box, so over the
   bright sky it read as a dark rectangle; the halo muddied the script's thin
   strokes. The clay lockup holds over the hero on its own. */
/* Andrew's supplied lockup, keyed to transparent from its flat cream board.
   Used to swap between a black and a white ink depending on nav-solid, back
   when it had to hold contrast against both the photo hero and the paper
   nav bar itself - clay reads clearly against both, so that's one lockup
   now instead of two. */
.wm-logo{height:68px;width:auto;display:block;align-self:flex-start}
/* Up ~22% on 2026-10-11 (client, on a call: "it's kind of hard to see the
   logo at the top left... make it like 20, 25 percent bigger"). 60 -> 73px
   on desktop, 56 -> 68 below that. That is close to the 72px it was before
   2026-10-09, when it came down to 60 for a different reason - it looked
   oversized *beside the nav links* on a paper bar. The complaint now is
   legibility over a photographic hero, which is the other end of the same
   trade; the clay lockup on a bright sky is what is actually faint.
   The bar deepens with it, as the client expected ("that toolbar thing at
   the top might be a bit deeper, so then the words will have to be
   re-centered on it"): 97.6 -> 111px. The re-centring is free, since .nav
   is align-items:center - the links find the new middle themselves, at the
   same size, which the client asked to leave alone ("the text size across
   the top is all good").
   111 is not arbitrary: it puts the logo's top at exactly (111-73)/2 = 19px,
   the same 19px it sat at before and the same as the configurator's own
   header. site_check compares the logo's box across every page, so that
   number has to survive - see the matching rule in css/app.css. */
@media (min-width:901px){
  .wm-logo{height:73px}
  .nav{min-height:111px}
}
/* The script carries the flourish, and only the flourish - "Modular" stays a
   plain tracked sans so the lockup is legible at nav size, where a full
   script reads as texture rather than a name. */
.wm-name{display:flex;align-items:baseline;gap:5.6px}
.wm-name b{font-family:var(--display);font-weight:700;font-size:14.8px;letter-spacing:.04em;text-transform:uppercase}
/* Dancing Script sets much larger on the body than Italianno did at the same
   px - bigger x-height, shorter ascenders - so the size drops to keep the
   lockup balanced against MODULAR beside it. */
.wm-name em{font-family:var(--script);font-style:normal;font-size:20.8px;font-weight:700;color:var(--clay);line-height:.72;position:relative;top:1px}
.wm-parent{font-family:var(--mono);font-size:11px;font-weight:700;letter-spacing:.2em;text-transform:uppercase}
/* ------------------------------------------------------------ nav pills

   Two states, and only one of them has pills in it.

   OVER THE HERO the wordmark, the links and the CTA each sit on a glass
   pill: a translucent scrim with a blur and a hairline edge. The scrim is
   what makes a transparent nav survive a photograph - the walkthrough behind
   it runs from a dusk sky to a sunlit timber interior, and no flat ink or
   flat white reads across that range on its own.

   PAST THE HERO the plate is there, so the pills come off entirely: no
   backgrounds, no borders, no blur. A pill drawn on a surface is a bubble
   sitting on a bar; the reference has one or the other, never both. */
/* Geometry measured off the reference: a 40px pill with 5px of padding
   around a 30px chip, 14px type, and the links butted together rather than
   gapped - the chip's own padding is the spacing. */
.nav-links{
  display:flex;gap:1.6px;padding:3.2px;border-radius:100px;
  border:1px solid transparent;
  transition:background .3s,border-color .3s,box-shadow .3s;
}
/* Montserrat 600 is a much heavier face than the reference's grotesque at the
   same nominal weight - side by side, ours read as bold where theirs read as
   medium. The unselected links drop to 500 and dim further; the selected one
   keeps 600 and full strength, so weight marks position rather than shouting
   the whole row. */
/* 14px (was 13px, client ask 2026-09-30: "a little bigger") - the same step
   on .nav-cta below, so the bar stays one size. */
.nav-links a{
  position:relative;
  padding:6.4px 15.36px;border-radius:100px;font-size:0.875rem;font-weight:600;
  line-height:1.2;
  transition:background .22s,color .22s;
}
/* The page you are on: full weight, no dimmer default to lift it out of -
   see the --ink-4 note above, the same rule applies to nav type. The
   underline stays hover/focus-only - tying it to scroll-spy too made it
   redraw on every section change while scrolling, which reads as the nav
   glitching rather than responding to you. */
.nav-links a.here{font-weight:600}
/* Underline reveal, measured off gardehvalsoe.dk/en: a hairline that grows
   in from the left edge on hover, rather than a background chip announcing
   itself. Inset matches the link's own horizontal padding so it hugs the
   text rather than the wider pill hit-area. */
.nav-links a::before{
  content:'';position:absolute;left:15.36px;right:15.36px;bottom:4px;height:1px;
  background:currentColor;transform:scaleX(0);transform-origin:0% 50%;
  transition:transform .3s ease;
}
.nav-links a:hover::before{transform:scaleX(1)}

/* Andrew's update, 3 Nov 2026: the hero render now shows at its supplied
   brightness, so the nav's own dark gradient scrim went with the hero veil
   ("remove the dark foreground overlay / gradient"). Over a bright sky and
   pale cladding the bar inverts to ink type instead: links, CTA and the
   logo read dark-on-light, with a paper halo (a shadow) rather than a tint
   behind them. The clay lockup darkens slightly over the photo only - at
   full clay it washed out against sunlit foliage; on the solid plate it
   keeps its brand colour. */
body:not(.interior) .nav:not(.nav-solid){background:none}
.nav:not(.nav-solid) .wordmark{text-shadow:none}
.nav:not(.nav-solid) .nav-links a{text-shadow:none}
/* The wordmark keeps its own clay (the old brightness(.42) darkened it to
   brown until the solid nav came up - Radin, 2026-11-03: "doesn't even look
   like the orangey colour"). */
body:not(.interior) .nav:not(.nav-solid) .wm-logo{filter:none}

/* Over the hero the ground is bright and varied now, so the type stays ink
   with a paper halo. On an interior page the nav opens over paper, so
   js/nav.js puts the plate on immediately and this never applies. */
body:not(.interior) .nav:not(.nav-solid){color:#000}
/* The CTA follows the bar's ink. */
body:not(.interior) .nav:not(.nav-solid) .nav-cta{
  color:#000;
  text-shadow:none;
}
/* CONTROL TYPE - shared by every interactive control on the site: nav links,
   buttons, the finish pills, the view switcher, the room tabs. Montserrat 600
   in natural case with tracking pulled slightly tight.

   The site's other label style is the opposite - uppercase on wide tracking -
   and that stays, but only on things that are genuinely annotation: drawing
   codes, spec labels, the title block. Words you click are words; codes are
   codes. Keeping the two apart is what stops the page reading as one
   undifferentiated wall of small caps.

   The nav sits on an unknown ground - paper on most of the page, a photograph
   at the top and bottom of the homepage - with no tint behind it to help, so
   it takes the largest size in the set. */
/* Weight and opacity live in the pill block above - this rule sits later in
   the file and was quietly overriding them. Letter-spacing matches
   gardehvalsoe.dk/en's measured 1.6px nav tracking. */
.nav-links a{font-family:var(--sans);letter-spacing:1.6px}
.nav-links a:hover{opacity:1}
/* ------------------------------------------------ single-page sections

   Every section of the site lives on this page now, so the vertical rhythm
   between them is the only thing saying "new section". The house chapters
   (.stage, .fx, .rooms) bring their own full-height staging; .sect is for the
   ones that are ordinary page content - Homes, Questions, About, Contact. */
/* Section titles were <h1> when each of these was its own page. They are
   <h2> now - one document, one h1 - but they still open a section, so they
   keep the size the page head gives them. Every section heading on the page
   carries this class, the house chapters and the closing CTA included - they
   each had their own size and weight until the small labels above them went,
   and then the mismatch was all you could see. Scaled down with the h1 rule
   on 2026-09-29 - at 54.4px they out-shouted the copy they introduce. */
/* Light 300 since 2026-10-02 (client, pointing at a home page's light
   title: "I like that font, make sure all text has it") - every display
   heading now shares h1's weight and tracking. Small headings, labels and
   buttons stay heavier on purpose: Light at 8-20px reads as grey type. */
.sect-title{
  font-family:var(--display);font-weight:300;letter-spacing:-.01em;
  font-size:clamp(24px,2.8vw,38.4px);line-height:1.05;margin:0 0 14.4px;
}
.sect-title:last-child{margin-bottom:0}

.sect{padding:clamp(51.2px,8vh,96px) 0}
.sect .wrap{max-width:var(--content);margin:0 auto;padding:0 var(--pad)}
/* .page-head draws a rule and a bottom margin sized for the top of a page;
   inside a stacked section it only needs to separate itself from its own
   content. */
.sect .page-head{margin-bottom:clamp(22.4px,3.6vh,41.6px)}
/* The About teaser's page-head now sits inside .about-split-copy beside a
   photo, not stacked above a full-width block - the rule it draws to
   separate itself from what used to come directly underneath has nothing
   left to separate from, and read as a stray line floating above the photo's
   own edge instead. */
#about .page-head{border-bottom:0;padding-bottom:0}
/* Spacing review 2026-09-29, fourth pass tried a fixed 56px here to land the
   copy column's height on the photo's (the .about-split media/copy pair is
   centred with align-items:center though, so any height gap just balances
   as even space top and bottom, not a hollow band - the 56px was solving a
   problem align-items already covers). Against the 24px above it and the
   18px between paragraphs below, it read as one oversized gap rather than a
   rhythm (review 2026-09-30: "fix gap here"). Left unset, so it falls back
   to .sect .page-head's own clamp() below - the same "head to body" gap
   every other section already uses. */
#about .sect-title{margin-bottom:24px;text-wrap:balance}
/* Lede to body: the same 24px as title to lede. The shared .sect .page-head
   gap (up to 41.6px) read as a break between two paragraphs set in the same
   size and colour (2026-10-07). */
#about .page-head{margin-bottom:24px}
#about .lede{max-width:none}
#about .about-block p{margin-bottom:18px}
#about .about-block:last-of-type{margin-bottom:56px}
.sect + .sect{padding-top:0}
/* .page-head draws a rule and .section draws its own; stacked they land ~25px
   apart with nothing between them. The head's is the one that belongs here. */
.sect .page-head + .section,
.sect .page-head + .faq,
.sect .page-head + .index{border-top:0}

/* About page copy - Andrew's own sections, each a short claim-then-reasoning
   block rather than one long paragraph. One column system for the whole page
   (2026-10-05: intro capped at 820px, splits at 1200px and the page at
   1500px produced three different left edges - client read it as
   "alignment all over the place"). Everything now sits on the page's own
   content column; only the text measure keeps a cap, so the copy stretches
   while staying readable. */
.about-body{max-width:none}
.about-block{margin-bottom:clamp(28.8px,4.4vh,44.8px)}
.about-block:last-of-type{margin-bottom:24px}
.about-block h3{
  font-family:var(--display);font-weight:600;letter-spacing:-.01em;
  font-size:clamp(17.6px,1.68vw,20.8px);color:var(--ink);margin:0 0 12.8px;
}
.about-block p{color:var(--ink);line-height:1.8;font-size:15.2px;max-width:76ch;margin:0 0 12.8px}
.about-block p:last-child{margin-bottom:0}
.about-block .pullq{margin-top:16px}
/* Generic text link + arrow, grows on hover - used by the About "Explore
   our homes" link and the homepage Process teaser's "read the full
   process" link alike. */
.link-arrow{
  display:inline-flex;align-items:center;gap:6.4px;font-weight:600;color:var(--ink);
  font-size:13.6px;transition:gap .2s ease;
}
.link-arrow:hover{gap:10px}
.link-arrow .arr{transition:transform .2s ease}
.link-arrow:hover .arr{transform:translateX(2px)}

/* ------------------------------------------------------- gallery slider

   Was a continuously-crawling marquee (briefed against gardehvalsoe.dk's
   projects strip, 2026-09-29); replaced 2026-09-30 with one frame at a
   time - client brief: "one big image/project... arrow buttons at the
   bottom which then can slide to the next project", clickable through to
   that home's page. Same crossfade-by-class approach as the Homes carousel
   above it (.hd-slide/js/home-display.js), just one shared caption+counter
   below the frame instead of a panel per slide (js/gallery-slider.js) -
   see the section comment in index.html, and tools/gallery_placeholders.py
   for how the placeholder frames themselves are generated. */

/* Heading-only head with the marquee coming straight after it - the rule
   .page-head draws (and the padding that sits above it) exists to separate
   a heading from a text block, and the lede this one used to carry went on
   review (2026-09-29), leaving nothing to separate. It read as a stray line
   floating between "Gallery" and the frames, so it goes - same removal as
   #about's head above. */
#gallery .page-head{border-bottom:0;padding-bottom:0}
/* Same again for the FAQ head - nothing sits under "Frequently asked
   questions" but the faq rows, which draw their own hairlines, so the
   rule .page-head draws reads as a stray line under the heading.
   Removed on review 2026-09-29. */
#questions .page-head{border-bottom:0;padding-bottom:0}

/* ------------------------------------------------------------ awards
   AJP's awards, as listed on ajpconstructions.com.au/awards/ (Andrew,
   2026-10-11 call: "a little bit more credibility... towards the bottom"),
   at the foot of about.html (.ab-awards) - Radin moved it there from the
   homepage the same night. Hairline rows and full-ink type, the FAQ's
   system. Three columns: the project (a link to AJP's page for it), the
   category, then body, year and result as a small mono label on the right -
   one line per award, so the eye can run down the results. Stacks on
   phones. */
.awards{list-style:none;margin:0;padding:0;border-top:1px solid var(--line)}
.ab-awards .awards{margin-top:8px}
.aw-row{
  display:grid;grid-template-columns:minmax(0,1fr) minmax(0,2.4fr);gap:6px 32px;
  padding:16px 0;border-bottom:1px solid var(--line);
}
.aw-proj{
  align-self:start;justify-self:start;
  font-family:var(--display);font-weight:500;font-size:clamp(14.4px,1.36vw,16px);
  line-height:1.7;letter-spacing:-.012em;color:var(--ink);text-decoration:none;
  background:linear-gradient(currentColor,currentColor) 0 100%/0 1px no-repeat;
  transition:background-size .3s ease;
}
.aw-proj:hover{background-size:100% 1px}
.aw-proj:focus-visible{outline:1px solid var(--clay);outline-offset:3px}
.aw-list{list-style:none;margin:0;padding:0}
.aw-list li{
  display:grid;grid-template-columns:minmax(0,1fr) auto;gap:24px;align-items:baseline;
  font-size:15.2px;font-weight:500;line-height:1.7;letter-spacing:-.006em;color:var(--ink);
}
.aw-by{color:var(--ink);text-align:right;white-space:nowrap}
.aw-more{margin-top:22.4px}
@media (max-width:700px){
  .aw-row{grid-template-columns:1fr;gap:6px}
  .aw-list li{grid-template-columns:1fr;gap:0;font-size:14.4px;padding:2px 0}
  .aw-by{text-align:left;white-space:normal;margin-bottom:4px}
}
.gal-slider{margin-top:clamp(22.4px,3.6vh,41.6px)}
/* First pass capped this at 860px, 3/2 - review 2026-09-30: "still small, I
   want it almost this size" pointing at .fx-stage (Home finishes). Matched
   directly: same 3400/1440 ratio, and full width of .wrap instead of a
   fixed cap, same "fill the column" sizing .fx-stage itself uses (.fx's own
   max-width:var(--stage) does the capping there, one level up). object-fit:
   cover below crops the placeholder frames' portrait 800x1000 harder at
   this wider ratio than the old 3/2 did, but it's a labelled "photo to
   come" box, not a composed shot with framing to protect. */
.gal-stage{
  position:relative;width:100%;aspect-ratio:3400/1440;
  border-radius:22px;overflow:hidden;background:var(--bg-2);
}
/* Same crossfade recipe as .hd-slide (css/pages.css): absolutely stacked,
   opacity+visibility+pointer-events so an inactive frame's link can't be
   tabbed to or clicked while hidden underneath the active one. */
.gal-slide{
  position:absolute;inset:0;display:block;opacity:0;visibility:hidden;pointer-events:none;
  transition:opacity .5s ease-in-out,visibility .5s;
}
.gal-slide.is-on{opacity:1;visibility:visible;pointer-events:auto}
/* Each picture is cut to the frame it shows in (tools/build_gallery.py), so
   cover only absorbs sub-pixel rounding - it never crops. */
.gal-slide picture{display:block;width:100%;height:100%}
.gal-slide img{display:block;width:100%;height:100%;object-fit:cover}
/* Temporary stand-in tags (2026-10-05): a frame that holds a stand-in video
   instead of the real thing carries a visible corner chip, so nothing
   transient reads as finished work. The gallery's own image chips went on
   Andrew's 3 Nov 2026 call ("Remove placeholder image at the top of each
   image"). */
.pf-temp{
  position:absolute;left:12px;top:12px;z-index:2;
  font-family:var(--mono);font-size:11px;font-weight:500;letter-spacing:.14em;text-transform:uppercase;
  color:var(--ink);background:var(--bg);border:1px solid var(--line);
  padding:3.2px 8.8px;border-radius:6px;
}
.gal-nav{
  display:flex;align-items:center;justify-content:space-between;gap:16px;
  width:100%;margin:20.8px auto 0;
}
/* A step up across the row (client, 2026-10-02: "slightly bigger, mainly the
   1/8") - the counter most: it carried .mono's 8px label size, which is
   built for drafting callouts, not a control you read at a glance. */
.gal-caption{font-family:var(--display);font-weight:600;font-size:17.6px;letter-spacing:-.01em;color:var(--ink)}
.gal-controls{display:flex;align-items:center;gap:18px}
.gal-counter{color:var(--ink);font-size:12px;font-weight:600;letter-spacing:.14em}
.gal-arrows{display:flex;gap:10px}
/* Bare chevron, no pill - the same "luxury" treatment as .hd-arrow in the
   Homes carousel above (review 2026-09-30 asked for it here too), just
   without that one's white ink + drop-shadow, which exist there only to
   hold contrast over a photo; this row sits on plain paper, so ink alone
   already reads clearly. */
.gal-arrow{
  width:44px;height:44px;display:flex;align-items:center;justify-content:center;
  background:transparent;color:var(--ink);border:none;
  cursor:pointer;transition:opacity .2s,transform .2s;
}
.gal-arrow svg{width:20px;height:20px}
.gal-arrow:hover{opacity:.6}
.gal-arrow:active{transform:translateY(1px)}
.gal-arrow:focus-visible{outline:2px solid var(--clay);outline-offset:2px}
/* 3400/1440 (~2.36:1) squashes to a thin strip on a narrow screen, so it
   swaps to a taller ratio at .fx-stage's breakpoint. 16:9, not the 4:5 it
   was: 4:5 cropped every wide render to a random 34%-wide slice (Radin,
   2026-10-11: "zoomed-in random images"). 16:9 shows the renders whole and
   matches the plan pages' gallery; each slide has its own 16:9 cut. */
@media (max-width:900px){
  .gal-stage{aspect-ratio:16/9}
}
@media (max-width:480px){
  .gal-caption{font-size:15.2px}
}

/* ------------------------------------------------------------ contact

   Fourth pass (Andrew's call, 2026-09-29): the site ends on "contact and
   actual information", not a picture. The third pass's placeholder image
   block (.contact-hero/.ch-img/.ch-overlay) is gone, and its rules with it.
   The section is the offer itself now - the complimentary assessment, in
   Andrew's own process copy - with the booking button opening the same
   <dialog> popup, and the direct lines beside it (Andrew's buyers "just
   like picking up phone and calling"). The form inside the popup is
   unchanged (same ids, same handler in the page script), and its field
   styling still lives in index.html's own <style> (the only form on the
   site). One column: the copy runs the full width of the page instead of a
   52ch block in the left half, then a closing row with phone and email
   bottom left and the booking button bottom right. Everything in it is
   pure black (#000), not the --ink charcoal, which read as grey here. */
.co-copy .sect-title{margin-bottom:24px}
/* The lede keeps its class for meaning, but takes the same rhythm as the
   paragraph after it. */
.co-copy p{max-width:none;font-size:15.2px;line-height:1.8;color:#000;margin:0 0 14.4px}
.co-foot{
  display:flex;align-items:center;justify-content:space-between;flex-wrap:wrap;
  gap:24px 48px;margin-top:clamp(24px,3.6vh,40px);
}
.co-direct{display:flex;flex-wrap:wrap;gap:22.4px clamp(32px,4vw,64px)}
/* Still the outline style (the configurator button below leads), but a
   full black edge and black type - the ghost's 30% border read as grey. */
.co-foot .btn.ghost{color:#000;border-color:#000}
.co-foot .btn.ghost:hover{background:#000;color:#fff}
/* Label over value: the same small tracked caps as the form's field labels
   (index.html's <style>), so the page and the popup speak one register. */
.co-line{display:grid;gap:6.4px;position:relative;padding-bottom:2.4px;color:#000}
.co-line .mono{font-size:11px;font-weight:600;letter-spacing:.14em;color:#000}
.co-val{font-size:14.4px;line-height:1.5;overflow-wrap:anywhere}
/* Same hairline hover as the footer's phone/email and the nav. */
.co-line::after{content:"";position:absolute;left:0;right:100%;bottom:0;height:1px;background:currentColor;transition:right .25s ease}
.co-line:hover::after{right:0}
@media (max-width:820px){
  /* Stacked on a phone: phone and email, then a full-width button. */
  .co-foot{flex-direction:column;align-items:stretch}
  .co-direct{flex-direction:column;gap:20px}
  .co-foot .btn{justify-content:center}
}

/* The popup. Padding sits on .cd-body rather than on the dialog so that
   clicks on the dialog element itself are exactly the backdrop ring around
   the panel - the backdrop-click handler compares e.target to the dialog.
   No position rule on the dialog: the UA positions modals (top layer,
   centred), and an absolute .cd-close anchors to it as-is. */
.contact-dialog{
  width:min(920px,94vw);max-height:88vh;overflow:auto;padding:0;
  background:var(--bg);color:var(--ink);border:0;border-radius:22px;
}
.contact-dialog::backdrop{background:rgba(17,18,17,.55)}
.cd-body{padding:clamp(28.8px,4vh,44.8px) clamp(24px,3.4vw,44.8px)}
.cd-close{
  position:absolute;top:16px;right:16px;width:38.4px;height:38.4px;
  display:flex;align-items:center;justify-content:center;
  background:transparent;border:1px solid var(--line);border-radius:50%;
  color:var(--ink);font-size:19.2px;line-height:1;cursor:pointer;transition:background .2s;
}
.cd-close:hover{background:var(--bg-2)}
/* A modal dialog does not stop the page scrolling behind it. */
body:has(dialog[open]){overflow:hidden}
.eyebrow{font-size:11px}
.c-head{margin-bottom:clamp(17.6px,2.6vh,26.4px)}
.c-head h3{
  font-family:var(--display);font-weight:300;letter-spacing:-.01em;
  font-size:clamp(20.8px,2.3vw,27.2px);line-height:1.12;margin:0;
}
/* Step headings take focus when a step opens (so a screen reader announces
   it) - that's programmatic, not something the visitor tabbed to. */
.c-head h3[tabindex="-1"]:focus{outline:none}
/* Every step's heading is visible now and sits level with the × in the
   corner, so it wraps short of it rather than running underneath. */
.contact-dialog .c-head{padding-right:48px}

/* ENQUIRY - the assessment request (Andrew's brief, 26 Oct 2026). The
   day/time calendar step and its .bk-* rules are gone: the popup is the
   form, then one result - "accepted" (needs a backend to say so) or
   "handoff" (the email app opened with the request). js/enquiry.js. The
   field rules themselves stay in index.html's <style>; these only add what
   the new fields and states need, in the same register. */
.cd-step{animation:cd-in .35s ease}
@keyframes cd-in{from{opacity:0;transform:translateY(6px)}to{opacity:1;transform:none}}
@media (prefers-reduced-motion:reduce){.cd-step{animation:none}}
/* Helper line under a field (Property address): the form-note's size and
   black, sitting just under the field's rule. */
.field-help{margin:6.4px 0 0;font-size:12px;line-height:1.7;color:#000}
/* Which home / How do you plan to use your Maison? / Timeframe side by
   side on a wide screen. The middle label can run to two lines, so the
   three selects line up along the bottom. Narrower, it's the usual .row. */
@media (min-width:901px){
  /* .row.row-3, not .row-3: index.html's <style> sets .row after this file. */
  .row.row-3{grid-template-columns:repeat(3,minmax(0,1fr));align-items:end}
}
/* Sending failed: the form stays exactly as it was, and this says so. A
   clay rule on the left, black type - no red, no grey. */
.form-error{margin:0;padding:2.4px 0 2.4px 12.8px;border-left:2px solid var(--clay);font-size:13.6px;line-height:1.7;color:#000}
.form-error a{white-space:nowrap;text-decoration:underline;text-decoration-thickness:1px;text-underline-offset:3px}
/* "Your configuration" (pages.css styles the panel): one line per room
   group, the control names in semibold so a long line still scans. 12px,
   the site's sentence floor, now the lines are sentences rather than one
   word each. */
.contact-dialog .spec-sum dd{font-size:12px}
.contact-dialog .spec-sum .ss-k{font-weight:600}
@media (max-width:640px){
  /* Stacked on a phone: SECOND BEDROOM beside its line left the line a
     word or two wide. */
  .contact-dialog .spec-sum{grid-template-columns:minmax(0,1fr);row-gap:2.4px}
  .contact-dialog .spec-sum dd{margin-bottom:6.4px}
  /* 16px, or iOS Safari zooms the whole page when a field takes focus. */
  .contact-dialog .field input,.contact-dialog .field textarea,.contact-dialog .field select{font-size:16px}
}
/* The result step. */
.cd-msg{margin:0 0 clamp(14.4px,2vh,19.2px);font-size:14.4px;line-height:1.75;max-width:60ch;color:#000}
.cd-msg-sm{font-size:13px}
.cd-msg-sm:empty{display:none}
.cd-msg a{white-space:nowrap;text-decoration:underline;text-decoration-thickness:1px;text-underline-offset:3px}
.cd-actions{display:flex;flex-wrap:wrap;gap:10px 16px;margin-top:clamp(8px,1.6vh,16px)}
/* Outline buttons in pure black, as .co-foot's - "fix that grey text"
   (client, 2026-10-01). */
.cd-actions .btn.ghost{color:#000;border-color:#000}
.cd-actions .btn.ghost:hover{background:#000;color:#fff}
@media (max-width:700px){
  /* Full-width buttons, one line each: Back and Copy share a row where
     they fit (stacked at 390px), Done always takes the full width. */
  .cd-actions .btn{flex:1 1 auto;justify-content:center;white-space:nowrap;padding-left:16px;padding-right:16px}
  .cd-actions .btn:last-child{flex-basis:100%}
}

/* about.html hero - full-bleed photo that FREEZES
   hero's ordinary scroll-away kind) while the page below it rises up and
   covers it, then hands off to normal scrolling. Reverse-engineered from
   vipp.com's actual component (m26-four-corner-split-description): its
   background sits on position:fixed while a foreground content tile is
   position:sticky with a bottom-anchored offset and its own z-index, so it
   visibly climbs up over the still image. Same visual result, simpler
   build - one sticky layer plus one classic pure-CSS trick, no JS:

   .about-hero is 200vh - 100vh of it is the pin, the other 100vh is how
   far .about-page (the very next element after it) gets to travel.
   .stage-pin is the actual sticky layer: it holds at the top of the
   viewport, fully frozen, for that whole 200vh - its own natural (unstuck)
   position never moves, so there's nothing for it to release INTO until
   the wrapper runs out of height. .about-page's negative margin-top:-100vh
   pulls its own top edge up to sit exactly at the bottom of the viewport
   at the moment .stage-pin starts sticking - so as the page scrolls, its
   opaque paper background is what visibly climbs the screen and buries the
   frozen photo, not a transform or a scroll-linked script. z-index just
   makes sure it paints on top of the pinned layer while the two overlap. */
/* .stage.about-hero, not .about-hero alone: .stage{height:100svh} (below,
   later in the cascade) is equal specificity to a bare .about-hero rule, so
   source order would let it win and silently cap this back to one viewport -
   no pin range at all. */
.stage.about-hero{height:200vh}
.about-hero .stage-pin{background:#111211}
.about-hero .stage-pin{
  --ink:#f2efe8;--on-ink:#111211;--ink-2:var(--ink);--ink-3:var(--ink);
  --ink-4:rgba(242,239,232,.4);--line:rgba(242,239,232,.14);
  color:var(--ink);
}
/* js/nav.js reads .hero's bounding box to decide when to swap the nav from
   glass-on-photo to solid-on-paper - it wants the BOTTOM of whatever holds
   this class to cross the bar as its signal. Neither real element here
   gives it that cleanly: the 200vh wrapper's box does not clear the
   viewport until the very end of that 200vh, long after .about-page has
   already risen and covered the photo (nav stays glass - unreadable light
   text - over paper the whole stretch in between); .stage-pin's OWN box,
   after it releases, is still 100vh tall and takes another 100vh of
   scrolling to clear the bar, same problem in a smaller way. What actually
   marks the moment paper takes over from photo is .about-page's top edge
   (the thing physically climbing the screen), not either box's bottom - so
   .hero goes on this zero-height marker, planted at that same document
   position (top:100vh inside the 200vh wrapper, exactly where .about-page's
   margin-top:-100vh pulls its own top edge to) instead of on the photo. */
/* .hero.about-hero-boundary, not .about-hero-boundary alone: same trap the
   .hero.hero-boundary marker hit (see its rule's comment) - the plain .hero
   height rules (0-1-0, later in this file) beat the lone single-class
   height:0 and stretched this marker to a full viewport (measured 950px at a
   950px window), which delayed the nav's solid-state flip by a whole screen.
   Two classes win regardless of source order. */
.hero.about-hero-boundary{position:absolute;top:100vh;left:0;width:1px;height:0}
/* The podium photo (Radin, 2026-10-11). Andrew stands mid-frame in a white
   shirt, right where the copy lands, and no scrim makes white type readable
   on a white shirt (tried: at 390px the lede ran straight across the shirt
   buttons). So there are two layouts:

   Desktop (1001px+) - full bleed, the copy on the photo, with a darker
   column behind the copy that fades out before his face. "Zoom out a
   little more, but still take the whole hero": the file is already the
   original's full width, which is what limits cover on a wide screen, so
   the only zoom left to give back was the drift script's scale(1.05) - off
   here. (Tried and reverted the same day: the photo at 90% height, right
   aligned, edges faded to black - "I don't want the image to be half the
   screen".)

   Phones and tablets - stacked: the photo fades into the pin's own #111211
   and the copy sits on the dark below it. The photo is a flex item taking
   whatever height the copy leaves, not a fixed share (a fixed 70% still put
   the headline on the shirt at 375x667). object-position 15% keeps his
   head clear of the nav from 375x667 up, allowing for the drift script's
   translateY. */
@media (min-width:1001px){
  .about-hero .grade{background:linear-gradient(90deg,rgba(6,7,6,.55) 0%,rgba(6,7,6,.45) 28%,rgba(6,7,6,.12) 44%,rgba(6,7,6,0) 52%)}
  .about-hero .stage-media img{transform:none!important}
  /* Placed like Process's hero copy (Radin, 2026-10-26: "move the about
     text there to the positioning of the process page"): on the page's
     own left margin and centred on the window's height - .pr-hero-copy's
     recipe in css/pages.css - not low and indented 137.6px like the
     homepage hero. Further left also keeps the headline off Andrew's
     shirt. Desktop only; phones keep the scrim at the foot (below). */
  .about-hero .stage-copy--hero{position:absolute;inset:0 var(--pad);display:flex;flex-direction:column;justify-content:center;padding:0;max-width:none}
  .about-hero .stage-copy--hero .lede{margin-bottom:0}
}
@media (max-width:1000px){
  /* Client, 2026-10-12: "half of it is black instead of it covering the
     whole thing". The photo sat in flow above the copy, so the pin's own
     near-black showed below it - with a fade-out mask making it worse.
     Now the photo covers the full pin exactly like desktop, and the copy
     rides a scrim at the foot. */
  .about-hero .stage-media{position:absolute;inset:0;flex:none;min-height:0}
  .about-hero .stage-media img{object-position:50% 15%;height:100%;
    -webkit-mask-image:none;mask-image:none}
  .about-hero .stage-copy--hero{position:relative;z-index:3;margin-top:auto;padding-top:30svh;
    background:linear-gradient(180deg,rgba(10,11,10,0) 0%,rgba(10,11,10,.5) 42%,rgba(10,11,10,.88) 100%)}
}
/* A landscape phone leaves the photo a letterbox strip; aim it at the face
   (15% showed hair down to the eyes at 844x390). */
@media (max-width:1000px) and (orientation:landscape){
  .about-hero .stage-media img{object-position:50% 25%}
}
/* The overlap trick above, applied from this side: pulled up to meet the
   pinned photo exactly at the point it starts sticking, and raised above
   it so its own background is what climbs into view, not the photo
   dropping away beneath a see-through gap.

   THIS has to be a separate, full-bleed element from .page/.about-page
   (below), not the same one - .page caps out at max-width:1500px and
   centres itself, which is right for the READING column but wrong for a
   backdrop that is meant to cover a full-bleed photo. Past 1500px+padding
   of viewport width, a cream background that stops at 1500px leaves the
   still-present (just visually buried, not gone) photo showing through
   down both margins - the cover has to reach the actual edges of the
   screen even though the text inside it doesn't. */
.about-cover{position:relative;z-index:1;margin-top:-100vh;background:var(--bg)}

/* Manta North-style alternating split - a photo on one side, a block of
   copy on the other, reversing each row. Plain static flow, not sticky -
   that treatment is reserved for the once-only hero pin above. */
.about-split{
  display:grid;grid-template-columns:1fr 1fr;gap:clamp(32px,5vw,72px);
  align-items:center;margin-bottom:clamp(48px,8vh,96px);
}
.about-split:last-child{margin-bottom:0}
.about-split.flip .about-split-media{order:2}
.about-split.flip .about-split-copy{order:1}
.about-split-media{
  border-radius:22px;overflow:hidden;background:var(--bg-2);
  aspect-ratio:4/3;position:relative;width:100%;min-width:0;
}
.about-split-media img{width:100%;height:100%;object-fit:cover;display:block}
/* The homepage teaser's stand-in (index.html #about) is a 16:9 render in
   this 4:3 box. Centred, cover trims the full-height glazing and the deck
   off the left edge, and those are what the brief asked to see, so the
   crop leans left. Scoped to #about so about.html's splits stay centred. */
#about .about-split-media img{object-position:15% 50%}
/* The photo's right edge lands exactly on the line where the Process video
   above it starts (Radin, 2026-10-08: "the start of top image and end of
   lower image to align"). At 1fr / 1fr it stopped 64px past it. Process
   (.pf-grid) is 1fr / 1.5fr with gutter --g, so its video starts one text
   track plus one gutter in: (100% - --g) / 2.5 + --g. The photo takes
   exactly that width, then the same gutter, then the copy. Both grids span
   the same width, so % resolves to the same number in each. Phones keep
   the single column below. */
@media (min-width:821px){
  #about .about-split{
    --g:clamp(32px,4.5vw,64px);
    grid-template-columns:calc((100% - var(--g)) / 2.5 + var(--g)) minmax(0,1fr);gap:var(--g);
  }
  /* Tried and reverted 2026-10-08: a square box here (aspect-ratio 1/1) to
     make the photo bigger. Radin wants the whole picture shown, not a
     bigger crop - "if you need to crop the photo, then move back". With the
     width fixed by the alignment, only a taller box makes it bigger, and on
     this 16:9 render a taller box means cropping more. The real fix is a
     render framed for the box (ask the renderer for 4:3 or square). */
}
/* No render picked for this slot yet - same "labelled empty box" idiom as
   .card-media.pending/.ix-media.pending elsewhere, not a fake photo. Dashed
   border reads as "photo goes here", not as a broken image. */
.about-split-media.pending{
  display:flex;flex-direction:column;justify-content:center;gap:8px;
  padding:28px;text-align:left;
  border:1px dashed var(--ink-4);color:var(--ink-3);
}
.about-split-media.pending p{margin:0;font-size:13.6px;line-height:1.7}
.about-split-media.pending p.mono{color:var(--ink-3)}
/* .about-block's h3/p rules already carry the right type - reused as-is by
   giving the copy column that class too, rather than duplicating them. */
.about-split-copy.about-block{margin-bottom:0}
@media (max-width:820px){
  .about-split{grid-template-columns:1fr;gap:19.2px}
  .about-split.flip .about-split-media,.about-split.flip .about-split-copy{order:0}
}
/* About page, Koto-style (Radin, 2026-10-08: "make our about page like
   this", pointing at koto.co.uk/about-koto). Koto's system, measured on their
   page: one column with everything on its left edge; every heading the same
   small tracked capitals; photos square-cornered, full width or in pairs; a
   three-figure strip. Ours runs on
   the page's own content column (.page), so its edges match the nav and
   footer. Two things are not copied: Koto's 9px grey captions (ours are 11px
   capitals in full ink) and its 300-weight body (ours is 400) - the
   readable-text floor. Text runs the full column, out to the photos' right
   edge, as Koto's does (Radin, 2026-10-08: "make the text stretch" - the
   80ch/72ch/64ch caps it shipped with came out). The alternating photo/copy rows this
   replaced are gone from about.html, but .about-split above stays - the
   homepage #about teaser still uses it. */
.ab{padding-bottom:clamp(64px,10vh,120px)}
.ab-label{
  font-family:var(--sans);font-size:14.4px;font-weight:500;letter-spacing:.16em;
  text-transform:uppercase;line-height:1.55;color:var(--ink);margin:0 0 20px;
}
.ab-head{margin:0 0 28px}
.ab-head .ab-label{margin:0 0 12px}
.ab-sub{
  margin:0;padding-left:20px;border-left:1px solid var(--ink);
  font-size:12.8px;font-weight:500;letter-spacing:.14em;text-transform:uppercase;line-height:1.6;color:var(--ink);
}
.ab-fig{margin:0 0 48px;aspect-ratio:16/9;overflow:hidden;background:var(--bg-2)}
.ab-fig picture{display:block;width:100%;height:100%}
.ab-fig img{display:block;width:100%;height:100%;object-fit:cover}
.ab-pair{display:grid;grid-template-columns:1fr 1fr;gap:clamp(16px,2.4vw,34px);margin:0 0 48px}
.ab-pair .ab-fig{aspect-ratio:4/5;margin:0}
/* A photo we don't have yet - the striped .card-media.pending fill, with a
   label saying what goes there, so it reads as a slot, not a broken image. */
.ab-ph{
  width:100%;height:100%;display:flex;align-items:center;justify-content:center;padding:24px;
  background:repeating-linear-gradient(45deg,var(--bg-2),var(--bg-2) 9px,var(--sand) 9px,var(--sand) 18px);
}
.ab-ph span{
  display:flex;flex-direction:column;gap:6px;align-items:center;text-align:center;
  background:var(--bg);padding:14px 20px;font-size:13.6px;line-height:1.5;color:var(--ink);
}
.ab-ph b{font-size:11px;font-weight:600;letter-spacing:.16em;text-transform:uppercase}
.ab-statement{margin:0 0 56px}
.ab-statement p{
  font-size:clamp(17.6px,1.45vw,20.8px);font-weight:300;line-height:1.75;letter-spacing:.01em;
  margin:0 0 16px;color:var(--ink);
}
.ab-statement p:last-child{margin-bottom:0}
.ab-stats{list-style:none;padding:0;margin:0 0 56px;display:grid;grid-template-columns:repeat(3,1fr)}
.ab-stats li{padding:28px 24px;display:flex;flex-direction:column;align-items:center;text-align:center;gap:18px}
.ab-stats li + li{border-left:1px solid var(--line)}
.ab-stats b{font-weight:300;font-size:clamp(30px,2.8vw,42px);letter-spacing:.12em;line-height:1;padding-left:.12em}
.ab-stats b::after{content:"";display:block;width:24px;height:1px;background:var(--ink);margin:20px auto 0}
.ab-stats span{font-size:11px;font-weight:500;letter-spacing:.14em;text-transform:uppercase;line-height:1.7;max-width:30ch}
.ab-sec{margin:0 0 56px}
.ab-sec > p{font-size:15.2px;line-height:2.05;letter-spacing:.02em;margin:0 0 18px;color:var(--ink)}
.ab-sec > .btn{margin-top:14px}
/* A credential, not a feature image: the award photo beside the sentence it
   evidences. Nested inside .ab-sec, so it is deliberately outside the
   `.ab-sec > p` reading rule - but the caption still takes full --ink, like
   every other line of copy on the site. */
.ab-credit{
  /* Capped, not a percentage: at 38% of a 1440 container the photo came
     out taller than the two-line caption beside it and read as a feature. */
  display:grid;grid-template-columns:minmax(0,clamp(220px,26%,320px)) 1fr;
  gap:clamp(16px,2.4vw,30px);align-items:center;
  margin:0 0 18px;
}
.ab-credit figure{margin:0;aspect-ratio:3/2;overflow:hidden;background:var(--bg-2)}
.ab-credit picture{display:block;width:100%;height:100%}
.ab-credit img{display:block;width:100%;height:100%;object-fit:cover}
.ab-credit p{margin:0;font-size:14.4px;line-height:1.95;letter-spacing:.02em;color:var(--ink)}
.ab-credit p + p{margin-top:12px}
@media (max-width:700px){
  .ab-fig{aspect-ratio:4/3}
  .ab-pair{grid-template-columns:1fr}
  .ab-credit{grid-template-columns:1fr;gap:14px}
  .ab-stats{grid-template-columns:1fr}
  .ab-stats li + li{border-left:0;border-top:1px solid var(--line)}
}

/* The drawing set, behind a disclosure - four 1500px plates unfolded into the
   scroll would be most of the page's height for a document most visitors do
   not want. */
/* ------------------------------------------------- skip link + focus

   The first thing on this page is several screens of pinned walkthrough. A
   keyboard or screen-reader user should not have to page through it to reach
   the content, and the nav is the only other way past. */
.skip{
  /* Below the bar and hard left, not centred: centred it appeared directly on
     top of the nav pill and covered two of the links it sits beside. */
  /* Hidden state is a fixed off-screen offset, not a percentage of the
     pill's own height - tying it to --bar instead meant it stopped
     clearing the bar once the header grew taller than it was tuned for. */
  position:fixed;z-index:70;top:-100px;left:var(--pad);
  background:var(--ink);color:var(--on-ink);padding:9.6px 16px;border-radius:999px;
  font-family:var(--sans);font-size:11px;font-weight:600;
  transition:top .2s ease;
}
.skip:focus{top:calc(var(--bar) + 10px)}
@media (prefers-reduced-motion:reduce){.skip{transition:none}}

/* A visible focus ring, because the nav pills and the burger had none - the
   browser default is drawn under the pill's own background on some of them.
   :focus-visible so a mouse click does not leave a ring behind. */
.nav-links a:focus-visible,
.nav-menu a:focus-visible,
.nav-cta:focus-visible,
.nav-call:focus-visible,
.nav-burger:focus-visible,
.skip:focus-visible{outline:2px solid var(--clay);outline-offset:3px}

/* Call affordance (client call, 2026-10-12; checked against the recording:
   "the top right where you can just call easily on the mobile version") -
   mobile only, icon only. Desktops keep the quiet contact block below. */
.nav-call{display:none}
.nav-call svg{width:18.5px;height:18.5px;flex:0 0 auto}
.nav-call:hover{opacity:.75}
@media (max-width:900px){
  .nav-call{
    display:inline-flex;align-items:center;margin-left:auto;margin-right:-6px;padding:10px 8px;
    color:var(--clay);text-decoration:none;
  }
  .nav-call-txt{display:none}
}
main :focus-visible{outline:2px solid var(--clay);outline-offset:3px}
/* Sections are given tabindex="-1" so a nav jump can land focus on them; that
   makes them focusable, and a 17,000px ring around a whole section is not a
   useful thing to draw. */
section:focus,section:focus-visible{outline:none}

/* ------------------------------------------------ invisible tap targets
   These controls are drawn smaller than a comfortable 44px thumb target -
   the 33.6px menu circle, text links 13-22px tall - and drawing them bigger
   would change the look. So each gets an empty pseudo-element that pads its
   hit area out to 44 x 44 around the same centre instead; a tap on a
   pseudo-element goes to its element, so nothing else changes. min(0px,
   50% - 22px) only ever grows a side: it is 0 on any side where the box is
   already 44px or more. Same idea in pages.css (.hd-arrow, .pg-arrow,
   .plan-tab) and app.css (.cfg-step); .gal-arrow here. */
.nav-burger,.link-arrow,.foot-top-link,.gal-arrow{position:relative}
.nav-burger::after,.link-arrow::after,.foot-top-link::after,.gal-arrow::after{
  content:"";position:absolute;inset:min(0px,calc(50% - 22px));
}

.plates{margin-top:16px;border-top:1px solid var(--line);padding-top:14.4px}
.plates summary{
  cursor:pointer;list-style:none;display:inline-flex;align-items:center;gap:7.2px;
  font-family:var(--sans);font-size:11.2px;font-weight:500;color:var(--ink-2);
  transition:color .2s;
}
.plates summary::-webkit-details-marker{display:none}
.plates summary::before{content:"+";font-family:var(--mono);font-size:11.2px;line-height:1}
.plates[open] summary::before{content:"\2212"}
.plates summary:hover{color:var(--ink)}

/* --------------------------------------------------------- mobile menu */
/* Three clay lines, the wordmark's own colour, and nothing round them
   (Radin, 2026-10-03: match the site, "not blue, not a circle around it",
   aligned with the logo). It was a 34px ring with no colour of its own, so
   the lines took the button's default text colour - black in Chrome, system
   blue in iPhone Safari. color and appearance are set outright now.
   The box is the icon itself, so its right edge sits on the same 16px
   gutter as the logo's left edge, centred on the logo's height; the
   invisible 44px tap area (::after, "invisible tap targets" above) is
   unchanged. flex:0 0 auto or the wordmark beside it squeezes the button. */
.nav-burger{
  display:none;flex:0 0 auto;width:24px;height:24px;cursor:pointer;
  -webkit-appearance:none;appearance:none;-webkit-tap-highlight-color:transparent;
  background:none;border:0;border-radius:0;padding:0;gap:6px;color:var(--clay);
  flex-direction:column;justify-content:center;align-items:flex-end;
  transition:opacity .2s;
}
.nav-burger:hover{opacity:.75}
.nav-burger span{
  display:block;width:24px;height:1.5px;background:currentColor;border-radius:1px;
  transition:transform .28s cubic-bezier(.4,0,.2,1),opacity .2s;
}
/* 7.5px = one line plus the 6px gap, so the outer lines cross on the middle one */
.nav-burger.on span:nth-child(1){transform:translateY(7.5px) rotate(45deg)}
.nav-burger.on span:nth-child(2){opacity:0}
.nav-burger.on span:nth-child(3){transform:translateY(-7.5px) rotate(-45deg)}

.nav-menu{
  position:fixed;z-index:49;left:0;right:0;top:0;
  padding:calc(var(--bar) + 14.4px) var(--pad) 22.4px;
  background:var(--bg);border-bottom:1px solid var(--line);
  transform:translateY(-100%);transition:transform .26s cubic-bezier(.4,0,.2,1);
  display:flex;flex-direction:column;gap:14.4px;
}
/* display:flex on .nav-menu beats the UA's [hidden]{display:none}, so the
   panel was in the layout from first paint - laid out, hit-testable, and only
   out of sight because of the transform. */
/* An open panel puts paper behind the bar whatever the page was doing, so
   js/nav.js holds .nav-solid while it is open. Trying to override the glass
   colours from a .menu-open rule instead lost on specificity to
   body:not(.interior) .nav:not(.nav-solid), and the wordmark stayed white on
   cream. */
.nav-menu[hidden]{display:none}
.nav-menu.on{transform:translateY(0)}
.nav-menu nav{display:flex;flex-direction:column}
.nav-menu nav a{
  font-family:var(--display);font-size:17.6px;font-weight:500;letter-spacing:-.02em;
  padding:10.4px 0;border-bottom:1px solid var(--line);color:var(--ink-2);
  transition:color .2s;
}
.nav-menu nav a:hover,.nav-menu nav a.here{color:#000}
.nav-menu nav a.here{font-weight:600}
.nav-menu .btn{align-self:flex-start}
@media (prefers-reduced-motion:reduce){
  .nav-menu,.nav-burger span{transition:none}
}

/* The row of links does not fit beside the wordmark and the CTA below 900.
   It used to just display:none, which left a phone with no navigation at all
   - the whole site is on this page now, so that would have meant scrolling
   past everything to reach anything. */

/* Outlined, not filled. A solid ink pill next to two glass ones was the one
   opaque object in the bar and read as a button someone had dropped on top of
   the design. */
.nav-cta{
  position:relative;
  background:transparent;color:#000;
  font-family:var(--sans);font-size:0.875rem;font-weight:600;letter-spacing:1.6px;
  padding:9.6px 19.2px;line-height:1.2;
  display:inline-flex;gap:6.4px;align-items:center;
}
/* Same hairline-reveal as .nav-links - no more filled pill announcing
   itself as a button shape. */
.nav-cta::before{
  content:'';position:absolute;left:19.2px;right:19.2px;bottom:5px;height:1px;
  background:currentColor;transform:scaleX(0);transform-origin:0% 50%;
  transition:transform .3s ease;
}
.nav-cta:hover::before{transform:scaleX(1)}
/* One line, always: "Design yours" wrapped onto two lines once the bar got
   tight, and a two-line nav button reads as broken. */
.nav-cta{white-space:nowrap;flex-shrink:0}
@media (max-width:1180px){
  /* Narrow desktops: tighter pills, so the 14px links, the logo and the
     button still share one row down to 1081px, where the burger takes over. */
  .nav-links a{padding:6.4px 11.2px}
  .nav-links a::before{left:11.2px;right:11.2px}
}

/* Sits AFTER .nav-cta deliberately: same specificity, so source order is what
   decides, and above the declaration it lost.
   1080, not 900: the 72px desktop logo, six 14px links and the button need
   ~1060px in one row. Below that the logo was the only thing that could
   give, and it gave by squashing - drawn 110px wide instead of 202 at a
   901px window (measured 2026-09-30). Up to 1080 the burger takes the links
   instead; js/nav.js closes an open menu at the same line. */
@media (max-width:1080px){
  .nav-links{display:none}
  .nav-cta{display:none}
  .nav-burger{display:flex}
}
.arr{display:inline-block;transition:transform .3s}
a:hover .arr{transform:translateX(4px)}

/* chapter rail */
/* Chapter rail rules removed with the component - see home.html. */

/* -------------------------------------------------------- stage shell */
.stage{position:relative;height:100svh}
.stage.tall{height:auto;min-height:100svh}
.stage-pin{
  position:sticky;top:0;height:100svh;overflow:hidden;
  display:flex;flex-direction:column;justify-content:flex-end;
}
.stage.tall .stage-pin{position:relative;height:auto;min-height:100svh;justify-content:center;
  padding:clamp(56px,8.8vh,104px) 0}
.stage-pin.dark{background:var(--bg)}

.stage-media{position:absolute;inset:0;z-index:0}
/* <picture> is inline by default, so height:100% on the img would resolve
   against auto and the cover fill would collapse. */
.stage-media picture{display:block;position:absolute;inset:0}
.stage-media img{width:100%;height:100%;object-fit:cover;transform:scale(1.05);will-change:transform}
.veil{
  position:absolute;inset:0;
  background:linear-gradient(to top,rgba(8,9,8,.9) 0%,rgba(8,9,8,.42) 34%,rgba(8,9,8,.05) 62%,rgba(8,9,8,.45) 100%);
}
.veil.strong{background:linear-gradient(90deg,rgba(8,9,8,.28) 0%,rgba(8,9,8,.62) 46%,rgba(8,9,8,.9) 100%)}

/* Cinematic grade, in two passes instead of one flat wash.
   .grade darkens only where type sits - the bottom band and the left column -
   and leaves the building itself alone. .vignette closes the corners so the
   frame reads as a photograph rather than a browser window. The render is the
   most expensive asset on the page; the old single 90deg wash to 90% black
   spent it on nothing. */
/* These were built when the renders shipped ungraded and needed help. The
   masters are graded now - contrast, saturation and their own baked vignette -
   so stacking another 72% black wash plus a 62% radial multiply on top was
   darkening a photograph twice and turning it murky. What is left is only the
   left-edge seat, which is structural: without it the render butts hard
   against the copy panel beside it. The vignette is gone outright; it was a
   straight duplicate of the one now baked into the file. */
.grade{
  position:absolute;inset:0;
  background:linear-gradient(90deg,rgba(6,7,6,.34) 0%,rgba(6,7,6,.08) 9%,rgba(6,7,6,0) 20%);
}
.vignette{display:none}
/* On a phone the copy sits over the whole frame, so the directional pass has
   nothing to point at - go back to a straight bottom-up lift. */
@media (max-width:1000px){
  .grade{background:linear-gradient(to bottom,rgba(6,7,6,.34) 0%,rgba(6,7,6,0) 26%,rgba(6,7,6,0) 72%,rgba(6,7,6,.46) 100%)}
}

/* ------------------------------------------------------- annotations */
.annos{position:absolute;inset:0;z-index:2;pointer-events:none}
.anno{position:absolute;left:var(--x);top:var(--y);display:flex;align-items:center;opacity:0}
.anno[data-side="left"]{flex-direction:row-reverse;transform:translateX(-100%)}
/* These mark a point on a PHOTOGRAPH, where the ground behind them varies
   from bright sky to dark timber in the same frame - a text-shadow can't
   guarantee legibility across that range the way it could reading light text
   off a uniformly dark image. Clay dot and leader instead of ink: it's the
   one colour that reads against both sky and cladding, and it's the same
   rust used for the section-cut pins, so a callout on a photo and a cut mark
   on the page read as the same drafting mark. The tag text gets its own
   small paper chip rather than a shadow, so it's legible on any ground under
   it, full stop - same fix as the fixed nav. */
.dot{
  width:5.6px;height:5.6px;border-radius:50%;flex:0 0 auto;
  background:var(--clay);box-shadow:0 0 0 5px rgba(196,122,90,.22);
}
.lead{display:block;height:1px;width:54px;background:var(--clay);opacity:.55}
.tag{
  display:block;color:var(--ink);font-size:11px;letter-spacing:.16em;line-height:1.6;
  white-space:nowrap;background:rgba(247,245,242,.88);backdrop-filter:blur(6px);
  padding:3.2px 6.4px;
}
.anno[data-side="left"] .tag{text-align:right}
.tag em{display:block;font-style:normal;color:var(--ink-3);font-size:11px;letter-spacing:.18em;margin-top:1.6px}
/* Annotations are a desktop luxury. The tags are nowrap by nature - they label
   a point, they cannot reflow - so on a 390px screen they run off the edge
   whatever x they are given. The assembly index below carries the same
   information in a form that fits. */
@media (max-width:1000px){.annos{display:none}}

/* ------------------------------------------------------------- copy */
.stage-copy{position:relative;z-index:3;padding:0 var(--pad) 0}
.stage-copy--hero{padding-bottom:clamp(128px,18vh,192px);max-width:1180px}
/* Hero-specific: raised well clear of the bottom edge. At the old padding the
   whole block sat as a tight cluster jammed into the corner, with almost
   nothing but empty photo above it - moving it up makes it read as placed,
   not stranded. Raised again for the front-elevation hero (2026-11-03): the
   render is bright edge to edge, so the headline rides the sky band where a
   shadow has plain air behind it instead of glass and grass. */
.hero .stage-copy--hero{padding-bottom:clamp(340px,52vh,580px)}
@media (min-width:1001px){.stage-copy--hero{padding-left:calc(var(--pad) + 137.6px)}}
@media (min-width:1001px){.hero .stage-copy--hero{padding-left:36px}}

/* The homepage hero: dark-on-photo scoping, same pattern as .fx-stage/.foot
   below. color is an inherited, already-resolved value, so descendants that
   never touch var(--ink) themselves need the scope redeclared here, not
   just the custom properties - an unscoped h1 read charcoal on a dark photo
   until that was made explicit (see h1's own comment just below). */
.hero{
  --ink:#f2efe8;--on-ink:#111211;--ink-2:var(--ink);--ink-3:var(--ink);
  --ink-4:rgba(242,239,232,.4);--line:rgba(242,239,232,.14);
  color:var(--ink);
}
.hero .stage-pin{background:#111211}
/* Desktop hero is exactly one screen: it scrolls away like ordinary
   content, and the homes section below it stays put until the scroll
   reaches it. It used to run 132px past one screen so the homes carousel
   could climb over the photo (.home-display's old -132px overlap in
   pages.css) with the pin holding the hero for those 132px - the homes
   coming up over the hero is a PHONE-only move (Radin, 2026-10-05: "on my
   PC I want it all to be still... it doesn't come over"). The extra
   height and the desktop overlap are both gone; the pin (position:sticky)
   stays but now has zero travel range on desktop, so nothing sticks. */
@media (min-width:701px){
  .hero{height:100svh}
}
/* nav.js's "past the hero" marker: nav.js measures the LAST .hero in the
   DOM (see its comment), which is this zero-height marker, not the section.
   It sits at 100svh, the hero's bottom at every width (phones dropped the
   200svh pinned cover on 2026-10-28), so the nav flips to its solid plate
   as the hero scrolls off. */
/* .hero.hero-boundary, not .hero-boundary alone: the marker carries class
   hero (nav.js finds it as the LAST .hero), and the phone rule
   .hero{height:200svh} (0-1-0, later in this file) beat a lone
   .hero-boundary{height:0} of equal specificity - the marker stretched to
   the section's full height and its bottom never reached the nav bar. Two
   classes here win regardless of source order. */
.hero.hero-boundary{position:absolute;left:0;top:100svh;width:1px;height:0}
/* .btn.ghost's border is a hardcoded dark rgba (see the comment on that rule)
   because every other ghost button on the site sits on paper. This is the one
   that sits on a photo, so it needs the hero's own light --ink-4 instead. */
.hero .btn.ghost{border-color:var(--ink-4)}
/* The shared .veil/.strong gradients were tuned for the old dusk render and
   a wider copy block with a CTA. This photo's glazed living area runs the
   full width right through the headline's vertical band (measured: the h1
   sits 25-41% up from the bottom edge), so no horizontal shift dodges it -
   the fix is a bottom-anchored scrim sized to the actual copy block instead
   of the generic .veil/.veil.strong gradients. */
/* Andrew's update, 3 Nov 2026: "Remove the dark foreground overlay /
   gradient. Use the render at its original supplied brightness and colour."
   The old bottom scrim + radial logo shade (which sat over the angled
   render's pale top-left leaves) is retired with the veil div itself.
   Legibility is text-shadow only now - see .hero h1 and .hero-sub below. */
/* Phones (Radin, 2026-10-03). Full-screen on a portrait phone this 16:9
   render showed ~25% of its width - a slice of timber wall - with the
   headline over it ("the house is really zoomed in, I can't see
   anything"). A first fix stood the photo under a dark header bar with the
   words on black below it; he liked the framing but wanted the rest as it
   was: "the nav bar and menu button should have a transparent background,
   so the bar shouldn't come up until I scroll down. I don't want that
   black stuff at the bottom of the image", text and button on the photo.
   So on phones:
   - the hero is as tall as its photo, not the screen, so the photo is
     scaled down: 135vw tall shows ~42% of its width instead of 25%
     (capped to the screen, so the button is always on it);
   - the photo runs right up under the transparent header, as it did
     full-screen. A version that started it below the header on a fade
     into the render's sky colour was rejected (Radin, 2026-10-03: "why
     did you put a white glow at the top, remove that");
   - aimed 56% from the left: the glazed living room, the cladding and the
     bedroom window. Aiming further left (16%, for the V-brace and the
     skylight) puts the render's top-left tree right behind the logo, and
     the clay lockup vanishes into the leaves - no scrim fixed that;
   - the headline starts 42% of the way down the photo, over the glass
     living room, with the button on the deck (Radin, 2026-10-03, "move
     the text higher" - it had sat on the lawn, then where the full-screen
     hero put it). Placed as a share of the photo's height, not px from the
     screen's bottom, so it lands on the same part of the house on every
     phone. The veil reaches higher to match, so white type holds over the
     sunlit cladding. No dark band below: the hero ends where the photo
     does;
   - no scroll drift: its scale(1.05) would cut the crop back down.
   The proper fix is a portrait render with the V-brace and skylight and
   clear sky top-left; it's in the render brief for Andrew's renderer.

   UPDATE, same day (Radin: "can we make the hero take up the whole screen
   before we scroll"). Phones now load their own 9:16 version of the render
   (index.html's <picture>, media max-width:700px): the same image extended
   with sky above and lawn below in Runway's Expand Image. So the hero is the
   full screen again without the zoom: the whole house shows across the
   middle, ~85% of its width on a 390x844 screen, aimed 40% so the V-brace
   and the bedroom window both stay in. The headline sits on the lawn just
   under the house (62% down, as a share of the screen so it lands on the
   same patch of grass on every phone), and the veil only darkens the lawn,
   not the house. The tree is now well below the logo, on open sky.

   UPDATE 2026-10-28 (Radin: "the new hero image we need to get it revamped
   for mobile"). The phone image is now "phone2": the whole house, from the
   new pro render, outpainted and with the original blended back over the
   house. The house spans ~4-97% of the image's width, so it's aimed at the
   middle (50%), which loses equal slivers of both eaves on a full-height
   390x844 and nothing on a real phone with browser bars (390x664). */
@media (max-width:700px){
  /* Plain scroll (Radin, 2026-10-28: "remove the thing where the section
     below comes over hero, just have a normal scroll"). The pinned-cover
     transition from 2026-10-04 is gone: the hero is one screen tall, so
     .stage-pin has no travel and never sticks, .home-display no longer
     pulls itself up over it (pages.css), and js/hero-cover.js with its
     settle/dim polish is retired. Same as desktop now. */
  .hero{--hero-h:100svh;height:100svh}
  /* With the hero scrolling away, its copy now passes under the bar - the
     glass nav's clay logo landed on the white text. The "past the hero"
     marker (nav.js) moves up to 20svh, so the bar turns solid after a
     short scroll, before the headline reaches it. */
  .hero.hero-boundary{top:20svh}
  body:not(.interior) .nav:not(.nav-solid){background:none}
  .hero .stage-pin{position:sticky;top:0;height:100svh;display:flex;flex-direction:column;justify-content:flex-end}
  .hero .stage-media{position:absolute;inset:0;height:100%}
  .hero .stage-media img{object-position:50% 50%;transform:none!important}
  .hero .stage-copy--hero{position:absolute;left:0;right:0;top:62%;bottom:auto;padding-bottom:0}
  /* The lawn under the button is full of pale pampas plumes, which fight the
     ghost button's white label. A faint smoky fill (the slider tags' recipe)
     settles it without a heavy block. */
  .hero .btn.ghost{background:rgba(22,20,18,.34)}
  /* The homes carousel shows straight away under the hero, without the
     scroll fade (as it did while it was the cover). */
  .home-display [data-reveal]{opacity:1;transform:none}
}

h1{
  /* Explicit, not inherited: color is an inherited property, and inheritance
     copies the ALREADY-RESOLVED value down the tree - it doesn't re-run
     var(--ink) at each descendant. .hero scopes --ink back to its light
     value for the dark photo, but that scoping is invisible to any element
     that never itself references the variable and is only inheriting a
     color fixed on body, above where the scope starts. h1 had no color rule
     at all until this, which is why the headline stayed charcoal on a night
     photo after the sitewide repaint. */
  color:var(--ink);
  /* One headline style for every page - hero, About, Process and each home.
     Light 300 started as the hero's exception (a bold weight at this size
     reads as a landing-page shout; light reads considered and editorial, the
     biggest single lever for "premium"), while Process and the home pages
     drifted to bold 600 at 54.4px and 44.8px. Client call 2026-09-29: every
     display heading read too loud, so this rule, .sect-title, .statement and
     .sc-left h2 all came down ~25% on desktop (52px to 40px here). The 26px
     phone floor sits just above the 24px section titles; 32px was tried on a
     phone and read oversized. The home pages cap lower on desktop - see
     .plan-intro-copy h1 in pages.css. Balanced so a wrapped headline splits
     into even lines instead of leaving one word on its own. */
  font-family:var(--display);font-weight:300;
  font-size:clamp(26px,2.9vw,40px);line-height:1.06;letter-spacing:-.01em;margin:0 0 19.2px;
  text-wrap:balance;
}
h1 .l{display:block}
/* Was 200 - Montserrat Thin, at 15-18px. Colour was --ink-2, a step lighter
   than body ink - full black now, per the "no grey anywhere" call. */
.lede{max-width:46ch;font-size:15.2px;line-height:1.8;color:var(--ink);margin:0 0 25.6px;font-weight:400}
.actions{display:flex;gap:8px;flex-wrap:wrap}

.btn{
  font-family:var(--mono);font-size:11px;letter-spacing:.14em;text-transform:uppercase;
  display:inline-flex;align-items:center;gap:7.2px;padding:12px 19.2px;
  /* Was a hardcoded #0e0f0e, left over from when the palette was dark and
     --ink was the cream. After the paper repaint --ink went dark, so this was
     near-black text on a near-black fill: 1.36:1 on every light page, which is
     the primary CTA on six of them. */
  background:var(--ink);color:var(--on-ink);border:1px solid var(--ink);transition:all .25s;
  /* 600, was the inherited 400 (client, 2026-10-01). At 8-8.8px with this
     much tracking, regular-weight ink on paper rendered grey - the outline
     buttons worst of all. Every .btn rather than only .ghost: solid and
     outline sit side by side as matched pairs (.plan-intro-actions, the
     booking popup's Back/Confirm), and a weight split would break them. */
  font-weight:600;
}
.btn:hover{background:transparent;color:var(--ink)}
.btn.lg{padding:14.4px 25.6px;font-size:11.2px}
/* "Book your complimentary assessment" can't fit one line on a 360-390px
   phone (385px of label for a 358px button). As a flex row the wrap left
   the arrow stranded at the far right of a two-line block; as plain inline
   text both lines centre and the arrow follows the last word. */
@media (max-width:480px){
  .btn.btn--wrap{display:block;text-align:center;line-height:1.75}
  .btn.btn--wrap .arr{margin-left:7px}
}
/* The translucent border still read as no border at all on paper (review:
   "make sure the text is black, it's not lacking colour") - so the frame is
   now full ink and the hover fills solid. The hero keeps its own --ink-4
   edge below: it sits on a photo, not paper. */
.btn.ghost{background:transparent;color:var(--ink);border-color:var(--ink)}
.btn.ghost:hover{background:var(--ink);color:var(--on-ink)}

/* .numbers, .fig-grid and .fig went with the ch1 stats section. .statement
   stays: it is the process chapter's heading (scaled with the 2026-09-29
   heading reduction). */
.statement{
  font-family:var(--display);font-weight:400;
  font-size:clamp(20.8px,2.5vw,33.6px);line-height:1.1;letter-spacing:-.006em;margin:0 0 clamp(32px,5.6vh,67.2px);
}
.statement.sm{font-size:clamp(19.2px,2vw,27.2px);margin-bottom:17.6px}
.statement em{font-style:italic;color:var(--ink-2)}


/* ------------------------------------------------------ ch2 structure */
.stage-copy--split{
  display:grid;grid-template-columns:1.02fr .98fr;gap:clamp(19.2px,4vw,70.4px);align-items:end;
  padding-bottom:clamp(48px,7.2vh,88px);
}
.sc-left h2{font-family:var(--display);font-weight:400;font-size:clamp(21.6px,2.3vw,32px);line-height:1.08;margin:0}
.sc-left h2 em{font-style:italic;color:var(--ink-2)}
.sc-right p{color:var(--ink-2);max-width:48ch;margin:0 0 12.8px;line-height:1.8;font-size:12px}
.sc-right p em{font-style:italic;color:var(--ink)}
/* Was weight 200 at --ink-2 (68% ink) - lighter than the 300 the body sets, so
   the one chapter carrying the most reading sat greyer and thinner than
   everything around it. Montserrat 200 is a display weight, not a text weight
   at 15px. */
.sc-lede{max-width:44ch;margin:16px 0 0;font-size:12px;line-height:1.75;color:var(--ink-2);font-weight:400}
.sc-left .sc-lede + .sc-lede{margin-top:11.2px}

/* Coded assembly index. This replaced a four-row definition list of prose.
   The codes are the ones actually on Ana's A.01 legend, which is the point -
   a builder recognises them, and a buyer reads them as evidence the thing has
   been drawn rather than styled. */
.idx-head{color:var(--ink-3);margin:clamp(20.8px,2.72vh,30.4px) 0 0;padding-bottom:9.6px;border-bottom:1px solid var(--line)}
.idx-head em{font-style:normal;text-transform:none;letter-spacing:.12em}
/* heading a stack of bordered cards, the label's own rule is a fourth edge */
.sp-copy-in .idx-head{border-bottom:0;padding-bottom:0}
/* The "What you get" facts, where the W-01..P-01 assembly index used to sit.
   A plain list between hairlines, like the FAQ - no tinted rounded card
   behind each item (Radin, 2026-10-01: remove "the box behind each card").
   Sized to stand as tall as the render beside it rather than huddle at the
   top of the column (Radin, same day: "spread the height of the image"). The
   render is 16:9 across ~62vw, so it grows with the window's width - the
   type (--sus-t title, --sus-b body) and the row padding (--sus-p) grow
   with it. Measured closed, heading top to last rule vs the render:
   1280x800 484/469, 1440x900 530/527, 1680x1050 610/615. The type is
   capped so a big monitor doesn't get poster-sized body copy, so the
   padding climbs faster instead (2.1vw - 8.6px is 1.5vw's value at 1440,
   more above it) to carry the height the rest of the way at 1920.
   Later the same day Radin found that too big ("make that section a bit
   smaller"), so type and row padding came down ~15-20% and the list no
   longer tries to match the render's height - it sits shorter than it.
   Then "put some space between each little section": the row padding went
   back up (a touch over the original), so it is small type with air around
   each item rather than a tight stack. Phones keep the old type sizes
   (12.4px body is already the floor for reading there). */
.sus{
  --sus-t:clamp(12.8px,.88vw,16px);
  --sus-b:clamp(12px,.8vw,14px);
  --sus-p:clamp(20px,calc(2vw - 7px),34px);
  list-style:none;margin:clamp(18px,1.5vw,28px) 0 0;padding:0;
  border-top:1px solid var(--line);
}
@media (max-width:760px){
  .sus{--sus-t:13.6px;--sus-b:12.4px;--sus-p:19px}
}
.sus li{border-bottom:1px solid var(--line)}
/* Each item drills down (Andrew, 2026-09-29 call). The padding lives on the
   summary, so the whole row is the tap target. The arrow is the homes
   carousel's chevron (.hd-arrow), turned down; open, it flips up. */
.sus summary{
  cursor:pointer;list-style:none;position:relative;
  padding:var(--sus-p) 40px var(--sus-p) 0;transition:padding-bottom .3s;
}
/* Open, the answer follows the point as its next paragraph, not as a
   separate block a row's padding away. */
.sus details[open] summary{padding-bottom:calc(var(--sus-p) * .5)}
.sus summary::-webkit-details-marker{display:none}
.sus summary::after{
  content:"";position:absolute;right:2px;width:14px;height:14px;
  top:calc(var(--sus-p) + (var(--sus-t) * 1.35 - 14px) / 2);   /* centred on the title line */
  background:var(--ink-3);
  -webkit-mask:url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='%23000' stroke-width='2' stroke-linecap='round' stroke-linejoin='round'%3E%3Cpath d='M6 9l6 6 6-6'/%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 24 24' fill='none' stroke='%23000' stroke-width='2' stroke-linecap='round' stroke-linejoin='round'%3E%3Cpath d='M6 9l6 6 6-6'/%3E%3C/svg%3E") center/contain no-repeat;
  transition:transform .3s,background-color .3s;
}
.sus details[open] summary::after{transform:rotate(180deg);background:var(--ink)}
.sus summary:hover::after{background:var(--ink)}
/* Keyboard focus only - a click never shows it. Ink, not clay, and square. */
.sus summary:focus-visible{outline:2px solid var(--ink-3);outline-offset:2px}
/* Closed, a row is just its title; the one-line summary (.sus-lead) and the
   longer explanation (.sus-more) both live in the part the arrow opens
   (Radin, 2026-10-02). */
.sus-lead{margin:0 0 calc(var(--sus-b) * .6);padding:0 40px 0 0;font-size:var(--sus-b);line-height:1.7;color:var(--ink-2)}
.sus-more{margin:0;padding:0 40px var(--sus-p) 0;font-size:var(--sus-b);line-height:1.7;color:var(--ink-2)}
/* Opening slides rather than snaps where the browser can animate to an auto
   height (Chrome 131+); elsewhere the rule is dropped and it opens at once. */
.sus{interpolate-size:allow-keywords}
.sus details::details-content{
  block-size:0;overflow:hidden;
  transition:block-size .45s cubic-bezier(.2,.7,.2,1),content-visibility .45s allow-discrete;
}
.sus details[open]::details-content{block-size:auto}
@media (prefers-reduced-motion:reduce){
  .sus details::details-content{transition:none}
}
/* The claim leads on its own line in the display face, the explanation sits
   under it as body. Run together on one line, the bold ran into the roman and
   all three rows read as a single grey paragraph with some words emboldened. */
.sus li b{
  display:block;font-family:var(--display);font-weight:600;font-size:var(--sus-t);
  letter-spacing:-.016em;line-height:1.35;color:var(--ink);margin:0;
}

/* The one line in this section worth slowing down for. Same 2px clay rule as
   .notice, so a pulled line and a flagged note are the same gesture. */
.pullq{
  margin:20.8px 0 0;padding:2.4px 0 2.4px 16px;border-left:2px solid var(--clay);
  font-family:var(--display);font-weight:500;font-size:clamp(13.2px,1.08vw,15.2px);
  line-height:1.5;letter-spacing:-.016em;color:var(--ink);max-width:38ch;
}

.idx{list-style:none;margin:0;padding:0}
.idx li{
  display:grid;grid-template-columns:62px 1fr;gap:12.8px;align-items:baseline;
  padding:8.8px 0;border-bottom:1px solid var(--line);
  transition:border-color .3s;
}
.idx li:hover{border-bottom-color:rgba(242,239,232,.34)}
.idx-c{color:var(--clay-t);font-size:11px;letter-spacing:.16em;white-space:nowrap}
.idx-b{display:block}
.idx-b b{display:block;font-weight:400;font-size:11.6px;letter-spacing:-.01em;color:var(--ink);margin-bottom:2.4px}
.idx-l{display:block;color:var(--ink-3);font-size:11px;letter-spacing:.11em;line-height:1.75;text-transform:none}
@media (max-width:520px){
  .idx li{grid-template-columns:1fr;gap:4px}
  .idx-c{color:var(--clay-t)}
}
.build{margin:20.8px 0 0;border-top:1px solid var(--line)}
.build div{display:grid;grid-template-columns:88px 1fr;gap:11.2px;padding:8.8px 0;border-bottom:1px solid var(--line)}
.build dt{color:var(--clay-t);margin:0}
.build dd{margin:0;font-size:11px;line-height:1.6;color:var(--ink-2)}
@media (max-width:1000px){
  .stage-copy--split{grid-template-columns:1fr;gap:20.8px;align-items:start}
  .build div{grid-template-columns:1fr;gap:2.4px}
}

/* ------------------------------------------------- ch2 split section
   Clay copy panel + render (see "Clay copy panel" below). The render is
   never dimmed for the sake of the type, and the type never has to fight a
   sunlit sky. On a phone the two simply stack, image first. */
.stage.split{
  position:relative;height:auto;min-height:100svh;
  display:grid;grid-template-columns:minmax(400px,38%) 1fr;align-items:stretch;
  background:var(--bg);
}
/* No rule down the column's edge: it ran the section's full height, well
   past the letterboxed render above and below it (Radin, 2026-10-01). The
   render's own edge divides the two columns. */
.sp-copy{display:flex;align-items:center}
.sp-copy-in{padding:clamp(57.6px,7.2vh,94.4px) clamp(22.4px,2.72vw,49.6px);width:100%}
/* Square corners at every width, the phone stack included (Radin,
   2026-10-02: "don't round the slider corners") - it was 22px below 1001px. */
.sp-media{position:relative;overflow:hidden;min-height:45svh;border-radius:0}
/* Sticky so the render holds while the assembly list is read beside it - the
   pinned-image feel of the reference, without pinning the whole section. */
/* height:100svh alone left a dead band. The copy column drives the row
   height, and once the sustainability points became cards the column grew
   past the viewport - so the photograph stopped 200-odd px short of the
   bottom of its own column and the drawing plate, pinned to the column,
   hung off the end of the picture onto bare paper. max of the two: the
   image always fills its column, whichever is taller. */
.sp-media .stage-media{position:sticky;top:0;height:100svh;min-height:100%}
/* The render is 1.79:1 and this column runs close to square on most desktop
   widths, so object-fit:cover was cropping close to half the image away -
   on a lot of screens that cut the entire right-hand end of the house off,
   not just the margin around it, because the roofline already runs almost
   to both edges of the source photo. object-fit:contain shows the whole
   render always; whatever gap that leaves top/bottom just shows the same
   plain paper as the rest of the section (.stage.split's own background),
   not a filled/blurred backdrop - a plain gap reads calmer than dressing
   it up. picture/img were width:100%;height:100%, so the img's own box
   still spanned the whole panel under contain and a border-radius on it
   clipped invisible padding, not the visible photo edge - flex-centring
   the picture and sizing the img to its own contained dimensions makes
   its box match the visible photo, so the radius actually shows. */
.sp-media .stage-media{display:flex;align-items:center;justify-content:center}
.sp-media .stage-media picture{position:static;display:flex;max-width:100%;max-height:100%}
.sp-media .stage-media img{
  position:static;width:auto;height:auto;max-width:100%;max-height:100%;
  transform:none;object-fit:contain;object-position:center;
  border-radius:0;
}
/* .grade is a legibility scrim for a headline sitting on top of the photo -
   this component's copy lives in the column beside it, not over the image,
   so the scrim was just adding an unwanted dark wash along the edges. */
.sp-media .grade{display:none}

/* The structure/material reveal slider standing in for the old static
   picture. .mr-frame takes over the sizing job .sp-media .stage-media img
   did above (content-sized, centred by the flex box, capped by the column)
   - specificity (3 classes) beats the generic ".sp-media .stage-media img"
   rule (2 classes) above, so .mr-after/.mr-before inside it get reset back
   to absolute/cover rather than inheriting that rule's static/contain
   sizing, which was built for a single plain <img> and would otherwise
   stack both layers as separate in-flow boxes instead of one cross-faded
   pair. aspect-ratio matches the render (2560x1440) so the frame's own box
   - not a full-bleed cover - equals the visible photo, letterboxed top and
   bottom same as the old image at this column's near-square desktop ratio;
   the slider's percentages stay correct either way since the frame IS the
   photo's box, not the taller sticky column around it. */
.sp-media .stage-media .mr-frame{
  /* position stays the base rule's relative - .mr-before-wrap/.mr-handle/
     these images all anchor to THIS box via absolute/inset:0, so it can't
     go static here the way the plain <picture> it replaces was.
     height:auto overrides the base rule's height:100% - with BOTH width
     and height definite, aspect-ratio has no auto dimension left to solve
     for and is ignored outright, which is why this was rendering as a
     near-square box (100% of the sticky column's height) instead of the
     photo's own ratio. height:auto lets aspect-ratio compute it from
     width, then max-height clamps and reflows width back down to match -
     the standard aspect-ratio+max-height "contain" pattern. */
  width:100%;height:auto;max-width:100%;max-height:100%;
  aspect-ratio:2560/1440;border-radius:0;
}
/* will-change:auto undoes the generic .stage-media img hint. Those two
   images never transform here, and the hint put each on a GPU layer, which
   pushed the callouts drawn over them onto a transparent layer of their
   own - where Chrome on Windows can't use ClearType, so the label text
   came out soft (Radin, 2026-10-02: "the text is not clear clean"). */
.sp-media .stage-media .mr-frame img{
  position:absolute;inset:0;width:100%;height:100%;max-width:none;max-height:none;
  object-fit:cover;object-position:center;transform:none;border-radius:0;will-change:auto;
}

/* Clay copy panel (Radin, 2026-10-01: "make same colour as the one above,
   the clay one" - the homes carousel's .hd-panel in css/pages.css - and
   "keep that white strip there"). On desktop the panel and the render are
   one block, flush top and bottom: the carousel's photo + clay panel,
   mirrored. The section no longer fills the screen and letterboxes the
   render in paper - its padding-block is the paper strip now, above and
   below - and the render stops being sticky; it is the row's own height.
   The row is as tall as whichever is taller, the copy or the render's own
   16:9 (that's the media column's aspect-ratio, which still counts toward
   the row while align-self:stretch fills it). The copy usually wins - it
   runs taller than a 16:9 render at most widths, and more with an item
   open - so the render covers the column the way the carousel's photo
   covers its slot: js/mat-reveal.js sets --cover (column height over the
   render's 16:9 height, between 1 and 1.15) and sizes the frame to it, the
   images cropping their sides to fill. Flush at 1366px and up with the
   items closed.
   --cover is only measured with every item closed: opening one leaves the
   render where it is (clay shows above and below) rather than zooming it
   mid-click (Radin, 2026-10-02). The callouts are moved by the same crop
   factor (pages.css), so the pins stay on the roof and the piles.
   Square corners, like the carousel. White type on plain clay is 3.34:1,
   the same trade .hd-panel makes for the exact brand clay - but without its
   text-shadow, which smudged this panel's small type (see .sp-copy below). */
@media (min-width:1001px){
  .stage.split{min-height:0;padding-block:clamp(48px,6.4vw,120px)}
  /* width:100% + justify-self:stretch: with the height stretched, the
     aspect-ratio would otherwise size the WIDTH off it and push the column
     out sideways instead of letting the render cover it. */
  /* Clay behind the render too: where --cover hits its cap (narrow laptops,
     or an item open) the render sits centred and the gap above and below
     it is the same clay as the panel, so the block stays one piece. */
  .sp-media{min-height:0;aspect-ratio:16/9;align-self:stretch;justify-self:stretch;width:100%;border-radius:0;background:var(--clay)}
  /* The stage fills the column and the frame sits centred in it, as tall as
     js/mat-reveal.js's --fh: the render's own 16:9 height times --cover. Its
     two images cover the extra height with object-fit, cropping the sides,
     and pages.css moves each callout by the same factor. No transform -
     scaling the stage painted the callouts as a stretched bitmap (soft
     labels, fuzzy hairlines; Radin, 2026-10-02). */
  .sp-media .stage-media{position:absolute;inset:0;height:auto;min-height:0}
  .sp-media .stage-media .mr-frame{height:var(--fh,auto)}
  /* Heading at the top, list filling the rest (Radin, 2026-10-02: "the
     heading pushed to top and everything spaciously laid out"). The panel
     is as tall as the render, so instead of centring a short block in it
     with spare clay above and below, the heading sits in the top corner -
     padded the same on every side - and the rows share out the leftover
     height equally, each title centred between its hairlines. An open
     row just grows; the closed ones fall back towards their own padding. */
  .sp-copy{align-items:stretch}
  .sp-copy-in{display:flex;flex-direction:column;padding:clamp(22.4px,2.72vw,49.6px)}
  .sp-copy .sus{flex:1;display:flex;flex-direction:column}
  .sp-copy .sus li{flex:1 1 auto;display:flex;flex-direction:column;justify-content:center}
  /* Opening an item shouldn't push the panel past the render (Radin,
     2026-10-02: "make the text on the left stretch as far as it can so the
     orange layer at the top and bottom don't show up"). The opened text
     runs the panel's full width, not the 52ch cap the stacked phone layout
     needs, and each row's own padding is a 12px floor rather than ~31px:
     closed, the flex rows still share out the render's height (same look as
     before); open, the closed rows give their spare space to the open one
     instead of the panel growing. Measured: every item opens inside the
     render at 1905px (tallest 629 of 664px); at 1366-1680 the longer items
     still overrun by up to ~150px, and the render holds rather than zooms
     there, as asked. */
  .sp-copy .sus{--sus-p:12px}
  /* .sus in the selector: it has to outrank the 52ch rule further down. */
  .sp-copy .sus .sus-lead,
  .sp-copy .sus .sus-more{max-width:none}
  /* The answer paragraphs drop the summary's 40px chevron gutter and run to
     the panel's inner edge (Radin, 2026-10-28: "stretch it out all the way.
     Don't crop it") - the chevron only sits beside the title row. */
  .sp-copy .sus .sus-lead,
  .sp-copy .sus .sus-more{padding-right:0}
}
/* No text-shadow here (Radin, 2026-10-02: "make text cleaner, it looks
   sloppy"). The carousel's soft 3px shadow suits its big title, but on this
   panel's 12-16px type it blurred every letter edge into a smudge. Crisp
   white instead, the body a weight heavier (500) to hold on the clay, lines
   capped at ~52 characters so the stacked phone/tablet layout doesn't run
   95-character lines, and text-wrap:pretty so no paragraph ends on one
   stranded word. */
.sp-copy{background:var(--clay);color:#fff}
.sp-copy .sect-title,
.sp-copy .sus li b,
.sp-copy .sus-lead,
.sp-copy .sus-more{color:#fff}
.sp-copy .sus-lead,
.sp-copy .sus-more{font-weight:500;line-height:1.6;letter-spacing:.005em;max-width:52ch;text-wrap:pretty}
.sp-copy .sus li b{text-wrap:balance}
/* Same type as the homes carousel's clay panel (Radin, 2026-10-02: "make
   that section the same text font or type as" the Maison 50 card), so the
   two clay panels read as one set. The heading is .hd-title (Montserrat
   Light), each item's name is that Light face a step down, and the text the
   arrow opens is .hd-desc (15.7px Regular) - all three sized in
   css/pages.css, so change them together. Phones get the same sizes too,
   as the carousel does, which is why this beats the 760px .sus rule above. */
.sp-copy .sect-title{font-weight:300;font-size:clamp(27.2px,2.4vw,32px);line-height:1.05;letter-spacing:-.01em}
.sp-copy .sus{--sus-t:clamp(17.6px,1.3vw,20px);--sus-b:15.7px}
.sp-copy .sus li b{font-weight:300;letter-spacing:-.01em}
.sp-copy .sus-lead,
.sp-copy .sus-more{font-weight:400;letter-spacing:normal}
.sp-copy .sus,
.sp-copy .sus li{border-color:rgba(255,255,255,.45)}
.sp-copy .sus summary::after,
.sp-copy .sus details[open] summary::after,
.sp-copy .sus summary:hover::after{background:#fff}
.sp-copy .sus summary:hover::after{opacity:.7}
.sp-copy .sus summary:focus-visible{outline-color:#fff}

@media (max-width:1000px){
  /* minmax(0,1fr), not 1fr - a bare 1fr can't shrink below its widest
     child, which pushed this section 75px past a 390px phone screen. */
  .stage.split{grid-template-columns:minmax(0,1fr)}
  /* No rule on top: the clay panel's own edge does that job. */
  .sp-copy{order:2}
  /* 16:9, the reveal slider's own ratio, so the render sits flush on the clay
     panel the way the homes carousel's photo does. It was a 4:3 box from
     when this held a single cover-cropped photo; the slider is contained,
     so 4:3 left ~37px of bare paper above the render and ~88px below it on
     a 390px phone. min-height:0 on the section too: its desktop 100svh
     floor stretched the rows apart into a second gap (2026-10-03 phone
     pass). */
  /* overflow:visible here specifically so the drawing-plate (a static-flow
     child, stacked below the photo on mobile) isn't clipped by the aspect-
     ratio box sized for the photo alone. */
  /* The paper strip above stays, as on desktop ("keep that white strip
     there", 2026-10-01) - without it the homes carousel's clay panel ran
     straight into the render. Below, the finishes section's own padding is
     the strip. */
  .stage.split{min-height:0;padding-top:clamp(32px,10vw,48px)}
  .sp-media{order:1;min-height:0;height:auto;aspect-ratio:16/9;overflow:visible;width:100%;min-width:0;align-self:start}
  .sp-media .stage-media{position:absolute;inset:0;height:100%;overflow:hidden}
  .sp-copy-in{padding:clamp(32px,4.8vh,46.4px) var(--pad) clamp(38.4px,5.6vh,52.8px)}
  /* The opened text runs to the panel's right edge (Radin, 2026-10-21, on
     his phone: "make sure the drop down the text goes all the way to right
     its all stuck together"). The 40px right padding on .sus-lead/.sus-more
     only keeps the chevron's column clear, but the chevron sits on the
     summary line above, so stacked it just wrapped every line ~40px early. */
  .sp-copy .sus-lead,
  .sp-copy .sus-more{padding-right:0}
}
@media (max-width:1000px) and (orientation:landscape){
  .sp-media{aspect-ratio:auto;height:56svh}
}
/* The real drawing plate, pinned in the corner of the photo like a sheet
   clipped to a board. This is the site's honest version of "sketch dissolves
/* --------------------------------------------------- ch2b finishes
   Big plate, pills floating on it, view toggles and the CTA on the bottom
   rail. Pattern lifted from buildcover.com/features, which is the clearest
   execution of it in the category. */
.fx{padding:clamp(43.2px,6.4vh,73.6px) var(--pad) clamp(38.4px,5.6vh,67.2px);background:var(--bg);max-width:var(--stage);margin:0 auto}
/* Headline and lede share a row on wide screens - stacked, the head alone ate
   590px and pushed the bottom rail off the fold. */
.fx-head{
  display:grid;grid-template-columns:1fr;gap:0;
  margin:0 0 clamp(17.6px,2.56vh,30.4px);max-width:760px;
}
@media (min-width:1100px){
  .fx-head{grid-template-columns:minmax(0,1fr) minmax(0,.82fr);gap:clamp(22.4px,3.2vw,57.6px);
    align-items:end;max-width:none}
  .fx-head .lede{padding-bottom:4.8px}
}
.fx-head .lede{margin:0}

.fx-stage{
  position:relative;overflow:hidden;background:var(--bg-2);
  border:1px solid var(--line);border-radius:0;
  /* Was a capped height (min(51svh,560px)) so the pills/plate/rail always
     fit one screen - but the renders are ~2.36:1, visibly wider than that
     capped box at most viewport widths, so object-fit:cover was cropping
     real house off the top/bottom to force the mismatch. aspect-ratio
     matching the actual render (3400x1440) instead means cover/contain both
     become a no-op - the full frame always fits, no crop - at the cost of a
     taller box than the old cap on typical desktop widths. Mobile keeps its
     own aspect-ratio:4/5 override below, unchanged - a wide photo forced
     tall on a narrow screen still needs the zoomed-in crop, just not here.
     A 16:9 box, narrowed to fit one screen, was tried on 2026-10-03 and
     reverted the same evening: Radin preferred this full-width box ("it was
     better when it's like this, with the whole image showing") - the house
     is whole here, only sky and grass are trimmed. Phones: see below. */
  aspect-ratio:3400/1440;
  /* Another instance of the .hero/.closing pattern: the pill group, view
     toggles and CTA here were all built as dark chrome (rgba(10,11,10,...)
     panels, light text) sitting on a photograph, before the sitewide
     repaint. .fx-head above this is correctly on paper and stays that way -
     only the photo stage itself needs scoping back to light text. See the
     comment on .hero for why both the custom properties AND an explicit
     color declaration are required. */
  --ink:#f2efe8;--on-ink:#111211;--ink-2:var(--ink);--ink-3:var(--ink);
  --ink-4:rgba(242,239,232,.4);--line:rgba(242,239,232,.14);
  color:var(--ink);
}
/* Every plate is stacked and cross-faded, so switching never shows a decode
   flash or a reflow. */
.fx-stack{position:absolute;inset:0}
.fx-plate{position:absolute;inset:0;opacity:0;transition:opacity .55s cubic-bezier(.4,0,.2,1)}
.fx-plate.on{opacity:1}
.fx-plate picture{display:block;position:absolute;inset:0}
/* The stage is a wide letterbox (~2.5:1 at desktop heights); the source
   renders are 16:9. A centred cover crop takes sky evenly off the top and
   bottom, which leaves almost no headroom above the roofline for the finish
   pills to sit in - they end up crowding the ridge line instead of floating
   in clear sky. Biasing the crop up trades a sliver of foreground grass
   (never the subject) for that headroom. */
.fx-plate img{width:100%;height:100%;object-fit:cover;object-position:50% 30%}
/* Darkening bands top and bottom used to sit here to help the controls read.
   They are gone: every control on this plate already carries its own backing -
   the finish pills and view toggles are their own translucent capsules, the
   CTA is a solid button - so the veil was dimming the photograph to solve a
   problem that had already been solved, and the bottom band in particular
   read as a smudge across the grass. */
.fx-veil{display:none}

/* finish pills - the floating group at the top of the plate.
   Client call 2026-09-29: corners off - the full capsules (Andrew's softer,
   glassier pill-switcher reference) are a square bar now, same as the view
   toggles and CTA below. Labels moved off the mono/uppercase system used
   for controls elsewhere (rail, view toggles, tags) onto plain Montserrat
   sentence case: this one control is a brand/lifestyle choice, not a
   technical read-out, so it earns a different voice - same split logic the
   config panel uses between spec labels (mono) and plan names (sans). */
.fx-finishes{
  position:absolute;z-index:3;top:clamp(14px,2.4vw,26px);left:50%;transform:translateX(-50%);
  display:flex;gap:2.4px;padding:3.2px;border-radius:0;
  background:rgba(10,11,10,.5);backdrop-filter:blur(16px);border:1px solid var(--line);
}
.fx-pill{
  display:inline-flex;align-items:center;gap:7.2px;cursor:pointer;
  font-family:var(--sans);font-weight:500;font-size:11px;letter-spacing:-.005em;
  background:transparent;border:0;border-radius:0;color:var(--ink-3);padding:8px 14.4px;
  transition:background .28s,color .28s;white-space:nowrap;
}
.fx-pill:hover{color:var(--ink-2)}
.fx-pill.on{background:rgba(242,239,232,.16);color:var(--ink)}
.fx-pill i{width:9.6px;height:9.6px;border-radius:50%;flex:0 0 auto;border:1px solid rgba(255,255,255,.3)}
/* "More options" closes the row and leaves the page. It was briefly filled
   clay (Andrew, 2026-10-11: "a little bit different colour... just to stand
   out"), then put back to the plain pill treatment the same day (Radin:
   "you dont need to make it filled with orange keep it normal looking").
   What still sets it apart is the arrow - no other pill has one, and no
   other pill goes anywhere. The swatch pills carry a colour dot and this
   does not, which reads the same way: a destination, not a colour. */
.fx-more{text-decoration:none}
.fx-more .arr{transition:transform .28s}
.fx-more:hover .arr{transform:translateX(3px)}

/* honest state for the two finishes Andrew has not named */
.fx-pendplate{
  position:absolute;z-index:2;left:50%;top:50%;transform:translate(-50%,-50%);
  width:min(430px,80%);padding:19.2px 20.8px;text-align:center;border-radius:0;
  background:rgba(8,9,8,.82);backdrop-filter:blur(16px);border:1px solid var(--line);
  opacity:0;visibility:hidden;transition:opacity .4s;
}
.fx.is-pending .fx-pendplate{opacity:1;visibility:visible}
.fx-pendplate .mono{color:var(--clay);margin:0 0 8px}
.fx-pendplate p:last-child{margin:0;font-size:13.6px;line-height:1.72;color:var(--ink-2)}

/* bottom rail */
.fx-foot{
  position:absolute;z-index:3;left:0;right:0;bottom:0;
  display:flex;align-items:flex-end;justify-content:space-between;gap:12.8px;
  padding:clamp(11.2px,1.76vw,20.8px);
}
.fx-views{display:flex;gap:1.6px;border-radius:0;background:rgba(10,11,10,.5);backdrop-filter:blur(12px);border:1px solid var(--line);padding:1.6px}
.fx-view{
  cursor:pointer;background:transparent;border:0;border-radius:0;color:var(--ink-3);
  font-family:var(--sans);font-size:11px;font-weight:600;letter-spacing:-.005em;
  padding:7.2px 12.8px;transition:background .28s,color .28s;white-space:nowrap;
}
.fx-view:hover{color:var(--ink-2)}
.fx-view.on{background:rgba(242,239,232,.14);color:var(--ink)}
/* Only Weathertex Natural has two camera angles (js/finishes.js hides the
   toggles for every other finish), and the note below only shows while the
   picked finish is still a candidate - both are flex/inline-flex, so the
   hidden attribute needs saying out loud. */
.fx-views[hidden]{display:none}
/* CTA here only, not the sitewide .btn: this card matches the now-square
   plate chrome end to end (client call 2026-09-29), everywhere else keeps
   the sharp mono button identity. margin-left:auto keeps it on the right
   when the rail has nothing else in it. */
/* Bigger since 2026-10-11 (Andrew: "there's also the design yours down the
   bottom. I'd probably make that bigger, that button too. So there's sort of
   two call to action button type things"). 11.2 -> 14.4px type, padding up
   with it, so the pair reads as a pair: "More options" at the top of the
   plate and this at the bottom are the two ways into the configurator, and
   this is the one that should carry weight at a glance. Still not the
   sitewide .btn - the square chrome stays. */
.fx-cta{
  flex:0 0 auto;border-radius:0;padding:16px 28px;margin-left:auto;
  font-family:var(--sans);font-weight:600;font-size:14.4px;letter-spacing:-.005em;text-transform:none;
}


/* ------------------------------------------------- ch2c room explorer */
/* Shares .fx-head with the finishes chapter above, so the two read as a pair.
   The stage borrows the finishes plate's geometry (squared with it on the
   2026-09-29 no-corners call); what is new is the hotspot layer.

   The ORIGINAL layout, restored 2026-10-11 after a same-day rebuild as a
   copy-and-chips spread (Radin: "revert the changes... on the left, i liked
   how it was before"): the picture fills the stage, the tab pill floats over
   it. Andrew's renders are in it now - see js/rooms.js for why each room has
   a wide picture and a tall one. */
.rooms{padding:clamp(8px,1.6vh,20.8px) var(--pad) clamp(43.2px,6.4vh,73.6px);background:var(--bg);max-width:var(--stage);margin:0 auto}
.rm-stage{
  position:relative;overflow:hidden;background:var(--bg-2);
  border:1px solid var(--line);border-radius:0;
  /* 2/1. Interiors are worth their ceiling in a CLT house, so not the
     finishes plate's wider letterbox. The hotspots sit in source-image
     percentages on .rm-canvas, so changing this ratio does not move them. */
  aspect-ratio:2/1;
}
.rm-stack{position:absolute;inset:0}
.rm-plate{
  position:absolute;inset:0;overflow:hidden;container-type:size;
  opacity:0;visibility:hidden;transition:opacity .5s cubic-bezier(.4,0,.2,1);
}
.rm-plate.on{opacity:1;visibility:visible}
/* .rm-canvas is the picture's own shape, sized and placed the way
   object-fit:cover + object-position (--fx/--fy) would place it, in the
   plate's container units. The dots are its children, in source-image
   percentages, so they stay on their object at any stage shape. One canvas
   per frame: wide on desktop, tall on phones (js/rooms.js). */
.rm-canvas{
  position:absolute;
  --cw:max(100cqw, calc(100cqh * var(--ar)));
  --ch:max(100cqh, calc(100cqw / var(--ar)));
  width:var(--cw);height:var(--ch);
  left:calc((100cqw - var(--cw)) * var(--fx));
  top:calc((100cqh - var(--ch)) * var(--fy));
}
.rm-canvas.is-tall{display:none}
.rm-canvas picture,.rm-canvas img,.rm-canvas video{display:block;width:100%;height:100%}

.rm-tabs{
  position:absolute;z-index:4;top:clamp(14px,2.4vw,26px);left:50%;transform:translateX(-50%);
  display:flex;gap:2.4px;padding:3.2px;border-radius:0;
  background:rgba(10,11,10,.5);backdrop-filter:blur(16px);border:1px solid rgba(242,239,232,.14);
}
.rm-tab{
  cursor:pointer;background:transparent;border:0;border-radius:0;
  font-family:var(--sans);font-weight:600;font-size:11px;letter-spacing:-.005em;
  color:#f2efe8;padding:7.2px 13.6px;white-space:nowrap;
  transition:background .28s;
}
.rm-tab.on{background:rgba(242,239,232,.16)}

/* Hotspots. Dots sit ABOVE the card, not below it. Two hotspots closer
   together than the card is wide are unavoidable - the callouts have to land
   on the feature they describe, not where the panel happens to fit - and with
   the card on top the covered dot became literally unclickable. Above, it
   stays live and reads as "there is another one here". */
.rm-dot{
  position:absolute;z-index:5;left:var(--x);top:var(--y);transform:translate(-50%,-50%);
  width:30.4px;height:30.4px;border-radius:50%;cursor:pointer;
  background:rgba(247,245,242,.94);border:0;color:#2b2b2a;
  box-shadow:0 2px 14px rgba(6,7,6,.28);
  display:flex;align-items:center;justify-content:center;
  transition:transform .25s cubic-bezier(.4,0,.2,1),background .25s;
}
.rm-dot::before,.rm-dot::after{content:"";position:absolute;background:currentColor;transition:opacity .25s}
.rm-dot::before{width:13px;height:1.5px}
.rm-dot::after{width:1.5px;height:13px}
.rm-dot:hover{transform:translate(-50%,-50%) scale(1.1)}
.rm-dot.on{background:#2b2b2a;color:#f2efe8}
.rm-dot.on::after{opacity:0} /* plus turns to minus */

/* The card belongs to the plate, not the canvas, so the plate's overflow
   cannot crop it; js/rooms.js reads the dot's position into --cx/--cy. */
.rm-card{
  position:absolute;z-index:4;
  left:calc(var(--cx) + 30px);top:calc(var(--cy) - 16px);width:min(330px,34vw);
  padding:12.8px 14.4px;border-radius:0;
  background:rgba(24,22,20,.88);backdrop-filter:blur(18px);
  border:1px solid rgba(242,239,232,.14);
  opacity:0;visibility:hidden;transform:translateY(6px);
  transition:opacity .28s ease,transform .28s cubic-bezier(.4,0,.2,1);
  pointer-events:none;
}
.rm-card.flip{left:auto;right:calc(100% - var(--cx) + 30px)}
/* Vertical mirror of .flip. A card opening off a hotspot low on the plate ran
   past the bottom edge, so below the midline it grows upward from the dot
   instead of down. */
.rm-card.up{top:auto;bottom:calc(100% - var(--cy) - 16px)}
.rm-plate.open .rm-card{opacity:1;visibility:visible;transform:none;pointer-events:auto}
.rm-card-x{
  position:absolute;top:6.4px;right:6.4px;width:19.2px;height:19.2px;
  display:flex;align-items:center;justify-content:center;
  background:transparent;border:0;border-radius:50%;cursor:pointer;
  color:#f2efe8;font-size:13.6px;line-height:1;
  transition:background .2s;
}
.rm-card-x:hover{background:rgba(242,239,232,.12)}
.rm-card-ref{margin:0 0 5.6px;padding-right:17.6px;color:var(--clay);font-size:11px;letter-spacing:.18em}
.rm-card-t{margin:0 0 4.8px;font-weight:600;font-size:11.2px;color:#f2efe8;letter-spacing:-.01em}
.rm-card-b{margin:0;font-size:13.6px;line-height:1.6;color:#f2efe8}

.rm-dot:focus-visible,.rm-tab:focus-visible{outline:1px solid var(--clay);outline-offset:3px}

@media (max-width:900px){
  .rm-stage{height:auto;aspect-ratio:4/5}
  .rm-canvas.is-wide{display:none}
  .rm-canvas.is-tall{display:block}
  .rm-tabs{left:var(--pad);right:var(--pad);transform:none;justify-content:space-between}
  /* Touch controls on the house photos (these tabs, .fx-view, .fx-pill) are
     44px tall on phones and tablets - a comfortable thumb target, and level
     with the 46px "Design yours" pill - up from ~25px. The type comes up with
     them (8.8px semibold to 11.2px medium, a touch of tracking) so a taller
     pill doesn't read as an empty box around a tiny word. */
  .rm-tab{flex:1 1 0;min-width:0;min-height:44px;padding:0 4.8px;font-size:11.2px;font-weight:500;letter-spacing:.01em;text-align:center}
  /* Drawn at 25.6px, touchable at 43.6px: a transparent border widens the
     hit area without enlarging the dot (border-box keeps the painted circle
     the same size), and the shadow moves to a filter so it traces the dot
     rather than the wider invisible box. Below the docked card, so the
     card's own close button is the way out. */
  .rm-dot{
    width:43.6px;height:43.6px;z-index:1;
    border:9px solid transparent;background-clip:padding-box;
    box-shadow:none;filter:drop-shadow(0 2px 6px rgba(6,7,6,.3));
  }
  /* .rm-dot.on sets the dark fill with the background shorthand, which
     resets background-clip - without restating it here the open dot filled
     the whole 43.6px box. */
  .rm-dot.on{background-clip:padding-box}
  .rm-dot:focus-visible{outline-offset:-6px}
  /* A 290px card beside a dot does not fit a 390px screen, so on mobile it
     stops tracking the hotspot and docks across the bottom of the plate. This
     only works because the card is a child of the plate. */
  .rm-card,.rm-card.flip,.rm-card.up{
    left:12px;right:12px;top:auto;bottom:38px;width:auto;
  }
}

.fx-pill:focus-visible,.fx-view:focus-visible{outline:1px solid var(--ink);outline-offset:2px}

@media (max-width:900px){
  /* Whole photo here too (Radin, 2026-10-03: "make it so the whole image
     shows"). The 4:5 box showed only the middle 45% of a 16:9 render's
     width; the stage is the renders' own 16:9 now. And it matches the
     laptop layout (Radin: "make it match the same colouring as the laptop
     website"): the finish bar and the CTA float on the photo in the same
     dark glass and paper. On a ~200px-tall photo they are drawn smaller
     (32px) to keep the house clear, with a 44px tap area kept through an
     invisible ::after ("invisible tap targets"). Two earlier tries moved
     them off the photo - onto a dark strip, then onto the page - and both
     were rejected. The 9.6px-label note below is the tablet bar's.
     Then the finish bar alone came off the photo, to sit just above it in
     the same dark glass (Radin, 2026-10-04: "put the selection thing above
     the image rather than on it for the phone"); the CTA stays on the
     photo. The stage is a column now - bar, then the 16:9 photo - and the
     CTA rail, absolute at the stage's foot, still lands on the photo. */
  .fx-stage{display:flex;flex-direction:column;gap:8px;height:auto;aspect-ratio:auto;overflow:visible;background:none;border:0}
  .fx-stack{position:relative;inset:auto;order:1;aspect-ratio:16/9;overflow:hidden}
  .fx-finishes{position:relative;order:0;top:auto;left:auto;right:auto;transform:none;justify-content:space-between;padding:2.4px}
  .fx-pill{position:relative;min-height:32px;padding:0 6.4px;gap:4.8px;font-size:11px;letter-spacing:0;flex:1 1 0;min-width:0;justify-content:center}
  .fx-pill::after,.fx-view::after,.fx-cta::after{content:"";position:absolute;left:0;right:0;top:-6px;bottom:-6px}
  .fx-pill i{width:8.8px;height:8.8px}
}
/* Five finishes with two-word names overlapped at 390px when squeezed
   into equal fifths. On phones the unselected ones collapse to their
   swatch (name kept as aria-label) and only the selected pill is named;
   the swatches share out the rest of the bar evenly, so it reads as one
   segmented control rather than a label with dots trailing after it.
   No gap between segments: the swatch cells have no fill, so nothing
   changes visually, but every tap on the bar now lands on a finish. Each
   swatch cell is ~31-35px wide on a 360px phone, ~38-42px at 390px and
   44px+ from 414px (measured) - the most the bar allows without shrinking
   the selected name's type. tools/site_check.py lists this as known. */
@media (max-width:700px){
  .fx-finishes{gap:0}
  .fx-pill{flex:0 0 auto;padding:0 14.4px;font-size:11.2px;font-weight:500;letter-spacing:.01em}
  .fx-pill:not(.on){flex:1 1 0;padding:0}
  .fx-pill:not(.on) span{display:none}
  .fx-pill i{width:12px;height:12px}
  /* The collapse rule above assumes every pill still shows its swatch when
     its name is hidden. "More options" has no swatch - it is a link, not a
     colour - so it collapsed to an empty clay block. It keeps its arrow
     instead: the one cell on the bar that is filled, and the only one
     pointing somewhere, which is enough to read as a way out at this size.
     The full name stays available to screen readers via aria-label. */
  .fx-more{flex:0 0 auto;padding:0 12px}
  .fx-more:not(.on) .arr{display:inline}
  .fx-more span:not(.arr){display:none}
}
/* The selections register's names (Andrew's brief 26 Oct, §9) run longer
   than this bar was sized for: "Grey Abodo Vulcan — bandsawn, Greying Agent
   (Weathered)" alone is ~370px of 11px type - wider than a phone, and wider
   than a tablet's equal-fifth cell. The name wraps inside its pill instead
   of pushing the bar off the screen or over its neighbours; on a phone the
   selected pill takes what the swatch cells leave, and they keep a
   thumb-width minimum rather than collapsing to nothing. */
@media (max-width:900px){
  .fx-pill span{white-space:normal;line-height:1.2;text-align:center}
}
/* Same on the laptop bar, which floats centred on the photo: it now stops
   16px short of the photo's edges, and only wraps a name when the window is
   too narrow for the bar on one line (about 901-1050px); wider than that,
   nothing changes. */
@media (min-width:901px){
  /* max-content: absolute at left:50%, the bar would otherwise shrink-wrap
     to the half of the photo right of its anchor. */
  .fx-finishes{width:max-content;max-width:calc(100% - 32px)}
  .fx-pill{flex:0 1 auto;min-width:0}
  .fx-pill span{white-space:normal}
  .fx-more{flex-shrink:0}
  .fx-more span{white-space:nowrap}
}
@media (max-width:700px){
  .fx-pill.on{flex:0 1 auto;min-width:0;padding:4px 12px}
  .fx-pill.on span{text-align:left}
  .fx-pill:not(.on){min-width:34px}
}
/* 12px at every width, not 11-11.2: a name of five words or more reads as a
   sentence, and "Grey Abodo Vulcan — bandsawn, Greying Agent (Weathered)"
   is one, so the 12px sentence floor applies (tools/site_check.py). Every
   pill steps up together so the bar stays one size; the wrap rules above
   are unchanged. Later than the per-width sizes above, so it wins. */
.fx-pill{font-size:12px}
@media (max-width:900px){
  /* The laptop's bottom rail, scaled down: view toggles (Weathertex
     Natural only) bottom-left, the CTA bottom-right, both 32px drawn. */
  .fx-foot{flex-direction:row;align-items:flex-end;gap:8px;padding:8px}
  .fx-views{gap:1.6px;padding:1.6px}
  .fx-view{position:relative;min-height:32px;padding:0 10px;font-size:11px}
  .fx-cta{position:relative;min-height:32px;padding:0 14px}
  .fx-pendplate{width:min(300px,86%);padding:12px}
}

/* ---------------------------------------------------- ch3 walkthrough */
/* Tall section, pinned canvas. Scroll distance is the camera path length -
   ~110svh per beat reads as deliberate rather than twitchy. */
/* -------------------------------------------------------- ch4 weeks */
/* Was capped at 1700px like .fx and .rooms - but every ordinary section
   (.sect .wrap, .page) shares the 1500px line, so on a wide monitor the
   process grid and its photo ran ~40px outside the FAQ lines below on
   each side. Client call 2026-09-29: the whole chapter sits on the shared
   1500px line; the photo gets slightly smaller past 1500px, which is the
   trade the client accepted. */
.weeks{padding:70.4px var(--pad) 38.4px;width:100%;max-width:var(--content);margin:0 auto}
/* The process as a vertical timeline: a numbered circle per step, joined by
   a hairline that fades out as it falls. The shape is the Kovax process
   section, which is the reference the brief pointed at.

   NO WRAPPER DIVS. The reference builds each row from a .step-left holding
   the circle and a flex-filling connector, plus a .step-right beside it.
   Here the circle is the existing <span class="mono"> absolutely positioned,
   and the connector is the li's own ::before stretched top to bottom - so the
   markup stays <li><span>01</span><h4/><p/></li>, nothing to re-nest.

   Capped at 680px like the reference - on the homepage it sits in the right
   half of .weeks-grid so the page width is not left empty beside it. */
.steps{
  list-style:none;padding:0;margin:0;
  max-width:680px;
  display:flex;flex-direction:column;
}
.steps li{
  position:relative;
  /* 38px circle + a 26px gutter */
  padding:0 0 clamp(24px,3.52vh,36.8px) 51.2px;
}
.steps li:last-child{padding-bottom:0}
/* Runs from under one circle to just short of the next, so it reads as a
   thread rather than butting into the marker below. Clay (was sage - see the
   note at --clay-t) at .5, a touch up from the old .45: clay is lighter than
   the dark olive it replaced, so the same alpha drew a fainter thread. */
.steps li::before{
  content:"";position:absolute;left:18.5px;top:46px;bottom:6px;width:1px;
  background:linear-gradient(to bottom,rgba(196,122,90,.5),rgba(196,122,90,0));
}
.steps li:last-child::before{display:none}
/* The numeral becomes the marker. --clay-t, not the raw brand clay: this is
   10px type and --clay measures 3.07:1 on paper (--clay-t on this .10 clay
   tint: 5.05:1). */
.steps .mono{
  position:absolute;left:0;top:0;
  width:30.4px;height:30.4px;border-radius:50%;
  display:flex;align-items:center;justify-content:center;
  border:1px solid rgba(196,122,90,.5);
  background:rgba(196,122,90,.10);
  color:var(--clay-t);
  letter-spacing:.06em;
}
.steps h4{font-family:var(--display);font-size:14.4px;margin:0 0 7.2px}
.steps p{margin:0;color:var(--ink-2);font-size:11.2px;line-height:1.75}
@media (max-width:560px){
  .steps li{padding-left:43.2px}
  .steps li::before{left:15.5px;top:40px}
  .steps .mono{width:25.6px;height:25.6px;font-size:11px}
}

/* Just the Process block now - its heading lives inside it (.pf-title),
   and the centred heading + subtext that used to sit here went with it. */
.weeks-grid{
  display:flex;flex-direction:column;align-items:center;
  gap:clamp(28.8px,4.4vh,48px);
}

/* Process teaser: all seven steps on screen at once beside one frame for the
   build timelapse (2026-10-01). It used to pin and scrub - each step lit up
   as you scrolled, across ~4 screens of scroll (js/process-feature.js,
   retired) - which made the visitor work to read seven short lines. Now it's
   a plain list in normal flow: no JS, no dimmed rows, nothing to wait for. */
/* Only the page's normal section gap above and below. The sections either
   side already bring .sect's padding; this stage's own padding plus .weeks'
   stacked on top of it to ~190-230px of blank paper at each end. The 100svh
   minimum goes too: the steps set the height now, not the screen. */
#process{min-height:0}
/* .stage-pin crops to its own box (overflow:hidden, further up) - and the
   last thing in this one, "Read the full process", starts its reveal 36px
   lower, i.e. fully below that edge, so it never registered as in view and
   never appeared. Nothing in the Process block needs cropping. */
#process .stage-pin{overflow:visible}
/* Straight after the room photos since "What is included" came off the
   homepage (2026-10-02 - every line of it was already on the home pages and
   in the Room by room cards). .rooms' bottom padding (6.4vh) is a little
   under the usual section gap (.sect, 8vh); this makes up the difference. */
.rooms + #process{padding-top:clamp(8px,1.6vh,22.4px)}
#process .stage-pin{padding:0;min-height:0}
/* Client call 2026-10-05: on wide monitors the process block sat on the
   1500px --content column while the room photos above it run on the 1700px
   --stage column - a ~100px split after ~1560px that read as the heading
   being indented. Process now shares the staged column so its heading and
   list start exactly where the image above starts. .weeks is used by no
   other section, so this is scoped here. */
#process .weeks{padding-top:0;padding-bottom:0;max-width:var(--stage)}
/* .weeks-grid centres its children instead of stretching them (it's a
   flex column with align-items:center) - .pf-wrap opts back into filling
   the full width .weeks reserves, up to its own --stage cap and the shared
   --pad edge (moved from --content to --stage 2026-10-05, see above),
   instead of shrinking to its own content width. */
.pf-wrap{align-self:stretch;width:100%}
/* Left-aligned on the steps' edge, the same heading-to-content gap as
   "Home finishes" (.fx-head's bottom margin). */
.pf-title{text-align:left;margin:0 0 clamp(17.6px,2.56vh,30.4px)}
/* Client call 2026-09-29 had the photo take more of the row (1.5fr), then
   Andrew's update 3 Nov 2026 removed the placeholder video entirely
   ("we will add this later"), so the steps are one full-width column now.
   The list keeps a readable measure - seven lines across 1300px would be
   unreadable - and the title/link ride with it. */
.pf-grid{
  display:block;
  width:100%;text-align:left;
}
.pf-grid .pf-col{max-width:min(78ch,100%)}
/* The step list stretches to the video's height and spreads its rows, so
   step 01 starts level with the top of the video and "Read the full
   process" sits level with its bottom - two clean edges instead of a list
   floating in the middle of a taller frame (2026-10-07). Where the list is
   the taller of the two, it keeps its natural spacing and the frame
   stretches to it instead (see .pf-stage below). */
.pf-col{min-width:0;align-self:stretch;display:flex;flex-direction:column}
.pf-steps{list-style:none;padding:0;margin:0;display:flex;flex-direction:column;justify-content:space-between;flex:1;gap:clamp(14.4px,1.9vh,19.2px)}
/* Straight under the last step, flush with the step text now that the
   markers are inline in the headings (2026-10-04 - the text aligns with the
   section titles above, so the link indents with nothing to follow). */
.pf-col .link-arrow{display:flex;width:max-content;margin:clamp(24px,3.2vh,32px) 0 0 0}
.pf-step{display:block}
/* Step numerals sit inline ahead of the heading, in the logo clay - the
   ringed markers were dropped from the homepage summary (2026-10-04) so the
   step text lines up flush with every section title above it. The full
   ring treatment stays on process.html. */
/* Type matches "What you get" (2026-10-07, Radin: "the process fonting
   seems off"): light 300 titles on the same clamp as its item titles, 400
   body at About's 15.2px. The old 600 titles, 500 body and 600 numerals
   were the only semibold run left on the homepage and read as chunky. */
.pf-num{
  font-family:var(--mono);font-size:14.4px;font-weight:400;letter-spacing:.06em;
  color:var(--clay,#c47a5a);margin-right:11.2px;position:relative;top:-1px;
}
.pf-text h4{font-family:var(--display);font-size:clamp(17.6px,1.3vw,20px);font-weight:300;letter-spacing:-.01em;line-height:1.35;margin:0 0 6px}
.pf-text p{margin:0;color:var(--ink);font-weight:400;font-size:15.2px;line-height:1.7;text-wrap:pretty}
/* The timelapse frame (.pf-stage), the .pf-temp chip and their sticky 4:3
   rules are retired with the placeholder video per Andrew's 3 Nov 2026 note
   ("we will add this later"); the frame comes back with real footage. */

/* Moved from pages.css - process.html was the only page-only user left once
   its content folded into this chapter, and homes.html/contact.html already
   load this stylesheet too. Same reasoning as .steps below: one copy in the
   sheet every page loads, not one per page. */
.notice{
  border:1px solid var(--line);border-left:2px solid var(--clay);
  padding:12.8px 14.4px;margin:0 0 20.8px;background:var(--bg-2);
}
/* Bumped off the caption tier (10.8px) - this is a sentence someone has to
   actually read before filling in the form, not a footnote, so it gets the
   same size as .credit/.contact-grid's body copy. Both lines explicit black
   rather than --ink-2/--clay-t, which read as grey/rust at small sizes. */
.notice p{margin:0;font-size:12px;line-height:1.75;color:#000;max-width:none}
.notice .mono{display:block;color:#000;margin-bottom:6.4px}

/* ------------------------------------------------------------ closing */
/* No image any more - it was a render standing in as the section's whole
   background, and it went. Plain paper band, same as the rest of the page.
   Two columns again, but the right side isn't empty this time - the button
   lives there, so it reads as a deliberate split rather than the old
   leftover layout with nothing to balance the copy. */
/* No min-height, and the same padding as .sect: a half-screen box with the
   row centred in it left ~275px of blank paper between Contact and this
   heading. .sect + .closing mirrors .sect + .sect - the section above
   already supplies the gap, so this one adds no top padding of its own. */
.closing{display:flex;justify-content:center}
.closing-row{
  display:flex;align-items:center;justify-content:space-between;
  gap:clamp(32px,4vw,64px);
  padding:clamp(51.2px,8vh,96px) var(--pad);max-width:var(--content);width:100%;
  text-align:left;
}
.sect + .closing .closing-row{padding-top:0}
.closing-copy{max-width:820px}
/* The row is as wide as the sections above (var(--content) plus --pad), so
   the heading starts on the same left edge and the button ends on the same
   right edge: the deliberate two-column split, heading left, button
   anchored right. space-between pins the button to the row's right edge;
   the gap stays as the MINIMUM separation so the two can never collide on
   in-between widths. */
.closing-cta{display:flex}
.closing-cta .btn.lg{flex-shrink:0}
/* align-items:center on .closing-row keeps the button centred on the gap
   between the heading's two lines. */
@media (max-width:760px){
  .closing-row{flex-direction:column;align-items:flex-start;gap:22.4px}
  /* Full width once it stacks: an easier thumb target than a small button
     parked on the left. */
  .closing-cta{width:100%;justify-content:flex-start}
  .closing-cta .btn.lg{width:100%;justify-content:center}
}

/* ------------------------------------------------------------- footer */
/* Warm walnut fill + off-white ink - the business-card treatment from
   Andrew's brand board (walnut back, cream type), the one place on the
   site that colour was named for but never used. Same scoped-override
   pattern as .hero/.fx-stage: redefine the ink ramp AND set
   colour explicitly, since colour inherits as a resolved value, not a
   live var() lookup. */
.foot{
  /* Clay since 2026-10-26, the logo's own orange (Andrew, on a call: change
     the brown "to that burnt clay or the same orange colour that we're
     using for the logo"). wordmark3-clay.png measures #c47a5a, which is
     --clay. White on clay measures 3.34:1, under AA's 4.5:1 for this small
     type, so the same remedy as the homes panel on clay (pages.css
     .hd-content): pure white ink, every step of the ramp at full strength
     (the .75 step would drop to ~2.6:1), and a light text shadow. Was
     walnut, #6b4f3a. */
  background:var(--clay);color:#fff;
  --ink:#fff;--on-ink:var(--clay);
  --ink-2:var(--ink);--ink-3:var(--ink);--ink-4:var(--ink);
  --line:rgba(255,255,255,.32);
  text-shadow:0 1px 2px rgba(0,0,0,.22);
  padding:0 var(--pad) 27.2px;
}
/* One flat flex row, not brand-vs-info nested two deep: nesting a second
   space-between inside an outer space-between starved the brand-to-HOMES
   gap down to whatever .foot-top's own gap was, while the inner row got
   the full leftover width to itself - the columns ended up on two
   different spacing scales. Flattening means every gap comes from the
   same distribution, so they're mathematically equal. */
.foot-top{display:flex;flex-direction:column;flex-wrap:wrap;align-items:flex-start;gap:20.4px;padding:20.4px 0 17px;border-top:1px solid var(--line)}
.foot-brand{display:flex;flex-direction:column;gap:11.9px;max-width:238px}
.foot-brand .wm-name b{font-size:13.6px}
.foot-brand .wm-name em{font-size:25.84px}
.wm-logo-foot{height:78.2px;width:auto;display:block;align-self:flex-start;margin-top:1.7px}
/* No socials live yet, so these are inert glyphs, not links - see
   .foot-cols FOLLOW note history. Swap the span for an <a> per icon
   once real profiles exist; the hover rule is already scoped to wait for it. */
.foot-social{display:flex;gap:11.9px;list-style:none;margin:0;padding:0;color:var(--ink-2)}
.foot-social li{display:flex}
.foot-social span{display:inline-flex;align-items:center;justify-content:center;width:44.2px;height:44.2px;border-radius:999px;cursor:pointer;transition:background .2s ease,color .2s ease,transform .2s ease}
.foot-social span:hover{background:rgba(247,245,242,.14);color:var(--ink);transform:translateY(-2px)}
.foot-social svg{width:28.9px;height:28.9px;display:block;transition:filter .2s ease}
/* Glow follows the icon's own silhouette (drop-shadow), not a box-shadow
   ring around the circular hit area - reads as a soft light bloom on the
   glyph itself rather than a hard circle outline. */
.foot-social span:hover svg{filter:drop-shadow(0 0 6px rgba(196,122,90,.65))}
.foot-links{display:flex;flex-direction:column;gap:4.25px;font-size:12.75px;color:var(--ink-2)}
.foot-links .mono{font-size:11px}
/* GET STARTED stacks a second labelled group (HOMES) beneath its own
   links - the extra top margin is what separates the two rather than
   reading as one continuous list. */
.foot-links .mono ~ .mono{margin-top:7.65px}
/* Same hairline-reveal as .nav-links a - grows in from the left on hover
   rather than just a colour change, so footer links read consistently
   with the main nav. Scoped to DIRECT children only - a plain descendant
   selector here also matches .foot-contact-item nested inside .foot-contact
   and clobbers its own inline-flex icon+text alignment. */
.foot-links > a{position:relative;display:inline-block;padding-bottom:1.7px;width:fit-content}
.foot-links > a::after{content:'';position:absolute;left:0;right:100%;bottom:0;height:1px;background:currentColor;transition:right .25s ease}
.foot-links > a:hover::after{right:0}
.foot-links a:hover{color:var(--ink)}
/* Icon + text, underline draws in on hover - see the reference bar
   Andrew's screenshot pointed at (icon, email, icon, phone). Lives under
   the logo now, so it's a clean vertical stack rather than an inline row. */
.foot-contact{display:flex;flex-direction:column;gap:7.65px;font-size:12px;color:var(--ink-2)}
/* items hug their text - stretched to the column they make the resting
   underlines (touch devices) read as full-width rules (neatening pass,
   2026-10-12) */
.foot-contact-item{display:inline-flex;align-items:center;gap:8.5px;position:relative;padding-bottom:2.55px;align-self:flex-start}
.foot-contact-item svg{width:15.3px;height:15.3px;flex:0 0 auto}
.foot-contact-item::after{content:"";position:absolute;left:0;right:100%;bottom:0;height:1px;background:currentColor;transition:right .25s ease}
.foot-contact-item:hover::after{right:0}
/* Touch screens never fire :hover, so the underline that says "this is a
   link" never appears on the device that needs it most. Rest it visible
   there, with roomier tap targets. (Client call, 2026-10-12: the phone
   and email at the bottom should read as things you can simply tap.) */
@media (pointer:coarse){
  .co-line::after,
  .foot-contact-item::after{right:0}
  .co-line{padding-bottom:7px}
  .foot-contact-item{padding:8px 0}
}
.foot-bottom{display:flex;flex-direction:column;gap:6.8px;padding:11.9px 0;border-top:1px solid var(--line)}
.foot-note{color:var(--ink-3);letter-spacing:.06em;text-transform:none;font-size:12px;line-height:1.6;margin:0;max-width:64ch}
.foot-top-link{display:inline-flex;align-items:center;gap:5.1px;font-size:11px;letter-spacing:.06em;color:var(--ink-3);transition:color .2s ease}
.foot-top-link:hover{color:var(--ink)}
.foot-top-link:hover .arr{transform:translateY(-3px)}
/* Phones (client, 2026-10-12: "all the stuff just on the left side doesn't
   look right") - the footer was one long left stack. Two columns, brand
   across the top, socials across the bottom: it reads as a footer instead
   of a receipt. */
@media (max-width:760px){
  .foot-top{
    display:grid;grid-template-columns:1fr 1fr;gap:26px 20px;align-items:start;
  }
  .foot-brand{grid-column:1 / -1;max-width:none}
  .wm-logo-foot{height:62px}
  .foot-top .foot-links:nth-of-type(2){grid-column:1}
  .foot-top .foot-links:nth-of-type(3){grid-column:2}
  /* company + get started stretch full width - mid-phrase wraps at half
     width ("Service area: Sydney / and surrounds") read as broken text
     (client, 2026-10-12: "let it stretch") */
  .foot-top .foot-links:nth-of-type(4){grid-column:1 / -1}
  .foot-top .foot-links:nth-of-type(5){grid-column:1 / -1}
  .foot-social{grid-column:1 / -1}
}
@media (min-width:761px){
  .foot-top{flex-direction:row;flex-wrap:nowrap;justify-content:space-between}
  .foot-bottom{flex-direction:row;align-items:center;justify-content:space-between}
}

/* --- A.01 interactive layout ------------------------------------------------
   Markers are positioned against .lay-plan, which wraps the image tightly and
   carries no padding of its own - the plate's padding lives on .lay-frame
   outside it. Putting padding on the positioned parent would offset every
   marker by the padding amount, and by a different amount at each breakpoint
   because the padding is a clamp(). */
.lay{margin:0 0 27.2px}
/* The homepage copy of this component sits inside .rooms, which runs to
   1700px. At that width the drawing went full-bleed and stood taller than
   the viewport, and a plan you have to scroll to see all of is not a plan
   anyone reads. two-bedroom.html's .page caps at 1500 and needs no help. */
.plan-ch .lay{max-width:1200px;margin:0 auto}
/* .lede is weight 200 sitewide, which is a display setting for a big
   hero line. Beside a black drawing it read as a caption. */
.plan-ch .lede{color:var(--ink);font-weight:400}
.lay-frame{background:#fbfaf7;border:1px solid var(--line);border-radius:22px;padding:clamp(8px,1.44vw,17.6px)}
.lay-plan{position:relative;margin:0;line-height:0}
.lay-plan img{width:100%;height:auto;display:block}

.lay-mark{
  position:absolute;left:var(--x);top:var(--y);transform:translate(-50%,-50%);
  width:20.8px;height:20.8px;padding:0;border-radius:50%;
  display:flex;align-items:center;justify-content:center;
  background:var(--bg);border:1px solid var(--ink-2);color:var(--ink);
  font-family:var(--mono);font-size:11px;line-height:1;cursor:pointer;
  transition:background .18s,border-color .18s,color .18s,transform .18s;
}
/* The dot stays small so it does not cover the drawing; the tap target is
   grown separately with a transparent ring. Scaling the dot itself to reach a
   comfortable touch size made markers 4, 5 and 6 overlap each other and hide
   the whole west wing on a 390px screen. */
.lay-mark::before{content:"";position:absolute;inset:-10px;border-radius:50%}
.lay-mark:hover{border-color:var(--ink);color:var(--ink);transform:translate(-50%,-50%) scale(1.12)}
.lay-mark.on{
  background:var(--clay-t);border-color:var(--clay-t);color:#fff;
  transform:translate(-50%,-50%) scale(1.12);
}
.lay-mark:focus-visible{outline:1px solid var(--clay-t);outline-offset:3px}

/* Fixed height, not min-height: the longest note is four lines and the shortest
   is one, and a box that grows shunts the plan up the page while the reader is
   still pointing at it. */
/* Black, not grey. Everything in this block is read rather than skimmed -
   the note IS the content of the interaction, and the key is how a room's
   area is looked up. --ink-3 at 14px was legible by the numbers but still
   reads as secondary, which is wrong for the only thing the plan says. */
/* Weight, not just colour. body sets Montserrat at 300, so this paragraph
   was rendering in Light - black, but visibly thinner than the room names on
   the drawing beside it, which are 600. Colour alone did not close that gap:
   at 14.5px Light reads grey even when the ink is pure. */
.lay-note{
  margin:14.4px 0 0;color:var(--ink);line-height:1.75;
  font-size:12.8px;font-weight:500;
  max-width:70ch;min-height:3.4em;
}

.lay-key{
  list-style:none;margin:14.4px 0 0;padding:0;
  display:grid;gap:0.8px;background:var(--line);border:1px solid var(--line);
  border-radius:16px;overflow:hidden;
  /* Explicit counts, all divisors of the six rooms in js/plan.js, NOT
     auto-fit. The grid draws its rules by showing a --line background
     through 1px gaps, so an incomplete last row is not empty space - it is
     a solid grey block the width of the missing cells. auto-fit gave five
     columns at 1200px and exactly that. If a room is ever added or removed,
     these three counts have to divide the new total. */
  grid-template-columns:repeat(3,1fr);
}
@media (max-width:900px){.lay-key{grid-template-columns:repeat(2,1fr)}}
.lay-key li{margin:0}
.lay-row{
  width:100%;display:flex;align-items:center;gap:8.8px;
  padding:8.8px 10.4px;background:var(--bg);border:0;cursor:pointer;
  text-align:left;transition:background .18s;
}
.lay-row:hover{background:var(--bg-2)}
.lay-row.on{background:var(--sand)}
.lay-n{
  flex:0 0 auto;width:16.8px;height:16.8px;border-radius:50%;
  display:flex;align-items:center;justify-content:center;
  border:1px solid var(--ink-2);color:var(--ink);
  font-family:var(--mono);font-size:11px;font-style:normal;line-height:1;
  transition:background .18s,border-color .18s,color .18s;
}
.lay-row.on .lay-n{background:var(--clay-t);border-color:var(--clay-t);color:#fff}
.lay-name{flex:1 1 auto;font-size:11.2px;font-weight:500;color:var(--ink)}
.lay-a{flex:0 0 auto;font-size:11px;font-weight:500;letter-spacing:.08em;color:var(--ink)}
.lay-row:focus-visible{outline:1px solid var(--clay-t);outline-offset:-2px}

.lay-tot{
  margin:14px 0 0;display:flex;flex-wrap:wrap;gap:6px 18px;
  font-size:11px;letter-spacing:.16em;color:var(--ink);
}
.lay-tot b{color:var(--ink);font-weight:600}

@media (max-width:640px){
  /* smaller, not larger: the plan is ~350px wide here, so a 30px dot is a
     tenth of the drawing. The ::before ring keeps it thumb-sized. */
  .lay-mark{width:17.6px;height:17.6px;font-size:11px}
  .lay-mark::before{inset:-12px}
  .lay-key{grid-template-columns:1fr}
  .lay-note{min-height:4.4em;font-size:12px}
}

/* ---------------------------------------------------------- animation */
/* The hidden state is scoped to .reveal-on, which js/reveal.js adds on its
   first synchronous line and removes if Motion never loads. [data-anim]
   before it hid unconditionally, so a blocked CDN left the content
   permanently invisible rather than merely unanimated. See js/reveal.js. */
.reveal-on [data-reveal]{opacity:0;transform:translateY(36px)}
.no-motion [data-reveal],.no-motion .anno{opacity:1!important;transform:none!important}
/* The five-homes display is its own component, not part of this sitewide
   system - see css/pages.css's .home-display rules and js/home-display.js. */
@media (prefers-reduced-motion:reduce){
  /* The movement goes, the fade stays - see js/reveal.js. Forcing opacity to
     1 here as well would have overridden the fade and left the site static
     for anyone with Windows animation effects switched off. */
  .reveal-on [data-reveal]{transform:none}
  .anno{opacity:1!important;transform:none!important}
  html{scroll-behavior:auto}
  .stage-media img{transform:none!important}
}

/* ------------------------------------------------------- display type
   Montserrat replaces the serif. Two consequences worth being explicit about:
   1. Montserrat does ship a real italic, but emphasis here stays weight +
      colour for consistency with the mono/technical-label system elsewhere -
      an italic would read as a different register, not a match for it.
   2. It wants tight negative tracking at display sizes, the way Modu sets it
      (-1.6px at 80px is about -0.02em). The page h1 is the exception - light
      weight, lighter tracking; see its own rule. */
.statement,
.sc-left h2{
  font-weight:600;
  letter-spacing:-.028em;
}
.steps h4{font-weight:600;letter-spacing:-.02em}

.statement em,
.sc-left h2 em{
  font-style:normal;
  font-weight:300;
  color:var(--ink-2);
}

/* ==================================================================
   HOMEPAGE - Andrew's brief, 26 Oct 2026 (homepage owner's block).
   Hero supporting copy, the homes model strip, Starting prices, Why
   Modular Maison, the "What you get" intro and six-week note, and the
   "Explore the construction" disclosure. Everything here reuses the type
   of a neighbouring section; the notes say whose.
   ================================================================== */

/* Hero supporting copy. The first line is the site's .lede; the six-week
   qualification under it sits at the 12px sentence floor (smaller, still
   read over the render); the by-line between the two. All weight 500 and a
   tight shadow - the same recipe the nav's type uses over this photo -
   because 400 at 12-15px on a photograph thins to grey. The block is three
   lines taller than the headline-and-buttons it was, so it sits lower:
   its top lands about where the headline used to. */
/* The small print is its own block, .hero-fine (2026-10-28), so phones can
   move it under the buttons; here it keeps the spacing it had inside
   .hero-sub - the lede's 16px above it, 25.6px to the buttons. */
/* Small print block retired (Andrew's update, 3 Nov 2026): the hero is now
   the headline, the lede and the buttons. With the veil gone, these shadows
   carry the type over pale lawn and pampas - a single soft pass vanished
   into the grass, so it is a tight 1px edge plus a mid halo plus a wide
   one. The ghost buttons get the phone's translucent fill at every width
   for the same reason (a hairline outline alone disappears on pampas). */
.hero-sub{max-width:58ch;margin:0}
.hero-sub p{margin:0}
/* Andrew's update, 3 Nov 2026: with the dark overlay gone, the render's
   lower band (deck, lawn, pampas) is pale, so light type cannot hold on it
   without a scrim. The hero copy therefore INVERTS: ink type with a soft
   paper halo, the editorial treatment for a bright architectural photo.
   The halo is a shadow, not a layer - the render keeps its supplied
   brightness everywhere. */
.hero{--ink:#f8f6f2;--on-ink:#141514;--ink-2:var(--ink);--ink-3:var(--ink);--ink-4:rgba(248,246,242,.55);--line:rgba(248,246,242,.22);color:var(--ink)}
/* White type, tight shadow only (a whisper, not a glow) - the reference
   version's clarity. Black on this render was the mushy one. */
/* Radin, 4 Nov 2026: "make that text white and then move it down and across
   on the grass". White type, sitting low on the lawn, running across the
   frame - the render itself stays untouched, so the shadow does the work. */
.hero h1,.hero .hero-sub,.hero .lede{
  color:var(--ink);
  text-shadow:0 2px 3px rgba(8,9,8,.95),0 4px 10px rgba(8,9,8,.85),
              0 10px 34px rgba(8,9,8,.65),0 18px 70px rgba(8,9,8,.4);
}
@media (min-width:701px){
  /* Andrew's Website Final Edits, #2: "Remove the dark foreground overlay /
     gradient. Use the render at its original supplied brightness and
     colour." No grade, no shade - the render exactly as supplied.
     Legibility comes from the type's own tight shadow only. */
}
/* Both hero buttons hollow (Radin, 2026-11-03: "just like it wasn't in that
   photo, see-through, hollow") - transparent, white hairline, white type. */
/* Hero buttons in the wordmark's own clay (Radin, 2026-11-04: "the colour of
   those buttons the same colour as logo") - hollow, clay hairline + clay
   labels, a faint clay wash on hover. */
.hero .actions .btn,
.hero .actions .btn:first-child{
  background:var(--clay);border-color:var(--clay);color:var(--ink);
  text-shadow:none;backdrop-filter:none;
}
.hero .actions .btn:hover,
.hero .actions .btn:first-child:hover{background:#b06a4c;border-color:#b06a4c;color:var(--ink)}
/* Type pass (Radin, 28 Oct: "fix fonting"): two sizes, not three - the
   lede, then the qualification and by-line as one small-print pair at the
   same size (12 and 13.6px read as a mistake). The lede drops to 400 so it
   sits with the light headline instead of reading bold under it; the pair
   keeps 500 (400 that small thins to grey on the photo) and gets a little
   tracking and leading. */
.hero-sub .lede{max-width:none;margin:0 0 16px;font-size:clamp(16px,1.2vw,18.4px);line-height:1.55;font-weight:500;letter-spacing:.005em}
@media (min-width:701px){
  /* Radin, 2026-11-03: copy this layout - WHITE type, lower-left, headline
     then the lede (Andrew's copy - never remove it) then the two hollow
     buttons. White reads clear; the black was mushy against the render. */
  .hero .stage-pin{justify-content:flex-end}
  /* Andrew, 4 Nov call: "make it white and then maybe even just move it down
     across, down over that grass over to the right-hand side of the bottom of
     the page". Right-hand end of the lawn, same low baseline. */
  .hero .stage-copy--hero{
    padding:0 0 clamp(4px,1vh,18px);margin:0 var(--pad) 0 auto;
    max-width:min(860px,calc(100% - 2*var(--pad)));
    align-self:flex-end;text-align:left;background:none;
  }
  /* Wider, so the copy reads as lines, not a block (Radin, 28 Oct: "so
     blocky"), then brought back from 940px ("don't extend that much").
     text-wrap:pretty only keeps a lone word off a last line (balance
     halved every line and brought the block back). */
  .hero-sub{max-width:min(1080px,100%)}
  .hero-sub p{text-wrap:pretty}
  /* The call button's icon is the phone layout only (below). */
  .hero-call .hero-call-ico{display:none}
}
@media (max-width:700px){
  /* Phones (Radin, 28 Oct): "its all over the screen", "looks even
     worse... the positioning", then "i want all the texty then the buttons
     below it". So: headline, lede, small print, buttons - one block,
     bottom-anchored on the photo, kept as short as it can be (tight gaps,
     small print at the 12px floor, two button rows). The small print sat in
     a band under the photo for an hour; Radin wanted it with the rest. */
  .hero .stage-copy--hero{top:auto;bottom:clamp(140px,20svh,180px)}
  /* The phone crop puts the copy over the hedge and pampas, which are much
     darker than the desktop's lawn - ink type disappears there, so phones
     keep LIGHT type with a strong shadow (desktop stays ink on its pale
     lawn). Andrew's "no overlay" still holds: no tint, just shadows. */
  .hero{--ink:#f7f5f2;--on-ink:#141514;--ink-4:rgba(247,245,242,.5);--line:rgba(247,245,242,.16);color:var(--ink)}
  .hero h1,.hero .hero-sub{text-shadow:0 1px 2px rgba(8,9,8,.9),0 2px 10px rgba(8,9,8,.65),0 6px 26px rgba(8,9,8,.4)}
  .hero .actions .btn:first-child{background:var(--ink);color:var(--on-ink);border-color:var(--ink)}
  /* The paper-filled ghost button needs ink type on phones: the hero's --ink
     is light there, so it was white-on-white. */
  .hero .actions .btn.ghost:not(:first-child){color:#141514;border-color:rgba(20,21,20,.3)}
  /* Andrew's update, 3 Nov 2026: no darkening shade behind the copy either
     ("remove the dark foreground overlay / gradient") - the old
     .stage-copy--hero::before gradient is retired. The headline's shadow
     below is what holds the type off the lawn. */
  /* The light headline crosses the white V-brace - a soft shadow keeps its
     letters off the post (verifier, 28 Oct). */
  .hero h1,.hero .hero-sub{color:#f7f5f2}
  .hero h1{margin-bottom:12px;text-shadow:0 1px 2px rgba(8,9,8,.55),0 2px 18px rgba(8,9,8,.7),0 4px 32px rgba(8,9,8,.45)}
  .hero-sub{margin:0 0 12px}
  /* Phone lede stays 500: at 15px over the photo, 400 goes thin. */
  .hero-sub .lede{font-size:15.2px;font-weight:500;line-height:1.5;margin-bottom:0}
  /* Two rows, not three equal outlines: "Design yours" is the one filled
     button, full width; "Check your property" and the call button share
     the row under it, the call button as a square phone icon (the nav's
     glyph). It is still the direct CALL button (Radin, 2026-10-14) - its
     label stays for screen readers, and shows in full from 701px. */
  .hero .actions{display:grid;grid-template-columns:1fr 46px;gap:8px}
  .hero .actions .btn{justify-content:center;min-height:46px;padding:0 16px}
  .hero .actions .btn:first-child{grid-column:1/-1;background:var(--ink);color:var(--on-ink);border-color:var(--ink)}
  .hero .actions .hero-call{padding:0}
  .hero-call .hero-call-ico{display:block;width:19px;height:19px}
  .hero-call .hero-call-txt{position:absolute;width:1px;height:1px;overflow:hidden;clip-path:inset(50%);white-space:nowrap}
}

/* The homes model strip: the room switcher's smoked tab group (.rm-tabs,
   further up) floated over the carousel photo, centred on the photo
   column (65% of the track) rather than the whole track. Below 900px the
   photo is the full width, so the strip spans it edge to edge like the
   room tabs do there, and on a phone each name breaks after "Maison". */
.hd-models{
  position:absolute;z-index:4;top:clamp(14px,2.4vw,26px);left:32.5%;transform:translateX(-50%);
  display:flex;gap:2.4px;padding:3.2px;border-radius:0;
  background:rgba(10,11,10,.5);backdrop-filter:blur(16px);border:1px solid rgba(242,239,232,.14);
}
.hd-models .rm-tab:hover{background:rgba(242,239,232,.08)}
.hd-models .rm-tab.on{background:rgba(242,239,232,.16)}
@media (max-width:900px){
  .hd-models{left:var(--pad);right:var(--pad);top:12px;transform:none;justify-content:space-between}
}
@media (max-width:560px){
  /* One line, not two (Radin, 28 Oct: the strip "takes up half image").
     Broken after "Maison", the five names made a two-line bar over a fifth
     of the photo. The phone shows only the model part - 60 Sky, 60,
     60 Urban, 50, 50 Urban - and "Maison" stays in the button for screen
     readers; the card below still carries the full name. */
  .hd-models .rm-tab span:first-child{position:absolute;width:1px;height:1px;overflow:hidden;clip-path:inset(50%);white-space:nowrap}
  /* Smaller, still over the photo (Radin, 28 Oct: a band above the photo
     "looks worse now, move back but just shrink size"). The bar drops from
     52px to ~30px: tabs 24px tall instead of the 44px phone tap height,
     tighter padding and a smaller inset from the photo's top. The ::after
     strip keeps a ~44px touch area without drawing a taller bar (the
     .fx-pill recipe). */
  .hd-models{top:8px;padding:2px}
  .hd-models .rm-tab{position:relative;min-height:24px;padding:0 2px;flex:1 1 0;min-width:0}
  .hd-models .rm-tab::after{content:"";position:absolute;left:0;right:0;top:-10px;bottom:-10px}
}

/* Starting prices. Ordinary .sect content on the shared column. The pair
   is About's stats row turned to the left edge: the model name in the
   carousel card's light title, the type as a tracked label, the figure in
   the stats' light numeral, a hairline between the two. */
#prices .page-head,#why .page-head{border-bottom:0;padding-bottom:0}
.price-list{
  list-style:none;margin:0;padding:0;display:grid;grid-template-columns:repeat(2,minmax(0,1fr));
  border-top:1px solid var(--line);border-bottom:1px solid var(--line);
}
.price-list li{padding:clamp(24px,3vw,40px) clamp(20px,3vw,48px) clamp(24px,3vw,40px) 0}
.price-list li + li{border-left:1px solid var(--line);padding-left:clamp(20px,3vw,48px)}
.price-name{
  font-family:var(--display);font-weight:300;font-size:clamp(24px,2.4vw,32px);
  line-height:1.05;letter-spacing:-.01em;margin:0 0 12px;color:var(--ink);
}
.price-type{margin:0 0 clamp(18px,2.2vw,28px)}
.price-fig{margin:0;font-size:15.2px;line-height:1.5;color:var(--ink)}
.price-fig b{
  font-family:var(--display);font-weight:300;font-size:clamp(30px,2.8vw,42px);
  letter-spacing:.02em;line-height:1;margin:0 .12em;
}
.price-foot{
  display:flex;flex-wrap:wrap;align-items:center;justify-content:space-between;
  gap:24px 48px;margin-top:clamp(24px,3.2vw,40px);
}
.price-foot p{flex:1 1 480px;margin:0;max-width:76ch;font-size:15.2px;line-height:1.8;color:var(--ink)}
.price-foot .btn{flex:0 0 auto}
@media (max-width:700px){
  /* Own layer, own paper. Added while phones pinned the hero photo for 2x
     the screen and it covered the top of Prices (28 Oct); the pin is gone
     since, and this stays as a harmless guard. */
  #prices,#why{position:relative;z-index:2;background:var(--bg)}
  .price-list{grid-template-columns:minmax(0,1fr)}
  .price-list li{padding-right:0}
  .price-list li + li{border-left:0;border-top:1px solid var(--line);padding-left:0}
  .price-foot p{flex-basis:100%}
  /* As a flex item the button kept its one-line width (414px) and pushed
     the page sideways; full width lets .btn--wrap break it in two. */
  .price-foot .btn{flex:1 1 100%;min-width:0}
}

/* Why Modular Maison. The Process list's type (.pf-num's clay numeral,
   .pf-text's light title and 15.2px body), five across on a wide screen,
   each under its own hairline. Narrower, five across is a 200px column,
   so they become rows - numeral and title left, text right - and on a
   phone a plain stack. The paper below is .stage.split's own strip. */
.why{padding-bottom:0}
.why-list{
  list-style:none;margin:0;padding:0;display:grid;
  grid-template-columns:repeat(5,minmax(0,1fr));gap:0 clamp(24px,2.4vw,40px);
}
.why-list li{border-top:1px solid var(--line);padding-top:clamp(18px,1.6vw,24px)}
.why-list .pf-num{display:block;top:0;margin:0 0 12px}
.why-list h3{
  font-family:var(--display);font-size:clamp(17.6px,1.3vw,20px);font-weight:300;
  letter-spacing:-.01em;line-height:1.35;margin:0 0 10px;color:var(--ink);text-wrap:balance;
}
.why-list p{margin:0;color:var(--ink);font-weight:400;font-size:15.2px;line-height:1.7;text-wrap:pretty}
@media (max-width:1279px){
  .why-list{grid-template-columns:minmax(0,1fr)}
  .why-list li{
    display:grid;grid-template-columns:minmax(0,1fr) minmax(0,2fr);column-gap:clamp(24px,4vw,64px);
    align-items:start;padding:clamp(18px,2vw,24px) 0;
  }
  .why-list li:last-child{border-bottom:1px solid var(--line)}
  .why-list .pf-num{grid-column:1;grid-row:1}
  .why-list h3{grid-column:1;grid-row:2}
  .why-list p{grid-column:2;grid-row:1 / span 2}
}
@media (max-width:700px){
  .why-list li{display:block}
  .why{padding-bottom:clamp(8px,3vw,16px)}
}

/* "What you get": the brief's intro under the heading, in the panel's
   .hd-desc type, and the six-week qualification right under the list at the
   12px sentence floor - kept with the list, not only inside a row. The lede
   runs the panel's full width (Radin, 2026-10-28: "stretch it out all the
   way. Don't crop it") - the old 52ch cap stopped it short of the clay
   panel's edge, which read as cropped text. On the stacked phone layout the
   column is narrower than 52ch anyway, so nothing changes there. */
.sp-lede{margin:clamp(10px,1vw,16px) 0 0;font-size:15.7px;line-height:1.6;font-weight:400;color:#fff;max-width:none;text-wrap:pretty}
.sus-note{margin:clamp(12px,1vw,16px) 0 0;font-size:12px;line-height:1.6;font-weight:500;color:#fff;max-width:none;text-wrap:pretty}
@media (max-width:1000px){.sus-note{max-width:64ch}}

/* "Explore the construction": its own section below the split (Radin,
   2026-10-28: "make the explore the construction separate below the what
   you get", then "dont make it orange make it like a heading"). Not a clay
   band any more: it sits on the paper on the page's content grid, its
   summary set exactly like .sect-title (display, 300, clamp 24-38.4px,
   lh 1.05) with a hairline above and an ink chevron, so closed it reads as
   a section heading that opens. Open, the six labels sit three across,
   then two, then one. */
.mr-explore-sect{margin:clamp(44px,4.6vw,68px) 0}
.mr-explore-sect .mr-explore{
  width:100%;max-width:var(--content);margin:0 auto;
  background:transparent;color:var(--ink);
  padding:0 var(--pad);
}
.mr-explore details{border-top:1px solid var(--line)}
.mr-explore summary{
  cursor:pointer;list-style:none;position:relative;
  padding:clamp(18px,1.6vw,24px) 40px clamp(18px,1.6vw,24px) 0;
  font-family:var(--display);font-weight:300;font-size:clamp(24px,2.8vw,38.4px);
  letter-spacing:-.01em;line-height:1.05;color:var(--ink);
}
.mr-explore summary::-webkit-details-marker{display:none}
.mr-explore summary::after{
  content:"";position:absolute;right:2px;top:50%;width:16px;height:16px;margin-top:-8px;
  background:currentColor;
  -webkit-mask:url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 24 24' fill='none' stroke='%23000' stroke-width='2' stroke-linecap='round' stroke-linejoin='round'%3E%3Cpath d='M6 9l6 6 6-6'/%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 24 24' fill='none' stroke='%23000' stroke-width='2' stroke-linecap='round' stroke-linejoin='round'%3E%3Cpath d='M6 9l6 6 6-6'/%3E%3C/svg%3E") center/contain no-repeat;
  transition:transform .3s,opacity .3s;
}
.mr-explore details[open] summary::after{transform:rotate(180deg)}
.mr-explore summary:hover::after{opacity:.7}
.mr-explore summary:focus-visible{outline:2px solid var(--ink);outline-offset:2px}
.mr-explore-body{padding:clamp(4px,.4vw,8px) 0 clamp(28px,2.6vw,44px)}
.mr-explore-list{
  list-style:none;margin:0;padding:0;display:grid;
  grid-template-columns:repeat(3,minmax(0,1fr));gap:24px clamp(24px,3vw,48px);
}
.mr-explore-list b{display:block;font-family:var(--display);font-weight:600;font-size:15.2px;letter-spacing:-.006em;margin:0 0 6px;color:var(--ink)}
.mr-explore-list p{margin:0;font-size:15.2px;line-height:1.6;color:var(--ink);text-wrap:pretty}
@media (max-width:1000px){
  .mr-explore-list{grid-template-columns:repeat(2,minmax(0,1fr))}
  /* Stacked, the heading keeps the page gutter (padding is on the
     container above, so nothing else to do here). */
}
@media (max-width:700px){
  .mr-explore-list{grid-template-columns:minmax(0,1fr)}
}

/* ==================================================================
   PHONE TYPE SCALE - outlier pass (Radin, 28 Oct: "the mobile site at
   parts the sizing is so different and off"). Every text node on all 11
   pages was measured at 390px (e94dd27b scratchpad verify/t_sizes.js):
   the site runs page title 26 / section heading 24 / body 15.2 / labels
   ~11, and these were the strays. Phone only, hero excluded. The
   pages.css half of this pass is at the end of that file.
   ================================================================== */
@media (max-width:700px){
  /* "What you get" was 27.2px against every other section's 24px. Its
     twin, the homes card title (.hd-title, pages.css), comes down with it
     so the two clay panels still read as one set. */
  .sp-copy .sect-title{font-size:24px}
  /* Body 15.7 -> 15.2 (slider intro and feature text), and the About
     award caption 14.4 -> 15.2: once it stacks under its photo it reads
     as one of the paragraphs around it. */
  .sp-lede{font-size:15.2px}
  .sp-copy .sus{--sus-b:15.2px}
  .ab-credit p{font-size:15.2px}
}
