Align release note policy with independent modules

This commit is contained in:
2026-10-11 13:07:45 +00:00
parent 7ce2fc0bf2
commit 4ba5a56e21
2 changed files with 25 additions and 7 deletions

View File

@@ -180,7 +180,15 @@ names. This is documentation work, not a request for additional runtime rules.
## R4: Complete the module-specific release-note policy adaptation
**Status:** Open. **Priority:** P2.
**Status:** Completed (2026-10-11). **Priority:** P2.
**Completed work:** release policy now places notes relative to the selected
module and distinguishes semantic-version filenames/titles from full Git tags
and immutable source URLs. Checked all three prepared notes against their profile
products, versions, full-tag footers, and existing module-local destinations;
they agree with the runbook and ReleaseKit v0.4.0's public module-release ADR.
The added local link/fragment and whitespace checks pass. Independent versioning,
immutability, and source-push completion rules remain intact; no tags were created.
**Evidence:** [release policy](../policy/release.md#release-documentation-and-preparation)
still requires `docs/releases/<version>.md` in the tagged source tree and says