litclaude-ai 0.2.2

package/CHANGELOG.md

@@ -0,0 +1,155 @@
+# Changelog
+
+## Unreleased — LazyClaude → LitClaude rebrand
+
+- Rename the project from **LazyClaude / `lazyclaude-ai`** to **LitClaude / `litclaude-ai`**
+  end-to-end: npm package, `litclaude`/`litclaude-ai` bins, `plugins/litclaude/` payload, installer
+  identifiers (`litclaude@litclaude-ai`), 13 `LITCLAUDE_*` env vars, per-project state dir
+  `.litclaude/` (was `.omo/`), HUD banner `[LitClaude vX.Y.Z]` (dropped the 💤), and the 7
+  `litclaude:*` slash commands. See `docs/migration.md` for the upgrade guide.
+- Add a fail-closed legacy-token scanner (`tools/scan-legacy-tokens.mjs`) + allowlist that keeps the
+  shipped surface free of legacy and upstream-lineage tokens and the source-origin handle;
+  `ulw`/`ultrawork` are kept as own vocabulary.
+- Add a no-publish CI workflow (`.github/workflows/ci.yml`, `permissions: contents: read`) plus
+  version-lockstep, CI-integrity, and pack-payload hardening gates.
+- Make the atomic state store durable (fsync), remove the ported `codex:` session-id residue (Claude
+  host semantics), and replace brittle `import.meta.url.pathname` with `fileURLToPath` for
+  spaced/`#`/non-ASCII workspace paths.
+- **Version for the first public `litclaude-ai` release is pending user confirmation (proposed
+  `1.0.0`). No `npm publish` or push has occurred.**
+
+## 0.2.2 - 2026-06-07
+
+- Harden Dynamic workflow delegation with an explicit child-assignment
+  contract: `TASK:`, `DELIVERABLE`, `SCOPE`, and `VERIFY`, plus bounded wait and
+  fallback rules for missing deliverables, acknowledgement-only replies, and
+  `BLOCKED:` reports.
+- Add `litclaude-ai start-work-next --json` so long `$start-work` runs can
+  resume from `.litclaude/boulder.json` and `.litclaude/start-work/ledger.jsonl` without
+  guessing the next unchecked top-level plan item.
+- Make PostToolUse guidance name actual mutated files for write/edit/multiedit,
+  notebook, and patch-shaped tool inputs, and add bounded SessionStart resume
+  guidance when transcript context-pressure markers are detected.
+- Extend `workflow-check --json` with subagent reliability and command/hook
+  agreement checks.
+
+## 0.2.1 - 2026-06-04
+
+- Add a dedicated `/dynamic-workflow` route for Dynamic workflow bootstrap,
+  native `/goal` fallback guidance, and Claude Code subagent delegation.
+- Add `litclaude-ai workflow-check --json` so operators can verify goal,
+  Dynamic workflow, hook route, and subagent delegation readiness before full QA.
+- Fix the right-pane `test/` local-session ignore pattern so ad hoc Claude Code
+  session artifacts stay out of git and package payloads.
+
+## 0.2.0 - 2026-06-03
+
+- Align the package and Claude plugin manifests to `litclaude-ai@0.2.0` for
+  the workflow parity release candidate.
+- Add the `review-work` 5-lane review route and document its goal/constraint
+  verification, hands-on QA execution, code quality, security, and local-first
+  context mining lanes.
+- Add the `ultragoal` CLI/runtime surface for durable criteria, evidence,
+  checkpoints, steering, and review blocker records under `.litclaude/ultragoal/`.
+- Keep the release boundary explicit: this version is prepared for verification
+  and publication approval, but no npm publish or marketplace publication is claimed
+  here.
+
+## 0.1.18 - 2026-06-02
+
+- Shorten the HUD into compact HUD bars with a three-cell context gauge and
+  two-cell rate-limit gauges for tighter Claude Code status-line space.
+- Replace muted installer choices with vivid HUD color choices and shared
+  mini-HUD previews for all ten brand accent themes.
+- Apply the selected accent as a broader brand accent across separators,
+  labels, brackets, reset text, and git metadata.
+
+## 0.1.17 - 2026-06-02
+
+- Render a dense bracketed context bar in the HUD, for example
+  `ctx [▉░░░░░░░░░] 9%/1000k`.
+- Show low non-zero rate-limit usage with partial bar glyphs so 1% and 7% no
+  longer look empty, and add spacing before the `↻` reset countdown.
+- Add more eye-catching installer color labels for animated `npx` installs
+  while preserving deterministic plain `INSTALL_STEP` output in CI.
+
+## 0.1.16 - 2026-06-02
+
+- Show compact HUD rate-limit reset countdowns with a `↻` suffix and parse
+  Claude Code's epoch-second `rate_limits.*.resets_at` fields as well as ISO
+  timestamps.
+- Add `/deep-interview`, `$deep-interview`, and
+  `/litclaude:deep-interview` routing for a Socratic requirements mode before
+  planning or implementation.
+- Ship the `deep-interview` skill and its progress renderer, plus English and
+  Korean README guidance for when to chain it into `/ulw-plan` or `/ulw-loop`.
+
+## 0.1.15 - 2026-06-01
+
+- Add an install-time LitClaude HUD brand color picker with immediate ANSI
+  previews for each `[LitClaude vX.Y.Z]` choice.
+- Persist the selected HUD accent in Claude `settings.json` and inject it into
+  the managed `statusLine` command through `LITCLAUDE_HUD_ACCENT`.
+- Allow noninteractive installs to keep the default LitClaude cyan accent
+  without hanging CI, postinstall, or fresh-machine smoke tests.
+
+## 0.1.14 - 2026-06-01
+
+- Ignore Claude Code command XML transcript packets such as
+  `<command-name>...</command-name>` when selecting the HUD's latest user prompt
+  preview, so command metadata never appears as the second HUD line.
+- Add the sleepy LitClaude HUD prefix `[LitClaude vX.Y.Z]` while preserving
+  the compact context, rate-limit, and git segments.
+
+## 0.1.13 - 2026-06-01
+
+- Fix short slash ULW routing so `/ulw-plan`, `/ulw-loop`, and `/start-work`
+  map to their matching LitClaude disciplines instead of falling through to
+  plain `ulw` loop activation.
+- Preserve punctuation-delimited triggers such as `ulw.` and `/ulw-plan, ...`
+  while ignoring hyphenated near-misses such as `/ulw-plan-ish`.
+- Round HUD context/rate-limit percentages before rendering, so floating-point
+  values such as `7.000000000000001%` never leak into the status line.
+- Ignore transcript entries that start with `<local-command-stdout>` or
+  `<local-command-stderr>` when selecting the HUD's latest user prompt preview.
+- Document the short slash aliases in English/Korean README and hook docs.
+
+## 0.1.12 - 2026-06-01
+
+- Recover from the npm publish rejection for already-published `0.1.11` by
+  preparing a new `litclaude-ai@0.1.12` package version.
+- Include the source-checkout npx shim so same-name checkout installs can
+  resolve the package-name executable.
+- Add installer progress output with animated TTY spinner frames and
+  deterministic CI-safe `INSTALL_STEP` logs.
+
+## 0.1.11 - 2026-06-01
+
+- Add `litclaude-ai --version` / `litclaude-ai -v` for quick package smoke
+  checks without requiring install state.
+- Align package, plugin, README, HUD examples, release checklist, and cover image
+  generation to `litclaude-ai@0.1.11`.
+- Refresh README, reference metadata, and workflow
+  compatibility audit wording.
+- Deepen trigger-specific hook routing for `$ulw-plan`, `$ulw-loop`, and
+  `$start-work`, with safer post-edit diagnostic guidance.
+
+## 0.1.10 - 2026-06-01
+
+- Install a LitClaude-branded Claude Code statusLine HUD automatically during
+  `litclaude install`, with safe previous-statusLine restoration on uninstall.
+
+## 0.1.8
+
+- Teach `litclaude doctor` to separate LitClaude's own LSP declaration from
+  external Claude Code LSP plugin binary warnings.
+
+## 0.1.7
+
+- Expand the workflow compatibility audit beyond skill frontmatter into upstream legacy
+  component coverage.
+- Ship the original `ai-slop-remover` skill alias alongside the LitClaude
+  `remove-ai-slops` skill.
+- Include LitClaude programming and debugging auxiliary reference packs so the
+  Claude plugin carries the same deep language/runtime guidance, not only short
+  summary skills.

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 LitClaude contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,369 @@
+<p align="center"><img src="./cover.png" width="100%" /></p>
+
+<h1 align="center">LitClaude</h1>
+<p align="center">
+  <em>Claude Code-native LitClaude workflows: prompt hooks, litwork skills, agents, MCP, and LSP helpers.</em>
+</p>
+<p align="center">
+  <a href="#quick-start">Quick Start</a> · <a href="#lit-usage">LIT Usage</a> · <a href="#commands">Commands</a> · <a href="./README_ko-KR.md">한국어</a>
+</p>
+<p align="center">
+  <img src="https://img.shields.io/badge/npm-litclaude--ai-cb3837" />
+  <img src="https://img.shields.io/badge/version-0.2.2-2ea44f" />
+  <img src="https://img.shields.io/badge/Claude%20Code-plugin-blueviolet" />
+  <img src="https://img.shields.io/badge/license-MIT-blue" />
+</p>
+
+---
+
+> [!NOTE]
+> LitClaude is a quiet Claude Code-native workflow package for prompt hooks,
+> skills, agents, MCP, LSP, and LIT discipline. It installs as
+> `litclaude@litclaude-ai`, so normal `claude` launches can load the
+> LitClaude skills and hooks without a long `--plugin-dir` command.
+
+This checkout is prepared as `litclaude-ai@0.2.2` for personal install
+convenience. The repo can remain quiet; preparing npm package metadata here does
+not imply public repo promotion, marketplace publication, or advertisement.
+Future package releases still require explicit user approval. The v0.2.2
+release materials preserve the v0.2.0 workflow parity work, add Dynamic
+workflow hardening on top of v0.2.1 readiness, describe LitClaude in its own
+terms, and do not claim that npm publication has completed.
+
+## Features
+
+- **Natural Claude launch** - install once with `npx`, then run plain `claude`
+- **LIT prompt hooks** - type `lit`, `litwork`, `$lit-plan`, or `$lit-loop`
+- **Deep interview mode** - type `/deep-interview` or `$deep-interview` to
+  turn broad intent into a spec before planning or implementation
+- **v0.2.0 workflow parity** - adds `review-work` 5-lane review discipline and
+  litgoal runtime docs without claiming a package publication has completed
+- **v0.2.2 Dynamic workflow hardening** - adds stricter subagent assignment
+  contracts, `start-work-next`, context-pressure resume guidance, precise
+  mutated-file detection, and richer `workflow-check --json` readiness checks
+- **5-lane review** - `/review-work` checks goal/constraint verification,
+  hands-on QA execution, code quality, security, and local-first context mining
+- **Native goal guidance** - LIT context points Claude toward `/goal` or
+  model-facing `get_goal`, `create_goal`, and delayed `update_goal` when those
+  surfaces exist, and gives a clear fallback when goal tools are unavailable
+- **Litgoal CLI/state** - `plugins/litclaude/lib/litgoal/` records durable
+  criteria, evidence, checkpoints, steering, and review blockers under
+  `.litclaude/litgoal/`
+- **Dynamic workflow/worktree guidance** - large or parallel tasks are steered
+  toward Claude Code Dynamic workflow orchestration, subagent delegation, and
+  Dynamic worktree isolation
+- **Claude skills** - a richer LitClaude-owned corpus: `programming`,
+  `debugging`, `refactor`, `ai-slop-remover`, `remove-ai-slops`, `review-work`,
+  `frontend-ui-ux`, `comment-checker`, `rules`, `lsp`, `litgoal`,
+  `deep-interview`, `lit-plan`, `lit-loop`, and `start-work`
+- **Auxiliary workflow packs** - ships `programming/references`,
+  `programming/scripts`, and `debugging/references` for deeper language and
+  runtime guidance
+- **Workflow agents** - planner, executor, verifier, reviewer, librarian, and QA runner
+- **Local marketplace registration** - Claude can resolve `claude plugin details litclaude@litclaude-ai`
+- **MCP and LSP helpers** - plugin-local stdio MCP plus TypeScript-family LSP doctor
+- **LitClaude HUD** - npm install configures a compact Claude Code statusLine
+  based on `pretty-claude-hud`, branded as a neon `[🔥LITCLAUDE vX.Y.Z]`
+  (truecolor hot-pink→cyan gradient, bright-magenta on 256-color terminals), with
+  install-time vivid color selection, live mini-HUD previews, compact context
+  bars, visible low-usage rate-limit bars, broader brand accent coverage, and
+  spaced reset countdowns
+- **Safe uninstall** - removes only LitClaude-managed state
+
+## Quick Start
+
+### Install
+
+```bash
+npx --yes litclaude-ai install
+```
+
+During an interactive `npx` install, LitClaude shows every HUD brand color as
+a vivid live terminal preview and writes the selected accent into the managed
+Claude `statusLine` command. Animated installs also use colored setup, plugin,
+marketplace, registry, and cache labels so progress is easier to scan.
+Noninteractive installs keep deterministic plain `INSTALL_STEP` lines.
+
+If you are currently inside this repository checkout, which has the same
+package name as the registry package, older published builds such as
+`npx --yes litclaude-ai@0.1.11 install` could resolve the local same-name
+source checkout and fail with `sh: litclaude-ai: command not found`. This
+checkout intentionally does not track a `node_modules/.bin` shim. From a fresh
+directory, the normal install command works:
+
+```bash
+cd /tmp
+npx --yes litclaude-ai@0.2.2 install
+```
+
+Validate the installed plugin:
+
+```bash
+npx --yes litclaude-ai doctor
+```
+
+The installer also sets Claude Code's `statusLine` command to the packaged
+LitClaude HUD. A typical no-color render starts like:
+
+```text
+[🔥LITCLAUDE v0.2.2] | O4.8 │ ctx [▎░░] 9%/1000k │ 5h [▏░] 4% ↻2h15m │ 1w [▊░] 35% ↻3d6h │ git main +3 ✓
+```
+
+The `↻` suffix is a compact rate-limit reset countdown. It is separated from
+the percentage for readability, and low non-zero percentages still get a
+partial bar glyph instead of looking empty. The context bar uses three cells
+and the rate-limit bars use two cells so the HUD stays tight in Claude Code's
+status-line space. Claude Code reports reset windows as epoch seconds, and
+LitClaude also accepts ISO reset timestamps for compatibility with test
+fixtures and older status-line helpers.
+
+To override the accent without the picker, set `LITCLAUDE_HUD_ACCENT` to one
+of `cyan`, `blue`, `teal`, `green`, `lavender`, `rose`, `gold`, `orange`,
+`slate`, or `gray` before installing.
+
+Launch Claude Code normally:
+
+```bash
+claude
+```
+
+### Alternative Entrypoints
+
+```bash
+bunx litclaude-ai install
+npm install -g litclaude-ai
+litclaude install
+```
+
+If you need the explicit `npm exec` form while standing inside the source
+checkout, use a fresh prefix so npm does not confuse the registry package with
+a same-name source checkout:
+
+```bash
+npm exec --prefix "$(mktemp -d)" --yes --package litclaude-ai -- litclaude install
+```
+
+Remove only LitClaude-managed install state:
+
+```bash
+npx --yes litclaude-ai uninstall
+```
+
+## How Install Works
+
+The installer registers `litclaude@litclaude-ai` in Claude Code's user plugin
+registry under `~/.claude/plugins`, enables it in `settings.json`
+`enabledPlugins`, and writes a LitClaude-managed local marketplace entry in
+`known_marketplaces.json`. That marketplace metadata is what lets Claude show
+the skill and hook inventory in `claude plugin details`.
+
+Use `CLAUDE_CONFIG_DIR=/some/path` and `LITCLAUDE_HOME=/some/path` only for
+isolated tests.
+
+## LIT Usage
+
+After install, start Claude Code:
+
+```bash
+claude
+```
+
+Then type one of these prompts:
+
+```text
+lit
+litwork
+$lit-plan <what you want planned>
+/lit-plan <what you want planned>
+$lit-loop <what you want executed with evidence>
+/lit-loop <what you want executed with evidence>
+$deep-interview <what needs clarification>
+/deep-interview <what needs clarification>
+$dynamic-workflow <parallel or delegated objective>
+/dynamic-workflow <parallel or delegated objective>
+$review-work <scope to review>
+/review-work <scope to review>
+$litgoal <goal operation>
+/litgoal <goal operation>
+$start-work plans/example-plan.md
+/start-work plans/example-plan.md
+```
+
+Expected behavior: LitClaude's prompt hook adds `LITWORK MODE ENABLED`
+context for LIT routes and shows `LitClaude lit hook active` as a visible hook
+message. For `/deep-interview`, the hook adds `DEEP INTERVIEW MODE ENABLED`
+context and routes Claude toward `/litclaude:deep-interview` /
+`Skill(deep-interview)`. Plain `lit` still maps to `/litclaude:lit-loop` /
+`Skill(lit-loop)` semantics before ordinary task execution, then the matching
+skill and agent instructions steer Claude toward test-first work, native goal
+handling, manual QA evidence, cleanup receipts, and explicit approval before
+future release steps.
+
+LitClaude does not auto-type `/goal` or send slash command text for you.
+Instead, the hook and LIT skills add run-context guidance: use Claude Code's
+native goal surface when available, inspect `get_goal`, call `create_goal` only
+when no matching goal is active, and reserve `update_goal` for verified
+completion or a genuine blocker. When goal tools are unavailable or not exposed,
+LitClaude keeps the local evidence ledger authoritative and may suggest an
+exact `/goal <completion condition>` before long execution without repeatedly
+printing fallback chatter.
+For large independent work, LitClaude applies the same principle to Claude
+Code's available orchestration surfaces: when `Workflow` is exposed, call the
+`Workflow` tool; when isolated edits need a model-facing worktree lane, use
+`EnterWorktree`. If only the CLI surface is available for a fresh isolated lane,
+use `claude --worktree <short-name> --tmux`.
+
+For v0.2.2 Dynamic workflow hardening, `/dynamic-workflow` is the consolidated
+bootstrap route for broad delegated work. It keeps `/goal` user-controlled,
+checks model-facing goal tools when exposed, asks for an exact fallback
+`/goal <completion condition>` when needed, and maps subagent delegation to
+`prometheus-planner`, `boulder-executor`, `oracle-verifier`, `qa-runner`,
+`quality-reviewer`, and `librarian-researcher`. Child assignments are expected
+to start with `TASK:` and include `DELIVERABLE`, `SCOPE`, and `VERIFY`, so
+delegated work has a concrete artifact, bounded scope, and verification path.
+Run the package diagnostic from the checkout or an installed package before
+full QA:
+
+```bash
+litclaude-ai workflow-check --json
+```
+
+When a long `$start-work` run is interrupted, compacted, or resumed in a new
+terminal pane, use the continuation helper from the checkout:
+
+```bash
+litclaude-ai start-work-next --json
+```
+
+It reads `.litclaude/boulder.json` and `.litclaude/start-work/ledger.jsonl`, then prints the
+active plan, ledger path, and first unchecked top-level task. If the plan is
+complete, it returns `{"status":"idle","directive":null}`.
+
+For v0.2.0 workflow parity, `review-work` is the dedicated review route. It is a
+5-lane review: goal/constraint verification, hands-on QA execution, code
+quality, security, and local-first context mining. The lanes bind to
+`oracle-verifier`, `qa-runner`, `quality-reviewer`, and `librarian-researcher`,
+then aggregate evidence into a PASS, FAIL, or NEEDS-CONTEXT verdict. Manual-QA
+channels must write artifacts, and every tmux session, server, port, browser
+tab, or temp directory needs a cleanup receipt before review completion.
+
+`litgoal` is the durable local state route for long goals. The runtime lives
+in `plugins/litclaude/lib/litgoal/`, stores state in `.litclaude/litgoal/`, and
+keeps current docs/test reads authoritative when stale state disagrees with the
+checkout. Common commands are:
+
+```bash
+litclaude litgoal create-goals --brief "<brief>" --json
+litclaude litgoal record-evidence --criterion <id> --status pass --json '{"artifact":"...","cleanup":"..."}'
+litclaude litgoal checkpoint --status active --note "<progress>" --json
+litclaude litgoal steer --kind scope --note "<what changed and why>" --json
+```
+
+`record-review-blockers` captures unresolved review findings. Malformed JSON,
+unknown criteria, corrupt state, and invalid steering kinds return controlled
+errors instead of silently reporting success.
+
+Plain `lit` is hook context activation. Claude may still show it as hook
+guidance rather than a separate Skill tool invocation in history. Use visible
+namespaced commands when you want explicit LitClaude skill activation:
+
+```text
+/litclaude:lit-loop <what you want executed with evidence>
+/litclaude:dynamic-workflow <parallel or delegated objective>
+/litclaude:lit-plan <what you want planned>
+/litclaude:deep-interview <what needs clarification>
+/litclaude:review-work <scope to review>
+/litclaude:litgoal <goal operation>
+/litclaude:start-work plans/example-plan.md
+```
+
+Those namespaced commands are shipped as real Claude Code command files under
+`plugins/litclaude/commands/`, so `/litclaude:lit-loop` should load the
+command body, then the matching skill guidance.
+The shorter slash aliases above are also recognized by the prompt hook and
+route to the matching discipline instead of the plain `lit` loop fallback.
+
+Use `/deep-interview` before `/lit-plan` when the request is broad,
+underspecified, or missing non-goals and acceptance criteria. It writes a
+requirements artifact under `deep-interview/` and then hands off to planning or
+execution without building directly.
+
+## Commands
+
+| Command | Purpose |
+| --- | --- |
+| `npx --yes litclaude-ai install` | Install and enable the Claude Code plugin |
+| `npx --yes litclaude-ai --version` | Print the packaged LitClaude version |
+| `npx --yes litclaude-ai doctor` | Validate files, Claude plugin validation, and plugin details |
+| `npx --yes litclaude-ai path` | Print the installed Claude plugin path |
+| `npx --yes litclaude-ai run -- --help` | Run plain `claude` after verifying install state |
+| `npx --yes litclaude-ai update` | Reinstall the current package version |
+| `npx --yes litclaude-ai uninstall` | Remove LitClaude-managed install state |
+
+The package alias can be inspected without installing anything globally:
+
+```bash
+node bin/litclaude-ai.js --dry-run install
+node bin/litclaude-ai.js --dry-run doctor
+```
+
+## Local Development
+
+Use the plugin directly from this checkout while editing it:
+
+```bash
+claude --plugin-dir ./plugins/litclaude
+```
+
+Inside Claude Code, reload local plugin metadata after edits:
+
+```text
+/reload-plugins
+```
+
+If an OMC/omc Claude plugin is installed, do not co-load it with LitClaude
+while testing. Local checkout tests use `--plugin-dir`, and npm installs create
+only a LitClaude-managed local marketplace under the user's LitClaude home.
+The checkout does not ship a root Claude marketplace skeleton. If user-level
+OMC creates a local `.omc/` state directory during smoke tests, LitClaude
+ignores and excludes that directory from git and npm package surfaces.
+
+## Verification
+
+```bash
+npm test
+npm run validate:plugin
+npm run qa:tmux
+npm run qa:portable
+npm run pack:dry-run
+```
+
+`validate:plugin` and `qa:tmux` are local checks. If Claude Code is not
+available on the machine, the smoke harness records a controlled skip with the
+version probe evidence instead of failing mysteriously.
+
+## Safety Model
+
+- Hooks read Claude Code event JSON from stdin and return bounded JSON context.
+- Hooks do not execute user prompt text.
+- The litwork prompt hook returns constant guidance and does not echo prompt text.
+- `.omc/`, `.litclaude/`, and `evidence/` local state are ignored and excluded from the npm package.
+- The planner agent is read-only and has no edit tools.
+- MCP and LSP helpers are local stdio commands.
+- Future publication, remote marketplace mutation, and package releases require explicit user approval.
+
+## Project Map
+
+| Surface | Path |
+| --- | --- |
+| CLI | `bin/litclaude-ai.js` |
+| Claude plugin | `plugins/litclaude/` |
+| Skills | `plugins/litclaude/skills/` |
+| Agents | `plugins/litclaude/agents/` |
+| Hooks | `plugins/litclaude/hooks/hooks.json` |
+| MCP | `plugins/litclaude/.mcp.json` |
+| LSP | `plugins/litclaude/.lsp.json` |
+
+See `README_ko-KR.md` for Korean setup notes, `docs/migration.md` for the
+workflow migration table, `docs/workflow-compatibility-audit.md` for the current
+compatibility audit, and `CHANGELOG.md` for release notes.