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/theme-toggle.css

@@ -1,18 +1,18 @@
 /*
  * <x-theme-toggle>: `mode="toggle"|"cycle"` an icon button between light, dark (and system for
- * cycle); `mode="picker"|"contrast"` a connected group over native radios (docs/audits/m3-alignment/
- * navigation.md N-04, N-17 — the Expressive-deprecated segmented button's successor,
- * `<x-group>`, already fixes both there). This file only draws the icon button; the group's own
- * shape, colour and 48px minimum below `medium` are group.css's.
+ * cycle); `mode="picker"|"contrast"` a connected group over native radios — the Expressive-
+ * deprecated segmented button's successor, `<x-group>`, already gives it the keyboard handling and
+ * shape a hand-rolled control would have to reimplement. This file only draws the icon button; the
+ * group's own shape, colour and 48px minimum below `medium` are group.css's.
  *
  *   [data-md-theme-toggle="toggle"|"cycle"]     the icon button: 40px reaching 48px through
- *                                                md-touch-target (N-01), morphing corner
+ *                                                md-touch-target, morphing corner
  *   [data-md-theme-toggle="picker"|"contrast"]  the group's own wrapper (`role="group"`)
  *
  * The icon button also carries `data-md-icon-button`, the hook `resources/css/components/
  * toolbar.css` matches generically (not `[data-md-button][data-md-icon-button]`, as button.css
  * requires): a theme toggle placed in a toolbar's `actions` takes the toolbar's own icon colour
- * (N-13) the same way one of its `<x-button icon>` children would.
+ * the same way one of its `<x-button icon>` children would.
  *
  * The corner morphs from full to `sm` while pressed on the fast spatial spring — M3 Expressive's
  * pressed-state shape change, the same motion `<x-button>`'s own icon buttons use