feat: prefer stateful runtime for mcp content access

docs/current_roadmap.md

@@ -253,6 +253,9 @@ implementation state.
     - Completed: persistent MCP runtime can now route `get_prompt` through
       the owner-task queue and `McpSourceClient`. This keeps prompt reads
       stateful without adding raw method invocation or notification support.
+    - Completed: broker content access now prefers a configured stateful MCP
+      runtime for `read_resource` and `get_prompt`, with one-shot adapter fallback.
+      Catalog refresh/discovery remains one-shot by policy.
   - Auth/source secrets boundary: keep registry desired state separate from
     upstream credentials, and surface missing auth as validation diagnostics.
     The contract is now specified in

docs/historical/superpowers/plans/2026-06-07-content-access-stateful-runtime-routing.md

@@ -1,5 +1,10 @@
 # Content Access Stateful Runtime Routing Implementation Plan
 
+> **Historical:** This plan has been implemented. The `StatefulMcpRuntime` protocol
+> is in `wf_sources_mcp.sdk`, upstream transport prefers it for content reads,
+> and `WfMcpService` wires the configured runtime pool as both `tool_executor`
+> and `stateful_runtime`.
+
 > **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.
 
 **Goal:** Route broker content reads (`read_resource`, `render_prompt`) through a stateful MCP runtime when one is configured, while preserving one-shot adapter fallback.

docs/superpowers/specs/2026-06-03-long-lived-workflow-api-boundary.md

@@ -120,7 +120,10 @@ First slices should move leaf modules only and leave `wf_mcp` re-export shims:
 12. Complete: persistent MCP runtime can route `get_prompt` through the
     owner-task queue and `McpSourceClient`. Runtime still does not expose raw
     method invocation, notifications, or discovery list operations.
-13. Upstream transport/discovery/session services.
+13. Complete: broker content access now prefers configured `StatefulMcpRuntime`
+    for resource and prompt reads, falling back to the one-shot adapter when no
+    stateful runtime is configured. Catalog refresh/discovery remains one-shot.
+14. Upstream transport/discovery/session services.
 
 Each slice should add import-direction tests so the new source-provider package
 does not depend on `wf_mcp.workflow_surface`, `wf_mcp.admin_surface`,