docs(web): soften README typography rules per review

Clarify that raw uppercase is legacy-only (prefer text-display for new
code) and broaden when normal-case is appropriate on DS buttons.

Co-authored-by: Cursor <cursoragent@cursor.com>

web/README.md

@@ -67,12 +67,12 @@ Read before adding or editing UI styles. These rules keep the dashboard legible
   - `text-text-disabled` — disabled states.
   - `text-text-on-accent` — text on filled accent surfaces.
 
-### Brand uppercase via `text-display`, never `uppercase`
+### Brand uppercase via `text-display`, not raw `uppercase`
 
 - The dashboard preserves the Nous brand uppercase aesthetic, but it is **opt-in per element, not global**.
 - Apply uppercase via the DS utility `text-display` on **brand chrome only** — page titles, nav section headings, badges, brand wordmark. DS components (`Button`, `Badge`, `Tabs`, `Segmented`, etc.) already self-apply `text-display`.
-- **Do not** add `uppercase` (the literal Tailwind class) anywhere in `hermes-agent/web/src`.
-- **Do not** add `normal-case` to "opt out" of inheritance — the app shell no longer forces uppercase, so opt-outs aren't needed. The only legitimate `normal-case` overrides are on DS `<Button>` instances that display **dynamic, user-typed content** (model slugs, theme names, language names, profile names).
+- **Do not introduce new `uppercase`** (the literal Tailwind class) in `hermes-agent/web/src`. Prefer `text-display` for new brand chrome. Legacy `uppercase` call sites (e.g. `components/ui/label.tsx`, `card.tsx`) remain until migrated.
+- The app shell no longer forces uppercase globally, so blanket `normal-case` opt-outs are unnecessary. Use `normal-case` only where a DS component applies `text-display` but the label should stay sentence case — e.g. dynamic user content (model slugs, theme names) **or** fixed UI copy that is not brand chrome (EnvPage “not configured” toggle, sidebar “New chat”).
 
 ### Fonts