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/modal.blade.php

@@ -26,13 +26,13 @@
      above a centred title, as M3 draws a dialog with a hero icon. `fullscreen` makes a dialog that
      holds a form take the whole screen on a compact window (below `medium`, 600px — M3 uses
      full-screen dialogs "only in compact breakpoints", FullScreenDialogTokens), with a 56px
-     close-and-title bar clear of the notch (docs/audits/m3-alignment/containment.md, C-17).
+     close-and-title bar clear of the notch.
      `persistent` ignores Escape and the scrim, for a dialog that must be answered. It opens on the
      fast spatial spring and closes at once, as M3's do.
 
      "Dialog content generally shouldn't scroll; if it must, the title stays pinned at the top and
      the buttons at the bottom" (docs/reference/m3/components-actions-communication-containment.md
-     § Dialogs → Behaviour, C-06): the header and the action row are their own rows of the flex
+     § Dialogs → Behaviour): the header and the action row are their own rows of the flex
      column and only the body between them scrolls, each with the 24dp padding the box used to
      carry.
 
@@ -53,7 +53,7 @@
      around the slot, so content a Livewire render adds counts, and marks the `<dialog>` with
      `data-md-overflow-top`/`data-md-overflow-bottom`.
 
-     `alert` is M3's "on web, basic dialogs should have the alert dialog role" (C-20): it sets
+     `alert` is M3's "on web, basic dialogs should have the alert dialog role": it sets
      `role="alertdialog"` and points `aria-describedby` at the body, for the dialog that
      interrupts to say something important. It is opt-in, because ARIA-APG keeps `alertdialog`
      for exactly that and a form dialog would over-announce with it. A `subtitle` is always the
@@ -106,11 +106,11 @@
     @if ($alert) role="alertdialog" @endif
     @if (filled($title)) aria-labelledby="{{ $id }}-title" @endif
     @if (filled($describedBy)) aria-describedby="{{ $describedBy }}" @endif
-    {{ $attributes->whereDoesntStartWith('wire:model')->except(['id'])->merge(array_filter([
+    {{ $attributes->whereDoesntStartWith('wire:model')->except(['id'])->merge([
         'id' => $id,
         'data-md-modal' => true,
         'data-md-fullscreen' => $fullscreen ? true : null,
-    ], fn ($value): bool => $value !== null)) }}
+    ]) }}
 >
     <div data-md-modal-box @if (filled($boxClass)) class="{{ $boxClass }}" @endif>
         @if ($fullscreen)