document-release

To sync documentation with shipped code, run the document-release process after a merge. It cross-references project diffs against existing docs, updates README and ARCHITECTURE files, and polishes the CHANGELOG to reflect the actual release.

Updating a CHANGELOG and CLAUDE.md after shipping is best handled by a post-ship diff detection process. It reads project docs, cross-references shipped changes, polishes changelog wording, and aligns CLAUDE.md to prevent documentation drift.

You should run post-ship documentation hygiene immediately after a release or PR merge. This ensures your README, CONTRIBUTING, and ARCHITECTURE docs are updated to match the shipped product before development continues.

Yes, post-ship documentation synchronization works without external dependencies. It reads project files directly, identifies drift between shipped code and documentation, and updates core docs like CLAUDE.md and README automatically.

Yes, you can automatically bump the VERSION while syncing project docs. The post-ship documentation process includes an optional version bump alongside cleaning TODOS and updating essential files to mirror shipped changes.

Your README drifts from the shipped product because post-merge documentation updates are often skipped. A diff-detection process cross-references shipped changes against project docs to automatically update README, ARCHITECTURE, and CONTRIBUTING files.