Resolve the package's own components through its namespace

Package views now write <x-livewire-material::button>, so a configured
prefix (which Blade spells <x-m::button>) and an application component
of the same name can no longer break or shadow them. The showcase
rewrites its examples to the configured prefix. Adds the README, and
waits for the adaptive rail to hear a resize before the navigation
tests press its menu button.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V9NnLxnPp8vaaurb3Z1MFy

src/LivewireMaterialServiceProvider.php

@@ -47,6 +47,15 @@ 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.
+     */
+    public static function componentPath(): string
+    {
+        return __DIR__.'/../resources/views/components';
+    }
+
     /**
      * The error-view root: a folder holding only `errors/`.
      */
@@ -105,11 +114,15 @@ class LivewireMaterialServiceProvider extends ServiceProvider
 
     /**
      * Register the components as anonymous Blade components under the configured prefix.
+     *
+     * The package's own views never go through this registration: they write
+     * `<x-livewire-material::button>`, which resolves through the view namespace whatever the
+     * prefix, and which an application's own `<x-button>` cannot shadow.
      */
     protected function registerComponents(): void
     {
         Blade::anonymousComponentPath(
-            __DIR__.'/../resources/views/components',
+            static::componentPath(),
             filled(config('livewire-material.prefix')) ? config('livewire-material.prefix') : null,
         );
     }