docs: clarify deployed release confirmation - #25
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.
Clarify that a website release is confirmed only after deployment health checks pass.
This harmless eligible documentation change validates the installed guarded pipeline from PR #23: native CI and read-only Codex review, scoped merge App token, native squash auto-merge, and push-triggered production deployment. No operator merge request or temporary installation helper will be used for this PR. GitHub requirements remain authoritative.
Validation:
git diff --check; the existing full CI and production audit run on this exact candidate. The preceding implementation passed 98 Node tests, 9 deployment tests, actionlint, ShellCheck, parsing checks, and live GitHub contract verification.