Source catalog! wfmcpservice thinning

docs/current_roadmap.md

@@ -118,6 +118,9 @@ implementation state.
   - Double-delegation has been removed: CLI and MCP workflow tools construct
     `WorkflowApi(context_from_service(service))` directly. `WorkflowSurfaceHandlers`
     remains only as a temporary compatibility shim for older imports.
+  - `WfMcpService` is being reduced into injected implementation services. Source
+    registry and catalog projection now live in `SourceCatalogService`; the old
+    service methods remain as compatibility delegates for MCP broker callers.
 
 Frame stress points remaining for native subgraphs and future fork/gather:
 

docs/superpowers/research/2026-06-01-wf-api-extraction-map.md

@@ -112,6 +112,10 @@ The extraction seam is clean: `WorkflowSurfaceHandlers` touches ~6 distinct capa
 | `adapters` | `dict[str, BackendAdapter]` | `self.service.adapters` | 1 | **MCP-specific** (live source check) |
 | `load_auth(connection_id)` | `AuthRecord \| None` | `self.service.load_auth(...)` | 1 | **MCP-specific** (live source check) |
 
+Source/catalog ownership is now split: `WfMcpService` coordinates broker runtime
+state, while `SourceCatalogService` owns capability source maps, planner catalog
+projection, snapshot hydration, and local docs lookup.
+
 ### WfMcpService Members NOT Used by WorkflowSurfaceHandlers
 
 These members of `WfMcpService` (`src/wf_mcp/broker/service/core.py`) are NOT accessed by `WorkflowSurfaceHandlers`: