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/fab-menu.css

@@ -4,17 +4,17 @@
  * FabMenuBaselineTokens (androidx Compose Material 3, Apache-2.0): the trigger is a 56px FAB,
  * `data-md-color`'s container, large corner, elevation 3, rising to elevation 4 under a hovering
  * pointer; while its list is open (`aria-expanded`) it turns fully round and paints the colour
- * itself, on the default spatial and effects springs (ACT-19 splits the two). It renders the
+ * itself, on the default spatial and effects springs (split between the two). It renders the
  * foundation's `md-state-layer` and `md-focus-ring` (foundation/interaction.css); its 56px already
  * meets M3's target, so it needs no `md-touch-target`. The list sits
  * `data-md-position`'s corner of the trigger, 8px padding — the room the close button keeps below
  * the first item — and scrolls past `calc(100dvh - 128px)` on a short window, behind the close
- * button, which stays fixed (ACT-32).
+ * button, which stays fixed.
  *
  * The items (fab-menu-item.css) rise into place as the list opens and sink back as it closes: the
  * entry is `@starting-style` on the item itself; the exit is the popover's exit copy
  * (`data-md-popover-exit`, resources/js/popover-exit.js), which stays on screen after the popover
- * has closed, so the items have somewhere to animate to (ACT-33) in every engine, Firefox included.
+ * has closed, so the items have somewhere to animate to in every engine, Firefox included.
  * `[data-md-fab-menu-popover]:not(:popover-open) > *` and the copy's `[data-md-popover-closing] > *`
  * are the closed values; inside the layer they beat fab-menu-item.css's resting `translate: 0 0`
  * and `opacity: 1` on specificity — two attributes, or an attribute and a pseudo-class, against the