ci(web): commit visual baselines, enable visual regression - #15
Merged
Conversation
Baselines generated on ubuntu-latest via visual-baselines.yml (run 30716527348) against the healthy post-rollback production build (Godot 4.7.0), and every PNG inspected: legible text, correct HUD, distinct per-algorithm layouts, stair markers on the 3D case. Flag flipped in the same commit as the snapshots so they can never disagree, per docs/VISUAL_REGRESSION.md. 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.
Final step of the visual-guard work (#14): commits the five Linux-generated baseline PNGs and flips
MAZE_VISUAL_BASELINES: "1"in both visual jobs, in the same commit per docs/VISUAL_REGRESSION.md.Baselines were generated by the Generate Visual Baselines workflow (run 30716527348) on
ubuntu-latestagainst the healthy post-rollback production build, and each PNG was visually inspected before committing: legible text, correct HUD values, distinct per-algorithm layouts, stair markers on the 3D case, seed-stability identical to its sibling case.From the next deploy onward, every production and preview deploy is screenshot-compared against these — a boots-but-garbled build like the Godot 4.7.1 one now fails two independent gates (WebGL console assertion in the smoke test, and pixel diff here).
🤖 Generated with Claude Code