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>

src/LivewireMaterialServiceProvider.php

@@ -5,7 +5,6 @@ namespace NoNameWeb\LivewireMaterial;
 use Illuminate\Contracts\View\Factory;
 use Illuminate\Support\Facades\Blade;
 use Illuminate\Support\Facades\Route;
-use Illuminate\Support\Facades\View;
 use Illuminate\Support\ServiceProvider;
 
 class LivewireMaterialServiceProvider extends ServiceProvider
@@ -22,7 +21,6 @@ class LivewireMaterialServiceProvider extends ServiceProvider
     public function boot(): void
     {
         $this->loadViewsFrom(__DIR__.'/../resources/views', 'livewire-material');
-        $this->loadTranslationsFrom(__DIR__.'/../lang', 'livewire-material');
 
         $this->registerComponents();
         $this->registerPagination();
@@ -49,8 +47,7 @@ class LivewireMaterialServiceProvider extends ServiceProvider
     }
 
     /**
-     * The anonymous components. Blade names their view namespace after a hash of this string, and
-     * compiled views keep that name, so it stays written the way it always was.
+     * The anonymous components.
      */
     public static function componentPath(): string
     {
@@ -121,8 +118,7 @@ class LivewireMaterialServiceProvider extends ServiceProvider
      * component folder's absolute path when there is none. That path differs between a laptop and
      * a container sharing `storage/framework/views`, or between release directories, while the
      * compiled file's name does not — so a view compiled on one showed `a1b2…::button` as text on
-     * the other. A prefix does not stop an unprefixed tag resolving. The path's namespace stays
-     * registered, so views compiled before this release still render until they are recompiled.
+     * the other. A prefix does not stop an unprefixed tag resolving.
      *
      * The package's own views never go through this registration: they write
      * `<x-livewire-material::button>`, which resolves through the view namespace whatever the
@@ -134,8 +130,6 @@ class LivewireMaterialServiceProvider extends ServiceProvider
             static::componentPath(),
             filled(config('livewire-material.prefix')) ? config('livewire-material.prefix') : 'livewire-material',
         );
-
-        View::addNamespace(hash('xxh128', static::componentPath()), static::componentPath());
     }
 
     /**