Build the Workbench's package CSS apart from Tailwind

Plan step 37 review. @tailwindcss/vite inlines the imports of an entry
that uses Tailwind without Vite's skipDuplicates, so with all.css beside
@import 'tailwindcss' every shared component stylesheet repeated later in
the cascade (231 repeated rules; button.css's hover and disabled rules
thirteen times), and every browser test ran against an order no
application gets. workbench/resources/css/package.css now holds all.css
and the scheme in an entry Tailwind never touches, and app.css keeps
Tailwind for the showcase's classes. The built package CSS repeats no
rule, and the Workbench's CSS shrinks from 559 to 406 KB.

Both entries open with the same layer statement, properties first,
because Tailwind hoists that layer to the top of its output; the order
is the one the single entry had, whichever the page links first. The
showcase's Vite config, vite.config.js and the error page test's probe
manifest name the new entry.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Qwx5USif3wFFmxtHg5U1g9

workbench/app/Providers/WorkbenchServiceProvider.php

@@ -19,6 +19,8 @@ class WorkbenchServiceProvider extends ServiceProvider
     public function boot(): void
     {
         config(['livewire-material.showcase.vite' => [
+            // The package's CSS apart from Tailwind's, so Vite deduplicates its imports (package.css).
+            'workbench/resources/css/package.css',
             'workbench/resources/css/app.css',
             'workbench/resources/js/app.js',
         ]]);

workbench/resources/css/app.css

@@ -1,16 +1,11 @@
-/* The Workbench builds the package as an application would, with explicit sources so the plans
-   in docs/ are not scanned for class names. The layer statement puts the `material` layers above
-   Tailwind's preflight (`base`) and below its `components` and `utilities`: a rewritten component's
-   padding, margin and border would otherwise lose to preflight's `* { padding: 0 }`, which the
-   material reset already carries, while every utility still outranks the package. all.css brings
-   the foundation, every layout stylesheet and every component stylesheet in one import; tailwind.css
-   brings the theme and token utilities the showcase still writes as classes, without declaring the
-   tokens a second time. */
-@layer theme, base, material, components, utilities;
-@import '../../../resources/css/all.css';
+/* The Workbench's Tailwind entry, for the classes the showcase still writes, with explicit sources
+   so the plans in docs/ are not scanned for class names. tailwind.css brings the theme and token
+   utilities without declaring the tokens a second time. The package's own CSS is package.css, an
+   entry of its own (its header says why); the layer statement is the same in both, so the
+   `material` layers sit between Tailwind's preflight and its utilities whichever loads first. */
+@layer properties, theme, base, material, components, utilities;
 @import 'tailwindcss' source(none);
 @import '../../../resources/css/tailwind.css';
-@import './material-scheme.css';
 
 @source '../../../resources/views';
 @source '../../../src';

workbench/resources/css/package.css

@@ -0,0 +1,16 @@
+/* The package's CSS for the Workbench, built the way an application without Tailwind builds it:
+   all.css (the foundation, every layout and every component stylesheet) and the Workbench's
+   scheme, in an entry Tailwind never touches. Vite's own CSS pipeline inlines the imports here and
+   keeps a stylesheet several components import once, at its first position — the order an
+   application gets. `@tailwindcss/vite` inlines the imports of an entry that uses Tailwind without
+   that deduplication, so all.css imported beside `tailwindcss` would repeat every shared rule later
+   in the cascade; app.css keeps Tailwind, for the showcase's classes, apart.
+
+   Both entries open with the same layer statement, so the order holds whichever the page links
+   first: the `material` layers above Tailwind's preflight (`base`), whose `* { padding: 0 }` would
+   otherwise beat a component's padding, and below its `components` and `utilities`. `properties`
+   is the layer Tailwind hoists to the top of its output (the `--tw-*` fallbacks for a browser
+   without `@property`); named first, it stays lowest, as it was when both shared one entry. */
+@layer properties, theme, base, material, components, utilities;
+@import '../../../resources/css/all.css';
+@import './material-scheme.css';