REUSE-WP-0017-T01: explicit capability_status on roster + coverage split in report gaps

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>

templates/NO_CAPABILITIES.template.md

@@ -0,0 +1,24 @@
+---
+# Copy this file to registry/NO_CAPABILITIES.md in the target repo.
+# It marks the repo as reviewed with no reusable capability to register,
+# converting an "empty scaffold" from ambiguous to informative.
+repo: <slug>
+reason: >
+  One or two sentences on why this repo has nothing to register — e.g.
+  personal experiment, fork with no independent scope, docs/canon-only,
+  probe/spike not intended for reuse.
+reviewed: "YYYY-MM-DD"
+reviewed_by: <person-or-agent>
+revisit: >
+  Optional. Note a condition or date under which this repo should be
+  reclassified (e.g. "revisit if the probe becomes a maintained service").
+---
+
+# No reusable capability
+
+This repo was reviewed for the `reuse-surface` capability registry
+(REUSE-WP-0017 coverage campaign) and has no capability to register at this
+time. See the `reason` field above.
+
+Set `capability_status: none` for this repo's row in
+`local-repo-roster.yaml` when this file lands.