feat: add launch video animation scenes

[Miyamura80]

Summary

• Adds Storybook-based animation components for the Desktest CLI launch video (8 scenes: Title, Run, Loop, Debug, Codify, QA, Orchestration, Closing)
• Includes a Playwright headless recording pipeline that captures at 1920x1080 and converts to H.264 MP4 via ffmpeg
• Pure CSS keyframe animations with React functional components — no animation libraries

Test plan

• Run cd animations && bun install && bun run storybook to view individual scenes at localhost:6020
• Run node animations/scripts/record-animation.mjs to record the full ~78s launch video
• Verify animations/recordings/desktest-launch.mp4 plays correctly with all 8 scenes

🤖 Generated with Claude Code

---

Summary by cubic

Adds a new media/animations/ workspace with Storybook React scenes for the Desktest CLI launch video and a Playwright + ffmpeg recorder that exports a 1080p H.264 MP4. Also adds a launch demo video link to the root README.

• New Features

  • Eight React scenes with per-scene stories and a DesktestLaunchAnimation sequencer in Storybook (using @storybook/react-vite, port 6020).
  • Headless recording script (media/animations/scripts/record-animation.mjs) using playwright to capture 1920×1080 and transcode to H.264; outputs to media/animations/recordings/ (gitignored).
  • Dev docs added for timings and code review notes.

• Migration

  • In media/animations/, install deps and start Storybook on port 6020; update STORYBOOK_URL in record-animation.mjs only if you change the port.
  • Run node media/animations/scripts/record-animation.mjs (requires ffmpeg on PATH). Output: media/animations/recordings/desktest-launch.mp4.

^{Written for commit f008007. Summary will update on new commits.}

[qodo-code-review]

ⓘ You've reached your Qodo monthly free-tier limit. Reviews pause until next month — upgrade your plan to continue now, or link your paid account if you already have one.

[cubic-dev-ai]

2 issues found across 28 files

Confidence score: 4/5

• This PR looks safe to merge with minimal risk: the reported issues are mostly hygiene/config consistency rather than likely runtime regressions.
• The most severe item is in animations/.gitignore (6/10, high confidence): not ignoring recordings/*.mp4 can lead to large binary artifacts (like desktest-launch.mp4) being committed, which can bloat repo history and complicate maintenance.
• In animations/package.json, the Storybook port mismatch (6006 vs documented 6020) is a low-to-moderate coordination issue and may cause test-plan confusion, but it is unlikely to break production behavior.
• Pay close attention to animations/.gitignore and animations/package.json - prevent future MP4 commits and align the Storybook port with the documented test plan.

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="animations/package.json">

<violation number="1" location="animations/package.json:5">
P2: The storybook port (`6006`) doesn't match the port documented in the PR test plan (`6020`). Update the script to use `-p 6020` if that's the intended port, or update the PR description.</violation>
</file>

<file name="animations/.gitignore">

<violation number="1" location="animations/.gitignore:2">
P2: Missing `recordings/*.mp4` from `.gitignore`. The recording pipeline outputs MP4 files, and `desktest-launch.mp4` is already tracked in the repo. Large binary video files should not be committed to git as they permanently bloat repository history.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review, or fix all with cubic.}