THE UI. One style block, ~40 hardcoded hex values, 0.72-0.85rem type throughout, caps
section labels, no focus ring, and an infinite striped animation with no reduced-motion
guard. Rewritten as a token system, keeping every existing class so no page markup had to
change:

- Palette from the subject rather than a template: cool graphite (not a tinted black),
  title-belt gold for the single primary action, and red/blue corner as a SEMANTIC pair —
  every bout is fighter 1 vs fighter 2, so those two carry meaning here.
- Numbers set in a monospace with tabular figures: frame counts, odds and durations are
  compared down a column.
- 16px fields everywhere, not just on mobile — .85rem was cramped on a desktop too, and
  16px is what stops iOS zooming on focus.
- Numeric inputs capped at 11rem. A frame count is three digits; a box stretched across
  half the viewport makes the form longer to scan and harder to aim at.
- Section headings instead of tracked-out caps labels, which were harder to read and made
  every group shout.
- Sticky nav, with the active page carried by aria-current — it drives the underline AND
  tells a screen reader where you are, where the old inline colour did neither.
- :focus-visible everywhere, and prefers-reduced-motion collapses the animated bar.

Reviewed against renders of all six pages; the density pass alone fits roughly one extra
section per screen on a form with 66 settings.

TWO STARTER TEMPLATES, seeded on first use and never overwritten, so the picker is never
an empty box. They describe the same show rendered by models with opposite strengths:

  Wan      8fps, 50-70 frame clips  -> a 45s short is 6-8 scenes
  LongCat  15fps, 173-333 frames    -> the same short is 2-4 scenes

LongCat's numbers are its own: 15fps is the rate it was trained at (8 was a Wan-era
compromise), 173 = 93+80 and 333 = 93+80x3 are whole segment counts, and all of them are
4n+1 — the VAE's rule, which the server also checks before a long run. Since the server
owns the segment loop for LongCat, those long scenes are one request each rather than
chained sub-renders with a re-encoded join and accumulating drift.

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