Repository navigation
Enforce the code rules that need a graph pass, a filename check or the CLI #105
Description
Parent
What to build
(Rewritten 2026-09-16. #122 enforced six of the seven rules this ticket was opened for; only RULE-044 is left, and its acceptance criteria were still asking for all seven.)
One rule in the rule ledger still waits on code that does not exist yet:
- RULE-044: the CLI conventions — help on
--helpand-h, data on stdout and diagnostics on stderr, only data under--json, one exit-code enum,NO_COLOR, never prompting — proved by process-level tests once the CLI ring exists.
It moves from pending to enforced with a fixture that proves it fires, in the change that adds its enforcer.
Landed already, in #122: RULE-018 (depcruise:no-circular-folders), RULE-019, RULE-023, RULE-024, RULE-033 and RULE-042, each with the fixture its ledger row names.
Acceptance criteria
- RULE-044 is enforced, and its fixture fails on a probe that breaks the rule.
- The rule ledger's pending count drops by one.
Activity
test: enforce the code rules that need a graph pass or a filename che…
ExtraToast commentedon Sep 16, 2026
Rewritten, not closed. #122 landed six of the seven rules this ticket named — RULE-018, RULE-019, RULE-023, RULE-024, RULE-033 and RULE-042 — without a closing keyword, so the ticket stayed open with acceptance criteria that no longer matched the ledger: it still asked for all seven and for "the pending count drops by seven".
What is actually left is RULE-044, the CLI conventions, which cannot be enforced before the CLI ring exists. That is why #38 stays the blocker. The body now scopes the ticket to that one rule and records the six that landed, so the remaining work is what the ticket asks for.