WebSocket: search.start is documented but not implemented

[digizeph]

Problem

src/server/README.md lists search.start / search.cancel as implemented, but they aren't registered in the router. Calling them over /ws returns:

{"type":"error","data":{"code":"UNKNOWN_METHOD","message":"Unknown method: search.start"}}

Confirmed on bgpkit/monocle:1.3.0 and main (487a765). src/server/mod.rs registers no search/parse handlers, and src/server/query.rs marks them as "future".

Why it matters

search is the main reason to use the WS server (streaming on-demand MRT search). Without it, only DB/lookup methods are available.

Note

The search logic already exists — src/lens/search has SearchLens::search_with_progress(...) with progress callbacks and an element handler, which is what a streaming search.start handler would wrap.

Ask

• Implement and register search.start / search.cancel (reusing SearchLens::search_with_progress).
• Fix the README's "Implemented Methods" table to match reality. parse.start, system.methods, and inspect.search are also listed but not registered.