document-release

Automating documentation updates after a PR involves scanning code diffs to sync README, ARCHITECTURE, and CLAUDE.md files with shipped changes, while polishing the CHANGELOG and tidying TODOS.

Syncing core docs with shipped code changes requires orchestrating a Bash-based workflow that validates frontmatter, reads file diffs, and edits documentation to match the newly deployed state.

Diff scanning for documentation versioning works by reviewing code changes and automatically applying those updates to core docs, optionally bumping the VERSION file and enforcing safety through allowed-tools validation.

Yes, you can use Bash commands to orchestrate automatic updates to README and CHANGELOG files by invoking workflow tools like Read, Write, Edit, Grep, and Glob to align documentation with shipped changes.

Yes, automated documentation workflows enforce safety by requiring specific allowed-tools to execute, validating frontmatter and ensuring auditable updates when syncing docs after a PR.

Post-ship documentation drifts from the deployed state because manual updates are often skipped after merging code, making automated diff scanning and doc synchronization necessary to reflect reality.