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>

tests/Browser/CarouselTest.php

@@ -40,8 +40,8 @@ class CarouselMorphProbe extends Component
  * offset that brings item i into focus) and `at(i)`; the script's value is the result. Pest
  * retries a failing assertion and gives each attempt a second: keep scripts well inside it.
  *
- * `open(i)` rather than a zero inset: M3's 16dp of content padding, the carousel's default since
- * containment.md C-12, shrinks every keyline near the ends (Compose's
+ * `open(i)` rather than a zero inset: M3's 16dp of content padding, the carousel's default,
+ * shrinks every keyline near the ends (Compose's
  * createShiftedKeylineListForContentPadding), so a large item resting at the start or the end is
  * masked by that share of the padding — 1.33px on each side in the showcase's first carousel.
  */
@@ -188,7 +188,7 @@ it('scrolls instantly and leaves every item unmasked under reduced motion', func
 
 it('brings an item cut off at the row\'s edge into view when it is pressed under reduced motion', function () {
     // Owed by the Chromium baseline (step 32, docs/plans/material-3-browser-tests.md): reduced
-    // motion writes a zero inset for every item (C-05), so a mask cannot say an item is only partly
+    // motion writes a zero inset for every item, so a mask cannot say an item is only partly
     // shown; carousel.js reads the item's box against the row's instead, as for multi-aspect.
     $page = carouselShowcase(['reducedMotion' => 'reduce'])
         ->assertScript(onCarousel(0, <<<'JS'