.references-container.section__container {
    width: 100%;
    max-width: var(--container-max-width);
    /* CHR-7 (DONI-571) QA 2026-08-08 — round 2 of this QA item.
     *
     * Round 1 (PR #246) set 24px top / 48px bottom "per Figma" but that was
     * an eyeballed screenshot read, and it was wrong on both edges. The
     * authoritative source is the Section's own Figma AUTO-LAYOUT frame,
     * read via get_design_context on 29999:57084 (desktop) — its className
     * is `... overflow-clip pb-[24px] px-[120px] ...` with NO `pt-*` class
     * at all. Re-verified identically on mobile (29999:57096 > Section,
     * 0:245): get_metadata shows the ISI instance's bottom edge, the
     * Section's top edge and the Footer's top edge all EXACTLY flush with
     * the Section's own box (0 gap at both frame boundaries) on both
     * breakpoints, and the SubHead text node leaves exactly 24px of
     * trailing space before the Section's bottom edge on both (232-208=24
     * desktop, 822-798=24 mobile) — none at the top (SubHead starts at
     * y=0 in both).
     *
     * The "24" visual gap above the reference list that round 1 measured is
     * real, but it is already supplied entirely by `.isi-footer-content`'s
     * own bottom padding (CHR-3/DONI-564's `.isi-footer-content { padding:
     * 24px }` in css/base/isi-tray.css) — this container does not need to
     * add a second 24px on top of it. Confirmed by pixel-scanning the MOA
     * screenshot: charcoal text ink starts ~6px after the Section's own box
     * edge (ordinary line-height leading), not 24px after it.
     *
     * Horizontal gutters stay on --container-padding (resolves to 0 at
     * >=1250px — the 120px gutter at 1440 comes from this element's own
     * max-width auto-centering inside a 1440 viewport, not from padding). */
    padding: 0 var(--container-padding) 24px;
    margin: 0 auto;

    p {
        /* CHR-7 (DONI-571). Was a hardcoded `#1D2D3A`. `--color-charcoal`
           is declared as exactly `#1d2d3a` (variables.css:24), so this is
           render-neutral — the same discipline FND-6 applied to 217
           hardcoded corals. */
        color: var(--color-charcoal);
        font-family: var(--font-family-primary);

        /* 🔴 `16px` and `normal` are deliberately NOT tokenised, and that
           is the opposite of the line above.
           The nearest tokens hold DIFFERENT values:
             --font-size-base     clamp(1rem, 1vw, 1.125rem)  = 16-18px fluid
             --line-height-normal 1.5                          = 24px here
           Agenda's `normal` computes to about 1.136, so adopting either
           would visibly re-flow a reference list. That is claim-to-citation
           copy, so a re-flow is a change to regulated presentation and
           needs a design answer, not a tidy-up. Left as measured, and
           recorded in docs/hcp-nxt/reference-formatting-policy.md. */
        font-size: 16px;
        line-height: normal;
        margin: 0;

        &.homepage-references {
            font-size: 16px;
        }
    }
}

/* No mobile override needed. The 0/24 vertical padding above was measured
 * on BOTH the desktop (29999:57084) and mobile (29999:57096) Section frames
 * and is identical on both — see the comment above. --container-padding
 * already carries its own responsive step for the horizontal gutter
 * (variables.css), so nothing here is breakpoint-specific. */