coulomb/reuse-surface
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

REUSE-WP-0017-T04 cohort 2: draft entries for 10 more has-capability repos
Some checks failed
ci / validate-registry (push) Has been cancelled
Details

Browse Source 
issue-core (migrated existing CAPABILITY-issue-tracking.yaml),
kaizen-agentic, key-cape, kontextual-engine, llm-connect, markitect-filter,
markitect-main (registered as superseded legacy platform), markitect-quarkdown,
markitect-tool, net-kingdom. All validate, no overlap with existing
federated capabilities. Committed locally in each sibling repo; push held
for T05 human review. Coverage 34/61 -> 44/61.

Also fixed a stale empty_scaffold_count >= 40 test threshold -- no longer
meaningful as the coverage campaign shrinks that number by design.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
Bernd Worsch
2026-07-06 19:44:02 +02:00
parent b48a4edf81
commit 651b84a16b
3 changed files with 60 additions and 42 deletions
Download Patch File Download Diff File Expand all files Collapse all files

27
workplans/REUSE-WP-0017-capability-coverage-campaign.md
View File

@@ -139,16 +139,25 @@ principle anyway.
citation-evidence, email-connect, guide-board, hub-core, info-tech-canon,
infospace-bench, inter-hub. All validate; no overlap with the existing 24
federated capabilities. Committed locally in each sibling repo (push held
for T05). Coverage now 34/61.
for T05). Coverage 24/61 -> 34/61.
Remaining cohorts (27 repos): issue-core (migrate its existing
`CAPABILITY-issue-tracking.yaml` rather than draft fresh), kaizen-agentic,
key-cape, kontextual-engine, llm-connect, markitect-filter, markitect-main,
markitect-quarkdown, markitect-tool, net-kingdom, 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.
**Cohort 2 (20/37 done):** issue-core (migrated its existing
`CAPABILITY-issue-tracking.yaml` into the standard registry location rather
than drafting fresh), kaizen-agentic, key-cape, kontextual-engine,
llm-connect, markitect-filter, markitect-main (registered honestly as a
superseded legacy platform pointing at its three successor repos, not a
forward-looking target), markitect-quarkdown, markitect-tool, net-kingdom.
All validate; no overlap with existing federated capabilities. Committed
locally (push held for T05). Coverage 34/61 -> 44/61. Also fixed a stale
`empty_scaffold_count >= 40` test threshold in `tests/test_reports.py` —
no longer meaningful once the coverage campaign started shrinking that
number by design.
Remaining cohort (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.
- `reuse-surface establish --discover` with llm-connect per repo
- Manual tightening: id namespace (`capability.<domain>.<verb>`), scope