frankenbit/release-toolkit

Set F — Cut-path bug drain

New issue

The 11 high-priority bugs open at 2026-08-17, ten of which sit on the release/cut path — the machinery a release toolkit IS. None was in any milestone before this, so none could block a cut or be finished. Drains before the v1.0.0 stability commitment (Phase 10), because that commitment is a state-assertion this substrate must actually back. Named 'Set' per the Set D / Set E drain convention rather than 'Phase', since these are defects surfaced across phases rather than a migration stage.

No due date

100% Completed

bug(changelog): Seal inserts a duplicate version heading on every re-prepare — empty sections accumulate per failed cut

#691 by bosun was closed 2026-08-19 10:08:47 +02:00 4 / 4

bug(cut-safeguard): Layer 2 keys on merge_commit_sha, so under fast-forward-only it CANNOT see a buried prepare — Layer 1 supports the case Layer 2 refuses

#690 by shipwright was closed 2026-08-20 09:45:25 +02:00 9 / 9

release(decide): a dry-run skips all three forge-consulting checks and reports mode=cut as if it had passed them

priority/critical

#689 by bosun was closed 2026-08-18 23:20:37 +02:00 6 / 6

ci(release): the cut-safeguard cannot run pre-merge — it triggers on push:main only, so it can only refuse after the merge is irreversible

#688 by bosun was closed 2026-08-19 07:42:44 +02:00 6 / 6

feat(changelog): MERGE into an existing version section instead of refusing the cut

#665 by bosun was closed 2026-08-23 18:02:31 +02:00 5 / 5

path-gamma consumer never received a manifest PR — benign by fallback, silent by design?

#661 by engineer was closed 2026-08-19 09:46:40 +02:00

bug(release-decide): a FAILED cut leaves the version stamped-but-uncut, and the next run stamps it AGAIN — duplicate ## [X.Y.Z] silently drops entries

#659 by surveyor was closed 2026-08-19 10:08:47 +02:00 5 / 5

bug(changelog-body-check): check 3 cannot tell a DEPENDENCY pin from a forward reference — blocks any consumer whose deps outrank it

#658 by bosun was closed 2026-08-19 07:39:56 +02:00 5 / 5

docs(register-check.sh): wildcard semantics misdescribed as "pathname expansion" — * crosses /, so an over-broad allow-list silently under-reports

#655 by shipwright was closed 2026-08-17 22:55:38 +02:00 2 / 2

bug(release-decide): #417 orphan-check walk BREAKS on the first bump-worthy commit, so a fixup above the prepare commit makes the skip (and the #259 range-scan) unreachable

#650 by engineer was closed 2026-08-17 23:18:16 +02:00

bug(changelog): composed sections can carry byte-identical duplicate bullets — dedup keys on commit-to-fragment identity, never on the emitted line

#649 by engineer was closed 2026-08-19 10:08:48 +02:00

bug(fragment-check): the documented blank-line fragment shape has ZERO enforcement, and the skip path posts no status so the gate cannot be required

#644 by bosun was closed 2026-08-19 09:02:42 +02:00 5 / 5

bug(release): the automated post-cut manifest write-back regressed between v0.33.0 and v0.34.0 — two releases hand-patched, and a stale anchor re-proposes published versions

#637 by bosun was closed 2026-08-19 09:42:04 +02:00 4 / 4

bug(ci): the changelog density gate watches CHANGELOG.md — the one layer where density cannot be durably fixed

#621 by bosun was closed 2026-08-19 08:32:17 +02:00 4 / 4