Teach 2.0's plain CSS in the Boost guidelines and skills

2.0.0 took Tailwind out of the stack, but the texts Boost copies into
every application still taught its utilities: the core guideline said
"built on Tailwind CSS", the always-on material-3 guideline wrote every
rule as `bg-primary`, `type-*`, `rounded-corner-*`, `state-layer` and
`medium:`, and both skills' tables and examples did the same. None of
those classes exists in 2.0's stylesheets, so an agent following the
guideline wrote markup that compiled to nothing. Found moving ReStride
onto 2.0: its CLAUDE.md, and SealShare's, carry these texts.

The guidelines and skills now teach what 2.0 has: component and layout
component props (`gap="space200"`, `hide-from="medium"`), the `md-type-*`,
`md-ink-*` and interaction classes, and `--md-sys-*` tokens in the
application's own CSS, with breakpoints as range media queries.
UPGRADE.md §1, §2 and §4 describe the finished move instead of the
in-between state, and header comments that pointed at the removed
tokens/utilities.css and tailwind.css, or called a component "still
Tailwind", say what is true now.

BoostVocabularyTest runs DesignGuard over the code in every shipped
guideline and skill (fenced Blade and CSS, and each inline class list),
so a text that teaches a class the stylesheets do not define fails the
suite; it finds 268 violations in the texts as 2.0.0 shipped them. The
guard's own table of what it reports is exempt. BoostResourcesTest now
asks the design skill for each breakpoint's prop value and media query
instead of the removed `medium:` variants.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

resources/css/components/progress.css

@@ -11,9 +11,8 @@
  *
  * Linear mirrors in a right-to-left document unconditionally — M3's own rule for this indicator,
  * not the `mirror-rtl` a caller opts an icon into. The sizing here is a default only: an
- * application's own class, unlayered or in Tailwind's `utilities` layer, always outranks
- * `material.components`, so `w-*`/`size-*` still narrows or grows the indicator exactly as it did
- * before this file existed.
+ * application's own unlayered class always outranks `material.components`, so an `inline-size` or
+ * `block-size` of its own narrows or grows the indicator.
  *
  * resources/js/progress.js reads and writes `data-md-value`, `data-md-max`, `data-md-circular`,
  * `data-md-wavy` and `data-md-thick` — ProgressIndicator.kt, WavyProgressIndicator.kt and its