Import the components in the documented installation

Plan step 37 review. Removing material.css left README.md, the
development skill, UPGRADE.md and the tailwind.css and foundation.css
headers telling an application to import foundation.css, tailwindcss and
tailwind.css in its place. material.css was also what brought layout.css
and components.css, so that install rendered every component unstyled,
and without a layer statement Tailwind's preflight would have outranked
the package's layers.

The skill's snippet is now the Tailwind-free one 2.0.0 ends with: the
foundation, then the stylesheet of each component the views render, or
all.css. README.md, whose layout and prose still assume Tailwind, shows
all.css in its own entry and Tailwind in a second, both opening with the
layer statement, the shape the Workbench now builds; the skill and
UPGRADE.md describe that interim in a sentence.

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

resources/css/foundation.css

@@ -24,8 +24,9 @@
  * (`button { … }`) restyles the components too. foundation/hidden.css keeps its two `!important`
  * rules outside the layers, so `hidden` and `x-cloak` hide an element whatever sets its display.
  *
- * Until the components leave Tailwind, an application still building it imports this file before
- * `@import 'tailwindcss'`, so the `material` layers are declared first and sit below Tailwind's.
+ * An application still building Tailwind keeps it in a separate entry and opens both entries with
+ * `@layer properties, theme, base, material, components, utilities;`, so the `material` layers sit
+ * above Tailwind's preflight and below its utilities (resources/css/tailwind.css's header).
  */
 
 @layer material.reset, material.tokens, material.base, material.layout, material.components, material.text, material.visibility;