create-storyboard-html

Purpose

Every video project's storyboard.html is the single review surface — the operator opens it once and sees the latest state of every gate (idea brief → lyric/script → keyframes → animations → master). Per STORYBOARD.md at the repo root and the music-video-ad molecule's doctrine, all assets/handoffs/review notes land in this one file.

Hand-authoring the HTML across many states drifts. This atom replaces that with a fragment + render contract: each state writes a small JSON fragment under <video_folder>/_state/NN-<slug>.json, and scripts/render_storyboard.py collates them into the final HTML.

When to use

• Initializing a new ad — write a State 0 fragment and render the shell so the operator has a URL to bookmark from day one.
• After every state advance — append the new state's fragment, re-render. The pipeline already runs update-storyboard as a post-step in music-video-ad and create-cartoon-music-video; this atom is what those post-steps call.
• Reviewing — open <video_folder>/storyboard.html.

Use the legacy hand-authored route only if the project is one-off or the fragment kinds don't cover the format. For music-video, cartoon-music-video, comic-strip, and most narrator-driven ads the fragment kinds below are sufficient.

Fragment schema

<video_folder>/_state/<order-prefix>-<slug>.json. The order prefix decides where the section lands in the rendered HTML — use the orchestrator's state numbering (1-, 2-, 2.5-, 2.6-, 3-, 3.5-, 5-, 5.5-, 7-, 7.4-, 7.5-, 8-, 9-, 10-).