Take Tailwind out of the package, and its detection out of the guard

Tailwind left the stack in 2.0.0, but the package still carried about 330
mentions of it. What the guard's Tailwind detection protected — a class
that compiles to nothing — is now protected by a check that does not care
where a dead class came from.

DesignGuard: about 500 lines of Tailwind tables, scales, palettes and
"2.0.0 replacement" hints give way to one check — a class a view or PHP
file writes that neither the application's stylesheets nor the package's
own declare. It catches a utility of any framework, a typo and a class
whose rules were deleted alike, so it also found two classes ReStride
draws nothing with. A stylesheet has to be in reach for it: the `.css`
files among the scanned paths, or what the `missingStylesheets()` entry
imports. The class reader no longer mistakes an array index for a class
list (`$block['base']`), and it reads the array a class helper is given,
where it read nothing before.

The package's own three Tailwind self-guards go with it. Only their one
unique check stays, as a test of its own: every `matchMedia` width in
resources/js is an M3 breakpoint.

The pagination views are `material.blade.php` and
`simple-material.blade.php`; only Laravel's and Livewire's default theme
names ever made them `tailwind`. The provider sets `Paginator`'s default
views and switches `livewire.pagination_theme` to `material` when it is
still Livewire's own default, so no application can forget the config; a
theme an application chose, and a component's own `$paginationTheme` or
`paginationView()`, still win.

The rest is prose: the layer-order guidance for an application that still
builds Tailwind, the Tailwind wording in the README, the Boost guidelines
and the development skill, and about 25 "this used to be a Tailwind
utility" comments, along with every "plan step NN" pointer into a
gitignored folder. The reset keeps its credit, and NOTICE now carries it
too.

Feature suite 1159 passed, Chrome browser suite 299 passed.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

resources/views/pagination/livewire/material.blade.php

@@ -1,7 +1,7 @@
-{{-- Livewire's paginator, drawn in M3. The package puts this in front of Livewire's own
-     `livewire::tailwind` (config `livewire-material.pagination`), whose gray and blue classes do
-     not exist in an M3 theme. The file keeps Livewire's view name; nothing in it is Tailwind — the
-     drawing is resources/css/components/pagination.css.
+{{-- Livewire's paginator, drawn in M3. The name is `material`; Livewire resolves
+     `livewire::` . config('livewire.pagination_theme') to find it, and the provider sets that
+     config to `material` (config `livewire-material.pagination`) while it still reads as
+     Livewire's own default. The drawing is resources/css/components/pagination.css.
 
      The wiring is Livewire's, unchanged: `previousPage`, `nextPage` and `gotoPage` with the page
      name, and the scroll back to the top of whatever `scrollTo` names. A page number is drawn as a

resources/views/pagination/livewire/simple-material.blade.php

@@ -1,5 +1,7 @@
-{{-- Livewire's simple and cursor paginator, drawn in M3: previous and next as outlined buttons
-     (the package puts this in front of `livewire::simple-tailwind`). --}}
+{{-- Livewire's simple and cursor paginator, drawn in M3: previous and next as outlined buttons.
+     The name is `simple-material`; Livewire resolves `livewire::simple-` . config
+     ('livewire.pagination_theme') to find it, which the provider sets to `material` while it
+     still reads as Livewire's own default. --}}
 
 @php
     if (! isset($scrollTo)) {