docs(SCOPE): refresh Current State after workplan queue completion

Update status to stable maintenance now that all root CUST-WP workplans are
closed, including archived CUST-WP-0054. Clears C-30 freshness warning.

SCOPE.md

@@ -1,7 +1,7 @@
 ---
 domain: custodian
 repo: the-custodian
-updated: "2026-06-21"
+updated: "2026-07-08"
 ---
 
 # SCOPE
@@ -87,16 +87,17 @@ their own repositories and are referenced here only as integration pointers.
 
 ## Current State
 
-- Status: active — stable governance substrate, in daily use
+- Status: stable maintenance — governance substrate in daily ecosystem use; no
+  open CUST-WP workplans in this repo (queue complete as of 2026-07-08)
 - Implementation: substantial. Canon + memory + workplan conventions established;
-  State Hub operational (in its own repo); RAG-over-canon and drafting pipelines
-  (roadmap Phase 1) not yet started
+  State Hub operational on railiance01 (see `state-hub` repo); workstation
+  independence and fleet realignment finished (`CUST-WP-0054` archived);
+  RAG-over-canon and drafting pipelines (roadmap Phase 1) not yet started
 - Stability: stable — canon changes are review-gated; memory is append-only
-- Usage: daily, across the ecosystem; State Hub MCP active in agent sessions
-- Domains coordinated: dynamic — 14 active as of 2026-06-21 (canon, capabilities,
-  citation_evidence, coulomb_social, custodian, helix_forge, inter_hub, markitect,
-  netkingdom, personhood, railiance, stack, vergabe_teilnahme, whynot). Query the
-  live list with `list_domains()` rather than trusting a hard-coded count.
+- Usage: daily, across the ecosystem; State Hub MCP in agent sessions; new
+  implementation work typically lands in domain repos or `state-hub`, not here
+- Domains coordinated: dynamic — query the live list with `list_domains()` rather
+  than trusting a hard-coded count
 
 ---