fls-changelog-verification

To verify changelog entries match spec changes, compare the diff range between specification modifications and changelog entries, map changed paragraph IDs to their closest anchors, and flag any missing references in the changelog file.

Changelog verification is the process of ensuring release notes accurately reflect specification changes by mapping updated paragraph IDs to changelog anchors and identifying missing references or syntax changes before a release.

Mapping changed paragraph IDs to anchors involves identifying the diff range between spec changes and changelog entries, then matching each changed ID to the closest :dp: anchor to verify correct attribution in the changelog.

Yes, changelog verification works with RST format files by checking that src/changelog.rst entries correctly reference updated specification changes and flagging any missing syntax changes or outdated sections.

Changelog entries miss references to updated spec sections when the diff range between spec changes and changelog entries is not properly mapped, leaving new sections or updated paragraph IDs unattributed in the changelog file.

The best way to generate a remediation checklist for missing changelog references is to enumerate added or removed paragraph IDs, flag missing references and syntax changes, and produce actionable guidance linking validation results to upstream PRs.