Repository navigation
Keep two release-relative instructions true after the next release - #279
Merged
Merged
Conversation
adoption/README.md and docs/token-efficiency-stack.md said to run the token-efficiency coverage check "from a default-branch clone until the next release". Once v2026.09.25.2 is cut that release has the check, so the instruction would go stale. Say "from a later release or a default-branch clone", which is true before and after the tag. The historical "changed after v2026.09.25.1" markers stay. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
seathatflowsinourveins
added
the
lane:foundation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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.
Scope
adoption/README.mdline 74 anddocs/token-efficiency-stack.mdlines 139-141 told readers to run the token-efficiency coverage check "from a default-branch clone until the next release". They now say "from a later release or a default-branch clone". Both files are re-registered inmanifests/evidence.json.v2026.09.25.2is about to be cut from main and will contain--client-wiringand thetoken-efficiencyprofile, so "until the next release" would go stale. Changing a new-machine doc after the tag would make the re-pin failrelease_due --strict-if-repinned, so this lands first, inside the release window. The historical "changed afterv2026.09.25.1" markers are still true and stay.Checks
tests/test_adoption_docs_consistency.py,tests/test_adoption_contract.pyandtests/test_release_pin_contents.py: 63 passed, 1 skipped.scripts/validate.py: passed.🤖 Generated with Claude Code