ci: add check + Remotion smoke-render workflow - #7
Merged
Conversation
A reproducible-walkthrough tool with zero CI undercuts its own thesis. This workflow proves two things on every push/PR: the syntax gate (npm run check) passes, and the render pipeline reproduces a video from the committed walkthrough data alone (frames 0-30 of WT-NodeRoom, whose frames live in public/wt/NodeRoom). The Playwright capture step is deliberately excluded: it needs live localhost apps. Verified locally: check passes, WT-NodeRoom frames 0-30 renders 311 kB. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
HomenShum
added a commit
that referenced
this pull request
Jul 29, 2026
…ists WT-SoloFounder is in no committed walkthrough data file, so the documented example command failed on a fresh clone — a stale pointer surviving a re-cut, the same defect class the CI added in #7 exists to catch. Now targets WT-NodeRoom, which is exactly what that CI smoke-renders from committed inputs, so this script can no longer silently drift again without CI going red. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
Why
A reproducible-walkthrough tool with zero CI undercuts its own thesis. This adds a minimal workflow that actually exercises the pipeline, not a lint-only checkbox.
What CI covers
npm ci+npm run check(the repo's own syntax gate forwalkthrough.mjsandjudge-video.mjs)WT-NodeRoomfromsrc/index.js, using only committed inputs (src/walkthrough.data.js+public/wt/NodeRoom/). This proves the Remotion render pipeline reproduces from bundled walkthrough data on a clean machine — the core reproducibility claim.What CI deliberately excludes
node walkthrough.mjs): it drives live localhost apps (NodeRoom/NodeSlide dev servers) that do not exist in CI. Capture stays a local step by design; CI proves the render half reproduces from what capture commits.Verification
npm run checkpasses;WT-NodeRoom --frames=0-30renders a 311 kB MP4.pull_request.Side observation (not changed here):
render:examplein package.json targetsWT-SoloFounder, which no longer exists in any committed data file — the script is stale.🤖 Generated with Claude Code