@litfamily/litgrok 1.0.32 → 1.0.33

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
 

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

@@ -2,17 +2,18 @@
 
 - **Recommended server:** `typescript-language-server --stdio`
 - **Extensions:** `.ts .tsx .js .jsx .mjs .cjs .mts .cts`
-- **Install hint:** `npm install -g typescript-language-server typescript`
+- **Install hint:** `npm install -g typescript-language-server typescript@6`
 
 ## Install
 
-- **macOS:** `npm install -g typescript-language-server typescript`
-- **Linux:** `npm install -g typescript-language-server typescript`
-- **Windows:** `npm install -g typescript-language-server typescript` (PowerShell or cmd)
+- **macOS:** `npm install -g typescript-language-server typescript@6`
+- **Linux:** `npm install -g typescript-language-server typescript@6`
+- **Windows:** `npm install -g typescript-language-server typescript@6` (PowerShell or cmd)
 
 `typescript-language-server` is only a thin wrapper — it needs the `typescript`
 package (`tsserver`) present too, either globally or in the project's
-`node_modules`. Always install both.
+`node_modules`. Always install both. Pin `typescript@6`: TypeScript 7 ships no
+`lib/tsserver.js`, which `typescript-language-server` loads.
 
 Confirm it resolves:
 
@@ -22,34 +23,44 @@ command -v typescript-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
 
-Swap the server launch for your toolchain; each row owns the extensions named in
-its description:
+Swap the server for your toolchain. The first column is the string `command` and the second is `args`; do not paste a launch as a JSON array into `command`. Each row owns the extensions named in its description:
 
-| server launch                             | when to choose                          |
-| ----------------------------------------- | --------------------------------------- |
-| `["deno", "lsp"]`                         | Deno projects (handles `.ts/.tsx/.js`)  |
-| `["biome", "lsp-proxy", "--stdio"]`       | Biome lint/format as the LSP            |
-| `["vscode-eslint-language-server", "--stdio"]` | ESLint diagnostics                 |
-| `["oxlint", "--lsp"]`                     | fast Oxc-based linting                  |
-| `["vue-language-server", "--stdio"]`      | `.vue` single-file components           |
-| `["svelteserver", "--stdio"]`             | `.svelte` files                         |
-| `["astro-ls", "--stdio"]`                 | `.astro` files                          |
+| command | args | when to choose |
+| --- | --- | --- |
+| `deno` | `lsp` | Deno projects (handles `.ts/.tsx/.js`) |
+| `biome` | `lsp-proxy`, `--stdio` | Biome lint/format as the LSP |
+| `vscode-eslint-language-server` | `--stdio` | ESLint diagnostics |
+| `oxlint` | `--lsp` | fast Oxc-based linting |
+| `vue-language-server` | `--stdio` | `.vue` single-file components |
+| `svelteserver` | `--stdio` | `.svelte` files |
+| `astro-ls` | `--stdio` | `.astro` files |
 
 `eslint` install: `npm i -g vscode-langservers-extracted`. To run Deno instead
 of the default, launch `deno lsp` in place of `typescript-language-server --stdio`.
 
 ## Troubleshooting
-- **PATH:** `typescript-language-server` must be on PATH; reopen shell after `npm i -g`. Check your global bin with `npm bin -g`.
-- **Missing tsserver:** errors like "Could not find tsserver" mean the `typescript` package is absent — install it globally or in the project.
+- **PATH:** `typescript-language-server` must be on PATH; reopen the shell after `npm install -g typescript-language-server typescript@6`. Check your global bin with `npm bin -g`.
+- **Missing tsserver:** errors like "Could not find tsserver" mean the `typescript` package is absent — install `typescript@6` globally or in the project. TypeScript 7 ships no `lib/tsserver.js`.
 
 ## Verify
 

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

@@ -18,12 +18,23 @@ command -v yaml-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/zig/README.md

@@ -21,12 +21,23 @@ command -v zls
 
 ## 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-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "litgrok",
-  "version": "1.0.32",
+  "version": "1.0.33",
   "description": "Grok Build skills, project rules, and bounded lifecycle hooks for evidence-first lit work.",
   "author": {
     "name": "LitGrok contributors"

package/CHANGELOG.md

@@ -2,6 +2,11 @@
 
 ## Unreleased
 
+## 1.0.33 — 2026-11-09
+
+- Agent definitions use `permissionMode`, the key Grok reads. The old `permission_mode` spelling was ignored, so `plan` and `acceptEdits` never reached the host. Each agent's mode is unchanged: writers stay on `acceptEdits`, the QA runner stays on `default`, and the read-only reviewers and planner stay on `plan`.
+- Language-server notes now describe `.grok/lsp.json` and `~/.grok/lsp.json`. A server loads when `command` is a string, `args` is a list, and `extensionToLanguage` maps extensions. A `command` written as an array is dropped. The TypeScript install pins `typescript@6`, because TypeScript 7 ships no `lib/tsserver.js` for `typescript-language-server` to load.
+
 ## 1.0.32 — 2026-11-04
 
 - Dependency alerts cleared in the HyperFrames cover template: `@hono/node-server` 2.1.5 (was 2.1.1), and HyperFrames is now a development dependency of the template, as it is a render tool and never ships in an install. Its browser-driver chain still resolves zod 3.25.76, which GitHub now tracks as a development-scope dependency.

package/README.md

@@ -1,18 +1,18 @@
-<p align="center"><picture><source media="(prefers-reduced-motion: reduce)" srcset="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.32/docs/assets/cover-motion-still.webp" /><source media="(prefers-reduced-motion: no-preference)" srcset="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.32/docs/assets/cover-motion.webp" /><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.32/docs/assets/cover-motion.webp" width="100%" alt="LitFamily motion cover: seven armored robots power on one by one, the LitGrok robot wakes with glowing eyes and a lit frame, then LITFAMILY and KEEP THE WORK LIT. light up." /></picture></p>
+<p align="center"><picture><source media="(prefers-reduced-motion: reduce)" srcset="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.33/docs/assets/cover-motion-still.webp" /><source media="(prefers-reduced-motion: no-preference)" srcset="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.33/docs/assets/cover-motion.webp" /><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.33/docs/assets/cover-motion.webp" width="100%" alt="LitFamily motion cover: seven armored robots power on one by one, the LitGrok robot wakes with glowing eyes and a lit frame, then LITFAMILY and KEEP THE WORK LIT. light up." /></picture></p>
 
 <h1 align="center">LitGrok</h1>
 <p align="center"><strong>Keep the work lit.</strong></p>
 
 LitGrok gives xAI's Grok Build the habit of planning before it edits, checking what it built, and leaving a handoff, so tomorrow's session starts where today's stopped. One npm command adds its skills, project rule and hooks to your project.
 
-**[Full README on GitHub](https://github.com/wjgoarxiv/litgrok#readme)** · [Guide](https://github.com/wjgoarxiv/litgrok/blob/main/docs/guide.md) · [All skills](https://github.com/wjgoarxiv/litgrok/blob/main/docs/skills.md) · [한국어](https://github.com/wjgoarxiv/litgrok/blob/main/README_ko-KR.md) · [Install](#install-in-30-seconds) · [Reference](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.32/docs/reference.md)
+**[Full README on GitHub](https://github.com/wjgoarxiv/litgrok#readme)** · [Guide](https://github.com/wjgoarxiv/litgrok/blob/main/docs/guide.md) · [All skills](https://github.com/wjgoarxiv/litgrok/blob/main/docs/skills.md) · [한국어](https://github.com/wjgoarxiv/litgrok/blob/main/README_ko-KR.md) · [Install](#install-in-30-seconds) · [Reference](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.33/docs/reference.md)
 
 <p align="center">
-<a href="#install-in-30-seconds"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.32/docs/assets/readme/badge-version.svg" alt="1.0.32" /></a>
-<a href="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.32/LICENSE"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.32/docs/assets/readme/badge-license.svg" alt="MIT license" /></a>
+<a href="#install-in-30-seconds"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.33/docs/assets/readme/badge-version.svg" alt="1.0.33" /></a>
+<a href="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.33/LICENSE"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.33/docs/assets/readme/badge-license.svg" alt="MIT license" /></a>
 </p>
 
-<p align="center"><a href="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.32/docs/reference.md"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.32/docs/assets/readme/lucide-book-open.svg" width="16" alt="" /> Docs</a> &nbsp; <a href="#install-in-30-seconds">Install</a> &nbsp; <a href="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.32/docs/assets/cover-motion.webp"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.32/docs/assets/readme/lucide-play.svg" width="16" alt="" /> Cover motion</a> &nbsp; <a href="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.32/LICENSE"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.32/docs/assets/readme/lucide-shield-check.svg" width="16" alt="" /> MIT</a></p>
+<p align="center"><a href="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.33/docs/reference.md"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.33/docs/assets/readme/lucide-book-open.svg" width="16" alt="" /> Docs</a> &nbsp; <a href="#install-in-30-seconds">Install</a> &nbsp; <a href="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.33/docs/assets/cover-motion.webp"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.33/docs/assets/readme/lucide-play.svg" width="16" alt="" /> Cover motion</a> &nbsp; <a href="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.33/LICENSE"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.33/docs/assets/readme/lucide-shield-check.svg" width="16" alt="" /> MIT</a></p>
 
 Long Grok Build sessions get compacted, a new session starts without what the last one knew, and "done" often just means the model said so. LitGrok gives each session a routine to follow: a written plan before the first edit, checks against that plan, and a handoff file the next session can read. It ships 42 skills, 11 agents, one project rule, and twelve hook registrations. Grok Build still runs the session and chooses the model. It suits work that runs longer than one sitting, such as a feature spread over a few days or a report someone else will read.
 
@@ -24,7 +24,7 @@ You need Node.js and Grok Build. In an interactive terminal, from the project yo
 npm exec --yes --package @litfamily/litgrok@latest -- litgrok install
 ```
 
-The files land in `<project>/.grok/`. Add `--user` to install under `~/.grok/` instead, or use `--package @litfamily/litgrok@1.0.32` to pin this release. Add `--dry-run` to see every destination before anything is written.
+The files land in `<project>/.grok/`. Add `--user` to install under `~/.grok/` instead, or use `--package @litfamily/litgrok@1.0.33` to pin this release. Add `--dry-run` to see every destination before anything is written.
 
 Trying a local package instead? Put its real absolute path in a variable, then run these two lines separately:
 
@@ -69,11 +69,11 @@ Long sessions can write their own handoff. Turn on automatic handoff with `litgr
 
 `/skills` lists everything your session loaded. The [skills gallery on GitHub](https://github.com/wjgoarxiv/litgrok/blob/main/docs/skills.md) shows all 42 with a picture of each result.
 
-Beyond code, `lit-pptx` makes slide decks and `lit-docx` makes reports and Word documents, each in a design direction it picks for the job and names in the reply with two alternatives (eight for decks, six restrained ones for documents); `/frontend-ui-ux` builds and checks interfaces, `/readme-studio` writes source-checked READMEs, `lit-humanizer` rewrites stiff English or Korean prose, `lit-schematic` draws checked P&IDs, equipment layouts and isometric cutaways, `lit-hijack` ports published techniques clean-room with provenance, licence gate and parity proof, and `lit-adhd` briefs every recent session on one read-only screen.
+Beyond code, `lit-pptx` makes slide decks and `lit-docx` makes reports and Word documents, each in a design direction it picks for the job and names in the reply with two alternatives (thirteen for decks, six restrained ones for documents); `/frontend-ui-ux` builds and checks interfaces, `/readme-studio` writes source-checked READMEs, `lit-humanizer` rewrites stiff English or Korean prose, `lit-schematic` draws checked P&IDs, equipment layouts and isometric cutaways, `lit-hijack` ports published techniques clean-room with provenance, licence gate and parity proof, and `lit-adhd` briefs every recent session on one read-only screen.
 
 ## What changes after install
 
-The installer copies the skills, agents, project rule, and hooks into `.grok/`. The twelve hook registrations in [`hooks/hooks.json`](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.32/hooks/hooks.json) run only in a trusted Git root, and they log the order of events in `.grok/litgrok/session-ledger/`. Everything runs inside your Grok session, and nothing runs in the background; when the session ends, the work waits for the next one.
+The installer copies the skills, agents, project rule, and hooks into `.grok/`. The twelve hook registrations in [`hooks/hooks.json`](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.33/hooks/hooks.json) run only in a trusted Git root, and they log the order of events in `.grok/litgrok/session-ledger/`. Everything runs inside your Grok session, and nothing runs in the background; when the session ends, the work waits for the next one.
 
 If you'd like a status row showing the active LitGrok skill, the model and how much context is used, add it with `install --user --status-line`. It writes `[ui.status_line]` into `~/.grok/config.toml` and backs up an existing file first. Once a prompt starts a workflow skill, the row also shows the workflow stage, the tool running now and the last test result. Add `--notify` for Grok's terminal notification when a turn finishes.
 
@@ -112,6 +112,6 @@ If the status row is missing, add it with `install --user --status-line`. Grok r
 
 If LitGrok saves you some re-explaining, a [star on GitHub](https://github.com/wjgoarxiv/litgrok) helps other Grok Build users find it.
 
-[Reference](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.32/docs/reference.md) · [Changelog](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.32/CHANGELOG.md) · [Privacy](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.32/docs/privacy.md) · [MIT license](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.32/LICENSE) · [Trademark policy](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.32/TRADEMARK.md)
+[Reference](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.33/docs/reference.md) · [Changelog](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.33/CHANGELOG.md) · [Privacy](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.33/docs/privacy.md) · [MIT license](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.33/LICENSE) · [Trademark policy](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.33/TRADEMARK.md)
 
 The cover is brand motion made with the LitFamily motion skill: animated artwork, with no Grok session recorded in it.

package/README_ko-KR.md

@@ -1,18 +1,18 @@
-<p align="center"><picture><source media="(prefers-reduced-motion: reduce)" srcset="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.32/docs/assets/cover-motion-still.webp" /><source media="(prefers-reduced-motion: no-preference)" srcset="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.32/docs/assets/cover-motion.webp" /><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.32/docs/assets/cover-motion.webp" width="100%" alt="LitFamily 모션 커버: 일곱 로봇 패널이 차례로 켜지고, LitGrok 로봇의 눈과 테두리가 빛난 뒤 LITFAMILY와 KEEP THE WORK LIT. 문구가 밝아지는 영상" /></picture></p>
+<p align="center"><picture><source media="(prefers-reduced-motion: reduce)" srcset="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.33/docs/assets/cover-motion-still.webp" /><source media="(prefers-reduced-motion: no-preference)" srcset="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.33/docs/assets/cover-motion.webp" /><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.33/docs/assets/cover-motion.webp" width="100%" alt="LitFamily 모션 커버: 일곱 로봇 패널이 차례로 켜지고, LitGrok 로봇의 눈과 테두리가 빛난 뒤 LITFAMILY와 KEEP THE WORK LIT. 문구가 밝아지는 영상" /></picture></p>
 
 <h1 align="center">LitGrok</h1>
 <p align="center"><strong>Keep the work lit.</strong></p>
 
 LitGrok은 xAI Grok Build가 코드를 고치기 전에 계획부터 세우고, 만든 결과를 확인하고, 인수인계 문서를 남기게 합니다. 그러면 내일 세션이 오늘 멈춘 자리에서 이어집니다. npm 명령 한 줄이면 스킬과 프로젝트 규칙, 훅이 프로젝트에 들어갑니다.
 
-**[GitHub에서 README 전체 보기](https://github.com/wjgoarxiv/litgrok/blob/main/README_ko-KR.md)** · [안내서](https://github.com/wjgoarxiv/litgrok/blob/main/docs/guide_ko-KR.md) · [전체 스킬](https://github.com/wjgoarxiv/litgrok/blob/main/docs/skills_ko-KR.md) · [English](https://github.com/wjgoarxiv/litgrok#readme) · [설치](#30초-설치) · [상세 안내](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.32/docs/reference_ko-KR.md)
+**[GitHub에서 README 전체 보기](https://github.com/wjgoarxiv/litgrok/blob/main/README_ko-KR.md)** · [안내서](https://github.com/wjgoarxiv/litgrok/blob/main/docs/guide_ko-KR.md) · [전체 스킬](https://github.com/wjgoarxiv/litgrok/blob/main/docs/skills_ko-KR.md) · [English](https://github.com/wjgoarxiv/litgrok#readme) · [설치](#30초-설치) · [상세 안내](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.33/docs/reference_ko-KR.md)
 
 <p align="center">
-<a href="#30초-설치"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.32/docs/assets/readme/badge-version.svg" alt="1.0.32" /></a>
-<a href="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.32/LICENSE"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.32/docs/assets/readme/badge-license.svg" alt="MIT 라이선스" /></a>
+<a href="#30초-설치"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.33/docs/assets/readme/badge-version.svg" alt="1.0.33" /></a>
+<a href="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.33/LICENSE"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.33/docs/assets/readme/badge-license.svg" alt="MIT 라이선스" /></a>
 </p>
 
-<p align="center"><a href="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.32/docs/reference_ko-KR.md"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.32/docs/assets/readme/lucide-book-open.svg" width="16" alt="" /> 상세 안내</a> &nbsp; <a href="#30초-설치">설치</a> &nbsp; <a href="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.32/docs/assets/cover-motion.webp"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.32/docs/assets/readme/lucide-play.svg" width="16" alt="" /> 커버 모션</a> &nbsp; <a href="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.32/LICENSE"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.32/docs/assets/readme/lucide-shield-check.svg" width="16" alt="" /> MIT</a></p>
+<p align="center"><a href="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.33/docs/reference_ko-KR.md"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.33/docs/assets/readme/lucide-book-open.svg" width="16" alt="" /> 상세 안내</a> &nbsp; <a href="#30초-설치">설치</a> &nbsp; <a href="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.33/docs/assets/cover-motion.webp"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.33/docs/assets/readme/lucide-play.svg" width="16" alt="" /> 커버 모션</a> &nbsp; <a href="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.33/LICENSE"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.33/docs/assets/readme/lucide-shield-check.svg" width="16" alt="" /> MIT</a></p>
 
 Grok Build 세션이 길어지면 대화가 압축되고, 새 세션은 앞 세션이 알던 내용을 모른 채 시작하며, "다 됐다"는 말도 모델이 그렇게 말했다는 뜻일 때가 많습니다. LitGrok은 세션마다 따라갈 순서를 줍니다. 첫 수정 전에 계획을 글로 남기고, 그 계획에 비추어 확인하고, 다음 세션이 읽을 인수인계 문서를 남깁니다. 스킬 42개, 에이전트 11개, 프로젝트 규칙 하나, 훅 등록 열두 개가 들어 있고, 세션 실행과 모델 선택은 계속 Grok Build가 맡습니다. 며칠에 걸쳐 만드는 기능이나 다른 사람이 읽을 보고서처럼, 한 번 앉은 자리에서 끝나지 않는 일에 잘 맞습니다.
 
@@ -24,7 +24,7 @@ Node.js와 Grok Build가 있으면 됩니다. 써 보고 싶은 프로젝트에
 npm exec --yes --package @litfamily/litgrok@latest -- litgrok install
 ```
 
-파일은 `<project>/.grok/`에 들어갑니다. `~/.grok/`에 설치하려면 `--user`를, 이 릴리스로 고정하려면 `--package @litfamily/litgrok@1.0.32`을 쓰세요. `--dry-run`을 붙이면 파일을 쓰기 전에 들어갈 경로를 모두 보여 줍니다.
+파일은 `<project>/.grok/`에 들어갑니다. `~/.grok/`에 설치하려면 `--user`를, 이 릴리스로 고정하려면 `--package @litfamily/litgrok@1.0.33`을 쓰세요. `--dry-run`을 붙이면 파일을 쓰기 전에 들어갈 경로를 모두 보여 줍니다.
 
 로컬 패키지로 써 보려면 실제 절대 경로를 변수에 넣고 두 줄을 따로 실행하세요.
 
@@ -73,7 +73,7 @@ npm exec --yes --package "$LITGROK_PACK" -- litgrok install
 
 ## 설치하면 달라지는 것
 
-설치 프로그램이 스킬, 에이전트, 프로젝트 규칙, 훅을 `.grok/`에 복사합니다. [`hooks/hooks.json`](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.32/hooks/hooks.json)에 있는 훅 등록 열두 개는 신뢰한 Git 루트에서만 동작하고, `.grok/litgrok/session-ledger/`에 이벤트 순서를 남깁니다. 모든 작업은 Grok 세션 안에서 돌고 백그라운드 작업은 없습니다. 세션이 끝나면 다음 세션이 이어받을 때까지 그 자리에 멈춰 있습니다.
+설치 프로그램이 스킬, 에이전트, 프로젝트 규칙, 훅을 `.grok/`에 복사합니다. [`hooks/hooks.json`](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.33/hooks/hooks.json)에 있는 훅 등록 열두 개는 신뢰한 Git 루트에서만 동작하고, `.grok/litgrok/session-ledger/`에 이벤트 순서를 남깁니다. 모든 작업은 Grok 세션 안에서 돌고 백그라운드 작업은 없습니다. 세션이 끝나면 다음 세션이 이어받을 때까지 그 자리에 멈춰 있습니다.
 
 지금 어떤 LitGrok 스킬이 동작 중인지, 어떤 모델을 쓰는지, 컨텍스트를 얼마나 썼는지 보고 싶으면 `install --user --status-line`으로 상태 행을 켜세요. `~/.grok/config.toml`에 `[ui.status_line]`을 넣고, 파일이 이미 있으면 먼저 백업합니다. 프롬프트가 작업 흐름 스킬을 시작하면 지금 단계, 돌고 있는 도구, 마지막 테스트 결과도 함께 보입니다. 턴이 끝날 때 Grok의 터미널 알림을 받으려면 `--notify`를 붙이세요.
 
@@ -112,6 +112,6 @@ npm exec --yes --package @litfamily/litgrok@latest -- litgrok uninstall --user
 
 LitGrok 덕분에 같은 설명을 덜 반복하게 됐다면, [GitHub 스타](https://github.com/wjgoarxiv/litgrok) 하나가 다른 Grok Build 사용자에게 이 프로젝트를 알리는 데 도움이 됩니다.
 
-[상세 안내](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.32/docs/reference_ko-KR.md) · [변경 이력](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.32/CHANGELOG.md) · [개인정보](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.32/docs/privacy.md) · [MIT 라이선스](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.32/LICENSE) · [상표 정책](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.32/TRADEMARK.md)
+[상세 안내](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.33/docs/reference_ko-KR.md) · [변경 이력](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.33/CHANGELOG.md) · [개인정보](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.33/docs/privacy.md) · [MIT 라이선스](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.33/LICENSE) · [상표 정책](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.33/TRADEMARK.md)
 
 커버의 모션은 LitFamily 모션 스킬로 만든 브랜드 연출입니다. 그려서 움직인 그림이라 실제 Grok 세션을 녹화한 장면은 들어 있지 않습니다.

package/bin/litgrok.mjs

@@ -106,8 +106,29 @@ const PRE_MANIFEST_PAYLOAD_HASHES = Object.freeze({
   'skills/litresearch/SKILL.md': '93cf90ef9706531b7cacbce434a6eea13c3350df3266a25aabfa3149c0d82bf4',
   'skills/litwork/SKILL.md': '771b7cead03c0d1d1e67af82e308ea0980b8ab18474026516798f559048beda7',
   'skills/lsp-setup/SKILL.md': '313ffd924f00a1523905d2588e0812c8edcaec84b114d2d487506bd905e5376d',
+  'skills/lsp-setup/references/bash/README.md': 'aa6fd2b04ab55139e667363e1b135e06bb077e801d66ebff2294fd253b6c4d8e',
+  'skills/lsp-setup/references/c-cpp/README.md': '93c7f759c8f058aae7a43f457251b1b7631167cf8408f97be60681a3b1a40120',
+  'skills/lsp-setup/references/csharp/README.md': '687fbbfb814f1443cb11c916c70f3c374d7f90ec5e1135bfe3b239e7b7615c42',
+  'skills/lsp-setup/references/dart/README.md': '3f8abf0b9e81d3e66af27a419ecd27f05b58deb55b67d7f9067224b854790e58',
+  'skills/lsp-setup/references/elixir/README.md': '92fa887eda596ebd6edde47cca68250a3d6395e406dc98be1654d259596de13d',
+  'skills/lsp-setup/references/go/README.md': '0dcdc79be1220f8cea1c908756a77dba386ceaff4aa644658ff16186de8391a2',
+  'skills/lsp-setup/references/haskell/README.md': 'e59d8b06782cab4aa29a3dfcfda44e54e6e10ac9d03b4e65db01f2e1605b8210',
+  'skills/lsp-setup/references/java/README.md': '45a0a16a4460aa861794cda6bb09460e9c58714db6b16ae4de5f6d7754bfea22',
+  'skills/lsp-setup/references/julia/README.md': '50c3e0566bb23ac170bca5f98556daa9d524a702de754e3e7da7ae0d4d8d08af',
+  'skills/lsp-setup/references/kotlin/README.md': 'ebf9adf88dd5808d698e0a6d5c3bf1de114e5b87aa82a8f5aae73344639dd930',
+  'skills/lsp-setup/references/lua/README.md': 'cdfafc79777258d36de12362a6f446fb647767f61f9a48534079477ec8833c18',
+  'skills/lsp-setup/references/php/README.md': '1431440877f33c25d8367501cf3896e08a4fb57d863347578b466aa22a2809dc',
+  'skills/lsp-setup/references/python/README.md': 'b370324a479b5151e55afcc5bd59accf573a0252fa00796d1c44ccd039430153',
+  'skills/lsp-setup/references/ruby/README.md': 'f53ce1347339d7b6194275cde96fa9a9ee973dbff9be88b82ded8cf0bf9acb2e',
+  'skills/lsp-setup/references/rust/README.md': 'a8287717b3e09826d9791df56b07c0c0bd2e45bb30faf3dc9bd7556b13e6c47f',
+  'skills/lsp-setup/references/swift/README.md': '863927f6275d17ba9a325d635c149dcd61936ea33485633b6cb5414cb61c035d',
+  'skills/lsp-setup/references/terraform/README.md': '5711b1ffc8c6b91f37e644f08fbb35002f673a0b650e5795e588cf72fc935c1b',
+  'skills/lsp-setup/references/typescript/README.md': '9aa436e506ce95e3c5ae2a7ef73a28449135e8b6ff4bb8cf350d383666923a74',
+  'skills/lsp-setup/references/yaml/README.md': 'cd1ed82b29ac5b04f5026ed785c5cfe3b6104ef4e6a1e4f7a7fea07f8995fdd3',
+  'skills/lsp-setup/references/zig/README.md': '2df69b12907044eef11beb3c2f363264848cbda02d6ecd0035000888d91a4289',
   'skills/lsp-setup/scripts/lsp-server-table.mjs': 'c59d5a9a060eb67f701f025824c7e33930d0071d03c9f131128156f87895322e',
   'skills/lsp/SKILL.md': '2e4b1abdd0b03e993b8082ac34adc11de2fe6553f623e4a434b10a20499c4aad',
+  'skills/lsp/references/built-in-lsp-contract.md': 'bf9dc6d557ccee329fa15507d41b431cf063bce5ac5345c732ad22b121a4ec15',
   'skills/refactor/SKILL.md': '5fd2df1a36eae216f8af4db09e7e7d26231b167907ad19c49465153a1dcadde0',
   'skills/review-work/SKILL.md': 'acfef3ff9c6e243cb9b88169a67e749e27a2e530af09aed07a2d66dd932c3b5d',
   'skills/rules/SKILL.md': 'b880136962faeb3dea93cc42e30f5d3cc461a03fe71f7ff908d4b09170c38c5f',

package/docs/assets/readme/badge-version.svg

@@ -1 +1 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="146" height="20" role="img" aria-label="local: 1.0.32"><title>local: 1.0.32</title><g shape-rendering="crispEdges"><rect width="49" height="20" fill="#080d14"/><rect x="49" width="97" height="20" fill="#ff6337"/></g><g fill="#fff" text-anchor="middle" font-family="Verdana,Geneva,DejaVu Sans,sans-serif" text-rendering="geometricPrecision" font-size="110"><text x="255" y="140" textLength="290" transform="scale(.1)">local</text><text x="965" y="140" textLength="870" transform="scale(.1)" fill="#080D14">1.0.32</text></g></svg>
+<svg xmlns="http://www.w3.org/2000/svg" width="146" height="20" role="img" aria-label="local: 1.0.33"><title>local: 1.0.33</title><g shape-rendering="crispEdges"><rect width="49" height="20" fill="#080d14"/><rect x="49" width="97" height="20" fill="#ff6337"/></g><g fill="#fff" text-anchor="middle" font-family="Verdana,Geneva,DejaVu Sans,sans-serif" text-rendering="geometricPrecision" font-size="110"><text x="255" y="140" textLength="290" transform="scale(.1)">local</text><text x="965" y="140" textLength="870" transform="scale(.1)" fill="#080D14">1.0.33</text></g></svg>

package/docs/reference.md

@@ -80,7 +80,7 @@ npm exec --yes --package @litfamily/litgrok@latest -- litgrok install
 Pin a version when you need a reproducible install:
 
 ```bash
-npm exec --yes --package @litfamily/litgrok@1.0.32 -- litgrok install
+npm exec --yes --package @litfamily/litgrok@1.0.33 -- litgrok install
 ```
 
 Preview without writing files:

package/docs/reference_ko-KR.md

@@ -81,7 +81,7 @@ npm exec --yes --package @litfamily/litgrok@latest -- litgrok install
 재현 가능한 설치는 버전을 고정합니다.
 
 ```bash
-npm exec --yes --package @litfamily/litgrok@1.0.32 -- litgrok install
+npm exec --yes --package @litfamily/litgrok@1.0.33 -- litgrok install
 ```
 
 파일을 쓰지 않고 미리보기:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@litfamily/litgrok",
-  "version": "1.0.32",
+  "version": "1.0.33",
   "description": "Installer for LitGrok: skills, a project rule and hooks that help xAI Grok Build sessions plan, build, check and hand off their work.",
   "keywords": [
     "grok",

package/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "litgrok",
-  "version": "1.0.32",
+  "version": "1.0.33",
   "description": "Grok Build skills, project rules, and bounded lifecycle hooks for evidence-first lit work.",
   "author": {
     "name": "LitGrok contributors"