feat: add remote workflow lifecycle rpc methods

docs/current_roadmap.md

@@ -94,9 +94,9 @@ implementation state.
       `WorkflowServer` through fixed dotted methods. Remote CLI targeting remains
       the next transport-facing slice.
    - Completed: workflow config now distinguishes client targets from server
-      hosting config, selected `wf cap`/`wf run` commands can target JSON-RPC
-      HTTP with explicit CLI overrides, and local-only draft/artifact/deploy
-      commands fail fast for remote targets until they are wired.
+      hosting config, the basic `wf` lifecycle can target JSON-RPC HTTP:
+      capability discovery, draft workspace authoring, artifact/deployment
+      operations, run, inspect, and bounded trace.
 
 5. **CLI/API alignment**
    - Let the CLI target either local process-backed stores/runtime or the future

docs/superpowers/specs/2026-06-03-workflow-config-targets-and-sources.md

@@ -462,8 +462,9 @@ First slice implemented:
   wired source ids (`wf.std`, `wf.recipes`)
 - local and JSON-RPC client targets
 - `wf` root overrides for `--local`, `--url`, and `--timeout`
-- remote JSON-RPC client support for capability and run CLI commands
-- local-only CLI commands fail fast for `rpc_http` targets until they are wired
+- remote JSON-RPC client support now covers capability, draft workspace,
+  artifact, deployment, and run CLI commands
+- draft/artifact/deploy commands no longer fail fast for `rpc_http` targets
 - `wf-rpc-server --config` support for server store and RPC HTTP transport,
   including configured RPC path
 
@@ -473,7 +474,6 @@ Still future:
 - MCP/OpenAPI source config
 - arbitrary stdlib source aliases
 - `/mcp` hosting from neutral server config
-- remote draft/artifact/deployment CLI commands
 - auth and SQL stores
 
 ## Next Implementation Slice