Repository navigation
Preserve historical screenshot outside current release evidence - #31
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
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.
The Pages QA upload includes all JPEGs under docs/screenshots. A tracked image retained from PR #28 therefore becomes an unexpected eighth image, correctly failing the exact seven-capture postdeployment gate.
Move that historical screenshot byte-for-byte to docs/verification-evidence/aps-continuity and record its source path/commit/hash. Git reports a 100% rename. No app, workflow, verifier, pin, or acceptance check changes; the failed archive remains retained. The next actual deployment must produce the exact expected evidence archive before acceptance.