/*
 * pm.header-isolation.css
 *
 * Neutralises the ambient styles THIS SITE imposes on the shared Stardock header.
 *
 * WHY A SECOND PM-OWNED SHEET, NEXT TO pm.header-offset.css
 * --------------------------------------------------------
 * pm.header-offset.css has one job, and its name states it: move this site's own fixed chrome
 * (#nav-menu, #mobilenav, #account-menu) out from under a position:fixed header. That is a
 * GEOMETRY problem, and it changes when the bar's height changes.
 *
 * This file answers a different question: the header renders into the LIGHT DOM (0 attachShadow
 * calls in header.js — verified), so it shares a cascade with politicalmachine2024.css and
 * reset.css, and inherits whatever <body> declares. That is an INHERITANCE problem, and it
 * changes when this site's own typography changes. Different trigger, different lifetime, so
 * a different file — merging them would leave a file called "header-offset" holding colour
 * rules. The cost is one extra <link>; both sheets are under 1KB.
 *
 * WHAT IS ACTUALLY WRONG — measured, not assumed
 * ----------------------------------------------
 * Chromium computed-style diff of all 181 header elements against the package's own reference
 * example (upload/header/examples/dark.html), at 1920/850/390. Structure was identical on both
 * (0 elements added or missing), so every difference below is styling, not markup.
 *
 *   1. text-align — 176 of 181 elements. politicalmachine2024.css:30 declares
 *      `body { text-align: center }`. The package's scoped reset defends `line-height`, `color`
 *      and `box-sizing` on its roots but NOT `text-align`, so `center` inherits through the
 *      whole subtree. Visible: every mega-menu product name, description and "For Home |
 *      For Business" link row renders centred where the reference renders them flush left.
 *      This is the big one.
 *
 *   2. color-scheme — 37 elements, plus ~310 currentColor echoes (border-*-color, caret-color,
 *      outline-color, -webkit-text-fill-color ...) that merely follow them. NOT a cascade fight:
 *      the reference page declares <meta name="color-scheme" content="dark"> (dark.html:8) and
 *      this site declares no colour scheme anywhere, so the UA stylesheet's SYSTEM colours
 *      resolve in light mode instead of dark:
 *          input#search-text / input#nav-trigger   fieldtext   #fff -> #000
 *                                                  field       #3b3b3b -> #fff
 *          35 anchors with no explicit colour       -webkit-link  rgb(158,158,255) -> #0000EE
 *      Visible: the search box is a white rectangle with black text sitting on a 33px dark bar.
 *      `color-scheme` is an inherited property, so declaring it on the root covers the subtree
 *      and cannot reach the rest of the page.
 *
 *   3. Heading typography — the single h2.offscreen. politicalmachine2024.css:1,5,9,13 set the
 *      `font:` shorthand (52/48/33/26px cooper-black-std) on bare h1/h2/h3, and reset.css zeroes
 *      their margins. The header's accessible heading is therefore 48px/400 instead of
 *      19.5px/700. It is parked at left:-9999px so nothing is visibly wrong today, but the
 *      header's markup is driven by a CDN-hosted nav.json that can change WITHOUT a redeploy of
 *      this site, so a heading that becomes visible later would arrive already broken.
 *
 * WHAT IS DELIBERATELY NOT HERE
 * -----------------------------
 * - `-webkit-font-smoothing: antialiased` and 13 `--*` design tokens also differ, but those are
 *   declared by the REFERENCE PAGE's own demo styling, not by the header. header-dark.css
 *   contains 0 var() references. Copying them would be restyling the header to match a demo.
 * - body.has-stardock-header. Excluded by decision on this site; measurement confirms content
 *   already clears the bar. Not reintroduced here.
 * - reset.css's list and block-margin rules. They cannot bite: the header markup contains no
 *   ul, li or p (measured tag inventory: div, input, label, span, a, img, nav, h2, strong, br,
 *   form). `body { line-height: 1 }` cannot bite either — the package already declares
 *   `line-height: normal` on its roots, and a direct declaration always beats inheritance.
 *
 * CASCADE POSITION
 * ----------------
 * Loaded after header-dark.css, so it wins ties on source order. Specificity is chosen to sit
 * BETWEEN this site and the package, never above the package:
 *   - Root rules use `.header-container` (0,1,0). Nothing else declares these on the root.
 *   - Heading rules use `:where(.header-container) h1` (0,0,1) — :where() contributes nothing,
 *     so they tie with the site's bare `h1`/`h2`/`h3` and win only on load order, while still
 *     losing to any class-based rule the package itself may apply to a heading. `revert` rolls
 *     the declaration back to the user-agent origin, which is exactly what the reference gets.
 * Scoped entirely inside .header-container (the dark root) — `.stardock-header`, the LIGHT
 * variant root, is deliberately not matched: `color-scheme: dark` would be wrong there.
 */

.header-container{color-scheme:dark;text-align:start}
:where(.header-container) h1,:where(.header-container) h2,:where(.header-container) h3,:where(.header-container) h4,:where(.header-container) h5,:where(.header-container) h6{font:revert;margin:revert}