Zig files go to zls as a child process through the protocol client, as every other language does: the in-process ZLS backend goes

lsp_zls.zig (1,522 lines), the zls dependency, build.zig's zls wiring and the import graph it baked into the options only for it, and main.zig's reference go. lsp_client's table gains a zls row (PARDES_LSP_ZIG overrides it); Hover, Rename, Diagnostics, WsSymbols, Lspinfo and gd answer through it (checked with lspprobe and the snapshots against zls 0.16.1-dev). What changes for a user: zls must be on PATH; a completion's rows are zls's candidates at the cursor, where the linked analyser gave each one's declaration; document symbols carry no signature. The Zig snapshots (lsp, lspcomplete, lspcompletemoved, lspdebug, lsprelpath) run the real zls now: lspdebug reads the client's explain and report, lsprelpath spells gr's rows where it spelled a completion's, and their goldens are recorded again (stable over three runs). Lspinfo still opens with its backend line. The ReleaseFast tty binary is 105.35 MB to 96.28 MB, the Debug one 296.5 MB to 245.9 MB. docs/lsp.md, web.md, design.typ and the README say so.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

1 files changed, 2 insertions, 2 deletions

diff --git a/docs/web.md b/docs/web.md
index bbbed8a3..0a9783c9 100644
--- a/docs/web.md
+++ b/docs/web.md
@@ -80,7 +80,7 @@ What is genuinely absent is narrower than "no IO". The module has no threads
 and no host filesystem, so there is no startup config directory, init file,
 ThemeFile, or DumpThemes; LOOK resolves
 against the build-generated source archive rather than disk, and no language
-BACKEND is compiled in (`zls_backend` is off for wasm — which also means
+BACKEND is compiled in (there is none for wasm — which also means
 `lsp.supports` is empty, so the core never even raises a language query there,
 and the host leaves `lsp` null).
 
@@ -114,7 +114,7 @@ land in the per-instance fallback, so a pane with no child is SILENT rather
 than synthetic; `tty_taken` is never taken; any save the page declines resolves
 against the core's virtual filesystem, which is also where every read comes
 from — the core reads files itself and never asks a host; `watch_file` records
-the request; `lsp` answers an empty row set at once (`zls_backend` is off for
+the request; `lsp` answers an empty row set at once (no backend is built for
 wasm, so the core never raises a query there anyway) and `pipe` answers
 failure; `wait_input` is null because wasm must never block, and `watch_theme`
 and `dump_themes` are not reachable without a config directory. Of the