Avoid mixing boolean --coverage flag with dot-notation
--coverage.reporter=json which can conflict in vitest v4.
Use --coverage.enabled for explicit, compatible behavior.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Replace the blocking diff-cover workflow with a non-blocking coverage
reporter that posts a PR comment showing lines covered, lines not
covered, overall coverage percentage, and uncovered line ranges —
scoped to only the files changed in the PR.
Closes#913
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Uses dorny/paths-filter to detect which packages have changes.
Tests and coverage only run for affected packages — e.g. a
web-only change won't trigger core or CLI tests.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Uses diff-cover to check that newly added or modified lines in PRs
have at least 80% test coverage, without requiring the entire
codebase to meet the threshold.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
fireddd