Repository navigation
feat(release): stamp and verify growth rollout version across all seven pages - #64
Merged
Merged
Conversation
…battle/index.html
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.
Adds a single source-visible rollout fingerprint
<meta name="sk-growth-release" content="growth-20261106-wave2">to homepage, /apps and all five priority app landing pages. The read-only HTTP smoke requires the same expected marker on all seven HTML pages: an old/cached/mixed deployment is no longer accidentally marked current. Two regression tests cover missing and stale fingerprint, 22 total. During local testing an existing catalog expansion fixture was found to assume JSON-LD was the first node in /apps; repaired it to preserve the release marker and read JSON-LD by explicit script tag.Evidence: all seven GitHub page headers stamped. Local Python unittest 22/22 PASSED, with exact file hashes matching PR blobs: checker d55acbe1435ba0aa9549da1a218952a9913c33af, tests fa71b51c97ac651ed12bdd46c787b6d77939587c. Caution: This marker identifies the growth rollout, not a Git commit SHA; actual production HTML still requires deployment, networked HTTP smoke and GA4 verification. No GitHub Actions used.