/* ============================================================
   IWAI FOUNDATION — shared by every Innovating with AI product page
   ------------------------------------------------------------
   Link AFTER tokens.css, BEFORE your own product stylesheet.

   What is in here: the page shell, header, footer, container and
   section scale, bands and panels, buttons, hero, section heads,
   prose, dividers, FAQ, video testimonials, coach cards, pricing
   and plan chrome, payment icons, the countdown, the floating
   section nav, and the comparison table.

   What is NOT in here: anything invented for one product. Those
   live in kit/reference/<product>/css/styles.css — mine them for
   patterns, copy what fits, and rename to your own product.

   Rules that survived from the AICP build carry their original
   comments, including the ones that record a trap. Keep them.

   Two standing traps, both learned the hard way:
   • Media queries add no specificity. Among equal-specificity
     rules that all match, the LAST in source wins — so a
     narrower query placed earlier loses to a wider one placed
     later. Raise specificity when an override silently does
     nothing.
   • Gold (--iwai-yellow) fails WCAG AA as text at body size.
     Tint the BACKGROUND with --iwai-yellow-soft and keep the
     text navy.
   ============================================================ */

/* ---------- Page shell ---------- */
/* clip, not hidden. `overflow-x: hidden` forces the computed overflow-y to
   `auto`, which makes this element the scroll container for every sticky
   descendant — and since it is never itself scrollable, nothing could ever
   stick. That silently disabled the sticky site header AND the comparison
   table's sticky thead. `clip` crops the same way without creating a scroll
   container, so position:sticky resolves against the viewport again. */
.fs-page { overflow-x: clip; }

/* Visually hidden, still announced by screen readers. */
.fs-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;
}

.fs-skip-link {
  position: absolute;
  left: -9999px;
  top: 0;
  z-index: 1000;
  padding: var(--space-3) var(--space-5);
  background: var(--iwai-navy);
  color: var(--text-on-dark);
  border-radius: 0 0 var(--radius-md) 0;
}
.fs-skip-link:focus {
  left: 0;
  outline: none;
  box-shadow: var(--shadow-focus);
  text-decoration: none;
}

/* ---------- Layout measures ----------
   One scale for the whole page, taken by measuring the original. Every
   container and every full-width component picks a step here instead of
   inventing its own max-width, so re-proportioning the page is a change in one
   place rather than a hunt through the file.

     reading   620px   the spine: body copy, video testimonials, pull quotes
     panel     860px   playbook cards and other tinted panels
     wide     1000px   multi-column grids that need more room than the spine
     page     1075px   the outer bound; only full-bleed bands go wider

   These are CONTENT widths, not box widths. .fs-container adds
   --container-pad on top of the measure, so the number above is what the
   reader actually sees. Change --container-pad (as the ≤820px block does) and
   every container's outer width follows automatically. */
:root {
  --measure-reading:  620px;
  --measure-panel:    860px;
  --measure-wide:    1000px;
  --measure-page:    1075px;
  --container-pad:   var(--space-8);
}

/* ---------- Bands & containers ----------
   A band is full-bleed BACKGROUND ONLY. The page is white end to end — the
   original alternates nothing — so tint belongs to contained panels
   (.fs-panel, below), never to a run of alternating bands. --sand is kept for
   the footer, which is the one place the original does go full-bleed sand. */
.fs-band--white { background: var(--surface-page); }
.fs-band--sand  { background: var(--iwai-sand); }

.fs-container {
  max-width: calc(var(--measure-page) + 2 * var(--container-pad));
  margin: 0 auto;
  padding-left: var(--container-pad);
  padding-right: var(--container-pad);
}
.fs-container--wide    { max-width: calc(var(--measure-wide)    + 2 * var(--container-pad)); }
.fs-container--panel   { max-width: calc(var(--measure-panel)   + 2 * var(--container-pad)); }
.fs-container--reading { max-width: calc(var(--measure-reading) + 2 * var(--container-pad)); }
/* Older names, kept so existing markup keeps working: --mid is the wide step,
   --narrow is the reading spine. Prefer the names above in new markup. */
.fs-container--mid     { max-width: calc(var(--measure-wide)    + 2 * var(--container-pad)); }
.fs-container--narrow  { max-width: calc(var(--measure-reading) + 2 * var(--container-pad)); }

/* ---------- Tinted panels ----------
   The page's only tinting mechanism outside the footer: a CONTAINED surface
   that carries a tint, so it reads as a card sitting on a white page. Compose
   with a container to set its width, e.g.
   <div class="fs-container fs-container--panel"><div class="fs-panel fs-panel--sand"> */
.fs-panel {
  padding: var(--space-8);
  border-radius: var(--radius-lg);
}
.fs-panel--sand  { background: var(--iwai-sand); }
.fs-panel--cream { background: var(--iwai-paper); }
.fs-panel--blue  { background: var(--iwai-blue-tint); }

/* ---------- Section rhythm ----------
   ONE gap between sections, everywhere: --section-gap, split half above and
   half below so any two adjacent blocks add up to exactly it. Before this the
   page had 16 different boundary gaps ranging 64–233px, because the spacing
   came from whichever combination of --half / --half-top / --half-bottom a
   container happened to carry.

   The --half* modifiers are kept so existing markup keeps working, but they all
   now resolve to the same value — there is no "half" any more, there is just
   the gap. Prefer plain .fs-section in new markup.

   First/last child margins are zeroed: a leading <p> or a trailing .fs-prose
   would otherwise stack its own margin on top of the gap and reintroduce the
   variance this exists to remove. */
:root {
  --section-gap: 44px;
}
.fs-section,
.fs-section--half        { padding-top: calc(var(--section-gap) / 2); padding-bottom: calc(var(--section-gap) / 2); }
.fs-section--half-top    { padding-top: calc(var(--section-gap) / 2); }
.fs-section--half-bottom { padding-bottom: calc(var(--section-gap) / 2); }
/* Half above / half below only works when both halves are the same color. A
   section that opens straight after a band change carries the WHOLE gap on top,
   because the previous section's half is painted in the old background — its
   22px reads as part of the tinted block, not as space. */
.fs-section--band-top    { padding-top: var(--section-gap); }
.fs-section > :first-child { margin-top: 0; }
.fs-section > :last-child  { margin-bottom: 0; }
/* Same job one level up, for the containers that carry no .fs-section at all:
   .fs-prose leads many sections and brings its own space-8 top margin, which
   would sit on top of the gap. Section edges are the gap's business only. */
main > section > :first-child { margin-top: 0; }
main > section > :last-child  { margin-bottom: 0; }
main > section > :first-child > :first-child { margin-top: 0; }
main > section > :last-child  > :last-child  { margin-bottom: 0; }

/* ---------- Typographic helpers ---------- */
.fs-eyebrow {
  font-family: var(--font-sans);
  font-size: 16px;
  font-weight: var(--fw-semibold);
  text-transform: uppercase;
  letter-spacing: var(--ls-overline);
  color: var(--text-muted);
  margin: 0 0 var(--space-4);
}

.fs-section-title {
  font-family: var(--font-serif);
  font-size: var(--fs-display-lg);
  line-height: var(--lh-snug);
  letter-spacing: var(--ls-display);
  color: var(--iwai-navy-900);
  text-wrap: balance;
  margin: 0 0 var(--space-5);
}
.fs-section-title__muted { font-weight: var(--fw-regular); color: inherit; }

.fs-subhead {
  font-family: var(--font-serif);
  font-size: var(--fs-h1);
  line-height: var(--lh-snug);
  color: var(--iwai-navy-900);
  margin: var(--space-10) 0 var(--space-3);
}

.fs-lede {
  font-size: var(--fs-body-lg);
  line-height: var(--lh-normal);
  color: var(--text-muted);
  text-wrap: pretty;
  max-width: 60ch;
}

.fs-center { text-align: center; }
.fs-center .fs-lede { margin-left: auto; margin-right: auto; }

/* ---------- Eyebrow tag (bracketed pill) ----------
   Carried over from the AIEX hero: blue caps flanked by rules that fade out
   at the far ends. Blue on white is 7.5:1, so this one is safe as text. */
.fs-tag {
  display: flex;
  align-items: center;
  gap: var(--space-3);
  width: fit-content;
  font-family: var(--font-sans);
  font-size: 14px;
  font-weight: var(--fw-bold);
  letter-spacing: var(--ls-overline);
  text-transform: uppercase;
  color: var(--iwai-blue);
  margin: 0 auto var(--space-5);
}
.fs-tag::before,
.fs-tag::after {
  content: "";
  flex: 0 0 auto;
  width: 40px;
  height: 1px;
}
.fs-tag::before { background: linear-gradient(to right, transparent, var(--iwai-gray-400)); }
.fs-tag::after  { background: linear-gradient(to left, transparent, var(--iwai-gray-400)); }
.fs-divider-rule::before,
.fs-divider-rule::after {
  content: "";
  flex: 1 1 auto;
  max-width: 140px;
  height: 1px;
}
.fs-divider-rule::before { background: linear-gradient(to right, transparent, var(--iwai-gray-400)); }
.fs-divider-rule::after  { background: linear-gradient(to left, transparent, var(--iwai-gray-400)); }
.fs-divider-rule svg { flex: 0 0 auto; width: 32px; height: 32px; }
/* The divider's padding is the whole gap. A paragraph directly above it would
   otherwise stack its own bottom margin on that padding and push the mark off
   center — 41px above versus 24px below, everywhere this pairing occurs. */
p:has(+ .fs-divider-rule) { margin-bottom: 0; }

/* Centered section header */
.fs-head { max-width: 820px; margin: 0 auto var(--space-10); text-align: center; }
.fs-head .fs-lede { margin-left: auto; margin-right: auto; }

/* Long-form prose column */
/* Vertical rhythm only — width is the container's job, never a component's.
   .fs-prose used to carry its own max-width, which double-counted the gutter
   whenever it landed on a .fs-container (620px cap, then 32px padding inside
   it, so the copy came out at 556). Pair it with .fs-container--reading. */
.fs-prose { margin: var(--space-8) auto 0; }
.fs-prose p { color: var(--iwai-gray-700); text-wrap: pretty; }
.fs-prose strong { color: var(--iwai-navy-900); }

/* ---------- Buttons ---------- */
.fs-btn {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  gap: var(--space-2);
  font-family: var(--font-sans);
  font-weight: var(--fw-semibold);
  line-height: 1;
  border-radius: var(--radius-pill);
  border: 2px solid transparent;
  cursor: pointer;
  text-decoration: none;
  transition: transform var(--dur-fast) var(--ease-standard),
              background var(--dur-base) var(--ease-standard),
              box-shadow var(--dur-base) var(--ease-standard),
              color var(--dur-base) var(--ease-standard);
}
.fs-btn:hover { text-decoration: none; }
.fs-btn:active { transform: scale(0.97); }
.fs-btn:focus-visible { outline: none; box-shadow: var(--shadow-focus); }

.fs-btn--primary { background: var(--iwai-navy); color: var(--text-on-dark); }
.fs-btn--primary:hover { background: var(--iwai-navy-900); box-shadow: var(--shadow-md); }

.fs-btn--sm { font-size: var(--fs-body-sm); padding: 10px 18px; }
.fs-btn--md { font-size: var(--fs-body); padding: 13px 24px; }
.fs-btn--lg { font-size: var(--fs-body-lg); padding: 17px 34px; }
.fs-btn--full { width: 100%; }

/* ---------- Header ---------- */
/* Not sticky. This carried position:sticky for a long time but never actually
   pinned, because .fs-page's overflow-x:hidden made it the scroll container for
   every sticky descendant. Switching that to `clip` (so the comparison table's
   thead could pin) would have turned this on as a side effect — the page header
   is meant to scroll away. */
.fs-header {
  z-index: 100;
  background: color-mix(in srgb, var(--iwai-sand) 88%, transparent);
  backdrop-filter: saturate(1.4) blur(10px);
  border-bottom: var(--border-hairline);
}
.fs-header__inner {
  max-width: var(--container-max);
  margin: 0 auto;
  padding: var(--space-3) var(--space-8);
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: var(--space-6);
}
.fs-header__logo { display: block; height: 46px; width: auto; }
.fs-header__logo-link:focus-visible { outline: none; box-shadow: var(--shadow-focus); border-radius: var(--radius-sm); }


.fs-header__press { display: flex; align-items: center; gap: var(--space-4); }
.fs-header__press-label {
  font-size: var(--fs-overline);
  text-transform: uppercase;
  letter-spacing: var(--ls-overline);
  /* gray-600 on the sand header is 4.54:1 — only 0.04 over AA at this 12px size.
     gray-700 gives a comfortable margin for a label this small. */
  color: var(--iwai-gray-700);
}
.fs-header__press-reel { display: flex; align-items: center; gap: var(--space-5); }
.fs-header__press-logo {
  height: 30px;
  width: auto;
  filter: grayscale(1);
  opacity: 0.9;
  transition: transform var(--dur-base) var(--ease-out);
}
.fs-header__press-logo:hover { transform: rotate(-4deg); }

/* ---------- Hero ---------- */
.fs-hero--center { text-align: center; padding-top: 56px; padding-bottom: 0; }
.fs-hero__sub {
  font-size: var(--fs-body-lg);
  line-height: var(--lh-normal);
  color: var(--iwai-gray-700);
  max-width: var(--measure-reading);
  margin: 0 auto var(--space-5);
  text-wrap: pretty;
}
.fs-hero__sub strong { color: var(--iwai-navy-900); }
/* Opt-in only: a caret standing in for a section divider carries the section
   gap above it, the way .fs-divider-rule:last-child does. Without it the caret
   reads tight above and loose below, since the space under it comes from the
   section padding. Left off the hero/usecase carets, whose 24px beat is
   deliberate. */
.fs-hero__caret--section { margin-top: var(--section-gap); }

.fs-hero__note { margin-top: var(--space-6); margin-bottom: var(--space-6); }
.fs-hero__note-caret { margin: 0 auto var(--space-2); }
.fs-hero__note-caret--after { margin: var(--space-2) auto 0; }
.fs-hero__note-text {
  margin: 0;
  font-size: var(--fs-h2);
  font-weight: var(--fw-bold);
  line-height: var(--lh-snug);
  color: var(--iwai-navy-900);
}
/* Thicker rule, dropped clear of the descenders — a default underline on bold
   serif at this size sits too tight to read as emphasis. Matches AIEX. */
.fs-hero__note-text u { text-decoration-thickness: 2px; text-underline-offset: 3px; }

/* ---------- Student win cards ---------- */
/* One bold navy lead line. Used above the hero wins ("Results:") and above the
   audience paths ("Designed with precision and care for…"). The look lives here
   so the two cannot drift; each caller adds only its own spacing. */
.fs-leadline {
  font-size: var(--fs-body-lg);
  color: var(--iwai-navy-900);
  text-align: center;
}

/* ---------- Screenshot / diagram figures ---------- */
.fs-shot { margin: var(--space-8) auto; text-align: center; }
.fs-shot__img {
  display: block;
  max-width: 100%;
  height: auto;
  margin: 0 auto;
  border: var(--border-hairline);
  border-radius: var(--radius-lg);
  box-shadow: var(--shadow-sm);
  background: var(--iwai-white);
}
/* Transparent-background artwork (logos, wordmarks) needs no frame. */
.fs-shot__img--plain { border: 0; box-shadow: none; background: none; }
.fs-shot--wide .fs-shot__img { max-width: 100%; }
/* Twice the usual room below — for a shot that closes a thought before a
   testimonial, where the standard gap read as if the two belonged together. */
.fs-shot--roomy { margin-bottom: calc(var(--space-8) * 2); }
/* min() so the reading cap never beats the 100% fit — a plain max-width here
   overrides the base rule and the image runs past a phone viewport, where
   .fs-page's overflow-x: hidden silently crops it rather than scrolling. */
.fs-shot--slack .fs-shot__img { max-width: min(var(--measure-reading), 100%); }

/* Slack screenshots sit in a macOS window, so they read as "this is the Slack
   app" rather than a loose image someone pasted in. The title bar is the SAME
   .fs-slack__bar/__dot the textual Slack cards use — one definition of the
   chrome, two callers. The window owns the frame; the image inside goes flush,
   otherwise you get a border inside a border. */
.fs-shot__window {
  /* fit-content so the frame hugs its screenshot. Without it the window always
     fills the 620 cap, and a narrower image (dan-slack-reactions is 551px and
     is never upscaled) leaves a strip of empty white inside the chrome. */
  width: fit-content;
  max-width: min(var(--measure-reading), 100%);
  margin: 0 auto;
  border: var(--border-hairline);
  border-radius: var(--radius-lg);
  overflow: hidden;
  box-shadow: var(--shadow-sm);
  background: var(--iwai-white);
}
.fs-shot__window .fs-shot__img {
  max-width: 100%;
  border: 0;
  border-radius: 0;
  box-shadow: none;
}
.fs-shot__cap {
  margin: var(--space-4) auto 0;
  max-width: 60ch;
  font-size: var(--fs-body-sm);
  color: var(--iwai-gray-700);
  text-align: center;
}

/* ---------- Video testimonial (component carried over from the AIEX page) ----
   Serif punchy headline → 16:9 rounded video → italic serif detail → name.
   aspect-ratio reserves the box before the lazy iframe loads, so the embed
   costs no layout shift. */
/* Sits on the reading spine, same measure as the body copy either side of it —
   that's what makes a testimonial read as part of the argument rather than a
   sidebar. The --2 / --3 rows below shrink it; nothing else should. */
.fs-vidtest { max-width: var(--measure-reading); margin: 0 auto; text-align: center; }
.fs-vidtest__quote {
  font-family: var(--font-serif);
  font-weight: var(--fw-bold);
  font-size: 30px;
  line-height: 1.32;
  color: var(--iwai-navy);
  margin: 0 0 var(--space-6);
  text-wrap: balance;
}
.fs-vidtest__video {
  position: relative;
  aspect-ratio: 16 / 9;
  background: var(--iwai-blue-tint);
  border-radius: var(--radius-lg);
  overflow: hidden;
  box-shadow: var(--shadow-md);
}
.fs-vidtest__video iframe { position: absolute; inset: 0; width: 100%; height: 100%; border: 0; }
/* Text-only testimonials are the SAME component with a portrait standing in for
   the video frame — same 620 spine, same serif headline, same attribution.
   They alternate with the filmed ones as between-playbook proof, so they have
   to scan as one thing rather than two.

   Two deliberate departures, both because a text headline has to carry the
   whole testimonial where a filmed one only has to introduce a video:
   these average ~136 characters against ~80 for the video quotes, so at a
   shared 30px they ran 3–7 lines where the filmed ones sit at 2–3. */
.fs-vidtest--text .fs-vidtest__quote { font-size: 24px; }
.fs-vidtest--text .fs-vidtest__portrait {
  display: block;
  width: 125px;
  height: 125px;
  margin: 0 auto;
  border-radius: var(--radius-pill);
  object-fit: cover;
  object-position: top center;
  box-shadow: var(--shadow-md);
}
/* Dan / Elliott / Kathleen are stills, not embeds — same frame, <img> inside. */
.fs-vidtest__still { position: absolute; inset: 0; width: 100%; height: 100%; object-fit: cover; }
.fs-vidtest__detail { margin: var(--space-8) auto 0; }
/* Upright, not italic. These run to several paragraphs — a long italic serif
   passage is genuinely hard to read, and the emphasis is already carried by
   <strong>. The headline quote above stays as it is; this is body text. */
.fs-vidtest__detail p {
  font-family: var(--font-serif);
  /* A notch down from body-lg: upright serif reads comfortably smaller than the
     italic did, and these run to several paragraphs. */
  font-size: var(--fs-body);
  line-height: 1.62;
  color: var(--iwai-gray-700);
  margin: 0 0 var(--space-4);
  /* These quotes are broken into short paragraphs, and at 620px several of them
     landed a one- or two-character last line — Dave Waring's had three in a row
     ending on "team…", "…" and ",". `pretty` reflows the preceding lines to pull
     a word down instead. Browsers without it just wrap as before. */
  text-wrap: pretty;
}
.fs-vidtest__detail p:last-child { margin-bottom: 0; }
/* The component centers its text, which a bulleted list cannot inherit: with
   list-style: outside the markers hang off a centered ragged block and every
   line starts somewhere different (Sean S. was the visible case). Left-align
   the text, then center the list BOX so it still sits under the quote, and
   draw the marker ourselves so it tracks the first line. */
.fs-vidtest__detail ul {
  display: inline-block;
  text-align: left;
  list-style: none;
  margin: 0 0 var(--space-4);
  padding: 0;
}
.fs-vidtest__detail li {
  position: relative;
  padding-left: var(--space-6);
  margin-bottom: var(--space-3);
  font-family: var(--font-serif);
  font-size: var(--fs-body);
  line-height: 1.62;
  color: var(--iwai-gray-700);
}
.fs-vidtest__detail li:last-child { margin-bottom: 0; }
/* Deeper gold, not --iwai-yellow: that's 1.51:1 on white and the markers all
   but vanish. This clears the 3:1 non-text bar. */
.fs-vidtest__detail li::before {
  content: "";
  position: absolute;
  left: 0;
  top: 0.6em;
  width: 7px;
  height: 7px;
  border-radius: 50%;
  background: var(--iwai-warning);
}
.fs-vidtest__attr { margin-top: var(--space-5); display: flex; flex-direction: column; gap: 2px; }
.fs-vidtest__name { font-weight: var(--fw-bold); color: var(--iwai-navy); }
.fs-vidtest__role { font-size: var(--fs-body-sm); color: var(--iwai-gray-600); }

/* ---------- Slack-style card (ported from Ethical AI Foundations) ---------- */
.fs-slack {
  background: var(--iwai-white);
  border: var(--border-hairline);
  border-radius: 12px;
  box-shadow: var(--shadow-sm);
  overflow: hidden;
  transition: transform var(--dur-base) var(--ease-out), box-shadow var(--dur-base) var(--ease-out);
}
/* macOS-style title bar */
.fs-slack__bar {
  display: flex;
  align-items: center;
  gap: 8px;
  height: 30px;
  padding: 0 14px;
  background: #2b2b2b;
  flex: 0 0 auto;
}
.fs-slack__dot { width: 12px; height: 12px; border-radius: 50%; }
.fs-slack__dot--r { background: #ff5f57; }
.fs-slack__dot--y { background: #febc2e; }
.fs-slack__dot--g { background: #28c840; }
.fs-slack__msg {
  display: flex;
  align-items: flex-start;
  gap: 12px;
  padding: 16px 18px;
  background: var(--iwai-white);
}
.fs-slack__avatar {
  flex: none;
  width: 38px;
  height: 38px;
  border-radius: 9px;
  display: flex;
  align-items: center;
  justify-content: center;
  color: #fff;
  font-family: var(--font-sans);
  font-weight: var(--fw-bold);
  font-size: 16px;
}
/* Foundations used #b8860b for the third tint; white on that is only 3.2:1,
   so the initial is swapped to --iwai-success (4.9:1) rather than shipping a
   marginal one. The avatar is aria-hidden either way. */
.fs-slack__avatar--a { background: var(--iwai-blue); }
.fs-slack__avatar--b { background: var(--iwai-navy); }
.fs-slack__avatar--c { background: var(--iwai-success); }
.fs-slack__body { min-width: 0; }
.fs-slack__head { display: flex; align-items: baseline; flex-wrap: wrap; gap: 8px; margin-bottom: 4px; }
.fs-slack__name { font-weight: var(--fw-bold); font-size: 15px; color: var(--iwai-ink); }
.fs-slack__time { font-size: var(--fs-caption); color: var(--iwai-gray-600); }
.fs-slack__text { margin: 0; font-size: 15.5px; line-height: 1.55; color: var(--iwai-gray-700); }

/* ---------- Carousel ----------
   A scroll-snapped rail rather than a transform track: native touch swipe and
   keyboard scrolling come free, and with JS off it degrades to an ordinary
   scrollable row with every card still reachable. */
.fs-carousel { position: relative; }
.fs-carousel__rail {
  display: flex;
  /* center, not stretch: each card is only as tall as its own quote, and the
     varying heights sit on a shared middle line rather than a shared top. */
  align-items: center;
  gap: var(--space-5);
  overflow-x: auto;
  scroll-snap-type: x mandatory;
  scroll-behavior: smooth;
  scrollbar-width: none;
  -ms-overflow-style: none;
  /* Padding here has to clear the hover tilt without revealing the next card.
     The slides are sized to the CONTENT box, but the scrollport is the content
     box plus the padding — so at a snap point the view runs (padding-left +
     padding-right) past the third slide. Keep that total under the gap and it
     lands inside the gap, showing nothing; let it exceed the gap and the
     surplus is the fourth card peeking in. 16px total against a 20px gap
     leaves 4px of slack, and 8px a side is ample for the ~3px the tilt
     reaches. If the gap ever shrinks, this has to shrink with it. */
  padding: var(--space-2);
  /* Padding alone does not clear the tilt: snapping scrolls the padding out of
     view, so the first card lands flush against the clip edge and its rotated
     corner gets shaved. scroll-padding insets where snapping lands, which puts
     the padding back between the card and the edge. */
  scroll-padding-inline: var(--space-2);
}
.fs-carousel__rail::-webkit-scrollbar { display: none; }
.fs-carousel__rail:focus-visible { outline: none; box-shadow: var(--shadow-focus); border-radius: var(--radius-lg); }
.fs-carousel__nav {
  position: absolute;
  top: 50%;
  transform: translateY(-50%);
  z-index: 2;
  display: inline-flex;
  align-items: center;
  justify-content: center;
  width: 44px;
  height: 44px;
  padding: 0;
  border: var(--border-hairline);
  border-radius: var(--radius-pill);
  background: var(--iwai-white);
  color: var(--iwai-navy-900);
  box-shadow: var(--shadow-md);
  cursor: pointer;
  transition: background var(--dur-base) var(--ease-standard), color var(--dur-base) var(--ease-standard);
}
.fs-carousel__nav svg { width: 22px; height: 22px; }
.fs-carousel__nav:hover { background: var(--iwai-navy); color: var(--text-on-dark); }
.fs-carousel__nav:focus-visible { outline: none; box-shadow: var(--shadow-focus), var(--shadow-md); }
.fs-carousel__nav--prev { left: calc(-1 * var(--space-6)); }
.fs-carousel__nav--next { right: calc(-1 * var(--space-6)); }

/* ---------- Testimonials ---------- */
.fs-testi-grid { display: grid; gap: var(--space-6); grid-template-columns: repeat(4, minmax(0, 1fr)); align-items: start; }
.fs-testi-grid--3 { grid-template-columns: repeat(3, minmax(0, 1fr)); }

.fs-testi {
  margin: 0;
  padding: var(--space-6);
  background: var(--iwai-white);
  border: var(--border-hairline);
  border-radius: var(--radius-lg);
  box-shadow: var(--shadow-xs);
  transition: transform var(--dur-base) var(--ease-out), box-shadow var(--dur-base) var(--ease-out);
}
.fs-testi:hover { transform: translateY(-4px); box-shadow: var(--shadow-md); }
.fs-testi__attr { font-size: var(--fs-body-sm); font-weight: var(--fw-semibold); color: var(--iwai-navy-900); margin-bottom: var(--space-3); }
.fs-testi__body { margin: 0; font-size: var(--fs-body-sm); color: var(--iwai-gray-700); }
.fs-testi__body p { margin: 0 0 var(--space-3); }
.fs-testi__body p:last-child { margin-bottom: 0; }
.fs-testi__body strong { color: var(--iwai-navy-900); }

/* ---------- Personalized learning plan ---------- */
.fs-plan { display: grid; grid-template-columns: minmax(0, 380px) minmax(0, 1fr); gap: var(--space-12); align-items: center; }
.fs-plan__media { margin: 0; }
.fs-plan__img { display: block; width: 100%; height: auto; border-radius: var(--radius-lg); box-shadow: var(--shadow-md); }
.fs-plan__body { color: var(--iwai-gray-700); }
.fs-plan__body ul { padding-left: var(--space-5); }
.fs-coach {
  padding: var(--space-6);
  background: var(--iwai-white);
  border: var(--border-hairline);
  border-radius: var(--radius-lg);
  box-shadow: var(--shadow-xs);
}
.fs-coach__icon { display: block; width: 32px; height: 32px; color: var(--iwai-blue); margin-bottom: var(--space-3); }
.fs-coach__icon svg { width: 100%; height: 100%; }
.fs-coach__title { font-family: var(--font-serif); font-size: var(--fs-h3); color: var(--iwai-navy-900); margin: 0 0 var(--space-3); }
.fs-coach p { margin: 0; color: var(--iwai-gray-700); font-size: var(--fs-body-sm); }

/* ---------- FAQ ---------- */
/* The list sits on the reading spine even though the section head keeps the
   wider measure — a question at 1000px reads as a banner, not a line of copy. */
.fs-faq {
  display: flex;
  flex-direction: column;
  gap: var(--space-3);
  margin: var(--space-8) auto 0;
  max-width: var(--measure-reading);
  width: 100%;
}
.fs-faq__item {
  background: var(--iwai-white);
  border: var(--border-hairline);
  border-radius: var(--radius-md);
  box-shadow: var(--shadow-xs);
  overflow: hidden;
}
.fs-faq__q {
  width: 100%;
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: var(--space-4);
  background: none;
  border: none;
  cursor: pointer;
  text-align: left;
  font-family: var(--font-sans);
  font-size: var(--fs-body-lg);
  font-weight: var(--fw-semibold);
  color: var(--iwai-ink);
  padding: var(--space-5) var(--space-6);
}
.fs-faq__q:focus-visible { outline: none; box-shadow: var(--shadow-focus); border-radius: var(--radius-sm); }
.fs-faq__sign { font-size: var(--fs-h2); font-weight: var(--fw-regular); color: var(--iwai-blue); line-height: 1; flex: 0 0 auto; }
.fs-faq__a { display: none; padding: 0 var(--space-6) var(--space-6); color: var(--iwai-gray-700); }
.fs-faq__a p { margin: 0; }
.fs-faq__a p + p { margin-top: var(--space-3); }
.fs-faq__a ul { margin: var(--space-3) 0 0; padding-left: var(--space-5); }
.fs-faq__a li { margin-bottom: var(--space-2); color: var(--iwai-gray-700); }
.fs-faq__a strong { color: var(--iwai-navy-900); }
.fs-faq__item[data-open="true"] .fs-faq__a { display: block; }

/* ---------- Level descriptions ---------- */

/* ---------- Comparison table ---------- */
/* The level summaries above are prose now, not a card grid, so the table needs
   its own breathing room where the grid used to supply a bottom margin. */
/* No overflow here on purpose. overflow-x:auto forces the computed overflow-y
   to auto as well, which made this element the scroll container for the sticky
   thead below — so the header scrolled away with the table instead of pinning
   to the viewport. The table is all percentage widths and collapses to a card
   list at 820px, so it never needed the horizontal scroller. */
.fs-compare-wrap { margin-top: var(--space-12); }
.fs-compare { width: 100%; border-collapse: collapse; font-size: var(--fs-body-sm); }
.fs-compare thead th {
  position: sticky;
  top: 0;
  z-index: 2;
  padding: var(--space-4);
  background: var(--iwai-navy);
  color: var(--text-on-dark);
  font-family: var(--font-serif);
  font-size: var(--fs-h3);
  text-align: center;
  vertical-align: middle;
}
.fs-compare thead th:first-child { background: var(--iwai-navy-900); width: 40%; }
.fs-compare tbody th {
  text-align: left;
  font-weight: var(--fw-regular);
  color: var(--iwai-gray-700);
  padding: var(--space-4);
  vertical-align: top;
}
.fs-compare tbody th strong { color: var(--iwai-navy-900); }
.fs-compare tbody tr:nth-child(odd) { background: var(--iwai-sand-200); }
.fs-compare tbody td { text-align: center; vertical-align: middle; padding: var(--space-4); width: 20%; }
.fs-compare tbody td::after {
  display: inline-block;
  font-size: 20px;
  line-height: 1;
  font-weight: var(--fw-bold);
}
.fs-compare tbody td.is-yes::after { content: "\2713"; color: var(--iwai-success); }
.fs-compare tbody td.is-no::after  { content: "\2715"; color: var(--iwai-danger); }
/* Third state the original carried on exactly one row (FEATURED Directory
   Listing / Hybrid Consulting): a neutral filled dot, not a check or a cross. */
.fs-compare tbody td.is-partial::after { content: "\25CF"; color: var(--iwai-gray-400); font-size: 15px; }
.fs-compare__prices td { vertical-align: top; padding: var(--space-6) var(--space-4); }
.fs-compare__price { margin: 0 0 var(--space-1); font-size: var(--fs-body); color: var(--iwai-navy-900); }
.fs-compare__perday { margin: 0 0 var(--space-4); font-size: var(--fs-caption); color: var(--iwai-gray-700); }
/* Same idea in the table: the cells are vertical-align:top, so Hybrid's missing
   per-day line floated its button 36px above the other two. Reserve the height
   of the two-line stack (26 + 4 + 20 + 16) and center the one line in it. */
.fs-compare__price:not(:has(+ .fs-compare__perday)) {
  display: flex;
  align-items: center;
  min-height: 62px;
}
.fs-compare__alt { display: block; margin-top: var(--space-3); font-size: var(--fs-caption); font-weight: var(--fw-semibold); }

/* Payment method icons */
.fs-payments {
  display: flex;
  align-items: center;
  justify-content: center;
  flex-wrap: wrap;
  gap: 12px;
  margin-top: 36px;
}
.fs-payment-icon {
  height: 34px;
  width: auto;
  border-radius: 5px;
  border: 1px solid rgba(9, 54, 91, 0.12);
  box-shadow: var(--shadow-xs);
}
/* Payment-plan note + support line, ported verbatim from the AI Executive
   System page so the foot of both pricing sections reads identically. */
.fs-plans-note { max-width: 760px; margin: var(--space-8) auto 0; text-align: center; font-size: var(--fs-body-sm); color: var(--text-muted); }
.fs-plans-note strong { color: var(--iwai-navy-900); }
.fs-pricing__support {
  text-align: center;
  max-width: 620px;
  margin: 28px auto 0;
  font-size: var(--fs-body-sm);
  line-height: 1.65;
  color: var(--iwai-gray-700);
}
.fs-pricing__contact { text-align: center; margin: var(--space-2) auto 0; font-size: var(--fs-body-sm); font-weight: var(--fw-semibold); color: var(--iwai-ink); }
.fs-pricing__contact a { color: var(--iwai-blue); text-decoration: none; }
.fs-pricing__contact a:hover { text-decoration: underline; }
.fs-contact-item { white-space: nowrap; }
.fs-contact-sep { margin: 0 8px; color: var(--iwai-gray-600); }
.fs-tp { margin-top: var(--space-8); }

/* ---------- Editorial letter ---------- */
.fs-letter { font-size: var(--fs-body-lg); line-height: var(--lh-relaxed); color: var(--iwai-ink); }
.fs-letter p { text-wrap: pretty; }
.fs-letter ul { padding-left: var(--space-6); }
.fs-letter li { margin-bottom: var(--space-2); }
/* The PS is its own beat at the end of the letter — an extra 1em of air above
   and below sets it apart from the sign-off and from the pricing that follows.
   The closing line needs the container class to outrank `.fs-section >
   :last-child` and `main > section > :last-child > :last-child`, both of which
   zero trailing margins. */
.fs-letter__ps { margin-top: 2em; }
.fs-container.fs-letter .fs-letter__ps-end { margin-bottom: 1em; }

.fs-letter__sig { display: block; width: 200px; height: auto; margin: var(--space-8) 0 var(--space-2); }
.fs-letter__signoff { font-family: var(--font-serif); color: var(--iwai-navy-900); margin: 0 0 var(--space-6); }

/* ---------- Footer ----------
   Ported verbatim from the AI Executive System page so the two sites end on the
   identical mark: logo alone, then a legal line. Keep them in sync. */
.fs-footer { background: var(--iwai-sand); }
.fs-footer__inner {
  max-width: var(--container-max);
  margin: 0 auto;
  padding: 40px 32px 24px;
  display: flex;
  align-items: center;
  justify-content: space-between;
  flex-wrap: wrap;
  gap: 20px;
}
.fs-footer__logo-link { display: inline-flex; }
.fs-footer__logo { height: 32px; width: auto; display: block; }
.fs-footer__legal {
  max-width: var(--container-max);
  margin: 0 auto;
  padding: 6px 32px 40px;
  display: flex;
  flex-direction: column;
  gap: 8px;
  font-size: 13px;
  /* gray-600 on the sand footer is 4.54:1 — 0.04 over AA at 13px. gray-700
     gives real headroom for legal text this small. */
  color: var(--iwai-gray-700);
}
.fs-footer__policies { display: flex; flex-wrap: wrap; align-items: center; gap: 4px 10px; }
.fs-footer__policies a { color: var(--iwai-gray-700); text-decoration: none; white-space: nowrap; }
.fs-footer__policies a:hover { color: var(--iwai-ink); text-decoration: underline; }
.fs-footer__sep { color: var(--iwai-gray-700); }

/* ---------- Floating section nav ----------
   Ported from the WordPress page's "consultancy-floating-nav", rebuilt rather
   than copied. The original translated the panel off-screen and then pushed the
   handle back with a second, opposite transform; here the panel and handle are
   one flex row and the whole thing shifts left by exactly the panel width, so
   the handle lands at x=0 with a single transform and nothing to keep in sync.

   Three states, all on the root: .is-hidden (before the reveal, and the state it
   ships in so there is nothing focusable without JS), .is-closed (handle only),
   neither (open). Visibility — not just opacity — does the hiding, so the links
   leave the tab order and the accessibility tree when the panel is away. */
.fs-toc {
  --toc-w: 264px;
  position: fixed;
  left: 0;
  /* Bottom corner, not mid-edge. Vertically centered it landed exactly at eye
     level — measured, the handle's center and the viewport's middle were the
     same pixel — which is what made it intrusive while reading. The corner also
     keeps it off the text column, which it overlapped at phone widths.
     Anchoring by `bottom` rather than centering also means no vertical transform,
     which is half of the iOS repaint fix noted on the panel below. */
  bottom: var(--space-6);
  z-index: 90;              /* over the countdown (60), under the header (100) */
  display: flex;
  align-items: flex-end;    /* a closed panel still has height; pin to the edge */
  transform: translateX(0);
  transition: transform var(--dur-slow, 320ms) var(--ease-out), opacity var(--dur-slow, 320ms) var(--ease-out);
}
.fs-toc.is-closed { transform: translateX(calc(var(--toc-w) * -1)); }
.fs-toc.is-hidden {
  /* Sits a little further out than "closed" so the reveal has somewhere to
     travel from, and is fully inert until then. */
  transform: translateX(calc((var(--toc-w) + 60px) * -1));
  opacity: 0;
  visibility: hidden;
  pointer-events: none;
}
.fs-toc__panel {
  width: var(--toc-w);
  /* dvh so the cap tracks the visual viewport as iOS collapses its URL bar; a
     70vh panel can exceed the visible area while the bar is up, which is when
     the missing-background artifact showed. vh first as the fallback. */
  max-height: 70vh;
  max-height: 70dvh;
  overflow-y: auto;
  overscroll-behavior: contain;
  padding: var(--space-5);
  background: var(--iwai-white);
  border: var(--border-hairline);
  border-left: 0;
  border-radius: 0 var(--radius-lg) var(--radius-lg) 0;
  box-shadow: var(--shadow-lg);
  /* The other half: give the panel its own compositing layer so its background
     and shadow are painted as one unit with its content, instead of being left
     to a parent layer that iOS sizes from the pre-scroll state. */
  transform: translateZ(0);
  -webkit-backface-visibility: hidden;
          backface-visibility: hidden;
}
/* Closed means gone, not merely translated: without this the links stay
   tabbable off-screen and tabbing scrolls the page sideways. */
.fs-toc.is-closed .fs-toc__panel { visibility: hidden; }
.fs-toc__title {
  margin: 0 0 var(--space-4);
  padding-bottom: var(--space-3);
  border-bottom: var(--border-hairline);
  font-family: var(--font-serif);
  font-size: var(--fs-body);
  color: var(--iwai-navy-900);
}
.fs-toc__list { list-style: none; margin: 0 0 var(--space-5); padding: 0; }
.fs-toc__list a {
  display: block;
  padding: var(--space-2) 0 var(--space-2) var(--space-3);
  border-left: 2px solid transparent;
  font-size: var(--fs-body-sm);
  color: var(--iwai-gray-700);
  text-decoration: none;
}
.fs-toc__list a:hover { color: var(--iwai-navy-900); }
/* Scroll-spy state. aria-current is the source of truth so the styling and the
   announcement can't drift apart. */
.fs-toc__list a[aria-current] {
  color: var(--iwai-navy-900);
  font-weight: var(--fw-semibold);
  border-left-color: var(--iwai-blue);
}
.fs-toc__cta { text-decoration: none; }
/* A quiet chip rather than a solid navy block. Solid navy measured 15.1:1
   against the page — louder than the body copy it sits beside, which is the
   wrong hierarchy for a control you only occasionally want. Full contrast
   returns on hover and focus. */
.fs-toc__toggle {
  flex: 0 0 auto;
  display: inline-flex;
  align-items: center;
  justify-content: center;
  gap: var(--space-2);
  width: 44px;
  height: 44px;
  padding: 0;
  background: var(--iwai-white);
  color: var(--iwai-navy-900);
  border: var(--border-hairline);
  border-left: 0;
  border-radius: 0 var(--radius-md) var(--radius-md) 0;
  box-shadow: var(--shadow-sm);
  opacity: 0.72;
  cursor: pointer;
  transition: opacity var(--dur-base) var(--ease-out), background var(--dur-base) var(--ease-out);
}
.fs-toc__toggle:hover { opacity: 1; background: var(--iwai-sand); }
.fs-toc__toggle:focus-visible { opacity: 1; outline: none; box-shadow: var(--shadow-focus); }
.fs-toc__toggle svg { width: 20px; height: 20px; }
/* Visually hidden on desktop, where the icon and position carry it; shown as
   the pill's label on phones. Its own class, so .fs-sr-only keeps its meaning. */
.fs-toc__label {
  position: absolute;
  width: 1px; height: 1px;
  padding: 0; margin: -1px;
  overflow: hidden; clip: rect(0 0 0 0); white-space: nowrap; border: 0;
}@media (max-width: 768px) {

  /* Phones get a labeled pill at the bottom center instead of an edge tab:
     it's in the thumb zone, clear of the text column entirely, and reads as a
     control because it has words on it. Deliberately allowed to cover the
     countdown — at this width there is no room to sit beside it, and the nav is
     the thing being interacted with. */
  .fs-toc {
    --toc-w: min(78vw, 300px);
    left: 50%;
    bottom: var(--space-5);
    flex-direction: column;
    align-items: center;
    transform: translateX(-50%);
  }
  /* The pill itself never moves; only the panel above it comes and goes. */
  .fs-toc.is-closed { transform: translateX(-50%); }
  .fs-toc.is-hidden { transform: translate(-50%, var(--space-6)); }

  /* Floated above the pill rather than sitting in the column: a closed panel
     that still occupied row height would push the pill up off the bottom edge. */
  .fs-toc__panel {
    position: absolute;
    bottom: calc(100% + var(--space-3));
    left: 50%;
    transform: translateX(-50%) translateZ(0);
    width: var(--toc-w);
    max-height: 62vh;
    max-height: 62dvh;
    padding: var(--space-4);
    border-left: var(--border-hairline);
    border-radius: var(--radius-lg);
    transition: opacity var(--dur-base) var(--ease-out);
  }
  .fs-toc.is-closed .fs-toc__panel { opacity: 0; }

  .fs-toc__toggle {
    width: auto;
    height: 44px;
    padding: 0 var(--space-5);
    border: var(--border-hairline);
    border-radius: var(--radius-pill);
    box-shadow: var(--shadow-md);
    opacity: 1;
  }
  .fs-toc__label {
    position: static;
    width: auto; height: auto;
    margin: 0; clip: auto; overflow: visible;
    font-size: var(--fs-body-sm);
    font-weight: var(--fw-semibold);
  }

}
@media (prefers-reduced-motion: reduce) {

  /* Still reveals, just without the travel. */
  .fs-toc { transition: none; }

}


/* ---------- Enrollment countdown ---------- */
.fs-countdown {
  position: fixed;
  right: var(--space-6);
  bottom: var(--space-6);
  z-index: 60;
  width: 268px;
  padding: var(--space-5) var(--space-5) var(--space-4);
  background: var(--iwai-white);
  border: var(--border-hairline);
  border-top: 3px solid var(--iwai-warning);
  border-radius: var(--radius-lg);
  box-shadow: var(--shadow-lg);
  text-align: center;
  /* Hidden with visibility, not display:none — you cannot transition out of
     display:none, and visibility also keeps it out of the a11y tree. */
  opacity: 0;
  visibility: hidden;
  pointer-events: none;
  transform: translateY(12px);
  transition: opacity var(--dur-slow) var(--ease-out), transform var(--dur-slow) var(--ease-out),
              visibility 0s linear var(--dur-slow);
}
.fs-countdown.is-visible {
  opacity: 1;
  visibility: visible;
  pointer-events: auto;
  transform: translateY(0);
  transition-delay: 0s;
}
.fs-countdown__label {
  margin: 0 0 var(--space-3);
  font-size: var(--fs-body-sm);
  font-weight: var(--fw-bold);
  color: var(--iwai-navy-900);
}
.fs-countdown__clock { display: flex; justify-content: center; gap: var(--space-2); margin: 0 0 var(--space-3); }
.fs-countdown__clock span {
  display: flex;
  flex-direction: column;
  align-items: center;
  min-width: 46px;
  padding: 6px 4px;
  background: var(--iwai-sand-200);
  border-radius: var(--radius-sm);
}
.fs-countdown__clock b {
  font-family: var(--font-serif);
  font-size: var(--fs-h3);
  line-height: 1.05;
  color: var(--iwai-navy-900);
  /* tabular figures keep the seconds from nudging the layout each tick */
  font-variant-numeric: tabular-nums;
  font-feature-settings: "tnum";
}
.fs-countdown__clock i {
  margin-top: 2px;
  font-style: normal;
  font-size: var(--fs-overline);
  text-transform: uppercase;
  letter-spacing: var(--ls-overline);
  color: var(--iwai-gray-700);
}
.fs-countdown__deadline { margin: 0; font-size: var(--fs-caption); color: var(--iwai-gray-700); }
.fs-countdown__close {
  position: absolute;
  top: 6px;
  right: 6px;
  display: inline-flex;
  align-items: center;
  justify-content: center;
  width: 28px;
  height: 28px;
  padding: 0;
  border: 0;
  border-radius: var(--radius-pill);
  background: none;
  color: var(--iwai-gray-700);
  cursor: pointer;
}
.fs-countdown__close svg { width: 15px; height: 15px; }
.fs-countdown__close:hover { background: var(--iwai-sand-200); color: var(--iwai-navy-900); }
.fs-countdown__close:focus-visible { outline: none; box-shadow: var(--shadow-focus); }


/* ============================================================
   RESPONSIVE — widest first, narrowest last, so that among
   equal-specificity rules the narrower query wins wherever both
   match. Where an override must beat a WIDER block regardless of
   order, its specificity is raised with a parent class (§4).
   ============================================================ */

/* ---------- ≤960px : 4-up and 5-up grids step down ---------- */
@media (max-width: 960px) {
  .fs-wins { grid-template-columns: repeat(2, minmax(0, 1fr)); }
  .fs-freedoms { grid-template-columns: repeat(2, minmax(0, 1fr)); }
  .fs-testi-grid { grid-template-columns: repeat(2, minmax(0, 1fr)); }
  .fs-skillareas { grid-template-columns: repeat(2, minmax(0, 1fr)); }
  .fs-header__press-reel {
    position: relative;
    width: 88px;
    height: 32px;
    gap: 0;
  }
  .fs-header__press-reel .fs-header__press-logo {
    position: absolute;
    top: 50%;
    left: 50%;
    transform: translate(-50%, -50%);
    height: auto;
    max-width: 88px;
    max-height: 28px;
    opacity: 0;
    transition: opacity 600ms var(--ease-out);
    pointer-events: none;
  }
  .fs-header__press-reel .fs-header__press-logo.is-active { opacity: 0.9; }
}

/* ---------- ≤820px : two-column layouts collapse ---------- */
@media (max-width: 820px) {
  /* Redefining the tokens rather than the properties keeps every container's
     calc()-derived max-width and every section's calc()-derived padding in step
     — one place to change, no per-class overrides to keep in sync. 32px is the
     same ~0.73 ratio the old 88 → 64 step used. */
  :root {
    --container-pad: var(--space-5);
    --section-gap: var(--space-8);
  }

  .fs-container .fs-layers { grid-template-columns: minmax(0, 1fr); gap: var(--space-6); }
  .fs-container .fs-bio { grid-template-columns: minmax(0, 1fr); gap: var(--space-8); }
  .fs-container .fs-plan { grid-template-columns: minmax(0, 1fr); gap: var(--space-8); }
  .fs-container .fs-playbook__cols { grid-template-columns: minmax(0, 1fr); gap: var(--space-8); }
  /* The evidence rail can't stay a rail on one column — screenshots drop below
     the steps and spread back out into a strip. */
  .fs-container .fs-playbook__row--how { grid-template-columns: minmax(0, 1fr); }
  .fs-container .fs-playbook__row--how .fs-lessons { grid-template-columns: repeat(auto-fit, minmax(220px, 1fr)); margin-top: var(--space-6); }
  .fs-container .fs-steps { grid-template-columns: minmax(0, 1fr); }
  .fs-container .fs-coach-grid { grid-template-columns: minmax(0, 1fr); }
  .fs-container .fs-mythtruth { grid-template-columns: minmax(0, 1fr); }
  .fs-container .fs-sets { grid-template-columns: minmax(0, 1fr); }
  .fs-container .fs-tiers { grid-template-columns: minmax(0, 1fr); }
  .fs-container .fs-skillareas { grid-template-columns: minmax(0, 1fr); }
  .fs-container .fs-guarantee3 { grid-template-columns: minmax(0, 1fr); }
  .fs-container .fs-vidtests { grid-template-columns: minmax(0, 1fr); gap: var(--space-12); }
  .fs-container .fs-vidtests--3 { grid-template-columns: minmax(0, 1fr); }

  /* Same treatment for the ROI Problem Journey: six columns can't survive a
     phone, so subgrid is dropped and each timeframe becomes its own stacked
     block, with the two row labels reading as an intro above them. The arrows
     point across a table that no longer exists, so they go. */
  .fs-container .fs-journey__grid {
    grid-template-columns: minmax(0, 1fr);
    grid-template-rows: none;
    row-gap: var(--space-6);
  }
  .fs-container .fs-journey__col { grid-row: auto; grid-template-rows: none; text-align: left; }

  /* Three orbs side by side leave the smallest unreadable on a phone. One per
     row, orb beside its figures rather than above them, so the scale comparison
     survives as a left-edge column you read down. */
  .fs-economy__row { grid-template-columns: minmax(0, 1fr); gap: var(--space-10); }
  /* Orb stays ABOVE its text rather than beside it: side by side, the smallest
     circle gets squeezed below the size that can hold the figure it now owns. */
  .fs-economy__orbwrap { height: auto; }

  /* Five columns is unreadable on a tablet/phone. Drop subgrid and give each
     step its own row: chevron + letter on the left, label + detail on the
     right. Specificity raised with .fs-container so these keep beating the
     base rules whatever order the blocks end up in (§4). */
  .fs-container .fs-proof {
    grid-template-columns: minmax(0, 1fr);
    grid-template-rows: none;
    border-bottom: 0;
  }
  .fs-container .fs-proof__step {
    grid-row: auto;
    grid-template-rows: none;
    grid-template-columns: 120px minmax(0, 1fr);
    grid-template-areas: "chev label" "letter detail";
    align-items: center;
    column-gap: var(--space-5);
    padding: var(--space-5) 0;
    border-bottom: 1px dashed var(--border-strong);
    text-align: left;
  }
  .fs-container .fs-proof__chev   { grid-area: chev; }
  .fs-container .fs-proof__letter { grid-area: letter; }
  .fs-container .fs-proof__label  { grid-area: label; }
  .fs-container .fs-proof__detail { grid-area: detail; }
  .fs-container .fs-proof__chev,
  .fs-container .fs-proof__letter,
  .fs-container .fs-proof__label,
  .fs-container .fs-proof__detail {
    align-items: flex-start;
    padding: var(--space-1) 0;
    border-bottom: 0;
  }
  .fs-container .fs-proof__letter { font-size: 44px; }

  /* The icon-in-arrow does not survive the drop to two columns: the chevron is
     a wide horizontal shape and this layout is vertical. Hide it and let the
     letter carry the left column across both rows. */
  .fs-container .fs-proof__chev { display: none; }
  .fs-container .fs-proof__step {
    grid-template-columns: 72px minmax(0, 1fr);
    grid-template-areas: "letter label" "letter detail";
  }
  .fs-container .fs-proof__letter { align-self: center; }

  /* ---- Touch targets: 44px minimum on anything tappable ---- */
  .fs-btn { min-height: 44px; display: inline-flex; align-items: center; justify-content: center; }
  /* Secondary payment links are 20-23px of text. Pad them out to 44 without
     moving the text — the extra height is hit area, centered on the label. */
  .fs-tier__alt,
  .fs-compare__alt {
    display: flex;
    align-items: center;
    justify-content: center;
    min-height: 44px;
  }
  /* The dismiss control keeps its 28px glyph; the pseudo-element grows the hit
     area to 44 without changing the widget's corner layout. */
  .fs-countdown__close { position: absolute; }
  .fs-countdown__close::after {
    content: "";
    position: absolute;
    top: 50%;
    left: 50%;
    width: 44px;
    height: 44px;
    transform: translate(-50%, -50%);
  }

  /* Two cards across, and the arrows come inside the rail — at this width
     there is no gutter left to hang them in. */
  .fs-carousel__rail > .fs-slack-slide { flex: 0 0 calc((100% - var(--space-5)) / 2); }
  .fs-carousel__nav--prev { left: 0; }
  .fs-carousel__nav--next { right: 0; }

  .fs-playbook { --pb-pad: var(--space-5); }
  .fs-playbook__head { padding-top: var(--space-5); padding-bottom: var(--space-5); }
  .fs-bio__media, .fs-plan__media { max-width: 420px; }


  /* The comparison table stops being a table and becomes one card per feature:
     each cell carries its tier name in data-tier, so the header row is not
     needed to read it.

     No zebra here. Striping is a device for scanning across a wide row; once
     each row is its own card it just tints half of them at random — and worse,
     it tinted them the SAME sand as the feature-name strip inside, so on every
     odd card the header was invisible against the card it was heading. Every
     card is now identical, and the strip is the only tinted thing in it. */
  .fs-compare thead { display: none; }
  .fs-compare, .fs-compare tbody, .fs-compare tfoot, .fs-compare tr { display: block; width: 100%; }
  .fs-compare tbody tr, .fs-compare tfoot tr {
    margin-bottom: var(--space-4);
    background: var(--iwai-white);
    border: var(--border-hairline);
    border-radius: var(--radius-lg);
    box-shadow: var(--shadow-xs);
    overflow: hidden;
  }
  .fs-compare tbody tr:nth-child(odd) { background: var(--iwai-white); }
  .fs-compare tbody th, .fs-compare tfoot th { display: block; background: var(--iwai-sand-200); }
  .fs-compare tfoot th:has(.fs-sr-only:only-child) { display: none; }

  /* The three tiers share one row rather than stacking, which takes a feature
     card from ~290px to ~200px. Three equal columns fit their labels on one
     line at this size, "Hybrid Consulting" included. */
  .fs-compare tbody tr {
    display: grid;
    grid-template-columns: repeat(3, minmax(0, 1fr));
  }
  .fs-compare tbody th {
    grid-column: 1 / -1;
    border-bottom: var(--border-hairline);
  }
  .fs-compare tbody td {
    display: flex;
    flex-direction: column;
    align-items: center;
    justify-content: flex-start;
    gap: var(--space-1);
    width: auto;
    padding: var(--space-3) var(--space-2);
    text-align: center;
    border: 0;
  }
  .fs-compare tbody td + td { border-left: var(--border-hairline); }
  .fs-compare tbody td::before {
    content: attr(data-tier);
    display: block;
    font-size: var(--fs-caption);
    font-weight: var(--fw-semibold);
    line-height: 1.25;
    color: var(--iwai-gray-700);
    text-wrap: balance;
  }

  /* The price row keeps stacking: each tier there carries an amount, a button
     and an alternative payment link, which will not survive a third of a phone. */
  .fs-compare tfoot td {
    display: block;
    width: 100%;
    text-align: left;
    border-top: var(--border-hairline);
  }
  .fs-compare tfoot td::before {
    content: attr(data-tier);
    display: block;
    margin-bottom: var(--space-3);
    font-weight: var(--fw-semibold);
    color: var(--iwai-navy-900);
  }
}

/* ---------- ≤620px : phone ---------- */
@media (max-width: 620px) {
  .fs-contact-item { display: block; }
  .fs-contact-sep { display: none; }
  .fs-sub-br { display: none; }

  /* 32px of panel padding costs ~19% of a 375px viewport on top of the
     container gutter, so the tint hugs its contents more closely on a phone. */
  .fs-panel { padding: var(--space-5); }

  .fs-container .fs-wins { grid-template-columns: minmax(0, 1fr); }
  .fs-container .fs-wins--3 { grid-template-columns: minmax(0, 1fr); }
  /* One column already, so the feature card only needs to stop being oversized. */
  /* Keep the tight top pad from the base rule — stacked single-column, she
     already reads as a separate beat without extra room above. */
  .fs-container .fs-win--feature { padding: var(--space-2) var(--space-5) var(--space-5); }
  .fs-container .fs-win--feature .fs-win__avatar { width: 125px; height: 125px; }
  .fs-container .fs-win--feature .fs-win__quote p:first-child { font-size: var(--fs-h3); }
  .fs-container .fs-freedoms { grid-template-columns: minmax(0, 1fr); }
  .fs-container .fs-testi-grid { grid-template-columns: minmax(0, 1fr); }
  .fs-container .fs-lessons { grid-template-columns: minmax(0, 1fr); }

  .fs-carousel__rail > .fs-slack-slide { flex: 0 0 100%; }
  .fs-container .fs-story { grid-template-columns: minmax(0, 1fr); }
  .fs-container .fs-story__avatar { width: 64px; height: 64px; }
  .fs-container .fs-icard { grid-template-columns: minmax(0, 1fr); }

  .fs-section-title { font-size: var(--fs-display-md); }
  .fs-statement, .fs-usecase__statement { font-size: var(--fs-h1); }
  .fs-wordmark { font-size: var(--fs-display-lg); }
  /* Too long to hold one line at a legible size here. Let it wrap to two and
     drop the flanking rules — centered against a two-line block they stop
     reading as rules and just look like stray dashes. */
  .fs-tag {
    display: block;
    font-size: 12px;
    letter-spacing: 0.1em;
    text-align: center;
    max-width: 30ch;
  }
  .fs-tag::before, .fs-tag::after { content: none; }
  /* Scale the testimonial headline down so it doesn't compete with section
     titles. Tag + class (h2.fs-vidtest__quote) so it keeps winning even if
     these blocks are ever reordered — see §4. */
  h2.fs-vidtest__quote { font-size: 22px; line-height: 1.3; margin-bottom: var(--space-5); }
  .fs-playbook__title { font-size: var(--fs-h1); }
  .fs-phase__title { font-size: var(--fs-h2); gap: var(--space-3); }
  .fs-phase__letter { width: 40px; height: 40px; font-size: var(--fs-h3); }
  .fs-hero--center { padding-top: 32px; }

  .fs-countdown {
    right: var(--space-4);
    left: var(--space-4);
    bottom: var(--space-4);
    width: auto;
    padding: var(--space-4);
  }
  .fs-countdown__clock span { min-width: 0; flex: 1; }
}

/* ---------- ≤520px : smallest phones ---------- */
@media (max-width: 520px) {
  .fs-footer__inner { flex-direction: column; gap: var(--space-6); }
  .fs-container .fs-playbook__head { padding-top: var(--space-5); padding-bottom: var(--space-5); }
  .fs-header__inner { padding-left: var(--space-5); padding-right: var(--space-5); }
}

/* ---------- Reduced motion ---------- */
@media (prefers-reduced-motion: reduce) {
  *,
  *::before,
  *::after {
    animation-duration: 0.001ms !important;
    animation-iteration-count: 1 !important;
    transition-duration: 0.001ms !important;
    scroll-behavior: auto !important;
  }
  .fs-win:hover, .fs-testi:hover, .fs-freedom:hover, .fs-header__press-logo:hover { transform: none !important; }

  /* Exception: a cross-fade is opacity, not movement. Accessibility guidance
     recommends fading as the SUBSTITUTE for motion, so these keep fading;
     anything that also traveled is pinned and only fades. */
  .fs-header__press-reel .fs-header__press-logo { transition-duration: 600ms !important; }
  .fs-countdown {
    transition: opacity var(--dur-slow) var(--ease-out) !important;
    transform: none !important;
  }
  .fs-countdown.is-visible { transform: none !important; }
  /* The carousel stops auto-advancing in JS; this also kills the smooth
     scroll so the arrows jump instead of animating. */
  .fs-carousel__rail { scroll-behavior: auto !important; }
}@media (max-width: 820px) {


}
@media (max-width: 820px) {


}


/* A panel wrapping a diagram that already has its own internal padding does not
   need the full space-8 — it just pushes the figure away from its own frame. */
.fs-panel--tight { padding-top: var(--space-2); padding-bottom: var(--space-2); }

/* Narrow screenshots that would look overblown at the full reading measure.
   The window is capped to match via :has(), so the macOS chrome hugs the image
   instead of framing empty white beside it. */
.fs-shot__img--sm { max-width: min(400px, 100%); }
.fs-shot__window:has(.fs-shot__img--sm) { max-width: min(400px, 100%); }
/* Two-thirds of the spine, derived rather than hard-coded so it tracks
   --measure-reading if that ever changes. */
.fs-shot__img--2-3 { max-width: min(calc(var(--measure-reading) * 2 / 3), 100%); }
.fs-shot__window:has(.fs-shot__img--2-3) { max-width: min(calc(var(--measure-reading) * 2 / 3), 100%); }

/* .fs-vidtest carries no bottom margin — inside a testimonial block the pieces
   set their own rhythm. Dropped into running copy, though, the next paragraph
   butts straight against the video frame. Restore the normal 1em paragraph gap
   so the line below the embed sits like the line above it. */
.fs-container--reading > .fs-vidtest + p { margin-top: 1em; }

/* Reaction strips are just a row of emoji — no frame, no chrome, no shadow.
   They read as part of the page rather than as a screenshot of something.
   Overrides .fs-shot__img's border/shadow, which every other screenshot wants. */
/* Doubled class (0,2,0) on purpose: .fs-shot--slack .fs-shot__img is also two
   selectors, so a single-class rule here loses to it whatever the source order
   — the cap silently did nothing on the two Slack reaction strips. */
.fs-shot__img.fs-shot__img--bare {
  max-width: min(400px, 100%);
  border: 0;
  border-radius: 0;
  box-shadow: none;
  background: none;
}@media (prefers-reduced-motion: reduce) {


}


/* A divider that OPENS a container already has the section gap above it. Its
   own top padding stacks on that and pushes the rule off-center — before this
   the Meet Rob divider sat 68px below the copy and 24px above the bio. Zero the
   top and let the bottom carry a full gap, so the rule lands equidistant. */
.fs-container > .fs-divider-rule:first-child {
  padding-top: 0;
  padding-bottom: var(--section-gap);
}
/* And the mirror: one that CLOSES a container has the section gap below it, so
   its own bottom padding is what pushes the rule off-center. Measured 24px above
   and 68px below before this. */
.fs-container > .fs-divider-rule:last-child {
  padding-top: var(--section-gap);
  padding-bottom: 0;
}
/* The last element before it still contributes its own bottom margin on top of
   that padding, which measured 61px above the rule against 44px below. The gap
   is the divider's business, so the neighbor's margin goes. */
.fs-container > :has(+ .fs-divider-rule:last-child) { margin-bottom: 0; }

/* A plan block with no media is a single column — otherwise the copy inherits
   the 380px image track and reads as a narrow ribbon beside empty space. */
.fs-plan:not(:has(.fs-plan__media)) { grid-template-columns: minmax(0, 1fr); }

/* Sean's reaction row is a much longer strip than the other two, so the 400px
   cap squeezed it unreadably. Doubled class for the same reason --bare needs
   one: .fs-shot--slack .fs-shot__img would otherwise outrank a single class. */
.fs-shot__img.fs-shot__img--wide { max-width: min(600px, 100%); }

.fs-guarantee-icon { display: block; width: 56px; height: 56px; color: var(--iwai-navy-900); margin: 0 auto var(--space-4); }
.fs-guarantee-icon svg { width: 100%; height: 100%; }@media (max-width: 820px) {


}
@media (max-width: 620px) {


}


/* The pricing heading's mark takes the divider icons' blue rather than the
   guarantee block's navy — scoped to #pricing so the guarantee icon, which uses
   the same class, keeps its own color. */
#pricing .fs-guarantee-icon { color: var(--iwai-blue); }

/* Doubled class for the same reason the other size caps need one: rules like
   .fs-shot--wide .fs-shot__img are two selectors and would outrank a single. */
.fs-shot__img.fs-shot__img--600 { max-width: min(600px, 100%); }

/* A headline quote whose lines are separate thoughts rather than one wrapped
   sentence. Dave Waring's had <p> tags nested inside the <h2> — invalid, and it
   rendered a stray empty paragraph — so the breaks are block spans instead,
   spaced like paragraphs. A plain <br> inside one still means a line break. */
.fs-vidtest__para { display: block; }
.fs-vidtest__para + .fs-vidtest__para { margin-top: 0.55em; }

/* Hero: the pivot line between the two halves of the subheadline. Small and
   quiet so the question beneath it carries the weight, not this. */
.fs-hero__ask {
  max-width: var(--measure-reading);
  margin: var(--space-5) auto var(--space-2);
  font-size: var(--fs-caption);
  font-weight: var(--fw-bold);
  text-transform: uppercase;
  letter-spacing: var(--ls-overline);
  color: var(--iwai-gray-600);
}
/* The question is the actual claim, so it sits a step up from the line above. */
.fs-hero__sub--q { font-size: var(--fs-h3); color: var(--iwai-navy-900); }
/* White card with a blue top edge. Shared by the three audience paths and the
   TL;DR card, so the two stay identical — each caller adds only its own
   alignment and padding. */
.fs-edgecard {
  background: var(--iwai-white);
  border: var(--border-hairline);
  border-top: 3px solid var(--iwai-blue);
  border-radius: var(--radius-lg);
  box-shadow: var(--shadow-xs);
  padding: var(--space-5);
}@media (max-width: 760px) {


}


/* A shot that closes a section: its top margin carries the full section gap so
   it sits the same distance from the copy above as from the section below.
   Without this it inherited .fs-shot's space-8 and read 71/44. */
.fs-shot--closing { margin-top: var(--section-gap); }
