/*
 * core/navigation — rules scoped to the units that place it.
 *
 * Every rule here is scoped to a unit's own hook class. An unscoped rule in this file
 * would repaint every core/navigation on the site, which is a theme decision and belongs
 * to wp-theme-scaffold, not to a unit build.
 */

/* -------------------------------------------------------------------------- header
 *
 * Unit: header (parts/header.html). Hook class .wm-header on the part's root group.
 */

/* MEASURED: the first top-level item renders at 18px. theme.json puts core/navigation at
 * the `medium` preset (1.25rem = 20px), which is the site-wide answer; this is the
 * header's own. */
.wm-header .wp-block-navigation {
	font-size: 18px;
}

/*
 * THE MENU ROW IS 57px TALL AND THE ITEMS FILL IT EDGE TO EDGE. Four boxes were measured
 * at 1440 and they agree: `ul.menu.main` is 770x57 at x=459, the column that holds it is
 * 800x57 at x=444, the row is 1200x57 and the header root is 117 = 30 + 57 + 30. The
 * container's own height is therefore a measured number, not a consequence of what is
 * inside it — core's would be 27px, the line box of an 18px item.
 *
 * THE ITEM PADDING IS DERIVED RATHER THAN FITTED, and two independent measurements land
 * on the same answer. Core lays these six items out at 91 + 89 + 105 + 107 + 96 + 93 =
 * 581px of content; the source's row is 770 and its first item is 124 against core's 91.
 * A gap of zero plus a horizontal padding of ~16px per side satisfies both at once
 * (581 + 6x32 = 773 ~ 770, and 91 + 32 = 123 ~ 124), which no other pair does. The value
 * written is 15px rather than 16 because 15 is the source's own half-gutter — the
 * `$grid-column-gutter` value site.yml's design_tokens records as the single most common
 * spacing in the whole capture — so the fit is to a source token instead of to one string
 * of text whose width depends on the font that happens to be rendering it.
 */
.wm-header .wp-block-navigation__container {
	min-height: 57px;
	align-items: center;
	gap: 0;
}

/*
 * THE ROW MUST NOT WRAP -- ADDED 2026-09-13, and this is the whole of the 175px-against-117px
 * height difference this unit was carrying. Core's flex layout defaults to `flex-wrap: wrap`
 * (`wp-includes/blocks/navigation/style.css`'s `.wp-block-navigation__container`), so once the
 * six top-level items exceeded the nav column's 800px the CTA and the search dropped onto a
 * second line: MEASURED before this rule, `nav.wm-header__nav` was 770x115 at (459,30) against
 * the source's 770x57, and 30 + 115 + 30 = 175, which is the reported root height exactly.
 *
 * The source does not wrap and does not fit either -- it OVERFLOWS its own wrapper and stays on
 * one line. The contract's own numbers say so: `ul.menu.main` is 770x57 at x=459, and inside it
 * the "Contact Us" anchor sits at x=1111..1245 and the search toggle at x=1290..1327, both past
 * the wrapper's own right edge at 1229. So `nowrap` reproduces the source's behaviour rather
 * than working around core's.
 *
 * `flex-shrink: 0` IS NOT OPTIONAL BESIDE IT. Core writes no `flex-shrink` for these items, so
 * under `nowrap` the browser splits the overflow across them in proportion to their flex bases
 * and every label squeezes -- the failure mode reference/sources/block-attributes.md §Siblings
 * describes. Pinning them makes the row overflow as one piece, which is what the source does.
 */
.wm-header .wp-block-navigation__container {
	flex-wrap: nowrap;
}

/*
 * PADDING 9px 15px, NOT 5px 15px -- CHANGED 2026-09-20. The source's top-level <li> measures 38px
 * tall (y 39.5..77.5) with its panel starting flush at y=77.5; the build's measured 30px, which
 * left a 14px dead gap between the trigger and its panel (panel at y=87 under a container that
 * ends at 87). Now that a panel opens on HOVER -- see "OPEN ON HOVER" below -- that gap is a
 * defect rather than a cosmetic: the pointer leaves the <li> on the way down to the panel and
 * the panel closes under it. 9 + 20 + 9 = 38 closes it. The row stays 57 (the items are
 * centred in it), so no other measurement moves.
 */
.wm-header .wp-block-navigation__container > .wp-block-navigation-item {
	/* 9px top/bottom is load-bearing (item 4, "a component's own size"): the comment above derives
	   it as 9 + 20 + 9 = 38, the exact row height the hover-panel gap fix depends on -- snapping it
	   to 10 would reopen the panel-closes-under-the-pointer defect this rule fixed. 15px left/right
	   snapped to spacing|25 (16px), 2026-09-25 (spacing-standard.md §1 item 3): purely horizontal,
	   no such dependency. */
	padding: 9px var(--wp--preset--spacing--25);
	flex-shrink: 0;
}

/*
 * THE TOP-LEVEL CHEVRON IS CORE'S, NOT THE SOURCE'S, AND IS NOW SHOWN ANYWAY -- REVISED
 * 2026-09-22, REVERSING THE 2026-09-13 "hide it, faithfully" DECISION BELOW. core/navigation
 * draws a disclosure caret after every item that has a submenu; the source draws none. This
 * unit's contract settles that twice over: its `chrome` key enumerates exactly three things this
 * header draws by itself (`search-trigger-icon`, `cta-fill-plate`, `mega-menu-column-divider`)
 * and no caret is among them, and its `core/navigation` why records that the one SCSS rule that
 * looks like a caret (`&.menu-item--expanded > a:after`) computes `content: ""` on the live
 * source -- "a byte-faithful rebuild reproduces NO chrome for this rule". That is still the
 * FAITHFUL reading and is not contradicted; it is overridden. Operator decision, this unit's fix
 * pass: a dropdown trigger with no visible affordance distinguishing it from a plain link is bad
 * practice on its own terms, source or no source, and is fixed rather than reproduced -- the same
 * "flag a source defect, don't copy it" instruction already applied elsewhere on this unit (the
 * search overlay gap, commit be3a77d).
 *
 * WHY THIS WAS A CSS RULE AND NOT THE `showSubmenuIcon` ATTRIBUTE -- TRUE WHILE THIS UNIT WAS
 * `submenuVisibility: click`, NO LONGER TRUE SINCE THE 2026-09-24 MOVE TO `hover`. Read off this
 * install's own `wp-includes/blocks/navigation-submenu.php`: the caret is rendered in two
 * branches, and only the NOT-open-on-click one consults the attribute (`:206`,
 * `if ( $show_submenu_indicators && $has_submenu )`) -- which is exactly the branch `hover` mode
 * takes. So on this build `showSubmenuIcon: true` (parts/header.html) is now what makes core emit
 * the toggle button at all; this stylesheet only sizes and colours it, it no longer decides
 * whether it exists. Left here as the historical reason a CSS-only approach was chosen over the
 * attribute, not as a description of the attribute's current effect.
 *
 * SIZED DOWN, NOT LEFT AT CORE'S OWN 0.6em, SO THE ROW STILL FITS ONE LINE -- SEE THE TOGGLE
 * PADDING RULE BELOW FOR THE FULL ARITHMETIC. Core's own caret plus its own reserved padding cost
 * ~15.3px per item (0.85em at this row's 18px) and reopening that in full was measured to push
 * the row 60px past its own container, which is the exact "Products overlaps the logo" defect the
 * 2026-09-13 pass below fixed by hiding the caret outright. A caret at roughly half that box (with
 * the toggle's own reserved space shrunk to match, below) costs far less per item while staying
 * clearly visible -- confirmed with a real screenshot at 1124px and at 1440px, not asserted.
 *
 * `color: primary` MATCHES THE NESTED-LEVEL CARET, WHICH WAS ALREADY VISIBLE AND ALREADY THIS
 * COLOUR (the flyout chevron rule further down, `.wp-block-navigation-item.has-child:not(
 * .wm-header__section-header) > .wp-block-navigation__submenu-icon`). The two are deliberately
 * different SIZES -- this one small and downward for a dropdown, that one larger and bolder for a
 * sideways flyout, different affordances for different directions -- but the same colour is what
 * reads as one consistent system rather than two unrelated treatments happening to coexist.
 *
 * REVISED AGAIN 2026-09-22, SAME DAY -- 0.4em (7.1875px measured at this row's 18px, 6px at the
 * 1124-1299 band's 15px) is not a caret, it is a dot: confirmed with a real screenshot zoomed on
 * one item, not asserted from the DOM. The nested-level caret above this note is the operator's
 * own bar for "styled properly, right size, proper space away from text" -- it is 14x14px with a
 * 2.5px stroke, SIZED ON THE SVG, NOT THE EM-DERIVED ICON SPAN, precisely so it does not shrink
 * when the row's own font-size steps down at 1124-1299px. This rule now matches it on size and
 * stroke, in PX rather than EM for the same reason: an em-sized caret shrinks a second time at the
 * 1124-1299 band's 15px row on top of already being too small, which is backwards -- a smaller row
 * is where the caret most needs to hold its legibility, not lose more of it. Root cause of the
 * previous, undersized rule: it was fitted to the row's own budget FIRST and never checked against
 * a zoomed screenshot before being called done.
 *
 * FITS BOTH DOCUMENTED EDGES, MEASURED WITH PROBE.JS, NOT ASSUMED. At 1440px the row (Search
 * toggle's own right edge) sits at 84px of slack before this change; at 1124px, the tighter of the
 * two, it sits at 36px. Four top-level items carry a caret (Products, Services, Resources,
 * Company); going from the previous ~6-7px reservation to 14px costs each one roughly
 * (14 - previous) more, ~4 x 8px = 32px at 1124px -- inside the 36px budget, with no other lever
 * (letter-spacing, item padding) needed. Confirmed after the change: no overflow, no logo overlap,
 * one line, at both 1440px and 1124px real viewport measurements (see this unit's own hand-back).
 */
.wm-header .wp-block-navigation__container > .wp-block-navigation-item.has-child > .wp-block-navigation__submenu-icon {
	width: 14px;
	height: 14px;
	margin-left: 0.15em;
	color: var(--wp--preset--color--primary);
}

/* The SVG's own box, sized explicitly rather than inherited from the icon span above, and its
   stroke widened to match -- the same reason and the same two-selector shape as the nested-level
   caret's own comment below (`.wp-block-navigation__submenu-icon svg` / `svg path`): the path
   carries its own `stroke-width` attribute, so only a selector naming the path can override it. */
.wm-header .wp-block-navigation__container > .wp-block-navigation-item.has-child > .wp-block-navigation__submenu-icon svg {
	width: 14px;
	height: 14px;
}

.wm-header .wp-block-navigation__container > .wp-block-navigation-item.has-child > .wp-block-navigation__submenu-icon svg path {
	stroke-width: 2.5px;
}

/*
 * THE CARET'S RESERVED SPACE MATCHES THE 14PX CARET ABOVE, IN PX FOR THE SAME REASON --
 * REVISED AGAIN 2026-09-22, carrying forward the 2026-09-13 finding below (still correct: core
 * reserves the caret's room with PADDING ON THE TOGGLE, a different element from the caret SPAN
 * itself, and the two have to be sized together or one contradicts the other).
 *
 *   .wp-block-navigation-item.open-on-click .wp-block-navigation-submenu__toggle
 *     { padding-left: 0; padding-right: 0.85em }
 *
 * navigation/style.css:360-363 on this install. `open-on-click` is the class this unit's
 * `submenuVisibility: click` puts on every expandable item. Core's own 0.85em is sized for core's
 * own 0.6em caret; this rule's own caret is a fixed 14px now (see the sibling comment above for
 * why px, not em -- the 1124-1299px band's own font-size step must not shrink it a second time),
 * so the reservation is written in px too: anything left in em would drift out of step with the
 * caret at exactly the band where the caret most needs to hold its size.
 *
 * THE HISTORY, KEPT FOR THE ARITHMETIC IT ESTABLISHES. 2026-09-13 measured the +15.3px-per-item
 * cost of core's FULL reservation with probe.js -- the build against the live source at 1440x900,
 * `header .menu.main > li` on one side and `.wm-header .wp-block-navigation__container > li` on
 * the other:
 *
 *   Products     source 124  build 139  (+15)   has-child
 *   Services     source 113  build 128  (+15)   has-child
 *   Applications source 152  build 152  ( 0)    NO submenu -- no toggle, no reservation
 *   Resources    source 134  build 149  (+15)   has-child
 *   Company      source 115  build 130  (+15)   has-child
 *   Contact Us   source 194  build 194  ( 0)    a link, not a submenu
 *
 * Applications and the CTA being exact was the control: a cause in the <li> padding, the font, or
 * the letter-spacing would have moved all six. 4 x 15.3 = 61px, and the row was 892 against the
 * source's 832 -- 60px, the same number from the other side. This is a KNOWING DEPARTURE from the
 * source's own "Products" width (124px, which the 2026-09-13 zero-reservation fix matched
 * exactly, and which the 2026-09-22 first revision below approximated at +7px): the caret is new
 * chrome the source never drew at all, so no source width can include room for it, and every
 * top-level item with a submenu is now ~14px wider than the pixel-exact source figure this file's
 * earlier pass reached, in exchange for a caret that actually reads as a caret. Confirmed to still
 * fit the row at 1124px and 1440px with a real screenshot -- see this rule's own sibling comment
 * above for the slack arithmetic.
 *
 * NOT DONE WITH `padding-right` ON THE TOGGLE ALONE: core sets `padding-left: 0` in the same rule
 * and the shorthand below restates both, so the toggle keeps core's own left value instead of
 * inheriting whatever a later edit leaves behind. The caret's own negative counter-margin
 * (core's `margin-left: -0.6em` on the icon that follows an `open-on-click` toggle,
 * navigation/style.css:364-367) is also re-scaled to match, in the rule beneath this one, so the
 * caret still sits pulled back into its own reserved space rather than floating in the middle of
 * it or doubling its own width with dead padding.
 *
 * THE NESTED TOGGLES CARRIED THE SAME DEAD 0.85em UNTIL THE 2026-09-13 PASS -- see the
 * nested-level caret rule far below (`.wp-block-navigation__submenu-container >
 * .wp-block-navigation-item.has-child:not(.wm-header__section-header) >
 * .wp-block-navigation__submenu-icon`), already visible before this pass for a different reason
 * (a real flyout, not a dead promise) and now the top level's own model rather than the other way
 * round.
 *
 * THE COUNTER-MARGIN NO LONGER CANCELS THE FULL RESERVATION -- FIXED 2026-09-22, SAME DAY, A
 * SECOND TIME. `margin-left: -14px` against a `padding-right: 14px` toggle pulls the icon back by
 * exactly the reserved width, landing its left edge flush on the label's own right edge --
 * MEASURED with a real `getBoundingClientRect()` on both boxes (not a screenshot crop, which the
 * chevron SVG's own internal viewBox whitespace can make read as spaced when the boxes are flush):
 * `labelRect.right === iconRect.left` on all four items, `gap: 0`. The operator wants real,
 * visible spacing between the label and the caret, not zero. `-7px` (half the reservation) leaves
 * a 7px gap -- `padding-right(14) - |margin-left(7)| = 7` -- while the icon still lands inside the
 * row's already-budgeted 14px-per-item cost this rule's own history above measured and fit at both
 * 1124px and 1440px; the 7px the icon now sits past the toggle's own right edge is new width, not
 * covered by that arithmetic, and was re-measured after this change (see this dispatch's own
 * hand-back) rather than assumed still safe.
 */
.wm-header .wp-block-navigation__container > .wp-block-navigation-item.has-child.open-on-click > .wp-block-navigation-submenu__toggle {
	padding-left: 0;
	padding-right: 14px;
}

.wm-header .wp-block-navigation__container > .wp-block-navigation-item.has-child.open-on-click > .wp-block-navigation-submenu__toggle + .wp-block-navigation__submenu-icon {
	margin-left: -7px;
}

/*
 * THE ROW OVERFLOWS RIGHT, NOT LEFT -- ADDED 2026-09-13, and it is the other half of the same
 * defect. The rule above recovers 61px; the row was 122px too far left, and this is the
 * remaining 61.
 *
 * THE MENU DOES NOT FIT ITS OWN WRAPPER IN THE SOURCE EITHER, which the `flex-wrap: nowrap` rule
 * above already establishes from the contract's own numbers. Where a flex line overflows, the
 * justification decides WHICH EDGE it spills past: `flex-end` (core's rendering of this unit's
 * `justifyContent: right`) overflows past the START edge, leftward. That is what put "PRODUCTS"
 * on top of the logo.
 *
 * MEASURED, BOTH SIDES, 1440x900. The container itself is identical on the two: source
 * `ul.menu.main` 770x57 at x=459, build `ul.wp-block-navigation__container` 770x57 at x=459 --
 * so nothing about the box needed changing, only which end its contents are anchored to. The
 * SOURCE's first item starts at x=459, flush with that container's own LEFT edge, and its last
 * spills past the right edge at 1229 (the CTA's <li> ends at 1291, the search toggle at 1327).
 * The BUILD's first item started at x=337 -- 122px LEFT of the container it sits in, and 107px
 * inside the logo column, which ends at x=444. With the reservation removed the row is 832 wide,
 * and anchored at 459 it runs 459..1291: the source's span exactly, to the pixel.
 *
 * THE CONTRACT'S `justifyContent: right` IS NOT CONTRADICTED AND IS NOT CHANGED. Its own why
 * derives `right` from the CONTAINER's position -- "the menu's 770px sits at x=459 flush to the
 * row's right edge" -- which is a fact about the <ul>, a block-level element filling its 770px
 * wrapper, not about how its children are packed inside it. Both are true at once and only one
 * of them has a core attribute; this is the scoped-stylesheet half, in the same file and for the
 * same reason as the `nowrap`, the 1124px collapse and the `pointer-events` rules the contract
 * also names as having nowhere else to live.
 */
.wm-header .wp-block-navigation__container {
	justify-content: flex-start;
}

/*
 * "CONTACT US" IS A CTA BUTTON, NOT A PLAIN LINK -- ADDED 2026-09-13, closing the gap this
 * unit's own contract found in its `<li class="cta-button menu-item" type="cta-button"><a
 * class="cta-button">Contact Us</a></li>` markup, invisible to the original 120-element
 * capture cap (it sits after five branches that already spend the whole budget) and
 * confirmed instead with a supplementary tooling/extract/probe.js reading against the live
 * source. `core/navigation-link` declares no colour support at all
 * (wp-includes/blocks/navigation-link/block.json: only `anchor` and `typography`), so
 * neither the fill nor the fill-plate chrome below can be reached through any attribute --
 * both need this scoped rule.
 *
 * MEASURED live on `li.cta-button > a` at 1440x900: display:inline-block, color:#fff,
 * background:rgb(219,36,11) (= this theme's `primary`), padding:20px 0 20px 30px,
 * margin:0 45px 0 15px, font:Jura 17px/700, uppercase, letter-spacing:-0.5px. CODE confirms
 * the mechanism: scss/base/_common.scss:20-51's `%cta-button` placeholder (`position:
 * relative` is the anchor's own containing block for the plate below), further overridden
 * for font-size by this nav's own nested rule (_menu_block.scss:72-86, 17px not the base
 * rule's 21px -- the value this build measures and writes). Not gated to the desktop
 * breakpoint below: unlike the mega-menu panel chrome, a styled CTA is a reasonable thing to
 * keep inside the mobile overlay menu too, and nothing measured says otherwise.
 */
/*
 * THE CTA'S OWN <li> TAKES NO PADDING -- ADDED 2026-09-13, and it is the last 10px of the
 * header's height. The row rule above gives every top-level item `padding: 5px 15px`, which is
 * right for a plain link whose anchor is 18px tall inside a 57px row. The CTA's anchor is
 * itself 57px tall (20px padding + a 17px line box + 20px padding -- MEASURED 134x57 after the
 * contract's `lineHeight: 1` landed, which is the source's anchor box exactly), so the same
 * 5px top and bottom made its <li> 67px and dragged the whole row to 67 and the header to 127
 * against the source's 117. The source's CTA carries its own spacing as MARGIN on the anchor
 * (`0 45px 0 15px`, already written in the rule below) and its <li> adds nothing, so the
 * horizontal padding goes with the vertical rather than being kept for symmetry.
 */
.wm-header .wp-block-navigation__container > .wp-block-navigation-item.wm-header__cta-button {
	padding: 0;
}

.wm-header .wp-block-navigation-item.wm-header__cta-button > .wp-block-navigation-item__content {
	position: relative;
	display: inline-block;
	color: var(--wp--preset--color--white);
	background-color: var(--wp--preset--color--primary);
	padding: var(--wp--preset--spacing--30) 0px var(--wp--preset--spacing--30) var(--wp--preset--spacing--40);
	margin: 0px var(--wp--preset--spacing--50) 0px var(--wp--preset--spacing--25);
	font-family: var(--wp--preset--font-family--jura);
	font-size: 17px;
	font-weight: 700;
	text-transform: uppercase;
	letter-spacing: -0.5px;
}

/*
 * THE OFFSET FILL-PLATE BEHIND IT -- this unit's own `chrome` key, `cta-fill-plate`.
 * CONFIRMED LIVE with probe.js --pseudo=after: the real `::after` measures 134x57 (the
 * anchor's own box), `background-color:rgb(219,36,11)`, `z-index:-1`, `left:30px`. CODE:
 * the SAME `%cta-button` placeholder's own `:after` (_common.scss:37-47). `z-index:-1`
 * needs no stacking-context fix here -- the anchor already paints its own opaque fill on
 * top, so the plate only shows in the 30px it extends past the anchor's own right edge.
 *
 * THIS IS THE SAME MECHANISM assets/css/blocks/button.css NOW WRITES ONCE, UNSCOPED, FOR
 * EVERY FILLED `core/button` CTA (`fix/global-link-decoration`, 2026-09-13) -- not a second
 * invention. It is registered here separately, not shared with that file, because this CTA is
 * a styled `core/navigation-link`, not a `core/button`: a different block, with no selector in
 * common with button.css, and button.css is enqueued only where a `core/button` is actually on
 * the page (`functions.php`'s `washington_mills_block_stylesheets()`) -- this header renders on
 * every page including ones with no `core/button` at all, so its fill-plate has to live where
 * `core/navigation`'s own stylesheet is guaranteed to load, not there. See that file's own
 * comment on this same rule for the fuller reconciliation note.
 *
 * THE HOVER SKEW, now reproduced (2026-09-13, same pass). It was not, and this comment used to
 * say so explicitly -- "a state with no `states` entry on this contract" -- which was true and
 * is why it went unbuilt rather than silently omitted. `&:hover { &:after { transform:
 * skew(15deg) } }` (_common.scss:48-51) is the whole of the filled CTA's hover treatment
 * site-wide, transcribed from the source's own SCSS the same way button.css's copy is, since no
 * DOM capture can witness a hover state at all.
 */
.wm-header .wp-block-navigation-item.wm-header__cta-button > .wp-block-navigation-item__content::after {
	content: "";
	position: absolute;
	top: 0px;
	left: 30px;
	width: 100%;
	height: 100%;
	background-color: var(--wp--preset--color--primary);
	z-index: -1;
	transition: 0.3s ease-in-out;
}

.wm-header .wp-block-navigation-item.wm-header__cta-button > .wp-block-navigation-item__content:hover::after {
	transform: skew(15deg);
}

/*
 * BELOW THE SOURCE'S `xlarge` STEP THE MENU IS SMALLER, AND WITHOUT IT THE ROW RUNS OFF THE
 * SCREEN -- ADDED 2026-09-20. MEASURED on the live source (Playwright, computed, resized in
 * place, bisected): from 1124 up to 1299 the top-level items are 15px with 13px each side
 * (li 102 wide, ul 703) and the CTA 15px (120 wide); at 1300 exactly they step to the 18px / 15px /
 * 17px this file writes above (li 124, ul 770, CTA 134). 1300 is the `xlarge` column of the
 * source's $header-styles map, the same edge site.yml's font ladder records. The build wrote the
 * large-step values at every width, so at 1124 its six items ran 325..1156 -- the CTA 32px past
 * a 1124px viewport, MEASURED as document.scrollWidth 1156 against the source's 1124 -- and
 * "the menu is overflowing the width of the screen" was true here as well as in the Products
 * panel. The pair below applies only to the 1124..1299 band; the collapse to the overlay is
 * below 1124 and untouched.
 */
@media (min-width: 1124px) and (max-width: 1299.98px) {
	.wm-header .wp-block-navigation {
		font-size: 15px;
	}

	.wm-header .wp-block-navigation__container > .wp-block-navigation-item {
		/* Was 13px a side, snapped to spacing|20 (10px), 2026-09-25 (spacing-standard.md §1 item 3,
		   a tie broken down, same precedent as 25px -> 20px). */
		padding-left: var(--wp--preset--spacing--20);
		padding-right: var(--wp--preset--spacing--20);
	}

	.wm-header .wp-block-navigation-item.wm-header__cta-button > .wp-block-navigation-item__content {
		font-size: 15px;
	}

	/*
	 * THE 7PX CARET GAP DOES NOT FIT HERE -- MEASURED 2026-09-22, NOT ASSUMED FROM THE 1440PX
	 * ARITHMETIC BELOW. `getBoundingClientRect()` on `.wm-header__search-toggle` (the row's own
	 * last, rightmost box) at exactly 1124x900 -- the documented tight edge this file already
	 * treats as the real worst case, not a hypothetical -- reports `right: 1120` against a 1124px
	 * viewport: 4px of total slack, for FOUR has-child items sharing it. A gap costs the same
	 * extra width per item everywhere on this row (padding and counter-margin trade off exactly,
	 * so splitting the reservation differently never changes the total) -- so 4px of slack over 4
	 * items is a hard ceiling of 1px of real gap each at this exact width, not an estimate: 2px
	 * measured 4px of overflow (`document.documentElement.scrollWidth` 1128 against 1124),
	 * confirmed with `tooling/node_modules/playwright`'s bundled Chromium, not inferred.
	 *
	 * This override narrows the gap back to 1px for the one band where the row is already this
	 * tight before the gap exists at all (see the "BELOW THE SOURCE'S `xlarge` STEP" comment
	 * above this block): not zero -- the defect this pass exists to fix -- but real headroom for
	 * a wider gap here would mean shrinking the 13px item padding two paragraphs up, which is a
	 * SOURCE-MEASURED value ("MEASURED on the live source... bisected"), or the caret's own fixed
	 * 14px size, which the 2026-09-22 pass above fixed deliberately and is not this dispatch's to
	 * reopen -- both out of scope for a two-named-bug fix pass. Flagged in this dispatch's own
	 * hand-back as a real constraint, not smoothed over.
	 *
	 * SUPERSEDED 2026-09-24, THE SAME DAY `submenuVisibility` MOVED FROM `click` TO `hover`. The
	 * `.open-on-click` class this rule keyed on no longer occurs anywhere in this build (every
	 * expandable item now carries `.open-on-hover-click`, and the toggle IS the caret element --
	 * one merged `<button class="wp-block-navigation__submenu-icon
	 * wp-block-navigation-submenu__toggle">`, not a button-plus-sibling-span), so the rule below
	 * went dead: `document.documentElement.scrollWidth` measured 1129 against a 1124px viewport
	 * with it inert, the same class of overflow this band existed to close, now back because the
	 * click-mode reservation this rule pulled back into no longer exists to reserve anything. The
	 * replacement targets the merged element directly and tightens its own small default
	 * `margin-left: 0.15em` (this file's general `.has-child > .submenu-icon` rule near the top)
	 * rather than counter-pulling a padding reservation hover mode never adds: `margin-left: 0` on
	 * four has-child items reclaims ~9px at this band's 15px font (4 x 2.25px), against a measured
	 * 5px deficit. CONFIRMED after the change: `document.documentElement.scrollWidth` 1124 against
	 * a 1124px viewport, real Playwright, not assumed from the arithmetic alone.
	 */
	.wm-header .wp-block-navigation__container > .wp-block-navigation-item.has-child.open-on-click > .wp-block-navigation-submenu__toggle + .wp-block-navigation__submenu-icon {
		margin-left: -13px;
	}

	.wm-header .wp-block-navigation__container > .wp-block-navigation-item.has-child.open-on-hover-click > .wp-block-navigation-submenu__toggle.wp-block-navigation__submenu-icon {
		margin-left: 0;
	}
}

/*
 * A SECOND, PRE-EXISTING GAP FOUND WHILE VERIFYING THE ONE ABOVE, AND DELIBERATELY NOT TOUCHED --
 * FOUND 2026-09-22. Scanning `document.documentElement.scrollWidth` across 1300..1440 in 10px
 * steps (real Playwright, not estimated) turned up a THIRD zone this file's two documented edges
 * (1124px, 1440px) never covered: from 1300px (where the `xlarge` band above ends and this
 * stylesheet's own 18px/15px "large" values in the rules above take over) up to roughly 1385px,
 * the row already overflows its viewport with NO caret gap at all, on `main` at this exact
 * commit -- 13px of overflow at 1300px, falling to 0 by ~1330px. This is not this dispatch's
 * defect: `git stash` confirmed the same overflow, same magnitude, with none of this pass's CSS
 * applied. It is named here rather than fixed because fixing it is not one of this dispatch's two
 * named bugs.
 *
 * IT WOULD HAVE BEEN MADE WORSE BY THE 7PX GAP, THOUGH, AND THAT PART IS THIS DISPATCH'S TO
 * PREVENT. Every has-child item's extra 7px compounds onto that pre-existing overflow the same
 * way it does everywhere else on this row, which measured as 41px of overflow at 1300px (13
 * pre-existing + 28 new) and did not fully clear until ~1390px -- dragging a completely
 * ordinary, extremely common laptop width (1366px, fine today) into visible horizontal overflow
 * it does not have on `main`. `margin-left: -14px` here is not a new value: it is THIS RULE'S OWN
 * PRE-FIX VALUE, restated for this one band so the pre-existing defect is reproduced exactly
 * rather than compounded -- the caret stays flush here, same as it already reads on `main` today,
 * until 1400px where the next rule's headroom is real (measured, not assumed: 1px of overflow
 * at 1380px, 0 at 1390px, so 1400px carries a real margin rather than sitting on the edge).
 *
 * SUPERSEDED 2026-09-24, THE SAME MODE SWITCH AS THE 1124px BAND ABOVE, FOR THE SAME REASON:
 * `.open-on-click` no longer occurs in this build, so the `-14px` rule below is dead and the
 * pre-existing 13px overflow this paragraph documents on `main` grew to 24px
 * (`document.documentElement.scrollWidth` 1324 against 1300px, real Playwright) once hover
 * mode's own small `margin-left: 0.15em` (2.7px at this band's 18px font) applied unchecked on
 * four has-child items with nothing pulling it back. The replacement below reclaims that same
 * ~11px the same way the 1124px band's does -- `margin-left: 0` on the merged toggle element --
 * which returns this band to its documented PRE-EXISTING 13px, not to zero: that 13px is still
 * not this dispatch's defect to fix, only not to worsen. CONFIRMED after the change:
 * `document.documentElement.scrollWidth` 1313 against a 1300px viewport -- 13px, matching the
 * pre-existing figure this paragraph already names.
 */
@media (min-width: 1300px) and (max-width: 1399.98px) {
	.wm-header .wp-block-navigation__container > .wp-block-navigation-item.has-child.open-on-click > .wp-block-navigation-submenu__toggle + .wp-block-navigation__submenu-icon {
		margin-left: -14px;
	}

	.wm-header .wp-block-navigation__container > .wp-block-navigation-item.has-child.open-on-hover-click > .wp-block-navigation-submenu__toggle.wp-block-navigation__submenu-icon {
		margin-left: 0;
	}
}

/*
 * THE COLLAPSE BREAKPOINT. core/navigation's `overlayMenu: mobile` is core's own
 * breakpoint, 600px (navigation/style.css, the two `@media (min-width: 600px)` blocks).
 * The source collapses the whole menu column somewhere above 1024px: the capture
 * measures a zero box for it at 1024, 768 and 390 and a live one at 1440. The value
 * taken is site.yml design_tokens `settings.viewport` tablet = 1123.98px, which is the
 * source's own `large` breakpoint read out of its compiled CSS (`max-width: 70.24875em`).
 * There is no attribute that moves core's 600px, so this is the scoped-stylesheet half
 * of the `overlayMenu` decision the contract records.
 */
@media (max-width: 1123.98px) {
	.wm-header .wp-block-navigation__responsive-container:not(.hidden-by-default):not(.is-menu-open) {
		display: none;
	}

	/* The hamburger is a 42x36 hit box in the source (measured, 1024/768/390), 24x24 in core. */
	.wm-header .wp-block-navigation__responsive-container-open {
		padding: 6px 9px;
		position: relative;
		top: 5px; /* offset only -- a margin here would make the row taller than the source's */
		color: var(--wp--preset--color--primary); /* the source's hamburger is red, three bars */
		/* Was 5px, snapped to spacing|20 (10px), 2026-09-25 (spacing-standard.md §1 item 3,
		   "standard wins") -- this now equals the <=639.98px override below, so the hamburger no
		   longer sits closer to the edge in the 640-1023px band than it does below 640px. */
		margin-right: var(--wp--preset--spacing--20);
		box-sizing: content-box;
	}

	.wm-header .wp-block-navigation__responsive-container-open:not(.always-shown) {
		display: flex;
	}
}

@media (max-width: 639.98px) {
	.wm-header .wp-block-navigation__responsive-container-open {
		margin-right: var(--wp--preset--spacing--20);
	}
}

/* The overlay's logo row (inc/header-overlay.php) exists at every width and shows only in an open overlay. */
.wm-header .wp-block-navigation-item:has(> .wm-header__overlay-logo) {
	display: none;
}

/* In the Site Editor the navigation's item list has no li wrapper, so the logo is a direct child of the container and the rule above never matches: the header showed two logos. The frontend logo sits inside the li, so this rule is editor-only. */
.wm-header .wp-block-navigation__container > .wm-header__overlay-logo {
	display: none;
}

/*
 * THE BURGER OVERLAY -- ADDED 2026-09-21. MEASURED on the live source (Playwright, computed, at
 * 1123, 768 and 390; jQuery read from themes/washington_mills/js/washington_mills.js and the rules
 * from its compiled washington_mills.css). Below the source's 70.25em (1124px) step a burger opens
 * the menu, and:
 *
 *   - the panel starts with the logo on the header's own row, the burger becomes a red X in the
 *     same place, then the five top-level items (18px/700/uppercase, 38px rows, left-aligned, at
 *     most 400px wide), a red CONTACT US button 20px below them, and the search field 16px under
 *     that as the last row;
 *   - a parent item has a red "+" (two 15x2 bars in a 50x35 hit box at the right of the row) that
 *     turns into a "-" while its list is open -- the whole rotation is one .3s transform;
 *   - every parent is a collapsed accordion, at every level: Products holds Core Technologies and
 *     All Products, each of which is a grey 15px uppercase heading with a "+" of its own, and All
 *     Products holds the 23 product links. jQuery slideToggle, 300ms; the panel itself 500ms;
 *   - the source's panel is in normal flow and pushes the page down, has no Escape, no focus
 *     handling and no scroll lock. Nothing else about it is a modal.
 *
 * WHAT IS BUILT. core/navigation's own overlay (`overlayMenu: mobile`) is the panel, so it brings the
 * behaviour the source lacks and the directives own: focus moves in on open and back to the burger
 * on close, Escape closes, Tab is trapped, `html.has-modal-open` locks the page, and every
 * submenu toggle is a real button whose `aria-expanded` core's Interactivity store drives. What
 * this block does is only paint it: core's overlay forces every submenu open and draws no
 * caret, so the accordion is CSS keyed on that same `aria-expanded`, and the "+"/"-" is drawn on
 * core's own caret element. Not identical, and named: the panel is FIXED and overlays the page
 * rather than pushing it (a scroll-locked modal cannot also be in flow, and a panel taller than
 * the viewport -- Products open is ~1,100px -- scrolls inside itself), and it fades in over
 * core's 0.1s where the source slides for 0.5s.
 */
@media (max-width: 1123.98px) {
	.wm-header {
		--wm-overlay-pad: 10px;
		interpolate-size: allow-keywords; /* lets height animate to auto where supported; snaps elsewhere */
	}

	/* The panel: white, top-anchored, as tall as its content up to the viewport. */
	.wm-header .wp-block-navigation.wp-block-navigation .wp-block-navigation__responsive-container.is-menu-open {
		top: 0;
		bottom: auto;
		height: auto;
		max-height: 100vh;
		max-height: 100dvh;
		padding: 0;
		background-color: var(--wp--preset--color--white);
		box-shadow: 0 0 8px rgba(0, 0, 0, 0.2);
	}

	.wm-header .wp-block-navigation.wp-block-navigation .wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation__responsive-container-content {
		padding: 0;
		display: block;
	}

	.wm-header .wp-block-navigation.wp-block-navigation .wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation__responsive-container-content .wp-block-navigation__container {
		display: flex;
		flex-direction: column;
		flex-wrap: nowrap;
		align-items: stretch;
		min-height: 0;
		gap: 0;
		/* The header row is 1100px centred above 1100px wide, so the panel's edge is the row's, not the viewport's. */
		padding: var(--wp--preset--spacing--25) max(var(--wm-overlay-pad), calc((100% - 1100px) / 2 + var(--wm-overlay-pad)));
		margin: 0;
	}

	/* The logo row: the header's own logo, at the header's own position and width. */
	.wm-header .wp-block-navigation.wp-block-navigation .wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation__responsive-container-content .wp-block-navigation__container > .wp-block-navigation-item:has(> .wm-header__overlay-logo) {
		display: block;
		width: calc(66.67vw - 2 * var(--wm-overlay-pad));
		max-width: 321px;
		margin: 0 0 var(--wp--preset--spacing--30);
		padding: 0;
		line-height: 0;
	}

	.wm-header .wp-block-navigation.wp-block-navigation .wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation__responsive-container-content .wm-header__overlay-logo img {
		display: block;
		width: 321px;
		max-width: 100%;
		height: auto;
	}

	/* A row: 38px, the label carrying the padding, 400px at most. */
	.wm-header .wp-block-navigation.wp-block-navigation .wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation__responsive-container-content .wp-block-navigation__container > .wp-block-navigation-item {
		position: relative;
		display: block;
		width: 100%;
		max-width: 400px;
		margin: 0;
		padding: 0;
		font-size: 18px;
		text-align: left;
	}

	.wm-header .wp-block-navigation.wp-block-navigation .wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation__responsive-container-content .wp-block-navigation-item__content {
		display: block;
		width: 100%;
		margin: 0;
		padding: var(--wp--preset--spacing--20) var(--wp--preset--spacing--25);
		font: inherit;
		letter-spacing: inherit;
		text-align: left;
		text-transform: inherit;
		color: var(--wp--preset--color--black);
		transition: color 0.3s;
	}

	.wm-header .wp-block-navigation.wp-block-navigation .wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation__responsive-container-content .wp-block-navigation-item__content:hover,
	.wm-header .wp-block-navigation.wp-block-navigation .wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation__responsive-container-content .wp-block-navigation-item__content:focus-visible {
		color: var(--wp--preset--color--primary);
	}

	/*
	 * "+" while closed, "-" while open: core's own caret element, redrawn.
	 *
	 * `pointer-events: none` REMOVED 2026-09-24, THE SAME DAY THE HEADER MOVED FROM
	 * `submenuVisibility: click` TO `hover`. In click mode `.wp-block-navigation__submenu-icon`
	 * was a decorative `<span>`, a SIBLING of the real toggle
	 * (`<button class="wp-block-navigation-item__content wp-block-navigation-submenu__toggle">`)
	 * that covered the whole row -- disabling pointer events on the span was inert there, the
	 * click landed on the button underneath regardless. In hover mode core folds the two into
	 * ONE element -- `<button class="wp-block-navigation__submenu-icon
	 * wp-block-navigation-submenu__toggle" data-wp-on--click="actions.toggleMenuOnClick">` -- so
	 * this same selector now names the only clickable toggle. Keeping `pointer-events: none` for
	 * a hover-mode build made this 50x35 box, the source's own "+/-" hit target, inert:
	 * confirmed with a real Playwright click landing a 30s timeout ("element is not visible,
	 * enabled and stable") before this fix, ok after. The label beside it is now a real `<a
	 * href>` (this same mode switch), so it correctly navigates instead of toggling; only the
	 * caret box opens the list, which is the source's own split behaviour.
	 */
	.wm-header .wp-block-navigation.wp-block-navigation .wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation__responsive-container-content .has-child > .wp-block-navigation__submenu-icon {
		position: absolute;
		top: 0;
		right: 0;
		display: block;
		width: 50px;
		height: 35px;
		margin: 0;
		padding: 0;
		color: var(--wp--preset--color--primary);
	}

	.wm-header .wp-block-navigation.wp-block-navigation .wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation__responsive-container-content .has-child > .wp-block-navigation__submenu-icon svg {
		display: none;
	}

	.wm-header .wp-block-navigation.wp-block-navigation .wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation__responsive-container-content .has-child > .wp-block-navigation__submenu-icon::before,
	.wm-header .wp-block-navigation.wp-block-navigation .wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation__responsive-container-content .has-child > .wp-block-navigation__submenu-icon::after {
		content: "";
		position: absolute;
		top: 50%;
		right: 17px;
		width: 15px;
		height: 2px;
		background-color: currentColor;
		transition: transform 0.3s;
	}

	.wm-header .wp-block-navigation.wp-block-navigation .wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation__responsive-container-content .has-child > .wp-block-navigation__submenu-icon::before {
		transform: rotate(90deg);
	}

	.wm-header .wp-block-navigation.wp-block-navigation .wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation__responsive-container-content .has-child > .wp-block-navigation-submenu__toggle[aria-expanded="true"] + .wp-block-navigation__submenu-icon::before,
	.wm-header .wp-block-navigation.wp-block-navigation .wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation__responsive-container-content .has-child > .wp-block-navigation-submenu__toggle.wp-block-navigation__submenu-icon[aria-expanded="true"]::before {
		transform: rotate(180deg);
	}

	/* The accordion: a list is closed until its own toggle says otherwise. */
	.wm-header .wp-block-navigation.wp-block-navigation .wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation__responsive-container-content .has-child > .wp-block-navigation__submenu-container {
		position: static;
		display: flex;
		flex-direction: column;
		gap: 0;
		width: auto;
		min-width: 0;
		height: 0;
		margin: 0;
		padding: 0;
		overflow: hidden;
		border: 0;
		background-color: var(--wp--preset--color--white);
		box-shadow: none;
		opacity: 1;
		visibility: hidden;
		transition: height 0.3s ease, margin 0.3s ease, visibility 0s linear 0.3s;
	}

	.wm-header .wp-block-navigation.wp-block-navigation .wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation__responsive-container-content .has-child > .wp-block-navigation-submenu__toggle[aria-expanded="true"] ~ .wp-block-navigation__submenu-container {
		height: auto;
		margin-bottom: var(--wp--preset--spacing--20);
		visibility: visible;
		transition-delay: 0s;
	}

	/* Nested rows: indented 15px a level, mixed case, tighter tracking. */
	.wm-header .wp-block-navigation.wp-block-navigation .wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation__responsive-container-content .wp-block-navigation__submenu-container > .wp-block-navigation-item {
		position: relative;
		display: block;
		width: 100%;
		margin: 0;
		padding: 0 0 0 var(--wp--preset--spacing--25);
		font-size: 18px;
	}

	.wm-header .wp-block-navigation.wp-block-navigation .wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation__responsive-container-content .wp-block-navigation__submenu-container > .wp-block-navigation-item > .wp-block-navigation-item__content {
		letter-spacing: -1.5px;
		text-transform: none;
	}

	/* A section heading: grey 15px caps, and it stays grey under the pointer. */
	.wm-header .wp-block-navigation.wp-block-navigation .wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation__responsive-container-content .wp-block-navigation__submenu-container > .wm-header__section-header > .wp-block-navigation-item__content {
		padding: var(--wp--preset--spacing--20) var(--wp--preset--spacing--40) var(--wp--preset--spacing--20) var(--wp--preset--spacing--25);
		font-size: 15px;
		letter-spacing: 0;
		text-transform: uppercase;
		color: var(--wp--preset--color--medium-gray);
		pointer-events: auto;
	}

	.wm-header .wp-block-navigation.wp-block-navigation .wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation__responsive-container-content .wp-block-navigation__submenu-container > .wm-header__section-header > .wp-block-navigation-item__content:hover {
		color: var(--wp--preset--color--medium-gray);
	}

	.wm-header .wp-block-navigation.wp-block-navigation .wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation__responsive-container-content .wp-block-navigation__submenu-container > .wm-header__section-header::before {
		content: none;
	}

	/* CONTACT US: the source's button, 20px under the last item. */
	.wm-header .wp-block-navigation.wp-block-navigation .wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation__responsive-container-content .wp-block-navigation-item.wm-header__cta-button > .wp-block-navigation-item__content {
		display: inline-block;
		width: auto;
		margin: var(--wp--preset--spacing--30) var(--wp--preset--spacing--50) 0 0;
		padding: var(--wp--preset--spacing--30) 0 var(--wp--preset--spacing--30) var(--wp--preset--spacing--40);
		font-size: 15px;
		letter-spacing: -0.5px;
		text-transform: uppercase;
		color: var(--wp--preset--color--white);
	}

	.wm-header .wp-block-navigation.wp-block-navigation .wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation__responsive-container-content .wp-block-navigation-item.wm-header__cta-button > .wp-block-navigation-item__content:hover,
	.wm-header .wp-block-navigation.wp-block-navigation .wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation__responsive-container-content .wp-block-navigation-item.wm-header__cta-button > .wp-block-navigation-item__content:focus-visible {
		color: var(--wp--preset--color--white);
	}

	/* The search row: the last row, the full width of the panel. */
	.wm-header .wp-block-navigation.wp-block-navigation .wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation__responsive-container-content .wp-block-navigation__container > .wm-header__search-item {
		max-width: none;
	}

	/* The X where the burger was: same box, same place, drawn in the source's red. */
	.wm-header .wp-block-navigation.wp-block-navigation .wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation__responsive-container-close {
		top: 20px;
		right: 20px;
		width: 42px;
		height: 36px;
		padding: 0;
		color: var(--wp--preset--color--primary);
	}

	.wm-header .wp-block-navigation.wp-block-navigation .wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation__responsive-container-close svg {
		display: none;
	}

	.wm-header .wp-block-navigation.wp-block-navigation .wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation__responsive-container-close::before,
	.wm-header .wp-block-navigation.wp-block-navigation .wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation__responsive-container-close::after {
		content: "";
		position: absolute;
		top: 12px;
		left: 0;
		width: 35px;
		height: 4px;
		background-color: currentColor;
		transform: rotate(135deg);
	}

	.wm-header .wp-block-navigation.wp-block-navigation .wp-block-navigation__responsive-container.is-menu-open .wp-block-navigation__responsive-container-close::after {
		transform: rotate(-135deg);
	}

	/* The burger: the source's three red bars, 25, 30 and 35px wide, not core's three equal ones. */
	.wm-header .wp-block-navigation__responsive-container-open {
		position: relative;
		width: 24px;
		height: 24px;
	}

	.wm-header .wp-block-navigation__responsive-container-open svg {
		display: none;
	}

	.wm-header .wp-block-navigation__responsive-container-open::before {
		content: "";
		position: absolute;
		top: 0;
		left: 0;
		width: 42px;
		height: 36px;
		background:
			linear-gradient(currentColor, currentColor) 0 0 / 25px 4px no-repeat,
			linear-gradient(currentColor, currentColor) 0 11px / 30px 4px no-repeat,
			linear-gradient(currentColor, currentColor) 0 23px / 35px 4px no-repeat;
	}
}

@media (min-width: 640px) and (max-width: 1123.98px) {
	.wm-header {
		--wm-overlay-pad: 15px;
	}
}

@media (min-width: 1124px) {
	/*
	 * THE PANEL IS LAID OUT AT REST AND HIDDEN BY SOMETHING THAT PRESERVES GEOMETRY.
	 * That is a measured property of the source, not a preference: the capture reports
	 * real boxes for the Products panel (815x40 at y=78) and for both of its section
	 * columns (203x114, 557x484) while the header is at rest, which only happens when the
	 * panel is painted out with visibility/opacity rather than removed from layout. Core
	 * hides it with `width: 0; height: 0; overflow: hidden` on top of `visibility:
	 * hidden` (navigation/style.css, `.has-child .wp-block-navigation__submenu-container`),
	 * so core's panel has no box at rest and the source's does. Only the three
	 * layout-suppressing declarations are lifted; visibility and opacity are left to
	 * core, which is what still hides it.
	 */
	.wm-header .wp-block-navigation .has-child .wp-block-navigation__submenu-container {
		width: auto;
		height: auto;
		min-width: 0;
		overflow: visible;
	}

	/*
	 * SHADOW RE-READ 2026-09-20 FROM THE LIVE SOURCE (probe of the open panel, computed on
	 * `ul.menu` inside `li.menu-item--expanded`): `box-shadow: rgba(0,0,0,0.1) 0 0 10px 1px`, no
	 * border, white fill. The value below is that measurement and replaces the borrowed
	 * `0 0 7px 0 rgba(0,0,0,0.2)` the next paragraph describes; core's own 1px border on a
	 * panel is removed for the same reason.
	 *
	 * PANEL CHROME -- ADDED 2026-09-13. At rest the Products/Services/Resources panels paint
	 * with no visual separation from the page: no border, background, or shadow distinct
	 * from the white page behind them. There is no measured source value for this (never
	 * captured), so rather than invent one this reuses the ONE elevation treatment already
	 * measured and repeated across this theme's own card/tile surfaces --
	 * `box-shadow: 0 0 7px 0 rgba(0, 0, 0, 0.2)` -- carried verbatim in
	 * patterns/link-list.php, patterns/product-teaser-card.php, patterns/section-menu.php
	 * and patterns/block-menu.php, one of which (link-list) has it as a MEASURED source
	 * value on a card rather than a guess. No border and no radius are added, because none
	 * of those four reused instances carries one either -- matching the convention means
	 * matching all of it, not the parts that are convenient.
	 *
	 * SCOPED TO THE OUTERMOST PANEL ONLY -- `.wp-block-navigation__container` direct child
	 * `.has-child`, direct child `.submenu-container` -- and not to the nested Core
	 * Technologies/Laboratory Services/Guides lists one level further in. Those are reached
	 * only by the descendant-combinator rule below ("A SECTION'S OWN LINKS ARE ALWAYS SHOWN
	 * INSIDE AN OPEN PANEL"), which deliberately keeps them transparent and unbordered so
	 * they read as part of the panel they sit inside rather than as a panel of their own;
	 * giving them this same shadow would double it up one level in.
	 */
	.wm-header .wp-block-navigation__container > .has-child > .wp-block-navigation__submenu-container {
		background-color: #fff;
		box-shadow: 0 0 10px 1px rgba(0, 0, 0, 0.1);
		border: 0;
	}

	/*
	 * A TOP-LEVEL PANEL THAT CONTAINS SECTIONS IS A ROW OF SECTIONS. Measured on
	 * Products: "Core Technologies" at x=469 (203 wide) and "All Products" at x=672
	 * (557 wide) sit side by side and add up to 760, ending at 1229 — the right edge of
	 * the menu column.
	 *
	 * CORRECTED 2026-09-12 — "CONTAINS A SECTION" IS NOT "IS A ROW OF SECTIONS", AND
	 * `:has(> .has-child)` ALONE TESTED ONLY THE FORMER. Products' panel qualifies both
	 * ways — every one of its children (Core Technologies, All Products) is itself a
	 * section — but Services and Resources each contain one nested trigger too
	 * (Laboratory Services, Guides) ALONGSIDE several plain sibling links, so the old test
	 * put those plain links into the same flex row as the section, each becoming its own
	 * single-item column: the confirmed defect on Services (New Product Development
	 * Services / Recycling / UAMA Standard Sands Supplier rendering as three cramped
	 * columns, "Recycling" wrapping mid-word inside one too narrow for it). The added
	 * `:not(:has(> …:not(.has-child)))` requires EVERY child to be a section before the
	 * row treatment applies — true for Products, false for Services and Resources, which
	 * now fall through to a plain vertical stack. No source geometry was ever captured
	 * for the Services/Resources panels (`ai/reference/` — forbidden here regardless),
	 * so this is a structural-soundness fix, not a fit to a measured width.
	 *
	 * `.wm-header__view-all` IS A SECOND ADMITTED EXCEPTION -- ADDED 2026-09-22 alongside the
	 * new "Products" escape-hatch link (ai/import/import-menus.php, first child of this same
	 * panel). That link is a plain `core/navigation-link`, not `.has-child`, so without this
	 * clause its mere presence would fail "every child is a section" and drop the whole
	 * Products panel back to a vertical stack -- a real regression this exact rule would
	 * otherwise cause, not a hypothetical. `:not(.has-child):not(.wm-header__view-all)` reads
	 * "a plain link that is not the view-all escape hatch", so Core Technologies and All
	 * Products still fail the check if a genuine plain link is ever added beside them, and only
	 * this one, named, escape-hatch class is let through.
	 */
	.wm-header .wp-block-navigation__container > .has-child > .wp-block-navigation__submenu-container:has(> .has-child):not(:has(> .wp-block-navigation-item:not(.has-child):not(.wm-header__view-all))) {
		flex-direction: row;
		flex-wrap: wrap;
		align-items: flex-start;
		/* The mega panel sizes to its content, right-anchored to the menu column; the plain
		   dropdowns below are a fixed 200px. Measured on the source: Products 815 wide with
		   padding 20px 10px, top 47.5px inside the 57px menu row (= y 77.5). */
		/* max-content, not auto: an absolutely-positioned box with `auto` width shrinks to the
		   containing block (the 770px menu <ul>), which is what wrapped the list to one column. */
		width: max-content;
		max-width: calc(100vw - 32px);
		padding: var(--wp--preset--spacing--30) var(--wp--preset--spacing--20);
		left: auto;
		right: 0;
		top: 47.5px;
	}

	/*
	 * THE VIEW-ALL ESCAPE HATCH READ AS A STRAY, DISCONNECTED COLUMN IN A ROW-OF-SECTIONS PANEL --
	 * FIXED 2026-09-22. Screenshot evidence (this dispatch's own hand-back): opening Products
	 * showed "Products" sitting alone in a narrow column of one, to the left of "CORE
	 * TECHNOLOGIES" and "ALL PRODUCTS", because the row rule above lays its children out as flex
	 * columns and a plain `core/navigation-link` sized to its own short content becomes exactly
	 * that -- a column one item tall and as narrow as the word "Products".
	 *
	 * `flex-basis: 100%` ON THE LINK PLUS `flex-wrap: wrap` ON THE ROW ABOVE turns it into a
	 * full-width bar that the two section columns wrap below, rather than a third column beside
	 * them -- the "distinctly-styled element … spanning full width" strategy, not "first item
	 * inside an existing column": Products' own escape hatch has no natural column to nest inside
	 * (it points at the parent page, not at Core Technologies or All Products specifically), so
	 * making it its own CTA row reads as intentional where forcing it under either column's own
	 * heading would not. The type treatment (bold, `primary` red, uppercase, a bottom rule)
	 * borrows this row's own top-level trigger colour and this panel's own section-heading
	 * uppercase convention (`wm-header__section-header`'s rule further down) rather than
	 * inventing a third type style for this one link.
	 *
	 * SCOPED TO THE EXACT SAME SELECTOR AS THE ROW RULE ABOVE, not to `.wm-header__view-all`
	 * generally: Services, Resources and Company's own escape-hatch links (and the nested
	 * Laboratory Services / Guides flyouts) sit in a plain vertical stack, not a row, and were
	 * checked with a real screenshot after this pass -- none of them show the stray-column defect
	 * this rule exists to fix, so none of them get this treatment; giving a plain vertical list's
	 * first row a bottom rule it does not need would be an unrequested style change outside this
	 * fix's own two named defects.
	 */
	.wm-header .wp-block-navigation__container > .has-child > .wp-block-navigation__submenu-container:has(> .has-child):not(:has(> .wp-block-navigation-item:not(.has-child):not(.wm-header__view-all))) > .wp-block-navigation-item.wm-header__view-all {
		flex: 1 0 100%;
		width: 100%;
		margin-bottom: var(--wp--preset--spacing--20);
		padding-bottom: var(--wp--preset--spacing--20);
		border-bottom: 1px solid var(--wp--preset--color--light-gray);
	}

	.wm-header .wp-block-navigation__container > .has-child > .wp-block-navigation__submenu-container:has(> .has-child):not(:has(> .wp-block-navigation-item:not(.has-child):not(.wm-header__view-all))) > .wp-block-navigation-item.wm-header__view-all > .wp-block-navigation-item__content {
		display: inline-block;
		padding: 0;
		font-weight: 700;
		text-transform: uppercase;
		letter-spacing: 0;
		color: var(--wp--preset--color--primary);
		font-size: var(--wp--preset--font-size--small);
	}

	/*
	 * A SECTIONED PANEL IS ALIGNED TO THE MENU, NOT TO THE ITEM THAT OPENS IT. Measured:
	 * the Products panel's two sections run 469..1229, and 1229 is the right edge of the
	 * menu column's content box — not the right edge of the "Products" item, which sits
	 * at 588. core positions a submenu against its own <li> (`items-justified-right`
	 * gives it `right: 0`, navigation/style.css), which put an 837px panel at x=-249,
	 * off the left of the viewport. Taking the <li> out of the positioning chain for
	 * these panels only, and making the menu container the containing block, is what
	 * reproduces the source's alignment; a plain dropdown with no sections keeps core's
	 * item-relative positioning.
	 *
	 * THE PANEL'S TOP IS NOT RECONCILED AND IS NOT GUESSED. core puts it at the
	 * container's bottom edge (`top: 100%`, y=103 here); the source measures y=78, which
	 * is 9px above the bottom of the 30..87 menu row, so the source overlaps the row by
	 * some amount nothing in this contract explains. That is one of the things the
	 * missing driven capture of the open state would answer.
	 */
	.wm-header .wp-block-navigation__container {
		position: relative;
	}

	/*
	 * CORRECTED 2026-09-13 -- THIS RULE TOOK EVERY PANEL WITH A NESTED TRIGGER OUT OF ITS OWN
	 * TRIGGER'S POSITIONING CHAIN, NOT ONLY THE ROW-OF-SECTIONS ONE THE COMMENT BELOW WAS
	 * MEASURED AGAINST. That comment ("A SECTIONED PANEL IS ALIGNED TO THE MENU, NOT TO THE
	 * ITEM") is about PRODUCTS ONLY -- panel 469..1229, right edge flush to the MENU
	 * CONTAINER's own right edge, which is what taking the <li> out of the chain and making
	 * the container the containing block reproduces. But the selector this shipped on --
	 * ":has(> .wp-block-navigation__submenu-container > .has-child)" -- reads "this panel
	 * contains a nested trigger ANYWHERE", which is equally true of Services (Laboratory
	 * Services) and Resources (Guides): neither is a row of sections, both are a plain
	 * vertical stack with one nested item among several plain sibling links. Once their own
	 * <li> stopped being the containing block, their panel's `right: 0` (core's own
	 * items-justified-right rule, navigation/style.css) resolved against the CONTAINER's
	 * right edge instead of their own trigger's, dragging both rightward.
	 *
	 * MEASURED 2026-09-13 with probe.js against the running build, each opened with
	 * `--do=click:button[aria-label="… submenu"]`: Services' trigger sits at x=603..692 and
	 * its panel rendered at x=886..1229 -- 283px clear of its own trigger, under
	 * "Resources"/"Company" instead. Resources' trigger sits at x=857..964 and its panel
	 * rendered at x=884..1229 -- only 27px off, which is why it read as nearly fine and was
	 * easy to miss, but it is the same wrong containing block, not a second, milder bug.
	 *
	 * THE FIX REUSES THE EXISTING "ROW OF SECTIONS" TEST BELOW RATHER THAN INVENTING A SECOND
	 * ONE, WITH ONE MECHANICAL DIFFERENCE THE FIRST ATTEMPT AT THIS GOT WRONG AND WHICH IS
	 * WORTH RECORDING. The row rule below applies its two `:has()`/`:not(:has())` clauses
	 * directly to the SUBMENU-CONTAINER, as siblings on one compound selector -- valid CSS.
	 * Wrapping that same pair inside a THIRD, outer `:has()` on the <li> (so the <li> itself
	 * could be qualified in one step) is `:has()` nested inside `:has()`, which the Selectors
	 * spec disallows outright: a relative selector list passed to `:has()` may not itself
	 * contain `:has()`. That version shipped, matched NOTHING at all -- not "nothing new",
	 * literally zero elements, Products included -- because an invalid selector drops the
	 * whole rule rather than erroring, so Products silently lost its `position: static` too
	 * and regressed to core's default (LI-relative) positioning, measured at x=-182, off the
	 * left edge of the viewport. CAUGHT by re-measuring Products with probe.js immediately
	 * after this change, which is why every fix in this pass was re-verified against the
	 * running build rather than trusted from the CSS alone.
	 *
	 * THE WORKING FORM keeps both `:has()` calls independent -- neither nested inside the
	 * other, each reaching two levels down from the <li> itself rather than one level down
	 * from the submenu-container: "has a child submenu-container whose child is a section"
	 * AND "does not have a child submenu-container whose child is a plain link". Same
	 * semantics as the row rule's own pair, applied one level higher.
	 *
	 * Products keeps exactly the behaviour it already had -- it passed the old broad
	 * selector and passes this narrower one too. Services and Resources now keep
	 * `position: relative` on their own trigger <li>, which is core's own default and was
	 * never the thing that needed changing, so their panel's `right: 0` resolves against
	 * THEIR OWN <li> and lands under its own trigger. There is no measured source geometry
	 * for either panel to fit instead (never captured) -- this is the structural requirement
	 * ("sits under its own trigger, does not drift"), not a pixel fit.
	 *
	 * `.wm-header__view-all` IS THE SAME ADMITTED EXCEPTION AS THE ROW RULE ABOVE, AND THIS
	 * SELECTOR NEEDED IT TOO -- FOUND 2026-09-22 BY RE-MEASURING, NOT BY READING THE CSS.
	 * Adding the new "Products" escape-hatch link (`ai/import/import-menus.php`) without this
	 * clause made Products fail "does not have a plain-link child" exactly like Services and
	 * Resources always have, dropping it back to `position: relative` on its own <li> -- which
	 * un-does the fix this whole rule exists for. MEASURED, with only the row rule above fixed
	 * and this one not yet: the panel's `right: 0` resolved against the "Products" <li> (right
	 * edge x=590) instead of the menu container (right edge x=1229), rendering the panel at
	 * x=-538, off the left edge of a 1440px viewport -- the same failure mode this rule's own
	 * history above already describes for a different cause. The two selectors have to move
	 * together: one decides whether the PANEL lays out as a row, the other decides what its
	 * `right: 0` resolves against, and a plain escape-hatch link is invisible to neither.
	 */
	.wm-header .wp-block-navigation__container > .has-child:has(> .wp-block-navigation__submenu-container > .has-child):not(:has(> .wp-block-navigation__submenu-container > .wp-block-navigation-item:not(.has-child):not(.wm-header__view-all))) {
		position: static;
	}

	/*
	 * A SECTION'S OWN LINKS ARE ALWAYS SHOWN INSIDE AN OPEN PANEL — they are not a second
	 * disclosure. Measured: both of Products' sections have their children laid out at
	 * rest ("All Products" is 484 tall with its 23 items starting at y=128), so the panel
	 * reveals everything at once. Core would make each section a hover target of its own.
	 * `visibility`/`opacity` are inherited so the section list appears and disappears
	 * with the panel that contains it, and core's absolute flyout positioning
	 * (`left: 100%; top: -1px`) is dropped.
	 */
	.wm-header .wp-block-navigation .wp-block-navigation__submenu-container .has-child.wm-header__section-header > .wp-block-navigation__submenu-container {
		position: static;
		visibility: inherit;
		opacity: inherit;
		background: transparent;
		border: 0;
		color: inherit;
	}

	/*
	 * 23 ITEMS IN TWO COLUMNS, 2 ITEMS IN ONE. Measured: the All Products list is 484
	 * tall, which at ~40px a row is 12 rows, and its items are reported in a two-column
	 * arrangement; Core Technologies' two items are one column 203 wide. A 12-row grid
	 * flowing into columns produces both from the same rule, and the column width is left
	 * to content rather than pinned, because only All Products' item width (270) was
	 * measured and Core Technologies' (139, 141) disagrees with it.
	 */
	.wm-header .wp-block-navigation .wp-block-navigation__submenu-container .has-child.wm-header__section-header > .wp-block-navigation__submenu-container {
		display: grid;
		grid-auto-flow: column;
		grid-template-rows: repeat(12, auto);
		grid-auto-columns: max-content;
	}

	/*
	 * THE ALL PRODUCTS LIST IS A LIVE QUERY OF ~44 PRODUCTS, NOT THE 23 CURATED ITEMS THE GRID
	 * ABOVE WAS SIZED FOR -- ADDED 2026-09-20. `repeat(12, auto)` with `max-content` columns turns
	 * 44 items into four columns as wide as their longest name and a 1,607px panel that ran 377px
	 * off the left edge of a 1440px viewport (MEASURED, Playwright, build, 1440: panel box
	 * x=-377 w=1607; the same at 1280 was x=-457). Columns are now CSS multi-column with a fixed
	 * count of 3 at the source's own measured item width (270px: `li` 269.75 wide in the source's
	 * 557px two-column list), which balances any number of products across the columns instead
	 * of encoding how many there are, and never exceeds 3 x 270 = 810 however many products the
	 * query returns. Core Technologies keeps the grid (two items, one column).
	 */
	.wm-header .wp-block-navigation .wp-block-navigation__submenu-container .has-child.wm-header__no-link > .wp-block-navigation__submenu-container {
		display: block;
		columns: 3 270px;
		column-gap: 0;
		width: 810px;
		grid-template-rows: none;
	}

	.wm-header .wp-block-navigation .has-child.wm-header__no-link > .wp-block-navigation__submenu-container > .wp-block-navigation-item {
		display: block;
		break-inside: avoid;
	}

	/*
	 * NARROW DESKTOP: THE MENU'S RIGHT EDGE MOVES IN WITH THE VIEWPORT, AND THE PANEL IS
	 * ANCHORED TO IT. MEASURED (Playwright, build, pointer parked in the open Products panel):
	 * at 1124 the menu column ends at x=1025, and a 1034px panel therefore started at x=-9 and
	 * added 32px of horizontal page scroll. 3 x 240 columns make the panel 943px, which starts
	 * at x=82 at 1124 -- the same three-column shape, tighter. From 1280 up the 270px columns fit
	 * with room to spare (x=115 at 1280).
	 */
	@media (max-width: 1279.98px) {
		.wm-header .wp-block-navigation .wp-block-navigation__submenu-container .has-child.wm-header__no-link > .wp-block-navigation__submenu-container {
			columns: 3 240px;
			width: 720px;
		}
	}

	/*
	 * CORRECTED 2026-09-12 — THIS RULE HID THE LABEL, NOT THE CARET, ON EVERY NESTED
	 * TRIGGER EXCEPT THE TWO SECTION HEADINGS. Verified against the live DOM (`curl
	 * http://127.0.0.1:8000/ | grep`, both "Core Technologies" and "Laboratory Services"):
	 * in `submenuVisibility: click` mode there is no separate caret-only toggle button left
	 * to hide. The label and the toggle are the SAME element —
	 *
	 *   <button class="wp-block-navigation-item__content wp-block-navigation-submenu__toggle">
	 *     <span class="wp-block-navigation-item__label">Laboratory Services</span>
	 *   </button>
	 *   <span class="wp-block-navigation__submenu-icon"><svg>...</svg></span>
	 *
	 * identically for a section heading and for an ordinary nested trigger. So
	 * `display: none` on `.wp-block-navigation-submenu__toggle` deletes the whole button —
	 * label included — and excluding `.wm-header__section-header` only protected "Core
	 * Technologies" and "All Products" from that, which is why every OTHER nested trigger
	 * (Laboratory Services, Guides) rendered as a bare, unlabelled chevron: none of them
	 * carry that class, so none of them were excluded. The rule is removed rather than
	 * re-scoped — nothing in this panel needs the toggle BUTTON hidden. The caret those two
	 * items still need hidden is the separate `.wp-block-navigation__submenu-icon` span
	 * below, which the structural rule further down now hides for every nested trigger
	 * alike, not just these two.
	 */

	/*
	 * PANEL ITEM TYPE AND SPACING -- ADDED 2026-09-20, every value read off the live source's open
	 * panels (Playwright, computed, 1440x900): an item's `a` is 17px / weight 700 / line-height
	 * 17px / letter-spacing -1.5px / text-transform none, padding 10px 15px (30px on the right
	 * where the item has a submenu). The build's panel items inherited the nav's own
	 * `uppercase` + -0.5px letter-spacing from the block's typography attributes and core's
	 * `0.5em 1em` padding, so every panel read as shouting capitals in a wider, taller box than
	 * the source's. This sits BEFORE the section-heading rule below on purpose: both are six
	 * classes deep and the later one wins, and the headings are the exception.
	 */
	.wm-header .wp-block-navigation .has-child .wp-block-navigation__submenu-container > .wp-block-navigation-item > .wp-block-navigation-item__content {
		font-size: 17px;
		line-height: 17px;
		letter-spacing: -1.5px;
		text-transform: none;
		padding: var(--wp--preset--spacing--20) var(--wp--preset--spacing--25);
	}

	/*
	 * OPEN ON HOVER -- ADDED 2026-09-20, and it is why the operator saw "nothing in these
	 * dropdowns". MEASURED on the live source at 1440x900 (Playwright, no click issued): moving
	 * the pointer onto "Services" takes its panel from height 0 / opacity 0 to 246px / opacity 1,
	 * the panel stays open while the pointer moves down into it, and it closes when the pointer
	 * leaves; a CLICK on the trigger navigates to its page instead of toggling. The build was
	 * `submenuVisibility: click`, so hovering did nothing at all -- measured: panel
	 * visibility hidden / opacity 0 after 800ms of hover on the build, opening only on a click.
	 *
	 * THE CONTRACT'S `submenuVisibility: click` IS CONTRADICTED BY THIS MEASUREMENT (it was
	 * derived from the Drupal theme's `.toggle-menu` click handler, which serves the mobile
	 * drawer; the desktop reveal is a hover) and is left as written in the part -- `click`
	 * is still what puts a real <button> with `aria-expanded` on each trigger, which the hover
	 * rule below deliberately rides on top of rather than replaces: touch and keyboard users keep
	 * a toggle, the mouse gets the source's behaviour. `:has(:focus-visible)` and not
	 * `:focus-within`, because a click focuses the trigger and `:focus-within` would then hold
	 * the panel open after the pointer left.
	 */
	.wm-header .wp-block-navigation .has-child:hover > .wp-block-navigation__submenu-container,
	.wm-header .wp-block-navigation .has-child:has(> .wp-block-navigation-item__content:focus-visible) > .wp-block-navigation__submenu-container {
		visibility: visible;
		opacity: 1;
	}

	/*
	 * A PLAIN DROPDOWN (Services, Resources, Company) IS 200px WIDE, LEFT-ALIGNED TO ITS OWN
	 * TRIGGER, FLUSH UNDER IT. Measured on the source: `ul.menu` 200px wide at x = its <li>'s
	 * left edge (583, 848, 982), top 38px = the <li>'s own height, padding 15px 10px, shadow as
	 * above. Core's `items-justified-right` puts a panel's RIGHT edge on its <li>'s right edge
	 * instead, which is what dragged Services 283px away from its trigger before this pass.
	 * The mega panel (Products) overrides the width and the anchor in its own rule above.
	 */
	.wm-header .wp-block-navigation.items-justified-right .wp-block-navigation__container > .has-child > .wp-block-navigation__submenu-container {
		width: 200px;
		padding: var(--wp--preset--spacing--25) var(--wp--preset--spacing--20);
		left: 0;
		right: auto;
		top: 100%;
	}

	/*
	 * A NESTED FLYOUT (Laboratory Services under Services, Guides under Resources) OPENS TO THE
	 * RIGHT OF ITS ITEM ON HOVER, with the red chevron the source draws. Measured on the source:
	 * the flyout is 200 wide at x = its item's right edge (773), y = 81 against the item's 93.
	 * The earlier rules in this file flattened EVERY nested trigger into an always-open list,
	 * which is right for the two Products sections (their lists are permanently shown in the
	 * source) and wrong for these two; they are now scoped to `.wm-header__section-header`.
	 * Core sends a nested panel LEFT under `items-justified-right`, hence the explicit reset.
	 */
	.wm-header .wp-block-navigation.items-justified-right .wp-block-navigation__container .has-child .wp-block-navigation__submenu-container > .has-child:not(.wm-header__section-header) > .wp-block-navigation__submenu-container {
		left: 100%;
		right: auto;
		top: -12px;
		width: 200px;
		padding: var(--wp--preset--spacing--25) var(--wp--preset--spacing--20);
		background-color: #fff;
		box-shadow: 0 0 10px 1px rgba(0, 0, 0, 0.1);
		border: 0;
	}

	.wm-header .wp-block-navigation__submenu-container > .wp-block-navigation-item.has-child:not(.wm-header__section-header) > .wp-block-navigation__submenu-icon {
		color: var(--wp--preset--color--primary);
		margin: 0 var(--wp--preset--spacing--25) 0 auto;
		align-self: center;
	}

	/* The source's chevron is a bold red 10x14 glyph; core's is a 12px 1.5px-stroke hairline that
	   read as grey at this size. The path carries its own `stroke-width` attribute, so the
	   override has to name the path -- a value set on the <svg> would be inherited and lose. */
	.wm-header .wp-block-navigation__submenu-container > .wp-block-navigation-item.has-child:not(.wm-header__section-header) > .wp-block-navigation__submenu-icon svg {
		width: 14px;
		height: 14px;
	}

	.wm-header .wp-block-navigation__submenu-container > .wp-block-navigation-item.has-child:not(.wm-header__section-header) > .wp-block-navigation__submenu-icon svg path {
		stroke-width: 2.5px;
	}

	/*
	 * TWO PRODUCTS-SUBMENU ITEMS ARE SECTION HEADINGS, NOT DESTINATIONS. Source CODE
	 * scss/modules/_menu_block.scss:89-98 — a `.section-header` reads `text-transform:
	 * uppercase`, `color: $medium-gray`, `font-size: rem-calc(15)`, `letter-spacing: 0`,
	 * `padding-top: 5px`. Both read off this theme's OWN tokens rather than new values:
	 * theme.json's palette carries `medium-gray` at #8a8a8a — the same source Sass
	 * variable name, not a coincidence — and its fontSizes carry `small` at 1rem (16px),
	 * one pixel from the source's 15px and the closest rung on the ladder (`medium` is
	 * 20px, five off). Written as the preset var, not the resolved number, so a token
	 * change elsewhere in the theme still reaches this rule.
	 *
	 * className lands on the <li> (`get_block_wrapper_attributes()` in
	 * render_block_core_navigation_submenu()), so the label itself is reached via the
	 * content element under it — `<button>` in click mode (both items have children) or
	 * `<a>`, whichever core emits, hence targeting `.wp-block-navigation-item__content`
	 * rather than the tag name.
	 *
	 * SPECIFICITY IS NOT INCIDENTAL HERE, MEASURED AFTER THE FIRST VERSION OF THIS RULE
	 * SILENTLY LOST ITS OWN `padding-top`. navigation/style.css:219-222 sets `padding: 0.5em
	 * 1em` on `.wp-block-navigation .has-child .wp-block-navigation__submenu-container >
	 * .wp-block-navigation-item > .wp-block-navigation-item__content` — five class
	 * selectors. A four-class version of this rule (`.wm-header .wp-block-navigation-item.
	 * wm-header__section-header > .wp-block-navigation-item__content`) computed
	 * `padding-top: 8px` (0.5em at this rule's own 16px font-size), not 5px: core's rule
	 * won on specificity alone, in a stylesheet the theme itself enqueues, regardless of
	 * source order. The chain below adds the real ancestors, `.wp-block-navigation` and
	 * `.wp-block-navigation__submenu-container >`, both true of this DOM location, to reach
	 * six and win outright rather than tie.
	 */
	.wm-header .wp-block-navigation .wp-block-navigation__submenu-container > .wp-block-navigation-item.wm-header__section-header > .wp-block-navigation-item__content {
		text-transform: uppercase;
		color: var(--wp--preset--color--medium-gray);
		font-size: var(--wp--preset--font-size--small);
		letter-spacing: 0;
		padding-top: var(--wp--preset--spacing--20);
	}

	/*
	 * "ALL PRODUCTS" DOES NOT NAVIGATE -- RESTORED 2026-09-22, REVERTING THE PRIOR CHANGE HERE.
	 * The source's own `&.no-link { pointer-events: none }` (scss/modules/_menu_block.scss:89-91)
	 * disables this exact link on the live source despite its real `/products` href, and this
	 * rule reproduces that faithfully. It was removed for one build (be3a77d, 2026-09-22 morning)
	 * on the theory that a real, non-placeholder url whose children are already shown with no
	 * click needed should navigate regardless of the source; the operator corrected that same day
	 * -- "Core Technologies" and "All Products" are both pure section headings, not destinations,
	 * and neither should be clickable, matching the source rather than deviating from it. See
	 * `inc/header-overlay.php`'s own comment at the same date for the corresponding PHP revert:
	 * the button-to-anchor swap that made this href reachable is gone, so this rule is restored to
	 * disable it again rather than leaving a dead anchor with nothing to stop it navigating.
	 */
	.wm-header .wp-block-navigation-item.wm-header__no-link > .wp-block-navigation-item__content {
		pointer-events: none;
	}

	/*
	 * THE MEGA-PANEL COLUMN DIVIDER -- this unit's own `chrome` key,
	 * `mega-menu-column-divider`. `.wm-header__no-link` already uniquely selects "All
	 * Products" (the only item that carries it, per the rule directly above), so no new
	 * class is added for this. CODE: scss/modules/_menu_block.scss:243-256 --
	 * `li.two-column { &:before { content:''; height:100%; width:1px; background:$black;
	 * position:absolute; z-index:1; left:-8px } }`. CONFIRMED LIVE with
	 * `probe.js --pseudo=before` against `li.two-column`: 1px x 484px (the panel column's own
	 * full height), rgb(0, 0, 0), left:-8px. `height:100%` is written as the computed value
	 * rather than a hardcoded 484px, because this LI's own height is already its content's
	 * auto height via the `flex-direction:column` rule below, so the two stay in step without
	 * a second number to keep in sync.
	 */
	.wm-header .wp-block-navigation-item.wm-header__no-link {
		position: relative;
	}

	.wm-header .wp-block-navigation-item.wm-header__no-link::before {
		content: "";
		position: absolute;
		top: 0px;
		left: -8px;
		width: 1px;
		height: 100%;
		background-color: var(--wp--preset--color--black);
		z-index: 1;
	}

	/*
	 * THE CHEVRON IS A SEPARATE ELEMENT FROM THE TOGGLE IN CLICK MODE. In the anchor branch
	 * (hover mode) the icon and the toggle are one `<button class="wp-block-navigation__
	 * submenu-icon wp-block-navigation-submenu__toggle">`; in the button branch (click mode,
	 * navigation-submenu.php) `has_submenu` appends a SEPARATE `<span class="wp-block-
	 * navigation__submenu-icon">` after the content button, carrying neither
	 * `wp-block-navigation-item__content` nor `wp-block-navigation-submenu__toggle`.
	 *
	 * MADE STRUCTURAL 2026-09-12, REACHING EVERY NESTED TRIGGER RATHER THAN THE TWO SECTION
	 * HEADINGS BY NAME. "A SECTION'S OWN LINKS ARE ALWAYS SHOWN INSIDE AN OPEN PANEL" above
	 * (`.wm-header .wp-block-navigation .wp-block-navigation__submenu-container .has-child >
	 * .wp-block-navigation__submenu-container`) already makes ANY `.has-child` nested inside
	 * a submenu-container render its own children permanently — `visibility: inherit`,
	 * `position: static` — instead of as a second click-to-open disclosure, and that rule is
	 * unscoped: it reaches Laboratory Services and Guides exactly as it reaches Core
	 * Technologies and All Products. So a chevron promising a further click on any of them is
	 * false — their contents are already showing, unconditionally, the moment the panel above
	 * them is open. Scoped to `.wm-header__section-header` alone, this rule left a
	 * live-looking, non-functional chevron on Laboratory Services and Guides. The qualifier is
	 * `> .has-child` on a submenu-container — the same structural test that rule and the
	 * row-of-sections rule earlier already use for "this item is nested one level inside a
	 * panel" — not a className, so a future nested trigger inherits the correct chevron
	 * treatment without needing its own class.
	 */
	.wm-header .wp-block-navigation .wp-block-navigation__submenu-container > .wp-block-navigation-item.has-child.wm-header__section-header > .wp-block-navigation__submenu-icon {
		display: none;
	}

	/*
	 * A SECTION IS A HEADING WITH ITS LINKS UNDER IT. core renders every navigation item
	 * as `display: flex` in row direction, so a section's heading and its list become
	 * side-by-side flex siblings — the heading ends up vertically centred beside a
	 * 12-row list instead of sitting above it. Measured the other way on the source:
	 * "All Products" occupies 557x484 as one block and its 23 items start at y=128,
	 * which is below the heading, not beside it. The headings do not wrap in the source
	 * either — "Core Technologies" is one line inside a 203px column.
	 */
	.wm-header .wp-block-navigation__submenu-container > .has-child.wm-header__section-header {
		flex-direction: column;
		align-items: flex-start;
	}

	.wm-header .wp-block-navigation__submenu-container > .has-child.wm-header__section-header > .wp-block-navigation-item__content {
		white-space: nowrap;
	}
}

/* -------------------------------------------------------------------------- footer
 *
 * Unit: footer (parts/footer.html -> patterns/footer.php). Hook class .wm-footer on the
 * part's root group, .wm-footer__quick-links on the seven-item menu and
 * .wm-footer__legal on the four legal links.
 */

/*
 * THE QUICK-LINKS LIST IS CSS MULTI-COLUMN, NOT FLEX WRAP, AND THE MEASUREMENT IS WHAT
 * SAYS SO. The contract measures `ul.menu.quick-links-navigation` as 770x176 holding seven
 * items of 377x44 -- four at x=135 and three at x=528. Three numbers rule flex out:
 *
 *   - 377 + 16 + 377 = 770, so the two tracks are EQUAL HALVES of the list's own width.
 *     A wrapped column-direction flex container sizes each line to the widest item in it,
 *     which here would be 264 (Technical Data Sheets) and 296 (Particle Size Conversion
 *     Charts), not 377 and 377.
 *   - 528 - 135 = 393 = 377 + 16, so the gap between tracks is 16.
 *   - 4316 - 4272 = 44 = the item's own height, so the gap between ROWS is 0, and
 *     ceil(7 / 2) x 44 = 176 is the list's measured height exactly.
 *
 * `columns: 2` with `column-fill: balance` (the initial value) produces all three from one
 * declaration, and balances 7 items as 4 then 3 -- the split the contract measures.
 *
 * AND FLEX CANNOT DO IT AT ALL HERE, which is a WP 7.1 fact this toolkit had not recorded.
 * The contract's own note says "this node needs `justifyContent: stretch` on a vertical
 * orientation to reproduce the measured width", reading
 * wp-includes/block-supports/layout.php:800-815 -- which is correct for core/group and
 * wrong for core/navigation. Since 7.1, core/navigation does not take its flex
 * justification from that code path at all: it emits five CSS custom properties of its own
 * (`block_core_navigation_get_layout_custom_property_declarations()`,
 * wp-includes/blocks/navigation.php:51-79, `@since 7.1.0`) that
 * `.wp-block-navigation__container` then reads (blocks/navigation/style.css:440-449).
 * `stretch` IS NOT IN ITS VOCABULARY: `$justification_values` holds only
 * left/center/right/space-between (:52-57), anything else is reset to `left` (:58-61), and
 * on a vertical layout `--navigation-layout-align` is `flex-start` unless the
 * justification is `center` or `right` (:66-69). Measured on this install: the nav renders
 * with `is-content-justification-stretch` in its class list and `align-items: flex-start`
 * computed on the list. So `justifyContent: stretch` is not written in the pattern -- it
 * would be an attribute that reads as the fix and does nothing.
 */
.wm-footer .wm-footer__quick-links > .wp-block-navigation__container {
	display: block;
	columns: 2;
	column-gap: var(--wp--preset--spacing--25);

	/*
	 * `width: 100%` IS LOAD-BEARING AND IS NOT A TIDY-UP. The `<nav>` core renders around
	 * this list carries `is-layout-flex`, so the list is a flex ITEM, and a flex item sizes
	 * to max-content on the main axis unless told otherwise. Without this the two tracks
	 * sized themselves to the widest item instead of to the list's own width: measured
	 * 608x176 with items of 296 at x=135 and x=447, against the contract's 770x176 with
	 * items of 377 at x=135 and x=528. 296 x 2 + 16 = 608 is the shrink-wrap; the 770 only
	 * appears once the list fills the 770px column it sits in.
	 */
	width: 100%;
}

/*
 * ONE TRACK ONCE THE LIST IS TOO NARROW FOR TWO. The breakpoint is the source's own
 * `large`, which site.yml's design_tokens records as `settings.viewport` tablet
 * 1123.98px -- the same value the header's collapse above is keyed to, for the same
 * reason. Below it the links column is 653 wide and a 2-track split would put the
 * 296px-wide "Particle Size Conversion Charts" in a 318px track; the source's footer is
 * 571 tall at both 1024 and 768 against 476 at 1440, and a single 7-row track is what
 * accounts for the extra height.
 */
@media (max-width: 1123.98px) {
	.wm-footer .wm-footer__quick-links > .wp-block-navigation__container {
		columns: 1;
	}
}

/*
 * THE ITEM IS 44px TALL AND CORE'S IS 30px. The contract measures "seven `li.menu-item` of
 * 377x44" and, separately, that "THE LINK TEXT IS 20px AND THE ITEM 21px". theme.json puts
 * core/navigation at the `medium` preset, which renders 20px, and the theme's global
 * line-height of 1.5 makes that a 30px line box -- measured 30px on this install before
 * this rule. 44 - 30 = 14, split 7 and 7, and it goes on the anchor rather than the `li`
 * so the 14px is inside the click target rather than beside it. No `fontSize` is written:
 * the 20px the contract measures is what the theme already resolves to.
 */
.wm-footer .wm-footer__quick-links .wp-block-navigation-item__content {
	display: block;
	/* Was 12px, snapped to spacing|20 (10px), 2026-09-25 (spacing-standard.md §1 item 3). */
	padding-block: var(--wp--preset--spacing--20);
	font-size: 20px;
	font-weight: 700;
	line-height: 1;
	text-transform: uppercase;
}

/*
 * The footer's link type, measured on the live source 2026-09-21 (computed style, 1440 / 1024 / 390): Quick Links
 * anchors 20px / 700 / UPPERCASE (18px at <= 1123, li 38 tall), and the legal row 17.5px / 600 / UPPERCASE (15px at
 * <= 1123) in a 40px (37) row with 11.2px block padding, an " | " separator before every item but the first
 * (the li's ::before, 21px / 18px text), and a 16px right padding on each anchor. The build rendered all of it
 * mixed-case at core's 400.
 */
.wm-footer .wm-footer__legal .wp-block-navigation-item__content {
	font-size: 17.5px;
	font-weight: 600;
	line-height: 1;
	text-transform: uppercase;
	/* Was 11.2px 16px 11.2px 0: 11.2 snapped to spacing|20 (10px), 16 already the new step,
	   2026-09-25 (spacing-standard.md §1 item 3). */
	padding: var(--wp--preset--spacing--20) var(--wp--preset--spacing--25) var(--wp--preset--spacing--20) 0;
}

.wm-footer .wm-footer__legal .wp-block-navigation-item + .wp-block-navigation-item::before {
	content: "|";
	align-self: center;
	/* Was 12px, snapped to spacing|20 (10px), 2026-09-25 (spacing-standard.md §1 item 3). */
	margin-right: var(--wp--preset--spacing--20);
	font-size: 17.5px;
	font-weight: 600;
}

.wm-footer .wm-footer__legal.wp-block-navigation .wp-block-navigation__container {
	gap: 0;
}

@media (max-width: 1123.98px) {
	.wm-footer .wm-footer__quick-links .wp-block-navigation-item__content {
		font-size: 18px;
		padding-block: var(--wp--preset--spacing--20);
	}

	.wm-footer .wm-footer__legal .wp-block-navigation-item__content,
	.wm-footer .wm-footer__legal .wp-block-navigation-item + .wp-block-navigation-item::before {
		font-size: 15px;
	}
}

/* ==========================================================================
 * HOVER STATES. Written here, once, because `core/navigation-link`'s own
 * block.json supports only `anchor` and `typography` -- no colour at all --
 * so a nav link's hover colour cannot be an attribute, and theme.json's
 * `styles.elements.link` reaches these anchors only as the SITE-WIDE rule
 * they are supposed to override.
 *
 * WHAT THE SOURCE DOES, and it is two different treatments, not one.
 * Read from the Drupal theme's own SCSS, which is the only channel that
 * carries a pseudo-state -- a DOM capture records the resting state and
 * nothing else, so ai/reference/ cannot answer this question at all:
 *
 *   scss/modules/_menu_block.scss:99-104   header .menu li a:hover
 *                                            -> color: $highlight-1 (#db240b)
 *                                            -> .cta-button stays $white
 *                                            -> .section-header stays $medium-gray
 *   scss/modules/_menu_block.scss:164-172  header .menu li:hover > a
 *                                            -> the same colour, from the ITEM
 *   scss/modules/_menu_block.scss:386-388  .block-quicklinksnavigation a:hover
 *                                            -> opacity: 0.8, colour untouched
 *   scss/modules/_menu_block.scss:414-416  .block-footer ul.menu li a:hover
 *                                            -> opacity: 0.8, colour untouched
 *
 * WHY THE FOOTER RULES PIN A COLOUR THE SOURCE NEVER RESTATES. In the source
 * the footer's own `color` declaration is 0,1,3 and beats the global
 * `a:hover,a:focus{color:#bc1f09}` at 0,1,1, so a footer link keeps its colour
 * and only fades. Here the global equivalent is theme.json's
 * `styles.elements.link[":hover"]`, which compiles to
 * `:root :where(a:where(:not(.wp-element-button))):hover` -- and that applies
 * DIRECTLY to the anchor, where the footer's white comes from the `has-white-color`
 * class on the <nav> and reaches the anchor only by INHERITANCE. An inherited
 * value loses to any directly-applied one whatever the specificity, so without
 * `color: inherit` below the footer links would go dark red on hover, which is
 * a thing the source does not do. This is the cascade difference between the two
 * platforms being cancelled, not a second opinion about the colour.
 * ========================================================================== */

.wm-header .wp-block-navigation-item:not(.wm-header__section-header) > .wp-block-navigation-item__content:hover,
.wm-header .wp-block-navigation-item:not(.wm-header__section-header):hover > .wp-block-navigation-item__content {
	color: var(--wp--preset--color--primary);
}

/*
 * "CORE TECHNOLOGIES" AND "ALL PRODUCTS" ARE EXEMPTED BY NAME -- SCOPED 2026-09-22. Before this
 * change the rule above matched every `.wp-block-navigation-item__content`, real `<a>` and
 * non-navigating `.wp-block-navigation-submenu__toggle` `<button>` alike, so hovering either of
 * these two labels painted them `primary` red exactly as if they were a clickable link -- wrong on
 * two counts at once: they carry no click behaviour at all (their own children are already shown
 * with no click needed, `.wm-header__section-header`'s own rule above), and the source itself does
 * not do this. This unit's own hover-states block comment (above, "WHAT THE SOURCE DOES") already
 * recorded the source's rule for exactly this case and it went unbuilt until now:
 * `scss/modules/_menu_block.scss:99-104`'s `header .menu li a:hover -> color: $highlight-1` is
 * overridden immediately after by its own `&.section-header` clause, which keeps
 * `color: $medium-gray` -- the same "exempt this modifier by name, the way `.cta-button` already
 * is two rules below" pattern this file already uses, not a new mechanism.
 *
 * `:not(.wm-header__section-header)` on the rule above is the excluding half; this rule is the
 * explicit, stated half -- naming the colour it stays at rather than leaving it to the base
 * (non-hover) rule below to win on specificity alone, which is fragile the moment either rule's
 * selector changes.
 */
.wm-header .wp-block-navigation-item.wm-header__section-header > .wp-block-navigation-item__content:hover,
.wm-header .wp-block-navigation-item.wm-header__section-header:hover > .wp-block-navigation-item__content {
	color: var(--wp--preset--color--medium-gray);
}

/*
 * The header's CTA button is a nav item that is painted like a button, and the
 * source exempts it by name (`&.cta-button { color: $white }`) in both of the
 * rules above. It keeps its white label on hover.
 */
.wm-header .wp-block-navigation-item.wm-header__cta-button > .wp-block-navigation-item__content:hover,
.wm-header .wp-block-navigation-item.wm-header__cta-button:hover > .wp-block-navigation-item__content {
	color: var(--wp--preset--color--white);
}

/*
 * THE STRAY UNDERLINE ON "CONTACT US" -- DIAGNOSED AND FIXED 2026-09-13. The CTA picked up an
 * underline on hover that the source does not have. It is NOT core/navigation's: this theme's
 * own `theme.json` sets `elements.link.:hover.typography.textDecoration: "underline"`, which
 * compiles to a BARE `a:hover` tag selector with no block scoping at all -- the style surface
 * reference/sources/block-attributes.md §"A block's rendered TAG is a style surface" describes
 * -- so it lands on every anchor in the theme including this one, which core renders as a plain
 * `<a class="wp-block-navigation-item__content">`. MEASURED at rest before the fix the anchor
 * computes `text-decoration-line: none`, which is why a still screenshot shows nothing and the
 * cause is only visible with the pointer over it.
 *
 * THE SOURCE'S OWN HOVER ON THIS ELEMENT IS THE PLATE SKEW AND NOTHING ELSE (`%cta-button`'s
 * `&:hover { &:after { transform: skew(15deg) } }`, scss/base/_common.scss:48-51) -- no
 * underline, and the rule above already keeps the label white. `text-decoration: none` here is
 * the third clause of the same "the source exempts the CTA by name" reconciliation, not a new
 * decision.
 *
 * SCOPED TO THE CTA ALONE, DELIBERATELY. Whether the theme's site-wide link-underline-on-hover
 * is right for ordinary nav links is a theme.json question and wp-theme-scaffold's, not this
 * unit's -- the plain header links are handled by the colour rule above and are left as they
 * are.
 */
.wm-header .wp-block-navigation-item.wm-header__cta-button > .wp-block-navigation-item__content:hover,
.wm-header .wp-block-navigation-item.wm-header__cta-button:hover > .wp-block-navigation-item__content {
	text-decoration: none;
}

/*
 * "CURRENT SECTION" STATE -- ADDED 2026-09-26, one boxed fix (`ai/inventory.yml`
 * `selection.choices.header.instructions`, approved 2026-09-26). The source paints its own
 * current top-level item, and its own current-section ancestor, the same red as this file's own
 * hover rule above ($highlight-1 / #db240b, this theme's `primary` preset) -- confirmed on the
 * source screenshot named in that approval: APPLICATIONS in red both on /applications and on an
 * `application` CPT page such as /applications/industries/vibratory-finishing/. Reusing
 * `primary` here is not a fresh colour choice, it is the one red this header already uses for
 * exactly this kind of state indication.
 *
 * `current-menu-item` AND `current-menu-ancestor` ARE CORE'S OWN CLASSES, NOT NEW ONES -- see
 * `washington_mills_applications_nav_current()` in functions.php for why core's own exact-ID
 * match never fires for this link on its own and where these two classes come from instead. This
 * rule is the one place that has to know either happened; the markup either carries core's own
 * class or it does not.
 */
.wm-header .wp-block-navigation-item.current-menu-item > .wp-block-navigation-item__content,
.wm-header .wp-block-navigation-item.current-menu-ancestor > .wp-block-navigation-item__content {
	color: var(--wp--preset--color--primary);
}

.wm-footer .wm-footer__quick-links .wp-block-navigation-item__content:hover,
.wm-footer .wm-footer__links .wp-block-navigation-item__content:hover,
.wm-footer .wm-footer__legal .wp-block-navigation-item__content:hover {
	color: inherit;
	opacity: 0.8;
}

/*
 * KEYBOARD FOCUS ON THE HEADER CTA -- same ring and same reason as button.css's `:focus-visible`
 * rule for the filled `core/button` (2026-09-21): an outline on the anchor's rectangle would cut
 * through the skewed plate, so the ring follows the rendered silhouette via drop-shadow. Kept in
 * sync by hand for the same reason the plate itself is (this file loads without a `core/button`).
 */
.wm-header .wp-block-navigation-item.wm-header__cta-button > .wp-block-navigation-item__content:focus-visible {
	outline: none;
	filter: drop-shadow(2px 0 0 #fff) drop-shadow(-2px 0 0 #fff) drop-shadow(0 2px 0 #fff) drop-shadow(0 -2px 0 #fff)
		drop-shadow(2px 0 0 #000) drop-shadow(-2px 0 0 #000) drop-shadow(0 2px 0 #000) drop-shadow(0 -2px 0 #000);
}
