Files

ci / validate-registry (push) Has been cancelled

Details

REUSE-WP-0014: T11 docs, roster stats, workplan finished

Link local-repo-roster in RegistryFederation; rollout milestone history;
update IntentScopeGapAnalysis (60 hub members). Add stats --roster
--federation-ready for workstation federation readiness.

2026-06-16 02:09:57 +02:00

1.7 KiB

Raw Blame History

Local workstation repo registry rollout complete

Date: 2026-06-16
Workplan: REUSE-WP-0014
Tracking: registry/federation/local-repo-roster.yaml

Milestone

All 60 git repositories one level under /home/worsch/<slug>/ now have capability registry scaffolds (registry/indexes/capabilities.yaml), local validation, and hub registration on https://reuse.coulomb.social.

Metric	Value
Established	60/60
Hub registered	60/60
Publish pass (Gitea raw 200)	47/60
Publish fail (operator/Gitea)	13/60
Federated compose capabilities	37
Duplicate-ID warnings	16 (owner migration; see dedup plan)

Scope definition

A repo is in scope when it is ~/<slug>/ with a valid .git directory. Excluded: dot-directories, nested worktrees, non-git folders.

Batches completed

Task	Batch	Repos
T02	seed-ready	`activity-core`, `audit-core`, `flex-auth`
T03	B01	10
T04	B02	10
T05	B03	10
T06	B04	10
T07	B05	10
T08	B06	5

Operator follow-up (publish blockers)

13 repos return Gitea raw HTTP 404 despite local establishment. See roster publish_note per slug and T09 sweep in the workplan. hub-core also cannot push (Gitea repo missing; push-to-create disabled).

Federation artifacts

registry/federation/sources.yaml — 60 hub-synced URL sources
registry/indexes/federated.yaml — composed index (regenerate with federation compose)
history/2026-06-16-federation-deduplication-plan.md — per-owner reuse-surface dedup

Observability

reuse-surface stats --roster registry/federation/local-repo-roster.yaml --federation-ready

1.7 KiB Raw Blame History