/* ==========================================================================
   web/src/styles/pages/support.css

   The support page's own slot: the lead line under the H1, the plain list under "What to
   include", and the FAQ definition list. Nothing here is a second copy of a rule page.css or
   components.css already owns; every value is a token from tokens.css, every gap a step of the
   ladder page.css states (8 inside one thing, 24/16 within a group, 48/32 between groups).

   WHY A LIST AND A DEFINITION LIST, NOT A THIRD REPEAT OF HEADING-THEN-PARAGRAPH. The old
   `section__title` build put every part of this page in one shape, five times running, which is
   the exact "heading over a paragraph over nothing but more paragraph" pattern visual-rhythm
   rule 4 and the corporate-website test both name. "What to include" is a short checklist, so it
   is one; "Questions people ask" is genuinely a term and its answer, so it is a <dl>. Two shapes
   below the masthead, on a page whose content only ever needed two.

   THE MAIL LINK STAYS AN ORDINARY LINK, checked and left unchanged 2026-09-04. `sup.email.lead`
   in support.html carries no class, from this file, components.css's `.link`, or the app's own
   circular-control face, that turns it into a warm-lit control: plain underlined text in the
   page's ink, `a` from base.css, nothing added here. The offer to light it was raised in a status
   update on a different page (a lit-control option named while reporting the Safety page, ts
   1788512978) and settled against the Support page (founder call, Pin, founder-nudge thread
   1788329584.269439 at ts 1788516151: "No need to make support link the lit control.";
   `web/DECISIONS.md` D114, which he ruled on the Safety page; this page lights nothing for the same reason).

   Loaded by: web/scripts/build-site.mjs, into src/pages/support.html alone.

   Connected files:
     - web/src/pages/support.html      (the markup these rules style)
     - web/src/styles/page.css         (the frame, the masthead, the column, the ladder)
     - web/src/styles/tokens.css       (every value spent below)
     - web/src/styles/base.css         (the bare h2, p, ul and dl this file does not restate)
   ========================================================================== */

/* "What to include": a plain checklist. No browser marker: DESIGN.md 5.4 rule 7 bans dots, discs
   or small circles anywhere on the site outside the six controls around the object, and the
   browser's disc is exactly that. The three lines hang on the same left keyline as every other
   line on the page instead. The gap between items is the ladder's finest step, 8, because these
   three lines are one thought split three ways rather than three separate groups. */
.sup-list {
  list-style: none;
  padding-left: 0;
}

/* The FAQ. Its spacing is the shell's .page-defs, the definition-list shape every page shares: a
   term and its own statement 8 apart, one entry to the next at the served-block step. What is left
   here is the term's own register, which is this page's choice: a question is read, so it takes the
   reading face at the H3 role rather than the masthead's uppercase label register that the safety
   page's ledger of terms uses. */
.sup-faq__item dt {
  font-family: var(--font-text);
  font-weight: var(--weight-h3);
  font-size: var(--size-h3);
  line-height: var(--line-h3);
  color: var(--hotpot-text-primary);
}

.sup-faq__item dd {
  font-size: var(--size-body);
  line-height: var(--line-body);
}