@litfamily/litclaude 1.0.7 → 1.0.9

package/CHANGELOG.md

@@ -1,5 +1,18 @@
 # Changelog
 
+## 1.0.9
+
+- Add README Studio with visual decoration patterns, cover depth, and a bounded multi-round design interview.
+- Move new LitClaude OpenAI planning, review, lead, and helper routes to the GPT-6 family defaults.
+- Align the English and Korean README pages to the family layout and pin npm-served asset URLs to this package version.
+- Compare the ignition mark after stripping terminal color so the activation test checks visible text across styles.
+
+## 1.0.8
+
+- Paint the activation logo and its `🔥 LIT IGNITED · <discipline> 🔥` label with a bold truecolor gradient that runs from ignition orange through the HUD hot pink to electric cyan. The hook sets the colour depth itself because its output is always piped, so terminal detection cannot drop it to monochrome; `NO_COLOR` still prints plain text, and the reply line the model is asked to print stays free of escape codes.
+- Show a bold, ignition-orange `🔥 LIT IGNITED · <discipline> 🔥` mark in the HUD status line whenever the prompt hook activates a LitClaude discipline. The prompt hook records the selected discipline per session under `litclaude-hud/` in the per-user temp directory (`LITCLAUDE_HUD_STATE_ROOT` overrides it; the repository state root and home directory stay untouched), and the HUD reads that record back, so the mark reflects the hook's decision rather than model output. Turns without an activation clear the record and the mark disappears.
+- Ask model replies to start with `🔥 **LIT IGNITED · <discipline>** 🔥`, while hook messages and the HUD render the same activation mark without Markdown.
+
 ## 1.0.7
 
 - Add the animated cover to both README pages, with a static cover for reduced-motion settings.
@@ -85,9 +98,9 @@
   fallback, and plain text for non-UTF-8 or dumb terminals. Keep the install-plan
   frame and add `--help`. Respect NO_COLOR, piped output, JSON, and CI.
 - Render a standard mark once per session through the SessionStart system message
-  and a micro mark with the discipline on prompt activation. Preserve the session
+  and an ignition mark with the discipline on prompt activation. Preserve the session
   receipt across resume and compaction. Model replies begin with exactly one
-  `▲ LIT · <discipline>` probe line; the model does not redraw the harness mark.
+  `🔥 **LIT IGNITED · <discipline>** 🔥` probe line; the model does not redraw the harness logo.
   Refresh skill-resource pins and verify runtime closures before the major version transition.
 
 - Rename skills: `hyperplan` → `lit-crucible`, `init-deep` → `lit-init`,

package/README.md

@@ -1,15 +1,14 @@
-<p align="center"><picture><source media="(prefers-reduced-motion: reduce)" srcset="https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.7/docs/assets/cover.webp" /><img src="https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.7/docs/assets/cover-motion.webp" width="100%" alt="LitClaude cover art. An orange signal moves through orbital paths above the CLAUDE CODE wordmark. The static family cover appears for reduced-motion preference." /></picture></p>
-<p align="center"><a href="https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.7/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/litclaude@1.0.9/docs/assets/cover-motion-still.webp" /><img src="https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/docs/assets/cover-motion.webp" width="100%" alt="LitClaude cover art. An orange signal moves through orbital paths above the CLAUDE CODE wordmark. Reduced-motion users see a still frame from this motion cover." /></picture></p>
+<p align="center"><a href="https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/docs/assets/cover.webp">View the static cover</a></p>
 
 <h1 align="center">LitClaude</h1>
 <p align="center"><strong>Keep the work lit.</strong></p>
-<p align="center">A spark has been placed in your hands.<br />Give it somewhere to stay.</p>
 <p align="center">Plan, build, and check your work in Claude Code. Leave the next session a place to begin.</p>
 <p align="center">
-  <a href="#install">Install</a> · <a href="#first-use">First result</a> · <a href="#carry-the-work-forward">Continue</a> · <a href="#core-routes">Core routes</a> · <a href="./README_ko-KR.md">한국어</a>
+  <a href="#install">Install</a> · <a href="#quick-start">Quick start</a> · <a href="#core-routes">Core routes</a> · <a href="#links">Links</a> · <a href="https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/README_ko-KR.md">한국어</a>
 </p>
 
-<p align="center"><img src="./docs/assets/readme/ascii-readme.svg" width="480" alt="LIT ASCII B mark" /></p>
+<p align="center"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/docs/assets/readme/ascii-readme.svg" width="480" alt="LIT ASCII B mark" /></p>
 
 <details>
 <summary>Copy ASCII logo</summary>
@@ -39,75 +38,23 @@
 
 </details>
 
-<p align="center"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.7/docs/assets/litclaude-wordmark.svg" width="480" alt="LITCLAUDE display type" /></p>
-<p align="center"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.7/docs/assets/litclaude-clay-icon.png" width="160" alt="LitClaude clay mark" /></p>
+<p align="center"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/docs/assets/litclaude-wordmark.svg" width="480" alt="LITCLAUDE display type" /></p>
+<p align="center"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/docs/assets/litclaude-clay-icon.png" width="160" alt="LitClaude clay mark" /></p>
 
 <p align="center">
-  <img src="https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.7/docs/assets/readme/badge-version.svg" alt="1.0.7" />
-  <a href="./LICENSE"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.7/docs/assets/readme/badge-license.svg" alt="MIT license" /></a>
+  <img src="https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/docs/assets/readme/badge-version.svg" alt="1.0.9" />
+  <a href="https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/LICENSE"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/docs/assets/readme/badge-license.svg" alt="MIT license" /></a>
 </p>
 
 <p align="center">
-  <a href="#deeper-docs"><img src="./docs/assets/readme/lucide-book-open.svg" width="16" alt="" /> Docs</a> · <a href="./docs/assets/readme/ignition-film.mp4"><img src="./docs/assets/readme/lucide-play.svg" width="16" alt="" /> Ignition</a> · <a href="./LICENSE"><img src="./docs/assets/readme/lucide-shield-check.svg" width="16" alt="" /> MIT</a>
+  <a href="#deeper-docs"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/docs/assets/readme/lucide-book-open.svg" width="16" alt="" /> Docs</a> · <a href="https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/docs/assets/readme/ignition-film.mp4"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/docs/assets/readme/lucide-play.svg" width="16" alt="" /> Ignition</a> · <a href="https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/LICENSE"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/docs/assets/readme/lucide-shield-check.svg" width="16" alt="" /> MIT</a>
 </p>
 
-## Start with one lit task
-
-Append `lit` to the end of a prompt to activate the Claude Code hook. It supplies routing guidance; Claude Code still performs the work.
-
-| Prompt or route | Effect |
-| --- | --- |
-| `lit` | Activate the evidence-first work loop in the current Claude Code conversation. |
-| `handoff` | Carry the checked result and next step into another session. |
-| `lit-plan` | Write a bounded plan and its checks before implementation. |
-| `/litclaude:start-work <approved-plan>` | Execute a plan that has already been approved. |
-| `review-work` | Read the change and evidence, then report remaining work. |
-| `litresearch` | Research with sources; this route records facts and uncertainty separately. |
-
-The hook marks entry into the workflow; it does not prove that a task or browser check finished.
-
-<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>
-
-The poster opens the optional Ignition film; this README keeps motion opt-in.
-
-## Practical routes and visual cues
-
-Use `lit` to activate the evidence-first loop, `handoff` to carry checked work forward,
-`lit-plan` to write a bounded plan, `/litclaude:start-work <approved-plan>` to execute an
-approved plan, `review-work` to inspect changes and evidence, and `litresearch` to keep sources
-and uncertainty separate. Each route leaves its expected effect in the project record; no new
-slash route is introduced here. Host limit: Claude Code owns the hook and model execution, while
-permissions, browser access, and visual checks remain host capabilities. A hook mark or static
-editorial image is not completion evidence.
-
-<p align="center"><img src="./docs/assets/litclaude-ignition-1600.webp" width="49%" alt="LitClaude ignition editorial cue" /> <img src="./docs/assets/litclaude-continuity-1600.webp" width="49%" alt="LitClaude continuity editorial cue" /></p>
-
-The retained `docs/assets/readme/ascii-readme.svg` and `docs/assets/cover.svg` remain editable or low-bandwidth fallbacks; the WebP above is the product emphasis export.
-
-
-
-## Leave a spark
-
-A bug you want fixed. A screen you want built. A project you want to finish.
-
-Starting takes a sentence. Then the conversation grows, the session ends, and you
-have to work out where you left off: what you decided, what you checked, what comes next.
-
-**LIT leaves that spark with the work.** A goal, a plan, the results you checked,
-and the next step stay in the project for the next session to read.
-
-**Leave something the next session can pick up.**
-
-LitClaude adds evidence-first execution, planning, research and review to Claude Code.
-Install its plugin and managed HUD once, then work in ordinary `claude` sessions.
-
 ## Install
 
 `@litfamily/litclaude` is the scoped package. You need Node.js/npm and Claude Code.
 For local validation, start with the
-[separate trial profile](./docs/migration.md#separate-trial-profile).
-If an existing installation returns `INSTALL_OWNERSHIP_CONFLICT`, stop retrying or
-moving directories and read the [ownership guidance](./docs/migration.md#ownership-conflicts).
+[separate trial profile](https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/docs/migration.md#separate-trial-profile).
 
 The default safe installation command is:
 
@@ -119,7 +66,7 @@ npm exec --yes --package @litfamily/litclaude@latest -- litclaude install --yes
 choose permissions, HUD accents or output styles explicitly when needed.
 See [installation reference](#installation-reference) for those options and a version pin.
 
-## First use
+## Quick start
 
 Start Claude Code normally:
 
@@ -149,7 +96,45 @@ the hook; namespaced slash commands use Claude Code's native command surface and
 do not double-activate the hook. For an explicit skill invocation, use a route
 such as `/litclaude:lit-loop`.
 
-## Carry the work forward
+## Key features
+
+A spark has been placed in your hands. Give it somewhere to stay.
+
+A bug you want fixed. A screen you want built. A project you want to finish.
+
+Starting takes a sentence. Then the conversation grows, the session ends, and you
+have to work out where you left off: what you decided, what you checked, what comes next.
+
+**LIT leaves that spark with the work.** A goal, a plan, the results you checked,
+and the next step stay in the project for the next session to read.
+
+**Leave something the next session can pick up.**
+
+LitClaude adds evidence-first execution, planning, research and review to Claude Code.
+Install its plugin and managed HUD once, then work in ordinary `claude` sessions.
+
+## Core routes
+
+### Start with one lit task
+
+Append `lit` to the end of a prompt to activate the Claude Code hook. It supplies routing guidance; Claude Code still performs the work.
+
+| Prompt or route | Effect |
+| --- | --- |
+| `lit` | Activate the evidence-first work loop in the current Claude Code conversation. |
+| `handoff` | Carry the checked result and next step into another session. |
+| `lit-plan` | Write a bounded plan and its checks before implementation. |
+| `/litclaude:start-work <approved-plan>` | Execute a plan that has already been approved. |
+| `review-work` | Read the change and evidence, then report remaining work. |
+| `litresearch` | Research with sources; this route records facts and uncertainty separately. |
+
+The hook marks entry into the workflow; it does not prove that a task or browser check finished.
+
+<p align="center"><a href="https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/docs/assets/readme/ignition-film.mp4"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/docs/assets/readme/ignition-poster.png" width="720" alt="Ignition motion poster" /></a></p>
+
+The poster opens the optional Ignition film; this README keeps motion opt-in.
+
+### Carry the work forward
 
 ```text
 Plan → Build → Check → Hand off
@@ -165,13 +150,104 @@ Plan → Build → Check → Hand off
 Goal-bound work records its state under the project's `.litclaude/litgoal/`.
 Keep the **actual file path** returned by the handoff. In a new session, open the same
 project and ask Claude to read that file, check the current state, and identify the
-next action. Then choose what to continue. The [goal and ledger reference](./docs/migration.md#review-and-litgoal-parity)
+next action. Then choose what to continue. The [goal and ledger reference](https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/docs/migration.md#review-and-litgoal-parity)
 explains the recording commands and host boundaries.
 
 The lasting spark means leaving work another session can pick up. It does not mean
 a process runs forever or automatically resumes after the session closes. Read the
 record and compare it with the current files before continuing.
 
+### Full route catalog
+
+| Type this | Purpose |
+| --- | --- |
+| `lit`, `litwork` | Evidence-first, test-first execution loop; also `$lit-loop`, `/lit-loop`, and `/litclaude:lit-loop` |
+| `lit plan <what>` | Planning only; also `$lit-plan` and `/lit-plan` |
+| `lit review <scope>` | Review a plan or completed work; also `$review-work` and `/review-work` |
+| `lit research <question>` | Cited public-source research; also `$litresearch` and `/litclaude:litresearch` |
+| `lit search <question>` | Public-source retrieval |
+| `lit query <question>` | Evidence lookup against durable local state |
+| `lit goal <outcome>` | Bind one objective and checkable criteria; also `$litgoal` and `/litgoal` |
+| `lit workflow <objective>` | Propose a Dynamic workflow for broad delegated work |
+| `lit team`, `lit teammates` | Propose native agent teams when `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1` is enabled and the user approves |
+| `$deep-interview`, `/deep-interview` | Turn an underspecified request into a decision-complete brief |
+| `lit recap`, `litrecap`, `$lit-recap`, `/lit-recap`, `/litclaude:lit-recap` | Read-only session recap |
+| `handoff`, `/litclaude:lit-handoff` | Write a verified continuation packet |
+| `lit-scientific-visualization` | Prepare publication figures; also `/litclaude:lit-scientific-visualization` |
+| `litclaude wikify <capture/save/review/query/config>` | Manage reviewed local structured knowledge |
+| `browser-drive`, `$browser-drive` | Drive a real page only after a capability probe verifies an external driver; never substitute a fetch, use credentials, or install without approval |
+
+Named workflow skills include `lit-crucible` (adversarial planning), `lit-init`
+(repository guidance), `lit-commit` (Git history), `lit-team` (native teams),
+`lit-burnoff` (change-set cleanup), `lit-burnoff-file` (single-file cleanup),
+`lit-korean` (Korean prose), and `lit-code` (implementation discipline).
+Use the leading bare name or `$<skill-id>`. Previous typed names remain aliases
+for one release and emit a deprecation note; see [the alias migration table](https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/docs/migration.md#one-release-rename-aliases).
+
+## Troubleshooting
+
+If an existing installation returns `INSTALL_OWNERSHIP_CONFLICT`, stop retrying or
+moving directories and read the [ownership guidance](https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/docs/migration.md#ownership-conflicts).
+
+### Verify and uninstall
+
+The installed package also exposes these useful commands:
+
+```bash
+npm exec --yes --package @litfamily/litclaude@latest -- litclaude doctor
+npm exec --yes --package @litfamily/litclaude@latest -- litclaude --version
+npm exec --yes --package @litfamily/litclaude@latest -- litclaude path
+npm exec --yes --package @litfamily/litclaude@latest -- litclaude workflow-check --json
+npm exec --yes --package @litfamily/litclaude@latest -- litclaude update
+npm exec --yes --package @litfamily/litclaude@latest -- litclaude uninstall
+```
+
+`uninstall` removes only LitClaude-managed plugin, HUD, permission, and local
+state entries. It does not remove unrelated Claude settings. Modified or unrecognized
+installations are preserved and refused; follow the [ownership guidance](https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/docs/migration.md#ownership-conflicts).
+After a separate-profile trial, close that Claude session and terminal and return to
+your original terminal environment. Your previous installation needs no downgrade
+or reinstall.
+
+## Links
+
+<a id="deeper-docs"></a>
+
+- [Operational reference](#operational-reference)
+- [Hook triggers and activation boundaries](https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/docs/hooks.md)
+- [Agent and orchestration guidance](https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/docs/agents.md)
+- [Workflow migration table](https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/docs/migration.md)
+- [Native `/goal` surface matrix](https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/docs/native-goal-surface.md)
+- [Workflow compatibility audit](https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/docs/workflow-compatibility-audit.md)
+- [Package-name migration and marketplace choices](https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/docs/migration.md#scoped-npm-migration)
+- [Contributing](https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/CONTRIBUTING.md) · [Support](https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/SUPPORT.md) · [Security](https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/SECURITY.md)
+- [Code of conduct](https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/CODE_OF_CONDUCT.md) · [Privacy and network behavior](https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/docs/privacy.md)
+- [Release history](https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/CHANGELOG.md)
+- [Korean README](https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/README_ko-KR.md)
+
+### LITFAMILY
+
+<p align="center"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/docs/assets/cover.webp" width="100%" alt="Five LitFamily robot companions beneath the words KEEP THE WORK LIT." /></p>
+
+<details>
+<summary>More workflows and references</summary>
+
+## Practical routes and visual cues
+
+Use `lit` to activate the evidence-first loop, `handoff` to carry checked work forward,
+`lit-plan` to write a bounded plan, `/litclaude:start-work <approved-plan>` to execute an
+approved plan, `review-work` to inspect changes and evidence, and `litresearch` to keep sources
+and uncertainty separate. Each route leaves its expected effect in the project record; no new
+slash route is introduced here. Host limit: Claude Code owns the hook and model execution, while
+permissions, browser access, and visual checks remain host capabilities. A hook mark or static
+editorial image is not completion evidence.
+
+<p align="center"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/docs/assets/litclaude-ignition-1600.webp" width="49%" alt="LitClaude ignition editorial cue" /> <img src="https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/docs/assets/litclaude-continuity-1600.webp" width="49%" alt="LitClaude continuity editorial cue" /></p>
+
+The retained `docs/assets/readme/ascii-readme.svg` and `docs/assets/cover.svg` remain editable or low-bandwidth fallbacks; the WebP above is the product emphasis export.
+
+
+
 ## Inside Claude Code
 
 A plain prompt and a slash command enter through different surfaces. Hooks pass
@@ -194,45 +270,32 @@ flowchart TD
 ```
 
 Hook guidance alone does not prove that a skill ran. The next session must read
-the saved file and check the actual state. See the [hook reference](./docs/hooks.md)
-and [goal recording reference](./docs/migration.md#review-and-litgoal-parity) for the boundaries.
+the saved file and check the actual state. See the [hook reference](https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/docs/hooks.md)
+and [goal recording reference](https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/docs/migration.md#review-and-litgoal-parity) for the boundaries.
 
 <details>
 <summary>LITFAMILY · five armored machines</summary>
 
-![Concept art showing the five LIT products as armored machines](./docs/assets/litfamily-machines.png)
+![Concept art showing the five LIT products as armored machines](https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/docs/assets/litfamily-machines.png)
 
 Five armored machines: LitClaude, LitHermes, LitCodex, LitOpenCode, and LitGrok.
 Concept art; each product runs in its own host.
 
 </details>
 
-## Core routes
+## Design and README production
 
-| Type this | Purpose |
-| --- | --- |
-| `lit`, `litwork` | Evidence-first, test-first execution loop; also `$lit-loop`, `/lit-loop`, and `/litclaude:lit-loop` |
-| `lit plan <what>` | Planning only; also `$lit-plan` and `/lit-plan` |
-| `lit review <scope>` | Review a plan or completed work; also `$review-work` and `/review-work` |
-| `lit research <question>` | Cited public-source research; also `$litresearch` and `/litclaude:litresearch` |
-| `lit search <question>` | Public-source retrieval |
-| `lit query <question>` | Evidence lookup against durable local state |
-| `lit goal <outcome>` | Bind one objective and checkable criteria; also `$litgoal` and `/litgoal` |
-| `lit workflow <objective>` | Propose a Dynamic workflow for broad delegated work |
-| `lit team`, `lit teammates` | Propose native agent teams when `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1` is enabled and the user approves |
-| `$deep-interview`, `/deep-interview` | Turn an underspecified request into a decision-complete brief |
-| `lit recap`, `litrecap`, `$lit-recap`, `/lit-recap`, `/litclaude:lit-recap` | Read-only session recap |
-| `handoff`, `/litclaude:lit-handoff` | Write a verified continuation packet |
-| `lit-scientific-visualization` | Prepare publication figures; also `/litclaude:lit-scientific-visualization` |
-| `litclaude wikify <capture/save/review/query/config>` | Manage reviewed local structured knowledge |
-| `browser-drive`, `$browser-drive` | Drive a real page only after a capability probe verifies an external driver; never substitute a fetch, use credentials, or install without approval |
+Use `frontend-ui-ux build <target>` for an authorized working interface and rendered
+inspection. Material ambiguity prompts a targeted question; answers carry forward into
+the build. Explicit review or plan requests remain read-only.
 
-Named workflow skills include `lit-crucible` (adversarial planning), `lit-init`
-(repository guidance), `lit-commit` (Git history), `lit-team` (native teams),
-`lit-burnoff` (change-set cleanup), `lit-burnoff-file` (single-file cleanup),
-`lit-korean` (Korean prose), and `lit-code` (implementation discipline).
-Use the leading bare name or `$<skill-id>`. Previous typed names remain aliases
-for one release and emit a deprecation note; see [the alias migration table](./docs/migration.md#one-release-rename-aliases).
+Use `readme-studio <repository or README scope>` or `$readme-studio` for a factual
+README and local cover production. Claude Code's available tools determine image
+generation: `IMAGE_GENERATION_UNAVAILABLE` is explicit, and an inspected supplied
+background can enable the remaining composition. Bundled helpers support outlined
+Pretendard/Meslo typography and pinned local motion recipes. Fonts, renderer licenses
+and actual output are checked; hosted GitHub/npm display remains a later gate.
+These are native skill/leading-token routes, with no new slash-command file.
 
 ## Safety
 
@@ -250,44 +313,19 @@ for one release and emit a deprecation note; see [the alias migration table](./d
 - Publishing, version changes, tags, and remote marketplace changes require
   explicit user approval.
 
-Model selection is host-owned. Native `Workflow` and experimental agent teams need
-explicit opt-in; the durable `litgoal` ledger remains authoritative when native goal
-tools are unavailable. LitClaude never sends `/goal` on your behalf.
-
-## Verify and uninstall
-
-The installed package also exposes these useful commands:
-
-```bash
-npm exec --yes --package @litfamily/litclaude@latest -- litclaude doctor
-npm exec --yes --package @litfamily/litclaude@latest -- litclaude --version
-npm exec --yes --package @litfamily/litclaude@latest -- litclaude path
-npm exec --yes --package @litfamily/litclaude@latest -- litclaude workflow-check --json
-npm exec --yes --package @litfamily/litclaude@latest -- litclaude update
-npm exec --yes --package @litfamily/litclaude@latest -- litclaude uninstall
-```
-
-`uninstall` removes only LitClaude-managed plugin, HUD, permission, and local
-state entries. It does not remove unrelated Claude settings. Modified or unrecognized
-installations are preserved and refused; follow the [ownership guidance](./docs/migration.md#ownership-conflicts).
-After a separate-profile trial, close that Claude session and terminal and return to
-your original terminal environment. Your previous installation needs no downgrade
-or reinstall.
-
-## Deeper docs
-
-- [Operational reference](#operational-reference)
-- [Hook triggers and activation boundaries](./docs/hooks.md)
-- [Agent and orchestration guidance](./docs/agents.md)
-- [Workflow migration table](./docs/migration.md)
-- [Native `/goal` surface matrix](./docs/native-goal-surface.md)
-- [Workflow compatibility audit](./docs/workflow-compatibility-audit.md)
-- [Package-name migration and marketplace choices](./docs/migration.md#scoped-npm-migration)
-- [Contributing](./CONTRIBUTING.md) · [Support](./SUPPORT.md) · [Security](./SECURITY.md)
-- [Code of conduct](./CODE_OF_CONDUCT.md) · [Privacy and network behavior](./docs/privacy.md)
-- [Release checklist](./RELEASE_CHECKLIST.md)
-- [Release history](./CHANGELOG.md)
-- [Korean README](./README_ko-KR.md)
+Model selection is host-owned. Across LitFamily products that own OpenAI routing, new
+installs default to GPT-6: `gpt-6-astra` for planning, review, and lead roles,
+`gpt-6-sol` as the coding-lead alternative, and `gpt-6-luna` for helpers and ordinary
+workers. GPT-6 Luna supports `xhigh` but not `ultra`. The live host catalog still lists
+`gpt-5.6-sol`, `gpt-5.6-terra`, and `gpt-5.6-luna` as selectable, with no retirement
+date for any of them. The catalog supports `xhigh` for `gpt-5.6-luna` too, but LitClaude
+keeps a legacy policy-only block for that combination; `gpt-6-luna` at `xhigh` remains
+catalog-supported while the approved ordinary-worker default stays `max`. Install and
+update leave an existing model selection unchanged.
+LitClaude does not apply those OpenAI routes; Claude Code owns model selection. Native
+`Workflow` and experimental agent teams need explicit opt-in; the durable `litgoal` ledger
+remains authoritative when native goal tools are unavailable. LitClaude never
+sends `/goal` on your behalf.
 
 <details>
 <summary>Operational reference — installation options, learning, host boundaries and development</summary>
@@ -303,7 +341,7 @@ or reinstall.
 - **Claude skills** also include `litwork`, `structural-search`, `lit-team`,
   `autoresearch`, and `autoconference`. The core sequence is
   `lit-plan`, `lit-recap`, `lit-loop`.
-- Auxiliary Skill-discovery entries `frontend-ui-ux`, `lit-commit`, `lsp-setup`,
+- Auxiliary Skill-discovery entries `frontend-ui-ux`, `readme-studio`, `lit-commit`, `lsp-setup`,
   and `visual-qa` answer to a leading bare token or `$frontend-ui-ux`; they are
   not anywhere-tokens.
 - Bundled reference packs include `lit-code/references`,
@@ -355,13 +393,13 @@ npm exec --yes --package @litfamily/litclaude@latest -- litclaude install
 For a reproducible install, pin the current package version:
 
 ```bash
-npm view @litfamily/litclaude@1.0.7 version
+npm view @litfamily/litclaude@1.0.9 version
 ```
 
-If that lookup returns `1.0.7`, the exact install is available:
+If that lookup returns `1.0.9`, the exact install is available:
 
 ```bash
-npm exec --yes --package @litfamily/litclaude@1.0.7 -- litclaude install
+npm exec --yes --package @litfamily/litclaude@1.0.9 -- litclaude install
 ```
 
 Otherwise, wait for explicit human publication before using that pin. Check the
@@ -413,6 +451,13 @@ Interactive installation previews the available HUD accents. The LitClaude HUD
 uses `[🔥LITCLAUDE vX.Y.Z]`, a compact `ctx [▎░░]` bar, and a `5h [▏░] 4% ↻`
 rate-limit reset countdown. Set `LITCLAUDE_HUD_ACCENT` before installation to
 choose an accent.
+When the prompt hook activates a LitClaude discipline, the HUD adds a bold,
+ignition-orange `🔥 LIT IGNITED · lit-loop 🔥` mark right after the brand until
+the next turn without an activation; the hook records the selected discipline
+per session under `litclaude-hud/` in the per-user temp directory, never in the
+repository or your home directory (`LITCLAUDE_HUD_STATE_ROOT` overrides the location).
+The reply starts with `🔥 **LIT IGNITED · <discipline>** 🔥`; the hook system
+message and HUD display the same mark without Markdown.
 
 HUD appearance and color capability are independent. By default (`dark`) the
 model, context, usage, reset, and Git text carry the selected accent, usage
@@ -437,7 +482,7 @@ litclaude install
 
 ## Claude Code integration
 
-**Where Claude Code hands control to LitClaude.** Session and tool events feed the rules, routing, authority, and ledger surfaces; together they expose the package's 33 skills, 16 current commands, two hidden compatibility redirects, and 11 agents without hiding the host boundary.
+**Where Claude Code hands control to LitClaude.** Session and tool events feed the rules, routing, authority, and ledger surfaces; together they expose the package's 34 skills, 16 current commands, two hidden compatibility redirects, and 11 agents without hiding the host boundary.
 
 ```mermaid
 flowchart LR
@@ -458,7 +503,7 @@ flowchart LR
     H5 --> LEDGER
     H6 --> LEDGER
     H7 --> LEDGER
-    LC --> S["33 skills · 16 commands · 11 agents"]
+    LC --> S["34 skills · 16 commands · 11 agents"]
 ```
 
 **Why a fresh install can still execute the skills.** A self-contained skill needs an explicit allowlist reason, while a skill that names a corpus must carry that corpus inside the packed tarball. These payload gates prevent a checkout-only reference from becoming a user's runtime failure.
@@ -586,6 +631,8 @@ Reload plugin metadata inside Claude Code with:
 
 This is a brand film, not a recording of the plugin in use. Select the static poster to play it.
 
-[![Ignition motion graphic](./docs/assets/readme/ignition-poster.png)](./docs/assets/readme/ignition-film.mp4)
+[![Ignition motion graphic](https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/docs/assets/readme/ignition-poster.png)](https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/docs/assets/readme/ignition-film.mp4)
+
+[Animated version (GIF)](https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/docs/assets/readme/ignition-readme.gif) · [Lucide icon license (ISC)](https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/docs/assets/readme/Lucide-LICENSE.txt) · [JetBrains Mono font license (OFL)](https://cdn.jsdelivr.net/npm/@litfamily/litclaude@1.0.9/docs/assets/readme/JetBrainsMono-OFL.txt)
 
-[Animated version (GIF)](./docs/assets/readme/ignition-readme.gif) · [Lucide icon license (ISC)](./docs/assets/readme/Lucide-LICENSE.txt) · [JetBrains Mono font license (OFL)](./docs/assets/readme/JetBrainsMono-OFL.txt)
+</details>