Remove the frozen release history - #53
Merged
Merged
Conversation
The frozen release history covered releases through 0.4.0 and said it no longer described current state. Its current facts already live in RELEASING.md, SECURITY.md and AGENTS.md, the tags and git log keep the rest, and the npm package never shipped it. The last copy is e98b427:docs/release-history.md. The second "Retrieval quality" paragraph in docs/README.md narrated the documentation tests' caps and checks to npm readers. The tests' failure messages say the same when a rule breaks, so the paragraph only added a copy to keep in step with them. CONTRIBUTING.md restated cross-review's own install instructions. Keep the two facts its README lacks, that the tracked settings enable the plugins in a trusted checkout and that linked worktrees inherit that trust, and send readers to the README for the rest. The shared review procedure is unchanged. AGENTS.md now points at CONTRIBUTING.md for the focus-file fetch instead of restating it.
firstdraft deleted docs/owner-shape-exceptions.json once every page fit its size limits, so the shared Maintenance bullet named a file that no longer exists. It now names the one exceptions list left, currencyBaseline in firstdraft/skills. firstdraft, skills and cli carry the same line, as the shared section requires.
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.
Why
docs/release-history.mdwas frozen when CHANGELOG.md started, but agents still found and read it. Parts of the docs map and CONTRIBUTING repeated review and install text that the shared rules already state.What changed
docs/release-history.mdis removed. CHANGELOG, README and the documentation-test exemption now point at CHANGELOG and the git history.docs/README.mdis deleted.currencyBaselineas its example exceptions list, matching firstdraft and skills.Docs: updated CONTRIBUTING, CHANGELOG, README and docs/README; removed docs/release-history.md.
Validation
npm run check: passnpm audit: cleanReview
Review: codex-review 0.7.3, high effort, session
8a51993f-ae4f-4c16-aa6d-23bdcbb1a876, approve.