document-release

To update README and CLAUDE.md after a PR is merged, you can use a post-ship documentation sync tool that cross-references the shipped diff and modifies repository files to reflect the new changes.

Keeping project documentation in sync with shipped code changes involves cross-referencing diffs to automatically update README, ARCHITECTURE, and CONTRIBUTING files so the docs accurately reflect what was actually deployed.

Polishing a CHANGELOG and cleaning up TODOs before a version bump requires normalizing the release narrative tone and clearing completed items, which can be automated using bash and file editing tooling.

Yes, you can automatically bump the VERSION file and update architecture docs simultaneously by invoking a deterministic documentation refresh that reads shipped changes and modifies the repository files in one pass.

You need to sync documentation after shipping code whenever a merged PR introduces changes that alter the project's behavior, ensuring the README, ARCHITECTURE, and CLAUDE.md files do not become stale.

Yes, post-ship documentation sync works without external dependencies by using built-in bash and file read/write/edit tooling to directly modify repository files like CLAUDE.md and CONTRIBUTING docs.