Align current-boundary docs with v0.2.2#25
Merged
senseibelbi merged 1 commit intomainfrom Apr 12, 2026
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.
Summary
Align the remaining current-boundary docs with the active
v0.2.2public release.This PR:
v0.2.0v0.2.1stabilization plan intact as historical release contextWhy
The public release surface is already
v0.2.2, but several internal guides still described the current public boundary asv0.2.0. That wording was stale and easy to misread as the live contract.Validation
pytest -q tests/test_release_metadata.py->10 passedpytest -q->167 passedbash scripts/build_docs.shblack --check tests/test_release_metadata.py