4grayandClaude Opus 5 21e55e4bb4 fix(ci): classify release-tools in the coverage policy (#1260) ...

#1256 added the release-tools project with a test target but never listed it
in tools/coverage/coverage-policy.json, so `coverage:ci` fails with "Coverage
policy is missing projects that have a test target: - release-tools". Master
has been red since that merge (270350c2) and every PR rebased onto it inherits
the failure.

Tier B, mirroring the sibling `packaging` project: the tests validate
release-note parsing, rendering and gate policy, but the scripts are release
tooling rather than shipped source, so a percentage-coverage baseline would
measure nothing useful.

Verified: `check-coverage-policy.mjs` reports 36 projects classified
(30 A / 6 B / 6 C), and `--run-non-tier-a` runs the release-tools suite green.

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>

2026-07-25 21:17:35 +02:00

..

check-coverage-policy.mjs

feat(ci): enforce lint, guard coverage policy, add max-lines rule (#1117)

2026-07-04 10:06:45 +02:00

coverage-health.mjs

[codex] Add scoped coverage reporting (#1024)

2026-06-06 17:41:40 +02:00

coverage-policy.json

fix(ci): classify release-tools in the coverage policy (#1260)

2026-07-25 21:17:35 +02:00

e2e-semantic-summary.mjs

[codex] Add scoped coverage reporting (#1024)

2026-06-06 17:41:40 +02:00

e2e-v8-web.mjs

[codex] Add scoped coverage reporting (#1024)

2026-06-06 17:41:40 +02:00

merge-coverage.mjs

[codex] Add scoped coverage reporting (#1024)

2026-06-06 17:41:40 +02:00

run-tier-a-coverage.mjs

[codex] Add scoped coverage reporting (#1024)

2026-06-06 17:41:40 +02:00