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/app-bar.css

@@ -15,11 +15,11 @@
  *   small    64px, title-large title (label-medium subtitle), 4px from the edges, the title 16px
  *            from the start or straight after the navigation icon
  *   center   the same, the title centred — a three-column grid, so it shrinks against whatever is
- *            beside it rather than ellipsising underneath it (N-11: a fixed inset fit exactly one
- *            of M3's two trailing buttons)
+ *            beside it rather than ellipsising underneath it: a fixed inset fit exactly one
+ *            of M3's two trailing buttons
  *   medium   112px (136px with a subtitle): the 64px row of icons over a headline-medium title
  *   large    120px (152px with a subtitle): a display-small title
- *   search   the row holds a search bar, full width to 312px and then half of what is left (N-09)
+ *   search   the row holds a search bar, full width to 312px and then half of what is left
  *
  * The container is the surface, and surface-container once content scrolls under it. A medium or
  * large bar collapses into the small one without script moving anything: the bar is sticky at a
@@ -169,7 +169,7 @@
 
     /* Centred: a three-column row — leading, headline, trailing — so the headline is centred in the
        window and shrinks against whatever is actually beside it. M3 allows two trailing icon
-       buttons, which a fixed inset for one would have let a long title ellipsise underneath (N-11). */
+       buttons, which a fixed inset for one would have let a long title ellipsise underneath. */
     [data-md-app-bar][data-md-variant='center'] [data-md-app-bar-row] {
         display: grid;
         grid-template-columns: 1fr auto 1fr;
@@ -196,7 +196,7 @@
     }
 
     /* The search bar fills the space between the leading and trailing elements until it is 312dp
-       wide, and then grows into only half of what is left (N-09). The percentage is of the row
+       wide, and then grows into only half of what is left. The percentage is of the row
        rather than of that space, which CSS cannot name without measuring it; below 312px the cap
        never binds, so a phone still gets the whole row. */
     [data-md-app-bar-search] {