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>

tests/Browser/CascadeTest.php

@@ -7,13 +7,13 @@ use Livewire\Component;
 use Livewire\Livewire;
 
 /**
- * The central claims of the `@layer material` design (plan step 42, docs/plans/material-3-alignment.md
- * Decisions § "Components carry their styles as `data-md-*` attributes inside `@layer material`"),
- * each on its own small probe page: an application's unlayered rule beats a component default;
- * `[hidden]` beats a component's `display`; the layer order holds even when a component file is
- * imported before the foundation; a `data-md-*` attribute survives a Livewire `$refresh`; an icon
- * mirrors in a right-to-left document. Every other stylesheet claim (layers, imports, breakpoints,
- * no Tailwind) is StylesheetsTest.php's, asserted on the source rather than a rendered page.
+ * The central claims of the `@layer material` design — components carry their styles as
+ * `data-md-*` attributes inside `@layer material` — each on its own small probe page: an
+ * application's unlayered rule beats a component default; `[hidden]` beats a component's
+ * `display`; the layer order holds even when a component file is imported before the foundation;
+ * a `data-md-*` attribute survives a Livewire `$refresh`; an icon mirrors in a right-to-left
+ * document. Every other stylesheet claim (layers, imports, breakpoints) is StylesheetsTest.php's,
+ * asserted on the source rather than a rendered page.
  */
 function cascadeReady(mixed $page): mixed
 {
@@ -71,8 +71,8 @@ it('lets [hidden] beat a component\'s display', function () {
 });
 
 it('keeps the layer order even when a component file is imported before the foundation', function () {
-    // Every package stylesheet opens with the same full `@layer` statement (plan step 33), so the
-    // order it establishes holds whichever file a page reaches first — the error layout's copy of
+    // Every package stylesheet opens with the same full `@layer` statement, so the order it
+    // establishes holds whichever file a page reaches first — the error layout's copy of
     // it, reached here before the foundation's. The two prebuilt error-page stylesheets, in that
     // deliberate order: the layout's bundle, whose button.css rules sit in `material.components`,
     // physically precedes the fallback's foundation reset, in `material.reset` — and still loses