document-release

To update project documentation after shipping, you can scan code diffs and apply matching changes to README.md, ARCHITECTURE.md, CONTRIBUTING.md, and AGENTS.md. This process syncs docs with the shipped state and polishes the CHANGELOG voice.

Post-ship documentation drift happens when shipped code changes are not reflected in project docs. You fix it by cross-referencing the code diff to update README.md and ARCHITECTURE.md, cleaning up TODOS, and polishing CHANGELOG language to maintain consistency.

You sync README and ARCHITECTURE files by parsing the recent diff and modifying the Markdown files to match what shipped. This minimizes churn by guiding updates strictly through the detected code changes.

Yes, you can automatically bump your project VERSION and polish the CHANGELOG at the same time. The process updates documentation across the project and optionally bumps the VERSION after a release alongside CHANGELOG language improvements.

Yes, you need read and write access to the repository to sync docs after a code ship. The process requires parsing and modifying Markdown files directly within the repository to apply the diff-guided updates.