document-release

To keep release documentation in sync with shipped code changes, you audit post-merge diffs against README and changelog files, apply controlled auto-edits, and commit the synchronized updates via a pull request.

The best way to update a changelog after a code release is to analyze the latest diff, map factual changes to release notes, polish the changelog voice, and append entries that reflect what actually shipped.

Diataxis coverage mapping identifies missing documentation by categorizing existing repo files into tutorial, how-to, reference, and explanation quadrants, then highlighting gaps where the shipped diff lacks corresponding narrative updates.

Yes, you can automatically update README and architecture docs after a merge, but approval gates are required for risky narrative rewrites or version changes to prevent unauthorized factual drift in the repository.

Post-ship documentation drifts away from the actual codebase because manual updates are often skipped during fast releases, leaving stale setup steps and misleading architecture notes that fail to reflect recent diffs.

You should use an approval gate for repository documentation updates when the diff analysis detects risky narrative rewrites, structural version changes, or modifications to core architecture files that require human review.