Problem
skills/ba-propose/SKILL.md 5e defines a closed six-value enum for the terminal receipt's
capture: line (judged-reusable, suppressed — ship-url-unresolved, suppressed — non-interactive,
suppressed — already-captured, suppressed — judged-not-reusable, unavailable), and names 5e as its
canonical site. The literals are restated in 5f's dispatch paragraph and in two README.md feature
lists. Nothing pins them: rename or add a literal and a stale mention elsewhere reports green.
The same section admits this in prose ("No CI check pins any of this"). This issue is about closing
the cheap part of that gap.
Why the current justification is weaker than it reads
The trade was argued against load-site-mirror, whose byte-identity requirement genuinely does not fit
prose that legitimately paraphrases. But rubric-mirror in scripts/check-invariants.mjs is already a
presence-only mirror check — it asserts a literal (N ∈ {0, 25, 50, 75, 100}) appears per dispatch
block, plus a section-title citation per agent file. That is exactly the shape needed here, and it is
the precedent the deferral did not consider.
Proposed check
A seventh check asserting each of the six literals appears at least once outside 5e's canonical
block. Presence-only — deliberately not consistency-checking the prose paraphrases, since README's
bullets paraphrase by design.
Catches: "renamed the enum, missed a mention." Does not catch: a paraphrase that drifts without naming
a literal — which is a real residual and should stay documented rather than implied away. A worked
example of that exact residual is in this ship's learnings doc
(docs/solutions/prompt-authoring/2026-08-11-absence-grep-proves-spelling-not-concept-removed.md): a
full-token grep read green while the file still described the deleted machinery in other words.
Provenance
Surfaced by /ba-review on branch fix-ba-propose-5f-terminal-receipt (the ship that resolves #85) —
raised independently by complexity-reviewer (change amplification) and test-coverage-reviewer
(coverage gap), merged at confidence 100. The prose half of the finding was fixed in that ship: 5e's
mirror list now separates the two sites that restate literals from the three that are pointers. Only
the CI check was deferred here.
Adjacent
#82 (Pin the protected-artifacts guard per dispatch block, not just the confidence literal) is the
same kind of work — extending invariant coverage in check-invariants.mjs — and is already ready in
cluster:infra. Worth deciding whether these land as one slice; filed separately rather than folded in
unilaterally.
Problem
skills/ba-propose/SKILL.md5e defines a closed six-value enum for the terminal receipt'scapture:line (judged-reusable,suppressed — ship-url-unresolved,suppressed — non-interactive,suppressed — already-captured,suppressed — judged-not-reusable,unavailable), and names 5e as itscanonical site. The literals are restated in 5f's dispatch paragraph and in two
README.mdfeaturelists. Nothing pins them: rename or add a literal and a stale mention elsewhere reports green.
The same section admits this in prose ("No CI check pins any of this"). This issue is about closing
the cheap part of that gap.
Why the current justification is weaker than it reads
The trade was argued against
load-site-mirror, whose byte-identity requirement genuinely does not fitprose that legitimately paraphrases. But
rubric-mirrorinscripts/check-invariants.mjsis already apresence-only mirror check — it asserts a literal (
N ∈ {0, 25, 50, 75, 100}) appears per dispatchblock, plus a section-title citation per agent file. That is exactly the shape needed here, and it is
the precedent the deferral did not consider.
Proposed check
A seventh check asserting each of the six literals appears at least once outside 5e's canonical
block. Presence-only — deliberately not consistency-checking the prose paraphrases, since README's
bullets paraphrase by design.
Catches: "renamed the enum, missed a mention." Does not catch: a paraphrase that drifts without naming
a literal — which is a real residual and should stay documented rather than implied away. A worked
example of that exact residual is in this ship's learnings doc
(
docs/solutions/prompt-authoring/2026-08-11-absence-grep-proves-spelling-not-concept-removed.md): afull-token grep read green while the file still described the deleted machinery in other words.
Provenance
Surfaced by
/ba-reviewon branchfix-ba-propose-5f-terminal-receipt(the ship that resolves #85) —raised independently by
complexity-reviewer(change amplification) andtest-coverage-reviewer(coverage gap), merged at confidence 100. The prose half of the finding was fixed in that ship: 5e's
mirror list now separates the two sites that restate literals from the three that are pointers. Only
the CI check was deferred here.
Adjacent
#82 (Pin the protected-artifacts guard per dispatch block, not just the confidence literal) is the
same kind of work — extending invariant coverage in
check-invariants.mjs— and is alreadyreadyincluster:infra. Worth deciding whether these land as one slice; filed separately rather than folded inunilaterally.