Repository navigation
Conversation
Moves the motion-reel tooling out of gitignored scratch into scripts/newsletter/reels/: setup.mjs lays out tmp/issue-<N>/reels/ with the shared vendor files, three.js, a venv and links to the z-motion-reel audio library (never committed); render.mjs renders a reel frame by frame to stills or an mp4 with its audio muxed in; gallery.html compares named reel folders side by side.
A Choice line pointing at an .mp4, .mov or .webm crashed --apply, because every chosen file went through sharp. Videos are now copied untouched as image<ext>, which buffer-post.mjs already treats as video.
Shared reel contract, post and issue briefs, style menu and sound brief, each written to be copied into a worker brief as it stands.
New step 9 proposes reels, runs one durable headless worker per reel, reviews them live in the gallery, adds sound for the picks and renders the mp4 for Buffer. Later steps renumbered.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The newsletter-issue skill can now propose and build motion reels for an issue: one 16:9 main video for the whole issue and optional 4:5 reels for each article post. The tooling that made the issue 408 reels only existed in gitignored scratch under
tmp/reels/, so this moves what is needed into the repo and writes the workflow down as a new optional step 9.The scripts live in
scripts/newsletter/reels/.setup.mjs --issue Nlays outtmp/issue-N/reels/with the shared vendor files every reel references, three.js r170 downloaded once, a uv venv for the sound scripts, the review gallery, and links to the procedural audio library of the z-motion-reel skill. That library is found through--audio-lib, thenREEL_AUDIO_LIB, then the newest installed skill, the same pattern capture-gifs uses for the site-capture engine, so nothing personal is committed.render.mjsis the scratch renderer with the hardcoded npx path replaced byloadChromiumand the scratch-only mp4 guard dropped. The worker briefs are inreferences/reels.md, one section each so they can be pasted into a brief: shared contract, post brief, issue brief, style menu, sound brief.Also in here, at the coordinator's request:
fetch-images.mjs --applycrashed when aChoice:line pointed at an mp4, because every chosen file went through sharp:Videos (.mp4, .mov, .webm) now skip sharp and are copied as
image<ext>, which buffer-post already treats as video. Reel mp4s are now a normal post choice, so step 9 relies on this.Verified today (2026-10-11): ran setup for a throwaway issue 999 twice (idempotent), copied the picked 408 Hugging Face reel in, rendered stills at 0 and 5s and looked at them, then a full render that ffprobe reports as 1080x1350, 10.0s, with an audio stream. A headless Playwright check of
gallery.html?reels=408s-3afound the iframe and the Sound A/B/C buttons.--applyagainst a real issue 408 posts.md with an mp4 choice wroteimage.mp4. Lint,check:ratchetandcheckpass.Weaknesses: the installed z-motion-reel skill keeps
score.pyundertemplate/, so setup links individual files rather than the directory, and a future layout change in that skill would make setup fail (loudly, which seemed better than guessing). The briefs record no visual style recommendations from the 408 reels, since the owner rated those styles poor, so the style menu is a list of directions and nothing more. I haven't run a fresh end-to-end issue through step 9 with real workers; the cost figure in it ($109 for twelve workers over three rounds) is from the 408 run.