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/tabs.css

@@ -12,7 +12,7 @@
  *         [data-md-tab-content]    [data-md-icon] (optional), [data-md-tab-label],
  *                                  [data-md-tab-indicator]
  *           [data-md-tab-label]    [data-md-tab-text], [data-md-badge] (optional)
- *   [data-md-tab-panel]            role="tabpanel", hidden server-side until chosen (N-05)
+ *   [data-md-tab-panel]            role="tabpanel", hidden server-side until chosen
  *
  * "Labels: single row by default; may wrap to a max second line if needed with truncation, or use
  * scrollable tabs to give longer titles more room" (§ Tabs, "Behaviour and guidelines"). A fixed
@@ -25,7 +25,7 @@
  *
  * The active indicator is drawn in every tab and shown under the chosen one, so it is right before
  * Alpine starts and after a morph: 3px with rounded top corners under the content of a primary tab
- * (at least 24px wide, inset 2px at each side — N-18), 2px across the whole of a secondary one.
+ * (at least 24px wide, inset 2px at each side), 2px across the whole of a secondary one.
  * When the choice changes, a view transition moves it from the old tab to the new (resources/js/tabs.js),
  * as M3's slides.
  *
@@ -33,10 +33,10 @@
  * rest of the package draws 3px thick 2px outside the element (tokens/state.css). `--tabs-ring` is
  * the room that takes: the bar carries it as padding on every side, and the state layer and the
  * indicator reach back out into it, so the divider still sits against the tabs and the indicator
- * still sits on the divider (N-20). That makes the bar 10px taller than M3's 48px tab. A scrollable
- * set's first tab is offset 52dp from the leading edge, so it reads as scrollable (N-10). A link
+ * still sits on the divider. That makes the bar 10px taller than M3's 48px tab. A scrollable
+ * set's first tab is offset 52dp from the leading edge, so it reads as scrollable. A link
  * marked `aria-current="page"` (`<x-section-nav>`'s tabs) takes the active indicator and colour
- * exactly as `aria-selected="true"` does (N-21).
+ * exactly as `aria-selected="true"` does.
  */
 
 @layer material.reset, material.tokens, material.base, material.layout, material.components, material.text, material.visibility;
@@ -63,7 +63,7 @@
     }
 
     /* "Offset the first scrollable tab 52dp from the leading edge so it's clear that more content
-       is available" (N-10). Logical, so a right-to-left page mirrors it. */
+       is available". Logical, so a right-to-left page mirrors it. */
     [data-md-tabs-bar][data-md-scrollable] {
         padding-inline-start: 52px;
         scroll-padding-inline-start: 52px;
@@ -141,7 +141,7 @@
     }
 
     /* A link-based bar marks the page with aria-current, not aria-selected; both are the chosen
-       tab, and both take the variant's active colour (N-21). */
+       tab, and both take the variant's active colour. */
     [data-md-tab]:is([aria-selected='true'], [aria-current='page']) {
         color: var(--md-sys-color-primary);
     }
@@ -196,7 +196,7 @@
         white-space: normal;
     }
 
-    /* Primary indicators are inset 2dp at each side (N-18); both variants sit on the divider, which
+    /* Primary indicators are inset 2dp at each side; both variants sit on the divider, which
        the ring's room has pushed below the tab. */
     [data-md-tab-indicator] {
         position: absolute;