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/views/components/alert.blade.php

@@ -6,13 +6,13 @@
      `color` (alias `tone`): `info` (the default), `success`, `warning`, `error`, `primary`,
      `secondary`, `tertiary`, or `neutral` for surface-container-high. `icon` replaces the state's
      icon; `:icon="false"` drops it. `dismissible` adds a close button that hides it in the browser,
-     40px drawn with the 48px target M3 asks for (ACT-18).
+     40px drawn with the 48px target M3 asks for.
 
      It is a `role="status"`, whatever its colour: an alert is usually part of the page as it
      renders, and `role="alert"` is an assertive live region that some screen readers announce over
      the page title on load — and that a Livewire morph re-announces. `assertive` opts into
      `role="alert"` for the case the prop is named after: a notice put on screen in answer to
-     something the person just did (ACT-36). M3 publishes no banner; the nearest thing it does
+     something the person just did. M3 publishes no banner; the nearest thing it does
      publish, the snackbar, says polite and never assertive.
 
      Drawn by resources/css/components/alert.css from `data-md-alert` and `data-md-color`; the