Add live companion release verification - #2
Merged
Merged
Conversation
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
The Super Star transformation already passes lint, unit/integration tests, production static export, and GitHub Pages deployment. This closes the remaining release-QA gap by exercising the deployed site with the repository's existing Playwright verifier.
Changes
verify-release.mjswith living-companion E2E checks:Live Release Smokeverify-release.mjsagainst the public Pages URLThe existing verifier continues to cover all public routes, mobile overflow, search, quiz persistence, practice persistence, Goal → Today → Focus, backup export/import, and responsive protocol layouts.