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/css/components/error-page.css

@@ -20,10 +20,10 @@
  * The page carries this file itself: `src/Support/ErrorPage.php` inlines it, with its imports, into
  * every error page (`Stylesheets::bundle()`) — beside the application's Vite tags when there is a
  * build (`layoutStyles()`), inside the whole fallback stylesheet when there is none
- * (`fallbackStyles()`, plan step 40) — so an application imports nothing for its error pages
- * (plan step 46). The body is still matched only when it holds the layout
- * (`body:has(> [data-md-error-page])`): an application that imports `all.css` has this file in
- * its bundle beside every other page, where a bare `body` rule would restyle them all.
+ * (`fallbackStyles()`) — so an application imports nothing for its error pages. The body is still
+ * matched only when it holds the layout (`body:has(> [data-md-error-page])`): an application that
+ * imports `all.css` has this file in its bundle beside every other page, where a bare `body` rule
+ * would restyle them all.
  *
  * The page's font is the foundation's, `--md-ref-typeface-brand` on `html` (foundation/base.css),
  * as the old `font-sans` was; only the fallback, which has no `@font-face`, uses a system stack.

resources/css/components/navigation-bar.css

@@ -78,14 +78,11 @@
      * A bar that has slid off the bottom of the window is no longer there to clear, so the offset
      * everything pinned to the bottom reads drops to the bottom safe area and whatever the
      * application has docked on the bar — a `fab` button, the snackbar and the page's own bottom
-     * padding all follow it down and come back up with it. Layered now, unlike before this
-     * rewrite: <x-scaffold> used to publish --material-bottom-bar with a Tailwind utility, which
-     * no rule in any layer could outrank regardless of specificity; now scaffold.css publishes it
-     * itself in `material.layout` (layout/scaffold.css), a layer this file's own
-     * `material.components` always outranks by declaration order alone — the same reason
-     * toolbar.css's and fab.css's overrides only have to beat another `material.components` rule,
-     * not chase a Tailwind utility out of the cascade. Keyed on `data-md-scaffold`, the hook the
-     * scaffold renders on its root, not `data-app-shell`, which that rewrite also retired.
+     * padding all follow it down and come back up with it. `<x-scaffold>` publishes
+     * `--material-bottom-bar` itself, in `material.layout` (layout/scaffold.css), a layer this
+     * file's own `material.components` always outranks by declaration order alone — the same
+     * reason toolbar.css's and fab.css's overrides only have to beat another `material.components`
+     * rule. Keyed on `data-md-scaffold`, the hook the scaffold renders on its root.
      */
     [data-md-scaffold]:has([data-md-navigation-bar][data-md-hide-on-scroll][data-md-hidden]) {
         --material-bottom-bar: calc(var(--material-safe-bottom, env(safe-area-inset-bottom)) + var(--material-bottom-extra, 0px));

resources/css/components/pagination.css

@@ -1,7 +1,8 @@
 /*
- * The paginators, Laravel's and Livewire's, drawn in M3 (resources/views/pagination/**): the package
- * puts its views in front of the frameworks' `tailwind` and `simple-tailwind` ones, whose names they
- * keep.
+ * The paginators, Laravel's and Livewire's, drawn in M3 (resources/views/pagination/**): named
+ * `material`/`simple-material`, put in front of the frameworks' own namespaces and set as
+ * Laravel's default view (`Paginator::defaultView()`/`defaultSimpleView()`) and, where Livewire
+ * still reads its own default, as its `pagination_theme`.
  *
  * The numbered paginator is a row: on its start, what the page holds in body-small on-surface-variant
  * — "21–30 of 95", or "Page 3 of 10" below `medium` (600px), where the page numbers give way and only