feat: consume Repo Manager classification publisher

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a053ff-1d6f-7fe2-ac1c-a6eb40a42a0c

workplans/HUB-WP-0006-repository-classification-navigation.md

@@ -166,6 +166,21 @@ therefore still required before comparison can start. Hub-core commits
 off until those three gates close; rollback remains the flag set to off plus
 the prior State Hub read route.
 
+Publisher checkpoint 2026-09-01: Repo Manager revision
+`10d87e21f50a0205b62688604c78c6f43a7171e5` now emits the exact frozen
+envelope through a read-only, bearer-capable HTTP `port.repo` route with stable
+registrar UUIDs and HMAC-bound paging. Hub-core's built-in HTTP client refreshes
+at startup and on a configured interval. Live conformance accepted 123
+repositories over five pages as one current generation; Repo Manager evidence:
+`docs/evidence/RMGR-WP-0013-live-conformance-2026-09-01.md`.
+
+T06 still waits only on production placement/networking and deployment of the
+two committed runtimes. The public Core Hub cluster does not own the host-local
+Repo Manager checkout registry; do not solve that by mounting a broad home
+directory or restoring State Hub as the classification authority. Once a
+scoped publisher endpoint is deployed and the candidate migration/image is
+rolled out, comparison and `RM_SLICE_TOPICSPINE` can proceed.
+
 ## Acceptance
 
 - [x] Repo Manager v1.0 authority and projection contract accepted