Registry artifact corruption + four token bugs found during crashoverride.com adoption audit

Found while auditing/retheming crashoverride.com against this design system (crashappsec/digital-marketing#1745).

## 1. Published registry serves corrupted theme.json (P1)
`https://crashappsec.github.io/react-design-system/r/theme.json` contains U+FFFD replacement characters at two positions in `tokens.css` decorative comment lines (~lines 208, 235) where the repo source has U+2500 box-drawing characters. Likely a charset issue in the registry build or Pages pipeline. Downstream consumers vendoring via `shadcn add` get mangled bytes. (digital-marketing's sync tooling currently detects and skips U+FFFD'd theme files as a workaround.)

## 2. `--text-label-cobalt` / `--text-label-teal` fail AA in dark mode
`#A05FC0` (Fandango 400-equivalent) on `#0B1221` = **4.36:1** — below 4.5:1 for the small uppercase eyebrow text it's used for. Suggest binding to `--color-cobalt-300` `#BE8FD4` (7.19:1).

## 3. Light-mode `--text-label-amber` fails AA
Light block rebinds to neon-800 `#5E8A00` = **4.11:1** on white. Suggest neon-900 `#466700` (6.56:1).

## 4. Light mode never overrides the focus ring
Atomic Lime `#B3FF00` ring on white = **1.22:1** (needs 3:1 non-text). The light block doesn't re-bind `--focus-ring`/`--ring`-equivalent. Suggest Fandango in light (6.80:1).

## 5. Teal split-brain
`--color-teal-400` maps to Jazzberry while `--text-label-teal` maps to Fandango — a component using both (e.g. a teal-labeled chip) renders purple text in a pink chip. One mapping should win.

Contrast ratios are WCAG relative-luminance computations from the adoption audit (digital-marketing `docs/plans/2026-06-10-marketing-ds-audit.md` on branch `feat/marketing-ds-retheme`).