/**
 * R3.7A.4A: Expertise-archive-SPECIFIC rules only -- genuine differences from Portfolio/Insights/Team,
 * never duplicated generic behavior (the shared hero/results-shell/card-geometry/card-rhythm/hover
 * contract lives in, and is tested by, the shared `fgma-archive.css`, consumed here unchanged via the
 * generic `.fgma-archive-*` classes). `.fgma-expertise-card`/`.fgma-expertise-card__media` are
 * compounded into the shared card rules for zero-padding/flush-media/Production-derived rhythm and
 * hover (scale + brand-red title) -- nothing about geometry/rhythm/hover needs to be re-declared here.
 * There is deliberately NO `.fgma-expertise-card__meta` class or rule: confirmed live, Production's
 * real Expertise card has no metadata line at all (title only).
 *
 * Grid columns themselves (Production-confirmed: 2 mobile / 3 tablet+desktop, no further breakpoint) are
 * owned natively by each of the two Loop Grid widgets' own Elementor query/layout settings -- never
 * Custom CSS here, exactly like Portfolio/Insights/Team's own grids.
 *
 * The grid GAP is confirmed live to be BYTE-IDENTICAL to Insights' own contract (Production's real class
 * list on both the Practice Area and Specialty grids is `grid-cols-2 gap-x-lg gap-y-xl md:grid-cols-3
 * lg:gap-2xl`) -- this is a genuine match, not a coincidence assumed without checking, so this rule is a
 * direct, byte-identical port of `fgma-insights-archive.css`'s own rule, scoped to Expertise's own
 * results class so it can never leak onto (or be leaked onto by) any other archive.
 */
.fgma-expertise-archive-results .elementor-widget-loop-grid .elementor-grid {
    column-gap: var(--fgma-space-lg);
    row-gap: var(--fgma-space-xl);
}

@media (min-width: 900px) {
    .fgma-expertise-archive-results .elementor-widget-loop-grid .elementor-grid {
        column-gap: var(--fgma-space-2xl);
        row-gap: var(--fgma-space-2xl);
    }
}

/**
 * Media ratio -- confirmed live, Production's own Expertise card frame is `aspect-[3/4]` (portrait),
 * genuinely different from Portfolio's/Insights' own confirmed `3:2` frame (`--fgma-media-ratio`). A
 * plain, dimensionless structural ratio value, mirroring the same "structural keyword, not a hardcoded
 * design value" exemption already established for Team's own `aspect-ratio: 1`.
 *
 * R3.7A.4G fix -- confirmed live, ONE real card ("2026 City of Dallas White Rock Hills Recreation
 * Center Survey", a naturally-landscape 650x433 source) rendered as a landscape frame while adjacent
 * cards with naturally-portrait sources (768x1024) looked correct -- root-caused, not assumed: the
 * shared `.elementor .fgma-archive-card__media img{width:100%;height:100%;object-fit:cover;}` rule
 * (`fgma-archive.css`) sets the img's `height:100%`, but Expertise's own markup nests the `<img>`
 * two levels deeper than Portfolio's/Insights' own media widgets (Chrome placed the
 * `[fgma_expertise_tile_image]` shortcode inside a generic Elementor "Shortcode" widget, wrapping the
 * `<img>` in TWO extra, unstyled `<div>`s -- `.elementor-widget-shortcode` > `.elementor-shortcode`
 * -- neither of which has any height of its own). A percentage `height` only resolves against a
 * PARENT with a definite (non-`auto`) height; since both intermediate wrappers stay `height:auto`,
 * `height:100%` on the `<img>` was invalid and silently ignored, so the browser fell back to the
 * `<img>`'s own intrinsic aspect ratio (from its native `width`/`height` HTML attributes) -- correct-
 * looking only when that intrinsic ratio already happened to be near 3:4, which is why only the one
 * genuinely-landscape source ever visibly broke.
 *
 * R3.7A.4H correction -- the R3.7A.4G fix above (`position:absolute;inset:0` on the `<img>`) traded
 * one confirmed bug for a worse one: confirmed live, EVERY Expertise archive card's tile image
 * (Practice Areas and Specialties alike) started computing/rendering at `height:0` (invisible), not
 * just the one previously-broken Dallas card. Root cause: for an absolutely-positioned descendant's
 * `inset:0` to resolve, its containing block (the nearest `position:relative` ancestor --
 * `.fgma-expertise-card__media` itself) must have a genuinely DEFINITE height at the moment the
 * browser lays out that descendant. `aspect-ratio` on a block box is only ONE valid source of a
 * definite height, and combining it with an absolutely-positioned descendant whose own sizing
 * (`inset:0` from this rule PLUS the shared rule's own separate `width:100%;height:100%`) is action-
 * ably over-constrained (both `height:100%` and `top:0`+`bottom:0` specify the same axis) turned out
 * to be unreliable in practice, not merely a theoretical concern -- confirmed by the real regression.
 * Reverted to plain, unambiguous NORMAL-FLOW sizing instead: the two real, confirmed-present
 * intermediate wrapper `<div>`s Elementor's own Shortcode widget always emits between this frame and
 * the real `<img>` (`.elementor-widget-shortcode` > `.elementor-shortcode` -- confirmed live, re-
 * verified this pass, unchanged since R3.7A.4G) are EACH explicitly given `height:100%`, so the
 * percentage-height chain the shared `.fgma-archive-card__media img{height:100%}` rule already relies
 * on resolves correctly end-to-end, exactly like Portfolio's/Insights' own single-level media widgets
 * already do -- no `position:absolute`, no over-constraint, no aspect-ratio-as-containing-block
 * dependency, and this is durable regardless of aspect-ratio/positioning implementation quirks in any
 * given engine. `overflow:hidden` remains (clips the hover-zoom transform, unrelated to this bug).
 */
.fgma-expertise-card__media {
    aspect-ratio: 3 / 4;
    overflow: hidden;
}

.elementor .fgma-expertise-card__media .elementor-widget-shortcode,
.elementor .fgma-expertise-card__media .elementor-shortcode {
    display: block;
    height: 100%;
}

/**
 * Practice Areas / Specialties tab switcher -- confirmed live, Production's own tab bar is two plain
 * buttons (`data-slug="practice-area"`/`data-slug="specialty"`) with a sliding underline indicator.
 * R3.7A.4C correction: Production DOES carry URL state (`?expertise=specialty`) -- see
 * `fgma-expertise-tabs.js` for the corrected client-side contract; this file's own job is unchanged
 * (structural show/hide + underline transition only). Exact colors/typography are applied by Chrome
 * directly on the Elementor widgets it places (native Style tab), so this stays a visual-safety-net,
 * not a full restyle, pending the Chrome visual QA pass.
 *
 * R3.7A.4E correction: confirmed live, each results panel also carries Elementor's own
 * `.e-flexbox-base` class, and Elementor's real generated CSS (`base-desktop.css`) sets
 * `.elementor .e-flexbox-base{display:flex;}` -- specificity (0,2,0), EXACTLY TIED with the plain
 * `[data-fgma-expertise-panel][hidden]` rule's own (0,2,0), and confirmed live to be enqueued AFTER
 * `fgma-expertise-archive.css` in `<head>` -- so on the tie, Elementor's later-loaded rule won and
 * browser-native `[hidden]{display:none}` never took effect. Compounded with the real, always-present
 * `.fgma-expertise-archive-results` class (never a generated ID) to reach strictly-greater specificity
 * (0,3,0), which wins outright regardless of load order -- never `!important` (forbidden by this
 * file's own test contract, `ExpertiseArchiveStyleContractTest::testNoImportantIsUsed`).
 */
.fgma-expertise-archive-results[data-fgma-expertise-panel][hidden] {
    display: none;
}

/**
 * R3.7A.4M: tabs-to-listing vertical rhythm -- confirmed live, Production's real results grid carries
 * `mt-xl` (`margin-top:var(--space-xl)`) as a direct sibling of the tab bar's own closing wrapper,
 * creating the gap between the gray baseline/underline and the first card row. `--space-xl` is BYTE-
 * IDENTICAL to this codebase's own already-existing `--fgma-space-xl` token -- reused verbatim, never
 * an invented pixel value. DEV's own results panel had `margin-block-start:0px` (confirmed live,
 * Elementor's own v4 Global Class rule, bare `.fgma-archive-results` selector, (0,1,0)) -- compounded
 * with the real, always-present `.fgma-expertise-archive-results` class here to reach (0,3,0), safely
 * beating it regardless of load order. Scoped to Expertise only: Portfolio/Insights/Team have no tab
 * switcher between their hero and results at all, so this specific gap is genuinely Expertise-only,
 * never a generic archive concern.
 */
.elementor .fgma-archive-results.fgma-expertise-archive-results {
    margin-block-start: var(--fgma-space-xl);
}

/**
 * R3.7A.4P: root-box rewrite -- confirmed live, Production's OWN real tab wrapper (`<div class="mt-2xl
 * border-b border-light-grey">`) is a plain, unpadded child NESTED one level inside `.base-container`
 * (`padding:0 var(--space-pp-lg-sm); max-width:2560px; width:100%`, re-fetched live this pass from
 * Production's own critical CSS) -- its own border-box IS the content width, because a normal-flow
 * child's `width:auto` fills its parent's already-padded CONTENT box. This codebase has no equivalent
 * inner nesting level to borrow (`.fgma-expertise-tabs` is simultaneously the gutter-bearing box AND
 * the buttons' direct parent), so every prior round (R3.7A.4L/4N/4O) kept `padding-inline` for the
 * gutter -- which only ever insets CONTENT, never the element's own border-box (re-confirmed this pass:
 * for a normal in-flow block/flex box, `width:auto` and `width:100%` compute IDENTICALLY -- both fill
 * the containing block -- so R3.7A.4O's defensive `width:100%` changed nothing; it only reinforced
 * Elementor's own already-100%-by-default `.e-con{width:var(--width,100%)}`). Whatever paints on that
 * still-full-bleed border-box -- a direct border (R3.7A.4G/4N) or the R3.7A.4N `::after` workaround --
 * either renders at the true full-bleed edge or depends on padding-box inset math nobody could get a
 * real screenshot to confirm.
 *
 * FIXED HERE by making the box's own BORDER-BOX literally equal the content width, so a single, plain
 * border on the root itself is correct with no pseudo-element compensation needed: `width: calc(100% -
 * (var(--fgma-gutter) * 2))` removes exactly one gutter's worth of width from each side, and
 * `margin-inline: auto` distributes that freed-up space as EQUAL left/right margins (one gutter each)
 * -- landing this box's own left/right edges at the identical viewport position `.fgma-archive-hero`'s/
 * `.fgma-archive-results`' own padding-inset CONTENT edges already sit at, but this time as the box's
 * actual border-box, not merely its padding-inset interior. `padding-inline` is removed entirely (no
 * longer needed -- the box itself is now the content width, so the buttons sit flush against it with
 * zero extra inset), which also means `.fgma-expertise-tabs__underline`'s own `inset-inline-start: 0`
 * (an abspos child's `inset` resolving against the containing block's padding box) now resolves against
 * a padding box that equals the border box exactly -- no more distinction between the two to reason
 * about. `max-width: var(--fgma-content-max)` is kept as the same defensive ceiling `.fgma-archive-hero`/
 * `.fgma-archive-results` already use (never actually triggers at real viewport widths, confirmed
 * repeatedly this session, kept only for consistency with the established sibling pattern).
 */
.elementor .fgma-expertise-tabs.e-con {
    width: calc(100% - (var(--fgma-gutter) * 2));
    max-width: var(--fgma-content-max);
    margin-inline: auto;
}

/**
 * R3.7A.4P: the gray baseline moves from the R3.7A.4N `::after` pseudo-element back onto
 * `.fgma-expertise-tabs` itself, directly -- now correct (see the width-contract comment above) because
 * this box's own border-box IS the content width, so a plain `border-block-end` here paints exactly ONE
 * line at exactly the content boundary. No pseudo-element, no `inset-inline` compensation, no second
 * implementation to keep in sync -- single source of truth for both the box's geometry and its visible
 * baseline. `--fgma-rule-color` (`rgba(210,210,210,.5)`) is the same already-existing, byte-identical
 * token used since R3.7A.4G, confirmed against Production's own `border-light-grey`.
 */
.fgma-expertise-tabs {
    position: relative;
    gap: var(--fgma-space-lg);
    border-block-end: 1px solid var(--fgma-rule-color);
}

/**
 * R3.7A.4M: tab internal alignment -- confirmed live via `frontend.min.css`, Elementor's own default
 * Button-widget rule is `.elementor-button{...padding:12px 24px;...}` -- 24px LEFT/RIGHT padding.
 * Neither tab's own outer `[data-fgma-expertise-tab]` wrapper div nor Template 3301's own per-instance
 * CSS (confirmed live, `post-3301.css`) sets any padding of its own -- ALL of the horizontal inset
 * (and the underline's own oversized width, since `fgma-expertise-tabs.js` measures the wrapper div's
 * own `getBoundingClientRect()`, which is sized by this exact padded child) traces to this one native
 * default. Production's own real buttons carry no horizontal padding class at all (`filter-btn pb-sm`
 * -- `pb-sm` is `padding-bottom` only, confirmed live, `post-7.css`/inline styles). Zeroing
 * `padding-inline` here makes the wrapper's own rect naturally equal the visible label's rect -- no JS
 * change needed for the underline at all, matching the task's own explicit preference for a structural
 * fix over compensating in JS. `.elementor`+`[data-fgma-expertise-tab]`+`.elementor-button` reaches
 * (0,3,0), beating the native (0,1,0) default regardless of load order.
 *
 * Removing that padding also removes the ONLY thing that was visually separating "Practice Areas" from
 * "Specialties" (the two buttons' own padding boxes touching produced the illusion of a gap) -- `gap:
 * var(--fgma-space-lg)` restores real spacing the same way Production's own tab bar does
 * (`gap-lg`/`var(--space-lg)`, confirmed live, byte-identical token). The underline `<div>` is
 * `position:absolute` and never participates in flex gap sizing, so this only ever affects the space
 * between the two real tab buttons.
 */
.elementor [data-fgma-expertise-tab] .elementor-button {
    padding-inline: 0;
}

/**
 * R3.7A.4G: cursor affordance -- confirmed live, Production's real tab buttons show `cursor:pointer`
 * on hover; DEV's did not because the visible clickable element is an inert `<a role="button">` with
 * no `href` (browsers only default to a pointer cursor for a REAL link). Scoped to the real,
 * confirmed-present `data-fgma-expertise-tab` attribute this codebase's own JS click handler already
 * targets -- never a generated Elementor class/ID, never a global `button`/`a` rule.
 */
[data-fgma-expertise-tab] {
    cursor: pointer;
}

/**
 * R3.7A.4J: tab REST-state text color -- confirmed live (fetched `post-3301.css`, Template 3301's own
 * real generated per-instance CSS, not guessed), Chrome's own Style-tab configuration set the SAME
 * `color:var(--e-global-color-v4-fgma-off-black)` (#282828) on BOTH tab buttons' `.elementor-button`
 * unconditionally (`.elementor-element-1f88c68 .elementor-button{...color:var(--e-global-color-v4-
 * fgma-off-black);}`, specificity (0,2,0)) -- regardless of `aria-selected`, which the JS already
 * toggles correctly. `data-fgma-expertise-tab`/`aria-selected` live on the OUTER
 * `.elementor-widget-button` wrapper div; the actual visible text sits three levels deeper
 * (`<a class="elementor-button" role="button"><span class="elementor-button-content-wrapper"><span
 * class="elementor-button-text">`) -- `color` is inherited, and the existing per-instance rule already
 * proves inheritance reaches that text correctly (it is what currently renders uniformly), so this
 * only needs to re-target the same `.elementor-button` ancestor, never the inner spans.
 *
 * Production's real confirmed colors (re-fetched this pass, Kit CSS `post-7.css`): ACTIVE = literal
 * black (`--fgma-black:#000000`), INACTIVE = `--fgma-gray:#949494` -- an EXACT match to Production's
 * own reported "~#949494", not an approximation, so the already-existing `--e-global-color-v4-fgma-
 * black`/`--e-global-color-v4-fgma-gray` tokens are reused verbatim, never a new hardcoded value.
 *
 * `[data-fgma-expertise-tab]` alone (never seen anywhere else in this DOM, confirmed) is already
 * correctly scoped to the tab buttons without needing the `.fgma-expertise-tabs` ancestor class
 * repeated in the selector text -- adding it here would push specificity to (0,4,0), which would then
 * incorrectly also beat the `:hover`/`:focus` red rule below (0,3,0) at REST, breaking hover. Reaching
 * exactly (0,3,0) here -- one more than the buggy (0,2,0) rule it must beat, one less than the hover
 * carve-out that must still win -- is deliberate, not an oversight.
 */
[data-fgma-expertise-tab][aria-selected="true"] .elementor-button {
    color: var(--e-global-color-v4-fgma-black);
}

[data-fgma-expertise-tab][aria-selected="false"] .elementor-button {
    color: var(--e-global-color-v4-fgma-gray);
}

/**
 * Hover/focus preservation -- Chrome's own existing per-instance rule already sends both tab buttons
 * to brand-red on `:hover`/`:focus` (confirmed live in the same `post-3301.css` fetch above,
 * unchanged/untouched by this pass). That rule's own specificity (0,3,0) exactly TIES with the two
 * rest-state rules above, which would only resolve correctly via `<head>` load order (this file loads
 * before Elementor's own generated per-template CSS, confirmed live and repeatedly this session) --
 * rather than depend on that order, this explicit, strictly-higher-specificity (0,4,0) carve-out
 * guarantees hover/focus always reads red regardless of load order, scoped under `.fgma-expertise-tabs`
 * as instructed. This reinforces the SAME value Chrome already configured -- it is not a new state.
 */
.fgma-expertise-tabs [data-fgma-expertise-tab][aria-selected="true"] .elementor-button:hover,
.fgma-expertise-tabs [data-fgma-expertise-tab][aria-selected="true"] .elementor-button:focus,
.fgma-expertise-tabs [data-fgma-expertise-tab][aria-selected="false"] .elementor-button:hover,
.fgma-expertise-tabs [data-fgma-expertise-tab][aria-selected="false"] .elementor-button:focus {
    color: var(--e-global-color-v4-fgma-brand-red);
}

/**
 * R3.7A.4L: `inset-inline-start: 0` added -- confirmed live, this element previously had no explicit
 * `left`/`inset-inline-start` at all, leaving its un-transformed resting position to whatever an
 * absolutely-positioned flex-item's own browser-computed "static position" happens to resolve to --
 * under-specified/implementation-dependent, not a guaranteed contract. Pinning it explicitly to the
 * root's own padding-box inner edge (i.e. content-box-left, since an abspos child's `inset` resolves
 * against its containing block's padding box) gives `fgma-expertise-tabs.js`'s own `translateX` a
 * known, deterministic coordinate-space origin to calculate from -- see that file's own comment for
 * the matching JS-side fix this pairs with.
 */
.fgma-expertise-tabs__underline {
    position: absolute;
    inset-inline-start: 0;
    inset-block-end: 0;
    height: 2px;
    background: var(--e-global-color-v4-fgma-brand-red);
    transition: transform .5s cubic-bezier(.4, 0, .2, 1), width .5s cubic-bezier(.4, 0, .2, 1);
    will-change: transform, width;
}

/**
 * R3.7A.4C: classic-widget color-cascade fix -- confirmed live (fetched DEV HTML + Elementor's own
 * auto-generated `<style id="loop-3297">` block), the Expertise hero eyebrow/H1 and card title all use
 * the CLASSIC Heading widget (`elementor-widget-heading`, never the Atomic `e-heading-base` Portfolio/
 * Insights/Team's own hero uses), and Elementor auto-generates ITS OWN default-typography rule for
 * every classic Heading widget left on "Default" per-instance color:
 * `.elementor-widget-heading .elementor-heading-title{color:var(--e-global-color-primary)}` -- a light
 * blue Kit default, specificity (0,2,0), reaching the real `.elementor-heading-title` element (and, via
 * inheritance, its own inner `<a>` when the widget has a Link) DIRECTLY. The existing shared rest-state
 * rule in `fgma-archive.css` (`.elementor .fgma-archive-card__title.elementor-widget.elementor-widget-
 * heading{color:...}`) only ever reaches the WRAPPER div, never `.elementor-heading-title` itself -- an
 * inherited value from an ancestor NEVER beats an explicit declaration on the element itself, regardless
 * of either rule's specificity, so that shared rule was structurally incapable of winning here (this is
 * not a specificity bug, and raising the shared rule's own specificity would not fix it). Portfolio's
 * own classic-widget title never hits this because its own widget carries an explicit per-instance
 * Global Color binding in its own Style tab (native Elementor state, not CSS this codebase owns);
 * Expertise's widgets do not have that set, so a real, code-owned CSS floor is added here instead of
 * depending on every future editor session remembering a manual Style-tab step. Scoped to Expertise only
 * (`body.post-type-archive-expertise` -- WordPress's own native CPT-archive body class, never a
 * generated Elementor ID) since Portfolio/Insights/Team do not share this widget-type combination and
 * must not be touched. The `a` variant is required for the identical reason described in this same
 * comment for the wrapper: a theme/reset `a{color:...}` rule is also an explicit declaration on the
 * element itself and would otherwise silently beat the inherited value from `.elementor-heading-title`.
 */
body.post-type-archive-expertise .elementor .fgma-archive-eyebrow .elementor-heading-title,
body.post-type-archive-expertise .elementor .fgma-archive-eyebrow .elementor-heading-title a {
    color: var(--e-global-color-v4-fgma-gray);
}

body.post-type-archive-expertise .elementor .fgma-archive-title .elementor-heading-title,
body.post-type-archive-expertise .elementor .fgma-archive-title .elementor-heading-title a {
    color: var(--e-global-color-v4-fgma-black);
}

.elementor .fgma-expertise-card__title .elementor-heading-title,
.elementor .fgma-expertise-card__title .elementor-heading-title a {
    color: var(--e-global-color-v4-fgma-black);
    text-decoration: none;
}

/**
 * R3.7A.4N: desktop card-title typography -- confirmed live (fetched the real inline `<style
 * id="loop-3297">` block), this rule had NEVER set `font-family`/`font-weight`/`font-size`/`line-
 * height` at desktop widths at all -- only the mobile-scoped rule further below ever touched typography.
 * Desktop fell through entirely to Elementor's own Kit "Primary" default,
 * `.elementor-widget-heading .elementor-heading-title{font-family:var(--e-global-typography-primary-
 * font-family);font-weight:var(--e-global-typography-primary-font-weight);...}`, which resolves live
 * (`post-7.css`) to `"Roboto"` / `600` -- an EXACT match to the user's own reported "~600" and the
 * wrong family, confirmed rather than assumed. Production's own real desktop card-title contract
 * (`.header-4,.header-5{font-family:AvenirMedium;line-height:1.35}`, re-fetched live this pass) maps
 * onto this codebase's own established generic-family-plus-weight-token convention exactly like the
 * mobile rule already does -- `--fgma-font-family` + `--fgma-weight-medium` (500), never a literal
 * weight-specific family string. `font-size:var(--fgma-step-2)` matches Production's own
 * `font-size:var(--step-2)` (byte-identical token). Added to the SAME already-proven-winning (0,3,0)
 * selector the color rule above uses -- no new selector, no specificity risk. Only the non-`a` variant
 * is needed: no competing rule sets these specific properties on the inner `<a>` (only `color` needed
 * that duplication, per the theme-reset reasoning above).
 */
.elementor .fgma-expertise-card__title .elementor-heading-title {
    font-family: var(--fgma-font-family);
    font-weight: var(--fgma-weight-medium);
    font-size: var(--fgma-step-2);
    line-height: 1.35;
}

/**
 * R3.7A.4G: mobile (<900px) card-title typography -- confirmed live, Production's own real title
 * class below its `lg:` (900px) breakpoint is `paragraph-list-item` (`header-5` only applies at
 * `lg:`), whose real generated rule is `font-family:AvenirMedium;font-size:var(--space-md);line-
 * height:1.3` -- `--space-md` is BYTE-IDENTICAL to this codebase's own already-existing `--fgma-
 * space-md` token (re-verified live, same clamp formula), and `AvenirMedium` maps to this codebase's
 * own established generic-family-plus-weight-token convention (`--fgma-font-family` +
 * `--fgma-weight-medium`), never a literal weight-specific font-family string. DEV's own title was
 * inheriting Elementor's Kit-level "Primary" default typography instead (same auto-generated
 * `.elementor-widget-heading .elementor-heading-title{font-family:...;font-weight:...}` block already
 * diagnosed for color above) -- oversized and heavier than Production at every mobile width. Reuses
 * the SAME already-winning (0,3,0) selector the color fix above uses, extended with the missing font
 * properties, rather than introducing a new, potentially-tied selector.
 */
@media (max-width: 899px) {
    .elementor .fgma-expertise-card__title .elementor-heading-title {
        font-family: var(--fgma-font-family);
        font-weight: var(--fgma-weight-medium);
        font-size: var(--fgma-space-md);
        line-height: 1.3;
    }
}

.fgma-archive-card:hover .fgma-expertise-card__title .elementor-heading-title,
.fgma-archive-card:hover .fgma-expertise-card__title .elementor-heading-title a,
.fgma-archive-card:focus-within .fgma-expertise-card__title .elementor-heading-title,
.fgma-archive-card:focus-within .fgma-expertise-card__title .elementor-heading-title a {
    color: var(--e-global-color-v4-fgma-brand-red);
}

/**
 * R3.7A.4O: mobile header-to-hero clearance -- root-caused, not assumed. Confirmed live: Team's own
 * Template 3277 (which, like Expertise, consumes the SHARED `fgma-archive-hero`/`fgma-archive-eyebrow`
 * contract, unlike Portfolio's separate legacy `fgma-portfolio-*` classes) carries a real, Chrome-
 * authored mobile-only per-instance rule -- `global-3277-frontend-mobile.css`, confirmed live --
 * `@media(max-width:767px){.elementor .fgma-archive-eyebrow{margin-block-start:100px;}}`. Expertise's
 * own Template 3301 has NO mobile-specific per-instance CSS file at all (confirmed live: only
 * `global-3301-frontend-desktop.css`/`local-3301-frontend-desktop.css`/`post-3301.css`, all
 * `media="all"`) -- Chrome never gave Expertise this same header-clearance value, so its mobile hero
 * fell back to the shared `.fgma-archive-eyebrow{margin:0;...}` rule's own zeroed margin plus the
 * hero's own generic `padding-block:var(--fgma-space-lg)`, a genuinely different (and, per this pass's
 * own live Chrome QA, visibly wrong) total gap. Reuses Team's own exact, already-approved value
 * (matching "same spacing logic," never an invented pixel number) rather than a new Expertise-specific
 * guess. Scoped via `body.post-type-archive-expertise` (WordPress's own native CPT-archive body class)
 * so this can never reach Team/Portfolio/Insights, even indirectly -- (0,3,0), safely beating the
 * shared `margin:0` rule's own (0,1,0).
 */
@media (max-width: 767px) {
    body.post-type-archive-expertise .elementor .fgma-archive-eyebrow {
        margin-block-start: 100px;
    }
}
