Repository navigation
Qualify production smoke releases and sync canonical runner - #316
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.
Production smoke now accepts only this project's successful Vercel production deployments and verifies that the deployed release belongs to main. Sync the canonical runner from dotagents 457d251, preserving the checkbox behavior scenario.
Validation: six independent review lenses passed with an unchanged checkout fingerprint; full committed npm run gate passed; pinned gitleaks range scan passed. The published tree exactly matches the locally gated tree. Post-merge verification follows Vercel READY and the matching automatic smoke receipt.