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

@@ -50,7 +50,7 @@
      M3 **requires** a close affordance on a side sheet — without one nobody can predict the
      sheet's open/close flow or tell whether it is transient or permanent
      (docs/reference/m3/components-actions-communication-containment.md § Side sheets →
-     Accessibility, C-04) — so `with-close-button` is on by default, and
+     Accessibility) — so `with-close-button` is on by default, and
      `:with-close-button="false"` is ignored where nothing else closes the sheet: Escape off, the
      scrim off, or `standard`, which has neither from `expanded`.
 
@@ -88,11 +88,7 @@
     // A standard sheet bound to Livewire is drawn open from the first paint when its property is
     // (truthy as Alpine reads it), so it stands in the row before the script starts rather than
     // growing into it; drawer.css keeps any other standard sheet out of the row until then.
-    $startsOpen = false;
-
-    if ($standard && $model !== null && ($component = \Livewire\Livewire::current()) !== null) {
-        $startsOpen = ! in_array(data_get($component, $model), [null, false, 0, 0.0, ''], true);
-    }
+    $startsOpen = $standard && ! in_array(\NoNameWeb\LivewireMaterial\Support\Field::bound($model, false), [null, false, 0, 0.0, ''], true);
 
     // M3 requires a close affordance; the prop can only ever add one, never take away the last
     // way out of the sheet. A standard sheet keeps no scrim and no trap from `expanded`, and
@@ -231,7 +227,7 @@
         @isset($actions)
             {{-- The side-sheet specs table: bottom actions 72dp tall, 16dp above them, 24dp below
                  (the sheet's own padding), aligned **left** — a dialog's are trailing-aligned, and
-                 M3 specifies the two differently (C-10). --}}
+                 M3 specifies the two differently. --}}
             <div data-md-drawer-actions>{{ $actions }}</div>
         @endisset
     </aside>