Implement REUSE-WP-0012 federation scale and intent alignment

Add hub sync and report cohorts CLI commands with pytest coverage, document
sibling index publish contract and hub hardening path, align INTENT layout,
raise external evidence on three registry entries, and close gap priorities
19-23 (priority 18 deferred on sibling index blocks).

INTENT.md

@@ -240,38 +240,54 @@ evidence:
 ## Initial Repository Role
 
 The initial role of `reuse-surface` is to define and maintain the capability
-registry model, standards, schemas, examples, and reference tooling.
+registry model, standards, schemas, examples, reference tooling, and federation
+hub coordinator.
 
-Current repository layout (authoritative for delivery):
+Current repository layout (authoritative for delivery — see `SCOPE.md` for detail):
 
 ```text
 reuse-surface/
 ├── INTENT.md
 ├── SCOPE.md
 ├── AGENTS.md
+├── pyproject.toml
+├── Dockerfile
+├── reuse_surface/          # CLI, hub service, federation, graph, catalog
 ├── specs/
 │   ├── ProductRequirementsDocument.md
 │   ├── UseCaseCatalog.md
-│   └── CapabilityMaturityStandard.md
+│   ├── CapabilityMaturityStandard.md
+│   └── FederationHubAPI.md
 ├── schemas/
-│   └── capability.schema.yaml
+│   ├── capability.schema.yaml
+│   ├── federation.schema.yaml
+│   └── hub-registration.schema.yaml
 ├── templates/
 │   └── capability-entry.template.md
 ├── registry/
 │   ├── README.md
-│   ├── capabilities/
-│   └── indexes/
-│       └── capabilities.yaml
+│   ├── capabilities/       # per-entry Markdown
+│   ├── indexes/            # capabilities.yaml, federated.yaml
+│   └── federation/         # sources.yaml, cache/
 ├── docs/
 │   ├── CapabilityRegistryConcept.md
-│   └── IntentScopeGapAnalysis.md
-└── tools/
-    └── README.md
+│   ├── RegistryFederation.md
+│   ├── IntentScopeGapAnalysis.md
+│   ├── deploy/reuse-kubernetes.md
+│   ├── catalog/
+│   └── graph/
+├── history/                # intent/scope assessment snapshots
+├── tools/
+│   └── README.md
+└── workplans/
+    └── archived/
 ```
 
 See `SCOPE.md` for what is possible now versus planned. See
 `docs/IntentScopeGapAnalysis.md` for tracked gaps between intent and delivered
-scope.
+scope. Federation operations: `docs/RegistryFederation.md` and
+`specs/FederationHubAPI.md`. Assessment history:
+`history/2026-06-15-intent-scope-assessment.md`.
 
 ## Success Criteria