/* ============================================================================
   Commission Church Chandler — Canonical components
   The finished website loads this file. The Design Library renders these exact
   classes; nothing in css/library.css may style a .cc- class.
   Mobile-first; desktop refinements at >=900px.
   Derived from accepted Home slice-1 comps. Ids match page-assembly-map.json.
   ============================================================================ */

/* ==========================================================================
   COMPONENT: canvas  (id: canvas)
   The site's shell: a ground, and the sheet of site content centred on it.

     .cc-canvas         the ground. Fills whatever box it is given and paints
                        --cc-canvas-ground.
     .cc-canvas__sheet  the site content. Capped at --cc-canvas-max and
                        centred, so the ground shows beside it above that
                        width and nowhere below it.

   Self-contained and unscoped on purpose. A page puts .cc-canvas on <body> and
   gets the ground for the whole viewport, because a body background propagates
   to the viewport when <html> has none. A review surface puts it around one
   component and gets the same relationship at that size. Nothing here assumes
   it is used once, or that it owns the page.

   FLUID CLIENTS. The cap is a token, not a rule. Set --cc-canvas-max to none
   and the sheet fills its container at every width, the ground never shows,
   and no component, page, or review surface changes. max-width is used rather
   than width: min() precisely so that none stays valid.

   No inline padding. Section bands reach the sheet edge, and padding here
   would strand every edge-to-edge photograph short of it.
   ========================================================================== */
.cc-canvas {
  background: var(--cc-canvas-ground);
}

.cc-canvas__sheet {
  max-width: var(--cc-canvas-max);
  margin-inline: auto;
}

/* ==========================================================================
   COMPONENT: band  (id: band)
   A full-width section stripe. It paints one surface and separates one
   section of a page from the next.

     .cc-band         paints the surface. Never any inline padding.
     .cc-band__inner  optional child. Applies the page inset and the block
                      rhythm. Used only when the content owns neither.

   VERTICAL SPACE COMES FROM THE CHILD, NOT FROM THE BAND. A component placed
   directly in a band brings its own padding-block: feature-split, page-hero,
   and site-footer all declare one. Loose page copy declares none, and that is
   the case __inner exists for. Putting padding-block on .cc-band as well would
   add it a second time on every component band. Verified 2026-08-18 against
   .cc-feature-split, .cc-footer__inner, and .cc-hero__content.

   NO INLINE PADDING ON .cc-band. feature-split's bleed modifiers reach the
   band edge with a negative margin, so padding here would strand every
   edge-to-edge photograph short of the edge.

   NO WIDTH AND NO CENTRING. The band fills the box it is given. On a page that
   box is .cc-canvas__sheet, which is already capped at --cc-canvas-max. A band
   that set its own width would create a second authority for the canvas edge.

   CLIENT-NEUTRAL BY DESIGN. The object enumerates no colour. It reads two
   custom properties and nothing else:

     --cc-band-surface   any background value: a colour, a gradient, layers,
                         an image. `background` is the shorthand precisely so
                         a band is not limited to one flat colour.
     --cc-band-fg        the foreground colour that surface implies. It
                         inherits, so a child needs no on-dark variant of its
                         own; .cc-section-title below is the worked example.

   The modifiers under the rule below are THIS CLIENT'S preset list. They are
   not part of the object. Another client replaces the list, adds to it, or
   sets the two properties on one band for a one-off. Nothing above this
   sentence changes, and no page or component has to be refactored.
   ========================================================================== */
.cc-band {
  background: var(--cc-band-surface, transparent);
  color: var(--cc-band-fg, inherit);
}

.cc-band__inner {
  padding-inline: var(--cc-page-inset);
  padding-block: var(--cc-space-7);
}

/* Commission Church surface presets - THE BAND LADDER. Client-local; see the
   note above. The names match the surface token each one selects, which is
   also how page-assembly-map.json names a placement's surface.

   THIS LIST IS CLOSED AT SEVEN, and a section background may be none other.
   The three lights rise in lightness. The three warms rise in CHROMA - 2.5,
   4.2, 5.9 - and that ramp, not contrast, is what separates the page. A page
   names a preset from this list; a page never names a value, and this file
   never holds one. COL-01, founder-approved 2026-08-19; see
   080-design-library/col-01-plan.md. */
.cc-band--white   { --cc-band-surface: var(--cc-white); }
.cc-band--light-1 { --cc-band-surface: var(--cc-band-light-1); }
.cc-band--light-2 { --cc-band-surface: var(--cc-band-light-2); }
.cc-band--light-3 { --cc-band-surface: var(--cc-band-light-3); }
.cc-band--warm-1  { --cc-band-surface: var(--cc-band-warm-1); }
.cc-band--warm-2  { --cc-band-surface: var(--cc-band-warm-2); }
.cc-band--warm-3  { --cc-band-surface: var(--cc-band-warm-3); }
.cc-band--ink     {
  --cc-band-surface: var(--cc-ink);
  --cc-band-fg: var(--cc-text-on-dark);
}

@media (min-width: 900px) {
  /* Rises with feature-split's own block padding so a band of loose copy and
     a band holding a component sit on one rhythm. */
  .cc-band__inner {
    padding-block: var(--cc-space-8);
  }
}

/* ==========================================================================
   COMPONENT: button  (id: button)
   Variants:  primary | outline-light | outline-ink | outline-warm | warm | soft
   Modifiers: block | fluid (capped full width on mobile; shared desktop minimum)
   Labels render as written at every breakpoint (founder ruling, 2026-08-12).
   ========================================================================== */
.cc-btn {
  --_btn-bg: var(--cc-red);
  --_btn-fg: var(--cc-white);
  --_btn-border: transparent;
  display: inline-flex;
  align-items: center;
  justify-content: center;
  gap: var(--cc-space-3);
  /* Height is the component's, not its contents'. Vertical padding is zero so
     nothing inside can drive the box past the floor: the 24px icon and the
     30px badge icon both clear it, and every variant lands at exactly 56px.
     The former 0.9rem padding let each of those push through, giving one
     component three heights — 52px text, 57px icon, 63px badge. A label that
     wraps still grows the button, so nothing can clip. 56px is a full 8px
     step, well clear of the 44px minimum touch target. Founder direction
     2026-08-14: 48px read too tight. */
  padding: 0 var(--cc-space-5);
  min-height: 56px;
  font-family: var(--cc-font-body);
  font-size: var(--cc-fs-body);
  font-weight: var(--cc-weight-semibold);
  line-height: 1;
  text-decoration: none;
  color: var(--_btn-fg);
  background: var(--_btn-bg);
  border: 2px solid var(--_btn-border);
  border-radius: var(--cc-radius-md);
  cursor: pointer;
  transition: background var(--cc-transition), color var(--cc-transition),
    border-color var(--cc-transition), transform var(--cc-transition);
}

/* Optional mobile outline weight; desktop retains the shared 2px border.
   Founder-approved 1.5px stroke, independent of colour and width variants. */
@media (width < 900px) {
  .cc-btn--outline-mobile-thin {
    border-width: 1.5px;
  }
}

.cc-btn__icon {
  width: var(--cc-icon-btn);
  height: var(--cc-icon-btn);
  flex: none;
}
/* The wrapper above sets the slot; this sets the glyph inside it. BOTH are
   required. .cc-icon carries its own default size, so a wrapper alone leaves
   the glyph at that default and it overflows the slot. The badge variant has
   always had its own version of this rule further down; the plain variant did
   not, which went unnoticed only because the wrapper and the glyph happened to
   read the same token until the two were separated on 2026-08-18. */
.cc-btn__icon .cc-icon {
  width: var(--cc-icon-btn);
  height: var(--cc-icon-btn);
}
/* Get Directions uses the map pin, including existing navigation-class placements. */
.cc-btn__icon > .cc-icon--navigation {
  --cc-icon-url: url(../assets/icons/pin.svg);
}
/* Existing Watch Online placements use the same canonical YouTube asset. */
.cc-btn__icon > .cc-icon--watch {
  --cc-icon-url: url(../assets/icons/youtube.svg);
}
.cc-btn__icon:has(> .cc-icon--youtube, > .cc-icon--watch) {
  --cc-icon-btn: calc(18px * 1.15 * 0.9);
}
.cc-btn__icon:has(> .cc-icon--compass) {
  /* Founder-directed optical increase for the About button. */
  --cc-icon-btn: calc(18px * 1.1);
}
.cc-btn__icon:has(> .cc-icon--group, > .cc-icon--giving-heart, > .cc-icon--envelope) {
  /* Optical increase to balance these lighter marks with other button icons. */
  --cc-icon-btn: calc(18px * 1.15);
}
.cc-btn__icon:has(> .cc-icon--pin, > .cc-icon--navigation) {
  /* Founder-directed 10% increase for Get Directions, including legacy markup. */
  --cc-icon-btn: calc(18px * 1.1);
}
.cc-btn__label {
  display: inline-block;
}
/* __logo: a provider's full logomark in place of icon and label. The mark is
   the button's words, so the span carries role="img" and aria-label and the
   link takes its name from it. Painted with currentColor like an icon; on
   primary it paints white and the red shows through the cut-out play
   triangle and letter counters. 22px tall, set by eye between the icon-sm
   and icon-md steps: at 24px the mark outweighed the icon-and-label buttons
   beside it (founder direction 2026-09-29). An even height keeps the width
   whole (99px) against the 90 x 20 viewBox. The button keeps its 56px
   floor. HOME-07, founder direction 2026-09-29. */
.cc-btn__logo {
  display: block;
  height: 22px;
  flex: none;
  background-color: currentColor;
  -webkit-mask: var(--_btn-logo-url) center / contain no-repeat;
  mask: var(--_btn-logo-url) center / contain no-repeat;
}
.cc-btn__logo--youtube {
  --_btn-logo-url: url(../assets/images/youtube-logo.svg);
  aspect-ratio: 90 / 20;
}

/* Variant: primary (solid red) */
.cc-btn--primary {
  --_btn-bg: var(--cc-red);
  --_btn-fg: var(--cc-white);
  --_btn-border: var(--cc-red);
}
.cc-btn--primary:hover {
  --_btn-bg: var(--cc-red-strong);
  --_btn-border: var(--cc-red-strong);
}

/* Warm filled button: employee-selected normal and hover colours. */
.cc-btn--warm {
  --_btn-bg: var(--cc-button-warm);
  --_btn-border: var(--cc-button-warm);
  --_btn-fg: var(--cc-white);
}
.cc-btn--warm:hover {
  --_btn-bg: var(--cc-button-warm-hover);
  --_btn-border: var(--cc-button-warm-hover);
}

/* Variant: outline-light (transparent, light border — used on dark hero) */
.cc-btn--outline-light {
  --_btn-bg: transparent;
  --_btn-fg: var(--cc-white);
  --_btn-border: var(--cc-border-on-dark);
}
.cc-btn--outline-light:hover {
  --_btn-bg: rgba(255, 255, 255, 0.12);
  --_btn-border: var(--cc-white);
}

/* Variant: outline-ink (white fill, near-black border + label — Watch Online) */
.cc-btn--outline-ink {
  --_btn-bg: var(--cc-white);
  --_btn-fg: var(--cc-ink);
  --_btn-border: var(--cc-ink);
}
.cc-btn--outline-ink:hover {
  --_btn-bg: var(--cc-ink);
  --_btn-fg: var(--cc-white);
}

/* Shared tertiary action; disclosure triggers hold the hover look while open. */
.cc-btn--outline-warm {
  --_btn-bg: transparent;
  --_btn-border: var(--cc-button-warm-hover);
  --_btn-fg: var(--cc-button-warm-hover);
}
.cc-btn--outline-warm:hover,
.cc-btn--outline-warm[aria-expanded="true"] {
  --_btn-bg: var(--cc-button-warm);
  --_btn-fg: var(--cc-white);
}

/* Variant: soft (warm neutral fill, dark label — used on warm-gray sections) */
.cc-btn--soft {
  --_btn-bg: var(--cc-surface-warm-strong);
  --_btn-fg: var(--cc-text);
  --_btn-border: var(--cc-surface-warm-strong);
}
.cc-btn--soft:hover {
  --_btn-bg: var(--cc-surface-warm-strong-hover);
  --_btn-border: var(--cc-surface-warm-strong-hover);
}
/* Hold the hover look while a disclosure is open. */
.cc-btn--soft[aria-expanded="true"] {
  --_btn-bg: var(--cc-surface-warm-strong-hover);
  --_btn-border: var(--cc-surface-warm-strong-hover);
}

/* BOTH FULL-WIDTH MODIFIERS STOP AT --cc-btn-max-mobile AND CENTRE THERE.
   Founder ruling 2026-08-22. The cap is four reference columns, 416px, and
   tokens.css owns the derivation.

   A control that fills its column is right on a phone and wrong on a narrow
   tablet. The column is 788px at an 820px layout width and the button reads
   as a banner. The cap engages once the column passes 416px, which is a
   448px layout width, so every phone below that is untouched and still runs
   edge to edge.

   margin-inline: auto IS THE CENTRING, NOT SPACING. It divides the leftover
   width and resolves to zero whenever the cap is not engaged, so it adds no
   gap and touches no page inset. The inset belongs to the container; a
   max-width can only make this narrower and can never push outward.

   Undone inside the 900px block below, where the three-column floor governs
   and the button returns to fit-content. */

/* Modifiers: block and fluid — ONE RULE, TWO NAMES, DELIBERATELY.

   They were genuinely different until FIX-07 on 2026-08-17 gave both the same
   desktop treatment. That left their mobile declarations identical too, and
   the two copies sat here as separate blocks until 2026-08-22. Two identical
   blocks with nothing holding them together is a divergence waiting to happen:
   an edit lands on one, misses the other, and the two names quietly mean
   different things again — which is the state FIX-07 existed to fix. Merged so
   that cannot occur.

   THE SECOND NAME IS NOT DELETED, AND MERGING IS NOT A STEP TOWARD DELETING IT.
   cc-btn--block is live on six buttons across the three built pages. Removing
   it would break them SILENTLY: nothing checks that a class a page names still
   exists in the library, so the failure has no console error and no failed
   check — just a phone button that stops being full width. Retiring the name is
   a Website Build task, not a library one. See the pre-flight rule in
   project/skill-rules.md before deleting or renaming any cc- name.

   The 900px block below already declares them as one selector list. */
.cc-btn--block,
.cc-btn--fluid {
  display: flex;
  width: 100%;
  max-width: var(--cc-btn-max-mobile);
  margin-inline: auto;
}

.cc-btn:active {
  transform: translateY(1px);
}
.cc-btn[aria-disabled="true"],
.cc-btn:disabled {
  opacity: 0.5;
  pointer-events: none;
}

/* pin.svg has 5 empty viewBox units on each horizontal side (24 total).
   Remove that empty space from button layout while preserving the glyph size,
   so its visible edge uses the same label gap as the edge-to-edge YouTube mark. */
.cc-btn__icon:has(> .cc-icon--pin, > .cc-icon--navigation) {
  margin-inline: calc(var(--cc-icon-btn) * -5 / 24);
}

/* Plan Your Visit uses the church mark. The href selector supports existing
   assembled buttons until their markup adopts cc-icon--church. */
.cc-btn[href$="plan-your-visit.html"] .cc-btn__icon > .cc-icon {
  --cc-icon-url: url(../assets/icons/church.svg);
  width: var(--cc-icon-btn);
  height: var(--cc-icon-btn);
}
.cc-btn .cc-btn__icon:has(> .cc-icon--church),
.cc-btn[href$="plan-your-visit.html"] .cc-btn__icon {
  /* Optical sizing: the peaked roof and cross carry less mass than YouTube. */
  --cc-icon-btn: 24px;
  width: var(--cc-icon-btn);
  height: var(--cc-icon-btn);
  background: transparent;
  color: inherit;
  border-radius: 0;
  /* church.svg has 2 empty horizontal units per side in its 24-unit viewBox. */
  margin-inline: calc(var(--cc-icon-btn) * -2 / 24);
}

@media (min-width: 900px) {
  /* One desktop width for every button.

     These two modifiers used to disagree above the breakpoint. --block
     collapsed to `width: auto`, so it sized itself from whatever its label
     happened to say, while --fluid filled its whole column. Two buttons in
     equivalent positions therefore came out different widths, which is the
     mismatch between Get Directions and Plan Your Visit.

     The floor is three grid columns, computed rather than chosen. Short
     labels pad out to it so buttons look deliberate down the page, a longer
     label grows past it rather than wrapping. Left aligned in its cell, which
     is what the accepted comps show. It supersedes the provisional 320px in
     library-fix-list.md.

     FOUNDER RULING 2026-08-18: THIS IS A SPAN, NEVER A PIXEL VALUE. It was
     briefly pinned at 318px — the figure the old 24px-gutter grid produced —
     and that is precisely the drift the rule exists to stop. On the current
     grid it resolves to 300px, and it will move on its own if the grid moves.

     min() rather than a bare calc, because CSS resolves min-width after
     max-width and a min-width always wins. A fixed floor wider than a fluid
     column spills out of it and `max-width: 100%` cannot pull it back. The
     spill was measured at 11px at a 901px layout width while the floor was
     briefly pinned; on the 24px-gutter grid before it the same arithmetic
     gives about 66px, which was never observed and is quoted as arithmetic
     only. Mobile is unchanged and stays full width. */
  .cc-btn--block,
  .cc-btn--fluid {
    display: inline-flex;
    width: fit-content;
    min-width: min(var(--cc-btn-w-desktop), 100%);
    /* Releases --cc-btn-max-mobile. The floor above governs from here. */
    max-width: 100%;
    /* Releases the mobile centring. Without this a fit-content button would
       stay centred in its cell, and the comps align it left. */
    margin-inline: 0;
  }
}

/* ==========================================================================
   COMPONENT: section-title  (id: section-title)
   The heading for a page section. Standalone: it belongs to the section, not
   to any one component, so a band of loose copy can carry a heading without
   borrowing feature-split's.

   Colour is `inherit`, not a named value. On a light band it inherits the body
   colour; inside .cc-band--ink it inherits that band's --cc-band-fg. That is
   why this object needs no on-dark variant, and why a new client adding a dark
   surface preset gets a correct heading without touching this rule.

   Every other value is a token, so the client owns them in css/tokens.css.
   --cc-fs-h2 is the existing "section headings" step; it is deliberately not a
   new size, because SYS-02 restandardises the type scale next and a fresh
   value here would have to be redone.
   ========================================================================== */
.cc-section-title {
  margin: 0;
  font-family: var(--cc-font-display);
  font-size: var(--cc-fs-h2);
  font-weight: var(--cc-weight-semibold);
  line-height: var(--cc-lh-snug);
  color: inherit;
}

/* ==========================================================================
   COMPONENT: sub-heading  (id: sub-heading)
   A spaced-capitals heading INSIDE a section: it opens a run of copy under a
   section-title without competing with it. ABOUT-03's "Their Story" and
   "Mission & Multiplication" are the first placements; the accepted comp
   draws both as small tracked capitals over the body copy.

   An h3 by element, so the outline under the section's h2 is right, and the
   eyebrow step by size. NOT A NEW SIZE. The comp's capitals read between the
   body step and the eyebrow step, and the eyebrow step is the nearest rung on
   the six-step ladder, SYS-02 rule. The tracking does the rest: 0.18em is in
   the conventional range for a tracked-capitals label, 0.1 to 0.2em, and is a
   type value, not a grid one. Weight is the site heading weight, founder
   ruling 2026-08-18.

   Colour is inherit, like section-title, for the same reason: on a dark band
   it takes that band's foreground without an on-dark variant.
   ========================================================================== */
.cc-sub-heading {
  margin: 0;
  font-family: var(--cc-font-display);
  font-size: var(--cc-fs-lead);
  font-weight: var(--cc-weight-semibold);
  line-height: var(--cc-lh-snug);
  letter-spacing: 0.18em;
  text-transform: uppercase;
  color: inherit;
}

/* ==========================================================================
   COMPONENT: section-eyebrow  (id: section-eyebrow)
   Short red accent rule above an optional kicker line.
   Variants: rule-only (rule with no text) | on-dark (light kicker text)
   ========================================================================== */
.cc-eyebrow {
  display: flex;
  flex-direction: column;
  gap: var(--cc-space-3);
  margin: 0 0 var(--cc-space-4);
  color: var(--cc-text);
}
.cc-eyebrow__rule {
  display: block;
  width: 46px;
  height: 4px;
  background: var(--cc-red);
  border-radius: var(--cc-radius-pill);
}
.cc-eyebrow__text {
  font-family: var(--cc-font-body);
  font-size: var(--cc-fs-lead);
  font-weight: var(--cc-weight-medium);
  color: inherit;
}
.cc-eyebrow--on-dark {
  color: var(--cc-text-on-dark);
}
.cc-eyebrow--rule-only .cc-eyebrow__text {
  display: none;
}

/* ==========================================================================
   COMPONENT: section-copy  (id: section-copy)
   A band of loose page copy: one section heading and the paragraphs under it.

   base.css resets every margin to zero, so a heading and a run of paragraphs
   dropped straight into .cc-band__inner collapse into one block. This object
   is the stack that gives them their rhythm, and it is nothing else.

   IT IS NOT feature-split WITHOUT A PHOTOGRAPH. feature-split divides the band
   into 5 columns against 7 and pins its copy to the narrow side. This one
   fills whatever box it is given at every width and carries no breakpoint,
   which is what GROUPS-03 draws at both breakpoints.

   NO MEASURE CAP, AND THAT IS AN OPEN QUESTION, NOT A DECISION. The paragraph
   takes the full width of the band exactly as the accepted desktop comp draws
   it, which at --cc-canvas-max is a long line. feature-split carries a note
   saying a cap has to be re-derived against the column it will actually meet;
   the same applies here. Raised for founder direction 2026-08-22.

   The paragraph treatment is deliberately identical to
   .cc-feature-split__text, so copy reads the same whether it sits in a split
   or in a band of its own.
   ========================================================================== */
.cc-section-copy {
  display: flex;
  flex-direction: column;
  gap: var(--cc-space-4);
}
.cc-section-copy p {
  margin: 0;
  font-size: var(--cc-fs-body);
  line-height: var(--cc-lh-body);
  color: var(--cc-text-muted);
}

/* COMPONENT: statement (id: statement)
   Label and emphasized text. */
.cc-statement {
  display: flex;
  flex-direction: column;
  gap: var(--cc-space-2);
}
.cc-statement__label {
  margin: 0;
  font-family: var(--cc-font-body);
  font-size: var(--cc-fs-small);
  line-height: var(--cc-lh-body);
  color: var(--cc-text-muted);
}
.cc-statement__line {
  margin: 0;
  font-family: var(--cc-font-body);
  font-size: var(--cc-fs-lead);
  font-weight: var(--cc-weight-bold);
  line-height: var(--cc-lh-snug);
  color: var(--cc-text);
}

/* ==========================================================================
   COMPONENT: pull-quote  (id: pull-quote)
   A passage of the page's own copy set large inside a bordered box with a
   red rule down its start edge, so it reads as the section's thesis.
   ABOUT-03 carries two; the second also carries the pathway row.

   IT IS NOT A QUOTATION, SO IT IS NOT A blockquote. The passage is the copy
   itself, in its place in the reading order, not a citation of someone else,
   and a blockquote would announce a quotation to a screen reader. A div
   holding paragraphs is the honest element. An aside was rejected for the
   opposite reason: the passage is part of the flow, not beside it.

   Optional part: __pathway, the four pathway words under a hairline. They are
   a list because they are one. A middle-dot separator is TYPED between each
   word as its own <li class="cc-pull-quote__sep">, so the markup holds seven
   items: four words and three dots. The accepted comp draws a middle dot
   between them; Page Content ends each word with a full stop, which the markup
   drops. The dots are not drawn in CSS - the 2026-09-04 one-line rework removed
   the drawn separator; the rule below only spreads the row.

   Composes: nothing. Width comes from the parent. A composing component
   insets it from the grid when the comp asks for that, as leader-profile
   does; this object never insets itself.

   Type is the footer-name step, 24px. NOT A NEW SIZE. The comp sets the
   passage at about two thirds of the section heading, and 24 against the
   heading's 40 is the nearest rung, SYS-02 rule. The pathway row shares
   sub-heading's tracked-capitals treatment so the two motifs read as one.
   ========================================================================== */
.cc-pull-quote {
  /* --- Rule (adjustable) --------------------------------------------------
     5px, founder direction 2026-09-03. One heavier than the 4px eyebrow rule,
     so the two red marks on a page are no longer the same stroke. A design
     value, not a grid value. */
  --cc-pull-quote-rule: 5px;
  /* --- Fill (adjustable) --------------------------------------------------
     warm-3, founder direction 2026-09-04, to lift the callout off the band and
     break the page up a little more. A design value; retune the token here. */
  --cc-pull-quote-bg: var(--cc-band-warm-3);
  /* --- Divider (adjustable) ----------------------------------------------
     border-strong, founder direction 2026-09-04. The pathway hairline needs a
     darker neutral to stay visible on the warm-3 fill; --cc-border washed out
     once the fill moved off light-2. A design value; retune the token here. */
  --cc-pull-quote-line: var(--cc-border-strong);

  margin: 0;
  padding: var(--cc-space-5);
  background: var(--cc-pull-quote-bg);
  border: 1px solid var(--cc-border);
  border-inline-start: var(--cc-pull-quote-rule) solid var(--cc-red);
  color: var(--cc-text);
  /* Size container so the pathway type can shrink to the box width. */
  container-type: inline-size;
}
.cc-pull-quote--light-2 {
  --cc-pull-quote-bg: var(--cc-band-light-2);
}
.cc-pull-quote--light-1 {
  --cc-pull-quote-bg: var(--cc-band-light-1);
}
.cc-pull-quote--warm-2 {
  --cc-pull-quote-bg: var(--cc-band-warm-2);
}
.cc-pull-quote > p {
  margin: 0;
  font-family: var(--cc-font-display);
  font-size: var(--cc-fs-name);
  font-weight: var(--cc-weight-medium);
  line-height: var(--cc-lh-snug);
  color: inherit;
}
.cc-pull-quote > p + p {
  margin-block-start: var(--cc-space-4);
}

/* ONE LINE AT EVERY WIDTH. No wrap, no grid fallback: the row never breaks,
   the type gives way instead. The words spread edge to edge with the separators
   as their own items, each dot centred in its gap. The whole line is
   proportional to its own type - the letters, the 0.18em tracking, and the
   em-based dot gaps all scale together - so as the box narrows the type tracks
   the box width in cqi units and the line still holds on one row. The
   coefficient (3.9cqi) sits just under the width where the line would touch the
   box, leaving a few per cent of slack that space-between reopens between the
   dots. Ceiling is the lead size. The floor is a small readability floor, not
   the body size: holding one line below about a 530px screen means the type
   must drop under the body size. Founder direction 2026-09-04, replacing the
   2026-09-03 two-by-two grid - one line always, the size reduces, not the row.
   cc-pull-quote is the size container. */
.cc-pull-quote__pathway {
  display: flex;
  flex-wrap: nowrap;
  justify-content: space-between;
  column-gap: 0.8em;
  margin: var(--cc-space-5) 0 0;
  padding: var(--cc-space-5) 0 0;
  border-block-start: 1px solid var(--cc-pull-quote-line);
  list-style: none;
  font-family: var(--cc-font-display);
  font-size: clamp(0.625rem, 3.9cqi, var(--cc-fs-lead));
  font-weight: var(--cc-weight-semibold);
  line-height: var(--cc-lh-snug);
  letter-spacing: 0.18em;
  text-transform: uppercase;
}

@media (min-width: 900px) {
  /* More air inside the box on desktop, where the passage is wider than it
     is tall: the section step on the inline sides, a step less on the block
     sides. The rule and border do not step. */
  .cc-pull-quote {
    padding: var(--cc-space-6) var(--cc-space-7);
  }
}

/* ==========================================================================
   COMPONENT: info-list  (id: info-list) + item (id: info-list-item)
   Icon + title + detail rows with hairline dividers.
   The item's media slot takes a .cc-icon.
   Variants: default | on-dark (footer colours) | links (each row is one
             anchor with no detail line) | bare (no icons, no hairlines)
   ========================================================================== */
.cc-info-list {
  list-style: none;
  margin: 0;
  padding: 0;
}
.cc-info-list__item {
  display: flex;
  align-items: flex-start;
  gap: var(--cc-space-4);
  padding: var(--cc-space-4) 0;
  border-top: 1px solid var(--cc-border);
}
.cc-info-list__item:first-child {
  border-top: 0;
  padding-top: 0;
}
/* The mirror of :first-child: the last row keeps its divider above and gives
   up the padding below. A list's box begins at its first row's text and ends
   at its last row's; the row rhythm lives between rows, not outside them.
   Before this every band or stack that ended in a list carried a 16px tail
   the layout could not see: EVENTS-04's last row sat 80px above its band foot
   against the 64px the split sets. Founder direction 2026-09-11. links, bare
   and compact already zero the row padding and are not moved by this. */
.cc-info-list__item:last-child {
  padding-bottom: 0;
}

/* Icon size here is a designer decision held static, not a derived value.
   The default rows carry two lines of text and the icon is meant as a design
   statement, so it takes the large --cc-icon-page. The --links variant lower
   down carries one line and keeps the small size. Founder ruling 2026-08-18,
   FIX-03. */
.cc-info-list__icon {
  flex: none;
  width: var(--cc-icon-page);
  height: var(--cc-icon-page);
  display: inline-flex;
  align-items: center;
  justify-content: center;
  color: var(--cc-red);
}
.cc-info-list__icon .cc-icon {
  width: var(--cc-icon-page);
  height: var(--cc-icon-page);
}

.cc-info-list__body {
  display: flex;
  flex-direction: column;
  gap: 2px;
}
.cc-info-list__title {
  font-family: var(--cc-font-body);
  font-size: var(--cc-fs-body);
  font-weight: var(--cc-weight-bold);
  color: var(--cc-text);
  line-height: 1.3;
}
.cc-info-list__detail {
  font-size: var(--cc-fs-small);
  color: var(--cc-text-muted);
  line-height: 1.4;
}

/* Variant: on-dark — the footer runs this list on the ink surface. */
.cc-info-list--on-dark .cc-info-list__item {
  border-top-color: var(--cc-border-on-dark-soft);
}
.cc-info-list--on-dark .cc-info-list__title {
  color: var(--cc-text-on-dark);
}
.cc-info-list--on-dark .cc-info-list__detail {
  color: var(--cc-text-on-dark-muted);
}

/* Variant: links — the whole row is one anchor and carries no detail line. */
.cc-info-list--links .cc-info-list__item {
  padding: 0;
}

/* One line of text per row here, not two, so these keep the small icon.
   Founder 2026-08-18: the footer link icons are perfect as they are.
   Deliberately delinked from the default list above, which is much larger. */
.cc-info-list--links .cc-info-list__icon,
.cc-info-list--links .cc-info-list__icon .cc-icon {
  width: var(--cc-icon-lg);
  height: var(--cc-icon-lg);
}
.cc-info-list__link {
  position: relative; /* anchors the current-page bar */
  display: flex;
  align-items: center;
  gap: var(--cc-space-4);
  padding: var(--cc-space-4) 0;
  color: inherit;
  text-decoration: none;
  transition: color var(--cc-transition);
}
.cc-info-list--links .cc-info-list__title {
  font-weight: var(--cc-weight-medium);
}
.cc-info-list__link:hover .cc-info-list__title {
  color: var(--cc-red);
}

/* State: current page. The same leading bar the mobile menu uses, so the two
   vertical link lists carry one mark rather than two.

   The row's icon is ALREADY red - .cc-info-list__icon sets it and --on-dark
   does not override it - so reddening the icon marks nothing. The bar is the
   signal. The title stays --cc-text-on-dark against --cc-ink, 19.2:1. Red text
   here would be 3.17:1 against a 4.5 minimum, which is why the title is left
   alone.

   The offset is --cc-space-4 rather than --cc-page-inset because this list is
   not always at the page edge: on mobile the footer inset is 16px and the bar
   sits flush against it, and above the breakpoint the list is the second grid
   column, where the same 16px falls inside the --cc-space-8 column gap. Using
   the inset token would push the bar 48px out into the brand column there. */
.cc-info-list__link[aria-current="page"]::before {
  content: "";
  position: absolute;
  top: 50%;
  transform: translateY(-50%);
  left: calc(var(--cc-space-4) * -1);
  width: 4px;
  height: var(--cc-space-5);
  border-radius: var(--cc-radius-pill);
  background: var(--cc-red);
}

/* Variant: bare — no media slot and no hairlines; used for the footer's
   service blocks, which are title/detail pairs only. */
.cc-info-list--bare {
  display: flex;
  flex-direction: column;
  gap: var(--cc-space-5);
}
.cc-info-list--bare .cc-info-list__item {
  border-top: 0;
  padding: 0;
}

/* Variant: compact — icons kept, hairlines dropped, one line of text per row.

   Built for event-card, where three facts (date, location, registration) sit
   inside a card that is already bounded by its own edge. Hairlines there would
   draw a second set of divisions inside a division.

   NOT a fourth way to write the default list. The default carries two lines
   per row and makes its icon a design statement at --cc-icon-page; these rows
   carry one line, so they take --cc-icon-lg for exactly the reason --links
   does. Founder ruling 2026-08-18, FIX-03, governs both.

   The title drops to regular weight. The accepted Events comps set these rows
   at body weight, and there is no detail line under them for a bold title to
   distinguish itself from. */
.cc-info-list--compact {
  display: flex;
  flex-direction: column;
  gap: var(--cc-space-3);
}
.cc-info-list--compact .cc-info-list__item {
  border-top: 0;
  padding: 0;
  align-items: center;
  gap: var(--cc-space-3);
}
.cc-info-list--compact .cc-info-list__icon,
.cc-info-list--compact .cc-info-list__icon .cc-icon {
  width: var(--cc-icon-lg);
  height: var(--cc-icon-lg);
}
.cc-info-list--compact .cc-info-list__title {
  font-weight: var(--cc-weight-regular);
}

/* Variant: checks — one line of text per row, hairlines KEPT, a check mark per
   row. Built for GIVE-02's "You can" list.

   It is compact with the divider put back. compact drops the hairline because
   its rows sit inside an event-card that is already bounded by its own edge;
   these rows sit in open copy and the accepted comps draw a rule between them,
   so the default's border-top is left in place and only the icon size, the row
   alignment, and the title weight change. The icon stays --cc-red from the base
   slot, which is what paints the masked check. */
.cc-info-list--checks .cc-info-list__item {
  align-items: center;
}
.cc-info-list--checks .cc-info-list__icon,
.cc-info-list--checks .cc-info-list__icon .cc-icon {
  width: var(--cc-icon-lg);
  height: var(--cc-icon-lg);
}
.cc-info-list--checks .cc-info-list__title {
  /* Standard body weight. Founder ruling 2026-08-30: these rows read as body
     copy, matching GIVE-02's lead and the Questions paragraph, so the base
     __title bold is dropped to regular rather than the medium it first took. */
  font-weight: var(--cc-weight-regular);
}

/* ==========================================================================
   COMPONENT: bullet-list  (id: bullet-list) + item (id: bullet-list-item)
   A dot marker and a run of text. Nothing else.

   NOT info-list. That object is icon plus title plus detail in a bordered row
   and it does not fit this content. This one is the plain statement list the
   About comp shows beside What We Believe.

   BUILT FOR UNBOUNDED LENGTH. Founder direction 2026-08-20. The comps show
   five items because they predate the content update; canonical Page Content
   carries twenty for ABOUT-05, and it can carry more later. So:
     - no item cap, no fixed height, and NO INNER SCROLL BOX;
     - no column count and no balancing, which would reorder a numbered
       sequence into something a reader cannot follow;
     - the list is exactly as tall as its content and the page absorbs it.
   Verified at 5 and at 20 items before first review.

   WIDTH COMES FROM THE PARENT. The list fills whatever box it is given, so it
   is correct in a grid cell, in a band inner, or full width, and it needs no
   breakpoint of its own. The divided split that places it beside the copy on
   About is a separate object and is not built here.

   HANGING INDENT. Text wraps back to the text, never under the dot, so a long
   item still reads as one block. That is what the padding plus absolute
   marker does; it is not achievable with list-style alone.
   ========================================================================== */
.cc-bullet-list {
  /* --- Marker (adjustable) ----------------------------------------------
     An intrinsic dimension, not a grid-derived one: a marker is sized to read
     against the type beside it. 6px is the smallest dot that still reads as
     deliberate at --cc-fs-body and does not compete with the eyebrow rule,
     which is 4px and is a different signal. */
  --cc-bullet-list-marker-size: 6px;
  --cc-bullet-list-marker-color: currentColor;
  /* Space from the dot to the text, and from one item to the next. Both from
     the approved spacing scale. */
  --cc-bullet-list-marker-gap: var(--cc-space-4);
  --cc-bullet-list-item-gap: var(--cc-space-5);

  list-style: none;
  margin: 0;
  padding: 0;
  display: flex;
  flex-direction: column;
  gap: var(--cc-bullet-list-item-gap);
  font-size: var(--cc-fs-body);
  line-height: var(--cc-lh-body);
  /* inherit, not a value: the band decides the text colour, so the same list
     is correct on a light band and on ink. */
  color: inherit;
}
.cc-bullet-list__item {
  position: relative;
  padding-inline-start: calc(
    var(--cc-bullet-list-marker-size) + var(--cc-bullet-list-marker-gap)
  );
}
/* The dot. Centred on the FIRST LINE of the item, computed from the line box
   rather than nudged by eye: half the leftover after the dot is taken out of
   one line. It therefore stays centred if the type scale or the line height
   changes, and it does not drift when an item wraps to two lines. */
.cc-bullet-list__item::before {
  content: "";
  position: absolute;
  inset-inline-start: 0;
  top: calc(
    (1em * var(--cc-lh-body) - var(--cc-bullet-list-marker-size)) / 2
  );
  width: var(--cc-bullet-list-marker-size);
  height: var(--cc-bullet-list-marker-size);
  border-radius: 50%;
  background: var(--cc-bullet-list-marker-color);
}
/* Optional lead-in inside an item. Canonical ABOUT-05 copy names each belief
   before describing it. This is inline emphasis on the item's own text, not a
   second part of the object — the item is still one run of text. */
.cc-bullet-list__lead {
  font-weight: var(--cc-weight-bold);
}

/* ==========================================================================
   group-card-list / group-card. Accepted Groups redesign, 2026-10-08.
   Framed Church Center graphics are the square-corner exception documented
   at index.html#photos-cards-image-bleeds. Preserve their complete native ratio.
   The list owns its responsive context, including inset desktop placements.
   ========================================================================== */
.cc-group-card-list {
  container: group-cards / inline-size;
  list-style:none; margin:0; padding:0;
  display:flex; flex-direction:column; gap:var(--cc-space-6);
}
.cc-group-card__link {
  display:grid; grid-template-columns:minmax(0,1fr); gap:var(--cc-space-4);
  padding:0; border:1px solid var(--cc-card-border, var(--cc-border));
  border-radius:0; background:var(--cc-card-fill, var(--cc-band-light-1));
  color:inherit; text-decoration:none; overflow:visible; box-shadow:none;
}
.cc-group-card__link:focus-visible { outline:none; box-shadow:var(--cc-focus-ring); }
.cc-group-card__media {
  grid-column:1; grid-row:1; width:100%; aspect-ratio:auto;
  border-radius:0; overflow:visible; box-shadow:none;
}
.cc-group-card__img { display:block; width:100%; height:auto; aspect-ratio:16 / 9; object-fit:contain; border-radius:0; }
.cc-group-card__body {
  grid-column:1; grid-row:2; min-width:0; display:flex; flex-direction:column;
  gap:var(--cc-space-2); padding:0 var(--cc-space-4) var(--cc-space-5);
}
.cc-group-card__name {
  font-family:var(--cc-font-display); font-size:var(--cc-fs-lead);
  font-weight:var(--cc-weight-semibold); line-height:1.3; color:var(--cc-text);
  padding-right:var(--cc-space-5);
}
.cc-group-card__meta { font-size:var(--cc-fs-small); color:var(--cc-text-muted); line-height:1.4; }
.cc-group-card__time { white-space:nowrap; }
.cc-group-card__tags { display:flex; flex-wrap:wrap; gap:var(--cc-space-2); margin-top:var(--cc-space-2); }
.cc-group-card__tag {
  padding:var(--cc-space-1) var(--cc-space-2); background:var(--cc-band-warm-1);
  color:var(--cc-text-muted); font-size:var(--cc-fs-small); line-height:var(--cc-lh-snug);
  border-radius:var(--cc-radius-sm);
}
.cc-group-card__chevron {
  grid-column:1; grid-row:2; justify-self:end; align-self:start;
  display:inline-flex; align-items:center; justify-content:center;
  width:var(--cc-icon-md); height:var(--cc-icon-md); color:var(--cc-text-muted);
  /* Center on the first name line, even when the name wraps. */
  margin-top:calc((var(--cc-fs-lead) * 1.3 - var(--cc-icon-md)) / 2);
  margin-right:var(--cc-space-4);
}
.cc-group-card__chevron .cc-icon { width:100%; height:100%; transform:rotate(-90deg); }
@media (min-width:900px) {
  /* 804 = declared desktop threshold 900 minus two desktop page insets 48.
     Narrower parent slots retain the stacked card, even on a wide viewport. */
  @container group-cards (min-width:804px) {
    .cc-group-card__link {
      /* Employee-directed image proportion, explicitly overriding column spans. */
      grid-template-columns:calc(100% * 512 / 1184) minmax(0,1fr) calc(var(--cc-icon-lg) + var(--cc-space-6));
      gap:0; align-items:center;
    }
    .cc-group-card__body { grid-column:2; grid-row:1; padding:0; margin-left:var(--cc-space-7); margin-right:var(--cc-space-4); }
    .cc-group-card__name { font-size:var(--cc-fs-name); padding-right:0; }
    .cc-group-card__tag { padding:var(--cc-space-2); line-height:1.4; }
    .cc-group-card__chevron { grid-column:3; grid-row:1; justify-self:start; align-self:center; width:var(--cc-icon-lg); height:var(--cc-icon-lg); margin:0; }
    .cc-group-card__link:hover .cc-group-card__name { text-decoration:underline; text-decoration-color:currentColor; }
  }
}

/* ==========================================================================
   COMPONENT: event-card-grid  (id: event-card-grid) + card (id: event-card)
   A photograph, an event name, three facts, and one action. Built for
   EVENTS-02, Coming up soon.

   NOT group-card-list. That object is a one-line linked row with a thumbnail
   rail and a chevron, and the whole row is the link. This one is a stacked
   card with a full-width photograph and its own button, because EVENTS-02
   hands each event off to Church Center through a labelled control rather
   than through the card body.

   White fill with a continuous border and no shadow, per the accepted
   event-card refinement. Card surfaces remain separate from band presets.

   EVENTS-02 uses the existing light-1 band preset, selected by its placement.

   THE GRID FILLS ITS PARENT. It states no width and no column span, so it is
   correct at the page-inset width the map declares for EVENTS-02, whether
   that comes from a band inner or from any parent of the same width class.

   IT IS NOT CONTAINER-RESPONSIVE, AND IT IS NOT MAPPED INTO A NARROW SLOT.
   The two-column rule below is a media query, so it reads the browser width,
   not the box width. In a 400px parent at a desktop viewport the grid still
   draws two columns with a 48px gutter, leaving 176px cards and a clipped
   event name. Measured 2026-08-24. If a later placement needs a narrow slot,
   that rule becomes a container query; do not read this as working today.
   ========================================================================== */
.cc-event-card-grid {
  list-style: none;
  margin: 0;
  padding: 0;
  display: grid;
  grid-template-columns: 1fr;
  gap: var(--cc-space-5);
}

/* EVENTS-02 puts a section-copy above the grid on the same band. base.css
   zeroes every margin and .cc-band__inner supplies the inset but no block
   rhythm, so the lead paragraph and the first card would touch. The space is
   declared here, on the element that follows, so THE PAGE STILL WRITES NO
   CSS. A grid standing alone in a band takes no margin at all. */
.cc-section-copy + .cc-event-card-grid {
  margin-block-start: var(--cc-space-6);
}

.cc-event-card {
  position: relative;
  display: flex;
  flex-direction: column;
  background: var(--cc-white);
  border-radius: var(--cc-radius-md);
  /* The photograph runs edge to edge at the top of the card, so the card
     clips it to its own corners. The frame inside takes --flush and draws no
     radius of its own: two radii on the same corner read as a nick. Same
     reasoning as the square-corner rule on media-frame. */
  overflow: hidden;
}

/* Continuous border includes the image without changing the accepted geometry. */
.cc-event-card::after {
  content: "";
  position: absolute;
  inset: 0;
  border: 1px solid var(--cc-card-border-strong);
  border-radius: inherit;
  pointer-events: none;
}

/* The photograph is a second way to the same place as the Learn More button
   (founder direction 2026-09-17). The feed script wraps the frame in this
   link when the row carries an own-host url and leaves the bare frame when
   it does not, so the frame must read the same inside and outside the link.
   The link is aria-hidden with tabindex -1, the redundant-link pattern: the
   button already names the destination, so the photograph adds a tap target
   for the pointer without a second tab stop or a second announcement of one
   link. display: block so the anchor is exactly the frame's box; an inline
   anchor round a block adds descender space under the photograph. */
.cc-event-card__media {
  display: block;
  color: inherit;
  text-decoration: none;
}

.cc-event-card__body {
  /* flex: 1 1 auto so every card in a grid row is the height of the tallest,
     and the shorter card's own body absorbs the difference. */
  flex: 1 1 auto;
  display: flex;
  flex-direction: column;
  gap: var(--cc-space-4);
  padding: var(--cc-space-5);
  padding-bottom: var(--cc-space-6);
}

.cc-event-card__title {
  margin: 0;
  font-family: var(--cc-font-display);
  font-size: var(--cc-fs-name);
  font-weight: var(--cc-weight-semibold);
  line-height: 1.25;
  color: var(--cc-text);
}

/* THE BUTTON CARRIES NO WIDTH MODIFIER. THE SLOT SIZES IT AT BOTH BREAKPOINTS.

   The slot states a width at both breakpoints and centres itself:
   --cc-btn-max-mobile below 900px, --cc-btn-w-desktop above it. Both are the
   site's existing button widths, so this card introduces no new value.

   It measured 584px on desktop and 804px at an 899px layout width before
   these caps. The founder ruled the card is not an exception to either.

   THE CAP IS ON THE SLOT, NOT ON THE BUTTON, AND NO MODIFIER IS ADDED TO
   PAGE MARKUP. cc-btn--block and cc-btn--fluid would give the same 300px
   here, but reaching for one means editing four cards on events.html and the
   library's own examples, which is Website Assembly work. A cap on the slot
   is a library-only change and it publishes on its own.

   This is the THIRD rule to read --cc-btn-w-desktop, after the button's own
   min-width and hug-split's aside. It names the token whole and does no
   arithmetic on it, so it cannot drift away from the other two.

   margin-top: auto pins the action to the bottom of the card, so the buttons
   in a grid row line up even when one event name wraps to two lines. */
/* Below 900px the slot fills the card interior but stops at
   --cc-btn-max-mobile, the site-wide mobile button cap (founder ruling
   2026-08-22, applied to this card 2026-08-24). Uncapped it reached 804px at
   an 899px layout width, measured, and snapped to 300px one pixel later.

   A STATED WIDTH, NOT A max-width: an auto cross-axis margin cancels a flex
   child's stretch, so max-width plus auto margins collapses the slot to its
   label. min() keeps it inside a card narrower than the cap.

   margin-inline: auto is the centring, not spacing. It resolves to zero on a
   phone, where the card interior is under the cap and the button fills it. */
.cc-event-card__action {
  /* Body gap plus this padding gives a 24px minimum, before auto slack. */
  padding-top: var(--cc-space-2);
  display: grid;
  margin-top: auto;
  width: min(var(--cc-btn-max-mobile), 100%);
  margin-inline: auto;
}

@media (min-width: 900px) {
  .cc-event-card-grid {
    /* Two cards to a row, six grid columns each, separated by one desktop
       gutter. --cc-grid-gutter-desktop is named rather than --cc-space-7
       because that token owns the 48px gutter and a duplicate goes stale
       silently. The accepted desktop comp draws about 36px between the cards;
       the grid-true gutter is taken and the drift accepted. */
    grid-template-columns: repeat(2, 1fr);
    gap: var(--cc-grid-gutter-desktop);
  }
  .cc-section-copy + .cc-event-card-grid {
    margin-block-start: var(--cc-space-7);
  }
  .cc-event-card__body {
    padding: var(--cc-space-6);
  }
  /* The one desktop button width, centred in the card. Founder direction
     2026-08-24. It measured 584px before this - the 6-column card less its
     64px of body padding - against 300px everywhere else on the site.

     STATE A WIDTH, NOT A max-width. The slot is a flex child of the card
     body and it used to reach 584px by stretching. AN AUTO CROSS-AXIS
     MARGIN CANCELS THAT STRETCH: the item falls back to its content size
     and the auto margins absorb the rest. Pairing margin-inline: auto with
     max-width alone therefore gave a 144px button, measured 2026-08-24, not
     a 300px one. A stated width survives the auto margins.

     min(), so the slot can never be wider than the card interior. The
     narrowest desktop card is 314px inside its padding at a 900px layout
     width, so 300px clears it today; the min() is what keeps that true if
     the grid moves. Same guard, and the same reasoning, as the button's own
     min-width above.

     margin-inline: auto IS THE CENTRING, NOT SPACING. It resolves to zero
     when the slot fills its box, so it is inert below 900px, where the
     button still runs the full width of the card. */
  .cc-event-card__action {
    width: min(var(--cc-btn-w-desktop), 100%);
    margin-inline: auto;
  }
}

/* COMPONENT: step-card (id: step-card)
   Image heading, lead text, body copy, and optional quotation. */
/* Step collections use equal gaps; each card's text follows its own heading. */
.cc-event-card-grid--steps {
  gap: var(--cc-space-5);
}
.cc-section-copy + .cc-event-card-grid--steps {
  margin-block-start: var(--cc-space-4);
}
.cc-step-card {
  /* Image height scales the original mark by 1.25 × 1.15. */
  --_step-mark-h: 69px;
  display: flex;
  flex-direction: column;
  gap: var(--cc-space-4);
  padding: var(--cc-space-5);
  background: var(--cc-white);
  border-radius: var(--cc-radius-md);
  box-shadow: var(--cc-shadow-card-soft);
}
.cc-step-card--light-1 {
  background: var(--cc-band-light-1);
}
.cc-step-card__mark {
  margin: 0;
  line-height: 0;
}
.cc-step-card__mark img {
  width: auto;
  height: var(--_step-mark-h);
  max-width: 100%;
  object-fit: contain;
}
.cc-step-card__lead {
  margin: 0;
  font-family: var(--cc-font-body);
  font-size: var(--cc-fs-lead);
  font-weight: var(--cc-weight-bold);
  line-height: var(--cc-lh-snug);
  color: var(--cc-text);
  text-wrap: balance;
}
.cc-step-card__text {
  display: flex;
  flex-direction: column;
  gap: var(--cc-space-4);
}
.cc-step-card__text p {
  margin: 0;
  font-size: var(--cc-fs-body);
  line-height: var(--cc-lh-body);
  color: var(--cc-text-muted);
  /* pretty reduces isolated words on the last line where supported. */
  text-wrap: pretty;
}
.cc-step-card__quote {
  margin: 0;
}

@media (min-width: 900px) {
  .cc-step-card {
    /* Desktop mark: 56px × 1.25 × 1.15, independent of card spacing. */
    --_step-mark-h: 80.5px;

    padding: var(--cc-space-6);
  }
}

/* ==========================================================================
   COMPONENT: give-method-card-list  (id: give-method-card-list)
                + card              (id: give-method-card)
   A scan code, a method name, the account it points at, and one labelled
   action. Built for GIVE-03, Other ways to give.

   IT IS NEITHER OF THE OTHER TWO CARDS. group-card is a one-line linked row
   and the whole row is the link. event-card is a stacked card under a
   full-width photograph. This one carries a SCAN CODE, which is a square the
   reader points a phone at, so the code has to stay large and square at every
   width and the card reflows around it rather than around a landscape frame.

   IT REFLOWS, IT DOES NOT RESTACK. Below 900px the code is a fixed rail on
   the left and the name, account and action read down its right. At 900px the
   card turns vertical and centres, because three cards to a desktop row leave
   each one about four grid columns wide and a side-by-side rail there would
   squeeze the account line to nothing. Same markup, one component.

   SURFACE: white fill on a --cc-border hairline, no shadow. This is the third
   card treatment and all three come from their own comps: group-card is
   outline with no fill, event-card is white on a soft shadow, and both the
   accepted Giving comps draw this one as white inside a hairline at both
   breakpoints. --cc-white and --cc-border are both existing tokens, so no new
   value enters the file. A card is not a section background and COL-01 does
   not reach it.

   THE ACTION'S BORDER IS REPAINTED, NOT A SIXTH BUTTON VARIANT. The comps
   draw a quiet hairline round this button, not outline-ink's near-black rule.
   The card repaints outline-ink's private border property the same way
   page-hero repaints outline-light in copy-below-mobile. The button section
   is unchanged and the variant list stays at five.

   The action is a plain Ink Outline button with the fluid modifier.

   THE LIST STATES NO WIDTH. It fills whatever box it is given.

   IT IS NOT CONTAINER-RESPONSIVE. The three-column rule below is a media
   query, so it reads the browser width and not the box width, exactly as
   event-card-grid does. GIVE-03 is mapped full-inset; a narrow slot would
   need that rule to become a container query.
   ========================================================================== */
.cc-give-method-card-list {
  /* The scan code's rail below 900px.

     IT IS NOT group-card's rail, and the first pass was wrong to reuse what
     group-card's mobile thumbnail then was - a 136px rail. group-card is now a
     full-width banner below 900px and a 184px rail only above it. group-card
     puts a name, a meeting line and a chevron beside its photo; this card puts
     a BUTTON there, and a button has a min-content width its neighbours do not.
     At a 375px layout the card interior is 311px, and that then-136px rail plus
     the 16px gap left 158px for a button whose min-content was 177px. It
     overflowed the card by 19px and wrapped its label. Measured 2026-08-24.

     80px instead. Both accepted mobile comps give the code about a fifth of
     the card's width and the button about two thirds; 80px is the nearest 8px
     step to that fifth and it restores the same split. On a phone the code is
     the label for the method, not the thing the reader scans - nobody scans a
     code on the phone they are holding, they press the button beside it. */
  --cc-give-qr-rail: 80px;

  /* The code's widest at 900px and above, where the card is vertical and the
     code would otherwise take the whole card interior. Three reference
     columns plus their two gutters: 3 x 68 + 2 x 48 = 300px, derived at
     --cc-canvas-max and held as an absolute, the same way every other
     grid-derived minimum on this site is held. It is the same arithmetic
     --cc-btn-w-desktop uses and lands on the same number; it is NOT that
     token, because a scan code and a button have no reason to move together.
     The accepted desktop comp leaves the code about 70% of the card's width
     and this is the nearest whole-column span. */
  --cc-give-qr-max-desktop: 300px;

  list-style: none;
  margin: 0;
  padding: 0;
  display: grid;
  grid-template-columns: 1fr;
  gap: var(--cc-space-4);
}

/* Same reasoning as event-card-grid: GIVE-03 puts a section-copy above the
   list on the same band, base.css zeroes every margin, and the space is
   declared on the element that follows SO THE PAGE STILL WRITES NO CSS. A
   list standing alone in a band takes no margin at all. */
.cc-section-copy + .cc-give-method-card-list {
  margin-block-start: var(--cc-space-6);
}

/* minmax(0, ...) ON BOTH TRACKS, NOT A BARE RAIL AND A BARE 1fr. A grid track
   floors at its content's min-content width by default, and the button in the
   right-hand track has a real one - its two paddings plus the shortest line
   its label can make. Below about 350px of layout width that floor is wider
   than the track, and a bare 1fr overflows the card instead of shrinking.
   With minmax(0, ...) the code rail yields first and the button track can go
   below its button's min-content, so the label wraps and NOTHING LEAVES THE
   CARD. Verified down to 320px, 2026-08-24. */
.cc-give-method-card {
  display: grid;
  grid-template-columns: minmax(0, var(--cc-give-qr-rail)) minmax(0, 1fr);
  gap: var(--cc-space-4);
  align-items: start;
  padding: var(--cc-space-4);
  background: var(--cc-white);
  border: 1px solid var(--cc-border);
  border-radius: var(--cc-radius-md);
}

/* Square at every width, and it fills its rail. object-fit contain, not
   cover: a scan code cropped is a scan code that does not scan. */
.cc-give-method-card__qr {
  display: block;
  width: 100%;
  aspect-ratio: 1;
  object-fit: contain;
  border-radius: var(--cc-radius-sm);
}

.cc-give-method-card__body {
  display: flex;
  flex-direction: column;
  gap: var(--cc-space-3);
  /* min-width: 0 so a long account string wraps inside the column instead of
     pushing the card wider than its grid cell. */
  min-width: 0;
}

.cc-give-method-card__name {
  margin: 0;
  font-family: var(--cc-font-display);
  font-size: var(--cc-fs-name);
  font-weight: var(--cc-weight-semibold);
  line-height: 1.25;
  color: var(--cc-text);
}

.cc-give-method-card__account {
  margin: 0;
  font-size: var(--cc-fs-body);
  color: var(--cc-text-muted);
  /* An account handle is one unbroken token and can be longer than the rail
     beside it. Break it rather than let it overflow the card. */
  overflow-wrap: anywhere;
}

/* margin-top: auto pins the action to the bottom of the body, so the buttons
   in a desktop row line up even when one account line wraps. */
/* THE SITE-WIDE MOBILE BUTTON CAP, SAME AS event-card__action. Founder ruling
   2026-08-22: below the breakpoint a full-width button stops at
   --cc-btn-max-mobile and centres there. Uncapped this one reached 738px at an
   899px layout width, beside an 80px scan code. Measured 2026-08-24.

   A STATED WIDTH, NOT A max-width, and min() so it can never exceed the
   column. margin-inline: auto is the centring, not spacing; it resolves to
   zero on a phone, where the column is under the cap and the button fills it.

   min-width: 0 releases the same content floor the card's tracks release, one
   level down: this slot is a flex item of the body and the button is a grid
   item of this slot, and each floors at the button's min-content unless told
   otherwise. Both have to be zeroed or the button still pushes out. */
.cc-give-method-card__action {
  display: grid;
  margin-top: auto;
  min-width: 0;
  width: min(var(--cc-btn-max-mobile), 100%);
  margin-inline: auto;
}
.cc-give-method-card__action .cc-btn {
  min-width: 0;
}

/* The quiet hairline described at the top of this component. Hover still
   fills to ink, so the control reads as the same button everywhere else on
   the site — only its resting border is calmed. */
.cc-give-method-card__action .cc-btn--outline-ink {
  --_btn-border: var(--cc-border);
  border-width: 1px;
}
.cc-give-method-card__action .cc-btn--outline-ink:hover {
  --_btn-border: var(--cc-ink);
}

@media (min-width: 900px) {
  /* THREE ACROSS AT EVERY DESKTOP WIDTH. Employee direction 2026-08-24,
     against the accepted desktop comp: the count is a property of the design,
     not something the available width gets to decide. An auto-fit rule was
     tried and taken back the same day — it dropped to two cards between 900px
     and about 1050px, which the comp does not do.

     THE GUTTER IS ONE STEP TIGHTER THAN THE PAGE GUTTER, not equal to it.
     Employee direction 2026-08-24: --cc-space-6, 32px, one step down the
     spacing ladder from --cc-space-7. The comp draws the cards closer than a
     grid-true 48px gutter puts them, and the step is the same move the hero
     rule gap already makes at this breakpoint. It is a declared departure
     from the desktop grid gutter, so it names --cc-space-6 directly rather
     than --cc-grid-gutter-desktop, which owns the 48px value and must not be
     read where the value is deliberately not 48.

     The tighter gutter gives the cards more room near the breakpoint.
     Plain action labels use the shared button padding. */
  .cc-give-method-card-list {
    grid-template-columns: repeat(3, 1fr);
    gap: var(--cc-space-6);
  }
  .cc-give-method-card__action .cc-btn--fluid {
    /* Restore the shared desktop floor after the mobile overflow guard;
       min() lets the action fit a card narrower than that reference span. */
    min-width: min(var(--cc-btn-w-desktop), 100%);
  }
  .cc-section-copy + .cc-give-method-card-list {
    margin-block-start: var(--cc-space-7);
  }
  /* Vertical and centred. One column, so the rail value is not read here and
     the code takes the card interior. align-content stretch plus the body's
     own auto top margin keeps every card in a row the same height with its
     button on one line. */
  .cc-give-method-card {
    grid-template-columns: 1fr;
    gap: var(--cc-space-5);
    padding: var(--cc-space-5);
    text-align: center;
  }
  .cc-give-method-card__body {
    height: 100%;
    gap: var(--cc-space-4);
  }
  /* Capped and centred. margin-inline: auto IS THE CENTRING, NOT SPACING, and
     it resolves to zero in a card interior narrower than the cap. */
  .cc-give-method-card__qr {
    max-width: var(--cc-give-qr-max-desktop);
    margin-inline: auto;
  }
}

/* ==========================================================================
   COMPONENT: emblem-panel  (id: emblem-panel)
   A solid colour ground that centres one emblem image. GIVE-02 drops it into
   feature-split's media slot as the church crest on ink: the "image" side of
   that split is a positioned mark on a colour field, not a photograph that
   fills the frame. That is the whole of the difference from a photo media -- a
   background colour and a contained image -- so it is a split media variant,
   not a layout of its own.

   It fills whatever box it is given. In the split's media cell that box is
   stretched to the copy's full height (feature-split --media-panel), so the
   ink runs the height of the section and the crest sits centred in it. The
   crest keeps its own proportion and is capped so it never outgrows a wide
   panel, the same way the info-list icon sizes are held static rather than
   derived from the grid.

   Variant: surface -- a white card holding one wide picture that scales with
   the panel.
   ========================================================================== */
.cc-emblem-panel {
  display: flex;
  align-items: center;
  justify-content: center;
  height: 100%;
  background: var(--cc-ink);
  padding: var(--cc-space-8);
}
/* THE CAP IS THE LARGEST CREST THE COPY STILL OUTGROWS, AND THAT IS WHY IT IS
   THIS NUMBER. At --cc-canvas-max the media-panel ground is 5 columns, 580px,
   and GIVE-02's copy stands 512px. 24rem leaves the crest 64px of clear height
   top and bottom -- exactly the ground's own padding -- so the copy still sets
   the band height. One step further, 25rem, and the crest is the taller of the
   two: the band grows 16px and the copy gains a dead strip under its action.

   It also lands on the accepted desktop comp's proportion. That comp draws the
   crest at 66% of its panel and 24rem of 580 is 66%. Proportion only; the
   comp's pixels set nothing here.

   Below about a 512px ground the cap stops applying and .cc-emblem-panel's
   padding sizes the crest instead, which is what happens at every width from
   the breakpoint up to roughly 1300px. Founder call 2026-08-31. */
.cc-emblem-panel__img {
  display: block;
  width: 100%;
  height: auto;
  max-width: 24rem;
}

/* Variant: surface. */
.cc-emblem-panel--surface {
  display: grid;
  grid-template-columns: repeat(var(--cc-grid-columns), minmax(0, 1fr));
  column-gap: var(--cc-grid-gutter);
  height: auto;
  padding: var(--cc-space-4);
  background: var(--cc-white);
  border-radius: var(--cc-radius-md);
  box-shadow: var(--cc-shadow-card-soft);
}
.cc-emblem-panel--light-1 {
  background: var(--cc-band-light-1);
}
.cc-step-card--white,
.cc-emblem-panel--white {
  background: var(--cc-white);
}
.cc-step-card--light-1,
.cc-emblem-panel--light-1 {
  /* Stronger edge definition for the tinted surface against a white band.
     White cards retain the original shared 6% shadow token. */
  --cc-shadow-card-soft: 0 2px 8px rgba(0, 0, 0, 0.12);
}
.cc-emblem-panel--surface .cc-emblem-panel__img {
  grid-column: 1 / -1;
  width: 100%;
  max-width: none;
}


.cc-section-copy + .cc-emblem-panel--surface {
  margin-block-start: var(--cc-space-4);
}
.cc-feature-split--flush + .cc-emblem-panel--surface {
  margin-block-start: var(--cc-space-6);
}

@media (min-width: 900px) {
  .cc-emblem-panel--surface {
    padding-block: var(--cc-space-5);
    padding-inline: 0;
  }
  .cc-emblem-panel--surface .cc-emblem-panel__img {
    grid-column: 2 / span 10;
  }
  .cc-feature-split--flush + .cc-emblem-panel--surface {
    margin-block-start: var(--cc-space-7);
  }
}

/* ==========================================================================
   COMPONENT: disclosure  (id: disclosure)
   Hides the lower part of a block behind a More / Less control. Content
   agnostic — it wraps whatever it is given. On About it wraps the beliefs
   bullet-list, and it replaced the Learn More button that the mobile comp
   showed there. Founder direction 2026-08-20: the button is gone, the labels
   are "More" and "Less", and the control runs at BOTH breakpoints because
   twenty beliefs is a long column on any screen.

   PROGRESSIVE ENHANCEMENT, AND THIS IS THE SAFETY PROPERTY. With no
   JavaScript the panel is at its natural height and the control is not
   rendered at all, so content can never be hidden with no way to reach it.
   js/disclosure.js opts each instance in by setting data-cc-disclosure-ready,
   and it only does that after measuring that the panel really is taller than
   the collapsed height. A short list therefore shows no control.

   THE COLLAPSED HEIGHT IS A HEIGHT, NOT AN ITEM COUNT. How many items fit
   depends on the width of the box, because items wrap. The two values below
   are set so About shows roughly five beliefs at each breakpoint; they are
   the tuning point and no selector needs touching to change them.

   The cut is softened with a mask gradient rather than a painted overlay, so
   it works on any band without knowing the band's colour.

   THE CHEVRON EXTENT IS 14 x 8 UNITS AND IT STAYS THERE. That is under the
   family's landscape keyline of 21, deliberately. It was enlarged to 21 x
   11.6 on 2026-08-20 and the founder reversed it the same day: the icon had
   looked missing to him because icons are CSS masks and do not paint from
   file://, not because it was too small. SERVE THE PAGE OVER HTTP BEFORE
   JUDGING AN ICON, and do not enlarge this one again.

   Variant: on-dark. Modifier: lead -- an always-shown block above a panel
   that collapses to zero height.
   ========================================================================== */
.cc-disclosure {
  /* --- Collapsed height (adjustable) ------------------------------------
     Mobile is much taller than desktop for the same item count because a
     narrow column wraps every item to two or three lines. */
  --cc-disclosure-collapsed-mobile: 30rem;
  --cc-disclosure-collapsed-desktop: 16rem;
  /* How far the fade at the cut runs, from the approved spacing scale. */
  --cc-disclosure-fade: var(--cc-space-6);

  /* Resolved per breakpoint by the media query at the end of this block. */
  --_disclosure-collapsed: var(--cc-disclosure-collapsed-mobile);

  /* --- The control's block extent (read-only) ----------------------------
     The toggle's target height and the gap above it, declared here on the
     root rather than on the toggle so a composing component can read the
     total. --cc-disclosure-control is that total: the gap plus the target.
     leader-profile subtracts it from a photograph's height so the control
     ends a set distance above the photograph's foot. READ, NEVER SET: it is
     derived from the two private terms below, and a composer that wants a
     different control changes disclosure, not this value.

     The target is a control minimum, not a grid value: 44px is the
     accessible touch target and the label alone does not reach it. The gap
     is explained on the toggle rule, which uses both. */
  --_toggle-target: 44px;
  /* The touch box's overhang past the label's line box, one side: the
     target less the body line, halved. The gap below already subtracts it
     so the space ABOVE the label is exactly --cc-space-5. The ready rule
     below does the same BELOW the label with a negative end margin, so a
     foot is measured to the word everywhere. Named publicly for a composer
     that sets its own end margin on the disclosure and so must subtract it
     itself: leader-profile does, in both variants. Founder direction
     2026-09-11: every More read ~8px long against the 64px desktop foot and
     the 48px mobile foot. READ, NEVER SET. */
  --cc-disclosure-control-overhang: calc(
    (var(--_toggle-target) - var(--cc-fs-body) * var(--cc-lh-body)) / 2
  );
  --_toggle-gap: calc(var(--cc-space-5) - var(--cc-disclosure-control-overhang));
  --cc-disclosure-control: calc(var(--_toggle-gap) + var(--_toggle-target));
}

/* Not rendered until the script opts the instance in. display:none rather
   than visibility or opacity so it is out of the tab order too. */
.cc-disclosure__toggle {
  display: none;
}

/* THE FOOT IS THE WORD, NOT THE TOUCH BOX. The toggle's 44px target
   overhangs the label's line box by --cc-disclosure-control-overhang on each
   side. The gap above the label already absorbs the top. This absorbs the
   bottom: the negative end margin pulls the box's lower overhang out of the
   flow, so a band's padding, a composer's foot or a following sibling
   measures from the word. The box still paints and still takes the tap in
   that strip. Only while the control is rendered; without it there is no
   box to pull. A composer that sets margin-block-end on the disclosure
   replaces this and subtracts the overhang itself; see leader-profile. */
.cc-disclosure[data-cc-disclosure-ready] {
  margin-block-end: calc(-1 * var(--cc-disclosure-control-overhang));
}

.cc-disclosure[data-cc-disclosure-ready] .cc-disclosure__panel {
  /* CLIP, NOT HIDDEN, AND ON THE BLOCK AXIS ONLY. overflow: hidden opens a
     new block formatting context, and a box that does that cannot let its
     text flow around a float outside it: leader-profile floats its
     photograph beside this panel and the copy inside must wrap it, then run
     under it. overflow-y: clip cuts the same pixels without opening a
     context, so the lines still shorten beside the float. The inline axis
     stays visible so a part inside the panel can bleed to the band edge, as
     leader-profile's panorama does, and mask-clip: no-clip keeps the fade
     from erasing that bleed, because a mask paints only inside its border
     box by default. Changed 2026-09-03 for leader-profile slice 2. The
     beliefs list and the kids copy see no difference: neither has a float
     or a bleed, and scrollHeight, which js/disclosure.js reads to open,
     still reports the full content height under clip. */
  overflow-x: visible;
  overflow-y: clip;
  max-height: var(--_disclosure-collapsed);
  transition: max-height var(--cc-transition);
  -webkit-mask-clip: no-clip;
  mask-clip: no-clip;
  -webkit-mask-image: linear-gradient(
    to bottom,
    #000 calc(100% - var(--cc-disclosure-fade)),
    transparent 100%
  );
  mask-image: linear-gradient(
    to bottom,
    #000 calc(100% - var(--cc-disclosure-fade)),
    transparent 100%
  );
}
/* Open: no fade. The script writes the inline max-height that the transition
   runs to, so height is not set here.

   THE ATTRIBUTE IS REPEATED ON PURPOSE. The collapsed rule above is
   .cc-disclosure[<attr>] .cc-disclosure__panel, which is one selector heavier
   than a plain .cc-disclosure--open .cc-disclosure__panel. Without the
   attribute here the fade stays painted while the panel is open. Found in
   review, 2026-08-20. */
.cc-disclosure[data-cc-disclosure-ready].cc-disclosure--open
  .cc-disclosure__panel {
  -webkit-mask-image: none;
  mask-image: none;
}

.cc-disclosure[data-cc-disclosure-ready] .cc-disclosure__toggle {
  display: inline-flex;
  align-items: center;
  gap: var(--cc-space-2);
  /* THE VISIBLE GAP IS ONE ITEM GAP, NOT ONE MARGIN. Founder direction
     2026-08-20: the control must sit the same distance from the list as one
     list item sits from the next, and it must read the same whether the panel
     is open or closed.

     The touch target is taller than the label's line box, and align-items:
     center puts half that difference above the words, so a plain margin of
     --cc-space-5 rendered 32.5px of visible space against the list's own 24px.
     Subtracting the overshoot leaves exactly --cc-space-5. Both terms are read
     rather than typed, so a change to the type scale or to the touch target
     keeps the gap correct on its own.

     The margin does not depend on the panel's state, so More and Less sit at
     the same distance by construction. What still differs is the mask fade in
     the collapsed state, which softens the last 32px of ink and cannot be
     equalised by spacing.

     Both values are declared on .cc-disclosure, where --cc-disclosure-control
     sums them for composers; see there. */
  margin-top: var(--_toggle-gap);
  min-height: var(--_toggle-target);
  padding: 0;
  border: 0;
  background: none;
  font-family: var(--cc-font-body);
  font-size: var(--cc-fs-body);
  font-weight: var(--cc-weight-semibold);
  line-height: var(--cc-lh-body);
  color: var(--cc-red);
  cursor: pointer;
  transition: color var(--cc-transition);
}
.cc-disclosure__toggle:hover {
  color: var(--cc-red-strong);
}
.cc-disclosure__toggle:focus-visible {
  outline: none;
  border-radius: var(--cc-radius-sm);
  box-shadow: var(--cc-focus-ring);
}
.cc-disclosure__toggle .cc-icon {
  width: var(--cc-icon-btn);
  height: var(--cc-icon-btn);
  transition: transform var(--cc-transition);
}
/* One chevron file serves both states. Attribute repeated for the same
   specificity reason as the panel rule above. */
.cc-disclosure[data-cc-disclosure-ready].cc-disclosure--open
  .cc-disclosure__toggle
  .cc-icon {
  transform: rotate(180deg);
}

/* Variant: on-dark — the control on an ink band. */
.cc-disclosure--on-dark .cc-disclosure__toggle {
  color: var(--cc-text-on-dark);
}
.cc-disclosure--on-dark .cc-disclosure__toggle:hover {
  color: var(--cc-text-on-dark-muted);
}

/* Modifier: lead.
   flow-root contains the first-child margin within the collapsible panel.
   The lead mask covers the whole row; which column fades depends on its height.
   The panel and toggle use the existing disclosure data attributes. */
.cc-disclosure--lead {
  --cc-disclosure-collapsed-mobile: 0px;
  --cc-disclosure-collapsed-desktop: 0px;
}
.cc-disclosure--lead > .cc-disclosure__panel {
  display: flow-root;
}
.cc-disclosure--lead > .cc-disclosure__panel > :first-child {
  margin-block-start: var(--cc-space-6);
}
.cc-disclosure--lead[data-cc-disclosure-ready] > .cc-disclosure__panel {
  overflow-clip-margin: var(--cc-space-3);
}
.cc-disclosure--lead[data-cc-disclosure-ready]:not(.cc-disclosure--open)
  > .cc-disclosure__lead {
  -webkit-mask-image: linear-gradient(
    to bottom,
    #000 calc(100% - var(--cc-disclosure-fade)),
    transparent 100%
  );
  mask-image: linear-gradient(
    to bottom,
    #000 calc(100% - var(--cc-disclosure-fade)),
    transparent 100%
  );
  /* Extending the mask beyond the lead keeps its final line partially opaque. */
  -webkit-mask-size: 100% calc(100% + var(--cc-space-3));
  mask-size: 100% calc(100% + var(--cc-space-3));
  -webkit-mask-repeat: no-repeat;
  mask-repeat: no-repeat;
}


.cc-emblem-panel--surface + .cc-disclosure--lead,
.cc-emblem-panel--surface + .cc-disclosure--preview {
  margin-block-start: var(--cc-space-6);
}

/* Hint the final line of the marked text block. Without a marked block,
   preview one and a half body lines. The 5px optical adjustment keeps the
   clipped letter tops legible beneath the fade. JS measures the block end. */
.cc-disclosure--preview {
  --cc-disclosure-collapsed-mobile: calc(var(--cc-disclosure-preview-end, calc(var(--cc-fs-body) * var(--cc-lh-body) * 2)) - var(--cc-fs-body) * var(--cc-lh-body) * 0.5 + 5px);
  --cc-disclosure-collapsed-desktop: var(--cc-disclosure-collapsed-mobile);
  --cc-disclosure-fade: calc(var(--cc-fs-body) * var(--cc-lh-body) * 0.5);
}
.cc-disclosure--preview > .cc-disclosure__panel {
  display: flow-root;
}
/* Let expanded card shadows paint beyond the panel without changing layout
   height, card/control spacing, or the collapsed preview cutoff. */
.cc-disclosure--preview.cc-disclosure--open > .cc-disclosure__panel {
  overflow: clip;
  overflow-clip-margin: var(--cc-space-3);
}
.cc-disclosure--preview .cc-disclosure__lead + .cc-section-copy {
  margin-block-start: var(--cc-space-6);
}

@media (prefers-reduced-motion: reduce) {
  .cc-disclosure[data-cc-disclosure-ready] .cc-disclosure__panel,
  .cc-disclosure__toggle .cc-icon,
  /* message-form's fold runs on the same max-height motion; its script
     finishes at once when this matches. */
  .cc-message-form[data-cc-mail-ready] {
    transition: none;
  }
}

@media (min-width: 900px) {
  .cc-disclosure {
    --_disclosure-collapsed: var(--cc-disclosure-collapsed-desktop);
  }
}

/* ==========================================================================
   COMPONENT: media-frame  (id: media-frame)
   Rounded, clipped container for a content photograph. The frame owns its own
   proportion so it holds shape with no help from any surrounding page CSS.
   Proportion, radius, and shadow are exposed as custom properties so a
   composing component (feature-split) can change them per breakpoint without
   a second copy of this object.

   Framing: --cc-photo-focal and --cc-photo-zoom, with the optional
   --cc-photo-focal-desktop and --cc-photo-zoom-desktop from 900px up; the
   shared photo contract documented on .cc-hero__photo below. Same names on
   both photographic components.
   Variants: default (16/10) | wide (2/1) | widescreen (16/9) |
             pano (2470/1022, one ratio) |
             flush (square corners, no shadow) | video (16/9, play badge)
   Modifiers: phone-standard (3/2) | phone-feature (4/3) — phone emphasis,
              below 900px only; no modifier is quiet
   ========================================================================== */
.cc-media-frame {
  --cc-media-frame-ratio: 16 / 10;
  --cc-media-frame-radius: var(--cc-radius-md);
  --cc-media-frame-shadow: var(--cc-shadow-card);

  /* --- Framing (adjustable, per instance) --------------------------------
     Contract documented on .cc-hero__photo. 35% rather than the CSS default
     of 50% because a frame this wide crops a tall photograph heavily on the
     vertical, and faces sit above the middle of almost every photograph of
     people. At 50% the review photographs lose the tops of their heads.
     A default only decides what an UNTUNED placement looks like; every real
     placement sets its own value. */
  --cc-photo-focal: 50% 35%;
  --cc-photo-zoom: 1;

  margin: 0;
  aspect-ratio: var(--cc-media-frame-ratio);
  border-radius: var(--cc-media-frame-radius);
  overflow: hidden;
  background: var(--cc-ink);
  box-shadow: var(--cc-media-frame-shadow);
}
.cc-media-frame--wide {
  /* A wider-than-default frame. GIVE-07 is the only placement. Founder
     direction 2026-08-31 moved it from 12/5 to 2/1 - still wide against the
     16/10 default, but a taller box beside short copy on desktop. */
  --cc-media-frame-ratio: 2 / 1;
}
/* Variant: widescreen — 16 / 9 with no badge. VISIT-02 is the first
   placement, founder decision 2026-09-28: a named shape, so a page never
   writes its own ratio. Set through --cc-media-frame-ratio like wide, so the
   phone-emphasis modifiers still outrank it below 900px. Not video: that
   variant adds the play badge and locks aspect-ratio itself. */
.cc-media-frame--widescreen {
  --cc-media-frame-ratio: 16 / 9;
}
.cc-media-frame--flush {
  --cc-media-frame-radius: 0;
  --cc-media-frame-shadow: none;
}
/* Variant: pano — a panoramic frame for a wide group photograph. ABOUT-03's
   family panorama is the first placement, where leader-profile bleeds it to
   the band edges. The ratio matches the source, 2470 x 1022, so the whole
   photograph shows at every width with no crop, founder direction 2026-09-03.
   One ratio at all widths: on a 390px phone the box is ~161px tall and the
   faces read small, the accepted trade for showing the full frame uncropped.
   A photograph decision, adjustable here, not a grid value. */
.cc-media-frame--pano {
  --cc-media-frame-ratio: 2470 / 1022;
}

/* Modifiers: phone-standard | phone-feature — phone emphasis, below 900px
   only. On a phone a frame is nearly always full width, so height is the one
   lever that says how much a photograph matters. Three named levels, no free
   ratios, founder direction 2026-09-26:
     quiet      no modifier; the frame's own phone shape (2 / 1 where
                media-bleed-mobile sets it). A pause or supporting mood.
     standard   3 / 2, the camera's own shape. A photograph carrying content.
     feature    4 / 3. A high point of the page story; one or two a page.
   Set as aspect-ratio itself, so no composing component's phone ratio
   outranks the choice. Released at 900px below. Not for the video variant,
   which is 16 / 9 everywhere. */
.cc-media-frame--phone-standard {
  aspect-ratio: 3 / 2;
}
.cc-media-frame--phone-feature {
  aspect-ratio: 4 / 3;
}

/* Variant: video — a centred play badge over the photograph.

   PRESENTATIONAL ONLY, AND THAT IS DELIBERATE. It says "this is a video" and
   nothing more; it is not a control and it starts nothing. HOME-07 and VISIT-05
   both hand off to YouTube or Church Center in a later pass, and the affordance
   is settled there, not here. Drawn from two pseudo-elements so the page markup
   carries no badge node at all — which also keeps it out of the accessibility
   tree and out of the pointer path without an aria attribute to remember.

   ::before is the ring and ::after is the triangle, in that order, because the
   later pseudo-element paints on top.

   This variant supersedes the .home-watch__badge block in the website's
   page-shell.css, which is the same badge written as page CSS for one section
   of one page. Home moves onto this variant in a Website Build session; until
   it does, both exist and the website copy is the one Home renders.

   Badge size is a designer-set static value, the same convention the icon sizes
   follow, and it steps once at the breakpoint because the desktop photograph is
   much larger. Everything else derives from it, so one value moves the whole
   badge. */
.cc-media-frame--video {
  --cc-media-frame-badge-size: 4.5rem;
  --cc-media-frame-badge-ring: 3px;

  position: relative;
  /* Always 16 / 9, the shape of the YouTube player it stands for. Founder
     direction 2026-09-26. Set as aspect-ratio itself, not through
     --cc-media-frame-ratio, so no composing component's ratio can reshape it. */
  aspect-ratio: 16 / 9;
}
.cc-media-frame--video::before,
.cc-media-frame--video::after {
  content: "";
  position: absolute;
  pointer-events: none;
}
.cc-media-frame--video::before {
  inset: 0;
  margin: auto;
  width: var(--cc-media-frame-badge-size);
  height: var(--cc-media-frame-badge-size);
  border: var(--cc-media-frame-badge-ring) solid var(--cc-white);
  border-radius: var(--cc-radius-pill);
  background: rgba(0, 0, 0, 0.22);
}
/* A CSS triangle: the left border is the ink and the other two are the taper.
   The 0.25 and 0.1528 factors reproduce the founder-approved Home badge exactly
   at 4.5rem — 1.125rem of ink against 0.6875rem of taper — and carry the same
   proportion to the desktop size instead of restating a second pair of values.
   The -38% rather than -50% is optical: a triangle's mass sits left of its own
   box, so a true centre reads as sitting too far left inside the ring. */
.cc-media-frame--video::after {
  top: 50%;
  left: 50%;
  transform: translate(-38%, -50%);
  border-left: calc(var(--cc-media-frame-badge-size) * 0.25) solid var(--cc-white);
  border-top: calc(var(--cc-media-frame-badge-size) * 0.1528) solid transparent;
  border-bottom: calc(var(--cc-media-frame-badge-size) * 0.1528) solid transparent;
}
.cc-media-frame__img {
  width: 100%;
  height: 100%;
  object-fit: cover;
  object-position: var(--cc-photo-focal);
  scale: var(--cc-photo-zoom);
  transform-origin: var(--cc-photo-focal);
  display: block;
}

/* The badge is the one thing in this component that steps at the breakpoint,
   because the desktop photograph is much larger and a badge that does not grow
   with it reads as a stray mark. Ring width does not step; a hairline ring is a
   hairline ring at both sizes. */
@media (min-width: 900px) {
  .cc-media-frame--video {
    --cc-media-frame-badge-size: 6rem;
  }
  /* Desktop framing, when the placement sets it; otherwise the one framing
     holds at every width. See the contract on .cc-hero__photo. */
  .cc-media-frame__img {
    object-position: var(--cc-photo-focal-desktop, var(--cc-photo-focal));
    scale: var(--cc-photo-zoom-desktop, var(--cc-photo-zoom));
    transform-origin: var(--cc-photo-focal-desktop, var(--cc-photo-focal));
  }
  /* Phone emphasis is released: the frame returns to the ratio it is given. */
  .cc-media-frame--phone-standard:not(.cc-media-frame--video),
  .cc-media-frame--phone-feature:not(.cc-media-frame--video) {
    aspect-ratio: var(--cc-media-frame-ratio);
  }
}

/* ==========================================================================
   COMPONENT: series-card  (id: series-card)
   The latest service: its linked graphic and caption, "Latest Service"
   then the video title. HOME-02 is the first placement, where it
   supports the service times and never leads them. Founder rulings
   2026-09-29 are in project/active-work.md.
   Parts:     __media (a media-frame), __caption > __label + __title
   Composes:  media-frame

   THE GRAPHIC IS NEVER CROPPED. A series graphic carries its own words, so
   the frame takes the picture's own shape instead of imposing one. The img
   carries width and height attributes, which hold its space before it loads.
   media-frame keeps its radius and shadow; only its ratio and its crop are
   released, and only inside this card, so no other frame changes.

   THE MODE SWITCHES ON THE SITE BREAKPOINT, NOT ON THE CARD'S WIDTH. On a
   phone the card is 343-836px wide and on desktop 346-588px, so the two
   ranges overlap and no container width can tell them apart.
   ========================================================================== */
.cc-series-card {
  /* Below 900px the card is its own 4-column grid from the tokens: picture on
     2 columns, caption on 2, the caption centred on the picture. */
  display: grid;
  grid-template-columns: repeat(var(--cc-grid-columns), 1fr);
  column-gap: var(--cc-grid-gutter);
  align-items: center;
}
.cc-series-card__media {
  grid-column: span 2;
}
.cc-series-card .cc-media-frame {
  aspect-ratio: auto;
}
.cc-series-card .cc-media-frame__img {
  height: auto;
  object-fit: contain;
  scale: none;
}
/* A linked service graphic signals its YouTube destination without extra copy. */
.cc-series-card__link {
  display: block;
  position: relative;
}
.cc-series-card__link:focus-visible {
  outline: 3px solid var(--cc-text);
  outline-offset: 4px;
}
.cc-series-card__play {
  /* Intrinsic control cue: 48–72px stays legible on the small mobile graphic. */
  width: clamp(48px, 12%, 72px);
  aspect-ratio: 28.57 / 20;
  position: absolute;
  top: 50%;
  left: 50%;
  transform: translate(-50%, -50%);
  pointer-events: none;
}
.cc-series-card__play::after {
  content: "";
  position: absolute;
  inset: 0;
  background: #fff;
  clip-path: polygon(40% 28.6%, 66% 50%, 40% 71.45%);
}
.cc-series-card__play::before {
  content: "";
  position: absolute;
  inset: 0;
  background: rgb(20 20 20 / 65%);
  mask: url("../assets/icons/youtube.svg") center / contain no-repeat;
}
.cc-series-card__link:hover .cc-series-card__play::before,
.cc-series-card__link:focus-visible .cc-series-card__play::before {
  background: rgb(20 20 20 / 90%);
}
.cc-series-card__caption {
  grid-column: span 2;
  display: flex;
  flex-direction: column;
  gap: var(--cc-space-1);
  margin: 0;
}
/* The label: the feature-split kicker's treatment, in the muted text colour
   so it steps back from the title. Tracking 0.18em is the kicker ruling. */
.cc-series-card__label {
  font-family: var(--cc-font-body);
  font-size: var(--cc-fs-small);
  font-weight: var(--cc-weight-regular);
  line-height: var(--cc-lh-snug);
  letter-spacing: 0.18em;
  text-transform: uppercase;
  color: var(--cc-text-muted);
}
/* The title matches info-list's title exactly, so on HOME-02 the series reads
   at the same level as "Sunday Service" and below the section heading. */
.cc-series-card__title {
  font-family: var(--cc-font-body);
  font-size: var(--cc-fs-body);
  font-weight: var(--cc-weight-bold);
  line-height: 1.3;
  color: var(--cc-text);
}
/* The title sits in curly quotes, founder 2026-09-29. The quotes are drawn
   here, so the title text stays exactly as Page Content supplies it. */
.cc-series-card__title {
  quotes: "\201C" "\201D";
}
.cc-series-card__title::before {
  content: open-quote;
}
.cc-series-card__title::after {
  content: close-quote;
}

@media (min-width: 900px) {
  /* The picture takes the full width and the caption is one line under it,
     label then title on the same baseline. The line wraps where the card is
     narrow or the title is long: at a 900px layout the card is about 346px,
     and "The Wide Open" still fits on one line. The wrapped row-gap is
     the phone's label-to-title gap, 4px, so a wrapped caption reads the same
     as the phone one. */
  .cc-series-card {
    grid-template-columns: 1fr;
  }
  .cc-series-card__media,
  .cc-series-card__caption {
    grid-column: 1;
  }
  .cc-series-card__caption {
    flex-direction: row;
    flex-wrap: wrap;
    align-items: baseline;
    column-gap: var(--cc-space-4);
    row-gap: var(--cc-space-1);
    margin-top: var(--cc-space-3);
  }
}

/* ==========================================================================
   COMPONENT: feature-split  (id: feature-split)
   A band pairing a text stack (optional eyebrow, heading, body copy) with one
   photograph and a single action. One column below 900px; two columns above,
   where the photograph takes the height of the text column.
   Variants:  media-end (photo right on desktop, default) | media-start
   Modifiers: halves              — 6/6 instead of the standard 5/7 division
              actions-stacked     — two actions, each filling the text column
              narrow-slot         — 7/5 instead of the standard 5/7 division:
                                    the copy is the wide side, the slot narrow
              slot-centred        — the slot sits on the copy's own row and
                                    centres inside it
              media-after-text    — mobile order becomes copy, photo, action
              media-desktop-only  — photo is not shown below 900px
              media-bleed-mobile  — photo runs edge to edge below 900px
              media-bleed-desktop — photo drives the band height and runs to
                                    the band's outer edge at 900px and up
              media-panel         — media slot is a full-height colour ground
                                    five columns wide holding an emblem-panel;
                                    copy 7
              media-whole         — the picture is never cropped and sits on
                                    a soft glow; on desktop its height is the
                                    copy pane's, out to the band edge
              slot-float          — a small item under the heading on a
                                    phone; floats in columns 7-11 on desktop
              flush               — no side inset and no block padding: the
                                    split sits in a box that gives both
   Parts:     __kicker (small bold capitals over the title), __note (small
              line under the action, optional icon in front), __caption
              (one line in a media-whole picture's open corner),
              __title--measure (a configurable title width limit
              in em)
   Composes:  section-eyebrow, media-frame, emblem-panel, button
   ========================================================================== */
.cc-feature-split {
  /* The band's own inset is the site page inset. Held in a private property
     because media-bleed-desktop negates it to run the photograph out to the
     band edge. The token steps at the breakpoint on its own, so there is no
     desktop override below. */
  --_split-pad-inline: var(--cc-page-inset);
  display: grid;
  grid-template-columns: 1fr;
  row-gap: var(--cc-space-6);
  padding-block: var(--cc-space-7);
  padding-inline: var(--_split-pad-inline);
}

.cc-feature-split__media { order: 1; }
.cc-feature-split__body { order: 2; }

/* The slot takes one action on most bands and two on VISIT-07, so it is a
   column with a gap rather than a bare box. align-items is flex-start, not
   stretch: above the breakpoint a single action is fit-content and sits at the
   column's leading edge, and stretch would silently widen every existing
   one-button band. */
.cc-feature-split__actions {
  order: 3;
  display: flex;
  flex-direction: column;
  align-items: flex-start;
  gap: var(--cc-space-4);
}

/* Modifier: actions-hidden ---------------------------------------------------
   Suppresses the actions block at every width. display:none, not
   cc-visually-hidden, so a dead control is not left focusable in the
   accessibility tree. The __actions markup stays, so the button is restored by
   removing this class. GIVE-07 hides its Give Online button by founder
   direction 2026-08-31; the button stays canonical Page Content. */
.cc-feature-split--actions-hidden .cc-feature-split__actions {
  display: none;
}

.cc-feature-split__body {
  display: flex;
  flex-direction: column;
  gap: var(--cc-space-4);
}
/* section-eyebrow carries its own bottom margin for standalone use; inside
   this stack the flex gap owns the rhythm. */
.cc-feature-split__body .cc-eyebrow {
  margin-bottom: 0;
}

/* Shares the section heading step. This carried a private size until SYS-02
   phase 2 - 2px larger than --cc-fs-h2 on mobile so a long heading wrapped the
   way the accepted mobile comp shows, and identical to it at desktop. That is
   one size wearing two names. The mobile value it was protecting becomes the
   shared step's own mobile value in phase 3, so the wrap survives the merge. */
.cc-feature-split__title {
  margin: 0;
  font-family: var(--cc-font-display);
  font-size: var(--cc-fs-h2);
  font-weight: var(--cc-weight-semibold);
  line-height: var(--cc-lh-snug);
  color: var(--cc-text);
}

.cc-feature-split__text {
  display: flex;
  flex-direction: column;
  gap: var(--cc-space-4);
}
.cc-feature-split__text p {
  margin: 0;
  font-size: var(--cc-fs-body);
  line-height: var(--cc-lh-body);
  color: var(--cc-text-muted);
}

/* A bold body-size lead-in inside the body stack: "You can:" over a checks
   list, "Ready to give?" over an action note. Body size and full text colour,
   so it starts a labelled group without reading as a second heading (__title)
   or as muted running copy (__text p). */
.cc-feature-split__label {
  margin: 0;
  font-family: var(--cc-font-body);
  font-size: var(--cc-fs-body);
  font-weight: var(--cc-weight-bold);
  color: var(--cc-text);
}

/* media-panel's closing block: a lead-in and its note (__ready) beside the
   action (__foot). GIVE-02's "Ready to give?" over the ChurchTrac button.

   Scoped to media-panel on purpose. This is that variant's arrangement, not a
   shared feature-split part, and every other split keeps its action in the
   separate __actions item. Mobile stacks; the desktop block sets the row.

   The __ready gap is a half-step, not the body stack's step: the note reads as
   a continuation of the label above it rather than as a separate paragraph. */
.cc-feature-split--media-panel .cc-feature-split__foot {
  display: flex;
  flex-direction: column;
  gap: var(--cc-space-5);
  /* A hairline closes the list above and opens the action. It is the only
     rule in the band, so it reads as a divider rather than as one of a set. */
  border-top: 1px solid var(--cc-border);
  padding-block-start: var(--cc-space-6);
}
.cc-feature-split--media-panel .cc-feature-split__ready {
  display: flex;
  flex-direction: column;
  gap: var(--cc-space-1);
}

/* __kicker: a short label over the title, "Sermons online" on the Watch
   section. The small step in regular weight, widely tracked capitals: light
   and calm over the heading. Smaller than the eyebrow's text and not an
   eyebrow, no rule. Founder direction 2026-09-26. Text colour, not red: red
   holds 3.17:1, too low for 16px text. Regular, the body copy's weight, not
   medium: on a phone the medium kicker outweighed the title below it.
   Tracking 0.18em, down from 0.3em, for the same reason; it matches
   sub-heading and the pull-quote pathway, the library's other spaced
   capitals. Founder direction 2026-09-29. */
.cc-feature-split__kicker {
  margin: 0;
  font-family: var(--cc-font-body);
  font-size: var(--cc-fs-small);
  font-weight: var(--cc-weight-regular);
  line-height: var(--cc-lh-snug);
  letter-spacing: 0.18em;
  text-transform: uppercase;
  color: var(--cc-text);
}
/* The kicker labels the title, so it sits a half step closer to it than the
   body stack's 16px gap: 8px. At 16 it floated as far from the title as the
   paragraphs sit from each other. Founder direction 2026-09-29. */
.cc-feature-split__kicker + .cc-feature-split__title {
  margin-block-start: calc(var(--cc-space-2) - var(--cc-space-4));
}

/* __note: one small line under the action, "Opens our YouTube channel in a
   new tab". Sits in __actions after the button. An icon, when present, goes
   in front of the words and takes the small icon size. */
.cc-feature-split__note {
  display: flex;
  align-items: center;
  gap: var(--cc-space-2);
  margin: 0;
  font-size: var(--cc-fs-small);
  line-height: var(--cc-lh-body);
  color: var(--cc-text-muted);
}
.cc-feature-split__note .cc-icon {
  width: var(--cc-icon-sm);
  height: var(--cc-icon-sm);
}

/* __caption: one short line set into the picture's open lower corner, in the
   media slot. The Watch section's "Recent series from Sunday mornings".
   Desktop only: it exists to fill the open corner the picture leaves beside
   the copy, and below 900px the picture spans the width with no corner to
   fill, where it only put another line ahead of the heading. From 900px up
   it hangs from the picture's bottom edge and takes no row of its own, so it
   adds no height to the band. The note's size and line height, the smallest
   step, semibold. Founder direction 2026-09-26. */
.cc-feature-split__caption {
  display: none;
  margin: 0;
  font-family: var(--cc-font-display);
  font-size: var(--cc-fs-small);
  font-weight: var(--cc-weight-semibold);
  line-height: var(--cc-lh-body);
  text-align: end;
  color: var(--cc-text);
}

/* Modifier: media-whole — the picture shows whole and is never cropped.
   For a cut-out image with transparent edges, the Watch section's sermon
   posters first, founder direction 2026-09-26. The frame drops its ink
   ground so the band shows through; radius and shadow are the placement's
   choice through media-frame's own flush variant. Below 900px the picture
   takes the full width at its own proportion. */
.cc-feature-split--media-whole .cc-media-frame {
  aspect-ratio: auto;
  background: transparent;
}
.cc-feature-split--media-whole .cc-media-frame__img {
  height: auto;
  object-fit: contain;
  scale: none;
}
/* The slot holds the picture and its overlaid caption, and carries a soft light glow
   behind the picture: a wide pale ellipse on the band that lifts the posters
   off it. Drawn on a pseudo-element that reaches past the slot, under the
   picture, so it shades the band without a box edge. On desktop it reaches
   back under the copy, so the light runs under both halves. Founder direction
   2026-09-26, after a GPT Image reference. */
.cc-feature-split--media-whole .cc-feature-split__media {
  position: relative;
  isolation: isolate;
}
.cc-feature-split--media-whole .cc-feature-split__media > :first-child {
  display: block;
}
.cc-feature-split--media-whole .cc-feature-split__media::before {
  content: "";
  position: absolute;
  /* Never past the slot's far side: the slot already reaches the band edge
     on desktop and the page edge on a phone, and any overhang there widens
     the page and scrolls it sideways. Measured 2026-09-26: 18px of sideways
     scroll at 375 before this. Below 900px it does not reach back either;
     the copy is under the picture there, not beside it. */
  inset: -20% 0;
  z-index: -1;
  pointer-events: none;
  background: radial-gradient(ellipse closest-side at 50% 50%,
    color-mix(in srgb, var(--cc-white) 70%, transparent) 0%,
    color-mix(in srgb, var(--cc-white) 25%, transparent) 55%,
    transparent 100%);
}

/* Modifier: media-after-text — photo sits between the copy and the action. */
.cc-feature-split--media-after-text .cc-feature-split__body { order: 1; }
.cc-feature-split--media-after-text .cc-feature-split__media { order: 2; }

/* Modifier: narrow-slot — mobile order only. The division itself is in the
   900px block below.

   The narrow slot is never a lead photograph; it is a short trailing item, so
   it follows the copy rather than leading it the way the default slot does.
   Stated here rather than borrowed from media-after-text, which exists to move
   a PHOTOGRAPH and would put a second class on the page for a behaviour this
   division always wants. */
.cc-feature-split--narrow-slot .cc-feature-split__body { order: 1; }
.cc-feature-split--narrow-slot .cc-feature-split__media { order: 2; }

/* Modifier: halves — a 6/6 division instead of the standard 5/7.

   VISIT-06, Before You Come, is five detail rows split across two columns with
   a rule between them and one action under the shorter column. That is this
   component with `divided`, not a new one: the slot already takes a text list
   rather than a photograph, and `divided` already draws the rule from the grid.
   Only the division changes, and 6/6 is the grid's own even split.

   THE HEADING IS ITS OWN ROW. __title moves out of __body and becomes a direct
   child spanning the full width, and the rule starts on the row below it. That
   is what the accepted desktop comp draws: the line runs beside the rows only,
   not up alongside the heading. Leaving the heading inside __body would put it
   in the same grid row as the first column of rows, and the pseudo-element,
   which stretches across whole rows, would climb to the top of it.

   The heading is not lifted out of the component, though. __title keeps the
   page inset that .cc-feature-split already applies, and a heading placed in
   the band beside the split would have no inset of its own — a page carries no
   CSS, so there would be nothing to give it one.

   BELOW THE BREAKPOINT THE TWO LISTS ARE ONE LIST. The comp shows five rows in
   one unbroken run, so the row gap between the two halves closes, the second
   list's first row takes back the hairline and the top padding that
   info-list's :first-child rule removes, and the first list's last row keeps
   the bottom padding its :last-child rule removes. The action keeps its own separation
   through a margin instead of the container gap. All three are released again
   at 900px, where the halves are side by side and the gap is the standard one.

   Only media-end is built. media-start with halves would need its own mirrored
   spans and nothing uses it. */
.cc-feature-split--halves {
  row-gap: 0;
}
/* The title sits outside __body so it can span both halves, so it carries the
   16px that __body's gap gives every other split title. One value at every
   width, the same as those titles. */
.cc-feature-split--halves > .cc-feature-split__title {
  margin-bottom: var(--cc-space-4);
}
.cc-feature-split--halves .cc-feature-split__actions {
  margin-top: var(--cc-space-6);
}
.cc-feature-split--halves .cc-feature-split__media .cc-info-list__item:first-child {
  border-top: 1px solid var(--cc-border);
  padding-top: var(--cc-space-4);
}
/* The other side of the same seam: the hairline between the halves sits 16px
   under the first list's last text line, as every divider in the run does. */
.cc-feature-split--halves .cc-feature-split__body .cc-info-list__item:last-child {
  padding-bottom: var(--cc-space-4);
}

/* Text slots retain a gap when stacked; adjacent list slots remain gapless. */
.cc-feature-split--halves:has(> .cc-feature-split__media > :is(.cc-feature-split__text, .cc-statement)) {
  row-gap: var(--cc-space-6);
}

/* Modifier: flush. Zeroes the inset also used by bleed modifiers. */
.cc-feature-split--flush {
  --_split-pad-inline: 0px;
  padding-block: 0;
}

/* Part: __title--measure. --cc-title-measure overrides the default text measure. */
.cc-feature-split__title--measure {
  max-width: var(--cc-title-measure, 7em);
  text-wrap: balance;
}

/* Modifier: slot-float — a small item floats in the slot beside the copy.
   HOME-02 first, where the slot holds series-card beside the service times.
   Founder rulings 2026-09-29.

   The title moves out of __body as a direct child, as halves does, so the
   slot can sit between the heading and the list on a phone. DOM order is
   title, media, body, actions; the base order values already give that
   sequence, so no order rule is needed.

   BELOW THE BREAKPOINT THE SLOT IS ITS OWN ELEMENT WITH ONE HAIRLINE UNDER
   IT, not another list row. The container gap closes and each seam carries
   its own step: 16 under the heading, 16 over and under the hairline, 32
   over the action. Released at 900px below.

   Only media-end is built, as halves. */
.cc-feature-split--slot-float {
  row-gap: 0;
}
.cc-feature-split--slot-float > .cc-feature-split__title {
  margin-bottom: var(--cc-space-4);
}
.cc-feature-split--slot-float .cc-feature-split__media {
  padding-bottom: var(--cc-space-4);
  border-bottom: 1px solid var(--cc-border);
}
.cc-feature-split--slot-float .cc-feature-split__body {
  padding-top: var(--cc-space-4);
}
.cc-feature-split--slot-float .cc-feature-split__actions {
  margin-top: var(--cc-space-6);
}

/* Modifier: media-desktop-only — the photograph is not shown below the
   breakpoint. The action then sits directly beneath the copy, which is the
   relationship the two already have above the breakpoint.

   Declared for mobile and released inside the existing desktop block below,
   the same way media-bleed-mobile is written, so no second breakpoint value
   enters this file.

   THE PHOTOGRAPH MUST CARRY loading="lazy". A browser still downloads an
   image inside a display:none box unless it is lazy, so without it a phone
   pays for a photograph it never sees. Hiding also removes the figure from
   the accessibility tree, which is correct here: the photograph supports the
   copy and carries no information of its own. */
.cc-feature-split--media-desktop-only .cc-feature-split__media {
  display: none;
}

/* Modifier: media-bleed-mobile — photo escapes the band's inline padding and
   sits flush with the band's top edge. */
.cc-feature-split--media-bleed-mobile {
  padding-block-start: 0;
}
.cc-feature-split--media-bleed-mobile .cc-feature-split__media {
  margin-inline: calc(var(--_split-pad-inline) * -1);
}
.cc-feature-split--media-bleed-mobile .cc-feature-split__media .cc-media-frame {
  --cc-media-frame-ratio: 2 / 1;
  --cc-media-frame-radius: 0;
  --cc-media-frame-shadow: none;
}

/* THE BLEED FOLLOWS THE PHOTOGRAPH, NOT THE TOP OF THE BAND. media-after-text
   moves the photograph below the copy, so the edge it now has to meet is the
   band's bottom one. Zeroing padding-block-start there would strip the space
   above the heading and still leave the photograph short of the edge it
   reaches. One shorthand restores the start and zeroes the end, so no second
   spacing value enters the file. GROUPS-09 is the first user; no existing
   band carries both classes. */
.cc-feature-split--media-bleed-mobile.cc-feature-split--media-after-text {
  padding-block: var(--cc-space-7) 0;
}

@media (min-width: 900px) {
  /* The band is the site column grid. Children are placed by column span, so
     every section on every page divides its width the same way and no band
     invents a ratio of its own. The previous `1fr 1fr` split the band 50/50;
     the accepted desktop comps show the text column at roughly a third and the
     photograph at roughly half, which is 4 columns against 7 with one column
     between them. Read off the comps as proportion, then snapped to the grid:
     the text column lands within 5px of what the comps show.

     align-items is `start`, not `stretch`. Under stretch a tall text column
     dragged the photograph and the action row down with it, which is what put
     the buttons below their copy on four sections.

     Three rows, and the third one is load-bearing. The photograph spans the
     whole stack, so whenever it is taller than the copy plus the action the
     grid has to put that extra height somewhere. With only two rows it grows
     both of them and the button rides down with the growth — by 67px on the
     section with the most copy and 129px on the section with the least, which
     is why the buttons looked inconsistent rather than uniformly low. The
     third row is `1fr`, so it absorbs all of the slack and the copy and its
     button stay locked together at the top.

     NO ROW GAP UP HERE. The mobile row-gap separates the stacked slot, copy
     and action. Side by side, the three rows sit in the copy column only, and
     a grid gap is charged between every pair of rows whether or not they hold
     anything. A band with no action still paid two gaps, 64px, under its copy,
     so the copy column beat a photograph or a closed list that was in truth
     the taller one, and the band ran long under both. Measured 2026-09-11 on
     About's What We Believe: the More word sat 81px above the band foot at
     1280 and 135px at 1024 against the 64px the padding sets. Founder
     direction 2026-09-11: every split, every page. So the gap moves onto the
     action as its own top margin, which is spent only when there is an
     action. halves already works this way and keeps its own rules below. */
  .cc-feature-split {
    grid-template-columns: repeat(var(--cc-grid-columns), 1fr);
    grid-template-rows: auto auto 1fr;
    column-gap: var(--cc-grid-gutter);
    row-gap: 0;
    align-items: start;
    padding-block: var(--cc-space-8);
  }
  .cc-feature-split__actions {
    margin-top: var(--cc-space-6);
  }
  /* Reapply after the desktop base padding rule. */
  .cc-feature-split--flush {
    padding-block: 0;
  }

  /* The two blocks are ADJACENT. The space between them is one gutter and
     nothing else.

     They used to be separated by an empty column — copy on 1-4, photograph on
     6-12 — which left a gutter, a whole column, and another gutter between
     them. The founder reported it as a widened gutter on the deployed page and
     it was not one: what showed was column 5 with a gutter on each side. It
     arrived with SYS-01 and was approved by implication rather than by intent.

     Founder decision 2026-08-18: the photograph is not reduced, the copy
     column takes the spare column instead. The founder's reasoning, in their
     words, is that the photograph should if anything take up more horizontal
     space, never less. The accepted desktop comps were reviewed alongside it
     and read as more balanced than the empty-column layout, which ran 58
     percent photograph to 32 percent copy. That reading is qualitative — a
     raster comp is not a dimensional authority — and the decision is the
     founder's, not a measurement. The photograph keeps all 7 columns.

     At the canvas maximum: photograph 764px, gutter 48px, copy 532px = 1344.

     Closing the gap to one gutter was not enough on its own. At the 24px
     gutter it then read as crowded, and the grid offers no value in between —
     two spans are either adjacent or separated by a whole column. So the
     gutter itself went to 48px. See the derivation in tokens.css. This
     component did not change again for it; it takes the new gutter as it
     takes the old one. */

  /* Variant: media-end (default) — text left, photograph right. */
  .cc-feature-split__body    { grid-column: 1 / span 5; grid-row: 1; }
  .cc-feature-split__actions { grid-column: 1 / span 5; grid-row: 2; }
  .cc-feature-split__media   { grid-column: 6 / span 7; grid-row: 1 / span 3; }

  /* Variant: media-start — photograph left, text right. Same two spans
     mirrored: photo takes columns 1-7, text takes 8-12. */
  .cc-feature-split--media-start .cc-feature-split__media {
    grid-column: 1 / span 7;
  }
  .cc-feature-split--media-start .cc-feature-split__body,
  .cc-feature-split--media-start .cc-feature-split__actions {
    grid-column: 8 / span 5;
  }

  /* NO TEXT MEASURE CAP HERE, DELIBERATELY. The column owns the width.

     A max-width of 32rem used to sit here, described as the measure taken from
     the accepted desktop comps. It never once applied. 32rem is 512px, and the
     copy column was 4 columns — 432px at the canvas maximum and narrower at
     every width below it — so the cap was always wider than the box it capped.
     Widening the column to 5 columns would have made it bind for the first
     time. On the 24px-gutter grid in force at that moment that was 546px, so
     the cap would have clipped 34px off the change. Removed 2026-08-18.

     The column can hold the measure on its own. At 532px — five columns on
     the current 48px-gutter grid — the 17px body copy runs about 62
     characters, inside the 45-75 range. If a cap is ever wanted back, it has
     to be re-derived against the column it will actually meet. */

  /* The photograph keeps its own declared proportion at desktop, exactly as it
     does on mobile. It used to be released to `auto` with height:100%, which
     made the text column the author of the photograph's height — more copy
     produced a taller photograph, and the layout had no say.

     Founder ruling 2026-08-16: the layout is canon and photographs are
     subservient to it. media-frame already declares 16/10, and the cleanest
     photograph in the accepted desktop comps measures 1.60. So the correct fix
     is to stop overriding the ratio, not to introduce a new number. The
     photograph crops into the frame through object-fit: cover. */

  /* media-desktop-only: the photograph appears from here up. */
  .cc-feature-split--media-desktop-only .cc-feature-split__media {
    display: block;
  }

  /* Mobile-only bleed is released above the breakpoint. */
  .cc-feature-split--media-bleed-mobile {
    padding-block-start: var(--cc-space-8);
  }
  .cc-feature-split--media-bleed-mobile.cc-feature-split--media-after-text {
    padding-block: var(--cc-space-8);
  }
  .cc-feature-split--media-bleed-mobile .cc-feature-split__media {
    margin-inline: 0;
  }
  .cc-feature-split--media-bleed-mobile .cc-feature-split__media .cc-media-frame {
    --cc-media-frame-ratio: 16 / 10;
    --cc-media-frame-radius: var(--cc-radius-md);
    --cc-media-frame-shadow: var(--cc-shadow-card);
  }

  /* A wide frame keeps its own ratio on desktop. The reset above re-frames the
     desktop media - radius and shadow return - but its 16/10 ratio is written
     for the plain frame the bleed normally carries. GIVE-07 wants ONE wide
     ratio at both widths, so the explicit wide variant holds it here; only the
     radius and shadow re-frame. The compound class outranks the reset, so order
     does not decide it. Founder direction 2026-08-31. */
  .cc-feature-split--media-bleed-mobile .cc-feature-split__media
    .cc-media-frame.cc-media-frame--wide {
    --cc-media-frame-ratio: 2 / 1;
  }

  /* Modifier: media-bleed-desktop — the photograph reaches the band's outer
     edge, so the block padding moves onto the text column.

     It used to carry its own column ratio (1 : 1.25), its own row template,
     and min-height: 34rem, and its description here used to say the photo set
     the band height. All of that existed to stop the photograph collapsing
     once the text column stopped feeding it a height. The band now inherits
     the site column grid and the photograph holds its own proportion, so none
     of it is needed and none of it was ever a derived number. */
  .cc-feature-split--media-bleed-desktop {
    padding-block: 0;
  }
  .cc-feature-split--media-bleed-desktop .cc-feature-split__body {
    padding-block-start: var(--cc-space-8);
  }
  /* The foot too. The copy column is its own padding here, and only the start
     side was ever put back, so a copy column taller than the photograph ran
     its button into the band foot: 32px short at 1024 while the desktop
     row-gap stood, 0 once it went. Mirrors the rule above on the action, the
     column's last item. Founder direction 2026-09-11: 64 under every split. */
  .cc-feature-split--media-bleed-desktop .cc-feature-split__actions {
    align-self: start;
    padding-block-end: var(--cc-space-8);
  }
  .cc-feature-split--media-bleed-desktop .cc-feature-split__media {
    margin-inline-end: calc(var(--_split-pad-inline) * -1);
  }
  .cc-feature-split--media-bleed-desktop.cc-feature-split--media-start
    .cc-feature-split__media {
    margin-inline-end: 0;
    margin-inline-start: calc(var(--_split-pad-inline) * -1);
  }
  .cc-feature-split--media-bleed-desktop .cc-feature-split__media .cc-media-frame {
    --cc-media-frame-radius: 0;
    --cc-media-frame-shadow: none;
  }
  /* A bled photograph meets the band's top, outer edge and foot, so a copy
     column taller than the frame left a strip of ground under it (14px on
     VISIT-07 at 1280, more below). Here the ratio becomes a floor: the slot
     stretches over the whole stack and the frame fills it, the extra height
     cropping through object-fit: cover. Scoped to the bleed only; a framed
     photograph keeps the 2026-08-16 ruling and never grows with its copy.
     The width is stated because with an auto width the aspect-ratio carries
     the taller floor across into the width, and the frame ran 244px past
     the band edge on HOME-04 at 1024. Founder direction 2026-09-26. */
  .cc-feature-split--media-bleed-desktop .cc-feature-split__media {
    align-self: stretch;
  }
  .cc-feature-split--media-bleed-desktop .cc-feature-split__media .cc-media-frame {
    inline-size: 100%;
    min-block-size: 100%;
  }

  /* Modifier: divided — a hairline in the gutter separates the two columns.

     THE SLOT HOLDS A TEXT LIST HERE, NOT A PHOTOGRAPH. About's What We Believe
     puts bullet-list, wrapped in disclosure, into .cc-feature-split__media. The
     slot and its media-* modifiers are named for a photograph because they were
     built for Home; the rename is deferred and this modifier does not start it.
     No base rule assumes an image, so the list drops into the slot unchanged.

     The line is a pseudo-element placed in the grid, so it is one rule and the
     page markup carries nothing. grid-row 1 / -1 with align-self stretch makes
     it reach the bottom of whichever column is taller — which holds at both
     states of the disclosure. justify-self start puts it on column 6's leading
     edge, and the negative half-gutter margin moves it to the gutter's centre,
     so the line is derived from the grid and no position is typed in.

     Declared inside the existing desktop block only, so no divider renders
     below the breakpoint and no second breakpoint value enters this file.
     Mobile stacks copy then list through media-after-text, which already
     exists; this modifier adds no mobile rule. */
  .cc-feature-split--divided::before {
    content: "";
    grid-column: 6;
    grid-row: 1 / -1;
    justify-self: start;
    align-self: stretch;
    width: 1px;
    margin-inline-start: calc(var(--cc-grid-gutter) / -2);
    /* NEUTRAL ON PURPOSE. DO NOT CORRECT THIS TOWARD THE COMP. The accepted
       About desktop comp draws this hairline warm, sampled at about #dcd1c5;
       --cc-border is dead neutral at #d9d9d9 and is the library's declared
       token for a hairline on a light band. Founder ruling 2026-08-20: keep
       the token, add no warm divider value. Carried as Divergence 7 in
       project/decisions-and-approvals.md. */
    background: var(--cc-border);
  }

  /* Mirrored: media-start gives the slot columns 1-7 and the copy 8-12, so the
     gutter the line sits in is the one before column 8. */
  .cc-feature-split--divided.cc-feature-split--media-start::before {
    grid-column: 8;
  }

  /* THE SLOT FILLS THE ROW WHEN IT HOLDS A DISCLOSURE, so the word More ends
     where the copy ends. Founder direction 2026-09-12, under the 2026-09-11
     rule of 64 beneath every split at every desktop width: at 1024 About's
     What We Believe copy column stood 7px taller than the closed list, so
     More sat 71 above the band foot while the copy sat 64. Measured before
     the change: copy 314, closed list 307 at 1024; 260 and 307 at 1440.

     The slot stretches to the row, and the disclosure stretches to the slot
     as its one grid item, margin box to grid area. That keeps the ready
     state's negative end margin honest: the touch box still overhangs the
     row by --cc-disclosure-control-overhang and the word itself ends at the
     row's foot, the same construction as beside the copy. The disclosure's
     own rows put the panel first and the control last; the panel keeps its
     closed height, and whatever the copy column is taller by sits between
     the panel and the control, inside the fade gap, where there is no ink to
     see it. Where the list is the taller column, 1440 and up, that surplus is
     zero and nothing moves.

     The closed height is not changed and no pixel is typed in, so a longer
     title or another paragraph from the Page Content owner keeps the 64 on
     its own, and js/disclosure.js is untouched. halves + divided, VISIT-06,
     holds an info-list, not a disclosure; :has() keeps it out. */
  .cc-feature-split--divided .cc-feature-split__media:has(> .cc-disclosure) {
    align-self: stretch;
    display: grid;
  }
  .cc-feature-split--divided .cc-feature-split__media > .cc-disclosure {
    display: grid;
    grid-template-rows: 1fr auto;
  }

  /* Modifier: media-whole — the picture fills the slot's width, and copy and
     picture read as one unit.

     The slot spans exactly the copy and action rows and stretches to them.
     THE POSTERS SET THE ROW HEIGHT, and the band keeps its standard block
     padding. Founder direction 2026-09-30. A placement crops its image so the
     picture's top and bottom are the lead poster's top and bottom, and
     declares that image's proportion on the slot as --cc-picture-ratio
     (default 16/10). The picture box is then exactly the drawn picture, as
     wide as the slot, so its outer edge is the page inset at every width.
     Founder direction 2026-09-27; before it the picture was capped at the
     pane's height and sat 52px in from the inset at 1440.

     The picture is in flow, so its height counts. Four rows: slack, copy,
     action, slack, and the slot spans all four. Where the picture is the
     taller side, at the canvas maximum 333px against a copy pane of about
     270px, the two slack rows share the surplus: the copy is centred on the
     picture and the action stays with its copy. Where the copy is taller the
     slack rows are 0 and the picture is centred in the slot. Until
     2026-09-30 the slot was a size container, the picture added no height,
     and at 1440 it overhung the band padding by up to 35px top and bottom.

     The caption still adds no height. It hangs from the picture's bottom,
     below.

     Half a gutter. A cut-out marketing picture is not a photograph and has
     no edge of its own, so the full gutter read as two separate halves; the
     slot takes back half of it. Founder direction 2026-09-26.

     The slot stops at the page inset on its far side, and the picture stays
     against the copy. The picture and the copy are one marketing card, so
     the gap between them stays half a gutter. Not a photograph rule: a photograph keeps its own grid
     edges. Founder direction 2026-09-27; before it the slot ran to the band
     edge and the picture touched the screen from 900 to about 1355px.
     Columns are unchanged: copy 5, slot 7. */
  /* The glow reaches back under the copy only here, where the copy is
     beside the picture. */
  .cc-feature-split--media-whole .cc-feature-split__media::before {
    inset-inline-start: -45%;
  }
  .cc-feature-split--media-whole.cc-feature-split--media-start .cc-feature-split__media::before {
    inset-inline-start: 0;
    inset-inline-end: -45%;
  }
  .cc-feature-split--media-whole {
    grid-template-rows: 1fr auto auto 1fr;
  }
  .cc-feature-split--media-whole .cc-feature-split__body    { grid-row: 2; }
  .cc-feature-split--media-whole .cc-feature-split__actions { grid-row: 3; }
  .cc-feature-split--media-whole .cc-feature-split__media {
    --_picture-w: 100cqw;
    grid-row: 1 / -1;
    align-self: stretch;
    display: flex;
    flex-direction: column;
    justify-content: center;
    container-type: inline-size;
    margin-inline-start: calc(var(--cc-grid-gutter) * -0.5);
  }
  .cc-feature-split--media-whole .cc-feature-split__media > :first-child {
    flex: none;
    width: var(--_picture-w);
    aspect-ratio: var(--cc-picture-ratio, 16 / 10);
  }
  .cc-feature-split--media-whole .cc-media-frame,
  .cc-feature-split--media-whole .cc-media-frame__img {
    width: 100%;
    height: 100%;
  }
  .cc-feature-split--media-whole.cc-feature-split--media-start .cc-feature-split__media {
    margin-inline-start: 0;
    margin-inline-end: calc(var(--cc-grid-gutter) * -0.5);
  }
  /* The caption hangs from the picture's bottom edge and ends one step in
     from the picture's own right edge, so it belongs to the picture wherever
     the picture sits: the same gap under the picture at every width, not
     pinned to the note's line. The picture box is centred on the slot, so
     its bottom is half the slot plus half its own height.
     Founder direction 2026-09-26.

     In a slot 704px wide or more the caption rises 15px from that edge, up
     into the picture's transparent foot, so it sits closer to the posters.
     A founder-directed value, not the spacing scale: Cheyne 2026-09-27.
     Narrower, it drops one step, 8px, below the edge, so it reads as the
     posters' line and not as touching them: the caption keeps its text width while
     the picture shrinks, so its start runs over the lead poster, which
     reaches the picture's foot. 704 is where the caption, about 262px of
     "Recent series from Sunday mornings", clears the lead poster's end (56%
     of the Watch posters' width) by a 24px step. A longer caption or another
     picture needs a new threshold. The slot is the inline-size container. */
  .cc-feature-split--media-whole .cc-feature-split__caption {
    --_caption-rise: calc(var(--cc-space-2) * -1);
    position: absolute;
    inset-inline-end: calc(100cqw - var(--_picture-w) + var(--cc-space-5));
    top: calc(50% + var(--_picture-w) / (var(--cc-picture-ratio, 16 / 10)) / 2 - var(--_caption-rise));
    display: block;
  }
  @container (min-width: 704px) {
    .cc-feature-split--media-whole .cc-feature-split__caption {
      --_caption-rise: 15px;
    }
  }
  .cc-feature-split--media-whole.cc-feature-split--media-start .cc-feature-split__caption {
    inset-inline-end: var(--cc-space-5);
  }

  /* Modifier: halves — the even 6/6 division. Declared after media-start so the
     two never fight over the same spans at equal specificity; halves is
     media-end only and says so above.

     At the canvas maximum each half is 648px: six 68px columns and five 48px
     gutters. The rule takes column 7's leading edge and the same negative
     half-gutter as divided, so it lands in the middle of the one gutter between
     the halves, 720px from the sheet's left edge. Nothing here is typed in.

     Side by side, the halves are two separate lists again, so the second
     list's first row goes back to info-list's own :first-child treatment. The
     heading keeps its 16px margin. The action keeps the margin
     it carries on mobile, the same 32px the base split now puts on every
     action.

     STILL NO ROW GAP, same reason as the base split: a gap is charged above
     the empty slack row too, so the button sat 96px above the band foot at
     1024 on Plan Your Visit's Before you come, against the 64px the padding
     sets. Measured 2026-09-11. */
  .cc-feature-split--halves {
    /* One more row than the standard three: heading, rows, action, then the
       slack row that absorbs a taller second column. */
    grid-template-rows: auto auto auto 1fr;
  }
  .cc-feature-split--halves > .cc-feature-split__title {
    grid-column: 1 / -1;
    grid-row: 1;
  }
  .cc-feature-split--halves .cc-feature-split__body {
    grid-column: 1 / span 6;
    grid-row: 2;
  }
  .cc-feature-split--halves .cc-feature-split__actions {
    grid-column: 1 / span 6;
    grid-row: 3;
  }
  .cc-feature-split--halves .cc-feature-split__media {
    grid-column: 7 / span 6;
    grid-row: 2 / span 3;
  }
  .cc-feature-split--halves.cc-feature-split--divided::before {
    grid-column: 7;
    grid-row: 2 / -1;
  }
  .cc-feature-split--halves .cc-feature-split__media .cc-info-list__item:first-child {
    border-top: 0;
    padding-top: 0;
  }
  .cc-feature-split--halves .cc-feature-split__body .cc-info-list__item:last-child {
    padding-bottom: 0;
  }

  .cc-feature-split--halves:has(> .cc-feature-split__media > :is(.cc-feature-split__text, .cc-statement)) {
    row-gap: 0;
  }

  /* Modifier: slot-float — the slot floats: centred left and right inside
     columns 6-12 and centred on the whole copy stack, heading top to action
     bottom. It is not bound to the grid. Founder ruling 2026-09-29. ITS WIDTH
     IS A DESIGN VALUE SET BY EYE, not a column span. Service-art refinement
     2026-10-14: the percentage and cap below balance 16:9 artwork against
     the copy stack, filling the available column below the cap.
     Keep the same desktop breakpoint and centred placement. The
     caption keeps its type size and aligns with the graphic's left edge.

     Four rows, as halves: heading, body, action, then the slack row. The slot
     spans all four, so where it is the shorter side the slack row is 0 and
     the centring is on the copy stack alone; where it is the taller side the
     slack row absorbs the surplus and the copy stays at the top. The phone
     hairline and paddings are released. */
  .cc-feature-split--slot-float {
    grid-template-rows: auto auto auto 1fr;
  }
  .cc-feature-split--slot-float > .cc-feature-split__title {
    grid-column: 1 / span 5;
    grid-row: 1;
  }
  .cc-feature-split--slot-float .cc-feature-split__body {
    grid-row: 2;
    padding-top: 0;
  }
  .cc-feature-split--slot-float .cc-feature-split__actions {
    grid-row: 3;
  }
  .cc-feature-split--slot-float .cc-feature-split__media {
    grid-column: 6 / span 7;
    grid-row: 1 / -1;
    align-self: center;
    justify-self: center;
    /* 16:9 service-art refinement, 2026-10-14: fill the column below
       the cap for artwork readability. The 672px visual cap balances the graphic and
       caption against the service stack; it is not a structural grid span. */
    width: 100%;
    max-width: 672px;
    /* Equal top/bottom clearance: founder refinement, 2026-10-14. */
    translate: none;
    padding-bottom: 0;
    border-bottom: 0;
  }

  /* Modifier: actions-stacked — VISIT-07 closes with two actions rather than
     one. IT CARRIES NO CSS. The actions slot is already a flex column with a
     gap, so two buttons stack there without help at every breakpoint.

     It used to release the width, giving both buttons the full 5-column text
     column. FOUNDER RULING 2026-08-22: THERE IS ONE DESKTOP BUTTON WIDTH AND
     THIS WAS AN OUTLIER. Every button above the breakpoint is fit-content with
     the 3-column floor, left at its column's leading edge, and that rule lives
     in the button's own desktop block. Do not restore the override here and do
     not add a per-band width anywhere else.

     The class is kept as a marker only: the Page Assembly Map reads it to know
     this action slot takes an array of buttons rather than one. */

  /* Modifier: narrow-slot — A HELD SLOT, NOT A COLUMN SPAN. This is the one
     division in the component that does not cut the 12-column grid, and the
     departure is deliberate.

     GROUPS-07 closes Connect Groups with a short reassurance and one button.
     FOUNDER DIRECTION 2026-08-22: THE HORIZONTAL ORDER IS margin, copy, ONE
     gutter, button hard against the right margin, margin — and the button is
     the standard desktop button at every desktop width. It does not shrink.
     THE COPY COLUMN COLLAPSES INSTEAD.

     That is why a span cannot express it. A 3-column span looks right at
     --cc-canvas-max, where 3 columns is exactly 300px, and then fails
     everywhere below: the gutter is a fixed 48px while the columns are fluid,
     so at a 901px layout width three columns collapse to 165px and the label
     wraps to three lines. Measured, not predicted. So the slot is the held
     --cc-btn-w-desktop and the copy takes 1fr, which is the same arithmetic at
     the canvas maximum and the correct behaviour below it.

     At --cc-canvas-max: copy 996px, gutter 48px, slot 300px = 1344, the full
     content width. At a 901px layout: copy 457px, gutter 48px, slot 300px.
     Only the copy moved.

     THE SLOT IS THE BUTTON'S OWN WIDTH, NOT A BOX AROUND IT. The track and the
     button's desktop min-width read the same token, so the button fills the
     slot and its right edge sits on the page margin WITHOUT an alignment rule.
     Do not add justify-self here.

     THE CONTROL GOES IN THE SLOT, NOT IN __actions. The narrow side is a
     content slot that happens to hold a button here; a later section can put a
     short list or a small frame in it. __actions keeps its place under the copy
     and takes the copy's own track when a section needs both.

     The template override is scoped to this modifier, so the 12 columns and
     every other division are untouched. column-gap is inherited from the base
     rule and is still --cc-grid-gutter, so the one gutter between the two is
     the real one.

     The earlier cuts were 7/5 and then 9/3. Both are superseded. The
     action-aside modifier before them put dead columns between the two sides
     and is deleted.

     media-end only, as halves is. media-start is not built because nothing
     places it; the mirrored template would be --cc-btn-w-desktop 1fr. */
  .cc-feature-split--narrow-slot {
    grid-template-columns: 1fr var(--cc-btn-w-desktop);
  }
  .cc-feature-split--narrow-slot .cc-feature-split__body,
  .cc-feature-split--narrow-slot .cc-feature-split__actions {
    grid-column: 1;
  }
  .cc-feature-split--narrow-slot .cc-feature-split__media {
    grid-column: 2;
  }

  /* Modifier: slot-centred — the slot sits on the copy's own row and centres
     inside it.

     grid-row 1, not 1 / -1. Row 1 is the copy's own row, so centring inside it
     puts the slot exactly on the copy's midline, which is where the comp draws
     GROUPS-07's button. Spanning every row instead centres it against the
     grid's full height, and the two trailing row gaps push it 32px below the
     copy's midline. Measured at a 1403px layout width.

     Separate from narrow-slot on purpose. Centring is right for a short item
     beside taller copy and wrong for a slot holding a list, so the division
     does not decide it. */
  .cc-feature-split--slot-centred .cc-feature-split__media {
    grid-row: 1;
    align-self: center;
  }

  /* Modifier: media-panel -- the media slot is a full-height colour ground
     five columns wide, holding a positioned emblem (emblem-panel) rather than
     a photograph. GIVE-02's church crest on ink.

     FIVE AND SEVEN, WHICH IS THE DEFAULT DIVISION MIRRORED: the wide side is
     the copy's here, not the slot's. media-start only; the panel sits on the
     left.

     It was 4 and 8 first, snapped from the comp's panel edge alone. The copy's
     left edge is the better witness and it disagreed. In the accepted desktop
     comp, across its 1440 width, the panel ends at 530 and the copy starts at
     617. Span 4 starts the copy at 512, 105 out. Span 5 starts it at 628, 11
     out. The two shares agree: the comp reads 42:58 panel to copy, span 5
     gives 43:57, span 4 gave 35:65. Founder call 2026-08-31.

     Those are raster positions, so they are evidence of arrangement and
     proportion only. The spans are whole columns of the current grid; the
     measured pixels never set a width here.

     THE COST, TAKEN WITH THE CALL. The copy column loses 116px at the canvas
     maximum and the __foot gives all of it up from the __ready note, because
     the button does not shrink -- see --cc-btn-w-desktop. The pair still sets
     on two lines at 1440. At 900 the note wraps to seven lines where 4 and 8
     wrapped to four.

     THE PANEL BLEEDS TOP AND BOTTOM, THE COPY DOES NOT. Use with
     media-bleed-desktop: it zeroes the band's block padding so the ground runs
     to the band's top and bottom edges and reopens the copy's top padding on
     __body. The rule below restates that inset symmetrically at 48px, one step
     under the 64px media-bleed-desktop opens with, so the ink bleeds full
     height while the copy keeps an even inset top and bottom.
     align-self stretch fills the ground to the copy's height; the base 1fr
     slack row still absorbs the reverse case, a panel taller than the copy. */
  /* ONE ROW, NOT THREE. media-panel carries its action inside __body's __foot,
     so the base template's second row (__actions) and third row (slack) are
     both empty here - but the two 32px row-gaps between them are not, and they
     showed as 64px of dead band under the action. Collapsing the template to a
     single auto row removes both gaps.

     The slack row is not needed with it. It exists to stop growth splitting
     across a two-row copy stack; one row cannot split. A panel taller than the
     copy still grows this row and align-items: start still holds the copy at
     the top, which is what the slack row was protecting. */
  .cc-feature-split--media-panel.cc-feature-split--media-start {
    grid-template-rows: auto;
  }
  .cc-feature-split--media-panel.cc-feature-split--media-start .cc-feature-split__media {
    grid-column: 1 / span 5;
    grid-row: 1;
    align-self: stretch;
  }
  .cc-feature-split--media-panel.cc-feature-split--media-start .cc-feature-split__body,
  .cc-feature-split--media-panel.cc-feature-split--media-start .cc-feature-split__actions {
    grid-column: 6 / span 7;
  }
  .cc-feature-split--media-panel.cc-feature-split--media-bleed-desktop .cc-feature-split__body {
    padding-block: var(--cc-space-7);
  }

  /* The action moves up beside the lead-in. The gutter is the gap so the pair
     reads on the same grid rhythm as the columns around it; cc-btn--block is
     already fit-content here, so the button sizes to its label.

     THE ROW WRAPS, AND IT HAS TO. --cc-btn-w-desktop does not shrink, and the
     founder ruling behind it says whatever shares the row gives the space up
     instead. Here that row-mate is a sentence, so at the narrow end of desktop
     it was the one giving: 449px of copy column less the button and the gutter
     left the note 101px, which set it in five lines beside the button. The
     pair takes a --cc-btn-w-desktop basis and grows, so above about 1150px it
     fills the row and the button sits flush at the copy's trailing edge, which
     is where the accepted desktop comp draws it. Below that the button has no
     room left on the row and drops under the pair -- the arrangement the same
     component already uses below the breakpoint. No new breakpoint and no new
     width: the button's own token is the threshold. */
  .cc-feature-split--media-panel .cc-feature-split__foot {
    flex-direction: row;
    flex-wrap: wrap;
    align-items: center;
    justify-content: flex-start;
    /* TWO GAPS, NOT ONE. The gutter is the horizontal rhythm and it has no
       business setting a vertical one. The shorthand gave the wrapped row a
       48px row-gap where the same component stacks at --cc-space-5 below the
       breakpoint, so the button sat twice as far under its note on a narrow
       desktop as it does on a phone. The row-gap only ever shows once the row
       has wrapped, and when it does the arrangement is the mobile one, so it
       takes the mobile value. Founder call 2026-08-31. */
    column-gap: var(--cc-grid-gutter);
    row-gap: var(--cc-space-5);
  }
  .cc-feature-split--media-panel .cc-feature-split__ready {
    flex: 1 1 var(--cc-btn-w-desktop);
  }
}

/* ==========================================================================
   COMPONENT: photo-band  (id: photo-band)
   A band of short copy over one wide photograph that runs edge to edge and
   ends at the band's foot. VISIT-03, Worship, teaching, prayer, and
   community, is the first placement.
   Parts:     __copy (the title and its text), __media (the photograph)
   Composes:  section-title, section-copy, media-frame

   IT IS NOT A feature-split MODIFIER. Founder ruling 2026-09-26 (Plan Your
   Visit mockup, change 3). feature-split puts the copy and the photograph
   side by side; here the photograph is a full-width row of its own.

   THE COPY ROW IS TWO HALVES. Founder direction 2026-09-26, from a GPT Image
   reference: title 5 columns, a hairline in the next gutter, text 6 columns
   straight after it, the text centred on the title's height. Founder
   direction the same day: the halves must read as connected, tops and feet
   as level as the copy allows. The hairline is
   drawn from the grid, like feature-split's divided, in the same
   --cc-border token. No eyebrow: the next section opens with one, and the
   line is this band's accent.

   PHONE: the photograph comes first, flush with the band's top and sides,
   then the copy 16px under it and 48px above the band's foot. Tighter than
   the 32px photo-to-copy step other phone sections use, on purpose: the
   copy belongs to the edge-to-edge photograph, the desktop balance
   reversed. Founder direction 2026-09-27. So a photograph never follows the
   photograph that ends the band above it on a phone. 2 / 1 landscape keeps
   more depth than the desktop panorama. Founder direction 2026-10-15.

   DESKTOP: copy first, 64px under the band's top and 24px above the
   photograph, then the photograph to the band's foot. Square corners, no
   shadow, at every width.

   Placement value: --cc-photo-band-ratio, the desktop proportion. A
   photograph decision, set on the root per placement from the photograph's
   own crop, not a grid value. The 2 / 1 default only decides what an untuned
   placement looks like. Below 900px the phone ratio holds whatever it is.
   ========================================================================== */
.cc-photo-band {
  --cc-photo-band-ratio: 2 / 1;
  display: flex;
  flex-direction: column;
}
.cc-photo-band__media {
  order: -1;
  --cc-media-frame-ratio: 2 / 1;
  --cc-media-frame-radius: 0;
  --cc-media-frame-shadow: none;
}
.cc-photo-band__copy {
  display: grid;
  gap: var(--cc-space-4);
  padding: var(--cc-space-4) var(--cc-page-inset) var(--cc-space-7);
}

@media (min-width: 900px) {
  .cc-photo-band__media {
    order: 0;
    --cc-media-frame-ratio: var(--cc-photo-band-ratio);
  }
  .cc-photo-band__copy {
    grid-template-columns: repeat(var(--cc-grid-columns), 1fr);
    column-gap: var(--cc-grid-gutter);
    align-items: center;
    padding-block: var(--cc-space-8) var(--cc-space-5);
  }
  .cc-photo-band__copy > .cc-section-title {
    grid-column: 1 / span 5;
    grid-row: 1;
  }
  /* The text sits in the column straight after the title's, so the two read
     as one unit, and ends at column 11: column 12 is left open. Six columns
     keep the text about as tall as a two- or three-line title, so their tops
     and feet sit close to level. */
  .cc-photo-band__copy > .cc-section-copy {
    grid-column: 6 / span 6;
    grid-row: 1;
  }
  /* The hairline: column 6's leading edge, moved back half a gutter to the
     gutter's centre, stretched to the row's height. No position is typed. */
  .cc-photo-band__copy::before {
    content: "";
    grid-column: 6;
    grid-row: 1;
    justify-self: start;
    align-self: stretch;
    width: 1px;
    margin-inline-start: calc(var(--cc-grid-gutter) / -2);
    background: var(--cc-border);
  }
}

/* ==========================================================================
   COMPONENT: leader-profile  (id: leader-profile)
   A pastor or leader profile: one photograph at the start of a long
   introduction, the introduction clamped behind a More / Less control, and
   the rest of the profile running on below the photograph when it is opened:
   a spaced-capitals heading, two balanced columns, a pull quote, a plain
   paragraph, a full-bleed panorama, a second heading and paragraph, a second
   pull quote carrying the pathway row, and two balanced columns to the end.
   ABOUT-03, Meet Pastor Cal and Bethanie, is the first placement.

   THE ENGINE IS flow-split's FLOAT, NOT A GRID. Slice 1 was a two-column
   grid, and a grid cell cannot let copy run out under the photograph once it
   clears the bottom of it. Founder direction 2026-09-03: the copy is ONE
   STREAM, beside the photograph and then under it, and the More clamp cuts
   that stream at a height, never at a word. Only a float gives that. Read
   flow-split's header for the engine; the rules below are the differences.

   THE PHOTOGRAPH IS OUTSIDE THE DISCLOSURE PANEL. The panel is clamped to a
   height, and anything inside it is cut at that height. The photograph is
   therefore the first child of the component, floated, and the eyebrow, the
   title and the disclosure are its siblings. The panel clips on the block
   axis with overflow-y: clip, which opens NO formatting context, so the copy
   inside the panel still shortens beside the float and then runs under it.
   That rule lives in disclosure, not here; do not "fix" it back to hidden.

   THE STREAM IS FLAT, AND NOTHING IN IT MAY OPEN A FORMATTING CONTEXT UNTIL
   IT HAS CLEARED THE PHOTOGRAPH. cc-leader-profile__text is a plain block:
   never flex, grid, flow-root, or overflow anything. The intro paragraphs are
   plain p, so their lines wrap the float. Every other part of the stream, the
   sub-headings, the column blocks, the pull quotes and
   the panorama, carries clear: both, so it starts under the photograph at
   full width. The multi-column block MUST clear: a multicol container opens
   its own formatting context, and one that starts beside the float would be
   narrowed to the copy column for its whole height.

   ONE FIXED BOUNDARY: THE FIRST SUB-HEADING. Founder decision A, 2026-09-03.
   The two columns start at "Their Story", the heading spans the full width,
   and the intro tail above it stays one column. A stream cannot enter two
   columns mid-paragraph, so this is the only place the layout changes shape.
   When the intro is shorter than the photograph the heading clears to the
   photograph's foot and the air above it is the float's own bottom margin
   plus whatever the intro did not fill. That gap is a property of decision A,
   not a defect.

   THE PHOTOGRAPH SETS THE CLOSED HEIGHT. Above the breakpoint the photograph
   takes its declared 812 / 557 proportion across its seven columns plus the
   start inset, and the closed panel is cut so that the copy stack fills
   exactly that height: the section step at the head, the eyebrow, the title,
   the panel, the More control, and the section step at the foot. So the
   control ends one section step above the band's foot at every desktop
   width, and never under the photograph. There is no floor: where the
   photograph is short and the title is long, from about 990px down to the
   breakpoint, the panel shows less than two lines and near 900px none,
   founder direction 2026-09-11 (1024, the iPad, is the width that matters;
   900 is not). Founder direction 2026-09-10, the treatment media-end
   was built with first. Founder ruling 2026-08-16 holds;
   the photograph is subservient to the layout and crops into its box through
   media-frame's object-fit. Open, the copy runs under the photograph and the
   band is as tall as the copy.

   THE TITLE WRAPS, SO THE HEAD IS MEASURED, NOT SUMMED. "Meet Pastors Cal
   and Bethanie" is one line at the canvas maximum, two at 1280 and three
   near 900. A CSS sum cannot count lines, so the panel's distance from the
   band's top edge is read by js/disclosure.js and handed back as
   --cc-disclosure-offset; see the desktop block. Everything else in the sum
   is CSS: the photograph's height from its own width, the control from
   disclosure, the foot step from the spacing scale.

   THE PHOTOGRAPH REACHES THE BAND'S FOOT ONLY WHILE CLOSED. Open, the copy
   runs under the photograph and needs air beneath it, which is the float's
   bottom margin. Closed, that margin would hold the photograph 32px above the
   band's foot when it is the taller, and the accepted comp draws it flush.
   The :has() rule below drops the margin in exactly that state: the control
   is rendered and not open. Without JavaScript the panel is open, the margin
   stands, and nothing is hidden. A browser without :has() shows the 32px and
   nothing else changes.

   VARIANT media-end, ABOUT-06 and VISIT-04. The photograph floats at the END, framed
   inside the margins at 16 / 10 with the band's block padding kept; the copy
   takes the five columns at the start. Same engine and spans, mirrored. Its
   closed height FOLLOWS THE PHOTOGRAPH: the panel and the More control end
   at the photograph's foot, founder decisions 2026-09-10; see the variant
   rules at the end of the desktop block.

   Composes: section-eyebrow (rule-only), media-frame (flush, 812 / 557 on
   the default; framed, 16 / 10 on media-end; flush pano, full bleed),
   disclosure and through it the chevron icon, sub-heading, pull-quote (one
   with the pathway row). js/disclosure.js runs the control; this file only
   hands it a collapsed height.
   ========================================================================== */
.cc-leader-profile {
  /* The band's own inset is the site page inset. Private because the
     photographs negate it to run out to the band edge. */
  --_profile-pad-inline: var(--cc-page-inset);

  /* --- Collapsed copy height, mobile (adjustable) -----------------------
     Handed to the disclosure. A HEIGHT, NEVER A WORD COUNT: the cut lands
     wherever the stream is at that height, which is what founder direction
     2026-09-03 asks for. This is the tuning point below the breakpoint; no
     selector needs touching to move the cut. Above the breakpoint the closed
     height is not a value at all: it FOLLOWS THE PHOTOGRAPH, computed in the
     desktop block, founder direction 2026-09-10 for both variants. */
  --cc-leader-profile-collapsed-mobile: 20rem;

  display: flex;
  flex-direction: column;
  gap: var(--cc-space-4);
  /* The photograph meets the band's top edge on mobile, so the block padding
     is end-only. */
  padding-block: 0 var(--cc-space-7);
  padding-inline: var(--_profile-pad-inline);
}
/* The flex gap owns the stack rhythm below the breakpoint; every direct child
   starts from zero, including section-eyebrow's own standalone margin. */
.cc-leader-profile > * {
  margin: 0;
}

/* Mobile: the photograph runs edge to edge above the copy. The ratio matches
   the source, 1184 x 812, so the sides are not cropped, founder direction
   2026-09-03. A square or 2 / 1 box cut through the two faces. A photograph
   decision, not a grid value. One further step of air under it, on top of the
   stack gap, so the photograph reads as the band's head rather than another
   stack item. */
.cc-leader-profile__photo {
  margin-inline: calc(var(--_profile-pad-inline) * -1);
  margin-block-end: var(--cc-space-4);
}
.cc-leader-profile__photo .cc-media-frame {
  --cc-media-frame-ratio: 1184 / 812;
}
/* media-end: the photograph is framed above the breakpoint (see the variant
   at the end of the desktop block) but runs edge to edge here like the
   default's, so the frame is flattened below the breakpoint and returns
   above it. The page markup carries a plain cc-media-frame, as it does under
   feature-split's media-bleed-mobile. */
.cc-leader-profile--media-end .cc-leader-profile__photo .cc-media-frame {
  --cc-media-frame-radius: 0;
  --cc-media-frame-shadow: none;
}

/* Modifier: framed-mobile — below 900px the photograph is framed inside the
   margins, with media-frame's radius and shadow and the band's 48px section
   step above it, instead of running edge to edge from the band's top. For a
   placement that follows an edge-to-edge photograph, so two bleeds do not
   stack: VISIT-04 after VISIT-03's photo-band, founder direction 2026-09-26
   (Plan Your Visit mockup, change 2). Nothing to release above the
   breakpoint: media-end's desktop rules set the same frame, their own
   padding and their own photo margins. Only media-end is built; the default
   variant bleeds on desktop and would keep the radius. */
.cc-leader-profile--framed-mobile {
  padding-block-start: var(--cc-space-7);
}
.cc-leader-profile--framed-mobile .cc-leader-profile__photo {
  margin-inline: 0;
}
.cc-leader-profile--framed-mobile .cc-leader-profile__photo .cc-media-frame {
  --cc-media-frame-radius: var(--cc-radius-md);
  --cc-media-frame-shadow: var(--cc-shadow-card);
}

/* Modifier: compact — a square photograph at every width, and on desktop
   five columns instead of seven, so the copy takes seven. For a short
   profile whose photograph is a supporting picture rather than the subject:
   VISIT-04, founder direction 2026-09-26 (change 2). The ratio is declared
   once on the root, where both the frame and the desktop closed-height sum
   read it; the five-column width is in the desktop block. Only media-end is
   built. */
.cc-leader-profile--media-end.cc-leader-profile--compact {
  --_profile-photo-ratio: 1 / 1;
}
.cc-leader-profile--compact .cc-leader-profile__photo .cc-media-frame {
  --cc-media-frame-ratio: var(--_profile-photo-ratio);
}

/* Shares the section heading step, exactly as feature-split's title does. */
.cc-leader-profile__title {
  font-family: var(--cc-font-display);
  font-size: var(--cc-fs-h2);
  font-weight: var(--cc-weight-semibold);
  line-height: var(--cc-lh-snug);
  color: var(--cc-text);
}

/* The disclosure takes this component's clamp. disclosure declares its
   collapsed heights as its public tuning surface, so this is a value handed
   to a composed component, not a restyle of it. The desktop value is set in
   the desktop block, where the photograph's geometry lives. */
.cc-leader-profile .cc-disclosure {
  --cc-disclosure-collapsed-mobile: var(--cc-leader-profile-collapsed-mobile);
}

/* --- The stream ----------------------------------------------------------
   A plain block inside the panel. See the header: never flex, grid,
   flow-root, or overflow. Rhythm is margins on the parts, because a gap
   would need a flex or grid context and that would end the wrap. */
.cc-leader-profile__text > * {
  margin: 0;
}
.cc-leader-profile__text > * + * {
  margin-block-start: var(--cc-space-4);
}
/* A sub-heading opens a new run of copy, so it takes the section step above
   it. That is the same step the panorama takes, so a sub-heading reads the
   same distance from a paragraph above it as it does from the panorama, where
   the panorama's own margin already sets the gap. The pull quotes are breaks
   in the copy rather than items of it, and take a smaller step on both sides.
   Founder direction 2026-09-04: match the air above Their Story to the air
   above Mission & Multiplication. */
.cc-leader-profile__text > .cc-sub-heading {
  margin-block-start: var(--cc-space-7);
}
.cc-leader-profile__text > .cc-pull-quote {
  margin-block: var(--cc-space-6);
}
.cc-leader-profile__text > .cc-leader-profile__pano {
  margin-block: var(--cc-space-7);
}

/* The paragraph treatment is deliberately identical to
   cc-feature-split__text, so copy reads the same wherever it sits. The pull
   quote's own paragraphs are exempt; it sets its own type and colour. */
.cc-leader-profile__text p {
  font-size: var(--cc-fs-body);
  line-height: var(--cc-lh-body);
  color: var(--cc-text-muted);
}
.cc-leader-profile__text .cc-pull-quote p {
  font-size: var(--cc-fs-name);
  line-height: var(--cc-lh-snug);
  color: inherit;
}

/* A run of paragraphs that becomes two balanced columns above the
   breakpoint. One column here, and the paragraph rhythm is the stream's.
   Zero the browser's default paragraph margins first: these paragraphs are
   grandchildren of __text, so the stream's own reset does not reach them.
   Without this the first paragraph keeps a 1em top margin that the left
   column honours but the fragmentation break drops from the right column,
   so the two columns start on different lines. */
.cc-leader-profile__columns > p {
  margin: 0;
}
.cc-leader-profile__columns > p + p {
  margin-block-start: var(--cc-space-4);
}

/* The panorama runs edge to edge at every width; it is the one part of the
   stream that leaves the page inset. Only the margins are set here: the
   proportion belongs to media-frame's pano variant. */
.cc-leader-profile__pano {
  margin-inline: calc(var(--_profile-pad-inline) * -1);
}

@media (min-width: 900px) {
  /* flow-root for the same reason flow-split gives: the component's job above
     the breakpoint is to CONTAIN the float and let its own copy wrap it. The
     photograph reaches the band's top edge, so there is no block padding at
     all; the copy's own head margin and the disclosure's end margin carry the
     section rhythm instead. A BFC root contains both, so neither escapes. */
  .cc-leader-profile {
    display: flow-root;
    padding-block: 0;
    /* An inline-size container, so the photograph's width can be written
       once in container units and read by both the float and the closed-
       height sum. cqi measures the container's CONTENT box, which is the
       float's 100%, so the band's inline padding does not enter the sum.
       The sum is resolved where it is used, on the disclosure panel, whose
       nearest container is this root; js/disclosure.js's probe reads the
       same tokens, so the script gets the same number. */
    container-type: inline-size;
    /* Positioned so that js/disclosure.js's offsetTop is measured from this
       root's top edge, which on desktop is the band's top edge: the block
       padding is zero and the photograph bleeds to it. */
    position: relative;
    /* The photograph's declared desktop proportion, read by the photo frame
       below and by both closed-height sums. One owner, so the two can
       never disagree. */
    --_profile-photo-ratio: 812 / 557;
    /* A SEVEN-COLUMN SPAN PLUS THE START MARGIN, written as the grid's own
       arithmetic because a float inherits no tracks; the same derivation
       flow-split records for its seven. Seven columns and the six gutters
       between them, plus the page inset the photograph bleeds into. At
       --cc-canvas-max: 7 x 68 + 6 x 48 + 48 = 812px, and the copy takes the
       remaining five columns beside it. Seven against five, founder direction
       2026-09-03: it was briefly six against six, and the wider photograph
       narrows the copy column so the introduction runs deeper.

       The column count is read, not typed, so a client with a different
       count gets a correct width here without this rule being touched. Only
       the span, the 7 and the 6, is written literally, because that is this
       component's design decision. A live fluid span, not a fixed minimum,
       so it is not derived from --cc-grid-column-ref. Declared here and read
       by the float's width and by the sum, so the two cannot disagree. */
    --_profile-photo-w: calc(
      7 * (100cqi - (var(--cc-grid-columns) - 1) * var(--cc-grid-gutter-desktop))
        / var(--cc-grid-columns)
      + 6 * var(--cc-grid-gutter-desktop)
      + var(--_profile-pad-inline)
    );
  }
  /* The flex gap goes with the flex context, so the stack rhythm returns as
     margins. The photograph is out of flow, so the first in-flow child is the
     element after it, and that one takes the section step down from the
     band's top edge instead of a stack step. */
  .cc-leader-profile > * {
    margin-block-start: var(--cc-space-4);
  }
  .cc-leader-profile > .cc-leader-profile__photo + * {
    margin-block-start: var(--cc-space-8);
  }
  /* THE CLOSED HEIGHT FOLLOWS THE PHOTOGRAPH. The panel is the photograph's
     height, less the panel's own distance from the band's top edge, less
     the control and its gap, less the section step at the foot. So the
     control's LABEL ends one section step above the photograph's foot,
     which is the band's foot while closed. The foot is the section step
     every band pads to above the breakpoint, --cc-space-8, matching the head
     step the eyebrow takes; the first build had it tighter at --cc-space-6.
     The step is measured to the word, not to the 44px touch box, which
     overhangs the word by --cc-disclosure-control-overhang on each side:
     the box's foot sits that much inside the step, so the eye reads 64,
     founder direction 2026-09-11.

     THE SUM IS SPLIT ACROSS TWO ELEMENTS ON PURPOSE. The root above owns
     the photograph's geometry. The two disclosure terms are declared on the
     disclosure element and cannot be read from above it:
     --cc-disclosure-control is disclosure's own public sum of the control
     and its gap, and --cc-disclosure-offset is written by js/disclosure.js
     as this element's offsetTop from its positioned ancestor, the root, in
     px, before every measurement. That term carries the eyebrow, the title
     at whatever line count the width gives it, and the two stack steps.
     Without the script the offset is absent, the fallback of 0px stands,
     and nothing is clamped anyway: the clamp only applies once the script
     has opted the instance in.

     ONE FORMULA, NO FLOOR. The sum is the clamp at every desktop width.
     Where the photograph is short and the title is long, from about 990px
     down to the breakpoint, the sum is less than two lines and near 900px
     it is below zero; max() holds it at zero, so the panel shows nothing
     and More sits under the title, still beside the photograph. The first
     build carried a floor and a second case that ran the panel to the
     photograph's foot with More under it at full width; the founder
     rejected that look at 1024 (2026-09-11) and does not weigh 900. */
  .cc-leader-profile > .cc-disclosure {
    /* The foot step, measured to the word; see above. Declared once and
       used twice: as the band's foot under the control, and inside the
       closed-height sum, so the band's foot and the photograph's foot
       coincide by construction while closed. */
    --_profile-foot: calc(var(--cc-space-8) - var(--cc-disclosure-control-overhang));
    margin-block-end: var(--_profile-foot);
    --cc-disclosure-collapsed-desktop: max(
      0px,
      calc(
        var(--_profile-photo-w) / (var(--_profile-photo-ratio))
        - var(--cc-disclosure-offset, 0px)
        - var(--cc-disclosure-control)
        - var(--_profile-foot)
      )
    );
  }

  .cc-leader-profile__photo {
    float: inline-start;
    /* The seven-column span declared on the root; see --_profile-photo-w. */
    width: var(--_profile-photo-w);
    /* Bleed on the start side; one gutter to the copy and nothing else. */
    margin-inline: calc(var(--_profile-pad-inline) * -1) var(--cc-grid-gutter-desktop);
    /* The float's bottom edge is where the copy stops wrapping, so the end
       margin is the gap between the photograph and the first full-width
       line under it. Dropped to zero while closed; see the :has() rule. */
    margin-block: 0 var(--cc-space-6);
  }
  /* The photograph's declared desktop proportion. 812 / 557 across its box: at
     the canvas maximum that is 812 x 557. The height is held at slice 1's 557
     while the box widens to the seven-column span, founder direction
     2026-09-03, so the band keeps its height and only the width grows. The
     source is 1184 x 812. A photograph decision, adjustable here, not a grid
     value. */
  .cc-leader-profile__photo .cc-media-frame {
    --cc-media-frame-ratio: var(--_profile-photo-ratio);
  }
  /* Closed and clamped: the photograph reaches the band's foot. See the
     header. The selector names the disclosure's own ready attribute and open
     class, which are its declared public state; nothing here restyles it. */
  .cc-leader-profile:has(> .cc-disclosure[data-cc-disclosure-ready]:not(.cc-disclosure--open))
    > .cc-leader-profile__photo {
    margin-block-end: 0;
  }

  /* Every part of the stream that is not a plain paragraph starts under the
     photograph at full width. Only the intro paragraphs wrap it. */
  .cc-leader-profile__text > .cc-sub-heading,
  .cc-leader-profile__text > .cc-leader-profile__columns,
  .cc-leader-profile__text > .cc-pull-quote,
  .cc-leader-profile__text > .cc-leader-profile__pano {
    clear: both;
  }

  /* Two columns, balanced to within a line, which is what column-fill's
     default does; a paragraph may split across them, founder decision
     2026-09-03. The gap is the grid gutter, so the two columns are six site
     columns each. widows and orphans keep a split from leaving one line of a
     paragraph alone at the foot or head of a column. */
  .cc-leader-profile__columns {
    column-count: 2;
    column-gap: var(--cc-grid-gutter-desktop);
    orphans: 2;
    widows: 2;
  }

  /* The pull quotes sit eight of twelve columns wide: two columns and two
     gutters in from each side, founder direction 2026-09-03. The inset is a
     placement decision of this component, so it is written here and the
     element itself stays full width. */
  .cc-leader-profile__text > .cc-pull-quote {
    /* More air around the callout on desktop: space-7 (48px) block, up from
       the base space-6 (32px) that mobile keeps. Founder direction 2026-09-04. */
    margin-block: var(--cc-space-7);
    margin-inline: calc(
      2 * (100% - (var(--cc-grid-columns) - 1) * var(--cc-grid-gutter-desktop))
        / var(--cc-grid-columns)
      + 2 * var(--cc-grid-gutter-desktop)
    );
  }

  /* --- Variant: media-end (ABOUT-06) --------------------------------------
     The photograph floats at the END, FRAMED INSIDE THE MARGINS the way
     feature-split's media-end frames ABOUT-06 on the built page today: the
     band keeps its block padding, the photograph's top is level with the
     title's, it takes media-frame's radius and shadow, and nothing bleeds.
     The copy takes the five columns at the start. Same float engine as the
     default; the framing and the closed height are the differences. Founder
     feedback 2026-09-10 dropped the end bleed and the flush frame this
     variant was first built with.

     THE CLOSED HEIGHT FOLLOWS THE PHOTOGRAPH. Founder decision 2026-09-10:
     the closed panel AND the More control end at the photograph's foot at
     every desktop width, never below it. A fixed rem cannot promise that:
     the photograph shortens as the page narrows while a rem stands still. So
     the clamp is the photograph's height, less the in-flow stack above the
     panel (the one-line title and the stack step), less the control and its
     gap. The control's touch box then ends exactly at the photograph's foot;
     its label ends above it, because the touch target is taller than the
     line box. Founder feedback 2026-09-10 added the control term: the first
     build let the control sit under the photograph.

     THE HEAD IS MEASURED, THE SAME WAY THE DEFAULT VARIANT MEASURES ITS OWN.
     The first build summed the head in CSS as one title line and a stack
     step, so the variant took no eyebrow and no wrapping title. Now
     js/disclosure.js hands the disclosure its offsetTop from this root as
     --cc-disclosure-offset, which carries the root's top padding, the eyebrow
     if there is one, the title at whatever line count the width gives it,
     and the stack steps. The sum lives on the disclosure element, where that
     term and disclosure's own --cc-disclosure-control can be read; see the
     rule below. Extended 2026-09-11 for VISIT-04, which carries the rule-only
     eyebrow. ABOUT-06 gets the same number it had.

     The photograph's width overrides the root's --_profile-photo-w without
     the inset term, in the same container units; see the root for why cqi. */
  .cc-leader-profile--media-end {
    /* The framed photograph's declared desktop proportion: media-frame's
       16 / 10 default, the ratio feature-split media-end frames ABOUT-06 at
       today. Founder direction 2026-09-10. A photograph decision, adjustable
       here, not a grid value. */
    --_profile-photo-ratio: 16 / 10;
    /* Band padding on both block edges, feature-split's desktop value. The
       title's stack step and the disclosure's end margin are dropped below:
       the padding carries the head and the foot. */
    padding-block: var(--cc-space-8);
    /* Overrides the root's seven with no inset term: the photograph stays
       inside the margins. At --cc-canvas-max: 7 x 68 + 6 x 48 = 764px,
       feature-split's seven. Read by both the float's width and the sum, so
       the two cannot disagree. */
    --_profile-photo-w: calc(
      7 * (100cqi - (var(--cc-grid-columns) - 1) * var(--cc-grid-gutter-desktop))
        / var(--cc-grid-columns)
      + 6 * var(--cc-grid-gutter-desktop)
    );
  }
  /* The title sits level with the photograph's top: the band padding already
     holds it off the band's edge. */
  .cc-leader-profile--media-end > .cc-leader-profile__photo + * {
    margin-block-start: 0;
  }
  /* The WORD ends at the photograph's foot; the touch box ends one overhang
     below it, inside the band's padding, founder direction 2026-09-11 (it
     was the box at the foot, and the word read 8.5px short). The end margin
     is disclosure's own negative overhang, restated because the default
     variant's rule above sets a different one on the same element: it puts
     the disclosure's margin edge back at the photograph's foot, so the
     band's content box is the photograph and the padding is the foot. */
  .cc-leader-profile--media-end > .cc-disclosure {
    margin-block-end: calc(-1 * var(--cc-disclosure-control-overhang));
    /* The photograph's height less the measured head. offsetTop is read from
       the root's padding edge, so the root's top padding is inside it and is
       added back: the photograph's top sits that far down. Held at zero where
       the head and the control leave no room, as the default variant is.
       Without the script the offset is absent and nothing is clamped anyway. */
    --cc-disclosure-collapsed-desktop: max(
      0px,
      calc(
        var(--_profile-photo-w) / (var(--_profile-photo-ratio))
        + var(--cc-space-8)
        - var(--cc-disclosure-offset, 0px)
        - var(--cc-disclosure-control)
        + var(--cc-disclosure-control-overhang)
      )
    );
  }
  .cc-leader-profile--media-end .cc-leader-profile__photo {
    float: inline-end;
    width: var(--_profile-photo-w);
    /* One gutter to the copy, and nothing on the end side: the photograph
       ends at the band's inset. */
    margin-inline: var(--cc-grid-gutter-desktop) 0;
  }
  /* The frame returns above the breakpoint: media-frame's own radius and
     shadow, the values the mobile rule outside this block zeroes. */
  .cc-leader-profile--media-end .cc-leader-profile__photo .cc-media-frame {
    --cc-media-frame-radius: var(--cc-radius-md);
    --cc-media-frame-shadow: var(--cc-shadow-card);
  }
  /* NO MORE, NO GAP UNDER THE PHOTOGRAPH. When the whole copy fits beside
     the photograph, js/disclosure.js renders no control and leaves the
     disclosure without its ready attribute. Nothing then wraps under the
     photograph, so the float's end margin only pushed the band 32px past
     the photograph's foot. Every media-end placement, founder direction
     2026-09-26 (change 2). Without JavaScript the disclosure is also not
     ready and the whole copy shows; where that copy is longer than the
     photograph, its first line under the photograph loses the 32px. That
     is accepted: a no-script reader still gets all the copy. */
  .cc-leader-profile--media-end:has(> .cc-disclosure:not([data-cc-disclosure-ready]))
    > .cc-leader-profile__photo {
    margin-block-end: 0;
  }

  /* compact: five columns and the four gutters between them, inside the
     margins, the same arithmetic as media-end's seven. At --cc-canvas-max:
     5 x 68 + 4 x 48 = 532px, feature-split's five. */
  .cc-leader-profile--media-end.cc-leader-profile--compact {
    --_profile-photo-w: calc(
      5 * (100cqi - (var(--cc-grid-columns) - 1) * var(--cc-grid-gutter-desktop))
        / var(--cc-grid-columns)
      + 4 * var(--cc-grid-gutter-desktop)
    );
  }
}

/* ==========================================================================
   COMPONENT: flow-split  (id: flow-split)
   A band where one photograph, with its own section heading beneath it, sits
   on the trailing side and the copy WRAPS AROUND that block, then runs out to
   the band's far edge once it clears the bottom of it.

   THIS IS NOT A feature-split MODIFIER. feature-split is a grid: the copy sits
   in one set of column tracks and the photograph in another, and a grid cell
   cannot let text flow past it. Only a float can. The two use different layout
   engines, which is why this is a second component.

   THE ASIDE MUST BE THE FIRST CHILD, AND EVERY WRAPPING ELEMENT MUST BE ITS
   SIBLING. A float only affects the line boxes after it, and the accepted
   GROUPS desktop comp starts the wrap at the first heading. A wrapper around
   the copy would open a new block formatting context and the text would clear
   the float instead of flowing around it. That is why the eyebrow, both
   headings and every paragraph are flat children here.

   SOURCE ORDER IS THEREFORE NOT THE MOBILE ORDER. Below the breakpoint the
   component is a flex column and `order` puts the photograph back between the
   two runs of copy, which is what the accepted mobile comp draws. Anything
   belonging above the photograph carries __lead; everything else falls after
   it. This is the only way to get both orders without a wrapper.

   IT CARRIES TWO SECTIONS' HEADINGS ON PURPOSE. GROUPS-09's heading opens the
   copy; GROUPS-03's heading is the caption under the photograph. Both are
   section-title. __caption places the caption under the photograph and sets
   its type: --cc-fs-name (24px), weight 500 and centred at every width. The
   media-small modifier steps it to --cc-fs-lead (20px on phones) below the
   breakpoint and holds 24px on desktop. The two sections share one band
   because a float can only be wrapped by copy in its own container.

   Composes:  section-eyebrow, section-title, media-frame
   ========================================================================== */
.cc-flow-split {
  /* Same private property as feature-split, for the same reason: the
     photograph negates it to bleed below the breakpoint. */
  --_flow-pad-inline: var(--cc-page-inset);
  display: flex;
  flex-direction: column;
  gap: var(--cc-space-4);
  padding-block: var(--cc-space-7);
  padding-inline: var(--_flow-pad-inline);
}

/* Visual order below the breakpoint. Source order is the desktop float order;
   these three rules restore the mobile comp's arrangement with no wrapper. */
.cc-flow-split > *                     { order: 3; margin: 0; }
.cc-flow-split > .cc-flow-split__lead  { order: 1; }
.cc-flow-split > .cc-flow-split__aside { order: 2; }

.cc-flow-split > p {
  font-size: var(--cc-fs-body);
  line-height: var(--cc-lh-body);
  color: var(--cc-text-muted);
}

/* The photograph and its heading are one block at both breakpoints: on mobile
   because they travel together in the stack, on desktop because the float has
   to carry both or the copy would wrap the photograph alone and the heading
   would land in the flow. */
.cc-flow-split__aside {
  display: flex;
  flex-direction: column;
  gap: var(--cc-space-4);
  /* One further step of air above and below, on top of the stack gap, so the
     block reads as a break in the copy rather than another paragraph. */
  margin-block: var(--cc-space-4);
}

/* The photograph runs edge to edge below the breakpoint, as the accepted
   mobile comp draws it. Only the frame bleeds, so the heading under it keeps
   the page inset and no second inset value is needed. Same three frame
   properties media-bleed-mobile sets, for the same reason. */
.cc-flow-split__aside .cc-media-frame {
  margin-inline: calc(var(--_flow-pad-inline) * -1);
  --cc-media-frame-ratio: 2 / 1;
  --cc-media-frame-radius: 0;
  --cc-media-frame-shadow: none;
}

/* The caption is a section-title by markup, but it is a caption by role: it
   names the photograph it sits under, not the section, so it steps down to
   --cc-fs-name rather than holding the section heading's --cc-fs-h2. The 24px
   step already exists in the scale; no new size is added.

   WEIGHT 500 (--cc-weight-medium) IS DELIBERATE AND IS THE ONE HEADING THAT
   IS NOT 600. Employee direction: 700 on 2026-08-24, lowered to 500 on
   2026-08-26 so the caption reads lighter beneath the 600 section heading;
   confirmed 2026-10-31. Do not "correct" it to --cc-weight-semibold to match
   the site-wide heading weight.

   --cc-lh-snug is inherited from section-title and is left alone: 1.25 x 24
   is the 30px line box this caption was specified at.

   CENTRED AT EVERY WIDTH. Employee direction 2026-08-24. The caption motif is
   the same object on a phone as on a desktop, so the centring belongs here in
   the base rule and not in the 900px block. It was desktop-only from the
   component's first build until this direction; do not move it back under the
   breakpoint. */
.cc-flow-split__caption {
  font-size: var(--cc-fs-name);
  font-weight: var(--cc-weight-medium);
  text-align: center;
}

@media (min-width: 900px) {
  /* flow-root, not grid and not plain block: the component's only job above
     the breakpoint is to CONTAIN the float and let its own copy wrap around
     it. A plain block does not contain a float, and this one is taller than
     the copy beside it, so it would hang out of the band and land on the next
     section. flow-root is the declared way to open a block formatting context
     without the side effects of overflow or a clearfix pseudo-element. */
  .cc-flow-split {
    display: flow-root;
    /* 64px at the head. At the foot, 64 less the 24px that rides on whichever
       column ends lower; see the :last-child rule and the aside margin below. */
    padding-block: var(--cc-space-8) calc(var(--cc-space-8) - var(--cc-space-5));
  }

  /* The flex gap goes with the flex context, so the stack rhythm returns as
     margins. The aside is the first child and is out of flow, so the element
     directly after it is the first one in flow and takes no leading margin. */
  .cc-flow-split > * { margin-block-start: var(--cc-space-4); }
  .cc-flow-split > .cc-flow-split__aside + * { margin-block-start: 0; }

  /* THE 24px UNDER THE FLOAT IS ALSO THE 24px UNDER THE LAST PARAGRAPH.
     flow-root ends at whichever is lower, the float's margin edge or the last
     in-flow child's. The aside carries 24px so a line that wraps under the
     caption clears it. When nothing wraps, that 24px used to land on the band
     foot instead, and the caption sat 88px above it at 1280 against the 64
     every split holds. Founder direction 2026-09-11: 64 under every split at
     every desktop width. So the band's own foot padding is 40 and the last
     paragraph carries the other 24 as well. Copy lower: 24 + 40 = 64. Float
     lower: 24 + 40 = 64. A wrapped line still sits 24 under the caption.
     Measured after the change: 64 at 1024, where the copy is lower, and 64
     at 1280 and 1440, where the float is. */
  .cc-flow-split > :last-child { margin-block-end: var(--cc-space-5); }

  .cc-flow-split__aside {
    float: inline-end;
    /* A SEVEN-COLUMN SPAN — the same division feature-split takes, written as
       the grid's own arithmetic because a float inherits no tracks. The
       columns and the gutters between them fill the content box, so one column
       is (100% - (columns - 1) gutters) / columns, and the photograph takes
       seven of them plus the six gutters between. At --cc-canvas-max that is
       764px of 1344, the same figure the feature-split derivation records.

       THE COLUMN COUNT IS READ, NOT TYPED. --cc-grid-columns is the grid's own
       token and feature-split reads it too, so a client with a different count
       gets a correct width here without this rule being touched. Only the span
       itself — the 7 and the 6 — is written literally, because that is this
       component's design decision, the same way feature-split writes span 7.

       This is a live fluid span, not a fixed component minimum, so it is not
       derived from --cc-grid-column-ref and nothing here is stored or reused
       as a constant. */
    width: calc(
      7 * (100% - (var(--cc-grid-columns) - 1) * var(--cc-grid-gutter-desktop))
        / var(--cc-grid-columns)
      + 6 * var(--cc-grid-gutter-desktop)
    );
    /* One gutter between the photograph and the copy and nothing else, which
       is the same adjacency rule feature-split follows. */
    margin-inline: var(--cc-grid-gutter-desktop) 0;
    /* The float's bottom edge is where the copy stops wrapping, so this is the
       gap between the caption and the first full-width line, not spacing under
       a block. When no line wraps it is the foot's 24 instead; the :last-child
       rule above and the 40px foot padding are what make that 64. */
    margin-block: 0 var(--cc-space-5);
  }

  /* Framed again above the breakpoint: the bleed is a mobile treatment. */
  .cc-flow-split__aside .cc-media-frame {
    margin-inline: 0;
    --cc-media-frame-ratio: 16 / 10;
    --cc-media-frame-radius: var(--cc-radius-md);
    --cc-media-frame-shadow: var(--cc-shadow-card);
  }
}

/* Square media preserves the employee-selected square composition at every
   width while retaining the aside placement and caption spacing. */
.cc-flow-split--media-square .cc-flow-split__aside .cc-media-frame {
  --cc-media-frame-ratio: 1 / 1;
}

@media (min-width: 900px) {
  /* Fluid four-column photo leaves eight columns for text and one gutter
     between them. At the canvas maximum the photo spans 416px. */
  .cc-flow-split--media-small .cc-flow-split__aside {
    /* Employee-selected 350px desktop minimum; retain four-column growth
       when the available width produces a larger photo. */
    min-width: 350px;
    width: calc(
      4 * (100% - (var(--cc-grid-columns) - 1) * var(--cc-grid-gutter-desktop))
        / var(--cc-grid-columns)
      + 3 * var(--cc-grid-gutter-desktop)
    );
  }
}

/* Below the breakpoint the small-media caption uses --cc-fs-lead (20px on
   phones, about 21.6px at 899px), founder direction 2026-11-04: the caption is
   the band's moving text on phones too, and the 18px body size could not carry
   it. 20px is an existing step, holds one line at 320 (246px of ink in a 288px
   box) and stays below the 30px heading; 24px wraps at 320. */
.cc-flow-split--media-small .cc-flow-split__caption {
  font-size: var(--cc-fs-lead);
}

@media (min-width: 900px) {
  /* Desktop returns the small-media caption to the component's own caption
     step, --cc-fs-name (24px), founder direction 2026-10-31: the caption is
     the band's only moving text on desktop and 18px could not carry it. One
     line at every desktop width, 295px of ink under the 350px minimum photo. */
  .cc-flow-split--media-small .cc-flow-split__caption {
    font-size: var(--cc-fs-name);
  }
}

/* ==========================================================================
   COMPONENT: hug-split  (id: hug-split)
   A band where a run of copy and one control sit side by side, with the
   control GLUED TO THE END OF THE COPY rather than to a column edge or to the
   band's far margin.

   ONE RULE: THE GAP BETWEEN THE COPY AND THE CONTROL IS ALWAYS EXACTLY ONE
   GUTTER, AT EVERY WIDTH AND FOR ANY LENGTH OF COPY. Everything else follows
   from it.

     short copy   margin | copy | gutter | control | slack | margin
     long  copy   margin | copy | gutter | control | margin

   The copy pushes the control rightward as it grows. When the control reaches
   the page margin the copy has hit its ceiling and wraps. Any slack is always
   to the RIGHT of the control, never between the copy and it.

   THIS IS A THIRD COMPONENT FOR A THIRD LAYOUT ENGINE.
     - feature-split is a grid. A track cannot size itself to where the ink
       stops, so short copy leaves a hole between the copy and the slot. On
       GROUPS-07's own copy at --cc-canvas-max that hole measured 383px.
     - flow-split is a float pinned to the container edge. The control lands on
       the page margin whatever the copy does, so the same hole appears.
   Only a shrink-to-fit box can put the control at the copy's own end.

   WHY THE RESERVATION IS DECLARED. The box is width: fit-content, so it
   shrinks to the copy - and a shrink-to-fit box knows nothing about a control
   that is out of flow. It therefore reserves the control's room itself, in
   padding-inline-end, and the control is positioned into that padding. Without
   the reservation this box measured 925px against the 1261px it needs, at a
   1425px layout width, and the heading wrapped.

   THE CONTROL IS ABSOLUTELY POSITIONED AND VERTICALLY CENTRED ON THE COPY.
   Founder direction 2026-08-22. That is what keeps this component small: its
   height does not depend on where the aside sits in the markup, so there is no
   source-order rule for Website Build to honour and no alignment margin to
   keep in step. The earlier build floated the control and needed both.

   TWO CONSEQUENCES OF BEING OUT OF FLOW, BOTH DELIBERATE.
     1. THE COPY DOES NOT FLOW UNDERNEATH THE CONTROL. The control is not in
        the text's box at all - it is in the padding beside it - so the box
        ends one gutter short of it on every line. A control INSIDE the box
        could be flowed under, but only as a float, and a float can only park
        on the box's edge, which is flow-split and brings the hole back. The
        two behaviours cannot both be had.
     2. THE CONTROL DOES NOT GROW THE BOX. A control taller than the copy
        beside it would spill out of the band. A button never is.

   Below the breakpoint the component is a plain flex column and the control
   returns to the foot of the stack, where every other band puts its action.

   NO PIXEL VALUE APPEARS ANYWHERE IN THIS COMPONENT. It reads --cc-page-inset,
   --cc-grid-gutter and --cc-btn-w-desktop and declares nothing of its own, so
   it carries no client-specific value and no text measure.

   Composes:  section-eyebrow, section-title, button
   ========================================================================== */
.cc-hug-split {
  display: flex;
  flex-direction: column;
  gap: var(--cc-space-4);
  padding-block: var(--cc-space-7);
  padding-inline: var(--cc-page-inset);
}

/* Visual order below the breakpoint, so the markup may carry the aside
   wherever it reads best. Above the breakpoint the aside is out of flow and
   `order` no longer reaches it. */
.cc-hug-split > *                    { order: 2; margin: 0; }
.cc-hug-split > .cc-hug-split__aside { order: 3; }

.cc-hug-split > p {
  font-size: var(--cc-fs-body);
  line-height: var(--cc-lh-body);
  color: var(--cc-text-muted);
}

/* One further step of air above the control, on top of the stack gap, so the
   pair reads the way feature-split's copy and actions do. Mobile only - the
   desktop rule below centres instead. */
.cc-hug-split__aside {
  margin-block-start: var(--cc-space-4);
}

@media (min-width: 900px) {
  /* THE THREE PROPERTIES BELOW ARE ONE MECHANISM AND ARE NOT SEPARABLE.
     fit-content shrinks the box to the copy; padding-inline-end reserves the
     control's room beyond it, because fit-content will not; max-width stops
     the whole thing, reservation included, at the band. relative is what the
     control is positioned against. */
  .cc-hug-split {
    position: relative;
    width: fit-content;
    max-width: 100%;
    padding-inline-end: calc(
      var(--cc-page-inset) + var(--cc-grid-gutter) + var(--cc-btn-w-desktop)
    );
  }

  .cc-hug-split__aside {
    position: absolute;
    /* Flush to the reservation's outer edge, so the control's own right edge
       lands on the page margin once the box reaches the band. The gutter is
       then whatever the reservation has left over, which is exactly one. */
    inset-inline-end: var(--cc-page-inset);
    /* Both insets plus a definite height plus auto margins is the declared way
       to centre a positioned box. padding-block is symmetric, so centring on
       the border box centres on the copy. */
    inset-block: 0;
    height: fit-content;
    margin-block: auto;
    /* A PERCENTAGE MIN-WIDTH CANNOT SIZE AN OUT-OF-FLOW BOX. The control's own
       desktop rule is min(--cc-btn-w-desktop, 100%), and here that percentage
       is circular, so Chrome drops the floor and the control collapses to its
       label - 288px against the intended 300, measured. The aside therefore
       states the width, reading THE SAME TOKEN the control reads. One owner in
       tokens.css, two readers. */
    width: var(--cc-btn-w-desktop);
  }
}

/* ==========================================================================
   COMPONENT: message-form  (id: message-form)
   A short form-to-mail that unfolds in place under a section row and posts
   to whatever form-to-mail service the site is given. Built 2026-09-17 for
   GROUPS-07 and GIVE-04, founder decision of the same day: one standard
   form for both, differing by subject and hint only.

   THE FOLD. The panel is the next sibling after .cc-hug-split inside the
   same band, NEVER inside it: the aside control is centred on the copy's
   height, and a panel inside the box would move it. It ships open in the
   markup and js/message-form.js closes it at init, so without the script
   the form is simply visible, the browser checks `required`, and the post
   goes natively to the form's action. Nothing the visitor already read
   moves; the panel takes the room below. Motion is the disclosure's:
   max-height under --cc-transition, and the reduced-motion block at the
   foot of the disclosure component turns it off for this root too.

   NO CARD AND NO TOP MARGIN. The panel sits on the band, and hug-split's
   own --cc-space-7 bottom padding is the gap above it. Closed, it adds
   nothing: [hidden] takes it out of the flow entirely.

   THE WIDTH RULE. Above the breakpoint the panel repeats hug-split's
   padding-inline-end reservation, so the form never runs under the control
   column beside the copy. The form is then the smaller of that copy room
   and six reference columns. The six-column figure is a span held as an
   absolute, the way --cc-btn-w-desktop is: 6 x 68 + 5 x 48 = 648px at
   --cc-canvas-max, computed once from the reference tokens and never from
   a live column. Single column at every width, labels above fields.

   TRANSPORT-BLIND. The component knows no service, no host and no church.
   The endpoint, the encoding, the fallback address and the hidden fields
   are attributes and inputs the placement supplies, and the map records
   them per placement. With an empty endpoint the script posts nothing and
   shows the failed line honestly, with the fallback address as a mailto
   link. Nothing here names a colour, a church, or an address.

   STATE IS A CLASS ON THE ROOT and nothing else: is-open, is-sending,
   is-sent, is-failed. The script toggles classes, attributes and text;
   every appearance below keys on those. A field error keys on the field's
   own aria-invalid. The trigger's held look keys on aria-expanded and lives
   with the button variants, because it is a button state.

   Composes:  button (Send)
   Composed beside: hug-split, whose aside control becomes the trigger -
   <button type="button" data-cc-mail-trigger="{prefix}-panel">.
   ========================================================================== */
.cc-message-form {
  padding-inline: var(--cc-page-inset);
}

/* Keep the open-state spacing inside the fold. Padding on the animated
   root would impose a minimum height and snap away when it becomes hidden. */
.cc-message-form__form,
.cc-message-form__sent {
  padding-block-end: var(--cc-space-7);
}

/* Opted in by js/message-form.js. Clip on the block axis only, as the
   disclosure panel does, so the transition has something to cut against
   and the inline axis stays free for a field's focus ring. */
.cc-message-form[data-cc-mail-ready] {
  box-sizing: border-box;
  overflow-y: clip;
  transition: max-height var(--cc-transition);
}

.cc-message-form__form {
  /* Six reference columns at --cc-canvas-max, held as an absolute: 648px.
     A span, never a typed pixel value; see --cc-btn-w-desktop in tokens.css
     for the ruling. Never recalculated from a live column. */
  max-width: calc(
    6 * var(--cc-grid-column-ref) + 5 * var(--cc-grid-gutter-desktop)
  );
}

.cc-message-form__field + .cc-message-form__field {
  margin-block-start: var(--cc-space-4);
}

.cc-message-form__label {
  display: block;
  margin-block-end: var(--cc-space-2);
  font-family: var(--cc-font-body);
  font-size: var(--cc-fs-body);
  font-weight: var(--cc-weight-semibold);
  line-height: var(--cc-lh-body);
  color: var(--cc-text);
}

.cc-message-form__input {
  display: block;
  width: 100%;
  /* The same floor as the button, so a field and the Send control beneath
     it read as one family. A control minimum, not a grid value. */
  min-height: 56px;
  margin: 0;
  padding: var(--cc-space-3) var(--cc-space-4);
  font-family: var(--cc-font-body);
  font-size: var(--cc-fs-body);
  line-height: var(--cc-lh-body);
  color: var(--cc-text);
  background: var(--cc-white);
  border: 1px solid var(--cc-border-strong);
  border-radius: var(--cc-radius-md);
  -webkit-appearance: none;
  appearance: none;
  transition: border-color var(--cc-transition), box-shadow var(--cc-transition);
}
.cc-message-form__input::placeholder {
  color: var(--cc-text-muted);
  opacity: 1;
}
textarea.cc-message-form__input {
  /* Room for a few lines of a message before the visitor has to grow it.
     A readable minimum, not a grid value. */
  min-height: 160px;
  resize: vertical;
}
.cc-message-form__input:focus {
  outline: none;
  border-color: var(--cc-button-warm-hover);
  box-shadow: 0 0 0 3px var(--cc-button-warm-hover);
}
.cc-message-form__input[aria-invalid="true"] {
  border-color: var(--cc-red);
}

.cc-message-form__error {
  margin: var(--cc-space-2) 0 0;
  font-size: var(--cc-fs-small);
  line-height: var(--cc-lh-body);
  color: var(--cc-red);
}

.cc-message-form__status {
  margin: var(--cc-space-4) 0 0;
  font-size: var(--cc-fs-small);
  line-height: var(--cc-lh-body);
  color: var(--cc-text-muted);
}
/* An empty status takes no room between the fields and the actions. The
   script writes text into it and clears it; it never toggles hidden. */
.cc-message-form__status:empty {
  display: none;
}
.cc-message-form.is-failed .cc-message-form__status {
  color: var(--cc-red);
}

.cc-message-form__actions {
  display: flex;
  flex-direction: column;
  align-items: center;
  margin-block-start: var(--cc-space-6);
}

/* Cancel uses brand-red text and no underline. 44px is the
   accessible touch target, a control minimum and not a grid value. Below the
   breakpoint it sits under Send and carries its own gap; above it the row's
   gap governs and the margin goes. */
.cc-message-form__cancel {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  min-height: 44px;
  margin: var(--cc-space-2) 0 0;
  padding: 0;
  border: 0;
  background: none;
  font-family: var(--cc-font-body);
  font-size: var(--cc-fs-body);
  font-weight: var(--cc-weight-semibold);
  line-height: var(--cc-lh-body);
  text-decoration: none;
  color: var(--cc-red);
  cursor: pointer;
  transition: color var(--cc-transition);
}
.cc-message-form__cancel:hover {
  color: var(--cc-red-strong);
}
.cc-message-form__cancel:focus-visible {
  outline: none;
  border-radius: var(--cc-radius-sm);
  box-shadow: var(--cc-focus-ring);
}

@media (width < 900px) {
  /* Optical spacing below the text-only Cancel: its touch target and font
     metrics supply the remaining space to match a filled section CTA. */
  .cc-message-form__form {
    padding-block-end: var(--cc-space-6);
  }
}

/* Sent: the form goes and this line takes its place. It receives focus from
   the script so the thanks is read at once; the ring is suppressed because
   the line is not a control. */
.cc-message-form__sent {
  display: flex;
  align-items: flex-start;
  gap: var(--cc-space-3);
  margin: 0;
  font-size: var(--cc-fs-body);
  line-height: var(--cc-lh-body);
  color: var(--cc-text);
}
.cc-message-form__sent:focus {
  outline: none;
}
.cc-message-form__sent .cc-icon {
  width: var(--cc-icon-md);
  height: var(--cc-icon-md);
  /* Centred on the first line of the text, whatever the text wraps to. */
  margin-block-start: calc(
    (var(--cc-fs-body) * var(--cc-lh-body) - var(--cc-icon-md)) / 2
  );
  color: var(--cc-red);
}

@media (min-width: 900px) {
  /* The same reservation hug-split declares, read from the same three
     tokens, so the form stops one gutter short of the control column. */
  .cc-message-form {
    padding-inline-end: calc(
      var(--cc-page-inset) + var(--cc-grid-gutter) + var(--cc-btn-w-desktop)
    );
  }
  /* Send then Cancel on one row. stretch, not center, so Cancel's box takes
     the row's 56px and its top lines up with Send's. */
  .cc-message-form__actions {
    flex-direction: row;
    align-items: stretch;
    gap: var(--cc-space-4);
  }
  .cc-message-form__cancel {
    margin: 0;
  }
}

/* ==========================================================================
   COMPONENT: page-hero  (id: page-hero)
   Full-bleed photographic masthead. Owns the photograph and the black scrims
   that keep white type legible over it. site-header renders inside this
   component and is not modified by it.

   Two scrims, both black:
     top  — runs down from the top edge, clearing the nav row
     left — holds full strength across the content column, then eases to zero

   The left scrim is described by two numbers per breakpoint, each a
   percentage of the hero's own width:
     solid  where full strength ends      (comp: ~50% mobile, ~33% desktop)
     reach  where the fade finishes at 0

   Founder refinement 2026-09-22: the fade finishes inside the photograph
   at both breakpoints, leaving the right edge clear below the top scrim.
   This replaces the earlier mobile off-canvas fade, which darkened the
   entire photograph regardless of its exposure.

   The fade is deliberately long and shallow. A short ramp ending at the
   column edge leaves the tail of each line uncovered on a light photograph;
   a long tail still carries real alpha where the text actually sits.

   HEIGHT comes from width, never from viewport height. aspect-ratio sets it,
   max-height caps it on very wide screens, and min-height: min-content
   guarantees tall content is never clipped.

   TUNING: every dimension below is a named custom property. No selector
   needs to be touched to retune.
   ========================================================================== */
.cc-hero {
  /* --- Top scrim (adjustable) ------------------------------------------- */
  --cc-hero-scrim-top-size-mobile: 20%;  /* share of hero height reached from top */
  --cc-hero-scrim-top-size-desktop: 20%;

  /* --- Left scrim (adjustable), as a % of the hero's width --------------- */
  /* Mobile: about 37px solid at 393px, then clear just left of the Home
     hero's raised hand, which sits from 52% - 62px with the Home photo
     framing. The hand carries no shade. Founder pick (g1), 2026-11-07. */
  --cc-hero-scrim-left-solid-mobile: calc(10.1781% - 2.7273px);
  --cc-hero-scrim-left-reach-mobile: calc(52% - 66px);
  --cc-hero-scrim-left-solid-desktop: 14%;
  --cc-hero-scrim-left-reach-desktop: 50%;

  /* --- Scrim strength (adjustable): alpha at the solid end --------------- */
  --cc-hero-scrim-top-opacity: 1;
  /* Both modes anchor the copy against a black left edge. On Home the page
     hides it during the intro clip and fades it in with the words; this is
     its resting state (reduced motion, no script, failed clip). */
  --cc-hero-scrim-left-opacity: 1;

  /* --- Left scrim falloff curve (adjustable) -----------------------------
     Six stops between `solid` and `reach`. Each is a pair: p = position as a
     fraction of the fade span, a = alpha, multiplied by the opacity above.

     Mobile holds a full shoulder (alpha = 1 - t^2), dark behind the eyebrow
     and the start of the title, then falls to clear before the hand.
     Founder pick (g1), 2026-11-07; copy-below-mobile suppresses this scrim.

     These are the MOBILE values. The desktop block at the end of this
     component restates all twelve, so the two breakpoints tune independently
     — the desktop falloff is founder-approved and must not move when mobile
     is adjusted. */
  --cc-hero-scrim-left-p1: 0.15;  --cc-hero-scrim-left-a1: 0.978;
  --cc-hero-scrim-left-p2: 0.28;  --cc-hero-scrim-left-a2: 0.922;
  --cc-hero-scrim-left-p3: 0.40;  --cc-hero-scrim-left-a3: 0.84;
  --cc-hero-scrim-left-p4: 0.60;  --cc-hero-scrim-left-a4: 0.64;
  --cc-hero-scrim-left-p5: 0.78;  --cc-hero-scrim-left-a5: 0.392;
  --cc-hero-scrim-left-p6: 0.90;  --cc-hero-scrim-left-a6: 0.19;
  --cc-hero-scrim-left-end-alpha: 0;

  /* --- Bottom rule (adjustable) -----------------------------------------
     Measured 6px on the 571-wide mobile comp and 5px on the 1440-wide desktop
     comp; both normalise to one 4px half-step.

     Base characteristic, not a modifier. Founder ruling 2026-08-14: every
     page's hero carries the rule. This diverges from the accepted About comp,
     which ends its hero dark-to-light with no rule. The ruling governs; do not
     restore the modifier by re-reading that comp. */
  --cc-hero-rule-size: 4px;

  /* --- Photograph framing (adjustable, per instance) ---------------------
     The shared photo contract. Same two names on media-frame. Full
     explanation on .cc-hero__photo below. These are the hero's DEFAULTS; a
     placement overrides either one on this element.

     Was 70% 50%, carried over from the comps with the note "subject sits
     right of the scrim". Measured against real photographs on 2026-08-14,
     that value did neither thing. The X term is inert at desktop for every
     photograph we hold, because a hero 1.70 times wider than it is tall
     crops a near-square or portrait photograph vertically and not at all
     horizontally. At mobile the X term was live but pointed the wrong way:
     raising it moves the visible window right, which slides the subject LEFT,
     under the scrim. And 50% on the vertical put the top of a head exactly on
     the hero's top edge. 35% is the same generic upward bias media-frame
     carries. */
  --cc-photo-focal: 50% 35%;
  --cc-photo-zoom: 1;

  /* --- Height (adjustable) ----------------------------------------------
     Tracks the hero's OWN width. The cq term carries the ratio: measured off
     the comps on mobile, and a founder value on desktop. The clamp floors it
     and caps it so the tall mobile ratio cannot run away as the width
     approaches the 900px breakpoint.

     The unit is cqw, not vw. With vw the height was a function of the window
     while the width was a function of the container, so the two diverged and
     the ratio broke anywhere the hero was not exactly viewport-wide — inside
     this review page's 1100px wrap, and in any page that caps its content.
     A reusable object must not read the viewport to size itself.

     Applied on .cc-hero__inner, not here: an element cannot query itself, and
     the inner spans the whole masthead including the header, so the ratio
     describes what the comps actually measure.

     This is a min-height on purpose. Content always wins over it, so nothing
     can ever be clipped.

     Do NOT rewrite this as `aspect-ratio` plus `max-height`. When max-height
     clamps a box that carries an aspect-ratio, Chrome honours the ratio by
     SHRINKING THE WIDTH: a 34rem cap turned a full-bleed hero into a 435px
     box inside a 500px viewport, and clipped the second action button out of
     existence at the same time. Verified 2026-08-13. */
  --cc-hero-height-mobile: clamp(30rem, 125cqw, 44rem);  /* comp: 1.25 x width */
  --cc-hero-height-desktop: clamp(32rem, 50cqw, 54rem);  /* founder: 0.50 x width */

  /* --- Photograph height, copy-below-mobile only (adjustable) ------------
     Used by the `copy-below-mobile` modifier at the end of this component,
     where the photograph is a clean band of its own rather than the ground
     under the copy. It replaces --cc-hero-height-mobile in that mode.

     4:3 landscape, so 100cqw x 3/4 = 75cqw. A named conventional ratio, not a
     raster measurement: the About comp's photo band is close to 4:3 and this
     is the nearest standard. The clamp does the same job as the one above —
     it stops the ratio running away as the width approaches 900px. */
  --cc-hero-photo-height-mobile: clamp(18rem, 75cqw, 36rem);

  /* --- Content column (adjustable) --------------------------------------
     The cq term sizes the column on phones; the rem ceiling stops it — and
     therefore the block buttons inside it — from stretching between the
     phone range and the 900px breakpoint. This is what removes the need for
     a separate tablet breakpoint.

     cqw for the same reason as the height above: the measure is a fraction of
     the hero's own width, not of the window. Resolved on .cc-hero__body,
     which is inside the .cc-hero query container. */
  --cc-hero-content-max: clamp(17rem, 62cqw, 27rem);

  /* Resolved per breakpoint by the media query at the end of this block. */
  --_scrim-top-size: var(--cc-hero-scrim-top-size-mobile);
  --_scrim-left-solid: var(--cc-hero-scrim-left-solid-mobile);
  --_scrim-left-reach: var(--cc-hero-scrim-left-reach-mobile);
  --_hero-height: var(--cc-hero-height-mobile);

  /* Span of the left scrim's fade, used to place its stops. */
  --_scrim-left-fade: calc(var(--_scrim-left-reach) - var(--_scrim-left-solid));

  position: relative;
  isolation: isolate;
  /* Clips the photograph when --cc-photo-zoom is above 1, which scales it
     past the hero's edges. Safe: the mobile menu is in normal flow inside
     .cc-hero__inner and both scrims are inset:0 pseudo-elements, so nothing
     that must be seen sits outside this box. The bottom rule is a border and
     so lies outside the padding box, unaffected. */
  overflow: hidden;
  display: flex;
  flex-direction: column;
  /* Query container for the height ratio above. Makes the hero's geometry a
     function of its own width, so it is correct in any container it is given
     — this review page, a capped page, or a full-bleed one. */
  container-type: inline-size;
  background-color: var(--cc-ink);
  color: var(--cc-text-on-dark);
  /* Brand-red rule on the bottom edge, on every hero. A border rather than a
     pseudo-element: both pseudo-elements carry scrims, and a border sits
     outside the padding box so the left scrim's `inset: 0` cannot cover it. */
  border-bottom: var(--cc-hero-rule-size) solid var(--cc-red);
}

/* The gap below that rule. The hero owns it, because the rule is the hero's
   own edge; a following section has no way to know it is following one.

   Two page shapes reach the same section. Home writes the hero bare, so the
   next band is the hero's own sibling. About and Plan wrap the hero in a band
   to carry the surface its copy sits on below the breakpoint, so the next band
   is the wrapper's sibling. Both are matched here rather than asking a page to
   add a class, so a page written tomorrow needs no markup for this.

   The target is the band's padded child, never .cc-band itself: the band
   paints the surface and its child owns the block rhythm. feature-split and
   band__inner are the two that carry padding-block directly in a band;
   site-footer is the third and never follows a hero.

   This outranks both the base and the desktop step on those two components,
   so no @media rule is needed here - the token steps instead. Founder
   direction 2026-08-21. */
.cc-hero + .cc-band > .cc-feature-split,
.cc-hero + .cc-band > .cc-band__inner,
.cc-band:has(> .cc-hero) + .cc-band > .cc-feature-split,
.cc-band:has(> .cc-hero) + .cc-band > .cc-band__inner {
  padding-block-start: var(--cc-hero-rule-gap);
}

/* Exception. Above the threshold media-bleed-desktop zeroes the split's block
   padding so its ground reaches the band's top and bottom edges. The gap above
   would reopen the top and leave a strip of band showing under the hero's
   closing rule. Same specificity as the rule above, declared after it, and
   scoped to the desktop step because below it the ground is not bled and the
   gap is wanted. GIVE-02 is the only mapped case. */
@media (min-width: 900px) {
  .cc-hero + .cc-band > .cc-feature-split--media-bleed-desktop,
  .cc-band:has(> .cc-hero) + .cc-band > .cc-feature-split--media-bleed-desktop {
    padding-block-start: 0;
  }
}

/* Height carrier. Exists only because a query container cannot query itself.
   It wraps every in-flow child — header included — so the comp ratio applies
   to the whole masthead rather than to the copy block alone. */
.cc-hero__inner {
  display: flex;
  flex: 1;
  flex-direction: column;
  min-height: var(--_hero-height);
}

/* Photograph. Sits under both scrims.

   ---------------------------------------------------------------------------
   THE SHARED PHOTO FRAMING CONTRACT. Read this once; it governs every
   photograph on the site, in this component and in media-frame.

   One source photograph is reused across placements whose boxes differ in
   proportion and size. These two properties, and their optional desktop
   pair below, are how a placement chooses what the box shows. They are the
   ONLY framing controls.

     --cc-photo-focal   which part of the photograph stays in frame.
                        Any CSS <position>: "70% 50%", "left top", "center".
                        0% 0% shows the top-left of the image, 100% 100% the
                        bottom-right. Default varies by component.

     --cc-photo-zoom    how tight the crop is. 1 is the cover fit and is the
                        FLOOR — below 1 the image no longer fills the box and
                        the frame's background shows through at the edges.
                        1.2 shows roughly 83% of what 1 shows.

   transform-origin repeats the focal point so that zooming closes in on the
   chosen subject rather than on the middle of the box.

   HOW A PLACEMENT SETS THEM. On the element carrying the component class,
   as a custom-property-only style attribute:

     <section class="cc-hero" style="--cc-photo-focal: 40% 22%">
     <figure class="cc-media-frame" style="--cc-photo-zoom: 1.15">

   This is the one permitted use of a style attribute. It is per-placement
   data, not styling: the appearance still comes entirely from this file.

   PER-BREAKPOINT CROPPING. When one placement needs a different crop from
   900px up, it also sets --cc-photo-focal-desktop and/or
   --cc-photo-zoom-desktop in the same style attribute. Each falls back to
   its base property, so a placement that sets neither keeps one framing at
   every width. A page never writes its own media query for framing: that
   would be page CSS for a component. Founder direction 2026-09-27, after
   GIVE-01 failed the Portability Eval on a page-scoped rule.

     <section class="cc-hero" style="--cc-photo-focal: 79% 50%;
       --cc-photo-zoom: 1.17; --cc-photo-focal-desktop: 50% 40%">


   Adding srcset or <picture> later does not disturb any of this — these are
   CSS properties on the rendered <img>, whichever source it resolves to.
   --------------------------------------------------------------------------- */
.cc-hero__photo {
  position: absolute;
  inset: 0;
  z-index: -2;
  width: 100%;
  height: 100%;
  object-fit: cover;
  object-position: var(--cc-photo-focal);
  scale: var(--cc-photo-zoom);
  transform-origin: var(--cc-photo-focal);
}
@media (min-width: 900px) {
  .cc-hero__photo {
    object-position: var(--cc-photo-focal-desktop, var(--cc-photo-focal));
    scale: var(--cc-photo-zoom-desktop, var(--cc-photo-zoom));
    transform-origin: var(--cc-photo-focal-desktop, var(--cc-photo-focal));
  }
}

/* Scrims. Multi-stop rather than a two-stop linear ramp: a straight ramp
   bands visibly across a hero this large. The stops approximate an ease-out
   so the falloff reads smooth on a photograph.

   OPT-IN. Neither scrim paints unless its own modifier class is present, so a
   page can carry the top scrim, the left scrim, both, or neither according to
   what its photograph and copy placement require.

   A hero that puts white type over a photograph needs at least one of them.
   Omitting both is a legibility failure, not a style choice. */
.cc-hero--scrim-top::before,
.cc-hero--scrim-left::after {
  content: "";
  position: absolute;
  z-index: -1;
  pointer-events: none;
}

/* Top scrim. Hold a dark shoulder through half the reach, then taper to
   transparent with a soft tail. Positions are relative to the scrim height. */
.cc-hero--scrim-top::before {
  inset: 0 0 auto 0;
  height: var(--_scrim-top-size);
  background-image: linear-gradient(
    to bottom,
    rgba(0, 0, 0, var(--cc-hero-scrim-top-opacity)) 0%,
    rgba(0, 0, 0, calc(var(--cc-hero-scrim-top-opacity) * 0.98)) 25%,
    rgba(0, 0, 0, calc(var(--cc-hero-scrim-top-opacity) * 0.70)) 50%,
    rgba(0, 0, 0, calc(var(--cc-hero-scrim-top-opacity) * 0.65)) 65%,
    rgba(0, 0, 0, calc(var(--cc-hero-scrim-top-opacity) * 0.35)) 80%,
    rgba(0, 0, 0, calc(var(--cc-hero-scrim-top-opacity) * 0.12)) 92%,
    rgba(0, 0, 0, 0) 100%
  );
}

/* Left scrim. Spans the whole hero so every stop can be read directly as a
   percentage of the hero's width. Full strength to `solid`, then a long
   shallow ease to the endpoint alpha at `reach`. */
.cc-hero--scrim-left::after {
  inset: 0;
  background-image: linear-gradient(
    to right,
    rgba(0, 0, 0, var(--cc-hero-scrim-left-opacity)) 0%,
    rgba(0, 0, 0, var(--cc-hero-scrim-left-opacity)) var(--_scrim-left-solid),
    rgba(0, 0, 0, calc(var(--cc-hero-scrim-left-opacity) * var(--cc-hero-scrim-left-a1)))
      calc(var(--_scrim-left-solid) + var(--_scrim-left-fade) * var(--cc-hero-scrim-left-p1)),
    rgba(0, 0, 0, calc(var(--cc-hero-scrim-left-opacity) * var(--cc-hero-scrim-left-a2)))
      calc(var(--_scrim-left-solid) + var(--_scrim-left-fade) * var(--cc-hero-scrim-left-p2)),
    rgba(0, 0, 0, calc(var(--cc-hero-scrim-left-opacity) * var(--cc-hero-scrim-left-a3)))
      calc(var(--_scrim-left-solid) + var(--_scrim-left-fade) * var(--cc-hero-scrim-left-p3)),
    rgba(0, 0, 0, calc(var(--cc-hero-scrim-left-opacity) * var(--cc-hero-scrim-left-a4)))
      calc(var(--_scrim-left-solid) + var(--_scrim-left-fade) * var(--cc-hero-scrim-left-p4)),
    rgba(0, 0, 0, calc(var(--cc-hero-scrim-left-opacity) * var(--cc-hero-scrim-left-a5)))
      calc(var(--_scrim-left-solid) + var(--_scrim-left-fade) * var(--cc-hero-scrim-left-p5)),
    rgba(0, 0, 0, calc(var(--cc-hero-scrim-left-opacity) * var(--cc-hero-scrim-left-a6)))
      calc(var(--_scrim-left-solid) + var(--_scrim-left-fade) * var(--cc-hero-scrim-left-p6)),
    rgba(0, 0, 0, calc(var(--cc-hero-scrim-left-opacity) * var(--cc-hero-scrim-left-end-alpha))) var(--_scrim-left-reach)
  );
}

/* Content slot. The page supplies eyebrow, heading, copy, and actions; this
   component only sets the ground, the measure, and the padding. Bottom
   anchored at both breakpoints, matching the comps. */
.cc-hero__content {
  position: relative;
  display: flex;
  flex: 1;
  flex-direction: column;
  justify-content: flex-end;
  padding: var(--cc-space-7) var(--cc-page-inset) var(--cc-space-6);
}
.cc-hero__body {
  max-width: var(--cc-hero-content-max);
}
.cc-hero__body .cc-eyebrow {
  margin-bottom: var(--cc-space-4);
}
.cc-hero__title {
  margin: 0 0 var(--cc-space-5);
  font-family: var(--cc-font-display);
  font-size: var(--cc-fs-hero);
  font-weight: var(--cc-weight-semibold);
  line-height: var(--cc-lh-tight);
  letter-spacing: -0.015em;
  color: var(--cc-text-on-dark);
}
.cc-hero__lead {
  margin: 0 0 var(--cc-space-6);
  font-size: var(--cc-fs-body);
  line-height: var(--cc-lh-body);
  color: var(--cc-text-on-dark-muted);
}
.cc-hero__lead p {
  margin: 0 0 var(--cc-space-4);
}
.cc-hero__lead p:last-child {
  margin-bottom: 0;
}
.cc-hero__actions {
  display: flex;
  flex-direction: column;
  gap: var(--cc-space-3);
}

/* Modifier: copy-below-mobile ------------------------------------------------
   Below 900px the photograph renders CLEAN and the hero copy sits beneath it
   on the band. At 900px and above the component returns to the overlay hero,
   unchanged. About needs this; Home overlays at both breakpoints.

   ONE COMPONENT REFLOWING, NOT TWO LAYOUTS. The page supplies the same markup
   at both breakpoints and adds this one class. A page must never arrange the
   hero itself — that is the HOME-02 fork defect.

   Written mobile-first and undone inside the min-width block below, the same
   way media-bleed-mobile is written on feature-split, so no second breakpoint
   value exists anywhere in this file.

   The header still sits OVER the photograph, so the top scrim still applies
   and is not touched here. The left scrim is suppressed: nothing sits over the
   photograph to need it. A placement still declares scrim-left for desktop.

   Ground comes from the band, exactly as .cc-band resolves it, so this file
   still names no surface value and COL-01's closed ladder still governs.
   A placement must therefore put the hero inside a band.

   THE RED RULE MOVES WITH THE PHOTOGRAPH. Founder direction 2026-08-20: the
   rule always closes the header/hero unit, and in this mode that unit ends at
   the bottom of the photograph, not at the bottom of the component. The copy
   below then reads as its own section. Every interior mobile page obeys this.
   Same size, same colour, same job — only the edge it sits on changes, so no
   new value enters the file. */
.cc-hero--copy-below-mobile {
  background-color: var(--cc-band-surface, transparent);
  color: inherit;
  border-bottom-width: 0;
}
/* The rule, drawn on the top edge of the copy area. In flow, so it stays on
   the photograph's bottom edge when the row is at its natural height and
   follows the copy down when an open mobile menu grows the row. */
.cc-hero--copy-below-mobile .cc-hero__content {
  /* Keep a zoomed photograph behind the photo row, not the copy beneath. */
  background-color: var(--cc-band-surface, transparent);
  border-top: var(--cc-hero-rule-size) solid var(--cc-red);
  /* Below the breakpoint the rule is this element's own top edge, so the gap
     below it is this element's top padding rather than a following section's.
     Same token, same measured result, one rule: at desktop the token is
     --cc-space-7, which is the base padding this would otherwise inherit, and
     the copy is justified to flex-end there in any case. */
  padding-block-start: var(--cc-hero-rule-gap);
}

/* Two rows: the photograph, then the copy. The header and the content slot are
   already the only two children, so they auto-place — no selector here reaches
   into site-header, which this component still does not modify.

   minmax, not a bare height: when the mobile menu opens, the header grows past
   the photo band and row 1 must grow with it or the panel would overlap the
   copy. align-items keeps both rows' items at their natural height instead of
   stretching the header down the whole photo band. */
.cc-hero--copy-below-mobile .cc-hero__inner {
  display: grid;
  grid-template-rows: minmax(var(--cc-hero-photo-height-mobile), auto) auto;
  align-items: start;
  min-height: 0;
}
.cc-hero--copy-below-mobile .cc-hero__photo {
  inset: 0 0 auto 0;
  height: var(--cc-hero-photo-height-mobile);
}
/* Measure the top fade against the photograph, excluding the copy below.
   Background sizing preserves the shared percentage/length reach control. */
.cc-hero--copy-below-mobile.cc-hero--scrim-top::before {
  /* Give the mobile logo and menu a dark backdrop before the fade clears. */
  --cc-hero-scrim-top-size-mobile: 35%;
  height: var(--cc-hero-photo-height-mobile);
  background-size: 100% var(--cc-hero-scrim-top-size-mobile);
  background-repeat: no-repeat;
}
.cc-hero--copy-below-mobile.cc-hero--scrim-left::after {
  display: none;
}
/* Full measure. The overlay column exists because the scrim only covers part
   of the width; with no scrim the copy runs the full inset width. */
.cc-hero--copy-below-mobile .cc-hero__body {
  max-width: 100%;
}
.cc-hero--copy-below-mobile .cc-hero__title {
  color: inherit;
}
.cc-hero--copy-below-mobile .cc-hero__lead {
  color: var(--cc-text-muted);
}

/* The eyebrow does not render in this mode. The red rule on the photograph's
   bottom edge already carries that accent, and the two repeat within one
   screen. Founder ruling 2026-08-20, mobile only. Desktop is the overlay hero,
   has no photograph edge to carry the accent, and keeps its eyebrow, so the
   block below restores it. The page still supplies the eyebrow markup at both
   breakpoints; the breakpoint belongs to this file, not to a page. */
.cc-hero--copy-below-mobile .cc-hero__body .cc-eyebrow {
  display: none;
}

/* The secondary action. This mode moves the copy off the photograph and onto
   the band, so outline-light's white border and white label would land on a
   light ground and disappear. The page still writes outline-light, which is
   the hero's secondary at every placement; the three private colour
   properties are repainted here with the same tokens outline-ink already uses
   on a light band. That keeps this a hero behaviour, alongside the title,
   lead and eyebrow rules above, rather than a fourth outline variant. The
   button section of the library is unchanged. Founder ruling 2026-08-20.
   VISIT-01 is the first placement to need it: HOME-01's hero copy stays on
   the photograph at every width, and ABOUT-01 carries no outline action. */
.cc-hero--copy-below-mobile .cc-hero__actions .cc-btn--outline-light {
  --_btn-bg: var(--cc-white);
  --_btn-fg: var(--cc-ink);
  --_btn-border: var(--cc-ink);
}
.cc-hero--copy-below-mobile .cc-hero__actions .cc-btn--outline-light:hover {
  --_btn-bg: var(--cc-ink);
  --_btn-fg: var(--cc-white);
  --_btn-border: var(--cc-ink);
}

/* Modifier: copy-hidden-mobile -----------------------------------------------
   Below 900px the hero renders the nav + photograph only and withholds its
   own copy; the section placed after it leads in the copy's place. At 900px
   and above the hero is the full overlay hero, copy and all, unchanged.

   GIVE-01 is the only placement. Founder direction 2026-08-29: the Giving
   mobile hero keeps the site-wide interior pattern — nav over the photograph,
   the red rule closing that unit — but GIVE-01's copy did not carry the
   funnel, so GIVE-02 replaces it directly below. Showing GIVE-01's copy as
   well would be redundant. Desktop keeps the full hero.

   Layered on copy-below-mobile, the mode every interior hero uses to drop its
   copy below the photograph on mobile; this modifier withholds that dropped
   copy. Written mobile-first and undone in the min-width block, like the rest
   of this component, so no second breakpoint value is introduced. */
.cc-hero--copy-hidden-mobile .cc-hero__content {
  display: none;
}
/* The red rule closes the hero unit. copy-below-mobile hands the rule to the
   copy's top edge; with the copy withheld the unit ends at the photograph, so
   the rule returns to the hero's own bottom border — the base value this file
   already carries. Only meaningful alongside copy-below-mobile, the one mode
   that moved it, so the restore is scoped to that pair. */
.cc-hero--copy-below-mobile.cc-hero--copy-hidden-mobile {
  border-bottom-width: var(--cc-hero-rule-size);
}

@media (min-width: 900px) {
  .cc-hero {
    --_scrim-top-size: var(--cc-hero-scrim-top-size-desktop);
    --_scrim-left-solid: var(--cc-hero-scrim-left-solid-desktop);
    --_scrim-left-reach: var(--cc-hero-scrim-left-reach-desktop);
    --_hero-height: var(--cc-hero-height-desktop);
    /* Desktop falloff curve and strength. Founder-approved 2026-08-13 against
       the About comp. Independent of the mobile values above — change one
       without touching the other. */
    --cc-hero-scrim-left-opacity: 1;
    --cc-hero-scrim-left-end-alpha: 0;
    --cc-hero-scrim-left-p1: 0.14;  --cc-hero-scrim-left-a1: 0.86;
    --cc-hero-scrim-left-p2: 0.28;  --cc-hero-scrim-left-a2: 0.72;
    --cc-hero-scrim-left-p3: 0.42;  --cc-hero-scrim-left-a3: 0.58;
    --cc-hero-scrim-left-p4: 0.57;  --cc-hero-scrim-left-a4: 0.44;
    --cc-hero-scrim-left-p5: 0.71;  --cc-hero-scrim-left-a5: 0.30;
    --cc-hero-scrim-left-p6: 0.86;  --cc-hero-scrim-left-a6: 0.15;
    /* Desktop comp measure is 658px at 1440. The floor keeps the column from
       collapsing just above the breakpoint. */
    --cc-hero-content-max: clamp(27rem, 46cqw, 41rem);
  }
  .cc-hero__content {
    /* Bottom is one step above the inline gutter on the 4px scale, matching
       the mobile ratio. Block spacing carries the section boundary, so it
       stays above the inline gutter rather than equal to it. The former 6rem
       was off-scale. Founder direction 2026-08-13. */
    padding: var(--cc-space-8) var(--cc-page-inset);
  }
  .cc-hero__actions {
    flex-direction: row;
    flex-wrap: wrap;
    gap: var(--cc-space-4);
  }

  /* Undo copy-below-mobile. Desktop is the overlay hero for every page, so
     each line here restores a base value rather than introducing a new one.
     grid-template-rows needs no undo: display: flex ignores it. */
  .cc-hero--copy-below-mobile {
    background-color: var(--cc-ink);
    color: var(--cc-text-on-dark);
    border-bottom-width: var(--cc-hero-rule-size);
  }
  .cc-hero--copy-below-mobile .cc-hero__content {
    background-color: transparent;
    border-top-width: 0;
    /* Restores the base desktop padding. The rule this mode's top padding was
       tracking is a mobile-only edge; above the breakpoint the rule is back on
       the hero's bottom border and the following section carries the gap. The
       base here is --cc-space-8, not --cc-space-7, so this cannot be left to
       the token. */
    padding-block-start: var(--cc-space-8);
  }
  .cc-hero--copy-below-mobile .cc-hero__inner {
    display: flex;
    align-items: stretch;
    min-height: var(--_hero-height);
  }
  .cc-hero--copy-below-mobile .cc-hero__photo {
    inset: 0;
    height: 100%;
  }
  .cc-hero--copy-below-mobile.cc-hero--scrim-top::before {
    height: var(--_scrim-top-size);
    background-size: 100% 100%;
  }
  .cc-hero--copy-below-mobile.cc-hero--scrim-left::after {
    display: block;
  }
  .cc-hero--copy-below-mobile .cc-hero__body {
    max-width: var(--cc-hero-content-max);
  }
  .cc-hero--copy-below-mobile .cc-hero__title {
    color: var(--cc-text-on-dark);
  }
  .cc-hero--copy-below-mobile .cc-hero__lead {
    color: var(--cc-text-on-dark-muted);
  }
  /* Restores the base .cc-eyebrow display value. */
  .cc-hero--copy-below-mobile .cc-hero__body .cc-eyebrow {
    display: flex;
  }
  /* Restores the base outline-light values. The copy is back on the
     photograph here, so the variant is correct as written. */
  .cc-hero--copy-below-mobile .cc-hero__actions .cc-btn--outline-light {
    --_btn-bg: transparent;
    --_btn-fg: var(--cc-white);
    --_btn-border: var(--cc-border-on-dark);
  }
  .cc-hero--copy-below-mobile .cc-hero__actions .cc-btn--outline-light:hover {
    --_btn-bg: var(--cc-border-on-dark-soft);
    --_btn-fg: var(--cc-white);
    --_btn-border: var(--cc-white);
  }

  /* Restores the base content display. Desktop is the full overlay hero for
     this placement too; copy-hidden-mobile withholds the copy on mobile only. */
  .cc-hero--copy-hidden-mobile .cc-hero__content {
    display: flex;
  }
}

/* ==========================================================================
   COMPONENT: site-header  (id: site-header)
   Logo lockup + primary navigation. Responsive: mobile hamburger + panel,
   desktop inline nav.
   Variant: over-hero (transparent, white text)
   State:   menu-open (set on the root by js/site-header.js)
   ========================================================================== */
.cc-header {
  position: relative;
  width: 100%;
  color: var(--cc-text);
  z-index: 20;
}
.cc-header--over-hero {
  color: var(--cc-text-on-dark);
  background: transparent;
}

/* State: while the mobile panel is open the bar takes a solid surface so the
   transparent over-hero variant stays readable against the panel. */
.cc-header--menu-open.cc-header--over-hero {
  background: var(--cc-ink);
}

/* The bar's inline padding is the site page inset, so the logo and the nav sit
   on the same line as the hero title, the feature-split copy, and the footer
   beneath them. It previously held --cc-space-5 at both breakpoints and so did
   not rise to 48px at desktop, leaving the logo 24px adrift of everything
   below it. That was invisible while the review page capped every stage at
   1100px and added a gutter of its own. */
.cc-header__inner {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: var(--cc-space-4);
  padding: var(--cc-space-4) var(--cc-page-inset);
}

.cc-header__brand {
  display: inline-flex;
  align-items: center;
  text-decoration: none;
}
.cc-header__logo {
  height: 44px;
  width: auto;
}

/* Nav — inline on desktop, hidden on mobile (panel used instead) */
.cc-header__nav {
  display: none;
}
.cc-header__nav-list {
  list-style: none;
  display: flex;
  align-items: center;
  gap: var(--cc-space-5);
  margin: 0;
  padding: 0;
}
/* The nav RAMPS between the small and base steps rather than sitting on one.

   The header has a hard width limit that body copy does not. At a flat 18px
   the six links wrap onto two lines from 900px to 909px - measured, not
   assumed. Two fixes work. Tightening the gap between links holds 18px
   everywhere; dropping the nav to a flat 16px holds the gap. The founder
   chose the gap on 2026-08-18, on usability and accessibility grounds: the
   separation between click targets is worth more than two pixels of type.
   So --cc-space-5 stays and the type gives way instead, and only where it
   has to.

   (100vw - var(--cc-bp-desktop)) is the distance past the breakpoint, zero
   at the threshold. Divided by 50 it rises 2px across the first 100px, so
   the nav reads 16px at 900, 17px at 950, and reaches the base step at 1000,
   flat from there up. Most desktops therefore never see anything but 18px.

   NOTHING HERE IS SPECIFIC TO THIS CLIENT. Both endpoints are ladder steps
   and the ramp starts at the breakpoint token, so changing any of the three
   moves this rule with it. 50 is the only bare number and it is the rate:
   100px of width buys 2px of type.

   100vw reads the window, not this header's own box. That is safe because
   the ramp finishes at 1000px, far below --cc-canvas-max, so every wider
   screen sits on the flat ceiling. A header placed inside a narrower
   container would need a container query instead. */
.cc-header__nav-link {
  position: relative; /* anchors the current-page rule below */
  font-size: clamp(
    var(--cc-fs-small),
    calc(var(--cc-fs-small) + (100vw - var(--cc-bp-desktop)) / 50),
    var(--cc-fs-body)
  );
  font-weight: var(--cc-weight-medium);
  color: inherit;
  text-decoration: none;
  padding: var(--cc-space-2) 0;
  transition: color var(--cc-transition);
}
.cc-header__nav-link:hover {
  color: var(--cc-red);
}

/* State: current page. Set from the address by js/site-header.js, and never
   named by a page.

   THE MARK IS A SHAPE, NOT A COLOUR, AND THAT IS THE WHOLE POINT. Colour alone
   cannot carry this. The over-hero variant paints every link --cc-text-on-dark,
   which is #ffffff, and the earlier current-page rule painted the current one
   --cc-white, which is the same #ffffff. The state was invisible on every hero
   page from the day it was written; a 1px text-shadow was the only difference
   and it read as a rendering artefact. A rule under the label is visible on
   both variants and does not depend on being seen as a colour.

   THE RULE IS BRAND RED ON BOTH VARIANTS. Founder direction 2026-08-21,
   taken knowingly against visibility: it was white over a hero, matching the
   label, and the founder chose to match the footer's page marker instead so
   the site carries one colour for this state. Over a hero the label therefore
   stays white and only the rule is red. The rule was written as currentColor
   before this, which is why the declaration now names the token directly -
   THAT IS THE POINT OF IT, not an oversight, so do not fold it back into
   currentColor to save a line.

   Red holds 3.17:1 against --cc-ink. That is below the 4.5 minimum for text,
   which is exactly why the label is not red, but this is a graphical mark and
   3:1 is the non-text minimum, so the rule itself passes. It is a thin mark
   over a photograph, so it is quieter than the white was. That was accepted.

   2px, founder direction 2026-08-21. It is deliberately HALF the 4px of
   --cc-eyebrow__rule, which is the nearest relative. The eyebrow rule is a
   standalone decorative mark with air around it; this one sits directly under
   type at 16-18px, where 4px reads as a slab and 2px is the conventional
   weight for the job. The two vertical bars below stay at 4px: a short bar
   with nothing under it needs the weight to register at all. */
.cc-header__nav-link[aria-current="page"] {
  color: var(--cc-red);
}
.cc-header--over-hero .cc-header__nav-link[aria-current="page"] {
  color: var(--cc-white);
}
.cc-header__nav-link[aria-current="page"]::after {
  content: "";
  position: absolute;
  left: 0;
  right: 0;
  bottom: 0;
  height: 2px;
  border-radius: var(--cc-radius-pill);
  background: var(--cc-red);
}

/* Mobile toggle */
.cc-header__toggle {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  width: 48px;
  height: 48px;
  padding: 0;
  background: transparent;
  border: 0;
  color: inherit;
  cursor: pointer;
}
.cc-header__toggle .cc-icon {
  width: 28px;
  height: 28px;
}

/* Mobile slide-down panel */
.cc-header__menu {
  border-top: 1px solid var(--cc-border-on-dark);
  background: var(--cc-ink);
  color: var(--cc-text-on-dark);
}
.cc-header__menu[hidden] {
  display: none;
}
.cc-header__menu-list {
  list-style: none;
  margin: 0;
  /* Same page inset as the bar above it, so the panel's links line up with the
     logo. The panel only renders below the desktop threshold, where the token
     resolves to the 24px this previously hard-coded. */
  padding: var(--cc-space-3) var(--cc-page-inset) var(--cc-space-5);
  display: flex;
  flex-direction: column;
}
.cc-header__menu-list a {
  position: relative; /* anchors the current-page bar */
  display: block;
  padding: var(--cc-space-4) 0;
  font-size: var(--cc-fs-body);
  font-weight: var(--cc-weight-medium);
  text-decoration: none;
  color: inherit;
  border-bottom: 1px solid rgba(255, 255, 255, 0.12);
}
.cc-header__menu-list a:hover {
  color: var(--cc-red);
}

/* State: current page. A vertical list gets a leading bar rather than the
   nav's underline - an underline here would compete with the row hairline
   directly beneath it.

   The label keeps its inherited white on the ink panel, 19.2:1, so nothing a
   reader must read depends on the red. --cc-space-4 is the mobile page inset
   the menu list already pads by, so the bar lands flush against the panel edge
   without reading that inset a second time. */
.cc-header__menu-list a[aria-current="page"]::before {
  content: "";
  position: absolute;
  top: 50%;
  transform: translateY(-50%);
  left: calc(var(--cc-space-4) * -1);
  width: 4px;
  height: var(--cc-space-5);
  border-radius: var(--cc-radius-pill);
  background: var(--cc-red);
}

@media (min-width: 900px) {
  .cc-header__nav {
    display: block;
  }
  .cc-header__toggle,
  .cc-header__menu {
    display: none;
  }
  .cc-header__logo {
    height: 56px;
  }
}

/* ==========================================================================
   COMPONENT: site-footer  (id: site-footer)
   Ink band carrying the brand line, service details, address, and the icon
   link list. The compass rose sits behind the content as a faint watermark;
   the star divider separates the two blocks on mobile only.
   Composes: section-eyebrow (rule-only), info-list (bare + links, on-dark)
   ========================================================================== */
.cc-footer {
  position: relative;
  overflow: hidden;
  background: var(--cc-ink);
  color: var(--cc-text-on-dark);
}

/* Watermark. Decorative, so it is a background layer rather than an <img> and
   never takes pointer or assistive-technology attention. */
.cc-footer::before {
  content: "";
  position: absolute;
  top: var(--cc-space-6);
  right: -2rem;
  width: 26rem;
  aspect-ratio: 1;
  background-image: url(../assets/images/compass-transparent-image.png);
  background-repeat: no-repeat;
  background-size: contain;
  opacity: var(--cc-watermark-opacity);
  pointer-events: none;
}

.cc-footer__inner {
  position: relative; /* keeps content above the watermark */
  display: grid;
  grid-template-columns: 1fr;
  gap: var(--cc-space-6);
  padding: var(--cc-space-7) var(--cc-page-inset);
}

.cc-footer__name {
  margin: 0 0 var(--cc-space-3);
  font-family: var(--cc-font-display);
  font-size: var(--cc-fs-name);
  font-weight: var(--cc-weight-bold);
  line-height: var(--cc-lh-snug);
  color: var(--cc-text-on-dark);
}

.cc-footer__address {
  margin: var(--cc-space-5) 0 0;
  font-style: normal;
  font-size: var(--cc-fs-body);
  line-height: 1.5;
  color: var(--cc-text-on-dark-muted);
}

/* Star divider — mobile only, between the address block and the link list. */
.cc-footer__divider {
  display: block;
  width: 100%;
  max-width: 30rem;
  height: auto;
  margin: var(--cc-space-5) auto var(--cc-space-4);
}

@media (min-width: 900px) {
  .cc-footer::before {
    top: 50%;
    right: -10rem;
    width: 40rem;
    transform: translateY(-50%);
  }
  .cc-footer__inner {
    grid-template-columns: 1fr 1fr;
    column-gap: var(--cc-space-8);
    padding: var(--cc-space-8) var(--cc-page-inset);
  }
  .cc-footer__divider {
    display: none;
  }
}

/* Reusable full-width list placement. Owns its internal stack; inherited
   feature-split frame supplies the canonical page inset and section padding.
   The 640px reading measure is the employee's accepted copy cap, not a grid. */
.cc-feature-split--stacked-list { display:flex; flex-direction:column; gap:0; }
.cc-feature-split--stacked-list > .cc-feature-split__body { order:0; }
.cc-feature-split--stacked-list > .cc-feature-split__media { order:1; width:100%; margin-top:var(--cc-space-6); overflow:visible; }
.cc-feature-split--stacked-list > .cc-feature-split__actions { order:2; margin-top:var(--cc-space-6); align-items:stretch; }
@media (width < 900px) {
  .cc-eyebrow--desktop-only { display:none; }
}
@media (min-width:900px) {
  .cc-eyebrow--mobile-only { display:none; }
  .cc-feature-split--stacked-list > .cc-feature-split__body { max-width:640px; }
  .cc-feature-split--stacked-list > .cc-feature-split__media { margin-top:var(--cc-space-7); }
  .cc-feature-split--stacked-list > .cc-feature-split__actions { margin-top:var(--cc-space-8); align-items:flex-start; }
}

/* Rule 6: band context selects semantic card colors; non-card borders do not change.
   Light-2/warm-2 remains provisional pending the event-card comparison. */
.cc-band--white, .cc-band--light-3 { --cc-card-fill:var(--cc-band-light-1); --cc-card-border:var(--cc-band-warm-1); }
.cc-band--light-1 { --cc-card-fill:var(--cc-white); --cc-card-border:var(--cc-band-warm-1); }
.cc-band--light-2 { --cc-card-fill:var(--cc-white); --cc-card-border:var(--cc-band-warm-2); }
.cc-band--warm-1, .cc-band--warm-2, .cc-band--warm-3 { --cc-card-fill:var(--cc-white); --cc-card-border:transparent; }
