Cut duplicated and speculative code across the package

An over-engineering audit of the whole tree, applied in five reviewed
batches. Behaviour stays the same except where UPGRADE.md says otherwise.

PHP: the showcase and error-page stylesheets are prebuilt into
resources/dist by bin/stylesheets.mjs, through Vite's own postcss-import
(first occurrence kept, the order an application's build gives), instead
of Stylesheets::bundle() inlining imports on every request; only the
import walk DesignGuard needs stays. SchemeStylesheet::withProfiles()
replaces three copies of the scheme-plus-profiles loop, material:scheme
leaves spec and contrast checks to the node script that already made
them, and the error page's scheme cache, the hashed view namespace, the
translations path with no lang/ folder and DesignGuard's 1.x-name hints
are gone.

JS: the androidx shape port progress.js and both bin scripts each carried
lives once in resources/js/shapes.js (the generated SVGs are unchanged);
util.js holds ringIndex(), ms(), reopenGuard() and remember(), which
were written out several times; listeners are released through
AbortController; tooltip.js's hoverPopover() serves the rich tooltip too.

CSS: every rule for an element inside the navigation rail queries
`--md-navigation-rail-value` instead of repeating the seven collapsed
conditions under five media branches; badge, alert, progress, slider and
button read one non-inheriting colour-role table (components/color.css);
the dialog chrome, the submenu's popover chrome, the chip's state layer
and touch target, and the visually-hidden inputs use the shared rules
they copied; foundation/tokens.css is folded into foundation.css.

Views: Support\Field and Support\Link replace the error-key, bound-value
and link-attribute blocks copied into the fields and link components;
the timepicker period group, the menu filter and the showcase head are
partials; the datepicker's steppers and entry fields are loops; component
docblocks no longer restate SKILL.md.

Tests and tooling: one dataset-driven ComponentStylesheetsTest replaces
four per-group files, DesignGuardTest and the layout-component tests use
datasets, browser tests share one ready() helper, CSS parsing lives in
ComponentStylesheet alone. docs/audits and the finding IDs citing it are
removed, as are pestphp/pest-plugin-laravel, the unused composer scripts
and check:font; the lint job runs in the feature job, which now installs
node packages so the prebuilt-stylesheet staleness test runs in CI.

Feature suite 1177 passed, Chrome browser suite 299 passed.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

resources/css/components/list-item.css

@@ -4,7 +4,7 @@
  * Material 3, Apache-2.0) — the tallest element sets the height, and a three-line item top-aligns
  * rather than centring (docs/reference/m3/components-actions-communication-containment.md
  * § Lists → Specs). Leading/trailing gap and container padding are both `space200` (16px,
- * `ItemLeadingSpace`/`ItemTrailingSpace`/container padding, C-14).
+ * `ItemLeadingSpace`/`ItemTrailingSpace`/container padding).
  *
  * `data-md-list-row` (`resources/js/list-rows.js`, shared with `<x-card>` and an application's own
  * table rows) and `[data-md-list-open]:focus-visible` answer with the state layer — the row's ink at
@@ -12,25 +12,25 @@
  * `[data-md-card]`, which draws its own tint through the shared `md-state-layer` class instead
  * (card.css). The layer is mixed over the row's own fill, `--md-list-row-fill` (a segmented tile's
  * surface, a selected item's secondary-container, table.css's selected row), so a hovered, pressed
- * or focused row keeps its fill under the tint instead of trading it for a translucent one (C-08's
- * second fix). `data-md-selected` is M3's selected item, secondary-container filled, which also
+ * or focused row keeps its fill under the tint instead of trading it for a translucent one.
+ * `data-md-selected` is M3's selected item, secondary-container filled, which also
  * lifts the description/overline/trailing/icon colour rules below since they exclude it — the
  * container's own colour takes over by inheritance. The same attribute on any other row that is
  * not a card — an application's own `<li>`, `<div>` or `<tr>` — draws the same fill and ink, as
  * 1.x's `data-selected` did; a card keeps its own container. A selected option draws a second cue, a
- * trailing check, so selection is never colour alone (C-03). `aria-disabled` inks the whole item
+ * trailing check, so selection is never colour alone. `aria-disabled` inks the whole item
  * on-surface at the disabled-content opacity (38%) and blocks the pointer; the view drops the
- * item's link entirely rather than leaving a focusable, activatable control behind it (C-02).
+ * item's link entirely rather than leaving a focusable, activatable control behind it.
  *
  * `data-md-list="segmented"` items (M3 Expressive) are `surface-container` tiles (one tone up from
- * `ItemSegmentedContainerColor`, so they read against the package's own `surface` page;
- * C-21), 4px corners that open to 16px at the list's own ends and while hovered (12px), pressed,
- * focused or selected (16px) — the specs page's interaction-state expressive shapes (C-22). Leading
+ * `ItemSegmentedContainerColor`, so they read against the package's own `surface` page),
+ * 4px corners that open to 16px at the list's own ends and while hovered (12px), pressed,
+ * focused or selected (16px) — the specs page's interaction-state expressive shapes. Leading
  * icons there are drawn at 20px, not scaled down from 24 — list-item.blade.php passes `size` to
- * `<x-icon>` from the parent's `@aware(['segmented'])`, so no CSS override is needed here (C-26).
+ * `<x-icon>` from the parent's `@aware(['segmented'])`, so no CSS override is needed here.
  *
  * `data-md-dividers` on the list insets its rule 16px from both ends (`DividerLeadingSpace`/
- * `DividerTrailingSpace`, C-16) rather than full-bleed.
+ * `DividerTrailingSpace`) rather than full-bleed.
  *
  * Leading media: `data-md-list-item-avatar` is 40px, full corner, initials in primary-container
  * when it is a `<span>`, an image otherwise; `data-md-list-item-image` is a 56px small-corner