Remotion changelog prompt — release notes to video

<direction> A 9-second changelog film for v2.4.0 — 2 new, 1 fixed, 1 improved. A version header lands first; then four change rows slide in from the left, each with a tag pill (NEW in the accent, FIXED in white, IMPROVED in grey) and one plain-language line. A FULL NOTES → pointer closes the film. Sample notes, labelled in the header. Near-black background, one orange accent. Banned: glows, gradients, confetti for a bugfix, marketing adjectives in the change lines, more rows than fit (four is the cap at this size). </direction> <structure> Beat 1 (0–0.7s): version + RELEASE NOTES header. Beats 2–5 (1.0–6.0s): one row per beat — slide-in from -50px with a spring settle, hairline divider under each. Beat 6 (6.8s): the FULL NOTES → line springs in with a one-line pitch. Hold. </structure> <build> One Remotion composition, 1280x720 landscape, 30fps. Rows are a data array ({tag, text}); tag colours map from the tag value, so a row cannot wear the wrong pill. Entrances are spring() staggered 36 frames. Dividers are 1px borders, not shadows. </build> <gotchas> One line per change, written for users, not engineers: 'Audio no longer drifts on renders over 60 seconds' survives; 'Fixed AV sync regression in muxer' does not. If a change needs two lines, it is two changes or it belongs in the full notes. </gotchas> Before you finish: step through the timeline at five points and fix anything that overlaps, clips the frame, or drifts off the beat grid.