officially add sources

docs/project_map.md

@@ -22,6 +22,9 @@ This repository has three main packages plus examples and tests.
 - `wf_authoring.node`: typed Python function to `NodeSpec`.
 - `wf_mcp`: public MCP facade.
 - `wf-mcp`: CLI script from `pyproject.toml`.
+- `wf_mcp.broker.WfMcpService.get_catalog()`: backend MCP catalog snapshots.
+- `wf_mcp.broker.WfMcpService.get_planner_catalog()`: backend snapshots plus
+  broker-local workflow sources such as `wf.std` and `wf.mcp`.
 
 ## Examples
 
@@ -57,6 +60,7 @@ need local environment configuration.
   `wf_core.validation`.
 - Add author convenience helpers in `wf_authoring`, not `wf_core`.
 - Add MCP transport/proxy/config behavior in `wf_mcp` concern packages.
+- Add broker-local workflow utilities as `WfMcpService` spec sources, not as
+  fake MCP connections.
 - Add runnable examples in `examples`.
 - Add test-only servers or helpers in `tests/fixtures`.
-

docs/wf_mcp_architecture.md

@@ -31,6 +31,21 @@ relevant concern package directly.
 - `wf_mcp.shared` should stay pure and should not import other `wf_mcp` concern packages.
 - Root compatibility shims should stay thin: import and re-export only.
 
+## Broker Catalogs
+
+The broker keeps two related catalog views:
+
+- `get_catalog()` is the backend MCP catalog. It only includes enabled upstream
+  connection snapshots loaded from storage.
+- `get_planner_catalog()` is the workflow-planning catalog. It includes backend
+  connection snapshots plus broker-local system sources such as `wf.std` and
+  `wf.mcp`.
+
+Broker-local sources are not fake MCP backend connections. They are registered
+as service spec sources so raw workflow plans can address nodes like
+`wf.std.runtime_error` and `wf.mcp.call_tool` without polluting connection status,
+auth, adapter lookup, or persisted backend catalog snapshots.
+
 ## Hot Reload
 
 Transparent proxy reload is intentionally isolated in