document-release

To synchronize project documentation after a PR merge, you need to update key docs to reflect the shipped changes. This ensures files like README, ARCHITECTURE, CONTRIBUTING, and CLAUDE.md stay consistent and accurately describe the new codebase state.

Keeping README and ARCHITECTURE docs consistent across versions requires enforcing cross-document consistency after every ship. By reconciling file diffs and polishing documentation voice, you prevent post-ship updates from becoming error-prone and drifting out of sync.

You can bump VERSION and update the CHANGELOG after a release by triggering a post-ship documentation synchronization. This process cleans up TODOS, polishes the changelog voice, and optionally applies an automatic version bump when configured.

Documentation updates cannot be triggered automatically when code is shipped. Post-ship synchronization supports only manual triggering via the /document-release command, ensuring you have explicit control over when README and ARCHITECTURE files are aligned.

Post-ship documentation drifts out of sync because reconciling diffs across multiple files is error-prone when done manually. Without enforcing cross-document consistency after a ship, README, CONTRIBUTING, and CLAUDE.md files fail to reflect the exact merged changes.

You do not need any external dependencies to enforce cross-document consistency for your docs. The synchronization and polishing process for README, ARCHITECTURE, and CLAUDE.md works without requiring additional components or libraries.