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).

SCOPE.md

@@ -58,6 +58,8 @@ The MVP registry foundation, CLI tooling (REUSE-WP-0003), federation stack
   (local paths and remote HTTP URLs with cache)
 - **Register federation sources on the hosted hub** with `reuse-surface hub`
   against `https://reuse.coulomb.social`
+- **Sync local federation manifest from hub** with `reuse-surface hub sync`
+- **Export planning cohorts** with `reuse-surface report cohorts`
 - **Run the hub locally or in a container** with `reuse-surface serve`
 - **Generate relation graphs** with `reuse-surface graph`
 - **Explore relations interactively** at `docs/graph/index.html`
@@ -70,13 +72,13 @@ index, CLI automation, and the production hub.
 
 ## What Is Not Possible Yet
 
-- **`reuse-surface hub sync`** — materialize local `sources.yaml` from hub state
 - **Automatic hub refresh** — federated compose is on-demand; no polling or
   webhooks
 - **Cross-repo federation at scale** — hub has one registered repo; sibling
-  domains must publish capability indexes before registration
-- **Planning analytics** — no gap reports, roadmap views, or maturity-filter
-  reports beyond manual query/export
+  domains must publish capability indexes before registration (see
+  `history/2026-06-16-hub-registration-blocks.md`)
+- **Planning analytics beyond cohorts** — no gap reports, roadmap views, or
+  standardization tracker beyond `report cohorts`, query, and export
 - **Managed platform posture** — hub runs as a container (A5 artifact) without
   documented SLO, multi-replica, or Postgres backing
 - **Formal consumer feedback loop** for registry workflows (reliability evidence
@@ -98,14 +100,14 @@ See `tools/README.md` for command reference.
 - **Docs:** `docs/CapabilityRegistryConcept.md`, `docs/RegistryFederation.md`,
   `docs/IntentScopeGapAnalysis.md`, deploy guide `docs/deploy/reuse-kubernetes.md`.
 - **CI:** `.gitea/workflows/ci.yml` — validate, federation compose, catalog,
-  graph, pytest (20 tests).
+  graph, pytest, informational `report cohorts`.
 - **Federated index:** `registry/indexes/federated.yaml` (local compose).
 - **Relation graph:** `docs/graph/capability-graph.mmd`, `docs/graph/index.html`.
 - **Searchable catalog:** `docs/catalog/search.html`.
 - **Workplans:** REUSE-WP-0001 through REUSE-WP-0011 finished; WP-0011 archived;
-  **REUSE-WP-0012** ready (federation scale + intent alignment).
+  **REUSE-WP-0012** finished (federation scale + intent alignment).
 - **Assessment history:** `history/2026-06-15-intent-scope-assessment.md`.
-- **Self-assessed vector:** `D5 / A4 / C4 / R3` (see `docs/IntentScopeGapAnalysis.md`).
+- **Self-assessed vector:** `D5 / A4 / C5 / R3` (see `docs/IntentScopeGapAnalysis.md`).
 
 ## Repository Layout