/*
 * header-inheritance.css — site-owned inheritance guard for the shared header.
 * Loaded AFTER header/v1/header-dark.css. S1-06.
 *
 * ===========================================================================
 * WHAT THIS IS
 * ===========================================================================
 * The header bar is a FIXED-HEIGHT box (33px desktop / 44px ≤850px) that CANNOT
 * GROW. Any inherited property that changes glyph metrics or run position can
 * therefore overflow or clip it. That is the vendor's own stated reason for
 * pinning `line-height: normal` at its roots, and it is this file's INCLUSION
 * CRITERION: pin an inherited property iff it can change glyph metrics or run
 * position inside a box that cannot grow.
 *
 * Every rule here is a NO-OP TODAY — galciv4 ships no other site CSS, so
 * nothing is currently leaking in. This file is the BOUNDARY CONTRACT for when
 * the content ports land and site-wide typography arrives. Values are `initial`
 * rather than literals precisely so this file changes NO current rendering; it
 * only closes the path.
 *
 * ===========================================================================
 * WHY THIS IS LOADED AFTER header-dark.css
 * ===========================================================================
 * These pins target the vendor's own root selectors at EQUAL specificity
 * (0,1,0). At equal specificity source order decides, so this sheet must come
 * second. It does, in _Layout.cshtml.
 *
 * These root pins CANNOT break legitimate vendor styling: every vendor rule
 * that sets one of these properties is a DESCENDANT selector at specificity
 * ≥(0,2,0) and therefore wins. (Note header-dark.css:102 uses
 * `:where(.stardock-header, .header-container) .submenulong > .actions`;
 * `:where()` contributes 0, but `.submenulong` + `.actions` still yields
 * (0,2,0) — safe.)
 *
 * Both root classes are listed because `variant` selects which one is emitted:
 * light → `.stardock-header`, dark → `.header-container`. galciv4 is dark, but
 * pinning both costs nothing and survives a variant change.
 *
 * ===========================================================================
 * DELIBERATE EXCLUSIONS — these are decisions, not oversights
 * ===========================================================================
 * ALREADY OWNED BY THE VENDOR, do not second-source:
 *   `line-height`  — vendor pins `normal` at both roots.
 *   `color`        — vendor pins `#fdfdfd` at both roots.
 *   `font-family`  — each root declares its own.
 *   `font-size`    — each root declares its own.
 * Re-pinning these would be a second opinion fighting the vendor on every
 * future `v1` change. The vendor has already closed them.
 *
 * NOT PINNED ON PURPOSE:
 *   `text-shadow`, `font-variant`, and other purely cosmetic inherited
 *   properties. They cannot reflow a box that cannot grow, so they fail this
 *   file's inclusion criterion. Pinning them would be guessing rather than
 *   measuring.
 */

.stardock-header,
.header-container {
    /*
     * Measured as UNPINNED in header-dark.css (occurrences at either root: 0
     * for each of the four below). Each changes glyph advance or run position
     * inside the fixed-height bar.
     */
    letter-spacing: initial;
    word-spacing: initial;
    text-transform: initial;
    font-style: initial;

    /*
     * `text-align` appears 4 times in the vendor sheet, but ALL FOUR are
     * descendant selectors, never a root — so the root is genuinely open.
     * `initial` resolves to `start`, NOT `left`: direction-relative and
     * therefore RTL-safe, and `start` is the UA default the vendor implicitly
     * designed against.
     */
    text-align: initial;

    /*
     * PINNED PER S1-06 AUDIT (MINOR 2). `font-weight` is inherited and changes
     * glyph advance widths, so it meets this file's inclusion criterion exactly
     * as the five above do — it was simply missed the first time, being neither
     * pinned nor recorded as a deliberate exclusion.
     *
     * Verified open at the root: header-dark.css declares `font-weight` 18
     * times (400/500/600), but the two ROOT rules (:568 and :607) declare
     * line-height, color, font-family and font-size and NO font-weight. So a
     * site-wide `body { font-weight: 600 }` would inherit straight into the bar.
     *
     * Exposure today is genuinely limited — the nav anchors set their own
     * `font-weight: 400` at descendant specificity and are unaffected — which
     * is why this is a MINOR and not a defect. It is pinned anyway because the
     * cost is one line and the alternative is leaving a hole in a sheet whose
     * entire purpose is to have no holes.
     */
    font-weight: initial;
}