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

@@ -4,7 +4,7 @@ type: workplan
title: "Capability coverage campaign: seed or explicitly close all empty scaffolds"
domain: infotech
repo: reuse-surface
status: ready
status: active
owner: claude-code
topic_slug: helix-forge
created: "2026-07-06"
@@ -72,7 +72,7 @@ and CI.
```task
id: REUSE-WP-0017-T01
status: todo
status: done
priority: high
state_hub_task_id: "90fe5bf2-7c03-4af5-bc4a-e5d608c7e879"
```