/*
 * Croissant in Bed - public site.
 *
 * Hand-authored, no build step, one stylesheet for every static page. The
 * palette mirrors packages/ui/src/tokens.ts (cream ground, one brown ink) - it is
 * restated here rather than imported because these pages are plain files served
 * straight off the edge, with nothing to bundle them with.
 *
 * Premium in look, playful in copy (PRD section 1.4, WEB-024). The tricolore is
 * an accent rule, never a background: the French identity is an anchor, not a
 * costume.
 */

/*
 * Every value below is a copy of a token in packages/ui/src/tokens.css, named
 * on the line that carries it. Copies drift, and there is no build step here to
 * stop them, so the comment IS the mechanism: change a token and grep this file
 * for its name. Nothing here is a colour, radius, shadow or font that the
 * product does not already have - a value with no `--cib-` name beside it is a
 * bug, not a decision.
 */
:root {
  /*
   * Light, always. The brand ships one light mark and it sits on its own light
   * field (PRD section 1.4, WEB-015), so there is no dark palette here and no
   * `prefers-color-scheme` block anywhere in this file. Without this
   * declaration the browser still paints native controls and scrollbars dark
   * for a visitor whose OS prefers dark, over a page that stayed cream.
   */
  color-scheme: light;

  --cream: #f9e8d6; /* --cib-cream */
  --cream-soft: #fdf6ee; /* --cib-cream-soft, and the page ground (--cib-surface) */
  --cream-deep: #f0d9c0; /* --cib-cream-deep */
  --ink: #83522a; /* --cib-ink */
  --ink-strong: #6a4020; /* --cib-ink-strong */
  --ink-soft: #a8794d; /* --cib-ink-soft */
  --butter: #e8b04b; /* --cib-butter - the focus ring, nothing else */
  --charcoal: #2b211a; /* --cib-charcoal, and the body ink (--cib-text) */
  --charcoal-soft: #5a4a3d; /* --cib-charcoal-soft (--cib-text-muted) */
  /* The tricolore accent. Deliberately NOT in the token set: it is a flag, not a
     palette, and it appears only as a 4px rule (WEB-024). */
  --bleu: #0055a4;
  --rouge: #ef4135;
  --radius: 16px; /* --cib-radius-lg */
  --radius-lg: 24px; /* --cib-radius-xl */
  /*
   * The control height, and the default for every control on these pages: the
   * header CTA, the menu toggle, every form field, the dialog's close. It has
   * no `--cib-` twin on purpose - `--cib-control` (36px) is sized for dense
   * product tables and these pages have none, they are read thumb-first and
   * their controls are the page. That is the only licensed deviation, and it
   * is a deviation in the VALUE, not in the mechanism.
   *
   * Six separate reports of misaligned buttons came from having no token at
   * all: the switcher declared 40px, the toggle 44px, `.btn` 48px, so the
   * header's three controls rendered at three heights side by side, each
   * number chosen where it was written. There are exactly THREE sizes now, all
   * of them below, all of them named - a control picks one, it never states a
   * height of its own, and `scripts/check-control-metrics.mjs` fails the build
   * on a literal height in any control rule in this file.
   */
  --control: 48px;
  /* The one large variant, for a page's own primary action (hero, form submit).
     Never mixed with `--control` in the same row - see the check. */
  --control-lg: 56px;
  /* The one compact variant, for a control that is an icon and no words: the
     language switcher, whose whole content is a 24px flag. It is deliberately
     NOT the height of the owners CTA beside it - a flag does not carry a
     48px box - and it centres on the nav text rather than on the button.
     `--cib-control-sm` is the same idea in the product. */
  --control-sm: 32px;
  /*
   * The header's brand row. It is a height the ROW owns, not a control: the
   * row is brand + menu button, and below --nav-collapse the open menu joins
   * the same wrapping flex line as a second line. A `min-height` on the
   * container alone only holds while there is one line - the moment the panel
   * wraps, the container is taller than 68px on its own, there is no free
   * space left to distribute, and the brand row collapses to its content, so
   * the toggle jumps up against the tricolore. Stated on `.brand` as well, the
   * first line is 68px whether or not a second one exists.
   */
  --header-row: 68px;
  /*
   * The header navigation's rhythm: the space the EYE sees between any two of
   * its six controls, in both the wide bar and the narrow panel.
   *
   * It has to be stated this way because a nav link's box is not what a reader
   * sees. The links carry padding so they have a hover target and a tap target;
   * that padding is transparent, so it reads as space, while the switcher's
   * bordered chip and the CTA's filled pill show their true edges. A flat `gap`
   * therefore renders as three different spacings - it measured 8px between
   * every pair and looked like 32/32/32/20/8 down the panel, with the chip and
   * the button crowding each other at the bottom.
   *
   * So: `gap` is the rhythm MINUS the padding that the two neighbours already
   * contribute, and a neighbour with no padding of its own makes up the
   * difference with a margin. Change --nav-gap and every one of them follows.
   */
  --nav-gap: 24px;
  /* The links' own padding on the axis that separates them - 10px inline in the
     bar, and the same 10px block in the panel, which is why one name serves
     both. Every gap below is stated net of it. */
  --nav-link-pad: 10px;
  /* --cib-radius-md: the corner of a boxed control. The pill is for the
     buttons, which are the site's voice; a small square-ish control gets this. */
  --radius-md: 10px;
  --shadow: 0 12px 32px rgba(43, 33, 26, 0.14); /* --cib-shadow-lg */
  --white: #ffffff; /* --cib-white */
  /* --cib-border / --cib-border-strong. Every hairline on the site was its own
     alpha (0.14, 0.16, 0.18, 0.35) - four rules that were meant to be one. */
  --rule: rgba(131, 82, 42, 0.18);
  --rule-strong: rgba(131, 82, 42, 0.38);
  /* --cib-font-brand */
  --font-brand: "Iowan Old Style", "Palatino Linotype", Palatino, Georgia, "Times New Roman", serif;
  /* --cib-font-body */
  --font-body: system-ui, -apple-system, "Segoe UI", Roboto, "Helvetica Neue", Arial, sans-serif;
}

*,
*::before,
*::after {
  box-sizing: border-box;
}

html {
  scroll-behavior: smooth;
}

@media (prefers-reduced-motion: reduce) {
  html {
    scroll-behavior: auto;
  }
}

body {
  margin: 0;
  background: var(--cream-soft);
  color: var(--charcoal);
  font-family: var(--font-body);
  font-size: 17px;
  line-height: 1.6;
  -webkit-text-size-adjust: 100%;
}

img,
svg {
  max-width: 100%;
  height: auto;
}

a {
  color: var(--ink-strong);
}

a:focus-visible,
button:focus-visible,
summary:focus-visible,
input:focus-visible,
textarea:focus-visible,
select:focus-visible {
  outline: 3px solid var(--ink);
  outline-offset: 2px;
}

.wrap {
  width: min(1120px, 100% - 48px);
  margin-inline: auto;
}

@media (max-width: 640px) {
  .wrap {
    width: min(1120px, 100% - 32px);
  }
}

.skip {
  position: absolute;
  left: -9999px;
}

.skip:focus {
  position: static;
  display: inline-block;
  margin: 8px;
}

/* -- tricolore accent ---------------------------------------------------- */

.tricolore {
  display: block;
  height: 5px;
  background: linear-gradient(
    to right,
    var(--bleu) 0 33.33%,
    #ffffff 33.33% 66.66%,
    var(--rouge) 66.66% 100%
  );
}

.tricolore--rule {
  width: 120px;
  border-radius: 999px;
  margin: 0 0 20px;
}

/* -- header -------------------------------------------------------------- */

.site-header {
  position: sticky;
  top: 0;
  z-index: 10;
  /*
   * `--cream`, flat, and no `backdrop-filter`. The mark in this bar is the
   * founder's stamp, drawn on exactly this cream (--cib-topbar-bg on the
   * portals is the same colour, for the same reason). It was a translucent
   * cream-soft that let the page tint the bar as it scrolled - which is a fine
   * bar to have behind text and the wrong one to have behind artwork.
   */
  background: var(--cream);
  border-bottom: 1px solid var(--rule);
}

/* Artwork: it holds its 34px whatever the header row does to the flex line. */
.brand__mark {
  display: block;
  flex: none;
  -webkit-user-drag: none;
  user-select: none;
}

.site-header__inner {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: 16px;
  min-height: var(--header-row);
  flex-wrap: wrap;
}

.brand {
  display: inline-flex;
  align-items: center;
  /* See --header-row: this is what keeps the brand row at its full height once
     the open menu puts a second flex line under it. */
  min-height: var(--header-row);
  gap: 10px;
  text-decoration: none;
  color: var(--ink);
}

.brand__name {
  font-family: var(--font-brand);
  font-size: 20px;
  font-weight: 700;
  letter-spacing: 0.01em;
  color: var(--charcoal);
  white-space: nowrap;
}

.site-nav {
  display: flex;
  align-items: center;
  /* Two padded links either side of it, so the gap carries what is left. */
  gap: calc(var(--nav-gap) - 2 * var(--nav-link-pad));
  flex-wrap: wrap;
}

/*
 * `> a:not(.btn)`, not `a`. Two reasons, and both were live bugs.
 *
 * `.site-nav a` is (0,1,1) and `.btn--primary` is (0,1,0), so the plain nav
 * link rule outranked the button's own declarations on the one <a> in the nav
 * that is a button: the header CTA rendered charcoal-on-brown (2.40:1, below
 * the 4.5:1 floor) with the nav's 8px padding and 8px radius instead of white
 * on a 999px pill, and hovering it swapped in the cream nav background rather
 * than the darker ink. `:not(.btn)` takes the button out of this rule's reach
 * entirely instead of restating every property it stole.
 *
 * The child combinator does the same for the language switcher: its menu links
 * are descendants of the nav and are not nav links.
 */
.site-nav > a:not(.btn) {
  color: var(--charcoal);
  text-decoration: none;
  padding: 8px var(--nav-link-pad);
  border-radius: 8px;
  font-size: 15px;
}

.site-nav > a:not(.btn):hover {
  background: var(--cream-deep);
}

/* -- the narrow-screen menu ----------------------------------------------- */

/*
 * Six controls - four links, the language switcher and the CTA - wrap onto
 * three rows at 390px and eat 200px of the screen before the page has said
 * anything. Below `--nav-collapse` they fold behind one button instead.
 *
 * The button ships `hidden` in the markup and site.js unhides it, so the whole
 * collapse is conditional on `html.js`: with scripting off there is nothing to
 * open the menu with, and the nav stays visible and wrapping exactly as it did
 * before. That is the same bargain the language switcher already makes.
 *
 * The breakpoint is measured with a cushion, and the cushion is the point.
 * French is the wider of the two navigations - six controls at 727px beside a
 * 206px wordmark, plus a 16px flex gap and `.wrap`'s 48px of gutter - and it
 * breaks onto a second row below 997px of viewport here. English breaks at
 * ~943px. Neither number is the one to key off:
 *
 *   - a classic scrollbar takes ~15px off the layout viewport, and browsers do
 *     not agree on whether a `max-width` query sees that width or the outer
 *     one, so the real break can arrive ~15px early;
 *   - both numbers are macOS text metrics. `--font-brand` resolves to Iowan
 *     Old Style here and to Palatino Linotype or Georgia on Windows, so the
 *     wordmark and the links are not this wide on every machine.
 *
 * 1060px collapses roughly 60px before the measured break, which absorbs both.
 * Re-measure if a link is added or renamed - and keep the cushion.
 */
.nav-toggle {
  display: none;
  align-items: center;
  gap: 10px;
  min-height: var(--control);
  padding: 0 16px;
  border: 1px solid var(--rule-strong);
  border-radius: 999px;
  background: var(--white);
  color: var(--charcoal);
  font-family: inherit;
  font-size: 15px;
  font-weight: 600;
  cursor: pointer;
}

.nav-toggle:hover {
  background: var(--cream-deep);
}

/*
 * At 320px the 206px wordmark and a labelled button are 334px of content
 * against 288px of room, and the header wraps to two rows again - the exact
 * thing this menu exists to prevent. The word goes; `aria-label="Menu"` on the
 * button is what keeps the control named once the visible text is gone, and it
 * is on the button at every width so the accessible name never changes with
 * the viewport.
 */
@media (max-width: 380px) {
  .nav-toggle__label {
    display: none;
  }

  .nav-toggle {
    padding: 0 14px;
  }
}

/* Three bars from one element: the box is the middle bar, the two pseudo
   elements are the outer pair. */
.nav-toggle__bars,
.nav-toggle__bars::before,
.nav-toggle__bars::after {
  display: block;
  width: 18px;
  height: 2px;
  border-radius: 2px;
  background: currentcolor;
}

.nav-toggle__bars {
  position: relative;
}

.nav-toggle__bars::before,
.nav-toggle__bars::after {
  content: "";
  position: absolute;
  left: 0;
}

.nav-toggle__bars::before {
  top: -6px;
}

.nav-toggle__bars::after {
  top: 6px;
}

/*
 * Open: the outer bars meet in the middle and cross, and the word goes. "X
 * Menu" reads as a label for a menu that is already open and on screen below
 * it - the cross is the whole message. `aria-label="Menu"` is on the button at
 * every state, so the accessible name does not change with the visible text,
 * and with no label left the pill becomes a round icon button rather than a
 * wide box with a small cross adrift in it.
 */
.nav-toggle[aria-expanded="true"] .nav-toggle__label {
  display: none;
}

.nav-toggle[aria-expanded="true"] {
  justify-content: center;
  min-width: var(--control);
  padding: 0;
}

.nav-toggle[aria-expanded="true"] .nav-toggle__bars {
  background: transparent;
}

.nav-toggle[aria-expanded="true"] .nav-toggle__bars::before {
  top: 0;
  transform: rotate(45deg);
}

.nav-toggle[aria-expanded="true"] .nav-toggle__bars::after {
  top: 0;
  transform: rotate(-45deg);
}

/* -- language switcher --------------------------------------------------- */

/*
 * A flag trigger plus a menu of both languages (WEB-016). It is a <details>
 * disclosure so the menu still opens with scripting off - <summary> is
 * natively a button in the accessibility tree and natively carries the
 * expanded state - and site.js adds the menu-widget behaviour on top:
 * aria-expanded, Escape, outside click, arrow keys.
 *
 * The trigger is the flag alone in a small rounded box: no code beside it and
 * no caret under it. It is a setting, not an action, so it takes the compact
 * height and sits on the nav text's line rather than matching the owners CTA -
 * the button is the header's one loud thing and a language chip must not
 * compete with it. The control's name is on the summary's aria-label, and the
 * menu it opens still names both languages in words.
 */
.lang-switch {
  position: relative;
}

.lang-switch > summary {
  display: inline-flex;
  align-items: center;
  /* The default disclosure triangle, removed in both engines: the box is the
     affordance, and there is no second element inside it to point at. */
  list-style: none;
  min-height: var(--control-sm);
  padding: 0 8px;
  border: 1px solid var(--rule);
  border-radius: var(--radius-md);
  background: var(--white);
  color: var(--charcoal);
  cursor: pointer;
}

.lang-switch > summary::-webkit-details-marker {
  display: none;
}

.lang-switch > summary:hover {
  background: var(--cream-deep);
}

/* The open state is on the box itself now that there is no caret to turn. */
.lang-switch[open] > summary {
  background: var(--cream-deep);
  border-color: var(--rule-strong);
}

.lang-switch__menu {
  position: absolute;
  top: calc(100% + 8px);
  right: 0;
  z-index: 20;
  min-width: 190px;
  margin: 0;
  padding: 6px;
  list-style: none;
  background: var(--white);
  border: 1px solid var(--rule);
  border-radius: var(--radius);
  box-shadow: var(--shadow);
}

.lang-switch__menu a {
  display: flex;
  align-items: center;
  gap: 10px;
  padding: 10px 12px;
  border-radius: var(--radius-md);
  color: var(--charcoal);
  font-size: 15px;
  text-decoration: none;
  white-space: nowrap;
}

.lang-switch__menu a:hover,
.lang-switch__menu a:focus-visible {
  background: var(--cream-deep);
}

.lang-switch__menu a[aria-current] {
  font-weight: 700;
}

/* A tick beside the language already being read, so the menu says where you
   are as well as where you can go. */
.lang-switch__here {
  margin-left: auto;
  color: var(--ink);
  font-size: 13px;
}

/*
 * The flags are drawn in the markup, never fetched: these pages ship with no
 * external assets, and an emoji flag renders as two letters on Windows. The
 * global `svg { height: auto }` is why both dimensions are stated here.
 */
.flag {
  flex: none;
  width: 24px;
  height: 12px;
  border-radius: 2px;
  box-shadow: 0 0 0 1px var(--rule-strong);
}

/* -- buttons ------------------------------------------------------------- */

.btn {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  gap: 8px;
  min-height: var(--control);
  padding: 0 22px;
  border-radius: 999px;
  border: 1px solid transparent;
  font: inherit;
  font-weight: 600;
  text-decoration: none;
  cursor: pointer;
}

/*
 * White, in every state, and stated for every state rather than inherited.
 *
 * `--ink` is a dark brown: white on it measures 6.55:1 and the body ink
 * (`--charcoal`) measures 2.40:1, which is unreadable and is what the header
 * CTA rendered as while `.site-nav a` outranked this rule. `:visited` is
 * listed because the CTA points at the dashboard, which a returning partner
 * has been to, and a visited-link colour on a dark pill is the same defect
 * again.
 * Hover is `--ink-strong`: white on it measures 8.87:1.
 */
.btn--primary,
.btn--primary:link,
.btn--primary:visited,
.btn--primary:hover,
.btn--primary:focus,
.btn--primary:active {
  background: var(--ink);
  color: var(--white);
}

.btn--primary:hover,
.btn--primary:active {
  background: var(--ink-strong);
}

.btn--secondary {
  background: transparent;
  color: var(--ink-strong);
  border-color: var(--ink);
}

.btn--secondary:hover {
  background: var(--cream-deep);
}

.btn--lg {
  min-height: var(--control-lg);
  padding: 0 30px;
  font-size: 17px;
}

/*
 * The two controls that owe the nav a margin, declared here for the same
 * reason the panel below is: both beat `.lang-switch` and `.btn` on
 * specificity, so they have to come after the rules they beat.
 *
 * Neither has padding of its own on the axis that separates it from the thing
 * before it, so each makes up what a link would have contributed - the
 * switcher one link's worth, the CTA two, because it follows the switcher and
 * so has none on either side. See --nav-gap.
 */
.site-nav > .lang-switch {
  margin-left: var(--nav-link-pad);
}

.site-nav > .btn {
  margin-left: calc(2 * var(--nav-link-pad));
}

/*
 * The narrow-screen panel, declared here rather than beside `.nav-toggle`
 * above. It restyles the language switcher inside the panel, and a rule that
 * beats `.lang-switch` on specificity has to come after the rules it beats -
 * stated earlier it reads as a cascade accident, and biome flags it as one.
 */
@media (max-width: 1060px) {
  .js .nav-toggle {
    display: inline-flex;
  }

  /* The header row is brand + button, and the menu is a full-width panel
     beneath them - hence `flex-basis: 100%` on a wrapping flex row rather than
     absolute positioning, which would need the header's height hardcoded.
     `gap` is inherited from `.site-nav`: the rhythm is one number for both
     layouts, and a column gap nets out against the links' block padding
     exactly as the row gap nets out against their inline padding. */
  .js .site-nav {
    display: none;
    flex-basis: 100%;
    flex-direction: column;
    align-items: stretch;
    padding: 8px 0 14px;
    border-top: 1px solid var(--rule);
  }

  .js .site-header[data-nav-open] .site-nav {
    display: flex;
  }

  /* The block padding is now the same 10px as the inline padding, so one
     `--nav-link-pad` nets out the gap on whichever axis the nav is laid out on.
     A row is still 47px of tap target at this font size. */
  .js .site-nav > a:not(.btn) {
    padding: var(--nav-link-pad);
    font-size: 17px;
  }

  /*
   * Nothing here sets `order`: the panel's rows are the document's rows, which
   * is the wide header's order too - links, then the language switcher, then
   * the CTA last. It used to pull the CTA above the switcher, so the same six
   * controls read in one order across the top bar and the opposite one inside
   * the menu.
   *
   * The switcher sits on the links' own left edge rather than stretched across
   * the panel: the panel is `align-items: stretch`, and stretching a 32px flag
   * chip to full width produced an empty white bar with a flag adrift in the
   * middle. The old full-width rule was right for the labelled pill this
   * replaced.
   */
  .js .site-nav > .lang-switch {
    align-self: flex-start;
    /* Owed on the block axis now. The inline one stays: stacked, it is what
       lines the chip's left edge up with the links' text above it. */
    margin-top: var(--nav-link-pad);
  }

  .js .site-nav > .btn {
    margin-left: 0;
    margin-top: calc(2 * var(--nav-link-pad));
  }

  /* Dropped from the trigger's left edge rather than its right: the trigger is
     now narrower than the menu, and hanging a 190px menu off the right edge of
     a 40px chip put it half over the page behind at 390px. */
  .js .site-nav > .lang-switch .lang-switch__menu {
    right: auto;
    left: 0;
  }
}

/* -- hero ---------------------------------------------------------------- */

/*
 * WEB-024: the morning-ritual photograph IS the hero ground, not an
 * illustration beside it. Two rules make that safe for the copy on top.
 * (1) The photograph is bright cream and near-white, and every word over it is
 *     brown ink, so it is veiled by ::before rather than used raw - the veil is
 *     heaviest on the left where the headline sits and thinnest on the right,
 *     where the picture is allowed to read.
 * (2) The veil is a pseudo-element, not another background layer, so it paints
 *     over the photograph and under the text; `isolation` keeps its negative
 *     z-index inside this section instead of sliding behind the page ground.
 * Never `background-attachment: fixed` here: iOS Safari drops it to `scroll`
 * after re-rasterising the whole image, which is the jank without the effect.
 */
.hero {
  /* Tight on top: the WEB-001 answers must clear a 749px fold at 1280 wide. */
  padding: 40px 0 88px;
  position: relative;
  isolation: isolate;
  background-color: var(--cream-soft);
  /* The pair IS the fallback. An engine without image-set() keeps the JPEG from
     the first declaration and discards the second as invalid; one with it takes
     the WebP. Collapsing this to one declaration drops one of those engines. */
  background-image: url("/img/hero-breakfast.jpg");
  /* biome-ignore lint/suspicious/noDuplicateProperties: deliberate, see above */
  background-image: image-set(
    url("/img/hero-breakfast.webp") type("image/webp"),
    url("/img/hero-breakfast.jpg") type("image/jpeg")
  );
  background-repeat: no-repeat;
  background-position: 55% 56%;
  background-size: cover;
}

.hero::before {
  content: "";
  position: absolute;
  inset: 0;
  z-index: -1;
  background:
/* The section below is --cream, not --cream-soft: without this the photograph
       stops on a hard horizontal line one pixel above a different beige. */
    linear-gradient(to bottom, rgba(249, 232, 214, 0) 78%, var(--cream) 100%),
    radial-gradient(120% 90% at 12% 0%, rgba(249, 232, 214, 0.94) 0%, rgba(249, 232, 214, 0) 62%),
    linear-gradient(
      100deg,
      rgba(253, 246, 238, 0.96) 0%,
      rgba(253, 246, 238, 0.9) 32%,
      rgba(253, 246, 238, 0.6) 58%,
      rgba(253, 246, 238, 0.3) 100%
    );
}

/*
 * Stacked, the hero is ~1330px tall against a 390px viewport, and `cover` on
 * that ratio enlarges a 1600px-wide photograph to about 2000px and keeps a
 * 390px slice of pillow: a blurred white wash, not a picture. So on narrow
 * screens the photograph stops being a wash and becomes a band - laid in at
 * full width, natural height, pinned to the foot of the hero, with the veil
 * opaque cream above it and thin over it.
 */
@media (max-width: 880px) {
  .hero {
    padding-bottom: 0;
    background-size: 100% auto;
    background-position: 50% 100%;
  }

  .hero::before {
    background: linear-gradient(
      to bottom,
      var(--cream-soft) 0%,
      var(--cream-soft) 68%,
      rgba(253, 246, 238, 0.6) 80%,
      rgba(253, 246, 238, 0.22) 88%,
      rgba(253, 246, 238, 0.22) 100%
    );
  }

  /* The band is the hero's bottom edge, so the answers need to clear it. */
  .hero__grid {
    padding-bottom: 34vw;
  }
}

.hero__grid {
  display: grid;
  grid-template-columns: minmax(0, 1.05fr) minmax(0, 0.95fr);
  gap: 48px;
  align-items: center;
}

@media (max-width: 880px) {
  .hero__grid {
    grid-template-columns: minmax(0, 1fr);
    gap: 32px;
  }
}

.eyebrow {
  display: inline-flex;
  align-items: center;
  gap: 8px;
  font-size: 13px;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  color: var(--ink-strong);
  margin: 0 0 14px;
  font-weight: 600;
}

h1 {
  font-family: var(--font-brand);
  font-size: clamp(38px, 6vw, 62px);
  line-height: 1.04;
  margin: 0 0 18px;
  letter-spacing: -0.01em;
}

h1 em {
  font-style: italic;
  color: var(--ink);
}

.lede {
  font-size: clamp(18px, 2.2vw, 21px);
  color: var(--charcoal-soft);
  margin: 0 0 26px;
  max-width: 58ch;
}

.tagline {
  font-family: var(--font-brand);
  font-style: italic;
  font-size: 20px;
  color: var(--ink-strong);
  margin: 0 0 26px;
}

.hero__actions {
  display: flex;
  flex-wrap: wrap;
  gap: 14px;
  margin-bottom: 22px;
}

.hero__reassurance {
  font-size: 14px;
  color: var(--charcoal-soft);
  margin: 0;
}

/* -- the five answers (WEB-001), above the fold -------------------------- */

.answers {
  list-style: none;
  margin: 28px 0 0;
  padding: 0;
  display: grid;
  gap: 10px;
}

.answers li {
  display: grid;
  grid-template-columns: 26px minmax(0, 1fr);
  gap: 12px;
  align-items: start;
  font-size: 16px;
}

.answers b {
  font-weight: 700;
}

.answers .tick {
  width: 24px;
  height: 24px;
  border-radius: 999px;
  background: var(--ink);
  color: var(--white);
  display: grid;
  place-items: center;
  font-size: 13px;
  line-height: 1;
  margin-top: 2px;
}

/*
 * WEB-001: the five answers ARE the hero's right column, so at 1280x749 all
 * five sit fully above the fold in both languages - a list appended under a
 * ~700px stack of headline, lede, tagline and buttons never was.
 */
.hero__answers {
  margin: 0;
  align-self: center;
  /* Opaque enough to hold 16px ink over the photograph's brightest quarter -
     the pillows - which a 0.62 wash was not. */
  background: rgba(255, 255, 255, 0.92);
  border: 1px solid var(--rule);
  border-radius: var(--radius-lg);
  padding: 22px 24px;
  box-shadow: var(--shadow);
}

/*
 * The `.figure` / `.figure__art` / `.figure--hero` placeholder block stood here
 * until the real photograph arrived. It held one drawn SVG under the hero grid,
 * captioned "reserved for the definitive photograph"; that photograph is now
 * the hero's own background, so both the drawing and the rules that framed it
 * are gone rather than left unreferenced.
 */

/* -- sections ------------------------------------------------------------ */

section {
  padding: 64px 0;
}

section.tinted {
  background: var(--cream);
}

h2 {
  font-family: var(--font-brand);
  font-size: clamp(28px, 3.6vw, 38px);
  line-height: 1.12;
  margin: 0 0 14px;
}

h3 {
  font-family: var(--font-brand);
  font-size: 21px;
  margin: 0 0 8px;
}

.section-lede {
  color: var(--charcoal-soft);
  max-width: 62ch;
  margin: 0 0 32px;
}

.cards {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(260px, 1fr));
  gap: 20px;
}

.card {
  background: var(--white);
  border: 1px solid var(--rule);
  border-radius: var(--radius);
  padding: 24px;
}

.card p:last-child {
  margin-bottom: 0;
}

.card__step {
  display: inline-grid;
  place-items: center;
  width: 34px;
  height: 34px;
  border-radius: 999px;
  background: var(--cream-deep);
  color: var(--ink-strong);
  font-family: var(--font-brand);
  font-weight: 700;
  margin-bottom: 12px;
}

.prose {
  max-width: 74ch;
}

.prose h2 {
  margin-top: 40px;
}

.prose h3 {
  margin-top: 28px;
}

.prose ul,
.prose ol {
  padding-left: 22px;
}

.prose li {
  margin-bottom: 8px;
}

.callout {
  border-left: 4px solid var(--ink);
  background: var(--cream);
  padding: 16px 20px;
  border-radius: 0 var(--radius) var(--radius) 0;
  margin: 24px 0;
}

.callout p:last-child {
  margin-bottom: 0;
}

/* -- FAQ ------------------------------------------------------------------
 *
 * A stack of <details> disclosures, so every answer is reachable with
 * scripting off and a browser's own in-page find still opens the one it
 * matched. The default marker is removed in both engines and replaced by a
 * caret drawn with borders - no glyph, so the stylesheet stays ASCII.
 */

.faq {
  margin: 24px 0;
  border-top: 1px solid var(--rule);
}

.faq > details {
  border-bottom: 1px solid var(--rule);
}

.faq > details > summary {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: 16px;
  list-style: none;
  padding: 16px 0;
  color: var(--ink-strong);
  font-weight: 600;
  cursor: pointer;
}

.faq > details > summary::-webkit-details-marker {
  display: none;
}

.faq > details > summary:hover {
  color: var(--ink);
}

.faq > details > summary::after {
  content: "";
  flex: none;
  width: 0;
  height: 0;
  border-top: 6px solid currentcolor;
  border-right: 5px solid transparent;
  border-left: 5px solid transparent;
  transition: transform 150ms ease;
}

@media (prefers-reduced-motion: reduce) {
  .faq > details > summary::after {
    transition: none;
  }
}

.faq > details[open] > summary::after {
  transform: rotate(180deg);
}

.faq > details > p {
  margin: 0 0 16px;
  padding-right: 32px;
  color: var(--charcoal-soft);
}

table.terms {
  width: 100%;
  border-collapse: collapse;
  margin: 20px 0;
  font-size: 16px;
}

table.terms th,
table.terms td {
  text-align: left;
  padding: 12px 14px;
  border-bottom: 1px solid var(--rule);
  vertical-align: top;
}

table.terms th {
  font-size: 13px;
  text-transform: uppercase;
  letter-spacing: 0.06em;
  color: var(--charcoal-soft);
}

.table-scroll {
  overflow-x: auto;
  /* A scroll container must also be a containing block, or an absolutely
     positioned descendant - a `.cib-visually-hidden` column name - escapes the
     clip and extends the PAGE instead of the table. Measured on the partner
     Apartments list: one 1px span, 564px of horizontal page scroll at a 360px
     viewport. See packages/ui/src/layout.css, `.cib-tablewrap`. */
  position: relative;
}

/* -- forms --------------------------------------------------------------- */

.field {
  display: grid;
  gap: 6px;
  margin-bottom: 18px;
}

.field label {
  font-weight: 600;
  font-size: 15px;
}

.field input,
.field textarea,
.field select {
  font: inherit;
  font-size: 16px;
  padding: 12px 14px;
  border-radius: var(--radius-md);
  border: 1px solid var(--rule-strong);
  background: var(--white);
  color: inherit;
  min-height: var(--control);
}

.field .hint {
  font-size: 13px;
  color: var(--charcoal-soft);
}

form.stack {
  max-width: 560px;
}

/* -- enquiry forms and their dialog (WEB-025) ------------------------------
 *
 * The <form> lives in the page in the markup and is MOVED into a <dialog> by
 * site.js, so a visitor with scripting off still sees it and can still submit
 * it by the form's own mailto: action. Everything here therefore styles the
 * dialog around a form that is otherwise unchanged.
 */

.enquiry-dialog {
  width: min(560px, calc(100vw - 32px));
  max-height: calc(100vh - 64px);
  overflow-y: auto;
  padding: 24px;
  border: 1px solid var(--rule);
  border-radius: var(--radius-lg);
  background: var(--white);
  color: var(--charcoal);
}

.enquiry-dialog::backdrop {
  /* Deliberately not a token: ::backdrop resolves custom properties against
     its own originating element in some engines, and a missing value there is
     transparent - which reads as "the modal did not open". */
  background: rgba(43, 32, 24, 0.55);
}

.enquiry-dialog__head {
  display: flex;
  /* Centred, not `baseline`: the close is a full-height control now, and a
     baseline row would hang its box below the title it sits beside. */
  align-items: center;
  justify-content: space-between;
  gap: 16px;
  margin-bottom: 16px;
}

.enquiry-dialog__head h2 {
  margin: 0;
  font-size: 22px;
}

.enquiry-dialog__close {
  flex: none;
  display: inline-flex;
  align-items: center;
  min-height: var(--control);
  border: 1px solid var(--rule);
  border-radius: 999px;
  background: var(--white);
  color: var(--ink-strong);
  padding: 0 16px;
  font: inherit;
  font-size: 14px;
  cursor: pointer;
}

.enquiry-dialog__close:hover {
  background: var(--cream-deep);
}

/* The Turnstile widget's own iframe. Empty until a site key is configured, so
   it must collapse to nothing rather than leave a gap in the form. */
.enquiry-check:not(:empty) {
  margin-top: 8px;
}

.enquiry-status:empty {
  display: none;
}

.enquiry-status {
  margin: 12px 0 0;
  font-size: 15px;
}

.enquiry-status[data-tone="ok"] {
  color: var(--ink-strong);
  font-weight: 600;
}

.enquiry-status[data-tone="error"] {
  color: #a8322a;
}

.enquiry-status[data-tone="busy"] {
  color: var(--charcoal-soft);
}

/* -- footer -------------------------------------------------------------- */

.site-footer {
  background: var(--charcoal);
  color: var(--cream-soft);
  padding: 48px 0 32px;
  margin-top: 40px;
}

/* The footer is a rail of short link lists, not prose. Underlining every item
   draws a row of rules across three columns and reads heavier than the
   headings above them; the column and the cream-on-charcoal contrast already
   say these are links. The underline returns on hover and focus so the
   affordance is not lost - and the focus outline is drawn by the global
   :focus-visible rule regardless. */
.site-footer a {
  color: var(--cream);
  text-decoration: none;
}

.site-footer a:hover,
.site-footer a:focus-visible {
  text-decoration: underline;
}

.footer-grid {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(200px, 1fr));
  gap: 28px;
}

.site-footer h2 {
  font-size: 16px;
  font-family: var(--font-body);
  text-transform: uppercase;
  letter-spacing: 0.08em;
  color: var(--cream-deep);
  margin: 0 0 12px;
}

.site-footer ul {
  list-style: none;
  margin: 0;
  padding: 0;
}

.site-footer li {
  margin-bottom: 8px;
}

.footer-legal {
  margin-top: 32px;
  padding-top: 20px;
  border-top: 1px solid rgba(249, 232, 214, 0.24);
  font-size: 14px;
  color: var(--cream-deep);
  display: flex;
  flex-wrap: wrap;
  gap: 12px;
  justify-content: space-between;
}

/* Placeholder banner on documents whose text the founders supply (WEB-007). */
.draft-notice {
  border: 2px dashed var(--rouge);
  border-radius: var(--radius);
  padding: 16px 20px;
  background: var(--white);
  margin: 0 0 28px;
}

.draft-notice strong {
  color: var(--rouge);
}