hyperframes-cli

Run npx hyperframes render --quality high --output out.mp4 after the composition passes the check gate and the user approves the Studio preview. Verify the output file exists, is non-empty, and has a plausible duration with ffprobe.

lint is a fast static analysis for iteration feedback, while check is the required final gate that reruns lint plus runtime, layout, motion, and WCAG contrast audits in one browser session. Do not run a standalone lint immediately before check since check already includes it.

Use hyperframes cloud render for zero-infrastructure HeyGen-hosted rendering, Lambda only when AWS ownership is required, and Cloud Run only when GCP ownership is explicit. Local render remains the fastest option for iteration.

Run npx hyperframes doctor first to diagnose missing FFmpeg, missing bundled Chrome, low memory, or sandbox restrictions. Fix missing Chrome with npx hyperframes browser ensure, and note that doctor --json always exits zero so gate on its payload.

Declare variables in the composition with data-composition-variables, then run render --batch rows.json with an output template like renders/{name}.mp4. Use --strict-variables to validate every row before rendering and inspect the generated manifest.json for failures.

Never render merely because checks pass; pause at the final Studio preview and wait for explicit user approval. Also avoid the deprecated validate, inspect, and layout aliases, which are replaced by check.