motion-render

原文涵盖的主题

• Motion Render
• Agent Workflow (MANDATORY)
• Overview
• Critical Rules
• Architecture
• Reference Guide
• Concepts
• Templates

The production half of the fuse-motion pipeline: from .motion/brief.md and .motion/beats.md (owned by motion-method) to a verified file. A film is a pure function of time — an HTML or canvas scene exposing window.seek(t) — captured frame by frame by headless Chrome over the DevTools Protocol with zero dependencies, then encoded by ffmpeg (H.264 mp4 + palette GIF). Rendering is staged: stills (the default when --stage is omitted, so a forgotten flag can never skip a gate) → owner gate G1 → draft 540p → critic + owner gate G2 → master, whose FILE is verified by ffprobe, frame count, byte budget and SSIM against the approved stills. Terminal subjects use VHS tapes; sound, when the brief asks for it, follows the audio reference. Templates are generalized from the proven docs/demo/statusline-mod/ and docs/demo/hook-sniper.tape pipelines and were run end to end before shipping. 1. Read the locked inputs: .motion/brief.md (surfaces, byte budgets, aspect, duration) and .motion/beats.md — if either is missing, go back to motion-method. 2. Check tools: ffmpeg -version, ffprobe -version, bun --version, a Chrome binary (or CHROMEBIN); vhs --version + ttyd for terminal films. Missing tool → say

这里只展示节选，请以完整原文和当前要求为准。