The deliverable is the single merged plan.json — the same shape the
single-pass system prompt emits — and the multi-clip video is what the
node itself produces from it: each shot renders as its own clip, chained
through the H3 context loop into one continuous video. Removed the
--clips per-scene export (external stitching is NOT the design).
Workflow restated everywhere: outline turn -> the LLM writes each scene
one at a time (one focused turn per scene) -> build_plan.py puts it all
together at the end into plan.json -> paste once, queue once.
build_plan.py: --clips option and export block removed; docstring now
describes the node-side chaining. README: intro/example/validating/
wiring rewritten around the single deliverable. SKILL.md: goal, Step 3
(Put it all together at the end), Step 4 (the node makes the multi-clip
video), and the revising loop updated. Suite + --check green.
build_plan.py --clips [DIR] (default clips/) now exports one validated
single-shot plan JSON per scene (clip_01.json, ...) alongside the merged
plan. Each clip renders through plan_json_input as its own video at FULL
duration (no chain overlap trim), then the clips are stitched in order;
the mid-motion open/close craft rules make the cuts read as one take.
plan.json stays as the optional single continuous-take render.
SKILL.md Step 3/4 rewritten (merge exports clips + plan; deliver =
render-per-clip then stitch), README intro/example/wiring/validating
updated to multi-clip-first with real clip output shown. Verified from a
simulated project root: export green, every clip re-checks PLAN OK.