@litfamily/litgrok 1.0.4 → 1.0.6

package/README.md

@@ -1,71 +1,50 @@
-<p align="center"><picture><source media="(prefers-reduced-motion: reduce)" srcset="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.4/docs/assets/cover.webp" /><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.4/docs/assets/cover-motion.webp" width="100%" alt="LitGrok cover art. An orange signal moves through orbital paths above the GROK BUILD wordmark. The static family cover appears for reduced-motion preference." /></picture></p>
-<p align="center"><a href="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.4/docs/assets/cover.webp">View the static cover</a></p>
+<p align="center"><picture><source media="(prefers-reduced-motion: reduce)" srcset="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/docs/assets/cover-motion-still.webp" /><source media="(prefers-reduced-motion: no-preference)" srcset="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/docs/assets/cover-motion.webp" /><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/docs/assets/cover-motion.webp" width="100%" alt="LitGrok motion cover with an orange signal crossing orbital paths above the GROK BUILD wordmark." /></picture></p>
 
-<h1 align="center">LitGrok</h1>
-<p align="center"><strong>Keep the work lit.</strong></p>
-<p align="center"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.4/docs/assets/litgrok-wordmark.svg" width="480" alt="LITGROK display type" /></p>
-<p align="center"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.4/docs/assets/litgrok-clay-icon.png" width="160" alt="LitGrok clay mark" /></p>
-
-Make something useful in Grok Build. Leave the checked result and the next step with your project.
-
-[한국어](./README_ko-KR.md) · [Install](#install-in-30-seconds) · [First use](#first-lit-use) · [Reference](./docs/reference.md)
-
-<p align="center">
-<a href="#install-in-30-seconds"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.4/docs/assets/readme/badge-version.svg" alt="1.0.4" /></a>
-<a href="./LICENSE"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.4/docs/assets/readme/badge-license.svg" alt="MIT license" /></a>
-</p>
-
-<p align="center">
-<a href="./docs/reference.md"><img src="./docs/assets/readme/lucide-book-open.svg" width="16" alt="" /> Docs</a> &nbsp; <a href="#install-in-30-seconds">Install</a> &nbsp; <a href="./docs/assets/readme/ignition-film.mp4"><img src="./docs/assets/readme/lucide-play.svg" width="16" alt="" /> Ignition</a> &nbsp; <a href="./LICENSE"><img src="./docs/assets/readme/lucide-shield-check.svg" width="16" alt="" /> MIT</a>
-</p>
+<p align="center"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/docs/assets/readme/ascii-readme.svg" width="480" alt="LIT ASCII B mark — Grok" /></p>
 
-> **A spark has been placed in your hands. Put it to work.**
->
-> A bug you want fixed. A screen you want built. A project you want to finish.
->
-> Starting takes a line. When the session changes, the harder part is finding where you left off. LIT guides you through leaving a goal, a plan, a checked result, and a next step with your project.
->
-> **Leave something the next session can pick up.**
-
-It ships 33 skills, 11 agents, one project rule, and eleven hook registrations. The installer copies the complete payload into your project; Grok Build runs the session and owns model selection.
-
-Package: **@litfamily/litgrok** · Version: **1.0.4** · [MIT](./LICENSE)
-
-The scientific visualization corpus is packaged at `.grok/vendor/scientific-visualization/`; the numeric `045_scientific-visualization` label remains only in license and provenance filenames.
-
-> [!NOTE]
-> Install the scoped package with the registry command below. An absolute local package path is available for an isolated trial. Landing covers and badges ship in the package so they render on npmjs.
-
-## Start with one lit task
-
-Grok Build uses the explicit `/litwork` route for a bounded task. It owns model execution; LitGrok leaves skills, rules, and checked next steps in the project.
-
-| Prompt or route | Effect |
-| --- | --- |
-| `/litwork` | Start the shipped work checklist in Grok Build. |
-| `handoff` or `/lit-handoff` | Carry the checked result and next step into another session. |
-| `/lit-plan` | Write a plan with concrete checks. |
-| `/start-work <approved-plan>` | Execute an approved plan. |
-| `/review-work` | Review a change and its evidence. |
-| `/litresearch` | Run bounded, source-traceable research without overstating evidence. |
+<details>
+<summary>Copy ASCII logo</summary>
 
-## Practical routes and visual cues
+```text
+                             ▄▄▄▄
+                   ▗███▌   ▗██████▖
+ ▗▄▄▄▄▄          ▗▟████▌   ▝██████▘
+ ▐█████        ▗▟██████▌    ▝▀▜█▀▘
+ ▐█████      ▗▟███████▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
+ ▐█████    ▗▟█████████████████████████ ▐█▀
+ ▐█████    ████████████████████████████▀
+ ▐█████    ██▛▘   ▄ ▄▄▄▄▖▄▄▄▄▄▄▄▄▄▄▄▄▄▖
+ ▐█████    ▀    ▄██ ████▌█████████████▌
+ ▐█████       ▄████ ████▌█████████████▌
+ ▐█████     ▄█████▛
+ ▐█████  ▗▟█████▀▘       ▄▄▄▄▄     ▗▖
+ ▐█████ ▐█████▀          █████     ▐▛▀
+ ▐█████ ▐███▀            █████
+ ▐█████ ▐█▀              █████
+ ▐█████ ▝                █████
+ ▐█████▄▄▄▄▄▄▄▖          █████
+ ▐███████████▛           █████
+ ▐██████████▀            █████
 
-In Grok Build, `/litwork` starts the bounded work checklist; `handoff` or `/lit-handoff` carries the checked result and next step; `/lit-plan` records a plan with checks; `/start-work <approved-plan>` executes that plan; `/review-work` inspects the change and its evidence; and `/litresearch` runs bounded, source-traceable research. The expected effect is a resumable, checked project record. The host limit is explicit: Grok Build owns execution and model selection, while LitGrok installs the `.grok` payload; hooks require a trusted Git root and a plain folder may load skills and rules without hooks. These images are static route cues, not proof of live host behavior.
 
-The five activation contracts ask the model to start each activated response with exactly one line before other response content. For `/litwork`, the requested line is:
+grok
+```
 
-🔥 **LIT IGNITED · litwork** 🔥
+</details>
 
-This is advisory prompt guidance; it does not verify native host display.
+<h1 align="center">LitGrok</h1>
+<p align="center"><strong>Keep the work lit.</strong></p>
 
-<p align="center"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.4/docs/assets/litgrok-ignition-1600.webp" width="48%" alt="LitGrok ignition apparatus" /><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.4/docs/assets/litgrok-continuity-1600.webp" width="48%" alt="LitGrok continuity apparatus" /></p>
+Make something useful in Grok Build. Leave the checked result and the next step with your project.
 
-<p align="center"><a href="./docs/assets/readme/ignition-film.mp4"><img src="./docs/assets/readme/ignition-poster.png" width="720" alt="Ignition motion poster" /></a></p>
+[한국어](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/README_ko-KR.md) · [Install](#install-in-30-seconds) · [Quick start](#quick-start) · [Reference](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/docs/reference.md)
 
-The poster opens the optional film; this README keeps motion opt-in.
+<p align="center">
+<a href="#install-in-30-seconds"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/docs/assets/readme/badge-version.svg" alt="1.0.6" /></a>
+<a href="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/LICENSE"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/docs/assets/readme/badge-license.svg" alt="MIT license" /></a>
+</p>
 
-The retained `docs/assets/cover.svg` is the editable, low-bandwidth fallback; the WebP above is the product emphasis export.
+<p align="center"><a href="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/docs/reference.md"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/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.6/docs/assets/cover-motion.webp"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/docs/assets/readme/lucide-play.svg" width="16" alt="" /> Cover motion</a> &nbsp; <a href="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/LICENSE"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/docs/assets/readme/lucide-shield-check.svg" width="16" alt="" /> MIT</a></p>
 
 ## Install in 30 seconds
 
@@ -82,7 +61,7 @@ LITGROK_PACK='/absolute/path/to/the-provided-package.tgz'
 npm exec --yes --package "$LITGROK_PACK" -- litgrok install
 ```
 
-The default destination is `<project>/.grok/`. Use `--package @litfamily/litgrok@1.0.4` for a pinned install, or add `--user` to install under `~/.grok/`. [Install and upgrade details](./docs/reference.md#install).
+The default destination is `<project>/.grok/`. Use `--package @litfamily/litgrok@1.0.6` for a pinned install, or add `--user` to install under `~/.grok/`. [Install and upgrade details](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/docs/reference.md#install).
 
 The persistent Grok status row is optional and user-level only. Opt in with:
 
@@ -90,13 +69,34 @@ The persistent Grok status row is optional and user-level only. Opt in with:
 npm exec --yes --package @litfamily/litgrok@latest -- litgrok install --user --status-line
 ```
 
-This adds `[ui.status_line]` to `~/.grok/config.toml` with a two-second refresh. If a config already exists, LitGrok backs it up before changing it; an existing `ui.status_line` is preserved. `uninstall --user` removes only the unchanged LitGrok-managed value. Grok reads this setting from user or administrator configuration, not from project or plugin configuration ([status-line docs](https://docs.x.ai/build/features/status-line), [settings reference](https://docs.x.ai/build/settings/reference)). Example rows are `🔥 LIT IGNITED · lit-plan 🔥 │ grok-4 │ ctx 42%` and `LIT · grok │ grok-4 │ ctx 42%`. With color enabled, the active `LIT IGNITED · <discipline>` label is bold with a per-character truecolor gradient `#FF6337 → #FF2D95 → #00E5FF`; the flames and model/context segment remain unstyled. `NO_COLOR` (including an empty value) or `LITGROK_HUD_COLOR=0` keeps the row plain. Truecolor, bold and emoji rendering in the status row were confirmed on Grok Build 1.0.13. This adds a status command, not another hook registration; LitGrok still ships eleven hook registrations.
+This adds `[ui.status_line]` to `~/.grok/config.toml` with a two-second refresh. If a config already exists, LitGrok backs it up before changing it; an existing `ui.status_line` is preserved. `uninstall --user` removes only the unchanged LitGrok-managed value. Grok reads this setting from user or administrator configuration, not from project or plugin configuration ([status-line docs](https://docs.x.ai/build/features/status-line), [settings reference](https://docs.x.ai/build/settings/reference)). Example rows are `🔥 LIT IGNITED · lit-plan 🔥 │ grok-4 │ ctx 42%` and `LIT · grok │ grok-4 │ ctx 42%`. The first visible prompt match among `lit-scientific-visualization`, `lit-handoff`, `autoconference`, `autoresearch`, `lit-plan`, and `litwork` sets the discipline; bare `lit` maps to `litwork`, and inline or fenced Markdown code is ignored. With color enabled, the active `LIT IGNITED · <discipline>` label is bold with a per-character truecolor gradient `#FF6337 → #FF2D95 → #00E5FF`; the flames and model/context segment remain unstyled. `NO_COLOR` (including an empty value) or `LITGROK_HUD_COLOR=0` keeps the row plain. Truecolor, bold and emoji rendering in the status row were confirmed on Grok Build 1.0.13. This adds a status command, not another hook registration; LitGrok still ships eleven hook registrations.
 
-Project hooks need a trusted Git project root in Grok Build. A plain folder can still load the installed skills and rules while hooks remain unavailable. For a new disposable project, run `git init` yourself before trusting it; for an existing repository, open Grok Build from its actual root. The installer never runs `git init` or changes trust. In the observed Grok Build 1.0.23 host, `grok --trust inspect --json` accepted the trust-and-inspect route even though `--trust` was omitted from `grok --help`; this is version-specific behavior.
+### Safety and uninstall
 
-If `CI` or `NO_COLOR` is set, even to an empty value, installation is a no-write preview. So is `--no-color`. Without `--yes`, a non-interactive run is also a no-write preview; with `--yes`, installation proceeds without a TTY as long as none of the above apply. Check that the installer reports actual writes before continuing.
+Preview the exact destinations before writing:
+
+```bash
+npm exec --yes --package "$LITGROK_PACK" -- litgrok install --dry-run
+```
+
+The installer verifies file ownership before upgrades or removal. Modified, foreign, or unsafe destination files cause the operation to refuse rather than overwrite them. `CI`, `NO_COLOR` (even empty), `--no-color`, and `--dry-run` are no-write previews regardless of `--yes`. Without `--yes`, a non-interactive run is also a no-write preview; with `--yes`, it proceeds without a TTY as long as none of the above apply.
+
+For a local-package install, remove it with the same package in the same project. Add `--user` only to remove an installation made with `--user`.
+
+```bash
+npm exec --yes --package "$LITGROK_PACK" -- litgrok uninstall
+```
+
+Registry uninstall commands:
 
-## First lit use
+```bash
+npm exec --yes --package @litfamily/litgrok@latest -- litgrok uninstall
+npm exec --yes --package @litfamily/litgrok@latest -- litgrok uninstall --user
+```
+
+User-level uninstall backs up `~/.grok/config.toml` before removing the unchanged LitGrok-managed status-line keys; other settings and a user-edited status line are preserved. Match the scope used for installation. Re-run `install` to update. The installer does not grant hook trust, create a Git root, write login state or API keys, or choose a model. The hedge guard is fail-open on host errors; a passing package test does not prove live Grok behavior. Check `/hooks` and `grok inspect --json` from the repository root in your own session. [Host boundaries and verification](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/docs/reference.md#verify).
+
+## Quick start
 
 Open or restart Grok Build at the installed project’s Git root. Review and trust its project hooks with `/hooks-trust`, or, on the observed Grok Build 1.0.23 host, use `grok --trust inspect --json`. A plain folder can still load skills and rules while hooks remain unavailable. Check `/skills` for the installed catalog and `/hooks` for hook registrations. LitGrok does not create a Git root or change trust.
 
@@ -120,11 +120,37 @@ For a larger change, start with `/lit-plan`, review the saved plan, then invoke
 /lit-handoff Record what we built, what we checked, and what remains. Tell me where you saved the handoff.
 ```
 
-In the next session, supply that returned path and ask Grok Build to read it and check the current files before continuing. The default is `.handoff/HANDOFF.md` in a new Git project or `HANDOFF.md` in a non-Git workspace. An existing root handoff is reused. [Destination and handoff guidance](./.grok/skills/lit-handoff/SKILL.md).
+In the next session, supply that returned path and ask Grok Build to read it and check the current files before continuing. The default is `.handoff/HANDOFF.md` in a new Git project or `HANDOFF.md` in a non-Git workspace. An existing root handoff is reused. [Destination and handoff guidance](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/.grok/skills/lit-handoff/SKILL.md).
 
 **Keeping the spark means leaving work another session can pick up.** These are skill-guided steps in your session; LitGrok does not schedule background work or continue after the session ends.
 
-## How it fits inside Grok Build
+## Key features
+
+> **A spark has been placed in your hands. Put it to work.**
+>
+> A bug you want fixed. A screen you want built. A project you want to finish.
+>
+> Starting takes a line. When the session changes, the harder part is finding where you left off. LIT guides you through leaving a goal, a plan, a checked result, and a next step with your project.
+>
+> **Leave something the next session can pick up.**
+
+It ships 34 skills, 11 agents, one project rule, and eleven hook registrations. The installer copies the complete payload into your project; Grok Build runs the session and owns model selection.
+
+Package: **@litfamily/litgrok** · Version: **1.0.6** · [MIT](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/LICENSE)
+
+The scientific visualization corpus is packaged at `.grok/vendor/scientific-visualization/`; the numeric `045_scientific-visualization` label remains only in license and provenance filenames.
+
+These route examples are static guidance, not proof of live host behavior.
+
+The five activation contracts ask the model to start each activated response with exactly one line before other response content. For `/litwork`, the requested line is:
+
+🔥 **LIT IGNITED · litwork** 🔥
+
+This is advisory prompt guidance; it does not verify native host display.
+
+The retained `docs/assets/cover.svg` remains editable vector artwork; the README uses a still frame of the motion cover when reduced motion is preferred.
+
+### How it fits inside Grok Build
 
 The installer puts files in the project's `.grok/` directory. `/litwork` provides a checklist for the current session; Grok Build owns execution and model selection. These are the main connections.
 
@@ -144,99 +170,75 @@ flowchart TD
 
 The hooks' `.grok/litgrok/session-ledger/` records event order. Judge success from the artifact and its checks. The user supplies the handoff path in the next session; having a record does not automatically resume work.
 
-[Checklist and hook boundaries](./.grok/skills/litwork/SKILL.md) · [Handoff destinations](./.grok/skills/lit-handoff/SKILL.md) · [Install details](./docs/reference.md#install)
+[Checklist and hook boundaries](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/.grok/skills/litwork/SKILL.md) · [Handoff destinations](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/.grok/skills/lit-handoff/SKILL.md) · [Install details](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/docs/reference.md#install)
 
-## Core routes
+### Design and README production
 
-| Need | Skill |
-|---|---|
-| Clarify a vague request | [`/deep-interview`](./.grok/skills/deep-interview/SKILL.md) |
-| Write a plan with concrete checks | [`/lit-plan`](./.grok/skills/lit-plan/SKILL.md) |
-| Execute an approved plan | [`/start-work`](./.grok/skills/start-work/SKILL.md) |
-| Keep one task bounded and verifiable | [`/litwork`](./.grok/skills/litwork/SKILL.md) |
-| Review a change and its evidence | [`/review-work`](./.grok/skills/review-work/SKILL.md) |
-| Leave a resumable handoff | [`/lit-handoff`](./.grok/skills/lit-handoff/SKILL.md) |
+Use `/frontend-ui-ux <surface and outcome>` to build and inspect an authorized interface. A clear brief proceeds to working code; material ambiguity prompts a focused question. Review-only and plan-only requests remain read-only.
 
-Use `/skills` for all 33 skills. [Rename compatibility](./docs/reference.md#skill-rename-compatibility) covers the one-release aliases; old slash routes are not guaranteed.
+Use `/readme-studio <repository and outcome>` for a source-checked README, outlined Pretendard/Meslo typography, and portable cover/motion recipes. Check `/skills` after installation. Native image generation depends on the tools exposed in your Grok session; `IMAGE_GENERATION_UNAVAILABLE` permits an explicitly supplied background path. Fonts and renderers are task-local prerequisites. Local output is separate from live host and GitHub/npm acceptance. [README Studio](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/.grok/skills/readme-studio/SKILL.md).
 
-## Safety and uninstall
+The cover is brand motion, not a recording of a Grok task execution.
 
-Preview the exact destinations before writing:
+## Command and hook table
 
-```bash
-npm exec --yes --package "$LITGROK_PACK" -- litgrok install --dry-run
-```
+### Prompt or route
 
-The installer verifies file ownership before upgrades or removal. Modified, foreign, or unsafe destination files cause the operation to refuse rather than overwrite them. `CI`, `NO_COLOR` (even empty), `--no-color`, and `--dry-run` are no-write previews regardless of `--yes`. Without `--yes`, a non-interactive run is also a no-write preview; with `--yes`, it proceeds without a TTY as long as none of the above apply.
-
-For a local-package install, remove it with the same package in the same project. Add `--user` only to remove an installation made with `--user`.
-
-```bash
-npm exec --yes --package "$LITGROK_PACK" -- litgrok uninstall
-```
-
-Registry uninstall commands:
+Grok Build uses the explicit `/litwork` route for a bounded task. It owns model execution; LitGrok leaves skills, rules, and checked next steps in the project.
 
-```bash
-npm exec --yes --package @litfamily/litgrok@latest -- litgrok uninstall
-npm exec --yes --package @litfamily/litgrok@latest -- litgrok uninstall --user
-```
+| Prompt or route | Effect |
+| --- | --- |
+| `/litwork` | Start the shipped work checklist in Grok Build. |
+| `handoff` or `/lit-handoff` | Carry the checked result and next step into another session. |
+| `/lit-plan` | Write a plan with concrete checks. |
+| `/start-work <approved-plan>` | Execute an approved plan. |
+| `/review-work` | Review a change and its evidence. |
+| `/litresearch` | Run bounded, source-traceable research without overstating evidence. |
 
-User-level uninstall backs up `~/.grok/config.toml` before removing the unchanged LitGrok-managed status-line keys; other settings and a user-edited status line are preserved. Match the scope used for installation. Re-run `install` to update. The installer does not grant hook trust, create a Git root, write login state or API keys, or choose a model. The hedge guard is fail-open on host errors; a passing package test does not prove live Grok behavior. Check `/hooks` and `grok inspect --json` from the repository root in your own session. [Host boundaries and verification](./docs/reference.md#verify).
+### Skill catalogue
 
-## Documentation
+| Need | Skill |
+|---|---|
+| Clarify a vague request | [`/deep-interview`](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/.grok/skills/deep-interview/SKILL.md) |
+| Write a plan with concrete checks | [`/lit-plan`](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/.grok/skills/lit-plan/SKILL.md) |
+| Execute an approved plan | [`/start-work`](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/.grok/skills/start-work/SKILL.md) |
+| Keep one task bounded and verifiable | [`/litwork`](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/.grok/skills/litwork/SKILL.md) |
+| Review a change and its evidence | [`/review-work`](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/.grok/skills/review-work/SKILL.md) |
+| Leave a resumable handoff | [`/lit-handoff`](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/.grok/skills/lit-handoff/SKILL.md) |
 
-- [Operational reference](./docs/reference.md): installation, hooks, terminal output, payload checks, and source provenance.
-- [Project rule](./.grok/rules/00-litgrok.md) and [skill catalog](./.grok/skills/).
-- [Changelog](./CHANGELOG.md) and [license](./LICENSE).
+Use `/skills` for all 34 skills. [Rename compatibility](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/docs/reference.md#skill-rename-compatibility) covers the one-release aliases; old slash routes are not guaranteed.
 
-- [Contributing](./CONTRIBUTING.md), [security](./SECURITY.md), [conduct](./CODE_OF_CONDUCT.md), and [support](./SUPPORT.md).
-- [Privacy and local data](./docs/privacy.md); [migration from the old npm name](./docs/reference.md#npm-package-migration).
+### Project hooks
 
-## LITFAMILY
+| Surface | Registration and boundary |
+| --- | --- |
+| Project hooks | Eleven registrations are declared in [`hooks/hooks.json`](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/hooks/hooks.json). They require a trusted Git root and `/hooks-trust`; a plain folder may load skills and rules without hooks. |
 
-![Five armored machines representing LitClaude, LitHermes, LitCodex, LitOpenCode, and LitGrok](./docs/assets/litfamily-machines.png)
+## Troubleshooting
 
-An editorial illustration of five armored machines representing the products. Each works independently in its own host; they do not need to be installed together or connected to one another.
+### Project hooks
 
-## LIT mark
+Project hooks need a trusted Git project root in Grok Build. A plain folder can still load the installed skills and rules while hooks remain unavailable. For a new disposable project, run `git init` yourself before trusting it; for an existing repository, open Grok Build from its actual root. The installer never runs `git init` or changes trust. In the observed Grok Build 1.0.23 host, `grok --trust inspect --json` accepted the trust-and-inspect route even though `--trust` was omitted from `grok --help`; this is version-specific behavior.
 
-<p align="center"><img src="./docs/assets/readme/ascii-readme.svg" width="480" alt="LIT ASCII B mark — Grok" /></p>
+### Install preview
 
-<details>
-<summary>Copy ASCII logo</summary>
+If `CI` or `NO_COLOR` is set, even to an empty value, installation is a no-write preview. So is `--no-color`. Without `--yes`, a non-interactive run is also a no-write preview; with `--yes`, installation proceeds without a TTY as long as none of the above apply. Check that the installer reports actual writes before continuing.
 
-```text
-                             ▄▄▄▄
-                   ▗███▌   ▗██████▖
- ▗▄▄▄▄▄          ▗▟████▌   ▝██████▘
- ▐█████        ▗▟██████▌    ▝▀▜█▀▘
- ▐█████      ▗▟███████▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
- ▐█████    ▗▟█████████████████████████ ▐█▀
- ▐█████    ████████████████████████████▀
- ▐█████    ██▛▘   ▄ ▄▄▄▄▖▄▄▄▄▄▄▄▄▄▄▄▄▄▖
- ▐█████    ▀    ▄██ ████▌█████████████▌
- ▐█████       ▄████ ████▌█████████████▌
- ▐█████     ▄█████▛
- ▐█████  ▗▟█████▀▘       ▄▄▄▄▄     ▗▖
- ▐█████ ▐█████▀          █████     ▐▛▀
- ▐█████ ▐███▀            █████
- ▐█████ ▐█▀              █████
- ▐█████ ▝                █████
- ▐█████▄▄▄▄▄▄▄▖          █████
- ▐███████████▛           █████
- ▐██████████▀            █████
+**Status row missing:** the persistent row is optional and uses user or administrator configuration; project and plugin configuration are not read for this setting. See the [status-line reference](https://docs.x.ai/build/features/status-line).
 
+For host limits and current verification steps, see the [operational reference](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/docs/reference.md#verify).
 
-grok
-```
+## Links
 
-</details>
+- [Operational reference](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/docs/reference.md): installation, hooks, terminal output, payload checks, and source provenance.
+- [Project rule](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/.grok/rules/00-litgrok.md) and [skill catalog](https://github.com/wjgoarxiv/litgrok/tree/main/.grok/skills).
+- [Changelog](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/CHANGELOG.md) and [license](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/LICENSE).
 
-## Ignition motion
+- [Contributing](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/CONTRIBUTING.md), [security](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/SECURITY.md), [conduct](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/CODE_OF_CONDUCT.md), and [support](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/SUPPORT.md).
+- [Privacy and local data](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/docs/privacy.md); [migration from the old npm name](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/docs/reference.md#npm-package-migration).
 
-Brand motion, not a recording of a Grok task execution.
+### LITFAMILY
 
-[![Ignition motion poster](./docs/assets/readme/ignition-poster.png)](./docs/assets/readme/ignition-film.mp4)
+![LITFAMILY static cover with five armored machines beneath the words KEEP THE WORK LIT.](https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.6/docs/assets/cover.webp)
 
-[10-second film · MP4](./docs/assets/readme/ignition-film.mp4) · [Animated version · GIF](./docs/assets/readme/ignition-readme.gif)
+The static cover shows five armored machines representing the products. Each works independently in its own host; they do not need to be installed together or connected to one another.