@litfamily/litgrok 1.0.32 → 1.0.34

package/.grok/skills/lsp-setup/references/bash/README.md

@@ -25,12 +25,23 @@ command -v shellcheck
 
 ## Server settings
 
-Grok Build documents no project language-server schema, and LitGrok ships no server
-configuration: the only documented code-intelligence surface is the built-in tool
-behind `GROK_LSP_TOOLS=1` / `[features] lsp_tools`, which is off by default (see the
-`lsp` skill). Installing the server binary on PATH is the whole setup this reference
-can vouch for. Do not add a server entry to `.grok/config.toml`; that key is not a
-documented Grok Build surface.
+Grok reads language servers from project `.grok/lsp.json` and from `~/.grok/lsp.json`. The project file wins when both name the same server. A trusted plugin may add a server; LitGrok does not ship one. The built-in tool stays off until `GROK_LSP_TOOLS=1` or user `[features] lsp_tools` (see the `lsp` skill).
+
+On Grok 1.0.13, `grok inspect --json` listed a server only for a string `command`, a string array `args`, and `extensionToLanguage`. This is the entry that loaded. Use this page's binary as `command` and put flags such as `--stdio` in `args`.
+
+```json
+{
+  "typescript": {
+    "command": "typescript-language-server",
+    "args": ["--stdio"],
+    "extensionToLanguage": { ".ts": "typescript" }
+  }
+}
+```
+
+The same inspect dropped a `command` that was itself an array, and it dropped a file whose only key was `lspServers`. Do not put the entry in `.grok/config.toml`.
+
+Grok's documentation names the two `lsp.json` paths and does not name these fields. Only that one shape was probed, for one TypeScript server. Other fields, a `command` with no `args`, and the plugin file format were not probed. Installing the binary on PATH is still required, and LitGrok still does not write `lsp.json`.
 
 ## Alternatives
 

package/.grok/skills/lsp-setup/references/c-cpp/README.md

@@ -20,12 +20,23 @@ command -v clangd
 
 ## Server settings
 
-Grok Build documents no project language-server schema, and LitGrok ships no server
-configuration: the only documented code-intelligence surface is the built-in tool
-behind `GROK_LSP_TOOLS=1` / `[features] lsp_tools`, which is off by default (see the
-`lsp` skill). Installing the server binary on PATH is the whole setup this reference
-can vouch for. Do not add a server entry to `.grok/config.toml`; that key is not a
-documented Grok Build surface.
+Grok reads language servers from project `.grok/lsp.json` and from `~/.grok/lsp.json`. The project file wins when both name the same server. A trusted plugin may add a server; LitGrok does not ship one. The built-in tool stays off until `GROK_LSP_TOOLS=1` or user `[features] lsp_tools` (see the `lsp` skill).
+
+On Grok 1.0.13, `grok inspect --json` listed a server only for a string `command`, a string array `args`, and `extensionToLanguage`. This is the entry that loaded. Use this page's binary as `command` and put flags such as `--stdio` in `args`.
+
+```json
+{
+  "typescript": {
+    "command": "typescript-language-server",
+    "args": ["--stdio"],
+    "extensionToLanguage": { ".ts": "typescript" }
+  }
+}
+```
+
+The same inspect dropped a `command` that was itself an array, and it dropped a file whose only key was `lspServers`. Do not put the entry in `.grok/config.toml`.
+
+Grok's documentation names the two `lsp.json` paths and does not name these fields. Only that one shape was probed, for one TypeScript server. Other fields, a `command` with no `args`, and the plugin file format were not probed. Installing the binary on PATH is still required, and LitGrok still does not write `lsp.json`.
 
 ## Compile commands
 

package/.grok/skills/lsp-setup/references/csharp/README.md

@@ -22,12 +22,23 @@ command -v csharp-ls
 
 ## Server settings
 
-Grok Build documents no project language-server schema, and LitGrok ships no server
-configuration: the only documented code-intelligence surface is the built-in tool
-behind `GROK_LSP_TOOLS=1` / `[features] lsp_tools`, which is off by default (see the
-`lsp` skill). Installing the server binary on PATH is the whole setup this reference
-can vouch for. Do not add a server entry to `.grok/config.toml`; that key is not a
-documented Grok Build surface.
+Grok reads language servers from project `.grok/lsp.json` and from `~/.grok/lsp.json`. The project file wins when both name the same server. A trusted plugin may add a server; LitGrok does not ship one. The built-in tool stays off until `GROK_LSP_TOOLS=1` or user `[features] lsp_tools` (see the `lsp` skill).
+
+On Grok 1.0.13, `grok inspect --json` listed a server only for a string `command`, a string array `args`, and `extensionToLanguage`. This is the entry that loaded. Use this page's binary as `command` and put flags such as `--stdio` in `args`.
+
+```json
+{
+  "typescript": {
+    "command": "typescript-language-server",
+    "args": ["--stdio"],
+    "extensionToLanguage": { ".ts": "typescript" }
+  }
+}
+```
+
+The same inspect dropped a `command` that was itself an array, and it dropped a file whose only key was `lspServers`. Do not put the entry in `.grok/config.toml`.
+
+Grok's documentation names the two `lsp.json` paths and does not name these fields. Only that one shape was probed, for one TypeScript server. Other fields, a `command` with no `args`, and the plugin file format were not probed. Installing the binary on PATH is still required, and LitGrok still does not write `lsp.json`.
 
 ## Razor / Blazor
 

package/.grok/skills/lsp-setup/references/dart/README.md

@@ -20,12 +20,23 @@ command -v dart
 
 ## Server settings
 
-Grok Build documents no project language-server schema, and LitGrok ships no server
-configuration: the only documented code-intelligence surface is the built-in tool
-behind `GROK_LSP_TOOLS=1` / `[features] lsp_tools`, which is off by default (see the
-`lsp` skill). Installing the server binary on PATH is the whole setup this reference
-can vouch for. Do not add a server entry to `.grok/config.toml`; that key is not a
-documented Grok Build surface.
+Grok reads language servers from project `.grok/lsp.json` and from `~/.grok/lsp.json`. The project file wins when both name the same server. A trusted plugin may add a server; LitGrok does not ship one. The built-in tool stays off until `GROK_LSP_TOOLS=1` or user `[features] lsp_tools` (see the `lsp` skill).
+
+On Grok 1.0.13, `grok inspect --json` listed a server only for a string `command`, a string array `args`, and `extensionToLanguage`. This is the entry that loaded. Use this page's binary as `command` and put flags such as `--stdio` in `args`.
+
+```json
+{
+  "typescript": {
+    "command": "typescript-language-server",
+    "args": ["--stdio"],
+    "extensionToLanguage": { ".ts": "typescript" }
+  }
+}
+```
+
+The same inspect dropped a `command` that was itself an array, and it dropped a file whose only key was `lspServers`. Do not put the entry in `.grok/config.toml`.
+
+Grok's documentation names the two `lsp.json` paths and does not name these fields. Only that one shape was probed, for one TypeScript server. Other fields, a `command` with no `args`, and the plugin file format were not probed. Installing the binary on PATH is still required, and LitGrok still does not write `lsp.json`.
 
 ## Alternatives
 

package/.grok/skills/lsp-setup/references/elixir/README.md

@@ -21,12 +21,23 @@ command -v elixir-ls
 
 ## Server settings
 
-Grok Build documents no project language-server schema, and LitGrok ships no server
-configuration: the only documented code-intelligence surface is the built-in tool
-behind `GROK_LSP_TOOLS=1` / `[features] lsp_tools`, which is off by default (see the
-`lsp` skill). Installing the server binary on PATH is the whole setup this reference
-can vouch for. Do not add a server entry to `.grok/config.toml`; that key is not a
-documented Grok Build surface.
+Grok reads language servers from project `.grok/lsp.json` and from `~/.grok/lsp.json`. The project file wins when both name the same server. A trusted plugin may add a server; LitGrok does not ship one. The built-in tool stays off until `GROK_LSP_TOOLS=1` or user `[features] lsp_tools` (see the `lsp` skill).
+
+On Grok 1.0.13, `grok inspect --json` listed a server only for a string `command`, a string array `args`, and `extensionToLanguage`. This is the entry that loaded. Use this page's binary as `command` and put flags such as `--stdio` in `args`.
+
+```json
+{
+  "typescript": {
+    "command": "typescript-language-server",
+    "args": ["--stdio"],
+    "extensionToLanguage": { ".ts": "typescript" }
+  }
+}
+```
+
+The same inspect dropped a `command` that was itself an array, and it dropped a file whose only key was `lspServers`. Do not put the entry in `.grok/config.toml`.
+
+Grok's documentation names the two `lsp.json` paths and does not name these fields. Only that one shape was probed, for one TypeScript server. Other fields, a `command` with no `args`, and the plugin file format were not probed. Installing the binary on PATH is still required, and LitGrok still does not write `lsp.json`.
 
 ## Alternatives
 

package/.grok/skills/lsp-setup/references/go/README.md

@@ -25,12 +25,23 @@ command -v gopls
 
 ## Server settings
 
-Grok Build documents no project language-server schema, and LitGrok ships no server
-configuration: the only documented code-intelligence surface is the built-in tool
-behind `GROK_LSP_TOOLS=1` / `[features] lsp_tools`, which is off by default (see the
-`lsp` skill). Installing the server binary on PATH is the whole setup this reference
-can vouch for. Do not add a server entry to `.grok/config.toml`; that key is not a
-documented Grok Build surface.
+Grok reads language servers from project `.grok/lsp.json` and from `~/.grok/lsp.json`. The project file wins when both name the same server. A trusted plugin may add a server; LitGrok does not ship one. The built-in tool stays off until `GROK_LSP_TOOLS=1` or user `[features] lsp_tools` (see the `lsp` skill).
+
+On Grok 1.0.13, `grok inspect --json` listed a server only for a string `command`, a string array `args`, and `extensionToLanguage`. This is the entry that loaded. Use this page's binary as `command` and put flags such as `--stdio` in `args`.
+
+```json
+{
+  "typescript": {
+    "command": "typescript-language-server",
+    "args": ["--stdio"],
+    "extensionToLanguage": { ".ts": "typescript" }
+  }
+}
+```
+
+The same inspect dropped a `command` that was itself an array, and it dropped a file whose only key was `lspServers`. Do not put the entry in `.grok/config.toml`.
+
+Grok's documentation names the two `lsp.json` paths and does not name these fields. Only that one shape was probed, for one TypeScript server. Other fields, a `command` with no `args`, and the plugin file format were not probed. Installing the binary on PATH is still required, and LitGrok still does not write `lsp.json`.
 
 ## Alternatives
 

package/.grok/skills/lsp-setup/references/haskell/README.md

@@ -27,12 +27,23 @@ command -v haskell-language-server-wrapper
 
 ## Server settings
 
-Grok Build documents no project language-server schema, and LitGrok ships no server
-configuration: the only documented code-intelligence surface is the built-in tool
-behind `GROK_LSP_TOOLS=1` / `[features] lsp_tools`, which is off by default (see the
-`lsp` skill). Installing the server binary on PATH is the whole setup this reference
-can vouch for. Do not add a server entry to `.grok/config.toml`; that key is not a
-documented Grok Build surface.
+Grok reads language servers from project `.grok/lsp.json` and from `~/.grok/lsp.json`. The project file wins when both name the same server. A trusted plugin may add a server; LitGrok does not ship one. The built-in tool stays off until `GROK_LSP_TOOLS=1` or user `[features] lsp_tools` (see the `lsp` skill).
+
+On Grok 1.0.13, `grok inspect --json` listed a server only for a string `command`, a string array `args`, and `extensionToLanguage`. This is the entry that loaded. Use this page's binary as `command` and put flags such as `--stdio` in `args`.
+
+```json
+{
+  "typescript": {
+    "command": "typescript-language-server",
+    "args": ["--stdio"],
+    "extensionToLanguage": { ".ts": "typescript" }
+  }
+}
+```
+
+The same inspect dropped a `command` that was itself an array, and it dropped a file whose only key was `lspServers`. Do not put the entry in `.grok/config.toml`.
+
+Grok's documentation names the two `lsp.json` paths and does not name these fields. Only that one shape was probed, for one TypeScript server. Other fields, a `command` with no `args`, and the plugin file format were not probed. Installing the binary on PATH is still required, and LitGrok still does not write `lsp.json`.
 
 ## Alternatives
 

package/.grok/skills/lsp-setup/references/java/README.md

@@ -20,12 +20,23 @@ command -v jdtls
 
 ## Server settings
 
-Grok Build documents no project language-server schema, and LitGrok ships no server
-configuration: the only documented code-intelligence surface is the built-in tool
-behind `GROK_LSP_TOOLS=1` / `[features] lsp_tools`, which is off by default (see the
-`lsp` skill). Installing the server binary on PATH is the whole setup this reference
-can vouch for. Do not add a server entry to `.grok/config.toml`; that key is not a
-documented Grok Build surface.
+Grok reads language servers from project `.grok/lsp.json` and from `~/.grok/lsp.json`. The project file wins when both name the same server. A trusted plugin may add a server; LitGrok does not ship one. The built-in tool stays off until `GROK_LSP_TOOLS=1` or user `[features] lsp_tools` (see the `lsp` skill).
+
+On Grok 1.0.13, `grok inspect --json` listed a server only for a string `command`, a string array `args`, and `extensionToLanguage`. This is the entry that loaded. Use this page's binary as `command` and put flags such as `--stdio` in `args`.
+
+```json
+{
+  "typescript": {
+    "command": "typescript-language-server",
+    "args": ["--stdio"],
+    "extensionToLanguage": { ".ts": "typescript" }
+  }
+}
+```
+
+The same inspect dropped a `command` that was itself an array, and it dropped a file whose only key was `lspServers`. Do not put the entry in `.grok/config.toml`.
+
+Grok's documentation names the two `lsp.json` paths and does not name these fields. Only that one shape was probed, for one TypeScript server. Other fields, a `command` with no `args`, and the plugin file format were not probed. Installing the binary on PATH is still required, and LitGrok still does not write `lsp.json`.
 
 Most settings (runtimes, format, import order) come from `settings.java.*`
 defaults and work for Maven/Gradle projects with a standard layout.

package/.grok/skills/lsp-setup/references/julia/README.md

@@ -28,12 +28,23 @@ command -v julia
 
 ## Server settings
 
-Grok Build documents no project language-server schema, and LitGrok ships no server
-configuration: the only documented code-intelligence surface is the built-in tool
-behind `GROK_LSP_TOOLS=1` / `[features] lsp_tools`, which is off by default (see the
-`lsp` skill). Installing the server binary on PATH is the whole setup this reference
-can vouch for. Do not add a server entry to `.grok/config.toml`; that key is not a
-documented Grok Build surface.
+Grok reads language servers from project `.grok/lsp.json` and from `~/.grok/lsp.json`. The project file wins when both name the same server. A trusted plugin may add a server; LitGrok does not ship one. The built-in tool stays off until `GROK_LSP_TOOLS=1` or user `[features] lsp_tools` (see the `lsp` skill).
+
+On Grok 1.0.13, `grok inspect --json` listed a server only for a string `command`, a string array `args`, and `extensionToLanguage`. This is the entry that loaded. Use this page's binary as `command` and put flags such as `--stdio` in `args`.
+
+```json
+{
+  "typescript": {
+    "command": "typescript-language-server",
+    "args": ["--stdio"],
+    "extensionToLanguage": { ".ts": "typescript" }
+  }
+}
+```
+
+The same inspect dropped a `command` that was itself an array, and it dropped a file whose only key was `lspServers`. Do not put the entry in `.grok/config.toml`.
+
+Grok's documentation names the two `lsp.json` paths and does not name these fields. Only that one shape was probed, for one TypeScript server. Other fields, a `command` with no `args`, and the plugin file format were not probed. Installing the binary on PATH is still required, and LitGrok still does not write `lsp.json`.
 
 ## Alternatives
 

package/.grok/skills/lsp-setup/references/kotlin/README.md

@@ -22,12 +22,23 @@ command -v kotlin-lsp
 
 ## Server settings
 
-Grok Build documents no project language-server schema, and LitGrok ships no server
-configuration: the only documented code-intelligence surface is the built-in tool
-behind `GROK_LSP_TOOLS=1` / `[features] lsp_tools`, which is off by default (see the
-`lsp` skill). Installing the server binary on PATH is the whole setup this reference
-can vouch for. Do not add a server entry to `.grok/config.toml`; that key is not a
-documented Grok Build surface.
+Grok reads language servers from project `.grok/lsp.json` and from `~/.grok/lsp.json`. The project file wins when both name the same server. A trusted plugin may add a server; LitGrok does not ship one. The built-in tool stays off until `GROK_LSP_TOOLS=1` or user `[features] lsp_tools` (see the `lsp` skill).
+
+On Grok 1.0.13, `grok inspect --json` listed a server only for a string `command`, a string array `args`, and `extensionToLanguage`. This is the entry that loaded. Use this page's binary as `command` and put flags such as `--stdio` in `args`.
+
+```json
+{
+  "typescript": {
+    "command": "typescript-language-server",
+    "args": ["--stdio"],
+    "extensionToLanguage": { ".ts": "typescript" }
+  }
+}
+```
+
+The same inspect dropped a `command` that was itself an array, and it dropped a file whose only key was `lspServers`. Do not put the entry in `.grok/config.toml`.
+
+Grok's documentation names the two `lsp.json` paths and does not name these fields. Only that one shape was probed, for one TypeScript server. Other fields, a `command` with no `args`, and the plugin file format were not probed. Installing the binary on PATH is still required, and LitGrok still does not write `lsp.json`.
 
 The server resolves classpath from Gradle/Maven; keep the build descriptor
 importable.

package/.grok/skills/lsp-setup/references/lua/README.md

@@ -20,12 +20,23 @@ command -v lua-language-server
 
 ## Server settings
 
-Grok Build documents no project language-server schema, and LitGrok ships no server
-configuration: the only documented code-intelligence surface is the built-in tool
-behind `GROK_LSP_TOOLS=1` / `[features] lsp_tools`, which is off by default (see the
-`lsp` skill). Installing the server binary on PATH is the whole setup this reference
-can vouch for. Do not add a server entry to `.grok/config.toml`; that key is not a
-documented Grok Build surface.
+Grok reads language servers from project `.grok/lsp.json` and from `~/.grok/lsp.json`. The project file wins when both name the same server. A trusted plugin may add a server; LitGrok does not ship one. The built-in tool stays off until `GROK_LSP_TOOLS=1` or user `[features] lsp_tools` (see the `lsp` skill).
+
+On Grok 1.0.13, `grok inspect --json` listed a server only for a string `command`, a string array `args`, and `extensionToLanguage`. This is the entry that loaded. Use this page's binary as `command` and put flags such as `--stdio` in `args`.
+
+```json
+{
+  "typescript": {
+    "command": "typescript-language-server",
+    "args": ["--stdio"],
+    "extensionToLanguage": { ".ts": "typescript" }
+  }
+}
+```
+
+The same inspect dropped a `command` that was itself an array, and it dropped a file whose only key was `lspServers`. Do not put the entry in `.grok/config.toml`.
+
+Grok's documentation names the two `lsp.json` paths and does not name these fields. Only that one shape was probed, for one TypeScript server. Other fields, a `command` with no `args`, and the plugin file format were not probed. Installing the binary on PATH is still required, and LitGrok still does not write `lsp.json`.
 
 ## Alternatives
 

package/.grok/skills/lsp-setup/references/php/README.md

@@ -20,12 +20,23 @@ command -v intelephense
 
 ## Server settings
 
-Grok Build documents no project language-server schema, and LitGrok ships no server
-configuration: the only documented code-intelligence surface is the built-in tool
-behind `GROK_LSP_TOOLS=1` / `[features] lsp_tools`, which is off by default (see the
-`lsp` skill). Installing the server binary on PATH is the whole setup this reference
-can vouch for. Do not add a server entry to `.grok/config.toml`; that key is not a
-documented Grok Build surface.
+Grok reads language servers from project `.grok/lsp.json` and from `~/.grok/lsp.json`. The project file wins when both name the same server. A trusted plugin may add a server; LitGrok does not ship one. The built-in tool stays off until `GROK_LSP_TOOLS=1` or user `[features] lsp_tools` (see the `lsp` skill).
+
+On Grok 1.0.13, `grok inspect --json` listed a server only for a string `command`, a string array `args`, and `extensionToLanguage`. This is the entry that loaded. Use this page's binary as `command` and put flags such as `--stdio` in `args`.
+
+```json
+{
+  "typescript": {
+    "command": "typescript-language-server",
+    "args": ["--stdio"],
+    "extensionToLanguage": { ".ts": "typescript" }
+  }
+}
+```
+
+The same inspect dropped a `command` that was itself an array, and it dropped a file whose only key was `lspServers`. Do not put the entry in `.grok/config.toml`.
+
+Grok's documentation names the two `lsp.json` paths and does not name these fields. Only that one shape was probed, for one TypeScript server. Other fields, a `command` with no `args`, and the plugin file format were not probed. Installing the binary on PATH is still required, and LitGrok still does not write `lsp.json`.
 
 ## Alternatives
 

package/.grok/skills/lsp-setup/references/python/README.md

@@ -21,24 +21,35 @@ command -v basedpyright-langserver
 
 ## Server settings
 
-Grok Build documents no project language-server schema, and LitGrok ships no server
-configuration: the only documented code-intelligence surface is the built-in tool
-behind `GROK_LSP_TOOLS=1` / `[features] lsp_tools`, which is off by default (see the
-`lsp` skill). Installing the server binary on PATH is the whole setup this reference
-can vouch for. Do not add a server entry to `.grok/config.toml`; that key is not a
-documented Grok Build surface.
+Grok reads language servers from project `.grok/lsp.json` and from `~/.grok/lsp.json`. The project file wins when both name the same server. A trusted plugin may add a server; LitGrok does not ship one. The built-in tool stays off until `GROK_LSP_TOOLS=1` or user `[features] lsp_tools` (see the `lsp` skill).
+
+On Grok 1.0.13, `grok inspect --json` listed a server only for a string `command`, a string array `args`, and `extensionToLanguage`. This is the entry that loaded. Use this page's binary as `command` and put flags such as `--stdio` in `args`.
+
+```json
+{
+  "typescript": {
+    "command": "typescript-language-server",
+    "args": ["--stdio"],
+    "extensionToLanguage": { ".ts": "typescript" }
+  }
+}
+```
+
+The same inspect dropped a `command` that was itself an array, and it dropped a file whose only key was `lspServers`. Do not put the entry in `.grok/config.toml`.
+
+Grok's documentation names the two `lsp.json` paths and does not name these fields. Only that one shape was probed, for one TypeScript server. Other fields, a `command` with no `args`, and the plugin file format were not probed. Installing the binary on PATH is still required, and LitGrok still does not write `lsp.json`.
 
 ## Choosing a server
 
 Type checkers and the linter serve different roles. Run a type server, and
-optionally `ruff` ALONGSIDE it (not instead). Launch the server accordingly:
-
-| server launch                        | install                | role                                    |
-| ------------------------------------ | ---------------------- | --------------------------------------- |
-| `["basedpyright-langserver", "--stdio"]` | `pip install basedpyright` | strictest types, **default**       |
-| `["pyright-langserver", "--stdio"]`  | `pip install pyright`  | upstream Microsoft type checker         |
-| `["ty", "server"]`                   | `pip install ty`       | Astral, very fast, pre-1.0/experimental |
-| `["ruff", "server"]`                 | `pip install ruff`     | lint + format only, complements a type server |
+optionally `ruff` ALONGSIDE it (not instead). The first column is the string `command` and the second is `args`; do not paste a launch as a JSON array into `command`:
+
+| command | args | install | role |
+| --- | --- | --- | --- |
+| `basedpyright-langserver` | `--stdio` | `pip install basedpyright` | strictest types, **default** |
+| `pyright-langserver` | `--stdio` | `pip install pyright` | upstream Microsoft type checker |
+| `ty` | `server` | `pip install ty` | Astral, very fast, pre-1.0/experimental |
+| `ruff` | `server` | `pip install ruff` | lint + format only, complements a type server |
 
 Recommended: keep `basedpyright` as the Python server. `ruff` does not
 type-check, so if you want lint diagnostics too run it as a separate tool rather

package/.grok/skills/lsp-setup/references/ruby/README.md

@@ -22,12 +22,23 @@ command -v rubocop
 
 ## Server settings
 
-Grok Build documents no project language-server schema, and LitGrok ships no server
-configuration: the only documented code-intelligence surface is the built-in tool
-behind `GROK_LSP_TOOLS=1` / `[features] lsp_tools`, which is off by default (see the
-`lsp` skill). Installing the server binary on PATH is the whole setup this reference
-can vouch for. Do not add a server entry to `.grok/config.toml`; that key is not a
-documented Grok Build surface.
+Grok reads language servers from project `.grok/lsp.json` and from `~/.grok/lsp.json`. The project file wins when both name the same server. A trusted plugin may add a server; LitGrok does not ship one. The built-in tool stays off until `GROK_LSP_TOOLS=1` or user `[features] lsp_tools` (see the `lsp` skill).
+
+On Grok 1.0.13, `grok inspect --json` listed a server only for a string `command`, a string array `args`, and `extensionToLanguage`. This is the entry that loaded. Use this page's binary as `command` and put flags such as `--stdio` in `args`.
+
+```json
+{
+  "typescript": {
+    "command": "typescript-language-server",
+    "args": ["--stdio"],
+    "extensionToLanguage": { ".ts": "typescript" }
+  }
+}
+```
+
+The same inspect dropped a `command` that was itself an array, and it dropped a file whose only key was `lspServers`. Do not put the entry in `.grok/config.toml`.
+
+Grok's documentation names the two `lsp.json` paths and does not name these fields. Only that one shape was probed, for one TypeScript server. Other fields, a `command` with no `args`, and the plugin file format were not probed. Installing the binary on PATH is still required, and LitGrok still does not write `lsp.json`.
 
 ## Alternatives
 

package/.grok/skills/lsp-setup/references/rust/README.md

@@ -22,12 +22,23 @@ command -v rust-analyzer
 
 ## Server settings
 
-Grok Build documents no project language-server schema, and LitGrok ships no server
-configuration: the only documented code-intelligence surface is the built-in tool
-behind `GROK_LSP_TOOLS=1` / `[features] lsp_tools`, which is off by default (see the
-`lsp` skill). Installing the server binary on PATH is the whole setup this reference
-can vouch for. Do not add a server entry to `.grok/config.toml`; that key is not a
-documented Grok Build surface.
+Grok reads language servers from project `.grok/lsp.json` and from `~/.grok/lsp.json`. The project file wins when both name the same server. A trusted plugin may add a server; LitGrok does not ship one. The built-in tool stays off until `GROK_LSP_TOOLS=1` or user `[features] lsp_tools` (see the `lsp` skill).
+
+On Grok 1.0.13, `grok inspect --json` listed a server only for a string `command`, a string array `args`, and `extensionToLanguage`. This is the entry that loaded. Use this page's binary as `command` and put flags such as `--stdio` in `args`.
+
+```json
+{
+  "typescript": {
+    "command": "typescript-language-server",
+    "args": ["--stdio"],
+    "extensionToLanguage": { ".ts": "typescript" }
+  }
+}
+```
+
+The same inspect dropped a `command` that was itself an array, and it dropped a file whose only key was `lspServers`. Do not put the entry in `.grok/config.toml`.
+
+Grok's documentation names the two `lsp.json` paths and does not name these fields. Only that one shape was probed, for one TypeScript server. Other fields, a `command` with no `args`, and the plugin file format were not probed. Installing the binary on PATH is still required, and LitGrok still does not write `lsp.json`.
 
 ## Alternatives
 

package/.grok/skills/lsp-setup/references/swift/README.md

@@ -20,12 +20,23 @@ command -v sourcekit-lsp
 
 ## Server settings
 
-Grok Build documents no project language-server schema, and LitGrok ships no server
-configuration: the only documented code-intelligence surface is the built-in tool
-behind `GROK_LSP_TOOLS=1` / `[features] lsp_tools`, which is off by default (see the
-`lsp` skill). Installing the server binary on PATH is the whole setup this reference
-can vouch for. Do not add a server entry to `.grok/config.toml`; that key is not a
-documented Grok Build surface.
+Grok reads language servers from project `.grok/lsp.json` and from `~/.grok/lsp.json`. The project file wins when both name the same server. A trusted plugin may add a server; LitGrok does not ship one. The built-in tool stays off until `GROK_LSP_TOOLS=1` or user `[features] lsp_tools` (see the `lsp` skill).
+
+On Grok 1.0.13, `grok inspect --json` listed a server only for a string `command`, a string array `args`, and `extensionToLanguage`. This is the entry that loaded. Use this page's binary as `command` and put flags such as `--stdio` in `args`.
+
+```json
+{
+  "typescript": {
+    "command": "typescript-language-server",
+    "args": ["--stdio"],
+    "extensionToLanguage": { ".ts": "typescript" }
+  }
+}
+```
+
+The same inspect dropped a `command` that was itself an array, and it dropped a file whose only key was `lspServers`. Do not put the entry in `.grok/config.toml`.
+
+Grok's documentation names the two `lsp.json` paths and does not name these fields. Only that one shape was probed, for one TypeScript server. Other fields, a `command` with no `args`, and the plugin file format were not probed. Installing the binary on PATH is still required, and LitGrok still does not write `lsp.json`.
 
 ## Alternatives
 

package/.grok/skills/lsp-setup/references/terraform/README.md

@@ -21,12 +21,23 @@ command -v terraform
 
 ## Server settings
 
-Grok Build documents no project language-server schema, and LitGrok ships no server
-configuration: the only documented code-intelligence surface is the built-in tool
-behind `GROK_LSP_TOOLS=1` / `[features] lsp_tools`, which is off by default (see the
-`lsp` skill). Installing the server binary on PATH is the whole setup this reference
-can vouch for. Do not add a server entry to `.grok/config.toml`; that key is not a
-documented Grok Build surface.
+Grok reads language servers from project `.grok/lsp.json` and from `~/.grok/lsp.json`. The project file wins when both name the same server. A trusted plugin may add a server; LitGrok does not ship one. The built-in tool stays off until `GROK_LSP_TOOLS=1` or user `[features] lsp_tools` (see the `lsp` skill).
+
+On Grok 1.0.13, `grok inspect --json` listed a server only for a string `command`, a string array `args`, and `extensionToLanguage`. This is the entry that loaded. Use this page's binary as `command` and put flags such as `--stdio` in `args`.
+
+```json
+{
+  "typescript": {
+    "command": "typescript-language-server",
+    "args": ["--stdio"],
+    "extensionToLanguage": { ".ts": "typescript" }
+  }
+}
+```
+
+The same inspect dropped a `command` that was itself an array, and it dropped a file whose only key was `lspServers`. Do not put the entry in `.grok/config.toml`.
+
+Grok's documentation names the two `lsp.json` paths and does not name these fields. Only that one shape was probed, for one TypeScript server. Other fields, a `command` with no `args`, and the plugin file format were not probed. Installing the binary on PATH is still required, and LitGrok still does not write `lsp.json`.
 
 ## Alternatives