Problem
The unreleased #68 entry in CHANGELOG.md still says the define-disclosure fallback survives because the client’s API-version floor is 2:
which this client still supports because its API-version floor is 2
That premise was corrected by #79 before release. The floor is now 7, and ADR-0037 records that behaviour-level compatibility is governed by the Extractor’s honours list/member presence, not by api_version. The same changelog currently states the corrected model immediately above the stale sentence.
The consistency suite deliberately excludes CHANGELOG.md because released entries are dated records. This entry is still under [Unreleased], so preserving a statement already known to be false would publish avoidable misinformation.
Desired behaviour
Before the next release, rewrite only the stale justification in #68’s entry to name disclosure member presence / the disclosure honours capability. Preserve the historical description of #68’s actual change and do not alter released entries.
Problem
The unreleased #68 entry in
CHANGELOG.mdstill says the define-disclosure fallback survives because the client’s API-version floor is 2:That premise was corrected by #79 before release. The floor is now 7, and ADR-0037 records that behaviour-level compatibility is governed by the Extractor’s
honourslist/member presence, not byapi_version. The same changelog currently states the corrected model immediately above the stale sentence.The consistency suite deliberately excludes
CHANGELOG.mdbecause released entries are dated records. This entry is still under[Unreleased], so preserving a statement already known to be false would publish avoidable misinformation.Desired behaviour
Before the next release, rewrite only the stale justification in #68’s entry to name disclosure member presence / the
disclosurehonours capability. Preserve the historical description of #68’s actual change and do not alter released entries.