lda.chat/lda-wf
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: fix server CLI boundary status wording

Browse Source
This commit is contained in:
lda
2026-06-10 23:03:00 +07:00 Verified
parent 5c60ff5b9c
commit 3d2c78993f
1 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/superpowers/specs/2026-06-10-server-cli-transport-boundary.md
+6 -6
View File
@@ -13,9 +13,9 @@ Related:
## Purpose ## Purpose
`wf-rpc-server` currently lives in `wf_transport_rpc_http.cli`, but the module `wf-rpc-server` used to live in `wf_transport_rpc_http.cli`, but that module did
does more than transport work. It parses server startup config, selects local more than transport work. It parsed server startup config, selected local static
static vs MCP-backed composition, handles legacy `--mcp-config`, and starts the vs MCP-backed composition, handled legacy `--mcp-config`, and started the
JSON-RPC HTTP transport. JSON-RPC HTTP transport.
That made sense while JSON-RPC was the only long-lived server path. It is now That made sense while JSON-RPC was the only long-lived server path. It is now
@@ -40,15 +40,15 @@ wf_transport_rpc_http
The script name can remain `wf-rpc-server` for compatibility, but its entrypoint The script name can remain `wf-rpc-server` for compatibility, but its entrypoint
should eventually point at `wf_server.cli:main`. should eventually point at `wf_server.cli:main`.
## Current Shape ## Previous Shape
Current script registration: Previous script registration:
```toml ```toml
wf-rpc-server = "wf_transport_rpc_http.cli:main" wf-rpc-server = "wf_transport_rpc_http.cli:main"
``` ```
Current responsibilities inside `wf_transport_rpc_http.cli`: Previous responsibilities inside `wf_transport_rpc_http.cli`:
- parse `--config` - parse `--config`
- parse `--store-root` - parse `--store-root`