Papercut storyboard

The storyboard is the plan every scene is built from. It names the camera move and the cut for every scene, so the scene agent doesn't invent them. A brief that says "CameraPush or your own transform" gets a flat push or a hand-rolled zoom in every scene, and the kit's camera moves go unused.

Preflight

• Install: Minimal is enough. With a library, check library/papercut/CATALOG.md (sections "paper/camera.tsx" and "paper/transitions.tsx") for each move's props and when it fits. If the file is missing or stale, run python3 $PAPERCUT_LIB/tools/catalog.py. Resolve $PAPERCUT_LIB from the environment, else the PAPERCUT_LIB= line in ~/.config/papercut-explainer/config.env, else ask once.
• Needs narration/script.json and papercut/STORYBOARD.md with the HOOK block and the staging table (banner, set, prop, UI moment, mascot, gag per row). Missing: run papercut-hook and papercut-script.
• Backdrop sheet for choosing sets: library/papercut/public/bg/backdrops/_sheet.jpg. Open only what the step needs.

1. Global rules

Put these at the top of STORYBOARD.md, under the HOOK block. Palette by role (rotate background colours per set): ../papercut-explainer/references/style-guide.md section 5. Fonts: section 6. Canvas and zones: section 4. A feature-unlock that suits one extended metaphor can use section 12.

• 1080x1920, 30 fps. Banner at 14-21% height, caption band 68-80% (it shifts per scene to stay off faces), bottom 20% clear.
• Light from the top-left. Saturation only on characters, captions and signals.

2. Camera / Cut table

One row per scene, before the scene blocks. Every row names a component from the kit's paper/camera.tsx and the CutSeries kind (from paper/transitions.tsx) for the cut into that scene.