/* Shared inline CSS extracted from the 25 insights article pages (Task 11).
 *
 * Every insights page carried its own copy of the base block below,
 * byte-identical or near enough that the differences were minification noise
 * rather than content. Two pages keep their own residual inline <style>
 * because their layout genuinely differs: insights/index.html (the hub, a
 * different template) and insights/uk-tax-rates-2026-27/index.html (a rates
 * table page with its own :root override), and both link this file too, for
 * the parts of the base block they still share.
 *
 * The Newsreader weight pin (h1,h2,.faq h3{font-weight:600}) used to be a
 * SEPARATE <style> block that scripts/inject-chrome.js wrote INSIDE the
 * chrome-head markers on every insights page (renderHead's old WEIGHT_PIN).
 * It moved here because 25 copies of it inline (2600 bytes) alone busted this
 * family's byte ceiling, which was 2048 at the time and is 1024 since the
 * ceilings were lowered to the measured figures on 2026-09-02; see the comment on its old home in
 * inject-chrome.js for the full history. Every insights page already links
 * this file after the head partial and before its own remaining style, if
 * any, so the cascade position that comment cared about (the pin must lose to
 * a page's own explicit heading weight, which only uk-tax-rates-2026-27
 * declares) is unchanged.
 */
h1,h2,.faq h3{font-weight:600}

*{box-sizing:border-box}
body{margin:0;background:var(--paper);color:var(--ink);font-family:'Plus Jakarta Sans',-apple-system,system-ui,sans-serif;line-height:1.6}
main{max-width:46rem;margin:0 auto;padding:4rem 1.5rem}
h1{font-family:Newsreader,Georgia,serif;font-size:2.4rem;line-height:1.15;margin:0 0 1rem}
h2{font-family:Newsreader,Georgia,serif;font-size:1.5rem;margin:2.5rem 0 .75rem}
a{color:var(--orange)}
.byline{color:var(--ink-muted);font-size:.95rem;margin:0 0 2.5rem}
.faq{border-top:1px solid #B3A887;padding-top:1.25rem;margin-top:1.25rem}
.faq h3{font-family:Newsreader,Georgia,serif;font-size:1.15rem;margin:0 0 .4rem}

/* The bare `footer{...}` rule every page carried is NOT reproduced here. It
 * always lost the cascade to chrome.css's `.site-footer{...}` (a class beats
 * a bare element selector regardless of source order), so it painted nothing
 * on any page and dropping it changes no pixel. The same is true of
 * `.footer-wordmark{height:22px;width:auto}` and
 * `.footer-wordmark-link{display:inline-flex}`, both already declared,
 * byte-identical, in assets/chrome.css. The one part of that trio that was
 * NOT redundant is `.footer-wordmark-link{margin-bottom:.75rem}`, which
 * chrome.css deliberately does not carry (see its own comment). Only 16 of
 * the 25 pages painted it, so it is scoped below to a `wm-gap` class each of
 * those 16 pages' <body> now carries (added outside the injector's marked
 * regions, so it costs nothing against inject-chrome.js --check), rather than
 * repeated as a 44-byte inline <style> block 16 times, which alone would have
 * used more than a third of this family's 2048-byte ceiling. */
body.wm-gap .footer-wordmark-link{margin-bottom:.75rem}
