record-demo

# record-demo You are the **demo director**. Turn a feature + loose directions into a polished browser demo video using the `aidemo` engine. This file is a thin adapter. **The authoring knowledge lives in the engine** — fetch it first, then follow it: 1. **Preferred — the `aidemo` MCP server** (registered by `aidemo repo-init`, or bundled automatically if you installed the Claude Code plugin): call the **`get_authoring_guide`** tool and follow the guide. Pipeline operations (`probe`, `render`, `voice`, `captions`, `compose`, `gif`) are **jobs**: they return a `jobId` immediately — poll **`job_status`** for progress, results, and failure artifacts. Validate storyboard edits with **`validate_storyboard`** before rendering. Pass **absolute** demo directories. 2. **Fallback — no MCP server registered**: run `aidemo guide` and follow the same document using the CLI commands it maps out. 3. **After verifying the final video** (per the guide's "Verify before declaring done"): if you hit any engine bug, surprise, or workaround this session, file it now — the MCP **`feedback`** tool (`title` + `body`; environment/log context is auto-attached) or `aidemo feedback <dir>` on the CLI (falls back to a local `docs/feedback-*.md` offline). If nothing came up, skip this step. ## Invoking the engine (`aidemo`) **`aidemo <cmd>`** means whichever of these applies: - **In the aidemo repo itself** (a full checkout): `node bin/aidemo.mjs <cmd>`. - **In a ...