docs: clarify local cli config composition

docs/current_roadmap.md

@@ -105,6 +105,9 @@ auth admin are implemented. The next work is polish, not new broad surfaces.
 - Completed: static source inventory providers now have an explicit
   `WorkflowSourceProvider.load_sources()` seam in `wf_server`, and Python
   source loading is behind `PythonSourceProvider`.
+- Completed: `wf --local --config <workflow-config>` now composes configured
+  neutral server sources in-process instead of falling back to built-in static
+  sources only.
 - Completed: server startup policy moved to `wf_server.cli`; JSON-RPC HTTP
   remains in `wf_transport_rpc_http`:
   [`server CLI and transport boundary`](superpowers/specs/2026-06-10-server-cli-transport-boundary.md).

docs/wf_cli.md

@@ -13,6 +13,12 @@ wf --config wf_mcp.config.json <command>
 
 If `--config` is omitted, `wf_mcp.config.json` is used.
 
+`--local` still uses the selected `--config` file. For neutral workflow configs,
+it builds the configured server in the CLI process, including configured Python
+sources and other local source providers. Use `--url` when you want to force the
+CLI to talk to an already-running `wf-rpc-server`; `--local` and `--url` are
+mutually exclusive.
+
 ## Remote Server
 
 Start a local/static JSON-RPC workflow server:

src/wf_cli/context.py

@@ -151,6 +151,8 @@ def load_cli_context(
         store = config.server.workflow_store
         if not isinstance(store, FilesystemStoreConfig):
             raise ValueError("local CLI target currently requires filesystem store")
+        # Uses config-aware builder so configured sources (Python, etc.) are
+        # composed in-process, matching wf-rpc-server behavior.
         server = build_workflow_server_from_workflow_config(config)
         return CliContext(
             config_path=resolved_config_path,