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/layout/pane.css

@@ -21,7 +21,7 @@
  * way it goes, so it mirrors in a right-to-left document (§ Layout → Bidirectionality / RTL).
  *
  * In `material.layout`; `hide-below`/`hide-from` come from visibility.css. Imports app-bar.css and
- * button.css for the pane's own top app bar and its back button (plan step 36 carry-over).
+ * button.css for the pane's own top app bar and its back button.
  */
 
 @layer material.reset, material.tokens, material.base, material.layout, material.components, material.text, material.visibility;

resources/css/layout/scaffold.css

@@ -2,9 +2,7 @@
  * <x-scaffold>: M3's scaffold — bars, then rails, then panes (docs/reference/m3/foundations.md
  * § Layout → Scaffold) — as a column: an optional `banner` full width, a row below it holding the
  * adaptive navigation rail and the content region, the bottom navigation bar on a compact window,
- * and the snackbar host. Plan step 36 (navigation group) moves in everything the view drew with
- * Tailwind; `data-md-scaffold-fab` and the content region's `--md-layout-margin` are step 35's,
- * unchanged below.
+ * and the snackbar host.
  *
  * `--material-margin` is M3's window margin, which the content region pads itself with and an
  * application's own rules can read: 16px below `medium`, 24px from it
@@ -23,11 +21,11 @@
  * `[data-md-scaffold-content]` — the rail's sibling — is always a flex column, so the page's own
  * bar, the FAB wrapper and `<main>` stack regardless of the row's own display.
  *
- * `[data-md-scaffold-actions]`'s column layout is `rail-collapsed:flex-col`, the one Tailwind
- * variant scaffold.blade.php still used (`resources/css/tailwind.css`, removed with this rule): the
- * actions row is always inside a rail, never the rail element itself, so it reads
- * `--md-navigation-rail-value` with `@container style()` like any other application content does
- * (`resources/css/components/navigation-rail.css`), rather than copying the rail's own conditions.
+ * `[data-md-scaffold-actions]`'s column layout comes from a container style query on
+ * `--md-navigation-rail-value: collapsed`: the actions row is always inside a rail, never the rail
+ * element itself, so it reads that property with `@container style()` like any other application
+ * content does (`resources/css/components/navigation-rail.css`), rather than copying the rail's
+ * own conditions.
  *
  * `[data-md-scaffold-bar]` pins the navigation bar to the window's bottom edge below `medium`, at
  * z-index 30: over the page, under the rail's scrim (40) and the snackbar (50, toast.css). While a
@@ -38,8 +36,7 @@
  * (toast.css), a placed toolbar (toolbar.css) and the content region's bottom padding. Without a
  * bar, or from `medium`, the scaffold publishes nothing and each reader falls back to 0px. A bar that has slid
  * away on scroll drops its own height from the variable (navigation-bar.css); that rule wins
- * because `material.components` comes after this file's `material.layout`, where before this
- * rewrite the variable was a Tailwind utility and the override had to sit outside every layer.
+ * because `material.components` comes after this file's `material.layout` in the cascade.
  *
  * The content region's `<main>` is matched as the content wrapper's own child, so a `<main>` an
  * application nests inside the page takes none of the region's padding or clipping.