/* v2-overrides.css - scoped repair for the (site) marketing route group.
 *
 * WHY THIS EXISTS
 * The root app/layout.tsx loads Tailwind via src/index.css. Tailwind's Preflight
 * base reset includes `h1,h2,h3,h4,h5,h6 { font-size: inherit; font-weight: inherit; }`,
 * which strips the browser's UA-default bold off headings and lets the body's 400
 * cascade in. site.css gives MOST headings an explicit font-weight through classes
 * (.hero h1, .section-title, .card h3, ...), so those survive Preflight. But a few
 * v2 heading selectors set only size/family and relied on the UA-default bold:
 *   - .hero-split h1  (homepage hero) -> rendered 400 instead of 700
 *   - .value h4       (about page values) -> rendered 400 instead of 700
 *   - the bare h1/h2/h3 base rule in site.css (font-family only, no weight)
 * The standalone reference build has no Tailwind, so its headings stay UA-bold.
 *
 * This file re-asserts the UA-default heading weight that Preflight removed, at the
 * SAME element-level specificity as Preflight. Loaded AFTER site.css in the (site)
 * layout, so it wins the Preflight tie-break; site.css's explicit class/inline
 * weights still win on specificity, so 600-weight headings (.card h3, .tool-card h3,
 * .site-footer h4) and inline-700 pricing FAQ headings are untouched.
 *
 * Values mirror the reference computed styles exactly (h1/h2/h3/h4 = UA bold 700;
 * site.css classes override down to 600 where the design calls for it).
 * Scope: this CSS only loads inside app/(site)/layout.tsx, so the rest of the app
 * (dashboard, VA portal, auth) is unaffected.
 */
h1,
h2,
h3,
h4,
h5,
h6 {
  font-weight: bold;
}