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

registry/capabilities/capability.registry.register.md

@@ -47,14 +47,19 @@ external_evidence:
       - hosting registered capabilities
       - enforcing implementation architecture
   reliability:
-    level: R2
-    name: Tolerable
+    level: R3
+    name: Usable
     confidence: medium
     basis: consumer_quality_signals
     known_reliability_risks:
       - index drift still possible if authors skip validate
       - CLI requires local venv install
-      - schema ID pattern required a fix during WP-0003 dogfooding
+      - sibling repos cannot register until indexes publish raw URLs
+    evidence:
+      satisfied_signals:
+        - CI validate with fail-on-warnings on every push
+        - hub register/list/federated smoke on production reuse.coulomb.social
+        - pytest coverage for hub API and federation compose paths
 
 discovery:
   intent: >
@@ -112,7 +117,13 @@ evidence:
     - docs/deploy/reuse-kubernetes.md
   tests:
     - tests/test_hub.py
-  consumer_feedback: []
+    - tests/test_hub_sync.py
+    - .gitea/workflows/ci.yml
+  consumer_feedback:
+    - >
+        reuse-surface dogfood (REUSE-WP-0011): production hub registration and
+        /v1/federated compose succeeded on Railiance01 without write-path
+        regressions after WP-0011 deploy.
   bug_reports: []
   incidents: []
 
@@ -154,6 +165,14 @@ promotion_history:
       Hosted federation hub live at reuse.coulomb.social; hub register/update
       via HTTP API and reuse-surface hub CLI; production deploy on Railiance01.
     author: reuse-surface
+  - date: "2026-06-16"
+    dimension: reliability
+    from: R2
+    to: R3
+    rationale: >
+      CI gates, pytest hub/federation coverage, and production hub smoke support
+      normal registration workflows with documented limitations.
+    author: reuse-surface
 ---
 
 # Capability Registration

registry/capabilities/capability.registry.validate.md

@@ -33,12 +33,17 @@ external_evidence:
     out_of_scope_expectations:
       - runtime validation of registered capability implementations
   reliability:
-    level: R2
-    name: Tolerable
+    level: R3
+    name: Usable
     confidence: medium
     basis: consumer_quality_signals
     known_reliability_risks:
       - requires local venv install
+      - relation warnings require explicit --relations flag
+    evidence:
+      satisfied_signals:
+        - validate --relations --fail-on-warnings in CI
+        - tests/test_registry.py schema and drift coverage
 
 discovery:
   intent: Keep registry data structurally sound so agents and humans can trust discovery metadata.
@@ -72,7 +77,13 @@ relations:
 evidence:
   documentation:
     - tools/README.md
-  tests: []
+    - .gitea/workflows/ci.yml
+  tests:
+    - tests/test_registry.py
+  consumer_feedback:
+    - >
+        reuse-surface CI: registry changes fail when schema validation or relation
+        checks warn with --fail-on-warnings, giving agents a dependable pre-merge gate.
 
 consumer_guidance:
   recommended_for:
@@ -81,6 +92,14 @@ consumer_guidance:
     - certifying business correctness of capability claims
   known_limitations:
     - warnings do not fail CI unless --fail-on-warnings is set
+
+promotion_history:
+  - date: "2026-06-16"
+    dimension: reliability
+    from: R2
+    to: R3
+    rationale: CI fail-on-warnings and pytest registry coverage support dependable validation.
+    author: reuse-surface
 ---
 
 # Registry Entry Validation

registry/capabilities/capability.statehub.progress-log.md

@@ -32,11 +32,16 @@ external_evidence:
     out_of_scope_expectations:
       - replacing git commit history
   reliability:
-    level: R2
-    confidence: low
+    level: R3
+    name: Usable
+    confidence: medium
     basis: consumer_quality_signals
     known_reliability_risks:
-      - depends on hub availability
+      - depends on hub availability and tunnel health for remote agents
+    evidence:
+      satisfied_signals:
+        - reuse-surface AGENTS.md session-close protocol cites POST /progress/
+        - cross-repo agents log progress with workstream_id linkage
 
 discovery:
   intent: Provide auditable progress memory for cross-repo agent and operator work.
@@ -63,6 +68,14 @@ relations:
   related_to:
     - capability.statehub.workstream-coordinate
 
+evidence:
+  documentation:
+    - AGENTS.md
+  consumer_feedback:
+    - >
+        reuse-surface agents (REUSE-WP-0012): session-close progress posts to State
+        Hub succeeded for workstream fb0b6067 during federation workplan work.
+
 consumer_guidance:
   recommended_for:
     - closing agent sessions with hub progress notes