hyperframes-cli

Run npx hyperframes check as the final gate, open npx hyperframes preview for user approval, then run npx hyperframes render --quality high --output out.mp4. Verify the output 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 and then audits runtime errors, layout, motion sidecar assertions, and WCAG contrast in one browser session. Do not run a redundant standalone lint immediately before check.

A common cause is a video or audio element nested inside a sub-composition template, which is never seeked or decoded. Media must be a direct child of the host root index.html; grep compositions/*.html for video/audio tags and snapshot each scene to confirm footage appears.

Declare variables in the composition with data-composition-variables, then run npx hyperframes render --batch rows.json --output "renders/{name}.mp4". Each JSON row supplies one render's variables, and a manifest.json tracks per-row status, output, and errors.

Run npx hyperframes doctor first; it checks Node.js version, FFmpeg, Chrome, memory, and Docker. For missing bundled Chrome run npx hyperframes browser ensure, and gate CI on doctor --json by checking the payload's ok field since it always exits zero.