Loop the walkthrough and clarify Launch Control

[mattyu-dev]

What changed

• Replaced the manual replay control with an automatic Detect, Route, Prove loop that pauses off-screen, resumes cleanly, and stays static for reduced motion.
• Rewrote the landing page around the concrete product transformation: creative manifest in, deterministic checks and human review, reviewed launch plan and local receipt out.
• Fixed dark-on-dark headings, warning badges, microcopy contrast, mobile flow-arrow overlap, and the mobile Three.js token path.
• Tightened the desktop hero to two lines and raised active walkthrough labels to 12 px.
• Extended browser QA to prove loop restarts, off-screen RAF suspension, reduced motion, compositor integrity, mobile overflow, and the new copy contract.

Why

The landing page did not explain the SaaS clearly enough, the product trace required a manual replay, and several dark or undersized labels were difficult to read. Mobile screenshots also exposed short-lived asset and arrow overlaps.

Impact

Visitors now see a self-running product walkthrough and a direct explanation of what Launch Control accepts, does, and produces. The page remains read-only and makes the human approval boundary explicit.

Validation

• python -m unittest discover -s tests -q: 64 tests passed
• npm run qa:frontend: passed across 7 viewports
• Lighthouse desktop and mobile: 100 accessibility, performance, best practices, and SEO
• Mobile quality: LCP 1.652 s, TBT 0 ms, CLS 0
• Independent motion gate: two complete loops, off-screen pause and resume, reduced-motion static state, no black frames, no text or asset overlap