Development record
The lint chapter runs its site and outbound targets as CI gates; the lint contract says record-lint and docs-lint are the whole of CI's lint coverage.
The lint chapter runs its site and outbound targets as CI gates; the lint contract says record-lint and docs-lint are the whole of CI's lint coverage.
A premise contradiction (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/brief/04-surfaces/16-lint.md:147— "the docs target runs in thedocs-lintmake target and in CI, the site target in thesite-rendermake target and in CI" - End B:
.abcd/development/brief/05-internals/06-lint.md:56— "Until those ship, the two armed gates above are the whole of CI's lint coverage"
16-lint says three abcd lint targets are gated: the docs target in CI, the site target in the site-render make target and in CI, and the outbound target in CI's attribution workflow. 06-lint, the canonical lint contract, says that until the planned tiers ship, the two armed gates (record-lint and docs-lint) are the whole of CI's lint coverage. The site and outbound targets running in CI contradict 'the whole'.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 575.
Frontmatter
| id | iss-2610262035294777 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262035294777-the-lint-chapter-runs-its-site-and.md
open on GitHub ↗ · commit history ↗