kookr-demo-recordinglisted

# Demo Recording ## When to Use When you need to generate, verify, or regenerate the Kookr demo video and its distribution formats, with or without voice narration. ## Quick Reference ### ALWAYS check scenario alignment first The recording drives the **real current frontend** (built by `pnpm build`, served by the E2E test server), so the video always shows the current UI by construction. What drifts are the *selectors and flows in the demo script*. Before any recording — and after any significant frontend change — run: ```bash pnpm demo:check ``` This replays the entire scenario headless with all holds capped to ~150ms, no TTS, no video, no exports (~1 min). It fails loudly on any selector or flow drift and ends with `CHECK PASSED` when the script is fully aligned with the current UI. Never record without a passing check. ### Always prefer narrated video The `.env` file in the repo root has `HF_TOKEN` and `KOOKR_TTS=true`. Copy it to the worktree if needed, then record with TTS: ```bash cp $HOME/git/kookr/.env .env # if in a worktree pnpm demo:record # reads .env automatically ``` Only record silent if TTS is genuinely unavailable (Docker down, no HF token). ### Silent video (fallback only) ```bash KOOKR_TTS= pnpm demo:record ``` ### With external TTS service (already running) ```bash KOOKR_TTS_URL=http://localhost:8004 pnpm demo:record ``` ### Opening hook variants (A/B testing) The first narration line is selectable — everything else sta