/* ==========================================================================
   sections.css — page-level section styles.
   Batch 1: sticky header (§12) + footer (§14).
   Batch 2: homepage sections (§13.1–§13.11) — static structure, responsive
   behavior and the hover states required by HP-4/HP-5/HP-6.
   Batch 3: hero capability-path visual (task 4.1), hero load sequence +
   path draw (5.1), process activation states (5.1), active-nav current
   state (5.3). Scroll-reveal states live in base.css; the reveal transition
   itself is delivered inline by js/reveal.js (5.2).
   ========================================================================== */

/* ==========================================================================
   §12 Header — sticky, solid Off White bar with a 1px hairline.

   The logo keeps the approved wordmark's 1X clear space: its box stays
   --logo-box-h tall (the height at which the ink measures the brand minimum
   of 120px wide) while the BAR is shorter. The box's transparent padding
   overflows symmetrically via a negative block margin, so the bar can be
   slimmer without shrinking the mark below the guideline.
   ========================================================================== */

.site-header {
  position: sticky;
  top: 0;
  z-index: var(--z-sticky);
  background: var(--off-white);
  border-bottom: 1px solid var(--line-quiet);
}

/* One calm surface: solid Off White with a hairline. The .is-scrolled and
   .is-over-dark classes (js/navigation.js) intentionally change nothing, so
   the bar never shifts colour between sections. */

.site-header__inner {
  min-height: var(--header-h);
  display: grid;
  grid-template-columns: auto 1fr auto;
  align-items: center;
  gap: clamp(16px, 2vw, 28px);
}

.site-header__brand img {
  height: var(--logo-box-h);
  width: auto;
  /* The oversized transparent box must not dictate the bar's height. */
  margin-block: calc((var(--header-h) - var(--logo-box-h)) / 2);
}

/* ---- Desktop navigation (spec §12.3) -------------------------------- */
.site-nav {
  justify-self: end;
}

.site-nav__list {
  display: flex;
  align-items: center;
  gap: var(--space-6);
  list-style: none;
  padding: 0;
  margin: 0;
}

.site-nav__link {
  display: inline-flex;
  align-items: center;
  min-height: 44px;                        /* WCAG 2.2 AA target */
  font-size: var(--fs-small);              /* 14px */
  font-weight: 600;
  line-height: 20px;
  color: var(--brand-ink);
  text-decoration: none;
  position: relative;
}

/* 2px Kuneo Blue underline grows left → right in 180ms (§12.3). */
.site-nav__link::after {
  content: "";
  position: absolute;
  left: 0;
  bottom: 8px;
  width: 100%;
  height: 2px;
  background: var(--kuneo-blue);
  transform: scaleX(0);
  transform-origin: left center;
  transition: transform 180ms var(--ease-standard);
}

/* `[aria-current]` covers both "page" (the page itself) and "true" (a case
   study, whose section is Work): the same mark for both. */
.site-nav__link:hover::after,
.site-nav__link:focus-visible::after,
.site-nav__link[aria-current]::after {
  transform: scaleX(1);
}

.site-nav__link[aria-current] {
  color: var(--brand-ink);                 /* text stays Ink (restraint) */
}

/* Current-section highlight (js/active-nav.js): visual scrollspy state on
   the homepage — never aria-current (that stays on the logo link, and the
   checker enforces exactly one aria-current per page). */
.site-nav__link.is-current {
  color: var(--kuneo-blue);
}

.site-nav__link.is-current::after {
  transform: scaleX(1);
}

.site-header__cta {
  justify-self: end;
}

/* ---- Mobile header (spec §12.6) -------------------------------------- */
.site-header__menu {
  display: none;
  width: 44px;
  height: 44px;
  align-items: center;
  justify-content: center;
  border-radius: var(--radius-control);
  color: var(--brand-ink);
}

.site-header__menu-icon {
  display: block;
  width: 24px;
  height: 24px;
}

/* ---- Mobile navigation panel (spec §12.7, mobile refinement §6) --------
   A full-height surface the colour of the page, not a dropdown sheet: the
   brief asks for "a premium fullscreen or near-fullscreen navigation", and a
   visitor who has committed to opening the menu should get a composed screen
   rather than a panel that shows the page behind it.

   HEIGHT: `100dvh` minus the bar, not `100vh`. On iOS Safari the address bar
   means 100vh is taller than the visible area, which would put the CTA (the
   panel's last element) under the browser chrome. The visually-hidden-but-
   present alternative is that the panel simply scrolls internally, which the
   overflow below provides for short landscape phones. */
.site-nav-panel {
  position: fixed;
  top: var(--header-h-mobile);
  right: 0;
  left: 0;
  bottom: auto;
  z-index: var(--z-menu);
  background: var(--white);
  padding: var(--space-6) var(--space-4);
  box-shadow: var(--shadow-hover);
  height: calc(100dvh - var(--header-h-mobile));
  overflow-y: auto;
  overscroll-behavior: contain;
  display: flex;
  flex-direction: column;
  /* The home-indicator strip. Padding (not height) so the CTA keeps its own
     size and only the breathing room grows on a notched device. */
  padding-bottom: calc(var(--space-8) + env(safe-area-inset-bottom, 0px));
  /* The notch in landscape. There is no left/right padding to compose against
     at this width, so the insets are added to the panel's own. */
  padding-left: calc(var(--space-4) + env(safe-area-inset-left, 0px));
  padding-right: calc(var(--space-4) + env(safe-area-inset-right, 0px));
}

.site-nav-panel__list {
  list-style: none;
  padding: 0;
  /* `auto` pushes the CTA to the bottom of the screen: the list takes the
     space that is left after the action, so the action reads as a footer to
     the navigation rather than as a seventh item. */
  margin: 0 0 var(--space-6);
  display: flex;
  flex-direction: column;
}

.site-nav-panel__link {
  display: flex;
  align-items: center;
  min-height: 44px;
  /* Bigger than the old 1.5rem: the brief asks for 28–34px in a spacious
     fullscreen menu, and the larger size is what makes the screen feel
     deliberate instead of a list of links in a box. */
  font-size: clamp(1.75rem, 8vw, 2.125rem);   /* 28–34px */
  font-weight: 700;
  line-height: 1.15;
  letter-spacing: -0.03em;
  color: var(--brand-ink);
  text-decoration: none;
  padding-block: var(--space-4);
  border-bottom: var(--border-subtle);
}

.site-nav-panel__link:hover,
.site-nav-panel__link:focus-visible {
  color: var(--kuneo-blue);
}

/* The current page (or section) in the mobile panel: Kuneo Blue text and a
   blue rule in place of the hairline, so it is not marked by colour alone. */
.site-nav-panel__link[aria-current] {
  color: var(--kuneo-blue);
  border-bottom-color: var(--kuneo-blue);
}

/* The action is separated from the list by the space the list left over, not
   by a margin that would collapse on a short screen. */
.site-nav-panel__cta {
  width: 100%;
  flex: none;
  margin-top: auto;
}

/* ---- Breakpoint: collapse nav below 1024px -------------------------- */
@media (max-width: 1023px) {
  .site-nav,
  .site-header__cta {
    display: none;
  }

  .site-header__menu {
    display: inline-flex;
  }

  .site-header__inner {
    min-height: var(--header-h-mobile);
    grid-template-columns: 1fr auto;
    gap: var(--space-4);
  }

  /* THE MARK DOES NOT SHRINK, THE BAR DOES.
     --logo-box-h is the height at which the wordmark's INK measures the brand
     guideline's 120px floor (measured in the browser: 121px of ink inside a
     190x104px box). So the box stays 104px and bleeds its transparent padding
     past the 64px bar symmetrically instead — the same negative-margin
     technique the desktop bar already uses.

     THE BLEED MUST NOT EAT THE PAGE. The img's box is 104px tall, so its
     bottom 20px would hang over the content below the bar and — because an
     image is a replaced element and captures pointer events across its whole
     box, transparent padding included — swallow the first 20px of taps on
     whatever the page puts there (measured: elementFromPoint at y=68..83 under
     the bar returned IMG, not the hero). Two rules close it:
       · the anchor is pinned to the bar's own height, so its hit area stops
         where the bar stops;
       · the img itself is inert, so its overflowing half cannot intercept.
     The ink stays fully visible: it occupies the 35px centred band of the box,
     which at a -20px offset lands between y=14.5 and y=49.5 — inside the bar. */
  .site-header__brand {
    display: flex;
    align-items: center;
    height: var(--header-h-mobile);
  }

  .site-header__brand img {
    height: var(--logo-box-h);               /* box keeps the mark ≥120px wide */
    width: auto;
    margin-block: calc((var(--header-h-mobile) - var(--logo-box-h)) / 2);
    pointer-events: none;
  }

  /* No-JS fallback (redesign §33): the hamburger needs navigation.js, so
     without JS show the primary nav inline instead of an inert button. The
     panel stays hidden — its content duplicates the inline list. */
  html:not(.js) .site-header__menu {
    display: none;
  }

  html:not(.js) .site-nav {
    display: block;
    grid-column: 1 / -1;
    justify-self: stretch;
  }

  html:not(.js) .site-nav__list {
    flex-wrap: wrap;
    gap: var(--space-2) var(--space-6);
    padding-bottom: var(--space-4);
  }
}

@media (min-width: 1024px) {
  .site-nav-panel {
    display: none !important;
  }
}

/* ==========================================================================
   §14 Footer — Brand Ink, 4 zones, legal row = © year entity only (v1)
   ========================================================================== */

.site-footer {
  background-color: var(--brand-ink);
  color: var(--white);
  /* TRIMMED. The footer measured 656px tall at 1440x900, which the maintainer
     read as "MUY grande". Most of that height was structural padding rather
     than content: 80px above, 48px below the grid, 32px at the bottom, plus
     8px of margin under every one of the ~20 links. Each value comes down
     without touching the type or the 44px target floor. */
  padding-top: 56px;
  padding-bottom: 24px;
}

.site-footer__main {
  display: grid;
  grid-template-columns: repeat(12, minmax(0, 1fr));
  gap: var(--grid-gutter);
  padding-bottom: var(--space-8);
}

/* 12-column footer grid, now with FIVE zones (Careers added):
   brand 3 / capabilities 2 / company 2 / careers 2 / connect 3 = 12.
   The brand column shrank from 5 to 3 to make room; its support line already
   wraps inside its own max-width, so nothing reflows awkwardly. */
.site-footer__brand {
  grid-column: span 3;
}

.site-footer__nav {
  grid-column: span 2;
}

.site-footer__connect {
  grid-column: span 3;
}

.site-footer__brand img {
  width: 240px;                            /* FR-03: raised above §14.2's 230px ceiling */
  height: auto;
  margin-bottom: var(--space-4);
}

.site-footer__line {
  font-size: var(--fs-body-lg);
  font-weight: 600;
  color: var(--white);
  margin-bottom: var(--space-2);
}

.site-footer__support {
  font-size: var(--fs-small);
  color: var(--gray-300);
  max-width: 34ch;
}

.site-footer__heading {
  font-size: var(--fs-small);
  font-weight: 600;
  letter-spacing: var(--tracking-overline);
  text-transform: uppercase;
  color: var(--gray-300);
  margin-bottom: var(--space-4);
}

.site-footer__heading a {
  color: var(--gray-300);
  text-decoration: none;
  /* EXPANDED TARGET, ZERO LAYOUT COST.
     The heading link's own box is 17px tall (14px type at the heading's line
     box), which fails WCAG 2.2 AA Target Size (Minimum) at 24px. Growing the
     box instead would push the whole footer down and drag the rule that
     separates the heading from its list out of place.
     A pseudo-element is the right tool: it joins the link's hit area without
     entering layout at all. 44px is centred on the link, so 13.5px extend above
     and below. Measured free space below is 15px (the gap to the `<ul>`), so
     the expanded area stops 1.5px short of the first list link — no collision.
     Above, the heading is the first element of its column at every breakpoint,
     and the element it reaches (the footer grid gap) carries no link. */
  position: relative;
}

.site-footer__heading a::after {
  content: "";
  position: absolute;
  top: 50%;
  left: 0;
  width: 100%;
  height: 44px;
  transform: translateY(-50%);
}

.site-footer__heading a:hover,
.site-footer__heading a:focus-visible {
  color: var(--white);
}

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

/* TIGHTER RHYTHM. 44px of target plus 8px of margin put 52px between two
   consecutive links, which is what made the two long columns read as airy and
   pushed the whole footer down (maintainer: "el espacio entre elemento y
   elemento no haya tanto espacio"). The target floor is a HIT AREA, not a
   visual gap, so the margin is pulled back: the links stay tappable at 44px
   while the visible rhythm closes toward the type's own leading. */
.site-footer__nav li {
  margin-bottom: calc(var(--space-2) * -1);
}

/* FR-03: scoped to list links only — the Capabilities heading link must keep
   the heading's 14px line box + gray-300 color (root cause of the
   Capabilities/Company/Connect misalignment). */
.site-footer__nav li a {
  display: inline-flex;
  align-items: center;
  min-height: 44px;                        /* WCAG 2.2 AA target */
  font-size: var(--fs-small);
  color: var(--white);
  text-decoration: none;
}

/* A SHORT LABEL IS STILL A CONTROL (§38), AND ONLY ON TOUCH.
   "Work" measures 37px wide and "About" 43px — a two-word link's box is its
   text plus padding, so the WIDTH floor is missed even though the height is
   already 44px. The reach is extended with a pseudo-element instead of
   `min-width`, which on an inline-flex item would widen the box and shift the
   footer's columns out of alignment for a purely invisible gain.

   WHY THIS IS INSIDE A MEDIA QUERY: `position: relative` on the link is a
   computed-style change that shows up on every footer link at every width —
   the desktop fingerprint reported it 39 times. The reach is a touch concern,
   and a mouse already has a precise pointer, so the desktop footer stays
   byte-identical to what it was. */
@media (max-width: 1023px) {
  .site-footer__nav li a {
    position: relative;
  }

  .site-footer__nav li a::after {
    content: "";
    position: absolute;
    top: 50%;
    left: 50%;
    width: max(100%, 44px);
    height: 100%;
    min-height: 44px;
    transform: translate(-50%, -50%);
  }
}

.site-footer__nav li a:hover,
.site-footer__nav li a:focus-visible {
  color: var(--blue-300);
  text-decoration: underline;
}

/* ---- The two "explore" links: cyan + a drawn arrow ---------------------
   The maintainer asked for "Explore all our capabilities" and "Explore the
   talent network" to read as an invitation rather than as two more list rows:
   "en un color celestito con una flechita, o un boton. Lo que quede mejor".
   The arrow reuses the vocabulary the site already has (a 2px shaft whose head
   is a rotated border corner), and the colour is `--blue-300` — the light
   accent already established for text on Ink, so nothing new is invented. It
   is a link, not a filled button: a button here would compete with the Connect
   action and re-create the double-title problem this pass fixes. */
.site-footer__nav li a.site-footer__explore {
  color: var(--blue-300);
  font-weight: 600;
  /* ONE LINE. With the arrow gone the label is the whole control, and the
     maintainer asked to shorten it so it fits a single row ("si se puede
     recortar para que entre en una sola linea, mejor"). The labels are short
     enough for the column now; `white-space: nowrap` makes that a guarantee
     rather than a bet on the column width at every viewport. */
  white-space: nowrap;
}

.site-footer__nav li a.site-footer__explore:hover,
.site-footer__nav li a.site-footer__explore:focus-visible {
  color: var(--blue-200);
  text-decoration: none;
}


/* Connect links ship only when real URLs are configured (no placeholders). */
.site-footer__connect ul {
  list-style: none;
  padding: 0;
  margin: 0;
}

.site-footer__connect a {
  display: inline-flex;
  align-items: center;
  min-height: 44px;
  font-size: var(--fs-small);
  color: var(--white);
  text-decoration: none;
}

.site-footer__connect a:hover,
.site-footer__connect a:focus-visible {
  color: var(--blue-300);
  text-decoration: underline;
}

/* v2 §20 — while no real social/contact URL exists, the Connect zone carries
   a legitimate internal action instead of a dead column. When a URL is
   configured, js/site-config.js reveals the list and hides this block.

   THE BUG THIS FIXES (maintainer: "que esta mal el estilo y como que algo se
   ha roto ahi"): `.site-footer__connect a` above is a TWO-class selector, so it
   outranked this one-class rule and forced `display: inline-flex` + `align-
   items: center` onto the action. The label and the line then laid out SIDE BY
   SIDE and overlapped (measured: label 487..523, line 470..540 — a 53px
   collision in an 86px box). The action is a two-line stack, so it must win.
   Selector raised to match the connect-link rule's weight. */
.site-footer__connect .site-footer__action {
  display: grid;
  gap: var(--space-2);
  text-decoration: none;
  color: var(--white);
  padding-block: var(--space-2);
  min-height: 0;
  align-items: start;
  max-width: 30ch;
}

/* THE ACTION IS A CONTROL: it needs the 44px floor.
   `min-height: 0` above is deliberate — it stops the connect-link rule from
   stretching this two-line stack — but the box it leaves is 38px (a 22px line
   plus 8px of padding twice), under the touch floor. The height is NOT raised
   with min-height, because that would push the legal row down and change the
   footer's composition to fix something invisible; a pseudo-element joins the
   hit area without entering layout, which is the same technique the footer's
   heading links already use.
   Scoped below 1024px: a mouse has a precise pointer, and the desktop footer
   keeps the exact box it had. */
@media (max-width: 1023px) {
  .site-footer__connect .site-footer__action {
    position: relative;
  }

  .site-footer__connect .site-footer__action::after {
    content: "";
    position: absolute;
    left: 0;
    top: 50%;
    width: 100%;
    height: 44px;
    transform: translateY(-50%);
  }
}

/* The action carries NO label of its own any more. The zone's "Connect"
   heading is the only heading, and the action is a quiet line under it — the
   previous pairing of a "Connect" heading with a "Start a conversation" label
   read as two competing titles. */

.site-footer__action-line {
  font-size: var(--fs-body);
  font-weight: 600;
  line-height: 1.35;
  color: var(--blue-300);
  white-space: nowrap;
  transition: color var(--duration-fast) var(--ease-standard);
}

.site-footer__action:hover .site-footer__action-line,
.site-footer__action:focus-visible .site-footer__action-line {
  color: var(--blue-200);
  text-decoration: underline;
}

/* Legal row: © {YEAR} {LEGAL_ENTITY_NAME} only in v1 (SF-7; no legal
   page routes ship until counsel approves content). */
.site-footer__legal {
  border-top: 1px solid rgba(255, 255, 255, 0.14);
  padding-top: var(--space-6);
  display: flex;
  flex-wrap: wrap;
  gap: var(--space-4) var(--space-6);
}

.site-footer__legal p {
  font-size: var(--fs-small);
  color: var(--gray-300);
  max-width: none;
}

/* The corporate note. Kuneo is the brand; the legal entity behind it is
   GDCR Technology LLC. The copyright names the BRAND because that is what the
   site is, and this line states the relationship plainly so the record is
   accurate without turning the footer into a legal block. It sits quieter than
   the copyright itself. */
.site-footer__legal-note {
  color: var(--gray-400);
}

/* Privacy and Terms links, at the end of the legal row. */
.site-footer__legal-links {
  display: flex;
  flex-wrap: wrap;
  gap: var(--space-2) var(--space-6);
  margin-inline-start: auto;
}

.site-footer__legal-links a {
  font-size: var(--fs-small);
  color: var(--gray-300);
  text-decoration: none;
}

.site-footer__legal-links a:hover,
.site-footer__legal-links a:focus-visible {
  color: var(--white);
  text-decoration: underline;
}

/* ---- Responsive footer (§14.6) --------------------------------------- */
/* Five zones do not fit a 3-across tablet grid, so from 1023px down the
   footer becomes a 2-column grid and the brand spans both. */
@media (max-width: 1023px) {
  .site-footer {
    padding-top: 56px;                     /* §14.1 mobile */
    padding-bottom: 24px;
  }

  .site-footer__main {
    grid-template-columns: repeat(2, minmax(0, 1fr));
    row-gap: var(--space-8);
  }

  .site-footer__brand {
    grid-column: span 2;
    margin-bottom: var(--space-2);
  }

  .site-footer__brand img {
    width: 180px;                          /* min logo width (§14.2) */
  }

  .site-footer__nav,
  .site-footer__connect {
    grid-column: span 1;
  }
}

@media (max-width: 599px) {
  .site-footer__main {
    grid-template-columns: 1fr;
  }

  .site-footer__brand,
  .site-footer__nav,
  .site-footer__connect {
    grid-column: span 1;
    margin-bottom: var(--space-2);
  }
}

/* ---- Footer tidy (final layer) ------------------------------------------
   One quiet system: four equal groups beside the brand, one heading style,
   one link style (muted, white on hover), one accent style for the three
   "go further" links, one slim legal row. Overrides the rules above. */
.site-footer {
  padding-top: 64px;
  padding-bottom: 20px;
}

.site-footer__main {
  column-gap: var(--grid-gutter);
  row-gap: var(--space-8);
  padding-bottom: var(--space-12);
}

.site-footer__brand {
  grid-column: span 4;
}

.site-footer__nav,
.site-footer__connect {
  grid-column: span 2;
}

.site-footer__brand img {
  width: 200px;
  margin-bottom: var(--space-4);
}

.site-footer__line {
  font-size: var(--fs-body);
  font-weight: 600;
  line-height: 1.4;
  max-width: 26ch;
  margin-bottom: var(--space-2);
}

.site-footer__support {
  font-size: var(--fs-small);
  line-height: 1.55;
  max-width: 36ch;
}

.site-footer__heading {
  font-size: 0.75rem;
  line-height: 1.4;
  letter-spacing: 0.12em;
  margin-bottom: var(--space-3);
}

.site-footer__nav li,
.site-footer__connect li {
  margin-bottom: calc(var(--space-2) * -1);
}

.site-footer__nav li a,
.site-footer__connect li a {
  display: inline-flex;
  align-items: center;
  min-height: 44px;
  font-size: var(--fs-small);
  font-weight: 400;
  line-height: 1.4;
  color: var(--gray-300);
  text-decoration: none;
}

.site-footer__nav li a:hover,
.site-footer__nav li a:focus-visible,
.site-footer__connect li a:hover,
.site-footer__connect li a:focus-visible {
  color: var(--white);
  text-decoration: underline;
}

/* The three "go further" links share one accent style. */
.site-footer__nav li a.site-footer__explore,
.site-footer__connect .site-footer__action-line {
  font-size: var(--fs-small);
  font-weight: 600;
  line-height: 1.4;
  color: var(--blue-300);
  white-space: nowrap;
}

.site-footer__nav li a.site-footer__explore:hover,
.site-footer__nav li a.site-footer__explore:focus-visible,
.site-footer__action:hover .site-footer__action-line,
.site-footer__action:focus-visible .site-footer__action-line {
  color: var(--blue-200);
}

.site-footer__connect .site-footer__action {
  padding-block: var(--space-3);
  max-width: 24ch;
}

.site-footer__legal {
  flex-wrap: nowrap;
  align-items: baseline;
  gap: var(--space-2) var(--space-6);
  padding-top: var(--space-4);
}

.site-footer__legal p,
.site-footer__legal-links a {
  font-size: 0.8125rem;
  line-height: 1.5;
}

.site-footer__legal-note {
  color: var(--gray-400);
}

@media (min-width: 1024px) and (max-width: 1199px) {
  .site-footer__brand {
    grid-column: span 12;
  }

  .site-footer__nav,
  .site-footer__connect {
    grid-column: span 3;
  }
}

@media (max-width: 1023px) {
  .site-footer__main {
    grid-template-columns: repeat(2, minmax(0, 1fr));
  }

  .site-footer__brand {
    grid-column: span 2;
    margin-bottom: 0;
  }

  .site-footer__nav,
  .site-footer__connect {
    grid-column: span 1;
  }
}

@media (max-width: 599px) {
  .site-footer {
    padding-top: 48px;
  }

  .site-footer__nav li a.site-footer__explore,
  .site-footer__connect .site-footer__action-line {
    white-space: normal;
  }

  .site-footer__main {
    grid-template-columns: repeat(2, minmax(0, 1fr));
    column-gap: var(--space-4);
    padding-bottom: var(--space-8);
  }

  .site-footer__brand {
    grid-column: span 2;
    margin-bottom: 0;
  }

  .site-footer__nav,
  .site-footer__connect {
    grid-column: span 1;
    margin-bottom: 0;
  }

  .site-footer__legal {
    flex-wrap: wrap;
    flex-direction: column;
    align-items: flex-start;
  }

  .site-footer__legal-links {
    margin-inline-start: 0;
  }
}

/* ==========================================================================
   Live shared components still used by pages (kept after the v2 cleanup —
   everything else in this file belonged to the retired secondary-page
   design system and was removed; see Web/…_v2_FINAL.md §29 PASS 10).
   ========================================================================== */

/* FAQ accordion (§16) — native <details>/<summary>, keyboard accessible
   with zero JS; aria-expanded synced by main.js. */
.faq__list {
  max-width: 980px;
}

.faq__item {
  border-top: 1px solid var(--gray-200);
}

.faq__item:last-child {
  border-bottom: 1px solid var(--gray-200);
}

.faq__question {
  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: var(--space-4);
  min-height: 56px;
  padding-block: var(--space-4);
  cursor: pointer;
  font-size: var(--fs-h4);
  font-weight: 600;
  list-style: none;
}

.faq__question::-webkit-details-marker {
  display: none;
}

.faq__question::marker {
  content: "";
}

.faq__question:hover {
  color: var(--kuneo-blue);
}

.faq__question svg {
  flex: none;
  color: var(--kuneo-blue);
  transition: transform var(--duration-fast) var(--ease-standard);
}

.faq__item[open] .faq__question svg {
  transform: rotate(180deg);
}

.faq__answer {
  padding-bottom: var(--space-6);
  color: var(--gray-600);
  max-width: 62ch;
}

/* Contact form helpers still referenced by the calm form. */
.form-card__help {
  font-size: var(--fs-small);
  color: var(--gray-500);
  margin-top: var(--space-2);
}

.form-actions {
  margin-top: var(--space-8);
}

.form-actions .btn {
  width: 100%;                       /* §20.7: full width preferred */
}

.form-privacy {
  font-size: var(--fs-small);
  color: var(--gray-500);
  margin-top: var(--space-4);
  max-width: 52ch;
}

.form-status {
  min-height: 1.5em;
  margin-top: var(--space-4);
}

/* §20.9 error summary — top-of-form role=alert with anchor links to each
   invalid field (built by js/contact-form.js). */
.form-error-summary {
  border: 1px solid var(--error);
  border-radius: var(--radius-control);
  padding: var(--space-4) var(--space-6);
  margin-bottom: var(--space-6);
  font-size: var(--fs-small);
}

.form-error-summary__title {
  margin: 0 0 var(--space-2);
  font-weight: 600;
  color: var(--error);
}

.form-error-summary ul {
  list-style: none;
  margin: 0;
  padding: 0;
  display: grid;
  gap: var(--space-1);
}

.form-error-summary a {
  color: var(--error);
  font-weight: 600;
  text-decoration: underline;
}

/* §20.8 success panel — the aria-live status region becomes the confirmation
   panel (js/contact-form.js replaces the form body with it, CF-7). */
.form-status--success {
  border: 1px solid var(--gray-200);
  border-radius: var(--radius-card);
  background-color: var(--gray-050);
  padding: var(--space-6);
}

.form-status--success:focus-visible {
  outline: var(--focus-ring);
  outline-offset: var(--focus-offset);
}

.form-success__title {
  font-size: var(--fs-h4);
  font-weight: 700;
  color: var(--brand-ink);
  margin-bottom: var(--space-2);
}

.form-success__next {
  margin-top: var(--space-4);
}

/* Direct-email line (spec §13.11), reused by the homepage exit scene where
   the block sits on Brand-Kuneo Blue. Rendered only when a contact address is
   configured — site-config.js unhides it; never a placeholder in the DOM. */
.final-cta__email {
  font-size: var(--fs-small);
  color: var(--white);
  max-width: none;
  margin-top: var(--space-6);
}

.final-cta__email a {
  display: inline-flex;
  align-items: center;
  min-height: 44px;                        /* WCAG 2.2 AA target */
  color: var(--white);
  font-weight: 600;
  text-decoration: underline;
  text-underline-offset: 3px;
}

.final-cta__email a:hover,
.final-cta__email a:focus-visible {
  text-decoration-thickness: 2px;
}/* ---- FAQ progressive disclosure ("show more") ---------------------------
   The list opens with four answers and a quiet control that reveals the rest.
   The hidden items ship in the DOM with `hidden` — real HTML, not injected —
   so crawlers, no-JS visitors and assistive tech all still receive every
   answer; `hidden` only removes them from the visual flow and the tab order
   until the reader asks for them. Styled as a text control with the same
   chevron the questions use, so it belongs to the accordion rather than
   reading as a generic button. */
.faq__more {
  display: inline-flex;
  align-items: center;
  gap: var(--space-2);
  min-height: 44px;
  margin-top: var(--space-6);
  font-size: var(--fs-small);
  font-weight: 600;
  color: var(--kuneo-blue);
}

.faq__more:hover {
  text-decoration: underline;
  text-underline-offset: 3px;
}

.faq__more-icon {
  flex: none;
  width: 18px;
  height: 18px;
  transition: transform var(--duration-fast) var(--ease-standard);
}

.faq__more[aria-expanded="true"] .faq__more-icon {
  transform: rotate(180deg);
}

@media (prefers-reduced-motion: reduce) {
  .faq__more-icon {
    transition: none;
  }
}