Archived

This repository has been archived on 2026-07-08. You can view files and clone it. You cannot open issues or pull requests or push a commit.

Files

tegwick a5e9a4a242

ci / validate-registry (push) Has been cancelled

Details

Finish REUSE-WP-0017: T05 approved, T07 closeout complete.

Mark coverage campaign finished with 62/62 roster coverage and 61
production federated capabilities; update SCOPE.md current state and
add completion milestone history.

2026-07-07 16:37:53 +02:00

1.3 KiB

Raw Blame History

REUSE-WP-0017 coverage campaign — complete

Date: 2026-07-07
Workplan: workplans/REUSE-WP-0017-capability-coverage-campaign.md

Outcome

The workstation capability registry coverage campaign is finished.

Metric	Result
Roster repos	62/62 established
Capability coverage	62/62 (`has` or explicit `no-capability`)
Unclassified scaffolds	0
Publish pass	62/62
Production federated capabilities	61 (61 enabled hub sources)
Local `federated.yaml`	61 capabilities (matches production)

Key events (2026-07-07)

core-hub added to roster and hub-registered (Forgejo URL)
inter-hub retired — capability deprecated, hub registration disabled
Eight Forgejo-migrated repos got hub URL fixes (were still on stale Gitea raw URLs)
Production POST /v1/federated/compose refreshed index from 26 → 61 capabilities
T05 human review approved; follow-up registry commits in vergabe-teilnahme, markitect-main, issue-core, core-hub

Acceptance

All REUSE-WP-0017 acceptance criteria met (see workplan frontmatter).

Follow-on

REUSE-WP-0018 — plan-check consumption loop (unblocked by published federated index)
REUSE-WP-0019 — Gitea→Forgejo host migration for remaining ~53 hub registrations

1.3 KiB Raw Blame History