Priority: P3
Category: DevOps / Reporting
Background:
After adding coverage reporting, a visual badge keeps repository status visible. Without an external service, GitHub Pages + workflow can publish a static SVG updated on main merges.
Goal:
Automate generation & publication of coverage badge (SVG) to a gh-pages branch (or /docs) and reference it in README.
Acceptance Criteria:
- Workflow triggered on push to main after tests
- Generates coverage summary (parse lcov or vitest summary) -> compute line %
- Renders SVG badge (shield style) and publishes to gh-pages (or docs/coverage-badge.svg on main)
- README embeds badge
- Idempotent (only updates when value changes to reduce noise)
Tasks:
- Add script to parse lcov and output JSON + SVG
- Workflow job (after CI) to checkout pages branch, update asset, push
- Conditional commit (skip if unchanged)
- README badge URL update
- Document maintenance in Dev section
Definition of Done:
Badge updates when coverage changes; no infinite commit loop.
Priority: P3
Category: DevOps / Reporting
Background:
After adding coverage reporting, a visual badge keeps repository status visible. Without an external service, GitHub Pages + workflow can publish a static SVG updated on main merges.
Goal:
Automate generation & publication of coverage badge (SVG) to a gh-pages branch (or /docs) and reference it in README.
Acceptance Criteria:
Tasks:
Definition of Done:
Badge updates when coverage changes; no infinite commit loop.