feat: expose source registry admin reads

docs/current_roadmap.md

@@ -130,10 +130,12 @@ implementation state.
       [2026-06-03 source registry next slices](./superpowers/plans/2026-06-03-source-registry-next-slices.md):
       desired-registry admin reads and safe mutation commands remain later
       slices.
-   - Next executable source registry slice:
-      [2026-06-04 source registry admin reads](./superpowers/plans/2026-06-04-source-registry-admin-reads.md).
-      It keeps desired registry state separate from observed source inventory
-      and adds read-only admin/RPC/CLI access before any mutation commands.
+   - Completed: desired-registry admin read plumbing is available through
+      `WorkflowSourceRegistryApi`, JSON-RPC methods
+      (`workflow.admin.source_registry.list` / `.inspect`), and CLI commands
+      (`wf admin registry list` / `wf admin registry inspect`). Local/static
+      servers report unavailable instead of empty; a concrete MCP-backed
+      `WorkflowServer` construction path remains future work. No mutations added.
    - Longer term: make the MCP frontend an adapter over these neutral workflow,
       source-admin, and config-admin surfaces so the old `wf_mcp` server entry
       point can shrink or retire.

docs/superpowers/plans/2026-06-03-source-registry-next-slices.md

@@ -59,9 +59,13 @@ The next executable slice is startup merge:
    - Emit events/diagnostics for shadowed registry entries.
 
 4. **Slice 4: Read Desired Registry Through Admin**
-   - **Status: planned.**
+   - **Status: complete.**
    - Expose desired registry entries separately from observed source inventory.
-   - Make the difference visible in API/CLI docs.
+   - `WorkflowSourceRegistryApi` provides neutral read-only access.
+   - JSON-RPC methods `workflow.admin.source_registry.list` / `.inspect`.
+   - CLI commands `wf admin registry list` / `wf admin registry inspect`.
+   - Local/static servers report unavailable instead of empty.
+   - Concrete MCP-backed `WorkflowServer` construction remains future work.
 
 5. **Slice 5: Mutation Commands**
    - Add add/update/enable/disable/remove operations.
@@ -323,8 +327,13 @@ with config-defined connections/sources.
 
 Expose desired registry entries distinctly from observed source inventory.
 
-Implementation plan:
-`docs/superpowers/plans/2026-06-04-source-registry-admin-reads.md`.
+Status: complete for API/transport/CLI plumbing. `WorkflowSourceRegistryApi`
+provides neutral read-only access. JSON-RPC methods
+`workflow.admin.source_registry.list` / `.inspect` are registered. CLI commands
+`wf admin registry list` / `wf admin registry inspect` are available for targets
+that expose the surface. Local/static servers report
+`source_registry_unavailable`. Concrete MCP-backed `WorkflowServer` construction
+remains future work.
 
 ### Why
 

docs/superpowers/specs/2026-06-03-store-backed-source-registry-design.md

@@ -269,12 +269,14 @@ registry entries.
 
 ### Slice 4: Read Registry Through Admin
 
-Implementation plan:
-[2026-06-04 source registry admin reads](../plans/2026-06-04-source-registry-admin-reads.md).
-
-- Add admin read method for desired registry entries if needed.
-- Keep current source inventory list as runtime/observed source inventory.
-- Document difference between desired registry and observed source catalog.
+Status: complete for API/transport/CLI plumbing. `WorkflowSourceRegistryApi`
+provides neutral read-only access to desired registry entries. JSON-RPC methods
+`workflow.admin.source_registry.list` and `.inspect` are registered. CLI commands
+`wf admin registry list` and `wf admin registry inspect` are available for
+targets that expose the surface. Local/static servers report
+`source_registry_unavailable` instead of pretending to have an empty registry.
+No mutations added. `wf source list` behavior remains unchanged. Concrete
+MCP-backed `WorkflowServer` construction remains future work.
 
 ### Slice 5: Mutating RPC/CLI