REUSE-WP-0017-T01: explicit capability_status on roster + coverage split in report gaps
Some checks failed
ci / validate-registry (push) Has been cancelled

Adds capability_status: has|none|pending to every roster row (10 has /
51 pending currently), a coverage_ratio headline, and splits the gap
report's empty-scaffold section into unclassified vs explicitly-none.
Adds templates/NO_CAPABILITIES.template.md for the no-capability marker.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
2026-07-06 18:36:05 +02:00
parent 493f23123c
commit 8219a5d253
6 changed files with 154 additions and 11 deletions

View File

@@ -29,8 +29,8 @@ def test_collect_roster_stats_federation_ready():
root = Path(__file__).resolve().parent.parent
roster = root / "registry/federation/local-repo-roster.yaml"
stats = collect_roster_stats(roster, federation_ready=True)
assert stats["counts"]["total"] == 60
assert stats["counts"]["established"] == 60
assert stats["counts"]["total"] == 61
assert stats["counts"]["established"] == 61
assert "federation_readiness" in stats
text = format_roster_stats_markdown(stats)
assert "publish pass ratio" in text