Extract coverage badge generation to dedicated workflow using rhiza-tools

[Copilot]

Coverage badge generation was embedded in the make book target. This extracts it to a standalone workflow using the built-in rhiza-tools command.

Changes

New workflow .github/workflows/rhiza_coverage_badge.yml

• Runs on push to main/master
• Uses uvx "rhiza-tools>=0.2.0" generate-coverage-badge
• Uploads badge JSON as artifact (90-day retention)

Modified .rhiza/make.d/book.mk

• Removed inline badge generation logic (-17 lines)

Deleted .rhiza/utils/generate_coverage_badge.py

• Custom script replaced by rhiza-tools command (-103 lines)

Example

Badge generation now uses the official rhiza-tools CLI:

uvx "rhiza-tools>=0.2.0" generate-coverage-badge \
  --coverage-json _tests/coverage.json \
  --output _badge/coverage-badge.json

Previously required custom Python script maintained separately.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Coverage badge should be constructed in its own workflow.</issue_title>
<issue_description>not hidden somewhere in "make book"</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Coverage badge should be constructed in its own workflow. #591

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[tschm]

@copilot: no need to include the construction in rhiza_book.yml

[Copilot]

@copilot: no need to include the construction in rhiza_book.yml

Removed in 3783ac1. The book workflow no longer includes badge generation - it's now only in the dedicated coverage badge workflow.

[tschm]

@copilot: but the actual construction of the badge is also a command in rhiza-tools. Use that instead of having the py file in utils

[HarryCampion]

Does this need to be a workflow?

[tschm]

I think so. It's hidden in the book workflow. So better to be more isolated as some repos have tests but no book