Draw the scaffold without Tailwind

Plan step 36 (navigation group, third batch): <x-scaffold>'s own
styling moves into resources/css/layout/scaffold.css (the content
region, the bar and rail row, the banner, the actions row and its
rail-collapsed column layout, --material-bottom-bar and
--material-margin publishing, the skip link) alongside step 35's FAB
and content-margin rules already there. Every data-app-shell* hook
becomes data-md-scaffold-* (data-app-shell-bar, -actions, -banner);
the skip link is data-md-skip-link; data-app-shell itself is dropped,
data-md-scaffold already named the root.

The actions row's rail-collapsed:flex-col is written out branch for
branch as the navigation rail's own rewrite did for its internal
parts: the three width-independent conditions in one :where() group,
the four width-gated ones each in their own @media block. With that
gone, resources/css/tailwind.css's rail-collapsed custom-variant
shim (its last use) is removed; tailwind.css now carries only
tokens/theme.css and tokens/utilities.css, which the showcase still
needs until step 38.

navigation-bar.css's hide-on-scroll rule reading --material-bottom-bar
stayed unlayered only because <x-scaffold> published that variable
through a Tailwind utility, which no layered rule could outrank; now
scaffold.css sets it itself in material.layout, a layer
navigation-bar.css's own material.components always beats, so the
rule moves into the layer and the file fits one
@layer material.components block like every other navigation
stylesheet. navigation-bar rejoins NavigationStylesheetsTest.php's
dataset and NavigationBarTest.php's own duplicate shape test is
retired in favour of it.

Browser tests added (docs/plans/material-3-browser-tests.md): the
scaffold's FAB dropping the bar's own height once hide-bar-on-scroll
slides it away, at the trailing edge in a right-to-left document, and
clearing a safe area an application sets on its inline-end and bottom
edges.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Qwx5USif3wFFmxtHg5U1g9

tests/Feature/Components/NavigationStylesheetsTest.php

@@ -15,16 +15,17 @@ use NoNameWeb\LivewireMaterial\Tests\Support\ViewClasses;
  * The dataset grows by one name per component commit, the same rule ContainmentStylesheetsTest.php
  * and the earlier groups follow. `<x-tabs>` and `<x-tab>` share one stylesheet (tabs.css) and one
  * commit, so `navigationViews()` maps the 'tabs' entry onto both blade views; every other entry is
- * one view, one stylesheet, as usual. `navigation-bar` is not in this dataset: its stylesheet keeps
- * one rule unlayered on purpose (still beating a Tailwind utility <x-scaffold> has not lost yet),
- * so its shape does not match every other entry's single `@layer material.components` block; the
- * same checks, adjusted for that one rule, are in NavigationBarTest.php instead — the same reason
- * ContainmentStylesheetsTest.php gives for leaving the error layout to ErrorPagesTest.php.
+ * one view, one stylesheet, as usual. `navigation-bar` rejoined the dataset with the scaffold's own
+ * rewrite: its one rule reading `--material-bottom-bar` stayed unlayered only while `<x-scaffold>`
+ * published that variable through a Tailwind utility, which no layered rule could outrank; now
+ * scaffold.css sets it in `material.layout`, which this file's `material.components` always beats,
+ * so the whole stylesheet fits one `@layer material.components` block like every other entry here.
  */
 dataset('navigation components', [
     'app-bar',
     'toolbar',
     'tabs',
+    'navigation-bar',
     'navigation-bar-item',
     'navigation-rail',
     'navigation-rail-item',