/*
 * Takes back the two brand declarations the previous theme's bundle overrides.
 *
 * WHY THIS FILE EXISTS. On a page that still carries an unported legacy widget
 * or hand-typed previous-theme markup, inc/legacy.php re-enqueues the previous
 * theme's app.min.css - and WordPress prints it AFTER this theme's own
 * stylesheet. One rule in there is `body { font-family: "Instrument Sans";
 * font-size: 16px; overflow-x: hidden; color: #000; font-weight: 400 }`, which
 * ties with this theme's `body { ... }` on specificity and wins on source
 * order. The visible result: every element that inherits its colour renders
 * PURE BLACK instead of the brand ink.
 *
 * Measured on staging 2026-09-05, deployed, with the bundle loaded: on
 * /our-impact/impact-reports/impact-report-2025/ 1013 of 1767 elements computed
 * `rgb(0, 0, 0)` where the rest of the site computes `#362C2C`, and on
 * /research/sector-reports/health-sector-report/ it was 779 of 1577. Forty
 * published pages load that bundle, so this was the largest single group of
 * off-brand text left on the site - and invisible to a colour sweep of stored
 * content, because nothing is stored wrong. The wrong value is computed.
 *
 * WHY IT RESTORES ONLY COLOUR AND FONT STACK, and this is the whole design.
 * Reordering the two stylesheets would fix the colour too, and was measured
 * first: on the report pages it is clean (content geometry unchanged, zero
 * backgrounds changed), but on the 34 campaign pages that carry hand-typed
 * Bootstrap markup it also hands this theme's margins the win, and
 * /gs25/ lost 169px of height. That is a visual change to live campaign pages
 * that nobody asked for. Colour and font-family cannot move a box, so taking
 * back exactly those two takes the defect and none of the risk. Measured after:
 * /gs25/ 4877px before and after, zero elements moved; the health sector report
 * 12422px before and after, one inline footer link 1.9px narrower because its
 * arrow glyph now falls back through this theme's stack rather than the UA's.
 *
 * `font-size` is deliberately NOT restored even though the bundle sets it: this
 * theme's --b26-size-body is 1rem, which computes to the same 16px, so
 * restoring it would be a no-op that looked like a decision. `overflow-x` and
 * `font-weight` are left alone for the same reason - they already agree.
 *
 * The selector out-specifies the rule it answers (0,1,1 against 0,0,1), so it
 * wins wherever it is printed. The enqueue still declares the bundle as a
 * dependency, so the order is stated rather than relied upon.
 */

body.b26-page {
	background: var(--b26-paper);
	color: var(--b26-ink);
	font-family: var(--b26-font-body);
}

/*
 * THREE MORE DECLARATIONS, added 2026-09-06 on the same reasoning.
 *
 * Sandro reported the previous brand's red as the thing he notices most across
 * the site. It has one dominant cause and it is this bundle. Measured in Chrome
 * on deployed staging, /gs24-lg/, with the bundle loaded: app.min.css declares
 * `a { color: rgb(230, 76, 59) }` - the previous accent #E64C3B - while this
 * theme declares `a { color: inherit }` in app.css. Both are (0,0,1) and the
 * bundle is printed later, so the bundle wins on every page that loads it. A
 * sweep of the rendered site put that at 22 published pages.
 *
 * The bundle takes the blockquote colour (#E64C3B again) and the rule colour
 * (#BBBDBF) the same way, by bare element selector, so they are taken back in
 * the same edit rather than left to be found again later.
 *
 * BACKGROUND is added to the rule above for the same reason and with the same
 * limits. The bundle sets `body { background: #fff }` - pure white, which is
 * not a colour the 2026 brand contains at all; its white is #FBFBFB and its
 * page ground is Paper. Measured on /gs24-lg/: pure white covered 20.1% of the
 * painted area, from that one rule, against this theme's own
 * `body { background: var(--b26-paper) }` in 20-base.css. Checked before
 * writing this: `background(-color): #fff` appears in the bundle on `body` and
 * on a handful of form controls and one overlay, so a single body rule takes
 * back effectively all of it and no card loses its own white.
 *
 * All four stay inside this file's founding constraint - colour and font stack
 * only, never a property that can move a box. `hr` gets border-top-COLOR and
 * not `border-top`, so the 1px width the bundle sets is untouched.
 *
 * Specificity: (0,1,1) for body and (0,1,2) for the three element rules, each
 * against the bundle's (0,0,1). They win wherever they are printed.
 */

body.b26-page a {
	color: inherit;
}

body.b26-page blockquote {
	color: var(--b26-ink);
}

body.b26-page hr {
	border-top-color: var(--b26-rule);
}