document-release

To update project documentation after shipping, you can use a post-ship docs sync workflow that reads code diffs and updates core docs like README.md and ARCHITECTURE.md to reflect the actual released changes, reducing drift between code and documentation.

Keeping README and ARCHITECTURE docs in sync with merged PRs is best handled by applying diff data to the doc structure after code ships, safely updating core files to accurately reflect the latest shipped changes.

Yes, you can automatically update CHANGELOG entries and clean up TODOS by reading diff data from shipped changes. The process polishes CHANGELOG wording without overwriting existing entries and organizes TODOs based on the diff output.

You need to bump the VERSION file during a documentation sync when a shipped code change warrants a version increment. The post-ship docs sync process can optionally bump the VERSION when appropriate based on the diff data.

Yes, this docs sync workflow works with CONTRIBUTING.md and CLAUDE.md files. It reads diff data from shipped changes and applies updates across these core docs to ensure the entire project documentation stays aligned with the code.