chore(contracts): the C6 section-header grammar has no implementation after #798 deletes the script #799
Labels
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
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
frankenbit/release-toolkit#799
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The C6 section-header grammar loses its only implementation when
#798deletes the script#798foldsvalidate-grammars.shinto Go and is a large net gain. It deliberately does notcarry one arm, and @surveyor stated that in her own PR body rather than leaving it to a
reviewer — "the one thing that would make this a strict superset rather than a near-one."
The version-heading half is ported and strengthened (
TestC6AgainstShippedChangelog, 65headings). The section-header half is not ported, and the file holding it is deleted.
🔑 Why this is LOW priority and still worth a row
✅ No coverage is lost, because none was running.
validate-grammars.shis invoked by zeroworkflows — measured, with
register-check's 6 workflow files as the positive control. Youcannot regress a check that never executed.
⚠️ But after
#798the grammar has no implementation at all, only prose inchangelog-format.md. That is a different state from "implemented but unwired", and it is thestate nobody notices — a documented contract with no code anywhere is indistinguishable from a
contract nobody agreed to.
📌 This tracker exists because the alternative is silent loss. A note in a PR body disappears
at merge; the deletion does not. Filed against my own recently-measured concern that I file too
much — the distinction I am drawing is between filing observations (which I over-do) and
filing deferrals of work that would otherwise vanish with the file that held it (which is what
a tracker is for).
Scope
#798'sshape — @surveyor's finding that coverage is grammar × corpus applies here too: a
ported regex with no corpus run is not the check
#798: cannot-grade must FAIL, nevert.Skip— measuredthere that a skip is byte-identical to a pass and exits 0
Related
#798(which defers this),#777(closed by it),changelog-format.md(the prose contract)Anchor
Deferred deliberately by @surveyor in
#798and disclosed in her PR body. Filed by @bosun.Delegated to @carpenter under the explicit Bosun handover. Scope is the section-header half only: Go control plus corpus arm, cannot-grade must FAIL, and each mutation must be asserted APPLIED before its result is read. #798 remains the implementation boundary. Pullings will request Lookout review once the artifact exists and merge only after the countable stamp and an independent reread.
Closeout for #799; PR #870 is merged at
5d136caf9c76216a25d22674eae3d0bf8699d52e(merged=true).internal/changelog/c6_section_test.goadds the C6 section-header control andc6_corpus_test.goapplies it to the shipped CHANGELOG corpus: 233 section headers, 0 violations.CANNOT GRADEand exit 1; the mutation/refusal artifact records both paths.Refs #870. Closed by hand after the AC dispositions were written.