Repository navigation
docs: record verified beta and platform readiness - #16
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 V1 readiness checklist still marked the completed platform matrix and contract milestone as pending after PR #13 merged. Record the signed beta tag, the final integration result and the successful scheduled Composer compatibility run with their exact revisions.
Keep Packagist registration, RC/stable distribution and consumer adoption open. Distinguish fixture-backed integration coverage from skips in ordinary QA, and minimum/latest Composer coverage from an upgrade to a future minor.
Validation:
python3 tools/check-docs.pypasses for 83 Markdown files, 47 public options and 157 constants. This change only updates the evidence record.