docs(release): document refactor fragment dedup policy #986

Merged
pullings merged 1 commit from i/492-refactor-bullet-policy into main 2026-08-27 00:29:58 +02:00
Owner

Option (d) from rt#492: document the bounded policy rather than add a heuristic parser. The current Go rt prep path omits fragment-less conventional-commit subjects from the composed CHANGELOG, so the duplicate refactor-of-X class is avoided there. The documentation records the legacy/consumer edge, keeps an existing fragment as the sole note source, and documents Refactors: #NNN as a human/audit convention. The trailer is explicitly not parsed by the current toolkit.

Verification:

  • focused composer tests: PASS
  • full internal/prep tests: PASS
  • fragment-check changelog.d: all fragments valid, density PASS
  • git diff --check: PASS
Option (d) from rt#492: document the bounded policy rather than add a heuristic parser. The current Go `rt prep` path omits fragment-less conventional-commit subjects from the composed CHANGELOG, so the duplicate refactor-of-X class is avoided there. The documentation records the legacy/consumer edge, keeps an existing fragment as the sole note source, and documents `Refactors: #NNN` as a human/audit convention. The trailer is explicitly not parsed by the current toolkit. Verification: - focused composer tests: PASS - full internal/prep tests: PASS - fragment-check changelog.d: all fragments valid, density PASS - git diff --check: PASS
docs(release): document refactor fragment dedup policy
All checks were successful
manifest-check / manifest-vs-tag consistency (pull_request) Successful in 8s
manifest-check / check (pull_request) Successful in 0s
register-check / toolkit-self gate (PR's own rt) (pull_request) Successful in 4s
register-check / register-drift check (pull_request) Successful in 8s
register-check / check (pull_request) Successful in 0s
tests / workflow-schema (pull_request) Successful in 3s
tests / bats (pull_request) Successful in 11s
check-self-bootstrap / check (pull_request) Successful in 52s
tests / dated-examples (pull_request) Successful in 4s
tests / shellcheck (pull_request) Successful in 3s
fragment-check / toolkit-self gate (PR's own rt) (pull_request) Successful in 1m7s
changelog-body-check / toolkit-self gate (PR's own rt) (pull_request) Successful in 1m24s
manifest-check / toolkit-self gate (PR's own rt) (pull_request) Successful in 2m8s
go-ci / lint + build + test (pull_request) Successful in 2m53s
fragment-check / changelog fragment-kind (pull_request) Successful in 3m51s
fragment-check / check (pull_request) Successful in 0s
changelog-body-check / changelog body Cold-Read linter (pull_request) Successful in 4m7s
changelog-body-check / check (pull_request) Successful in 0s
ac-closure-check / toolkit-self gate (PR's own rt) (pull_request) Successful in 29s
ac-closure-check / ac-closure check (pull_request) Successful in 1m46s
ac-closure-check / check (pull_request) Successful in 0s
fb6548b064
lookout approved these changes 2026-08-27 00:13:42 +02:00
lookout left a comment

APPROVED — exact head fb6548b064.

Reviewed the complete two-file diff. It implements rt#492 option (d): exact filename-reference deduplication cannot infer a semantic refactor-of-X relationship when the numbers differ; the current Go rt prep path omits fragment-less conventional-commit subjects from composed notes while retaining their bump signal; and Refactors: #NNN is documented as an audit convention explicitly not parsed by release-toolkit. Legacy release-prep consumers and historical cuts are clearly separated from the current Go behavior, and the historical relationship is retained without promising an unimplemented suppression mechanism.

Independent verification on this head: go test -count=1 ./...; go vet ./...; Bats 99/99; fragment-check PASS; register-check 0; dated-examples-check PASS; git diff --check PASS; all 21 latest status contexts success. Added lines and commit messages contain no positional unqualified close-keyword Closes/Fixes/Resolves #N literals.

APPROVED — exact head fb6548b064d025e79f1a222fbd4e6246e0bda609. Reviewed the complete two-file diff. It implements rt#492 option (d): exact filename-reference deduplication cannot infer a semantic refactor-of-X relationship when the numbers differ; the current Go rt prep path omits fragment-less conventional-commit subjects from composed notes while retaining their bump signal; and `Refactors: #NNN` is documented as an audit convention explicitly not parsed by release-toolkit. Legacy release-prep consumers and historical cuts are clearly separated from the current Go behavior, and the historical relationship is retained without promising an unimplemented suppression mechanism. Independent verification on this head: go test -count=1 ./...; go vet ./...; Bats 99/99; fragment-check PASS; register-check 0; dated-examples-check PASS; git diff --check PASS; all 21 latest status contexts success. Added lines and commit messages contain no positional unqualified close-keyword `Closes/Fixes/Resolves #N` literals.
lookout approved these changes 2026-08-27 00:14:38 +02:00
pullings deleted branch i/492-refactor-bullet-policy 2026-08-27 00:29:58 +02:00
Sign in to join this conversation.
No description provided.