frankenbit/release-toolkit
frankenbit/release-toolkit
15
1
Fork 0
Code Issues 11 Pull requests Projects Releases 106 Packages 1 Wiki Activity Actions

docs(changelog): document #420 + #423 under [v0.27.0] for manual recovery #426

Closed
quartermaster wants to merge 1 commit from i/v0270-recovery-changelog-entries into main
pull from: i/v0270-recovery-changelog-entries
merge into: frankenbit:main
Conversation 0 Commits 1 Files changed 1 +4
quartermaster commented 2026-07-06 09:52:47 +02:00
Owner
Copy link

Summary

Operator manual recovery for v0.27.0 per Option D ratify (Bosun dispatch 59b0, Surveyor substrate ratify ba6b). Adds two entries to the existing [v0.27.0] CHANGELOG section documenting #420 (paragraph normalization) + #423 (orphan-check range-walk fix) shipping in the v0.27.0 tag.

Substrate framing

Cut-preparation, NOT retroactive rewrite. v0.27.0 has not been tagged yet (the recovery is exactly what this PR prepares for), so [v0.27.0] remains cut-scope-adjustable per #392's frozen-record policy (Surveyor ba6b ratified operator's substrate framing).

Entries added

  • ### Added — #420 paragraph normalization: adopter-outcome-first framing. Fragments authored with hard-wraps compile to render-clean output; structural elements pass through; hyphen-word rejoin heuristic; post-scan guard on residual [a-zA-Z]- [a-zA-Z] outside fenced code. v1.0.0 must-fix.
  • ### Fixed — #423 orphan-CHANGELOG range-walk: adopter-facing explanation of the false-positive class. Signature-only vs action-context; range-walk vs HEAD-only; handles both rebase-merge and squash-merge prep styles. Framed as #417 belt-and-suspenders refinement, surfaced during release-toolkit's own v0.27.0 self-hosting cut. v1.0.0 must-fix.

Non-bump-worthy subject

Commit subject uses docs(changelog): (non-bump-worthy per conventional-commits.sh's bump-producing set) so a subsequent legit cut's range-walk won't false-fire the orphan detector on this commit itself.

Post-merge sequence for operator

  1. git tag v0.27.0 <this PR's merge SHA>
  2. git push origin v0.27.0
  3. Create Forgejo release for v0.27.0 (Publish, or draft-then-publish per default)
  4. Edit .release-toolkit-manifest.json: last_released_version=0.27.0, last_released_tag=v0.27.0, last_released_sha=<this PR's merge SHA>; commit as chore(manifest): advance to v0.27.0 (paths-ignore skips workflow trigger)

Once manifest is at 0.27.0, subsequent rolling PRs work cleanly (CHANGELOG_TOP == manifest → orphan quiet). Any further #420/#423-shipped fragments would already be on main and would fold into the next natural cut.

Refs #420, #423, #417 (parent), PR#406 (v0.27.0 cut anchor), Bosun 59b0 (Option D ratify), Surveyor ba6b (substrate ratify).

## Summary **Operator manual recovery for v0.27.0** per Option D ratify (Bosun dispatch 59b0, Surveyor substrate ratify ba6b). Adds two entries to the existing `[v0.27.0]` CHANGELOG section documenting #420 (paragraph normalization) + #423 (orphan-check range-walk fix) shipping in the v0.27.0 tag. ## Substrate framing Cut-preparation, NOT retroactive rewrite. v0.27.0 has not been tagged yet (the recovery is exactly what this PR prepares for), so `[v0.27.0]` remains cut-scope-adjustable per #392's frozen-record policy (Surveyor ba6b ratified operator's substrate framing). ## Entries added - **### Added — #420 paragraph normalization**: adopter-outcome-first framing. Fragments authored with hard-wraps compile to render-clean output; structural elements pass through; hyphen-word rejoin heuristic; post-scan guard on residual `[a-zA-Z]- [a-zA-Z]` outside fenced code. v1.0.0 must-fix. - **### Fixed — #423 orphan-CHANGELOG range-walk**: adopter-facing explanation of the false-positive class. Signature-only vs action-context; range-walk vs HEAD-only; handles both rebase-merge and squash-merge prep styles. Framed as #417 belt-and-suspenders refinement, surfaced during release-toolkit's own v0.27.0 self-hosting cut. v1.0.0 must-fix. ## Non-bump-worthy subject Commit subject uses `docs(changelog):` (non-bump-worthy per conventional-commits.sh's bump-producing set) so a subsequent legit cut's range-walk won't false-fire the orphan detector on this commit itself. ## Post-merge sequence for operator 1. `git tag v0.27.0 <this PR's merge SHA>` 2. `git push origin v0.27.0` 3. Create Forgejo release for v0.27.0 (Publish, or draft-then-publish per default) 4. Edit `.release-toolkit-manifest.json`: `last_released_version=0.27.0`, `last_released_tag=v0.27.0`, `last_released_sha=<this PR's merge SHA>`; commit as `chore(manifest): advance to v0.27.0` (paths-ignore skips workflow trigger) Once manifest is at 0.27.0, subsequent rolling PRs work cleanly (CHANGELOG_TOP == manifest → orphan quiet). Any further #420/#423-shipped fragments would already be on main and would fold into the next natural cut. Refs #420, #423, #417 (parent), PR#406 (v0.27.0 cut anchor), Bosun 59b0 (Option D ratify), Surveyor ba6b (substrate ratify).
docs(changelog): document #420 + #423 under [v0.27.0] for manual recovery
Some checks failed
changelog-body-check / changelog body Cold-Read linter (pull_request) Successful in 4s
Details
changelog-body-check / check (pull_request) Successful in 0s
Details
check-self-bootstrap / check (pull_request) Failing after 3s
Details
manifest-check / manifest-vs-tag consistency (pull_request) Successful in 5s
Details
manifest-check / check (pull_request) Successful in 0s
Details
register-check / register-drift check (pull_request) Successful in 4s
Details
register-check / check (pull_request) Successful in 0s
Details
tests / bats (pull_request) Successful in 1m49s
Details
tests / shellcheck (pull_request) Successful in 8s
Details
711449d3ef 
Adds two entries to the existing v0.27.0 CHANGELOG section to
document the fixes shipping in the v0.27.0 tag (per operator's Option
D ratify, dispatch 59b0). Cut-preparation, not retroactive rewrite:
v0.27.0 has not been tagged yet (the recovery is exactly what this
commit prepares for), so the section is still cut-scope-adjustable
per the frozen-record policy (Surveyor ba6b ratified operator's
substrate framing).

**### Added — CHANGELOG fragment paragraph normalization (#420)**:
adopter-facing outcome-first framing (fragments authored with hard
wraps compile to render-clean output; structural elements pass
through; hyphen-word rejoin; post-scan guard). v1.0.0 must-fix.

**### Fixed — orphan-CHANGELOG range-walk (#423)**:
adopter-facing explanation of the false-positive class the fixup
closes (signature-only vs action-context, range-walk vs HEAD-only,
handles both rebase/squash prep styles). Frames as a #417
belt-and-suspenders refinement, surfaced during release-toolkit's
own v0.27.0 self-hosting cut. v1.0.0 must-fix.

Post-commit sequence (operator):
1. git tag v0.27.0 <THIS commit's SHA>
2. git push origin v0.27.0
3. Create Forgejo release for v0.27.0
4. Edit .release-toolkit-manifest.json: version=0.27.0, tag=v0.27.0,
   sha=<THIS commit's SHA>; commit as chore(manifest): advance to
   v0.27.0 (paths-ignore skips workflow trigger).

Non-bump-worthy subject (docs:) so any subsequent legit cut's range-
walk doesn't false-fire the orphan detector on this commit.

Refs #420 (paragraph normalization), #423 (range-walk fix), #417
(parent detector), PR#406 (v0.27.0 cut anchor), Bosun 59b0 (Option D
ratify), Surveyor ba6b (substrate ratify).
quartermaster closed this pull request 2026-07-06 09:53:02 +02:00
Some checks are pending
changelog-body-check / changelog body Cold-Read linter (pull_request) Successful in 4s
Required
Details
changelog-body-check / check (pull_request) Successful in 0s
Required
Details
check-self-bootstrap / check (pull_request) Failing after 3s
Required
Details
manifest-check / manifest-vs-tag consistency (pull_request) Successful in 5s
Required
Details
manifest-check / check (pull_request) Successful in 0s
Required
Details
register-check / register-drift check (pull_request) Successful in 4s
Required
Details
register-check / check (pull_request) Successful in 0s
Required
Details
tests / bats (pull_request) Successful in 1m49s
Required
Details
tests / shellcheck (pull_request) Successful in 8s
Required
Details
ac-closure-check / ac-closure check (pull_request)
Required
ac-closure-check / check (pull_request)
Required
fragment-check / check (pull_request)
Required
fragment-check / coverage (pull_request)
Required
fragment-check / density (pull_request)
Required
gitea-twin-check / check (pull_request)
Required
go-ci / lint + build + test (pull_request)
Required
prep-order-check / check (pull_request)
Required
readme-pin-check / digest (pull_request)
Required
tests / contract-paths (pull_request)
Required
tests / dated-examples (pull_request)
Required
tests / workflow-schema (pull_request)
Required
toolkit-self-gates / toolkit-self gates (PR's own rt) (pull_request)
Required
workflow-parse-check / check (pull_request)
Required
workflow-parse-check / toolkit-self parse guard and controls (pull_request)
Required
workflow-parse-check / workflow parse and schema (pull_request)
Required

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
bump
major
 Override the cut bump to MAJOR (release-toolkit#107)

  
bump
minor
 Override the cut bump to MINOR (release-toolkit#107)

  
bump
patch
 Override the cut bump to PATCH (release-toolkit#107)

  
kind/bug
Something is broken

  
kind/chore
Maintenance, tooling, refactor

  
kind/docs
Documentation work

  
kind/feature
New feature or capability

  
priority/critical
Critical: must be addressed immediately

  
priority/high
Important, should be addressed soon

  
priority/low
Low priority, address when convenient

  
priority/medium
Normal priority

  
size/L
Large: significant feature, ~6-16h

  
size/M
Medium: moderate feature, ~2-6h

  
size/S
Small: simple change, ~1-2h

  
size/XL
Extra large: major feature or refactor, 16h+

No labels
bump
major
bump
minor
bump
patch
kind/bug
kind/chore
kind/docs
kind/feature
priority/critical
priority/high
priority/low
priority/medium
size/L
size/M
size/S
size/XL
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
frankenbit/release-toolkit!426
No description provided.