document-release

Post-ship documentation synchronization reads code diffs, identifies mismatches, and updates core docs like README.md and ARCHITECTURE.md to accurately reflect the shipped state.

Keeping a CHANGELOG aligned involves performing a post-ship doc pass that polishes CHANGELOG voice, cleans up TODOS, and ensures notes describe the shipped state without losing intent or history.

Update README.md and ARCHITECTURE.md by scanning version control diffs after a ship and applying safe edits that preserve history while synchronizing the documentation with the latest code changes.

Yes, the documentation workflow suggests or prompts a VERSION bump when shipped changes warrant it, ensuring versioning stays aligned while preserving existing history and intent.

Yes, you can clean up TODOS alongside CHANGELOG updates during a post-ship pass, ensuring both files accurately describe the shipped state while maintaining safe edits across the project.

Run a post-ship documentation synchronization pass whenever code changes are shipped and you need to scan diffs to refresh docs, update CONTRIBUTING.md or CLAUDE.md, and interact with CI checks.