diff --git a/activity-definitions/state-hub-consistency-sweep.md b/activity-definitions/state-hub-consistency-sweep.md
index 8f88ae9..a48b9f4 100644
--- a/activity-definitions/state-hub-consistency-sweep.md
+++ b/activity-definitions/state-hub-consistency-sweep.md
@@ -2,12 +2,13 @@
 id: "7c4e9a12-8f3b-4d5e-9c6a-1b2d3e4f5a6b"
 name: "State Hub Consistency Sweep"
 type: activity-definition
-version: "1.0"
-enabled: true
+version: "1.1"
+enabled: false
 owner: custodian
 governance: custodian
-status: active
+status: paused
 created: "2026-06-21"
+updated: "2026-08-21"
 trigger:
   type: cron
   cron_expression: "*/15 * * * *"
@@ -37,6 +38,13 @@ activity-core owns the cron schedule and ActivityRun audit trail.
 
 ## Runner Status
 
+Paused 2026-08-21 under `RMGR-WP-0005-T11`. The production State Hub sweep
+mounted `/home/tegwick` read-write and the operator's `/home/tegwick/.ssh`,
+while 70 railiance01 checkouts still targeted the superseded `gitea-remote`
+lineage. The Temporal schedule is paused and State Hub sweep mounts are disabled
+until those checkouts are reconciled to `forgejo-remote` and the registrar
+preflight passes. Do not re-enable this definition independently.
+
 `enabled: true` during `STATE-WP-0064-T03` parallel week (started
 2026-06-21) alongside the local `custodian-sync.timer`. Both invoke the
 same State Hub API; the process lock makes overlapping runs idempotent.
@@ -80,4 +88,4 @@ The run should produce:
 - zero or more per-repo consistency reports in the API response
 - a lock-skipped response when another remote-all sweep is already active
 - one activity-core ActivityRun containing the sweep response metadata
-- no LLM call and no direct workplan or canon edits
\ No newline at end of file
+- no LLM call and no direct workplan or canon edits