changelog.d/220.md — the 0.4.1 → 0.6.1 gap statement (#220) #221

Merged

andres merged 2 commits from build/220-gap-fragment into main

2026-08-06 16:53:17 +00:00

Author	SHA1	Message	Date
clad2	286403da78	docs(changelog): drop the entry that pre-decided #219 spec 6 All checks were successful CI / test (pull_request) Successful in 3m15s Details CI / release-exercise (pull_request) Successful in 11s Details CI / self-guards (pull_request) Successful in 6s Details CI / action-exercise (pull_request) Successful in 5s Details CI / docs-sync-exercise (pull_request) Successful in 6s Details labels / labels (pull_request) Successful in 7s Details Refs guard / refs-not-closing (pull_request) Successful in 6s Details 'By decision rather than omission' published a back-tagging ruling that belongs to the operator and has not been made. The fragment's authorized scope is the measured gap, which the first two entries state (@codex-reviewer-andresmgsl, !221 review). Refs #220	2026-08-05 23:15:24 +00:00
clad2	b7775c68ea	docs(changelog): the 0.4.1 -> 0.6.1 gap statement, as a grouped fragment All checks were successful CI / test (pull_request) Successful in 3m15s Details CI / release-exercise (pull_request) Successful in 11s Details CI / self-guards (pull_request) Successful in 6s Details CI / action-exercise (pull_request) Successful in 6s Details CI / docs-sync-exercise (pull_request) Successful in 6s Details Refs guard / refs-not-closing (pull_request) Successful in 6s Details labels / labels (pull_request) Successful in 7s Details Three Changed entries naming what a reader comparing the two forges' tags would otherwise reconstruct: 0.5.0/0.6.0 arrived by merge and were never released here; the carried ## 0.6.0 section is upstream's record; and the absent 0.6.0 tag is a decision, not an omission. Verified: eleven fragments assemble cleanly with these entries present, shape/cite guards green. Refs #220	2026-08-05 23:10:25 +00:00