/* Interior pages. Loads after home.css, which owns the tokens, nav and footer. */

/* Every tracked-uppercase label on these pages used to be set in a mono face.
   It is Montserrat now (Andrew's brand board named only Montserrat and a
   script), which sets lighter at the same size - so the label register gets a
   weight step to keep the presence it had. Same reasoning as .mono in
   home.css; these selectors just never went through that class. */
.card-meta li,.render-cap,.plate-cap,
.spec-list dt,.meta-list dt{font-weight:500}

/* width:100% (not just max-width) matters specifically because body.interior
   is a flex column (below) and .page is its flex item, centred by auto
   margins - an item with no definite width sizes to its own content's
   max-content width first and THEN centres that, instead of filling the
   container and letting max-width cap it. Every page's content was wide
   enough that this never showed, until the plan-gallery figure (all its
   slides position:absolute) gave a flex item with genuinely nothing to
   measure - the whole page collapsed to a sliver around it.
   Top padding floors at 106px: the fixed header is 82px tall at every width,
   and pad + 59.2px alone is only 75px on a phone - each page's opening line
   started 7px underneath the header. 106px is the header plus 24px of air;
   from ~800px up the original formula is larger and still applies. */
/* Both numbers are the old ones plus 13.4px, the amount the nav grew when
   the logo went up ~22% on 2026-10-11 (97.6 -> 111px, see .wm-logo in
   home.css). They are not free-floating: at 1024 the 119.4 floor wins and
   leaves the same 8.4px of air under the bar that 106 used to, and above
   that the --pad term takes over at the same rate. Without the shift,
   privacy.html and terms.html ran their first heading under the deeper
   header - site_check catches exactly this. */
.page{padding:max(calc(var(--pad) + 72.6px),119.4px) var(--pad) 0;max-width:var(--content);width:100%;margin:0 auto}
/* The explore pages (two-bedroom, maison-*) opt into a wider column via this
   class on body - 404.html also uses .page and stays at the narrower default,
   since a wide-open error page has nothing to fill the extra room with. */
.plan-page .page{max-width:1900px}
/* .page's top padding is sized to clear the fixed nav on a page that opens
   straight onto .page-head. about.html opens on the full-bleed .about-hero
   instead (outside .page, same as the homepage's own full-bleed sections),
   so the div that follows it only needs normal inter-section breathing
   room, not nav clearance on top of a hero it isn't touching. */
.about-page{padding-top:clamp(51.2px,8vh,96px)}
.page-head{border-bottom:1px solid var(--line);padding-bottom:clamp(24px,4vh,44.8px);margin-bottom:clamp(27.2px,4.8vh,51.2px)}
/* Spacing only - the type itself is the sitewide page-headline rule on h1
   (home.css), shared with the hero, About and each home's page. */
.page-head h1{margin:0 0 14.4px}
/* a head with no lede under it should not carry the h1's bottom margin */
.page-head h1:last-child{margin-bottom:0}
.page-head .lede{max-width:52ch;margin:0}
.page-head .lede.wide{max-width:none}

/* generic two-column body */
.cols{display:grid;grid-template-columns:1fr 1fr;gap:clamp(19.2px,4vw,57.6px);align-items:start}
.cols p{color:var(--ink-2);line-height:1.85;margin:0 0 14.4px}
@media (max-width:820px){.cols{grid-template-columns:1fr}}

/* ------------------------------------------------------- plan intro
   Each home's page opens on this: heading, a couple of paragraphs and two
   CTAs on the left, one real photo of that specific home on the right -
   measured off dinesen.com's product pages, one of Andrew's four reference
   sites. The image stretches to match whatever height the copy ends up at
   (align-items:stretch on the grid), not a fixed viewport height - our
   renders are wide elevations, not portrait shots, so a tall fixed box would
   crop far more of the building away than this does. */
.plan-intro{
  display:grid;grid-template-columns:minmax(340px,680px) 1fr;
  gap:clamp(40px,5.6vw,88px);align-items:stretch;
  margin:0 0 clamp(36.8px,6.4vh,72px);
  /* Short copy left this well under half the viewport on a common laptop
     screen, so the tabs section below sat visibly in the fold on load -
     capped low (720px) rather than a full 100svh so the wide elevation
     render only gets modestly taller through align-items:stretch, not
     squeezed toward the portrait crop the fully-fluid height above was
     written to avoid. */
  min-height:clamp(500px,78svh,720px);
}
.plan-intro-copy{display:flex;flex-direction:column;justify-content:center}
/* Same light headline style as every page (home.css h1), but the home's name
   keeps its own lower desktop cap (34.4px to the shared 40px) - at the full
   page-headline size it reads oversized beside the photo. Same 26px on a
   phone as the other pages. */
.plan-intro-copy h1{font-size:clamp(26px,2.9vw,34.4px);margin:0 0 24px}
/* Wider than the sitewide 46ch body-copy cap on purpose - the wider left
   column (above) gives a line more room, and a narrower cap on top of that
   just wrapped every sentence into four short lines instead of two. Widened
   again (60ch to 70ch) and given more line-height and paragraph spacing -
   at 60ch every line broke after 7-8 words, which read as cramped even
   though nothing was actually overlapping. */
.plan-intro-copy p{color:var(--ink-2);line-height:1.95;max-width:70ch;font-size:15.5px;margin:0 0 20px}
.plan-intro-actions{display:flex;gap:8px;flex-wrap:wrap;margin-top:17.6px}
/* Both buttons white here rather than the sitewide solid-ink primary - on
   this pale a page a black box reads heavier than either CTA is meant to
   carry, and matching them lets the two read as one choice, not a primary
   and an afterthought. */
.plan-intro-actions .btn{background:#fff;color:#000;border-color:var(--ink)}
.plan-intro-actions .btn:hover{background:var(--bg-2);color:#000}
/* Phones: the pair shares the row edge to edge, and where it can't fit
   side by side (360px) each takes a full row - it wrapped as two
   different-width buttons stacked ragged-left (2026-10-03 phone pass). */
@media (max-width:600px){
  .plan-intro-actions .btn{flex:1 1 auto;justify-content:center}
}
.plan-intro-actions .btn.ghost:hover{background:var(--bg-2)}
/* Wider than the row it sits in is tall, and self-aligned rather than
   stretched to the row's min-height above - our elevation renders run
   1.78:1 to 2.37:1, so a box that stretched to fill a 500-720px-tall row
   forced a near-square crop that cut the roofline and ground off most of
   them. 16:9 fits four of the five renders edge to edge already; the one
   wider render (two-bedroom's, 2.37:1) crops in a little off each side
   instead - checked the actual crop first, and it loses only empty sky and
   grass margin, not the roofline, the ground plane or the V-brace leg. */
.plan-intro-media{
  border-radius:22px;overflow:hidden;background:var(--bg-2);
  aspect-ratio:16/9;align-self:center;position:relative;width:100%;min-width:0;margin:0;
  /* Every visible slide is position:absolute now (the gallery below), which
     means none of them contribute to this figure's own size. width:100% fills
     the grid column same as before, but a grid item's default min-width:auto
     still floors the 1fr track at the item's own (near-zero) content size -
     min-width:0 lets the track actually grow to fill the row. margin:0 resets
     the browser's default 40px inline margin on <figure> - harmless while the
     box sized itself from its (unmarged) content, but a 100%-width box plus
     that margin is wider than its own column, and overflowed on mobile. */
}
.plan-intro-media img{width:100%;height:100%;object-fit:cover;display:block}
@media (max-width:900px){
  .plan-intro{grid-template-columns:1fr;min-height:0}
  .plan-intro-media{order:-1;aspect-ratio:16/9;align-self:auto}
}

/* -------------------------------------------------------- process.html
   Andrew's 7-stage copy. Numbered circle + connecting line is the same
   visual language as the homepage's short .steps teaser, just built at
   page scale (bigger circle, room for a tagline plus several paragraphs
   per stage, not one line). */
.process-hero{max-width:760px}
.process-hero p{color:var(--ink-2);line-height:1.85;font-size:15.2px;max-width:68ch;margin:0 0 12.8px}
.process-hero p:last-child{margin-bottom:0}
/* .page-head .lede{margin:0} (home.css) otherwise beats the rule above on
   specificity and zeroes this one paragraph's bottom margin, running it
   straight into the next. */
.process-hero p.lede{margin-bottom:12.8px}

.process-list{list-style:none;margin:0 0 clamp(48px,7vh,80px);padding:0;max-width:760px}
.process-step{position:relative;padding:0 0 clamp(32px,4.8vh,52px) 60.8px}
.process-step:last-child{padding-bottom:0}
/* Stroke-only clay rings, briefed off archiblox.com.au's process rings
   (2026-10-04 client screenshot): full-strength 2px accent stroke, no tint
   fill, accent numeral, and a plain neutral connector from badge to badge.
   Ring + numeral are --clay #c47a5a, the logo/brand clay (favicon + clay
   wordmark), not the darker --clay-t text token. Numeral on white is 3.35:1 -
   accepted for a decorative index numeral that duplicates the heading text;
   swap to --clay-t if it needs AA at this size. */
.process-step::before{
  content:"";position:absolute;left:18.2px;top:38.4px;bottom:6px;width:2px;
  background:var(--line);
}
.process-step:last-child::before{display:none}
.process-step .mono{
  position:absolute;left:0;top:0;width:38.4px;height:38.4px;border-radius:50%;
  display:flex;align-items:center;justify-content:center;
  border:2px solid var(--clay,#c47a5a);background:transparent;
  color:var(--clay,#c47a5a);font-size:15.2px;letter-spacing:.06em;
}
.process-step 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 6.4px}
.process-step-tag{font-style:italic;color:var(--ink-3);font-size:14.4px;margin:0 0 12.8px}
.process-step-body p{color:var(--ink-2);line-height:1.85;font-size:15.2px;max-width:62ch;margin:0 0 12.8px}
.process-step-body p:last-child{margin-bottom:0}

/* margin-bottom: this is the last thing on both pages that use it
   (process.html, about.html) before the footer, and .page's own bottom
   padding is deliberately 0 (its padding shorthand's third value) since
   most closing content already carries its own trailing space. This one
   didn't, so the footer landed flush against the button with no gap at
   all - measured 0px on about.html, actually overlapping by 36px on
   process.html. */
.process-cta{border-top:1px solid var(--line);padding-top:clamp(28.8px,4.4vh,44.8px);margin-bottom:clamp(51.2px,8vh,96px);max-width:640px}
.process-cta h2{font-family:var(--display);font-weight:300;letter-spacing:-.01em;font-size:clamp(22.4px,2.8vw,32px);margin:0 0 12.8px}
.process-cta p{color:var(--ink-2);line-height:1.8;font-size:15.2px;margin:0 0 24px}

@media (max-width:560px){
  .process-step{padding-left:51.2px}
  .process-step::before{left:14.2px;top:30.4px}
  .process-step .mono{width:30.4px;height:30.4px;font-size:13.2px}
}

/* ---------------------------------------- process.html
   A full-screen photo header with the title and intro on it, then each of
   the seven stages as its own spread - text left,
   its own picture right - down the page, and the closing call to action.
   (Started 2026-10-08 after archiblox.com.au's process page; the tabs and
   ring-and-line timeline from that version were dropped the same day for
   one spread per stage, after Dvele, Vipp and Cover.) */

/* Header. The bar stays transparent over it (body has no .interior, and
   .pr-hero-mark is the .hero nav.js measures). */
.pr-hero{
  --ink:#f2efe8;color:var(--ink);
  position:relative;background:#1d2128;
  /* 200vh, not the one screen it started as (Radin, 2026-10-11: "make it
     so the hero is glued just like how the about is and when i scroll the
     stuff below comes and takes over the page"): 100vh of pin + 100vh of
     travel for .pr-cover, the exact accounting of .stage.about-hero in
     home.css - see its comment for the full mechanism. overflow:hidden
     moved OFF this box onto .pr-hero-pin: an ancestor that is a scroll
     container (overflow:hidden) is what stops a sticky child sticking. */
  height:200vh;
}
/* The frozen layer: photo + copy hold at the top of the viewport for the
   whole 200vh (the .stage-pin recipe, same as About's). */
.pr-hero-pin{position:sticky;top:0;height:100svh;overflow:hidden}
.pr-hero picture{position:absolute;inset:0}
/* The crew shot, 1066x869 whole, in a box nearer 16:9 - so cover takes a
   band out of its height and leaves the width alone, which makes the
   vertical position the only framing decision there is, and a
   consequential one. 22%, after sweeping it in a real browser at 1440x900
   (20/38/55/70): the percentage reads as how far down the photo the window
   sits, so lower keeps the top. At 38%, where this started, the hard hat
   and most of the man's face sat up behind the transparent nav bar; by 55%
   his head had gone entirely. At 22% the whole man clears the bar - hat,
   face, hi-vis shoulder, the arm all the way down to both hands - and the
   panel still lies across the lower third with its printed number in
   frame. What it gives up is the bottom edge: one sling and some blue site
   hoarding, the only part of this photo nothing depends on.
   Horizontally centred, unlike the render this replaced, which was pinned
   to 0% to slide the house clear of the copy. Nothing to gain here anyway:
   cover is width-bound at this aspect, so there is no horizontal overflow
   to position. Tighter framings were measured and rejected - cropping in
   far enough to enlarge the man costs 1.8-2.9 dB and the only slack in the
   frame is on the right, where the panel number lives. */
.pr-hero img{width:100%;height:100%;object-fit:cover;object-position:50% 22%;display:block}
/* Dark down the left side, under the copy, easing out before the middle of
   the house; a light band at the top for the bar. */
/* Deeper since 2026-10-11. These numbers were set against the blue-hour
   skeleton render, which was dark to begin with; the photo that replaced
   it is a daylight shot of raw pine, and the title was sitting on the
   brightest part of the frame. The shape of the gradient is unchanged -
   only how far it goes. */
.pr-hero-veil{
  position:absolute;inset:0;pointer-events:none;
  background:
    linear-gradient(90deg,rgba(8,9,8,.8) 0%,rgba(8,9,8,.66) 28%,rgba(8,9,8,.28) 48%,rgba(8,9,8,0) 66%),
    linear-gradient(to bottom,rgba(8,9,8,.44) 0%,rgba(8,9,8,0) 22%);
}
/* Title with the intro under it, one block on the logo's line, centred on
   the header's height (Radin, 2026-10-08: "aligned with the middle of
   height", the intro "stretch more", no orange line above). Dinesen and
   Garde Hvalsoe hold their header copy the same way. */
.pr-hero-copy{
  position:absolute;z-index:1;inset:0 var(--pad);
  display:flex;flex-direction:column;justify-content:center;
}
.pr-hero h1{color:var(--ink);margin:0;max-width:18ch}
/* As wide as it can run before the render's V-brace, at most 60ch. On a
   window squarer than the render the picture is sized by the header's
   height, so the brace sits ~55% of that height in from the left. */
.pr-hero-lede{margin:clamp(18px,2.6vh,26px) 0 0;max-width:max(300px,min(60ch,calc(max(55svh,308px) - var(--pad))));font-size:clamp(16px,1.1vw,18.4px);line-height:1.7;font-weight:500;color:var(--ink)}
/* The lede can run wider on a window this shape. The 10% scale from the
   left edge that used to come with it is gone: it existed to slide the
   render's V-brace out from behind the copy, and the photo has no brace -
   all the scale did was throw away 10% of a 4032px original. */
@media (min-aspect-ratio:16/9) and (min-width:901px){
  .pr-hero-lede{max-width:max(300px,min(60ch,calc(35vw - var(--pad))))}
}
/* Two classes, so the zero height beats .hero{height:100svh/200svh}.
   top:100vh - the document position of .pr-cover's top edge inside the
   200vh wrapper (its -100vh margin pulls it exactly there), which is what
   actually marks paper taking over from the photo. bottom:0 would now sit
   at 200vh, two screens down. Same reasoning as .hero.about-hero-boundary
   in home.css. */
.hero.pr-hero-mark{position:absolute;left:0;top:100vh;width:1px;height:0}

/* The climb. Same split as about.html's .about-cover: a separate
   full-bleed element from .page/.pr-page carries the pull-up and the
   paper background (the .page column must not, or past its max-width the
   still-buried photo would show through the margins), and it sits at
   z-index:1 so its background is what visibly rises over the frozen
   photo. margin-top:-100vh pulls its top edge to meet the pin exactly
   when the pin starts sticking. */
.pr-cover{position:relative;z-index:1;margin-top:-100vh;background:var(--bg)}

/* Edge to edge on the logo's line, not the 1500px column, under the
   full-window header. */
.pr-page{padding-top:clamp(72px,12vh,144px);max-width:none}

/* One spread per stage (Radin, 2026-10-08): text left, its own picture
   right, every stage on the page in order. After Dvele, Vipp and Cover -
   one large picture per step, light type and room around it, no rings,
   lines or tabs. A hairline sits between spreads.
   Text column and measure widened a touch on review (Radin, 2026-10-11:
   "the texts on the left of each, let them stretch a bit more"). */
.pr-stage{
  display:grid;grid-template-columns:minmax(0,1.1fr) minmax(0,1.15fr);gap:clamp(48px,6vw,120px);
  align-items:center;padding:clamp(56px,9vh,112px) 0;border-top:1px solid var(--line);
}
/* The first spread follows the header directly - no rule above it. */
.pr-stage:first-child{border-top:0;padding-top:0}
.pr-stage-n{margin:0 0 clamp(16px,2.4vh,24px);font-size:12px;font-weight:600;letter-spacing:.18em;text-transform:uppercase;color:var(--clay-t)}
.pr-stage h2{
  margin:0 0 14px;font-family:var(--display);font-weight:300;letter-spacing:-.015em;
  font-size:clamp(30px,3.2vw,48px);line-height:1.08;color:var(--ink);
}
.pr-stage-tag{margin:0 0 clamp(24px,3.6vh,36px);font-style:italic;font-size:clamp(16px,1.1vw,18px);line-height:1.5;color:var(--ink)}
.pr-stage-body p{margin:0 0 14px;max-width:64ch;font-size:clamp(15.2px,1vw,16.8px);line-height:1.8;color:var(--ink)}
.pr-stage-body p:last-child{margin-bottom:0}
/* The picture is shown WHOLE (Radin, 2026-10-11: "use full photo, don't
   crop any of it out"). No fixed frame and no object-fit:cover - the frame
   is simply the image's own shape at the column's width, so nothing is
   ever trimmed, whatever the window. This replaced a fixed 4/3 + cover,
   which side-cropped every widescreen render by ~26% of its width; the
   per-image zoom rules that fought that old frame (pr-stage-zoom,
   pr-stage-ground) were retired with it. */
.pr-stage-media{position:relative;overflow:hidden;background:var(--bg-2)}
.pr-stage-media picture{display:block}
.pr-stage-media img,.pr-stage-media video{display:block;width:100%;height:auto}
/* The floor plan is a drawing, not a photo: inset on paper so it keeps its
   white margin instead of running edge to edge. */
.pr-stage-media img.pr-stage-plan{padding:clamp(24px,4vw,64px);box-sizing:border-box}

/* Closing call to action: heading and line left, the button on the right
   (Radin's notes, 2026-10-08), as on the About page. */
.pr-page .process-cta{max-width:none}
.pr-page .process-cta p{max-width:62ch}
@media (min-width:641px){
  .pr-page .process-cta{display:grid;grid-template-columns:minmax(0,1fr) auto;column-gap:clamp(24px,4vw,64px)}
  .pr-page .process-cta h2{grid-column:1;grid-row:1}
  .pr-page .process-cta p{grid-column:1;grid-row:2;margin:0}
  .pr-page .process-cta .btn{grid-column:2;grid-row:1/span 2;align-self:center}
}

/* Stacked: picture first, then its text. */
@media (max-width:900px){
  .pr-stage{grid-template-columns:minmax(0,1fr);gap:28px;padding:clamp(40px,7vh,64px) 0}
  .pr-stage-media{order:-1}
  /* 701-900px is still served the whole frame, and a portrait window that
     wide takes a narrow slice of it. 24% keeps the man and his hands in
     that slice instead of centring on the panel's blank middle. */
  .pr-hero img{object-position:24% 50%}
  .pr-hero-lede{max-width:300px}
}
@media (max-width:700px){
  /* Copy runs the full width over the photo on a phone: an even, deeper
     veil instead of the side one. Deeper again since 2026-10-11 - the crew
     shot is a high-key frame, white sky behind the man, and the title was
     washing out against it where the render never did. */
  .pr-hero-veil{background:
    linear-gradient(to bottom,rgba(8,9,8,.62) 0%,rgba(8,9,8,.56) 30%,rgba(8,9,8,.64) 70%,rgba(8,9,8,.72) 100%)}
  .pr-hero-lede{max-width:none}
  /* Phones get the crew shot, already cropped tall in the import tool, so
     cover has only a little width left to trim. Centred is right. */
  .pr-hero img{object-position:50% 50%}
}

/* Small crossfade gallery inside the intro photo - same interaction as the
   homepage's .home-display carousel (see js/plan-gallery.js), but simpler
   markup: no side panel per slide, since the heading/copy/CTAs already live
   outside the photo and stay fixed while only the image cycles. First slide
   is the plan's own exterior; the rest are the three standard interior
   finish options, same on every plan page since finishes are sitewide, not
   plan-specific (see the Finishes tab below). */
.pg-track{position:absolute;inset:0}
.pg-slide{
  position:absolute;inset:0;opacity:0;visibility:hidden;
  transition:opacity .5s ease-in-out,visibility .5s;
}
.pg-slide.is-on{opacity:1;visibility:visible}
.pg-slide picture,.pg-slide img{width:100%;height:100%;display:block}
.pg-nav{
  position:absolute;left:0;right:0;bottom:0;z-index:1;
  display:flex;align-items:center;justify-content:space-between;
  padding:9.6px 12.8px;color:#fff;
  background:linear-gradient(to top,rgba(0,0,0,.5),transparent);
}
/* Full white, total included - same fix as .hd-counter: the " / 4" at 75%
   white was hand-rolled "secondary" text over a photo (site_check's grey
   text check, 2026-10-02). */
.pg-counter{font-family:var(--mono);font-size:11px;letter-spacing:.1em;color:#fff}
.pg-arrows{display:flex;gap:12px}
.pg-arrow{
  width:32px;height:32px;display:flex;align-items:center;justify-content:center;
  background:transparent;color:#fff;border:none;cursor:pointer;
  transition:transform .2s,opacity .2s;filter:drop-shadow(0 1px 2px rgba(0,0,0,.35));
}
.pg-arrow:hover{opacity:.65}
.pg-arrow:active{transform:translateY(1px)}
.pg-arrow:focus-visible{outline:2px solid #fff;outline-offset:2px}
/* 44 x 44 tap area without redrawing the chevron (see "invisible tap
   targets" in home.css). The pair sits 12px apart (was 4.8px) so each can
   grow 6px a side without Next's area reaching over Previous. */
.pg-arrow{position:relative}
.pg-arrow::after{content:"";position:absolute;inset:-6px}

/* --------------------------------------------------------- plan tabs
   dinesen.com's product-page tabs (Variants/Expression/Finishing/Dimensions/
   Technical), re-themed for a secondary dwelling rather than a wood floor -
   see the HTML comment on .plan-tabs for the category mapping. Tab row on
   top, a content column and a fixed-size image crossfading beside it below -
   the image never resizes the layout when the tab changes, only its content
   does, same as the reference. */
.plan-tabs-nav{
  display:flex;gap:clamp(24px,3.2vw,48px);flex-wrap:wrap;
  border-bottom:1px solid var(--line);margin-bottom:clamp(28.8px,4.8vh,48px);
}
.plan-tab{
  background:none;border:none;cursor:pointer;padding:0 0 14.4px;margin-bottom:-1px;
  border-bottom:1px solid transparent;
  font-family:var(--sans);font-size:15.2px;color:var(--ink-3);transition:color .2s;
}
.plan-tab:hover{color:var(--ink)}
.plan-tab.is-on{color:var(--clay-t);border-bottom-color:var(--clay-t)}
.plan-tab:focus-visible{outline:2px solid var(--clay);outline-offset:3px}
/* 31px-tall tabs, 44px to a thumb - see "invisible tap targets" in home.css.
   The 24px+ gap between tabs (and between wrapped rows) keeps the padded
   areas from overlapping. */
.plan-tab{position:relative}
.plan-tab::after{content:"";position:absolute;inset:min(0px,calc(50% - 22px))}
/* At 15.2px the four tabs need ~303px plus gaps, so on a phone
   "Specification" dropped to a row of its own. A touch smaller and tighter
   here keeps them on one line down to 360px. */
@media (max-width:430px){
  .plan-tabs-nav{gap:14px}
  .plan-tab{font-size:14px}
}

/* align-items default (stretch), not start: the text column's own content
   (a handful of spec rows + a couple of short notes) is much shorter than
   the media column's fixed 4:3 box, and start-aligning left it stranded at
   the top with a large dead gap below. Stretching the body to match height,
   then centering its content in .plan-tab-panel.is-on below, spreads it into
   that space instead of leaving it unused. */
/* minmax(0,1fr), not 1fr: a bare 1fr can't shrink below its content, and
   the 4:3 media box's content is its own 640px width - so between 901px and
   1279px the page scrolled sideways by up to 300px. */
/* One 5:7 split at every width (client, 2026-10-02: "make the sizing
   bigger"). It used to be a 460px text column beside a plan capped at 640px,
   which on a wide monitor left ~570px of empty paper between the two; the
   5:7 ratio is the one small laptops already used, now everywhere, so the
   plan grows with the screen and the text column with it. */
.plan-tabs-grid{display:grid;grid-template-columns:minmax(260px,5fr) minmax(0,7fr);gap:clamp(40px,5.6vw,88px)}
.plan-tabs-body{display:flex}
.plan-tabs-body h2{
  font-family:var(--display);font-weight:300;letter-spacing:-.01em;
  font-size:clamp(22.4px,2.3vw,32px);margin:0 0 16px;
}
.plan-tab-panel{display:none}
.plan-tab-panel.is-on{display:flex;flex-direction:column;justify-content:center;width:100%}
/* .plan-tab-panel p.plan-tab-note, not .plan-tab-note: the sitewide
   ".section p{margin:0 0 14.4px}" rule (class+type) was beating a lone
   class selector on specificity and silently zeroing the top margin, so
   each note sat flush against whatever came before it instead of the
   intended 16px gap. Two classes + type here so this wins outright rather
   than depending on which rule happens to come later in the file. */
.plan-tab-panel p.plan-tab-note{color:var(--ink-2);line-height:1.8;font-size:15.2px;margin:16px 0 0;max-width:none}
.plan-tab-panel .btn{margin-top:20.8px}

/* Layout's content (heading, hint, room rows, footnote) is shorter than the
   floor plan image beside it, same as the other three tabs - centering it
   (the shared .plan-tab-panel.is-on rule) is what actually lines it up with
   the plan; flex-start left it hugging the top of the row with a visible
   dead gap below while the image sat centred, reading as misaligned. */
/* The Layout tab's own rhythm is tighter than the rest of the panel copy:
   h2->hint->list->note all sat one collapsed 16px margin apart, reading as
   one dense block. Widening each of those three gaps independently rather
   than just bumping the shared .plan-tab-note margin, which would also
   pull apart the single-paragraph Finishes/Dimensions/Specification panels
   that don't have this problem. */
#panel-layout h2{margin-bottom:28.8px}
#panel-layout p.plan-tab-note:first-of-type{margin-top:0;margin-bottom:20.8px}
#panel-layout .spec-list{margin-bottom:24px}

/* Room rows double as hover/click targets for the floor plan overlay -
   see js/plan-tabs.js. Left border swaps from transparent to clay on
   hover/active rather than changing background, so the row doesn't
   compete with .room-hl's own highlight colour on the plan beside it. */
.spec-list>div[data-room]{
  cursor:pointer;border-left:3px solid transparent;margin-left:-16px;padding-left:13px;
  transition:border-color .15s,background-color .15s;
}
.spec-list>div[data-room]:hover,.spec-list>div[data-room].is-active{
  border-left-color:var(--clay);background:var(--bg-2);
}
.spec-list>div[data-room]:focus-visible{outline:2px solid var(--clay);outline-offset:-2px}
/* Rows in the tabs a size up from the shared .spec-list - same 2026-10-02
   sizing pass. Top/bottom padding only, so the hover rows' own left inset
   (above) survives. */
.plan-tabs .spec-list>div{grid-template-columns:180px 1fr;padding-top:16px;padding-bottom:16px}
.plan-tabs .spec-list dt{font-size:11px}
.plan-tabs .spec-list dd{font-size:15.2px}
@media (max-width:700px){.plan-tabs .spec-list>div{grid-template-columns:1fr}}

/* Overlay sits inside .lay-plan, which the existing width-driven/height:auto
   sizing (see the comment above .tab-plan .lay-plan) makes exactly equal to
   the SVG drawing's own box - so a child positioned in percentages here
   lines up with the drawing's real geometry, not just visually close to it.
   Percentages per room per plan are read straight off each plan's own SVG
   (viewBox + wall/leaf-divider coordinates), not eyeballed. */
.room-hl{
  position:absolute;border-radius:3px;pointer-events:none;
  background:rgba(147,81,52,.16);border:1.5px solid rgba(147,81,52,.6);
  opacity:0;transition:opacity .18s ease;
}
.room-hl.is-on{opacity:1}
/* A drawn feature's name as real text over the plan, placed in the same
   viewBox percentages as .room-hl (first use: the Sky's "Skylight in roof",
   Andrew 2026-10-14 - SVG text scaled with the drawing to ~7 px on a
   laptop). Centred on its x, hanging from its y. .lay-plan sets
   line-height:0 for the image, so this sets its own. */
.plan-note{
  position:absolute;transform:translateX(-50%);white-space:nowrap;pointer-events:none;
  padding:3px 8px;background:rgba(247,245,242,.94);border:1px solid rgba(20,20,20,.18);border-radius:2px;
  font-family:var(--sans);font-size:12px;font-weight:500;line-height:1.3;letter-spacing:.02em;color:var(--ink);
}
/* Anchored by its right edge instead of its centre - the deck captions on
   the two Maison 50 pages end flush with the 50's deck edge, which keeps a
   phone-width caption inside the drawing. */
.plan-note--end{transform:translateX(-100%)}
/* A sample of the drawing's dashed deck outline (#5c4a3d, 10/7 dashes),
   so the caption says which line it means. */
.plan-note .dash{display:inline-block;width:19px;height:2px;margin:0 7px 0 0;vertical-align:middle;
  background:repeating-linear-gradient(90deg,#5c4a3d 0 5px,transparent 5px 9px)}   /* drawn dashes - a dashed border goes solid this short */
@media (max-width:600px){.plan-note{padding:2px 6px}.plan-note .dash{width:14px;margin-right:5px}}

/* width:100% - without it the box sized itself to its content (a grid item
   with an aspect-ratio isn't stretched), which left it 589px wide on some
   homes and 640px on others, and 40px short of the text's right edge on a
   phone. */
.plan-tabs-media{position:relative;width:100%;margin:0;aspect-ratio:4/3;border-radius:22px;overflow:hidden;background:var(--bg-2)}
/* Toggled by js/plan-tabs.js while Finishes is active and no swatch preview
   is showing - drops the card background only (box keeps its normal size
   and position, see the no-media comment in plan-tabs.js's activate()), so
   idle Finishes reads as open space rather than a placeholder box, and a
   swatch hover can swap it back on every frame without anything shifting. */
.plan-tabs-media.blank{background:transparent}
/* Direct-child selector, not a descendant one: the layout tab nests its own
   <img> (the SVG floor plan) two levels inside .tab-plan, and a bare
   ".plan-tabs-media img" match forced that nested image to opacity:0 as well,
   independent of .tab-plan's own opacity - it rendered as a blank white box
   with just the numbered markers floating on it until this was scoped. */
.plan-tabs-media > img{
  position:absolute;inset:0;width:100%;height:100%;object-fit:cover;
  opacity:0;pointer-events:none;transition:opacity .4s ease;
}
.plan-tabs-media > img.is-on{opacity:1}

/* The Layout tab isn't a photo, it's the furnished plan tools/build_plan_svg.py
   draws straight from spec/products.json - navy walls, real furniture and
   door swings for mm-60/sky/urban, a generic furnished schematic for
   mm-50/urban. Same crossfade slot as the three photo tabs. White card
   background, since the drawing's own light blue-grey starts only at the
   building's own edge, with margin around it. */
.tab-plan{
  position:absolute;inset:0;opacity:0;pointer-events:none;transition:opacity .4s ease;
  display:flex;background:#fff;padding:20px;
}
.tab-plan.is-on{opacity:1;pointer-events:auto}
/* Width-driven, height:auto - NOT object-fit:contain on a fixed-height box.
   Every plan here is wider than the 4:3 media box (mm-50's is over 2:1) -
   contain on a stretched-height figure would letterbox it instead of filling
   the width. Sizing from width and letting height follow the image's own
   ratio makes .lay-plan's box exactly equal the drawing's box. */
.tab-plan .lay-plan{flex:1;min-width:0;align-self:center;position:relative;margin:0;line-height:0}
.tab-plan .lay-plan img{width:100%;height:auto;display:block}
/* The Layout tab's hint: "hover", and a plan to the right, only hold
   side by side. Stacked (900px and under, phones) the plan is above the
   room list and the reader has a thumb, so it says that instead. */
.hint-narrow{display:none}
@media (max-width:900px){
  .plan-tabs-grid{grid-template-columns:1fr}
  .plan-tabs-media{order:-1;aspect-ratio:16/10;max-width:none;margin-left:0}
  .hint-wide{display:none}
  .hint-narrow{display:inline}
  /* Finishes, stacked: no shared photo box. With eight categories it sat
     below the whole list, far from the swatch just tapped, so each row
     shows its own selection's photo instead (.finish-row-photo, below).
     .on-finishes is set by js/plan-tabs.js. */
  .plan-tabs-grid.on-finishes .plan-tabs-media{display:none}
}

/* Structure/material reveal slider (homepage, "Our values" section) - on
   mouse this tracks the cursor just by hovering, no click needed
   (buildcover.com's material comparison, which is what this was asked to
   match); touch has no hover equivalent so it keeps press-and-drag instead.
   Arrow keys work either way. .mr-before is the bare-CLT skeleton of the
   same render (mm-2bed-three-quarter-bluehour-skeleton-*), with callouts.

   No handle circle - buildcover.com's reference has none either, and the
   .mr-handle line alone is enough of a split marker. (An earlier circle+
   arrow handle here got removed outright rather than fixed a third time:
   it needed a grow/shrink hover animation, which meant either fighting the
   translate(-50%,-50%) centring transform for the same CSS property Motion
   was animating - two straight bugs already came from exactly that - or
   permanently carrying the two-element split that worked around it. Simplest
   is not having one.)

   Positioning is transform-only, never left/top - the line moves via
   translateX in px (computed from a width cached on pointerenter/resize,
   not re-read every pointermove), so tracking the cursor never forces
   layout. clip-path is compositor-paint only to begin with; will-change on
   both promotes them to their own layer so a repaint never touches anything
   outside the frame. js/mat-reveal.js additionally batches pointermove into
   one paint per rAF tick - together this is what fixed the original drag
   lag. Mouse hover tracking used to keep a .1s ease-out transition on both
   properties for a "barely-there trailing smoothness" - at normal-to-fast
   mouse speed that read as the line lagging noticeably behind the cursor
   instead, since a new pointermove lands well before the previous 100ms
   transition finishes, so it always chases rather than catches up. Removed
   for mouse too, matching touch/pen's already-instant .is-dragging path -
   both inputs now snap 1:1 with no animated catch-up. */
.mr-frame{position:relative;width:100%;height:100%;overflow:hidden;cursor:ew-resize;touch-action:pan-y}
.mr-frame img{
  position:absolute;inset:0;width:100%;height:100%;object-fit:cover;
  -webkit-user-select:none;user-select:none;pointer-events:none;
}
.mr-before-wrap{
  position:absolute;inset:0;overflow:hidden;clip-path:inset(0 50% 0 0);
  will-change:clip-path;
}
/* Callouts on the skeleton side (Andrew, 2026-09-29: notes on the skeleton
   only - "pulling across to the render hides it all"). Each .mr-call is a
   0x0 anchor at its pin, so Motion can pop it from that point (js/mat-reveal.js
   fades it in once the wipe passes data-x). The tag always hangs left of or
   above the pin, never right, so it is fully uncovered by the time the pin
   is. Dark type on paper - no grey text on this site.
   Drawn as an architect's annotation, not an app tooltip (Radin,
   2026-10-02: "more clean and luxury rather than ai generic"). It was a
   rounded white card on a heavy drop shadow, pointed at by a clay
   map-pin. Now: a square paper label with only a hairline of shadow, keyed
   01-05 in clay like a drawing's legend, the title in the site's tracked
   capitals (the .btn / .hd-spec label style) over a light one-line note;
   the pin is a small dot in a hairline ring, and the leader runs straight
   into the label's corner, flush with its edge. Colours are literal, not
   var(--ink): some scopes on this page redefine --ink as a light tone.
   Then sharpened (Radin, 2026-10-02: "the text and lines are lacking
   colour and blurry"). The blur was mostly the frame's scroll drift and
   cover scale painting all this as a stretched bitmap - both gone, see
   js/home.js and js/mat-reveal.js - and the rest was this file: a
   backdrop blur under the label, a soft shadow round every leader, a
   drop-shadow filter on the pin, half-pixel offsets, and the side labels
   centred by translateY(-50%), which lands their text on half pixels. All
   gone - whole-pixel offsets throughout. For colour: solid paper, the
   ink and the body a weight up (it read grey at 400), and the leaders and
   pins in the brand clay instead of white - clay holds on the pale timber
   and on the dusk sky alike, where white vanished into the wood. */
/* Then larger and on a whole-pixel grid (Radin, 2026-10-02 evening: "the
   text bubbles... the text is not clear clean"). On his 1920x1080 screen
   at 100% scaling a 9.2px tracked title and 11px note were at the edge of
   legible, so the type stepped up (10.4 / 12px), every line-height is a
   whole px, and the pins are rounded to whole px, so no label lands on a
   half pixel. The other half of the fix is in css/home.css: the slider
   images carried will-change:transform, which put them on GPU layers and
   pushed these labels onto a transparent layer of their own - and Chrome
   on Windows drops ClearType for text on such a layer, so it drew soft
   grey-smoothed letters however crisp the CSS. */
.mr-calls{position:absolute;inset:0;pointer-events:none;counter-reset:mr}
/* left: where the pin's feature sits once mat-reveal.js has cropped the
   images to fill a taller frame (--cover; 1 when it hasn't). top needs no
   correction - the crop is only ever off the sides. Both are then rounded
   to whole px where round() is supported; the plain calc() stays as the
   fallback. */
.mr-call{
  position:absolute;left:calc(50% + (var(--x) - 50%) * var(--cover,1));top:var(--y);
  left:round(nearest, calc(50% + (var(--x) - 50%) * var(--cover,1)), 1px);top:round(nearest, var(--y), 1px);
  width:0;height:0;opacity:0;transform-origin:0 0;
}
/* Dot in a hairline ring with clear air between - an outline, since it
   follows the radius and, unlike a spread shadow, leaves the gap empty. */
.mr-call::before{
  content:'';position:absolute;left:-3px;top:-3px;width:6px;height:6px;border-radius:50%;
  background:#c47a5a;outline:1px solid #c47a5a;outline-offset:3px;
}
/* the leader: one clay hairline, the label's right edge carrying it on */
.mr-call::after{content:'';position:absolute;background:#c47a5a}
.mr-call--u::after{left:-1px;bottom:10px;width:1px;height:22px}
.mr-call--d::after{left:-1px;top:10px;width:1px;height:22px}
.mr-call--l::after{right:10px;top:0;width:22px;height:1px}
/* Shadow: one tight contact shadow plus a short soft one - the old 24px
   blur spread a grey haze round each label that read as a smudged edge. */
/* Number + title only, at every size (client, 2026-10-03: "the text looks
   10 times bigger than the actual image for the slider"). With a one-line
   note under each, the labels were 228 x 75px boxes over an ~890px image
   and covered the roof and the base of the house. The notes are still in
   #mrCallsText for screen readers, and the "What you get" list beside the
   slider says the same things at more length. Same crisp paper label,
   11px title (the sitewide floor), just a third of the area. */
/* Then a quieter, smaller label (client, 2026-10-03: "on screen but smaller
   text and luxury looking so it fits in with the style and image"): a
   smoked, see-through chip with a hairline edge instead of a bright paper
   box, finer tracked caps, the number in a lighter clay that holds on the
   dark. Near-white on a dark backing stays crisp at 10px where dark-on-
   light at that size read grey. No backdrop-filter: it would put the label
   on its own GPU layer and lose ClearType again (see the note above). */
.mr-tag{
  position:absolute;display:block;width:max-content;white-space:nowrap;padding:5px 9px 6px;
  background:rgba(22,20,18,.6);color:#f7f5f2;border:1px solid rgba(247,245,242,.28);border-radius:0;
  box-shadow:0 2px 10px rgba(0,0,0,.18);
  font-size:12px;font-weight:500;line-height:18px;letter-spacing:0;text-align:left;
}
.mr-tag b{
  display:block;margin:0;
  font-family:var(--mono);font-size:11px;font-weight:500;line-height:13px;letter-spacing:.2em;text-transform:uppercase;
}
.mr-tag b::before{
  counter-increment:mr;content:counter(mr,decimal-leading-zero);
  margin-right:8px;color:#e0a98c;font-weight:600;letter-spacing:.1em;
}
.mr-tag span{display:none}
/* A title's second half, shown where there's room ("Decking cassette ·
   fast install" - Andrew, 2026-10-11, wanted the fast install on the
   label). Hidden in a narrow frame below, where the full title would run
   off the frame's left edge. */
.mr-tag b i{font-style:normal}
/* right:0 puts the label's right edge on the leader, so the line runs on
   up (or down) as the label's own edge. The side labels hang from the
   leader at their title line - not centred on it, which takes a 50% shift
   and half-pixel text. */
.mr-call--u .mr-tag{right:0;bottom:32px}
.mr-call--d .mr-tag{right:0;top:32px}
.mr-call--l .mr-tag{right:32px;top:-12px}   /* border 1 + padding-top 5 + half the 13px title line */
/* A narrow desktop frame (~680-860px, laptops 1000-1300px wide): shorter
   leaders again, so the roof label clears the frame's top edge - at 30px it
   was cut off there at 1024px wide. */
.mr-frame{container-type:inline-size}
@container (max-width:860px){
  .mr-call--u::after,.mr-call--d::after{height:16px}
  .mr-call--l::after{width:16px}
  .mr-call--u .mr-tag{bottom:26px}
  .mr-call--d .mr-tag{top:26px}
  .mr-call--l .mr-tag{right:26px}
  .mr-tag b i{display:none}
}
/* A phone-width frame is ~360px across: number + title only, shorter leaders. */
@media (max-width:700px){
  .mr-tag{padding:3px 6px 4px}
  .mr-tag b{margin:0;font-size:9px;line-height:12px;letter-spacing:.14em}
  .mr-tag b::before{margin-right:5px}
  .mr-tag span{display:none}
  .mr-call::before{left:-2px;top:-2px;width:4px;height:4px;outline-offset:2px}
  .mr-call--u::after,.mr-call--d::after{height:14px;bottom:7px}
  .mr-call--d::after{top:7px;bottom:auto}
  .mr-call--l::after{width:9px;right:7px}
  .mr-call--u .mr-tag{bottom:21px}
  .mr-call--d .mr-tag{top:21px}
  .mr-call--l .mr-tag{right:16px;top:-10px}   /* a short side leader, so 02 clears the frame's left edge */
  /* A longer drop for one label that would otherwise clip its neighbour's
     corner: on a 360px frame the screw piles label sat 3px into the
     decking cassette label beside it, and neither pin can move far
     (one pile in view; the joists end where the CLT floor starts). */
  .mr-call--long.mr-call--d::after{height:21px}
  .mr-call--long.mr-call--d .mr-tag{top:28px}
}
/* Labels on the left half hang RIGHT of their pin instead (Radin,
   2026-10-12: the labels were "all crammed into the mid section" - with
   every label hanging left, no pin could sit near the left edge). Its left
   edge sits on the leader, the mirror of right:0 above. Such a label isn't
   whole until the wipe is past its right edge, so js/mat-reveal.js waits
   for that before fading it in. Three classes, so it beats the per-size
   right: offsets above whatever their order. */
.mr-call.mr-call--right .mr-tag{right:auto;left:-1px}
/* A title's first half that only a phone drops ("High-spec insulation" ->
   "Insulation"), so that label fits its corner. */
.mr-tag b em{font-style:normal}
/* Phones: each callout's own place (Radin, 2026-10-21: "neaten the notes
   on the slider, they are all crammed together in the middle, space it
   out"). On a 360-430px frame the six labels stacked down the middle of
   the house; here they go out to its edges instead - top corners over the
   sky and the tree, mid left and right, the bottom over the grass - with
   longer leaders back to their pins. Set per callout in index.html: --mx/
   --my the phone pin, --lead the pin-to-label distance (cqw: the phone
   frame is always 16:9, so a share of its width is a fixed share of its
   height too), mr-m--u/--d which way the leader runs, mr-m--r a label
   hanging right of its pin. js/mat-reveal.js reads where each lands, so
   the fade-in still waits for the wipe to clear the whole label. */
@media (max-width:700px){
  .mr-call.mr-m{left:var(--mx);top:var(--my);left:round(nearest,var(--mx),1px);top:round(nearest,var(--my),1px)}
  .mr-call.mr-m::after{left:-1px;right:auto;width:1px;height:calc(var(--lead) - 7px)}
  .mr-call.mr-m--u::after{top:auto;bottom:7px}
  .mr-call.mr-m--d::after{top:7px;bottom:auto}
  .mr-call.mr-m .mr-tag{top:auto;bottom:auto;left:auto;right:0}
  .mr-call.mr-m--u .mr-tag{bottom:var(--lead)}
  .mr-call.mr-m--d .mr-tag{top:var(--lead)}
  .mr-call.mr-m--r .mr-tag{right:auto;left:-1px}
  .mr-tag b em{display:none}
}
/* The smallest phones (320-340px): tighter tracking, so the wide "Decking
   cassette" label clears the walls label beside it on the 2026-10-27
   professional render's slider. */
@media (max-width:340px){
  .mr-tag b{letter-spacing:.06em}
}
.sr-only{position:absolute;width:1px;height:1px;padding:0;margin:-1px;overflow:hidden;clip:rect(0 0 0 0);white-space:nowrap;border:0}
.mr-handle{
  position:absolute;top:0;bottom:0;left:calc(50% - 1.5px);width:3px;
  background:rgba(255,255,255,.9);pointer-events:none;
  will-change:transform;
}
.mr-frame:focus-visible{outline:2px solid var(--clay);outline-offset:-2px}

.section{padding:clamp(36.8px,6.4vh,72px) 0;border-top:1px solid var(--line)}
/* the page head already draws the rule, so the first section does not need a
   full pad on top of the head's margin */
.page-head + .section{padding-top:clamp(19.2px,2.8vh,35.2px)}
.section:first-of-type{border-top:0}
.section h2{
  font-family:var(--display);font-weight:300;letter-spacing:-.01em;
  font-size:clamp(19.2px,2.4vw,30.4px);line-height:1.1;margin:0 0 19.2px;
}
.section p{color:var(--ink-2);line-height:1.85;max-width:62ch;margin:0 0 14.4px}
/* 62ch is the right measure for a column of reading, but under a heading that
   spans the page it leaves the right half empty. .wide lets a paragraph run
   the full width where it is introducing what follows rather than being the
   thing you settle in to read. */
.section p.wide{max-width:none}
.section p strong{color:var(--ink);font-weight:500}

/* ------------------------------------------------------------ home cards */
.card-grid{display:grid;grid-template-columns:repeat(3,1fr);gap:1.6px;background:var(--line)}
.card{background:var(--bg);display:flex;flex-direction:column;transition:background .3s;border-radius:16px;overflow:hidden}
.card:hover{background:var(--bg-2)}
.card-media{aspect-ratio:16/11;overflow:hidden;background:var(--bg-2);position:relative}
.card-media picture{display:block;width:100%;height:100%}
.card-media img{width:100%;height:100%;object-fit:cover;transition:transform 1s cubic-bezier(.16,1,.3,1)}
.card:hover .card-media img{transform:scale(1.04)}
.card-media.pending{
  display:flex;align-items:center;justify-content:center;color:var(--ink);
  background:repeating-linear-gradient(45deg,var(--bg-2),var(--bg-2) 9px,var(--sand) 9px,var(--sand) 18px);
}
.card-body{padding:17.6px 17.6px 20.8px;display:flex;flex-direction:column;flex:1}
.card-head{display:flex;justify-content:space-between;align-items:baseline;gap:9.6px;margin-bottom:6.4px}
.card-head h3{font-family:var(--display);font-weight:600;letter-spacing:-.02em;font-size:17.6px;margin:0}
.card-head .mono{color:var(--ink-3)}
.card-body p{font-size:11.2px;line-height:1.7;color:var(--ink-2);margin:0 0 12.8px}
.card-meta{list-style:none;padding:9.6px 0 0;margin:auto 0 0;border-top:1px solid var(--line)}
.card-meta li{font-family:var(--mono);font-size:11px;letter-spacing:.14em;text-transform:uppercase;color:var(--ink-3);line-height:2.1}
@media (max-width:900px){.card-grid{grid-template-columns:1fr}}

/* ------------------------------------------------------------- drawings */
/* Full-bleed render band. Used where a page earns a photograph rather than a
   drawing - the 2560 front elevation is the only render we have at that size. */
.render-band{margin:0 0 clamp(27.2px,4.8vh,51.2px);overflow:hidden;background:var(--bg-2);border-radius:22px}
.render-band picture{display:block}
.render-band img{width:100%;height:auto;display:block}
.render-cap{
  display:flex;justify-content:space-between;gap:12.8px;flex-wrap:wrap;
  font-family:var(--mono);font-size:11px;letter-spacing:.18em;text-transform:uppercase;
  color:var(--ink-3);margin-top:8px;
}

/* This plate was a stark light-on-dark contrast before the repaint - it's
   paper-on-paper now, so a border does the job the old dark surround used to
   do: marking where the drawing sheet ends and the page begins. */
/* Deliberately still square, unlike .render-band/.card/.ix-media below. Those
   are photographs and get the softer rounded-card treatment; this holds a
   real CAD sheet - a rounded corner on a technical drawing reads as a sticker,
   not a document. Square is what marks it as the actual drawing set rather
   than another marketing image. */
.plate{background:#fbfaf7;border:1px solid var(--line);padding:clamp(11.2px,1.6vw,20.8px);margin:0}
.plate img{width:100%;height:auto}
.plate-cap{
  display:flex;justify-content:space-between;gap:12.8px;padding:9.6px 1.6px 0;
  font-family:var(--mono);font-size:11px;letter-spacing:.16em;text-transform:uppercase;color:var(--ink-3);
}
.plate-wrap{margin:0 0 24px}


/* --------------------------------------------------------------- specs */
.spec-list{margin:0;border-top:1px solid var(--line)}
/* Direct-child combinator, not a plain descendant selector: the Finishes
   tab nests a <div class="finish-swatches"> inside its <dd> (see
   js/plan-tabs.js's mountFinishSwatches()), and a bare ".spec-list div"
   match forced that nested div into this same 150px/1fr grid too, wrapping
   the third swatch onto its own row instead of sitting in one flex line. */
.spec-list>div{display:grid;grid-template-columns:150px 1fr;gap:16px;padding:13px 0;border-bottom:1px solid var(--line)}
/* Literal black, not var(--ink) (#2b2b2a) - the charcoal read as grey at
   this size and weight, and the brief asked for the text to be black. */
.spec-list dt{color:#000;font-family:var(--mono);font-size:11px;letter-spacing:.16em;text-transform:uppercase;margin:0}
.spec-list dd{margin:0;font-size:13px;line-height:1.7;color:#000}
.spec-list + .btn{margin-top:24px}
@media (max-width:700px){.spec-list>div{grid-template-columns:1fr;gap:3.2px}}

/* Dimensions tab - modelled on dinesen.com's "Dimensions and prices" tab
   (grouped subheadings over tight inline "Label — value" lines), not the
   150px/1fr two-column grid the other tabs use above: that grid reads well
   for a handful of one-line specs, but the Dimensions copy runs longer
   ("12.95 m x 9.6 m - 800mm eave, falling 1deg south") and wrapped awkwardly
   in a fixed 1fr value column next to a fixed label column. */
.dim-groups{display:flex;flex-direction:column;gap:24px}
.dim-group h3{
  font-family:var(--display);font-weight:600;font-size:19.2px;
  letter-spacing:-.01em;color:var(--ink);margin:0 0 9.6px;
}
.dim-rows{display:flex;flex-direction:column;gap:3.2px}
.dim-row{margin:0;font-size:15.2px;line-height:1.85;color:var(--ink-2)}
.dim-row b{font-weight:600;color:var(--ink)}
/* Mirrors the reference's own thin rule before its closing disclaimer line -
   .plan-tab-note's shared margin-top still applies, this only adds the rule. */
#panel-dimensions p.plan-tab-note{padding-top:16px;border-top:1px solid var(--line)}
/* "Planning and site suitability" under the Layout tab's area note (Andrew's
   brief 26 Oct, two-bedroom.html). Reuses .dim-group's h3 and .plan-tab-note's
   type, with the same thin rule as the Dimensions disclaimer above. The p is
   its div's first p, so #panel-layout's :first-of-type rule (margin 0 /
   20.8px) would catch it - this resets it (same specificity, later in file). */
.plan-planning{margin-top:24px;padding-top:20px;border-top:1px solid var(--line)}
#panel-layout .plan-planning p.plan-tab-note{margin:0}
/* Toggled by js/plan-tabs.js only while Dimensions is the active tab - the
   reference this tab is modelled on has no photo at all, just text, so the
   media column is dropped rather than shrunk. Collapsing the GRID to a
   single track, not just hiding the media child, matters: the grid's own
   two-column template (minmax(280px,460px) 1fr) reserves that second
   track's width regardless of whether anything sits in it, so without this
   the text stayed pinned to its narrow column with the photo just gone,
   leaving the same dead space the photo used to fill. Finishes does NOT use
   this class even though it also has no default photo - see the no-media
   comment in plan-tabs.js's activate() for why a grid collapse specifically
   breaks Finishes' hover preview. */
.plan-tabs-grid.no-media{grid-template-columns:1fr}
.plan-tabs-grid.no-media .plan-tabs-media{display:none}
.plan-tabs-grid.no-media .plan-tabs-body{max-width:760px}

/* Dimensions tab (2026-10-11): the line-drawing render with three
   measurements drawn on it - deck length, deck depth, overall height. The
   box takes the image's own shape on this tab so nothing is cropped and the
   SVG lines (same aspect, viewBox 100 x 55.81) land where they were measured.
   Numbers are per home; see each page's .tab-dims. */
.plan-tabs-grid.on-dims .plan-tabs-media{aspect-ratio:2752/1536;align-self:start}
.tab-dims{position:absolute;inset:0;opacity:0;pointer-events:none;transition:opacity .4s ease}
.tab-dims.is-on{opacity:1}
.tab-dims picture,.tab-dims img{display:block;width:100%;height:100%;object-fit:cover}
.dims-svg{position:absolute;inset:0;width:100%;height:100%;overflow:visible}
.dims-svg line{stroke:var(--clay);stroke-width:1.25px;vector-effect:non-scaling-stroke;stroke-linecap:round}
.dims-svg line.ext{stroke-width:1px;stroke-dasharray:2 3}
/* Architect's convention: each figure is written along its own line (--rot,
   set per tag from the line's on-screen angle) and sits in a gap in it - a
   soft page-colour chip with no border, so the label reads as part of the
   line rather than a box stuck on the picture. */
.dim-tag{
  position:absolute;transform:translate(-50%,-50%) rotate(var(--rot,0deg));white-space:nowrap;
  padding:2px 7px;background:rgba(247,245,242,.94);border-radius:2px;
  font-family:var(--sans);font-size:12px;font-weight:500;line-height:1.3;letter-spacing:.02em;color:var(--ink);
}
.dim-shown{
  position:absolute;right:12px;top:12px;padding:3px 8px;background:rgba(247,245,242,.9);
  font-family:var(--sans);font-size:11px;font-weight:500;letter-spacing:.02em;color:var(--ink);
}
@media (max-width:900px){
  .dim-tag{font-size:11px;padding:1px 5px}
}
/* Phones: numbers only - "3.6 m high" was as long as the height line itself
   on a 390px screen. The lines still say what each figure measures. */
@media (max-width:600px){
  .dim-w{display:none}
  .dim-shown{font-size:11px;padding:2px 6px;top:8px;right:8px}
}

/* Finish swatches on the plan-tabs Finishes panel - see js/plan-tabs.js's
   mountFinishes(). Colour + count come straight from spec/products.json's
   options.* so a placeholder slot (dashed ring, dimmed) turns into a real,
   solid swatch the moment Andrew names it - nothing here is invented. */
.finish-swatches{display:flex;gap:9.6px;margin-bottom:9.6px}
.finish-swatch{
  width:30px;height:30px;border-radius:50%;padding:0;cursor:pointer;
  border:2px solid transparent;box-shadow:0 0 0 1px var(--line) inset;
  transition:border-color .2s,transform .15s;
}
.finish-swatch:hover{transform:translateY(-1px)}
.finish-swatch.is-on{border-color:var(--clay)}
.finish-swatch.is-tbc{opacity:.5;border-style:dashed}
.finish-swatch:focus-visible{outline:2px solid var(--clay);outline-offset:2px}
.finish-swatch-label{display:block;font-size:13.6px;line-height:1.6;color:var(--ink-3)}
/* Andrew's selections register (spec/selections.json, 2026-10-26): up to
   five choices a row, so the swatches wrap rather than overflow on phones;
   a category's own note (which rooms it covers) under the chosen name. */
.finish-swatches{flex-wrap:wrap}
.finish-cat-note{display:block;font-size:12.8px;line-height:1.6;color:var(--ink-3);margin-top:1.6px}
/* The supplier credit, or "Illustrative image" (no exact visual yet), on the
   shared photo box - fades with the photo it belongs to. */
.finish-credit{
  position:absolute;left:12px;bottom:12px;padding:3px 8px;border-radius:2px;
  background:rgba(247,245,242,.9);color:var(--ink);
  font-family:var(--sans);font-size:11px;font-weight:500;letter-spacing:.02em;
  opacity:0;pointer-events:none;transition:opacity .4s ease;
}
.finish-credit.is-on{opacity:1}
.finish-credit:empty{display:none}
/* Stacked only: each row's own photo under its label (the shared box is
   hidden there, see the max-width:900px block above). Wide screens never
   render it, and its img is lazy, so they never download it either. */
/* Wide screens: the shared box rides alongside the eight rows, so the photo
   for a swatch near the bottom of the list is still in view. */
@media (min-width:901px){
  .plan-tabs-grid.on-finishes .plan-tabs-media{position:sticky;top:132px;align-self:start}
}
.finish-row-photo{display:none}
@media (max-width:900px){
  .finish-row-photo{display:block;position:relative;margin:12px 0 4px;aspect-ratio:16/10;border-radius:14px;overflow:hidden;background:var(--bg-2)}
  .finish-row-photo[hidden]{display:none}
  .finish-row-photo img{display:block;width:100%;height:100%;object-fit:cover}
  .finish-row-photo figcaption{
    position:absolute;left:8px;bottom:8px;padding:2px 7px;border-radius:2px;
    background:rgba(247,245,242,.9);color:var(--ink);
    font-family:var(--sans);font-size:11px;font-weight:500;letter-spacing:.02em;
  }
  .finish-row-photo figcaption:empty{display:none}
}

/* ----------------------------------------------------------------- faq */
.faq{border-top:1px solid var(--line);margin-top:6.4px}
/* the page head already draws a rule; the list's own top rule 64px below
   it left a banded strip of nothing between the two. */
.page-head + .faq{border-top:0}
.faq details{border-bottom:1px solid var(--line)}
.faq summary{
  cursor:pointer;list-style:none;padding:16px 32px 16px 0;position:relative;
  font-family:var(--display);font-weight:500;font-size:clamp(12.8px,1.36vw,16px);
  letter-spacing:-.012em;color:var(--ink);
}
.faq summary::-webkit-details-marker{display:none}
.faq summary::after{
  content:"+";position:absolute;right:6px;top:50%;transform:translateY(-50%);
  font-family:var(--mono);font-size:13.6px;color:var(--ink-3);transition:transform .3s,color .3s;
}
.faq details[open] summary::after{transform:translateY(-50%) rotate(45deg);color:var(--ink)}
.faq summary:hover{color:var(--ink)}
/* Full width of the list, not a 70ch column: opened, a short answer sat as
   a narrow block with the rest of the row empty beside it. */
.faq .answer{padding:0 0 17.6px;max-width:none}
/* Answers were 15.5px Regular at 90% ink. Next to a 500-weight question
   that reads as a caption, not an answer - so up a step in size and
   weight, and full ink. The tracking stays matched to the summary. */
.faq .answer p{color:var(--ink);font-weight:500;line-height:1.8;margin:0 0 11.2px;font-size:15.2px;letter-spacing:-.006em}
.faq .answer p:last-child{margin-bottom:0}
/* Andrew's 3 Nov 2026: the list closes on the offer, not a question - his
   closing line plus the hero's "Check your property" button (same .btn ghost
   lg, same #assess hook, so js/enquiry.js opens the form in place). */
.faq-cta{
  display:flex;align-items:center;justify-content:space-between;gap:24px;
  flex-wrap:wrap;padding:clamp(25.6px,3.6vh,35.2px) 0 0;
}
.faq-cta-title{
  font-family:var(--display);font-weight:500;font-size:clamp(17.6px,1.7vw,21.6px);
  letter-spacing:-.012em;color:var(--ink);margin:0;
}
@media (max-width:600px){
  .faq-cta{display:block}
  .faq-cta .btn{margin-top:16px}
}

/* ---------------------------------------------------------- steps/list */
/* .steps now lives in home.css, which every page here also loads: this file
   held a character-for-character copy of the homepage timeline. */

/* --------------------------------------------------------- contact/CTA */
.tail{
  border-top:1px solid var(--line);margin-top:clamp(40px,6.4vh,72px);
  padding:clamp(40px,7.2vh,80px) 0;display:flex;justify-content:space-between;
  align-items:center;gap:24px;flex-wrap:wrap;
}
/* A tail that is only its call to action. space-between with one child pins
   it hard left against a full-width rule, which reads as a stray button. */
.tail-cta{justify-content:center;padding:clamp(32px,5.6vh,60.8px) 0}
.tail h2{font-family:var(--display);font-weight:600;letter-spacing:-.026em;font-size:clamp(19.2px,2.72vw,33.6px);line-height:1.1;margin:0}

.contact-grid{display:grid;grid-template-columns:repeat(3,1fr);gap:1.6px;background:var(--line);margin-top:6.4px}
.contact-grid div{background:var(--bg);padding:19.2px 17.6px;display:flex;flex-direction:column;gap:7.2px}
.contact-grid .mono{color:#000}
.contact-grid a,.contact-grid span:not(.mono){font-size:13.6px;color:#000}
.contact-grid a:hover{color:var(--clay-t)}
@media (max-width:760px){.contact-grid{grid-template-columns:1fr}}

/* The configuration carried over from the configurator. Reads as the
   configurator's own spec sheet rather than as another form field, because
   that is what it is - the visitor already built it, and the job here is to
   show it came through, not to ask them to check it again. */
.spec-panel{border:1px solid var(--line);border-radius:16px;background:var(--bg-2);
  padding:11.2px 12.8px 12.8px;margin:0 0 20.8px}
.spec-panel-head{display:flex;justify-content:space-between;align-items:baseline;gap:12.8px;margin-bottom:8px}
/* --clay-t on the panel's --bg-2: 5.05:1 (was sage, retired - see home.css) */
.spec-panel-head .mono{color:var(--clay-t)}
.spec-panel-head a{font-size:11px;color:var(--ink-2);white-space:nowrap}
.spec-panel-head a:hover{color:var(--ink)}
.spec-sum{margin:0;display:grid;grid-template-columns:auto minmax(0,1fr);gap:5.6px 14.4px}
.spec-sum dt{font-family:var(--mono);font-size:11px;letter-spacing:.16em;text-transform:uppercase;
  color:var(--clay-t);margin:0;padding-top:2.4px;white-space:nowrap}
.spec-sum dd{margin:0;font-size:11.6px;line-height:1.5;color:var(--ink)}
.spec-full{margin-top:11.2px;border-top:1px solid var(--line);padding-top:9.6px}
.spec-full[hidden]{display:none}
.spec-full summary{cursor:pointer;list-style:none;font-size:11px;color:var(--ink-3);
  display:inline-flex;align-items:center;gap:5.6px;transition:color .2s}
.spec-full summary::-webkit-details-marker{display:none}
.spec-full summary::before{content:"+";font-family:var(--mono);font-size:11px;line-height:1}
.spec-full[open] summary::before{content:"2"}
.spec-full summary:hover{color:var(--ink)}
.spec-full pre{margin-top:9.6px}
.spec-panel pre{
  font-family:var(--mono);font-size:11px;line-height:1.75;color:var(--ink-2);
  background:#fbfaf7;border:1px solid var(--line);border-radius:12px;
  padding:11.2px;margin:0;overflow-x:auto;white-space:pre;max-height:230px;
}

/* Interior pages never sit under a full-bleed hero, so .nav can stay
   solid rather than the hero page's photo-aware transparent treatment - but
   the actual backing colour is .nav-plate's job now (added sitewide so the
   nav reads the same over any content, home.html's dark hero included).
   This hardcoded near-black background predates that and would paint a dark
   bar under the light plate on every interior page. */
/* The rule under the nav is the plate's now (css/home.css), which only
   paints once you scroll past the opening - so a permanent border here would
   double it, and would draw a line under a bar that is transparent. */
body.interior{padding-top:0}
/* about.html is one line of text, so the footer landed halfway up the window
   with bare paper under it. A column flex body with main taking the slack
   pins the footer to the bottom of a short page and changes nothing on a page
   that already fills the screen. .grain and .nav are position:fixed, so they
   are out of flow and unaffected. */
body.interior{min-height:100svh;display:flex;flex-direction:column}
body.interior > main{flex:1 0 auto}

/* 404 */
.oops{min-height:70svh;display:flex;flex-direction:column;justify-content:center;gap:14.4px}
.oops b{font-family:var(--display);font-weight:300;font-size:clamp(48px,9.6vw,120px);line-height:1;letter-spacing:-.04em}
.oops h1{margin:0;font:inherit}

/* ==================================================== five-homes display
   Full-bleed split-panel carousel modelled on a client-supplied reference
   (Dinesen's wood-species showcase): one home per slide, a large lifestyle
   photo on the left and a narrower accent panel on the right carrying the
   name/spec/CTA plus the counter and prev/next arrows. See index.html's
   comment on this section for why the right panel is a flat colour rather
   than a material-texture shot, and js/home-display.js for the interaction
   logic. */
.home-display{width:100%;overflow:hidden;background:var(--bg)}
/* The paper band + heading between the hero and the first slide is gone
   (Radin, 2026-10-04: it read as a cheap spacer). The h2 stays in the DOM
   for the section's aria-labelledby, clipped invisible. The hero join is
   normal flow at every width: the homes section simply sits below the hero
   until the scroll reaches it (desktop since 2026-10-05, "on my PC I want
   it all to be still"; phones since 2026-10-28, when the pinned-cover
   transition was removed). */
.hd-head{position:absolute;width:1px;height:1px;margin:-1px;padding:0;overflow:hidden;clip:rect(0 0 0 0);clip-path:inset(50%);white-space:nowrap;border:0}
/* Phone: no longer pulled up 100svh over a pinned hero - plain scroll since
   2026-10-28 (home.css). */
@media (max-width:700px){
  .home-display{position:relative;z-index:2}
}
/* Sized to the photo, not a viewport fraction. All five renders share the
   same 16:9 frame (Maison 60's is the architect's own VER.1.0 render since
   2026-09-30, 16:9 like the rest), and the photo column is 65% of this
   track's width - so an aspect-ratio of 65% of 16:9, inverted, makes the
   photo column exactly 16:9 itself. cover then never has anything to crop
   or letterbox: the box IS the image's own shape. Desktop only - see the
   aspect-ratio:auto under 900px below.
   max-width:100% because the 420px floor carries through the ratio as a
   minimum WIDTH: 420 x 2.735 = 1149px, so from 901 to 1148px the track ran
   past the screen and overflow:hidden cut off the panel's copy and next
   arrow (same failure as the phone one below). Capped, the floor just makes
   the photo box a little squarer there and cover trims its sides. */
.hd-track{position:relative;aspect-ratio:2.735/1;min-height:420px;max-width:100%;background:#121110}
/* Crossfade, not a slide - checked the actual reference site (dinesen.com)
   rather than guessing from the screenshot: every species panel sits
   absolutely stacked in the same spot, and "next" dissolves the outgoing
   one out while the incoming one dissolves in, with no sideways motion at
   all. Was a translateX push on .hd-track before; that's gone, along with
   the transition living there - it's per-slide opacity now. */
/* .5s ease-in-out, not .8s ease - measured the reference frame-by-frame
   (requestAnimationFrame, sampling computed opacity) rather than eyeballing
   it: its fade completes in ~520ms on a curve that matches jQuery's
   "swing" easing almost exactly (verified against the swing formula at
   several points), which is CSS ease-in-out's closest standard equivalent.
   .8s ease measured ~60% slower with a front-loaded curve - close enough to
   read as "a fade" but a visibly different pace side by side. */
.hd-slide{
  position:absolute;inset:0;display:flex;opacity:0;visibility:hidden;pointer-events:none;
  transition:opacity .5s ease-in-out,visibility .5s;
}
.hd-slide.active{opacity:1;visibility:visible;pointer-events:auto}
.hd-photo{flex:0 0 65%;height:100%;overflow:hidden}
/* Back to cover - contain filled the leftover space with the section's dark
   background as letterbox bars, which read as a bug rather than a frame.
   cover crops instead, but never leaves any bare space, on any of the five
   renders' aspect ratios. */
.hd-photo img{width:100%;height:100%;object-fit:cover;display:block}
/* Per-slide crop, for where centred cuts the thing that names the home.
   On a phone the photo box is close to square, so cover keeps only the
   middle ~60% of a 16:9 render; the Sky's circular skylight sits in its
   render's left third and lost half its circle to the frame edge. Leaning
   the crop left keeps the whole skylight and the V-strut in. The other four
   read fine centred. */
.hd-photo img.hd-crop-left{object-position:30% 50%}
.hd-panel{
  position:relative;flex:0 0 35%;height:100%;overflow:hidden;
  display:flex;flex-direction:column;
  /* Clay, not the olive #74785d this was (Andrew, call 2026-09-29: "that
     sage on the right... change it to the clay colour" - sage is AJP's, and
     clay is Modular Maison's; see the note on :root in home.css). This ran
     as --clay-t (a darker, text-safe shade) rather than plain --clay for a
     while, because white text on plain --clay measures 3.34:1 - under AA's
     4.5:1 for .hd-desc/.hd-spec, though .hd-title's larger size only needs
     3:1 and clears it. --clay-t read as a duller rust than the brand board's
     actual clay swatch (#C47A5A) though, so this is back to plain --clay for
     an exact match, with .hd-content's text-shadow below doing the work of
     keeping the smaller text legible instead. */
  background:var(--clay);
}
/* Client call 2026-09-29: the block is centered again. flex-start with a
   fixed 7.5rem top offset (the previous state) kept every slide's title at
   the same Y regardless of how many lines its description wrapped to, but
   on the taller panels the text read as hugging the top edge. Centering
   puts title + description + spec + button in the vertical middle of the
   panel; Maison 60's 3-line description shifts its block's midpoint a few
   px below the 2-line slides', which the client preferred over the
   top-anchored look. Symmetric padding floors the block off the edges
   (the tighter 32px all round crowded it). .hd-nav is absolute at the
   panel's bottom (see below) so the centering ignores the counter row -
   otherwise the block centered in the space ABOVE it, which on these
   panels is the same ~120px-from-top position the old top offset had and
   the change was invisible. */
/* text-shadow inherits to every child below (title, desc, spec, button) -
   same recipe as the nav wordmark's shadow over its photo (css/home.css),
   here making up for plain --clay's thinner contrast against white. */
.hd-content{
  position:relative;flex:1;display:flex;flex-direction:column;justify-content:center;align-items:flex-start;padding:4.8rem 3rem;
  text-shadow:0 1px 3px rgba(0,0,0,.35);
}
/* No eyebrow chip - the reference has nothing above the title, only the
   bottom counter marks position in the set. */
.hd-title{
  margin:0;color:#fff;font-family:var(--display);font-weight:300;
  /* Came down with the sitewide heading reduction (2026-09-29) - at 40px
     these card titles outranked the section headings they sit under. */
  font-size:clamp(27.2px,2.4vw,32px);line-height:1.05;letter-spacing:-.01em;
}
/* No ch cap - the panel's own padded width is the real constraint (a fixed
   character count read as a narrow block with dead panel width beside it),
   so the line should just run edge to edge of the column instead. */
.hd-desc{margin:18px 0 0;max-width:none;color:#fff;font-size:15.7px;line-height:1.6}
/* Real plan facts, not filler - the panel's own padded height left a gap
   between the description and the bottom nav row, and bed/bath/area is
   the actual next thing someone wants after reading the description,
   already the pattern this site uses everywhere else (spec chips, the
   configurator's spec panel).
   Same type as .hd-desc above it since 2026-10-14 (Radin: the bottom
   sentence's font should match the top one, and be a bit more spaced out).
   It was 11px tracked caps (.mono), which read as a different voice from
   the description. Same size and face now, with looser lines and a little
   more room above. */
.hd-spec{margin:20px 0 0;color:#fff;font-size:15.7px;line-height:1.9}
/* Up to 1286px the track sits on (or near) its 420px floor, which was
   already too short for Maison 60's three-line description: the Explore
   button overlapped the counter row by up to 59px at 901. A 470px floor -
   1286 is where 2.735:1 reaches 470 by itself, so there is no step - and
   tighter padding fit every card. */
@media (min-width:901px) and (max-width:1286px){
  .hd-track{min-height:470px}
  .hd-content{padding:40px 32px 88px}
}
/* Ghost/outline button, matching this site's existing .btn.ghost treatment
   for a button sitting on a photo (see css/home.css's .hero .btn.ghost). */
.hd-btn{
  display:inline-flex;align-items:center;gap:8px;
  margin-top:28px;padding:14.4px 25.6px;border-radius:0;
  background:transparent;color:#fff;border:1px solid rgba(255,255,255,.4);
  font-family:var(--mono);font-size:11px;font-weight:600;letter-spacing:.18em;text-transform:uppercase;
  text-decoration:none;transition:background .25s,border-color .25s;
}
.hd-btn:hover{background:rgba(255,255,255,.1);border-color:rgba(255,255,255,.6)}
.hd-nav{position:absolute;left:0;right:0;bottom:0;display:flex;align-items:center;justify-content:space-between;padding:0 64px 32px}
/* Full white, total included. At 65% white the " / 5" measured 3.6:1 on
   the clay (2.9:1 on the old olive) - under AA for 10.4px type, and exactly
   the hand-rolled translucent "secondary" text the note on :root in
   home.css rules out. So the current number no longer needs a colour rule
   of its own (.hd-counter-n stays in the markup, unstyled). */
.hd-counter{color:#fff;font-size:11px;letter-spacing:.1em}
.hd-arrows{display:flex;gap:10px}
/* Bare chevron, no pill - matches the reference (Dinesen): the arrow reads
   as a control floating on the image itself, not a button someone dropped
   on top of it. The hit target stays the same 38.4px box, just invisible. */
.hd-arrow{
  width:38.4px;height:38.4px;display:flex;align-items:center;justify-content:center;
  background:transparent;color:#fff;border:none;
  cursor:pointer;transition:transform .2s,opacity .2s;
  filter:drop-shadow(0 1px 2px rgba(0,0,0,.35));
}
.hd-arrow:hover{opacity:.65}
.hd-arrow:active{transform:translateY(1px)}
.hd-arrow:focus-visible{outline:2px solid #fff;outline-offset:2px}
/* ...and padded out to 44px to a thumb - see "invisible tap targets" in
   home.css. 2.8px a side, well inside the 10px gap between the two. */
.hd-arrow{position:relative}
.hd-arrow::after{content:"";position:absolute;inset:min(0px,calc(50% - 22px))}
@media (max-width:900px){
  /* Was height:auto - fine when slides sat in normal flow and only one was
     ever rendered "tall" at a time, but absolutely-positioned slides (the
     crossfade) don't contribute to a parent's auto height at all, so the
     track would collapse to 0. It had an explicit height here for that
     (clamp(760px,140vw,880px)) until 2026-10-03; the slides now stack in
     one grid cell instead, which keeps the crossfade AND gives the track a
     real auto height - see below. */
  /* aspect-ratio:auto is the fix for Andrew's "not really a shot of the
     actual house" on phones (call 2026-09-29). With the desktop ratio still
     set, this explicit height made the ratio size the WIDTH instead:
     760px x 2.735 = a 2078px-wide track in a 390px screen. .home-display's
     overflow:hidden clipped it, so a phone saw only the left fifth of each
     slide - garden and a V-strut, zoomed in - with the description running
     off the right edge. */
  /* The whole house, every slide (Radin, 2026-10-03: "make sure you can see
     the whole house... the right side is cut out"). The photo box was 42vh
     tall - near-square on a phone (390x354) - so cover kept only the middle
     ~60% of each 16:9 render, and four of the five houses run from ~2% to
     ~98% of their frame: the V-strut and the far end were both cut. The box
     is 16:9 now, the renders' own shape, so cover has nothing to crop.
     With a shorter photo the fixed track height above (760-880px) would
     have left a tall empty band of clay, so the track sizes itself instead:
     the slides stack in one grid cell (grid-area 1/1) rather than being
     absolutely positioned, which keeps the crossfade - they still overlap
     exactly - while the cell, and so the track, is as tall as the tallest
     slide. Hidden slides keep their layout (visibility, not display), so
     the height doesn't change from slide to slide. */
  .hd-track{display:grid;height:auto;min-height:0;aspect-ratio:auto}
  .hd-slide{position:relative;inset:auto;grid-area:1/1;flex-direction:column}
  .hd-photo{flex:0 0 auto;height:auto;aspect-ratio:16/9}
  /* flex:1, not flex:0 0 auto - auto sizes to the panel's own content
     height, which on the longest slide (Maison 60's desc) overflowed
     straight past the track's fixed height instead of respecting it,
     since the track can't grow (it's position:absolute inset:0 now, for
     the crossfade). flex:1 forces the panel to fill exactly what's left
     after the photo, whatever that is, so it can never push past the box. */
  .hd-panel{flex:1}
  /* Bottom padding clears the counter/arrows row, which is absolute at the
     panel's foot - with the track sized to its content, nothing else keeps
     the Explore button off it (Maison 60's was 8px from the arrows). */
  .hd-content{padding:32px 32px 100px}
  .hd-desc{max-width:none}
  .hd-nav{padding:0 32px 28px}
  /* 15% shorter (Radin, 2026-10-21: "the explore homes section is a bit big,
     the orange part, make it 15% smaller") - 410 -> 349px at 390 wide. The
     tallest slide sets every slide's height, so this is measured on it.
     Spacing only - padding, the gaps between title, text and button, the
     clear run above the counter row. Smaller type was tried and overshot
     unevenly (17% at 390, 23% at 768 - lines stop wrapping), so the text,
     and the Explore button (a tap target), keep their size. */
  .hd-content{padding:26px 32px 76px}
  .hd-nav{padding:0 32px 20px}
  .hd-desc{margin-top:12px}
  .hd-spec{margin-top:12px;line-height:1.6}
  .hd-btn{margin-top:20px}
}
@media (prefers-reduced-motion:reduce){
  .hd-slide{transition:none}
}

/* ============================================================ index system
   From the architecture-portfolio reference the client supplied: giant light
   numerals as the primary navigation, a slash-and-stop typographic tic, thin
   rules, and a ruled metadata column instead of prose where the content is
   really a spec. */

/* --- page index numeral, sits beside the page title */
.page-head{position:relative}
/* The giant /slug. numeral is gone from every page. It came from the
   portfolio reference, but it restated the page title in a lighter weight
   directly above the page title, and it was the widest thing in the head. */

/* --- contents list: .01 / title / meta / thumb */
.index{border-top:1px solid var(--line);margin:0 0 clamp(32px,5.6vh,64px)}
/* the page head already draws a rule; two of them 60px apart reads as a gap */
.page-head + .index{border-top:0;margin-top:calc(-1 * clamp(27.2px,4.8vh,51.2px))}
.ix{
  position:relative;
  display:grid;grid-template-columns:clamp(74px,9vw,150px) minmax(0,1fr);
  gap:clamp(12.8px,2.4vw,35.2px);align-items:start;
  padding:clamp(19.2px,2.88vh,33.6px) 0;border-bottom:1px solid var(--line);
  transition:background .35s ease,padding-left .35s cubic-bezier(.16,1,.3,1);
}
/* On .ix, not a.ix. Only the two-bedroom is a link - the other two are not
   drawn yet - so the lift, the tint and the numeral colour fired on one card
   of three and the other two sat dead. They are options either way, and the
   two that are not links still say IN DESIGN and carry no "view the plan". */
.ix:hover{background:var(--bg-2);padding-left:11.2px}
.ix-n{
  font-family:var(--display);font-weight:300;letter-spacing:-.045em;
  font-size:clamp(30.4px,4.32vw,62.4px);line-height:.72;color:var(--ink);
  transition:color .35s ease;
}
.ix:hover .ix-n{color:var(--clay-t)}
.ix-t h3{
  font-family:var(--display);font-weight:600;letter-spacing:-.02em;
  font-size:clamp(16px,2vw,27.2px);line-height:1.08;margin:0 0 6.4px;
}
/* Hidden by default and dropped in under the option's own text on hover -
   nested inside .ix-t rather than floated over the row, so the reveal is
   always contained within that option's own hairlines and never spills
   into the row below it. A max-height transition, not grid-template-rows:
   .ix-media carries its own aspect-ratio, and aspect-ratio on a stretched
   grid item overrides stretch sizing - the item renders at its natural
   height regardless of a 0fr track, which is why that version never
   collapsed. max-height has no such conflict: .ix-media's real height
   (from its aspect-ratio) is always under the 300px cap, so it is never
   clipped once open, only hidden while collapsed. */
.ix-media-wrap{max-height:0;overflow:hidden;transition:max-height .5s cubic-bezier(.16,1,.3,1)}
.ix-media{
  overflow:hidden;
  width:100%;max-width:420px;aspect-ratio:16/10;
  background:var(--bg-2);border-radius:16px;
  box-shadow:0 16px 40px -20px rgba(0,0,0,.35);
  margin-top:0;transition:margin-top .5s cubic-bezier(.16,1,.3,1);
}
.ix:hover .ix-media-wrap,.ix:focus-within .ix-media-wrap{max-height:300px}
.ix:hover .ix-media,.ix:focus-within .ix-media{margin-top:14.4px}
.ix-media img{width:100%;height:100%;object-fit:cover;transition:transform 1.1s cubic-bezier(.16,1,.3,1)}
.ix:hover .ix-media img{transform:scale(1.05)}
.ix-media.pending{
  display:flex;align-items:center;justify-content:center;
  border:1px dashed var(--ink-4);color:var(--ink-3);
}
.ix-go{
  /* Control type - see the note on .nav-links a in home.css. */
  font-family:var(--sans);font-size:11px;font-weight:600;letter-spacing:-.005em;
  color:var(--ink);display:inline-flex;gap:6.4px;align-items:center;margin-top:12.8px;
}
.ix:hover .ix-go{color:var(--ink)}
@media (max-width:900px){
  .ix{grid-template-columns:56px minmax(0,1fr);gap:11.2px 14.4px}
  /* No hover on touch, so the picture is just always open rather than
     waiting for a cursor that never arrives. */
  .ix-media-wrap{max-height:300px}
  .ix-media{margin-top:11.2px;box-shadow:none}
}

/* --- ruled metadata column, the reference's YEAR / TYPE / CLIENT block */
.meta-list{margin:0;border-top:1px solid var(--line)}
.meta-list div{
  display:grid;grid-template-columns:clamp(88px,11vw,150px) minmax(0,1fr);
  gap:14px;padding:11px 0;border-bottom:1px solid var(--line);align-items:baseline;
}
.meta-list dt{
  font-family:var(--mono);font-size:11px;letter-spacing:.18em;text-transform:uppercase;
  color:var(--ink);margin:0;
}
.meta-list dd{margin:0;color:var(--ink);font-size:13px;line-height:1.5}
.meta-list dd small{display:block;color:var(--ink);font-size:11px;margin-top:1.6px}

/* --- numbered section headers */
.section > .sec-n{
  font-family:var(--mono);font-size:11px;letter-spacing:.2em;text-transform:uppercase;
  color:var(--ink-3);margin:0 0 11.2px;display:flex;align-items:center;gap:9.6px;
}
.section > .sec-n::after{content:"";flex:1;height:1px;background:var(--line);max-width:180px}

/* The A.01 interactive layout moved to home.css: home.html shows it too,
   and home.html does not load this file. */

/* --- Privacy Policy and Terms of Use (privacy.html, terms.html) -------------
   Added 2026-10-07. Same register as the luxury references the rest of the
   site follows (Vipp, Aman, Garde Hvalsoe): one narrow reading column, the
   numbered rhythm process.html already uses, hairlines between sections,
   nothing boxed, no banner. Full ink at 15.2px - legal copy is still copy
   people read, so it gets the sitewide reading size, not the fine print
   treatment (no small grey text, 2026-10-02). */
.legal-head{max-width:760px}
.legal-head .lede a,.legal-body a,.legal-contact a{text-decoration:underline;text-decoration-thickness:1px;text-underline-offset:3px}
.legal-date{display:block;margin:19.2px 0 0;color:var(--ink)}
.legal{max-width:760px;margin:0 0 clamp(51.2px,8vh,96px)}
.legal-sec{display:grid;grid-template-columns:60.8px minmax(0,1fr);padding:clamp(24px,3.6vh,35.2px) 0;border-top:1px solid var(--line)}
.legal-sec:first-child{border-top:0;padding-top:0}
.legal-sec > .mono{padding-top:5.6px;color:var(--ink)}
.legal-body h2{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}
.legal-body p,.legal-body li{color:var(--ink);font-size:15.2px;line-height:1.85;max-width:62ch}
.legal-body p{margin:0 0 12.8px}
.legal-body ul{margin:0 0 12.8px;padding-left:1.15em}
.legal-body li{margin:0 0 6.4px}
.legal-body p:last-child,.legal-body ul:last-child{margin-bottom:0}
.legal-contact{display:flex;flex-wrap:wrap;align-items:baseline;gap:4px 28.8px;border-top:1px solid var(--line);padding:clamp(24px,3.6vh,35.2px) 0 0 60.8px;font-size:15.2px;color:var(--ink)}
.legal-contact .mono{flex-basis:100%;margin-bottom:4px}
.legal-contact a{padding:4px 0}
@media (max-width:640px){
  .legal-sec{grid-template-columns:1fr}
  .legal-sec > .mono{padding-top:0;margin-bottom:8px}
  .legal-contact{padding-left:0}
}

/* Footer legal links, in the bottom bar beside the copyright line - where
   the reference sites keep them: quiet, one line, no "cookie" anything
   (the site sets no cookies, see privacy.html section 04). 12px full ink,
   the sentence floor; 4px of padding above and below takes the tap area
   past WCAG's 24px without changing how the line looks. On desktop they
   sit right, next to Back to top. */
.foot-legal{display:flex;flex-wrap:wrap;gap:0 24px;font-size:12px;letter-spacing:.06em;color:var(--ink)}
.foot-legal a{position:relative;display:inline-block;padding:4px 0 5.7px}
.foot-legal a::after{content:'';position:absolute;left:0;right:100%;bottom:3px;height:1px;background:currentColor;transition:right .25s ease}
.foot-legal a:hover::after,.foot-legal a[aria-current="page"]::after{right:0}
@media (min-width:761px){
  .foot-legal{margin-left:auto}
  .foot-legal + .foot-top-link{margin-left:32px}
}
/* Phones stack the bar. Back to top pads its hit area out to 44px (home.css,
   the shared ::after rule), which reaches ~13.5px above it - over the bottom
   of these links at the bar's 6.8px gap. 8px more clears it. */
@media (max-width:760px){
  .foot-legal + .foot-top-link{margin-top:8px}
}

/* PHONE TYPE SCALE - the pages.css half of the 28 Oct outlier pass (see
   the end of home.css). Section headings to 24px, body to 15.2px. */
@media (max-width:700px){
  /* Process stage titles were 30px - bigger than the page's own 26px
     title; the process CTA and the plan pages' tab headings 22.4px; the
     homes card title 27.2px (kept matched to "What you get"). */
  .hd-title,
  .pr-stage h2,
  .process-cta h2,
  .plan-tabs-body h2{font-size:24px}
  /* 15.5 (plan intros), 15.7 (homes card text) and 16px (process lede and
     stage tags) were near-misses of the 15.2px body every page uses. */
  .hd-desc,.hd-spec,
  .plan-intro-copy p,
  .pr-hero-lede,.pr-stage-tag{font-size:15.2px}
}
