## Problem The VSCode extension hard-wires the analysis call. Neovim/Helix/Zed/JetBrains users get nothing. ## Acceptance Criteria - [ ] New binary or `sanctifier lsp` subcommand speaking LSP over stdio - [ ] Diagnostics for findings, code-actions for `sanctifier fix` suggestions - [ ] Smoke test with `vscode-test-cli` and Neovim's built-in LSP client - [ ] Doc page in `docs/` ## Pointers - Crate `tower-lsp` is a common choice - `vscode-extension/` for parity
Problem
The VSCode extension hard-wires the analysis call. Neovim/Helix/Zed/JetBrains users get nothing.
Acceptance Criteria
sanctifier lspsubcommand speaking LSP over stdiosanctifier fixsuggestionsvscode-test-cliand Neovim's built-in LSP clientdocs/Pointers
tower-lspis a common choicevscode-extension/for parity