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/Feature/TokensTest.php

@@ -39,8 +39,7 @@ function typeStyles(): array
 
 /**
  * The body of every `.md-type-…` class in text.css, keyed by class name without the `md-` prefix
- * (`type-display-lg`, `type-emphasized-display-lg`, …). Plain CSS now (plan step 39 deleted the
- * Tailwind utilities they used to be); text.css is theirs alone.
+ * (`type-display-lg`, `type-emphasized-display-lg`, …). Plain CSS; text.css is theirs alone.
  *
  * @return array<string, string>
  */
@@ -86,14 +85,9 @@ it('ships M3\'s medium and high contrast levels beside the standard one', functi
     }
 });
 
-// Tailwind's theme.css used to turn every scheme role into a `--color-*` Tailwind colour, in an
-// inline theme block so it resolved on the element and a nested data-theme still repainted it
-// rather than reading a value computed once on :root. Both went with Tailwind (plan step 39): the
-// first fact is already the scheme test above (every role a `--md-sys-color-*` custom property,
-// light and dark); the second no longer has anything to hold, because no file replaces theme.css's
-// alias — every package rule reads `--md-sys-color-*` directly at its point of use, so there is no
-// second custom property that could be computed once on :root and go stale under a nested
-// data-theme in the first place.
+// Every package rule reads a role's `--md-sys-color-*` custom property directly at its point of
+// use: no second alias computed once on `:root` that a nested `data-theme` could leave stale. The
+// scheme test above already proves every role is `--md-sys-color-*`, light and dark.
 it('never aliases a colour role to a second custom property resolved once on :root', function () {
     foreach (File::allFiles(packageCss()) as $file) {
         expect($file->getContents())->not->toMatch('/--color-[\w-]+:\s*var\(--md-sys-color-/', $file->getRelativePathname());