docs: record json rpc workflow transport

docs/current_roadmap.md

@@ -88,8 +88,11 @@ implementation state.
      JSON-RPC-over-HTTP first transport, remote CLI targeting, WebSocket/MCP
      transport siblings, source providers, auth, streaming/progress,
      transactional storage, and live upstream MCP sources.
-   - First slice implemented: `wf_server` can construct a local/static durable
-     `WorkflowApi` without `WfMcpService`. Transport adapters remain future work.
+    - First slice implemented: `wf_server` can construct a local/static durable
+      `WorkflowApi` without `WfMcpService`. Transport adapters remain future work.
+    - Completed: the first JSON-RPC-over-HTTP transport can expose the local/static
+      `WorkflowServer` through fixed dotted methods. Remote CLI targeting remains
+      the next transport-facing slice.
 
 5. **CLI/API alignment**
    - Let the CLI target either local process-backed stores/runtime or the future

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

@@ -275,6 +275,15 @@ composition:
 
 It should not implement source provider management yet.
 
+Implementation status:
+
+- `wf_transport_rpc_http.create_rpc_app(server)` exposes a fixed JSON-RPC
+  method set over an existing `wf_server.WorkflowServer`.
+- `wf-rpc-server --store-root <path>` starts the local/static server over
+  `/rpc`.
+- This slice still does not include remote `wf` CLI targeting, auth,
+  streaming/progress, or live upstream MCP source management.
+
 Preferred implementation dependency:
 
 ```bash