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>

tests/test_reports.py

@@ -97,7 +97,7 @@ def test_collect_gap_report_from_roster():
     roster = root / "registry/federation/local-repo-roster.yaml"
     report = collect_gap_report(roster)
     assert report["summary"]["total"] == 61
-    assert len(report["publish_fail"]) == 1
+    assert len(report["publish_fail"]) == 0
     assert report["unclassified_count"] + report["explicit_none_count"] == report["empty_scaffold_count"]
     assert "/" in report["coverage_ratio"]