Development record
launch's citation-baseline row refuses on an overdue citation; docs says the launch preflight only names what would stop a release, while the release still cuts
launch's citation-baseline row refuses on an overdue citation; docs says the launch preflight only names what would stop a release, while the release still cuts
A premise contradiction (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/brief/04-surfaces/04-launch.md:338— "against their receipts and refuses on a broken, unreceipted or overdue one." - End B:
.abcd/development/brief/04-surfaces/10-docs.md:228— "which names what the citation baseline would stop a release on while a release still cuts."
04-launch.md says the citation-baseline row of the pre-flight suite refuses on a broken, unreceipted or overdue citation. 10-docs.md says launch computes its own citation preflight and that this preflight names what the citation baseline would stop a release on, while a release still cuts. In docs, only the lint's release-gate flag, passed by the release workflow, makes an overdue citation a blocker, and no committed config can arm it. Either the cut refuses on an overdue citation without that flag, or it still cuts.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 277.
Frontmatter
| id | iss-2610262032307333 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262032307333-launch-s-citation-baseline-row-refuses.md
open on GitHub ↗ · commit history ↗