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>

src/Showcase/Sections.php

@@ -40,10 +40,10 @@ class Sections
             }
         }
 
-        // The Layout section's three canonical layouts (plan step 38): each is a page of its own
-        // rather than an anchor on the Overview, so its search entry carries its own URL; the
-        // page's own source joins the Layout section's for the component-homes scan below, so
-        // <x-list-detail>, <x-supporting-pane> and <x-feed> still find a home.
+        // The Layout section's three canonical layouts: each is a page of its own rather than an
+        // anchor on the Overview, so its search entry carries its own URL; the page's own source
+        // joins the Layout section's for the component-homes scan below, so <x-list-detail>,
+        // <x-supporting-pane> and <x-feed> still find a home.
         foreach (static::layoutPages() as $key => $page) {
             if ($key === 'layout') {
                 continue;
@@ -90,11 +90,11 @@ class Sections
     }
 
     /**
-     * The Layout section's own pages (plan step 38): the overview and the three canonical
-     * layouts, each on a page of its own, sharing one `<x-section-nav>` and the live breakpoint
-     * readout rather than three anchors on the Overview. They are not top-level destinations of
-     * their own — `Sections::all()` still has one `layout` entry for the rail and the overview
-     * grid — so this is their own small index instead.
+     * The Layout section's own pages: the overview and the three canonical layouts, each on a
+     * page of its own, sharing one `<x-section-nav>` and the live breakpoint readout rather than
+     * three anchors on the Overview. They are not top-level destinations of their own —
+     * `Sections::all()` still has one `layout` entry for the rail and the overview grid — so this
+     * is their own small index instead.
      *
      * @return array<string, array{title: string, icon: string, url: string}>
      */