document-release

To update documentation after a code release, you analyze shipped code diffs and apply those changes across README.md, ARCHITECTURE.md, CONTRIBUTING.md, and CLAUDE.md to ensure docs remain consistent with the latest release.

Keeping changelogs and READMEs synced with merged PRs is best handled by running a post-ship diff analysis that automatically updates documentation files and polishes the CHANGELOG voice to reflect the merged changes accurately.

Diff analysis for syncing project docs works by comparing shipped code changes against existing documentation, identifying discrepancies, and applying targeted updates across multiple files like CONTRIBUTING.md and CLAUDE.md to align with the new state.

Yes, you can automatically bump the VERSION file and clean up TODOS after shipping code. Post-ship documentation workflows handle version bumps when appropriate and remove completed TODOS alongside standard changelog polishing.

You do not need to manually update ARCHITECTURE.md and CLAUDE.md after a major release. Automated post-ship documentation tools proactively suggest and apply necessary updates to these files by analyzing the shipped code diff.

A limitation of automated documentation syncing is its reliance on accurate diff analysis; if shipped changes are highly ambiguous or lack clear user-facing impact, the automatic updates applied to README and changelog files may lack proper context.