didericis/bot-bottle
1
0
Fork 0
Code Issues 7 Pull Requests 15 Actions Packages Projects Releases Wiki Activity

Risk-weighted coverage policy + diff-coverage gate (ADR 0004) #294

Open
didericis-claude wants to merge 1 commits from cover-global-90 into cover-egress-addon-adapter
pull from: cover-global-90
merge into: didericis:cover-egress-addon-adapter
Conversation 0 Commits 1 Files Changed 6
+378

1 Commits

Author SHA1 Message Date
didericis 632ab002ed ci(coverage): risk-weighted coverage policy + diff-coverage gate
lint / lint (push) Successful in 1m52s
Details
test / unit (pull_request) Successful in 46s
Details
test / integration (pull_request) Successful in 16s
Details
test / coverage (pull_request) Successful in 1m2s
Details 
Adopt ADR 0004: stop chasing a single global coverage number and
measure what matters instead.

- Omit the genuinely-interactive `cli/init.py` shell (read_tty_line
  prompt loops) alongside the existing `cli/tui.py`, with a rationale
  comment in .coveragerc. Subprocess/backend orchestration is NOT
  omitted — it stays visible and is scored via the integration suite.
- scripts/coverage.sh runs unit + integration under one coverage
  measurement (the policy's yardstick) and can report the critical
  security/logic core held to the >=90% target.
- scripts/diff_coverage.py is a stdlib-only gate (no diff-cover dep):
  new/changed executable lines must be >=90% covered. This is the
  enforced regression guard; the global number is informational.
- CI gains a `coverage` job: combined report + the diff-coverage gate.
- Unit-test `cli/__init__.py` dispatch/exit-code mapping (it's logic,
  not I/O, so it earns tests rather than an omit).

Combined unit+integration coverage now reports 83% global / 87% across
the critical modules; per-module ratcheting toward 90% is the ongoing
work this policy frames.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NkwFXLFff9PYPy4wgVBJp9
 2026-06-25 21:29:08 -04:00