lsp-health-checklisted

# LSP Health Check ## Purpose Verify that language servers and project prerequisites are available before relying on diagnostics, semantic navigation, or Serena symbol tools. ## Command Run from a repository root: ```bash bash ${CLAUDE_PLUGIN_ROOT}/scripts/check_lsps.sh ``` For another project: ```bash bash ${CLAUDE_PLUGIN_ROOT}/scripts/check_lsps.sh /path/to/project ``` ## Workflow 1. Run the health-check script when available. 2. If the script is not available in the current environment, check commands manually using stable executable names from `${CLAUDE_PLUGIN_ROOT}/references/lsp-server-matrix.md`. 3. Report missing commands separately from project prerequisite warnings. 4. Do not start raw `stdio` LSP sessions as a test - they hang waiting for a real LSP client. 5. For C, C++, and Qt C++, treat missing `compile_commands.json` as a serious warning because diagnostics may be wrong. 6. For TypeScript and JavaScript, verify `tsconfig.json` or `jsconfig.json`. 7. For Python, verify `pyproject.toml`, `pyrightconfig.json`, or virtual environment expectations. 8. For Dart and Flutter, verify `pubspec.yaml`, `analysis_options.yaml`, and dependency resolution. ## Output In Russian, summarize: - Installed and missing commands. - Project prerequisite warnings. - What must be installed or configured next. - Whether Serena semantic work is safe for the detected languages. ## Anti-patterns - Запускать `pyright-langserver --stdio` без LSP-клиента (зависает). - Игнорироват