/**
 * core/list rules, each scoped to the unit that owns it.
 *
 * This file is shared by construction: every unit that places a core/list lands here.
 * Nothing in it may be written unscoped -- a rule with no unit hook class repaints every
 * list on the site, which is a theme decision and belongs to wp-theme-scaffold.
 *
 * The rules below are that theme decision, written by wp-theme-scaffold and deliberately
 * NOT unit-scoped -- same shape as button.css's outline/fill-plate rules. The reason is
 * the source, not a preference: the source's own list for this content
 * (`inner-section-content`) is a bare `<ul><li>` with NO class at all (confirmed by
 * reading ai/reference/units/
 * inner-section-content@www.washingtonmills-com.l5.wfdev.net.json's raw `html` field
 * directly), so there is no component to scope a rule to -- whatever paints the marker
 * and the inline-link colour in the source is a generic content-area rule, and core's own
 * `.wp-block-list` class (emitted by every core/list instance, confirmed: only
 * `inner-section-content` places core/list today, grepped across patterns/) is this
 * build's equivalent of that generic surface. A future unit that places core/list inherits
 * this automatically, which is the point -- the alternative (core/list's own
 * `color.link` block-attribute support) would set the link colour per pattern instance,
 * requiring every future list to remember to set it again; this does not.
 *
 * MEASURED against the live source, not the captured reference payload -- that payload's
 * `computed` array is 4 entries deep (one per viewport) and none goes past the ancestor
 * chain (div.paragraph__inner_section_content > ... > section); it never reaches the
 * `<li>`, its `::marker` or its `<a>`. Re-measured directly with probe.js against
 * https://www.washingtonmills-com.l5.wfdev.net/about-washington-mills, 2026-09-16:
 *
 *   - `list-style-type` is already `none` on both the source's `<ul>` and `<li>` -- the
 *     visible marker is a `::before`, 8x8px, `background-color: rgb(219, 36, 11)`, which is
 *     this theme's `primary` preset (theme.json settings.color.palette; ai/site.yml
 *     design_tokens confirms primary = #db240b = $highlight-1 = Foundation's own
 *     $foundation-palette.primary). It sits `top: 13px` inside a `position: relative` `<li>`
 *     whose own line box is 21px/33.6px -- (33.6 - 8) / 2 = 12.8, i.e. centred on the FIRST
 *     line, not a fixed pixel offset from the top of a (possibly multi-line) item. This
 *     build's list text is not necessarily the same line-height, so `top: 0.5em; transform:
 *     translateY(-50%)` reproduces the same first-line centring without hardcoding a
 *     line-height the two builds do not share.
 *   - the two inline links in this content measure `color: rgb(219, 36, 11)` -- the same
 *     `primary` preset -- with no underline (`textDecorationLine: none`, already covered by
 *     `styles.elements.link`'s site-wide `typography.textDecoration: none`, so it is not
 *     repeated here). Hovering measured `color: rgb(188, 31, 9)` = `#bc1f09`, which is
 *     `styles.elements.link`'s own existing `:hover` literal verbatim (theme.json
 *     `styles.elements.link.:hover.color.text`) -- reused here rather than restated as a
 *     new number.
 *   - `styles.elements.link`'s base colour is `currentColor`, which is correct for links
 *     elsewhere that must inherit their container's colour (buttons, nav) and is why this
 *     override lives here rather than changing `elements.link` itself: this content's own
 *     `<li>` text is black, so `currentColor` renders these links black, which is exactly
 *     the defect this file fixes.
 *
 * `:not(.is-style-checkmark-list)` guards every rule below that touches the marker or the
 * list's own reset, because `washington_mills_block_styles()` (functions.php) already
 * registers a `checkmark-list` block style on core/list with its own `::before`-free
 * checkmark marker -- unused by any pattern today, but a real competing mechanism on this
 * exact block, so this file must not fight it if an editor picks it later.
 */

.wp-block-list:not(.is-style-checkmark-list),
.wp-block-washington-mills-text-image-carousel__content ul {
	list-style: none;
	padding-inline-start: 0;
}

.wp-block-list:not(.is-style-checkmark-list) li,
.wp-block-washington-mills-text-image-carousel__content ul li {
	position: relative;
	padding-inline-start: var(--wp--preset--spacing--30);
}

/*
 * MARKER: `top: 13px`, no transform -- the source's own value, measured 2026-09-21 on the product body list and the
 * about-page lists at 1440, 1024 and 390 (8x8, `top: 13px` at 21px and at 18px text alike). The earlier
 * `0.5em` + translateY(-50%) sat 2.5-4px too high.
 */
.wp-block-list:not(.is-style-checkmark-list) li::before,
.wp-block-washington-mills-text-image-carousel__content ul li::before {
	content: "";
	position: absolute;
	left: 0;
	top: 13px;
	width: 8px;
	height: 8px;
	background-color: var(--wp--preset--color--primary);
}

/*
 * `.two-column` is a class the SOURCE authors on a `ul` (product bodies) and the import carries into the block's
 * className. Source: `column-count: 2` at >= 768px, auto below (measured 1440/1024 = 2, 390 = auto).
 * Link colour and hover for list links live in theme.json (`core/list` / `core/paragraph` `elements.link`).
 */
@media (min-width: 768px) {
	.wp-block-list.two-column {
		column-count: 2;
	}
}

/*
 * The text-image-carousel's slide copy is raw ul/li HTML from the block's own fields (no `.wp-block-list`), and the
 * source draws it with the same generic list rule -- red 8px square marker, 10px between items (about-washington-mills,
 * "Unrivaled Experience", 2026-09-21). The selectors above carry it; core's `& li` spacing in theme.json does not reach it.
 */
.wp-block-washington-mills-text-image-carousel__content ul li {
	margin: 0 0 var(--wp--preset--spacing--20);
}
