REUSE-WP-0017-T04 cohort 3 (final): draft entries for remaining 17 repos

open-cmis-tck, open-reuse, ops-bridge, phase-memory, railiance-apps,
railiance-cluster, railiance-enablement, railiance-fabric, railiance-forge,
railiance-infra, railiance-platform, repo-scoping, the-custodian,
user-engine, vantage-point, vergabe-teilnahme, whynot-design.

the-custodian entry deliberately scoped to its non-confidential
runtime/tools/ surface only, given the repo's NDA notice. vergabe-teilnahme
honestly registered at D1/C0 given its own unfilled SCOPE.md.

T04 complete: coverage 44/61 -> 61/61 (48 has-capability, 13 explicit
no-capability, 0 unclassified). All 50 sibling-repo commits across three
cohorts remain local only, pending T05 human review and push.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

workplans/REUSE-WP-0017-capability-coverage-campaign.md

@@ -123,7 +123,7 @@ For each confirmed `no-capability` repo:
 
 ```task
 id: REUSE-WP-0017-T04
-status: wait
+status: done
 priority: high
 state_hub_task_id: "20d67516-331b-46bd-8a90-1170139313c2"
 ```
@@ -153,11 +153,31 @@ locally (push held for T05). Coverage 34/61 -> 44/61. Also fixed a stale
 no longer meaningful once the coverage campaign started shrinking that
 number by design.
 
-Remaining cohort (17 repos): open-cmis-tck, open-reuse, ops-bridge,
+**Cohort 3 / final (17/17 done):** open-cmis-tck, open-reuse, ops-bridge,
 phase-memory, railiance-apps, railiance-cluster, railiance-enablement,
 railiance-fabric, railiance-forge, railiance-infra, railiance-platform,
 repo-scoping, the-custodian, user-engine, vantage-point, vergabe-teilnahme,
-whynot-design.
+whynot-design. All validate; no overlap with existing federated
+capabilities. Committed locally (push held for T05). Coverage 44/61 ->
+**61/61 — full coverage, T04 complete**.
+
+Notable calls in this cohort:
+- **the-custodian**: repo root is confidential/proprietary (NDA notice in
+  its README). Entry is deliberately scoped only to the non-confidential
+  `runtime/` agent framework and `tools/` repo-classification scripts;
+  canon/memory content is explicitly excluded from the entry's `includes`
+  and called out in `consumer_guidance.not_recommended_for`.
+- **vergabe-teilnahme**: its own `SCOPE.md` is an unfilled template, so
+  discovery is honestly D1/C0 — flagged in `known_limitations` that filling
+  in SCOPE.md is the natural next step before further promotion.
+- **markitect-main** (cohort 2) and **vantage-point**/**railiance-forge**
+  patterns repeat here: several repos (open-reuse, vantage-point) have a
+  stale repo-seed-template README; SCOPE.md/INTENT.md were used as the
+  authoritative source instead, noted per-entry.
+- **railiance-enablement**, **railiance-apps**, **the-custodian**: each
+  surfaced tooling directly relevant to REUSE-WP-0019 (Forgejo promotion
+  script, forgejo-smoke.sh, patch-forgejo-remote-urls.sh) — worth cross-
+  referencing when that workplan starts its host-migration inventory (T01).
 
 - `reuse-surface establish --discover` with llm-connect per repo
 - Manual tightening: id namespace (`capability.<domain>.<verb>`), scope