/**
 * core/post-title rules, each scoped to the unit that owns it.
 *
 * This file is shared by construction: every unit that places a core/post-title lands here. Nothing in it
 * may be written unscoped -- a rule with no unit hook class repaints every instance of the
 * block on the site, which is a theme decision and belongs to wp-theme-scaffold.
 */

/*
 * .wm-news-teaser-card: the teaser's title is 23px, and a block attribute cannot say so on
 * this theme.
 *
 * The contract's core/post-title node measures `h3.node-title` at 310x129 holding a 23px
 * weight-700 anchor, and 129 is four lines of 23px at theme.json's
 * `styles.elements.h3.lineHeight` of 1.4 (4 x 32.2 = 128.8). theme.json's `styles.elements.h3`
 * is `x-large`, 1.625rem, `fluid: false` -- 26px, which renders the same four lines 145.6 tall
 * and pushes the excerpt and the card's own bottom edge 17px down.
 *
 * WHY NOT THE BLOCK'S OWN `fontSize` ATTRIBUTE: `settings.typography.fluid` is true, so a
 * custom px size becomes a clamp at render -- measured in heading.css's .wm-image-link-cards
 * note on this install. And no preset is 23: `large` is fluid {21, 24} and `x-large` is 26.
 * The contract says the same thing in words: "23px is off this theme's ladder at both ends
 * ... the measurement is recorded rather than rounded."
 *
 * WHY THIS BEATS theme.json: `styles.elements.h3` compiles to a bare `h3` tag selector with no
 * block scoping, specificity 0,0,1. This is 0,2,0. Nothing inline is being fought, because the
 * attribute had to be dropped rather than supplemented.
 *
 * THE SIZE IS THE ONLY THING HERE. The weight (700), the leading (1.4) and the family
 * (roboto-slab) all come from `styles.elements.h3` already and match the measurement, so they
 * are not restated; the colour is the block's own `textColor: "primary"` attribute and the 8px
 * of bottom margin is the block's own `spacing.margin`, both in
 * patterns/news-teaser-card.php with their derivations.
 *
 * NOT A BREAKPOINT RULE, same assumption and same caveat as post-date.css.
 */
.wm-news-teaser-card .wp-block-post-title {
	font-size: 23px;
}

/*
 * .wm-navigation-card: THE TITLE IS `Jura` AT A FLAT 33px, AND NEITHER HALF IS REACHABLE BY A
 * BLOCK ATTRIBUTE ON THIS THEME.
 *
 * THE MEASUREMENT. A live probe of the source on 2026-09-11 reads the card's `h3.node-title`
 * as `Jura, sans-serif`, weight 700, font-size 33px, line-height 36.3px, `maxWidth: none`,
 * at every one of the four viewports -- 33px is FLAT across the sweep, not banded. The
 * contract records the same figures and three independent measurements behind them.
 *
 * WHAT THE THEME DOES UNTOUCHED, measured on this install before this rule: `"Roboto Slab",
 * serif` at 26 / 20 / 20 / 20px. `styles.elements.h3` is `roboto-slab` at `x-large`, and
 * `x-large` is `{"size":"1.625rem","fluid":false}` -- a flat 26px -- which theme.json's own
 * `styles.css` band steps to 1.25rem below 1123.98px. Both the family and the size are the
 * theme's h3 token reaching this block, not anything this pattern asked for: `core/post-title`
 * renders an `h3` for `level: 3`, and `styles.elements.h3` compiles to a bare `h3` tag
 * selector with no block scoping (reference/sources/block-attributes.md, "a block's rendered
 * TAG is a style surface").
 *
 * WHY NOT ATTRIBUTES, both halves:
 *   - SIZE. No preset is 33. The ladder is 16 / 17-20 / 21 / 21-24 / 26 / 44 / 57, and the
 *     nearest, `x-large`, is the 26 this rule is replacing. A custom px `fontSize` is not the
 *     escape either: `settings.typography.fluid` is true, so a custom px size becomes a clamp
 *     at render -- the same trap heading.css's .wm-image-link-cards note measured on this
 *     install. A literal declaration here is not fluidised and stays flat across the sweep,
 *     which is what the source does.
 *   - FAMILY. `core/post-title` exposes no fontFamily that would beat the bare `h3` selector
 *     for this block alone, and the value wanted is a font the theme already declares. The
 *     preset var is used rather than the literal stack so the `jura` fontFace -- and its
 *     assets/fonts/jura/Jura-VariableFont_wght-latin.woff2 -- stays the single source of the
 *     family.
 *
 * WHY THIS IS THE UNIT'S RULE AND NOT A theme.json CHANGE, stated because it is a real
 * question and the answer is not obvious. `styles.elements.h3` is site-wide: the same token
 * feeds .wm-news-teaser-card's title above, whose own measured family IS roboto-slab. So the
 * two units' h3s genuinely disagree about family, and changing the theme's h3 to Jura would
 * move the teaser away from ITS source. If a later pass finds most of this site's h3s are
 * Jura, the right fix is theme.json's `elements.h3` and this rule becomes redundant -- that
 * is wp-theme-scaffold's call and theme.json was NOT touched here. Named in the hand-back.
 *
 * SPECIFICITY. The bare `h3` selector is 0,0,1 and the band sets the preset VARIABLE on
 * `:root`, so it reaches the tag rule rather than this one. This is 0,2,0 with a literal
 * value, and `core/post-title` writes nothing inline in patterns/navigation-card.php for it
 * to fight.
 *
 * THE LEADING IS NOT HERE. 36.3 / 33 = 1.1, and the block's own
 * `style.typography.lineHeight` of 1.1 in patterns/navigation-card.php carries it -- a ratio
 * survives a size change, so it stays an attribute. THE WEIGHT IS NOT HERE EITHER:
 * `styles.elements.h3` already gives 700, which is what the source measures.
 */
.wm-navigation-card .wp-block-post-title {
	font-family: var(--wp--preset--font-family--jura);
	font-size: 33px;
}
