REUSE-WP-0017-T06: diagnose config-atlas publish blocker

Two conflated issues: (1) the raw-URL 303 redirect is already followed
correctly by establish.py's urllib-based probe -- re-running
publish-check now passes; the stale roster fail was from the 2026-06-16
sweep, not a live issue. (2) config-atlas was never actually registered
with the production hub (absent from the 60 sources at
reuse.coulomb.social/v1/federated despite hub_registered: true in the
roster) -- corrected to false. Local publish pass is now 61/61; hub
registration itself is blocked on REUSE_SURFACE_TOKEN, which has no
routing catalog entry -- needs Bernd to provide or route it.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

registry/federation/local-repo-roster.yaml

@@ -9,10 +9,10 @@ summary:
   established: 61
   pending: 0
   with_reuse_surface_seed: 8
-  hub_registered: 61
-  publish_pass: 60
-  publish_fail: 1
-  publish_sweep: '2026-06-16'
+  hub_registered: 60
+  publish_pass: 61
+  publish_fail: 0
+  publish_sweep: '2026-07-06'
   capability_status_has: 48
   capability_status_none: 13
   capability_status_pending: 0
@@ -111,9 +111,14 @@ repos:
   seed_from_reuse_surface: false
   seed_capability_ids:
   - capability.infotech.config-surface-atlas
-  hub_registered: true
-  publish_check: fail
-  publish_note: 303 not published (same block as state-hub/feature-control)
+  hub_registered: false
+  publish_check: pass
+  publish_note: local publish-check now passes (2026-07-06); Gitea's raw-URL
+    303 redirect (/raw/main/... -> /raw/branch/main/...) is followed
+    correctly by the current establish --publish-check code. hub_registered
+    corrected to false -- config-atlas is absent from the 60 sources in
+    https://reuse.coulomb.social/v1/federated; registration blocked on
+    REUSE_SURFACE_TOKEN (see REUSE-WP-0017-T06).
   batch: B02
 - slug: coordination-engine
   path: /home/worsch/coordination-engine