From 8a341de4b56cd70a6c9ce2b61c6bb76de599d1e3 Mon Sep 17 00:00:00 2001 From: archipelago Date: Fri, 7 Aug 2026 18:47:10 -0400 Subject: [PATCH] docs(api-reference): fix the one fabricated RPC method MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Verified all 144 documented RPC methods against the dispatcher. 143 are live; one was fabricated: `mesh.discover` (params { timeout_secs? }, returns { nodes: MeshNode[] }) does not exist — "mesh discovery" appears only in code comments as a concept, never as a method. A developer calling it gets "unknown method". Replaced with the real peer-listing method `mesh.peers` (no params, returns { peers, count }), which the frontend actually uses and which was undocumented. Also verified: every source path cited across the docs resolves (placeholders and a correctly-recorded deletion aside), and every documented app-manifest field exists in the schema (no fabricated fields). Co-Authored-By: Claude Opus 5 (1M context) --- docs/api-reference.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/api-reference.md b/docs/api-reference.md index b46b5522..b2657f1d 100644 --- a/docs/api-reference.md +++ b/docs/api-reference.md @@ -263,7 +263,7 @@ All endpoints use JSON-RPC over HTTP POST to `/rpc/v1`. | Method | Params | Returns | Auth | |--------|--------|---------|------| | `mesh.status` | — | `{ enabled: bool, device: string?, nodes: MeshNode[] }` | Yes | -| `mesh.discover` | `{ timeout_secs?: number }` | `{ nodes: MeshNode[] }` | Yes | +| `mesh.peers` | — | `{ peers: MeshPeer[], count: number }` | Yes | | `mesh.broadcast` | — | `{ ok: bool }` | Yes | | `mesh.configure` | `{ enabled: bool, device?: string }` | `{ ok: bool }` | Yes |