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

@@ -12,11 +12,11 @@
  *
  * 560/280px width (max/min), 48px scrim margin, 28px corner and 24dp padding all match the specs
  * page; a compact window's full-screen dialog swaps the box for the whole screen with a 56px bar
- * (C-17: this used to be 64px) instead of the headline block. It opens on the fast spatial spring
+ * (this used to be 64px) instead of the headline block. It opens on the fast spatial spring
  * and closes at once — a native `<dialog>` makes an exit transition awkward, since
  * `@starting-style` only ever supplies an entry.
  *
- * The dividers (§ Dialogs → Anatomy, C-06): a 1px outline-variant rule under the pinned head and
+ * The dividers (§ Dialogs → Anatomy): a 1px outline-variant rule under the pinned head and
  * over the pinned actions, each only while the body has more content hidden on its side.
  * resources/js/dialog.js marks the `<dialog>` with data-md-overflow-top/-bottom as the body
  * scrolls; `data-md-modal-divider` says an element takes part at all — the head and the actions
@@ -53,6 +53,19 @@
         padding: 0;
         background-color: transparent;
         color: var(--md-sys-color-on-surface);
+    }
+
+    /* Dialog chrome shared with the time picker's dialog and a modal date picker (timepicker.css,
+     * datepicker.css, both import this file for it): M3's spatial-fast pop and a 32%-scrim
+     * backdrop, entering only — a native `<dialog>` makes an exit transition awkward, since
+     * `@starting-style` only ever supplies an entry. A plain selector list, not `:is()`: `:is()`
+     * would flatten every branch to the specificity of `[data-md-datepicker-picker]:modal`, the
+     * one with a pseudo-class, and outrank whatever else the modal or the time picker's dialog is
+     * layered against.
+     */
+    [data-md-modal],
+    [data-md-timepicker-dialog],
+    [data-md-datepicker-picker]:modal {
         opacity: 1;
         scale: 1;
         transition-property: opacity, scale;
@@ -61,13 +74,17 @@
     }
 
     @starting-style {
-        [data-md-modal] {
+        [data-md-modal],
+        [data-md-timepicker-dialog],
+        [data-md-datepicker-picker]:modal {
             opacity: 0;
             scale: 0.95;
         }
     }
 
-    [data-md-modal]::backdrop {
+    [data-md-modal]::backdrop,
+    [data-md-timepicker-dialog]::backdrop,
+    [data-md-datepicker-picker]:modal::backdrop {
         background-color: color-mix(in srgb, var(--md-sys-color-scrim) 32%, transparent);
     }
 
@@ -100,7 +117,7 @@
         }
     }
 
-    /* The phone-only header bar: M3's full-screen dialog header, 56dp (C-17). */
+    /* The phone-only header bar: M3's full-screen dialog header, 56dp. */
     [data-md-modal-bar] {
         display: flex;
         height: var(--md-sys-measurement-space700);