The render harness: every screenplay's beats pinned as golden frames
deploy/verify-scenes.sh replays each screenplay to its authored beats under a paused Playwright clock — pulses, tweens, and fx advance only on the harness's schedule, so the same beat renders the same bytes every run — screenshots the reel, and diffs pixels against the goldens in deploy/scene-goldens (30 frames: warp transits, impacts, curses landing, in both views). A channel may drift 6 before a pixel counts, 0.2% of pixels before a beat fails; --update blesses intended changes. Proven both ways before landing: a clean double-run reproduces all 30 goldens exactly, and resurrecting the warp-smear cutaway bug fails the warp-transit beat at 61% pixel drift. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015RCWSTnb1KYTPyL4GmhGnF
This commit is contained in:
co-authored by
Claude Fable 5
parent
6c48174376
commit
58d1d34cb0
Executable
+8
@@ -0,0 +1,8 @@
|
||||
#!/bin/bash
|
||||
# Render-regression check: build the web client, then screenshot every
|
||||
# screenplay's pinned beats under a frozen clock and diff them against
|
||||
# deploy/scene-goldens/. Run from the repo root. Pass --update to bless
|
||||
# new goldens after an INTENDED renderer change (and commit them).
|
||||
set -euo pipefail
|
||||
(cd packages/web && npx vite build --logLevel error)
|
||||
npx tsx deploy/verify-scenes.mjs "$@"
|
||||
Reference in New Issue
Block a user