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/Feature/Components/ProgressTest.php

@@ -56,24 +56,25 @@ it('draws the first frame on the server, at the value', function () {
         ->toContain('<path d="M36.579 27.01A18 18 0 1 1 12.99 3.421" />');
 });
 
-it('draws the active indicator in the colour and the track in its container', function (string $color, array $declarations) {
-    $css = ComponentStylesheet::read('progress');
-
+it('draws the active indicator in the colour and the track in its container', function (string $color) {
+    // Every hue but primary comes straight off the shared colour-role table (color.css,
+    // ColorTest.php): `stroke` reads `--md-container`, which is the hue's own container for
+    // every one of them.
     expect((string) $this->blade('<x-progress value="50" :color="$color" />', ['color' => $color]))
-        ->toContain("data-md-color=\"{$color}\"")
-        ->and($css->declarations("[data-md-progress][data-md-color='{$color}']"))->toBe($declarations);
-})->with([
-    'secondary' => ['secondary', ['color' => 'var(--md-sys-color-secondary)', 'stroke' => 'var(--md-sys-color-secondary-container)']],
-    'tertiary' => ['tertiary', ['color' => 'var(--md-sys-color-tertiary)', 'stroke' => 'var(--md-sys-color-tertiary-container)']],
-    'error' => ['error', ['color' => 'var(--md-sys-color-error)', 'stroke' => 'var(--md-sys-color-error-container)']],
-]);
+        ->toContain("data-md-color=\"{$color}\"");
+})->with(['secondary', 'tertiary', 'error']);
 
 it('falls back to primary for an unknown colour, secondary-container track included', function () {
     $css = ComponentStylesheet::read('progress');
 
     expect((string) $this->blade('<x-progress value="50" color="purple" />'))->toContain('data-md-color="primary"')
         ->and($css->declarations('[data-md-progress]'))->toMatchArray([
-            'color' => 'var(--md-sys-color-primary)',
+            'color' => 'var(--md-color, var(--md-sys-color-primary))',
+            'stroke' => 'var(--md-container, var(--md-sys-color-secondary-container))',
+        ])
+        // Unlike every other hue, primary keeps a track of its own: the shared table's `primary`
+        // entry is plain primary-container, which progress does not want.
+        ->and($css->declarations("[data-md-progress][data-md-color='primary']"))->toBe([
             'stroke' => 'var(--md-sys-color-secondary-container)',
         ]);
 });