document-release

Release-readiness audits enforce quality on changelogs and handoff documentation by running pre-flight diffs and per-file checks before merge. This process validates branch alignment and generates structured release-readiness artifacts.

A release-readiness artifact is a structured document generated to validate completed implementations and ensure documentation aligns with project standards. You need one when preparing for a branch merge to guarantee release notes and handoff docs pass quality checks.

You can generate aligned handoff documentation by running an automated release-readiness workflow that detects the local base branch, checks protected-branch rules, and audits per-file changes. This ensures your docs match current branch and project standards.

Yes, the release-readiness workflow applies per-file audits across repository docs including README and ARCHITECTURE files. It validates these documents during the pre-flight diff stage before producing the final release-readiness artifact.

Automating changelog validation for protected branches requires a release-readiness process that derives the local base branch, checks protected-branch rules, and audits release notes. This ensures compliance before any merge operation is attempted.

The release-readiness audit enables project-memory updates when appropriate after completing the documentation validation. It generates the release-readiness artifact first, then optionally updates project memory to reflect the validated release state.