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/css/components/bottom-sheet.css

@@ -8,13 +8,13 @@
  *     [data-md-bottom-sheet-probe]  hidden, measures a stop's px height for a drag to settle on
  *     [data-md-bottom-sheet-panel]  surface-container-low, extra-large top corners, elevation 1;
  *                                   data-md-preset while `heights`/`snap` gives it stops
- *       [data-md-bottom-sheet-handle]   the drag target and M3's 48dp hit area (C-01)
+ *       [data-md-bottom-sheet-handle]   the drag target and M3's 48dp hit area
  *         [data-md-bottom-sheet-grip]   the 32×4px bar, the shared classes' touch target
  *       [data-md-bottom-sheet-announce] a live region, only while stops exist
  *       [data-md-bottom-sheet-body], [data-md-bottom-sheet-title], [data-md-bottom-sheet-actions]
  *
  * 640px max width, centred; 28px top corners only (`DockedContainerShape` = CornerExtraLargeTop);
- * 50dvh default open height under a ceiling of the screen less M3's 72dp top margin (C-19). It
+ * 50dvh default open height under a ceiling of the screen less M3's 72dp top margin. It
  * rises on emphasized decelerate and only falls on emphasized accelerate — the asymmetric timing a
  * more specific selector for the open state supplies, since a CSS transition always takes its
  * duration and easing from the *after-change* style (the technique resources/css/components/