lithermes-ai 0.8.6 → 0.8.7

package/README.md

@@ -39,6 +39,15 @@ Install the plugin:
 npx lithermes-ai install --yes
 ```
 
+For a non-interactive first install through npx, pass both approvals:
+
+```sh
+npx --yes lithermes-ai@latest install --yes
+```
+
+The first `--yes` is for npx; the second `--yes` is for LitHermes. The npm
+package is `lithermes-ai`; `lithermes` is the installed CLI/plugin name.
+
 Restart any running Hermes CLI or Hermes gateway process. Then open Hermes and try:
 
 ```text
@@ -128,6 +137,16 @@ Install with npm:
 npx lithermes-ai install --yes
 ```
 
+Non-interactive npx install:
+
+```sh
+npx --yes lithermes-ai@latest install --yes
+```
+
+`npx --yes` only suppresses npm's prompt to download/run the package. LitHermes
+still requires `install --yes` before it mutates Hermes config. Running
+`npx --yes lithermes-ai@latest install` is therefore expected to stop safely.
+
 Install with Bun:
 
 ```sh
@@ -142,6 +161,10 @@ npx lithermes-ai install --yes --hermes-home /path/to/.hermes
 
 LitHermes refuses to mutate Hermes config unless you pass `--yes`. If `~/.hermes/plugins/lithermes` already exists but was not created by this installer, installation stops instead of overwriting user files.
 
+Do not install as `npx lithermes@latest ...`: `lithermes` is not the npm package
+name. Use `lithermes-ai` (or `npx --package lithermes-ai@latest lithermes ...`
+when you explicitly want the `lithermes` binary name).
+
 ## Verify
 
 Check the package and Hermes compatibility:
@@ -229,6 +252,28 @@ Uninstall intentionally preserves unrelated files in `~/.hermes/plugins`.
 
 ## Troubleshooting
 
+### `Refusing to mutate Hermes config without --yes`
+
+You passed `--yes` to npx but not to the LitHermes installer. Use:
+
+```sh
+npx --yes lithermes-ai@latest install --yes
+```
+
+### `No matching version found for lithermes@latest`
+
+The npm package is `lithermes-ai`, not `lithermes`:
+
+```sh
+npx --yes lithermes-ai@latest install --yes
+```
+
+If you need the `lithermes` binary explicitly, run:
+
+```sh
+npx --yes --package lithermes-ai@latest lithermes install --yes
+```
+
 ### `Hermes installation not found`
 
 Pass the Hermes home explicitly:

package/README_Ko-KR.md

@@ -39,6 +39,16 @@ bunx lithermes-ai doctor
 npx lithermes-ai install --yes
 ```
 
+npx를 통한 첫 설치에서 확인 질문을 모두 생략하려면 두 종류의 `--yes`를 모두
+전달합니다.
+
+```sh
+npx --yes lithermes-ai@latest install --yes
+```
+
+앞의 `--yes`는 npx용이고, 뒤의 `install --yes`는 LitHermes installer용입니다.
+npm 패키지명은 `lithermes-ai`이며, `lithermes`는 설치 후 CLI/plugin 이름입니다.
+
 실행 중인 Hermes CLI 또는 Hermes gateway를 재시작합니다. 그 다음 Hermes에서 이렇게 사용합니다.
 
 ```text
@@ -114,6 +124,16 @@ npm으로 설치합니다.
 npx lithermes-ai install --yes
 ```
 
+npx 확인 질문까지 생략하는 설치:
+
+```sh
+npx --yes lithermes-ai@latest install --yes
+```
+
+`npx --yes`는 npm의 패키지 다운로드/실행 확인만 생략합니다. LitHermes가 Hermes
+config를 수정하려면 여전히 `install --yes`가 필요합니다. 따라서 `npx --yes
+lithermes-ai@latest install`이 안전하게 멈추는 것은 정상 동작입니다.
+
 Bun으로 설치합니다.
 
 ```sh
@@ -128,6 +148,10 @@ npx lithermes-ai install --yes --hermes-home /path/to/.hermes
 
 LitHermes는 `--yes`가 없으면 Hermes config를 수정하지 않습니다. 또한 `~/.hermes/plugins/lithermes`가 이미 있는데 이 installer가 만든 파일이 아니면, 사용자 파일을 덮어쓰지 않고 멈춥니다.
 
+`npx lithermes@latest ...`로 설치하지 마세요. npm 패키지명은 `lithermes-ai`이고,
+`lithermes`는 binary/plugin 이름입니다. binary 이름을 명시하고 싶다면
+`npx --package lithermes-ai@latest lithermes install --yes`를 사용하세요.
+
 ## 확인
 
 패키지와 Hermes 호환성을 확인합니다.
@@ -215,6 +239,28 @@ npx lithermes-ai uninstall --yes
 
 ## 문제 해결
 
+### `Refusing to mutate Hermes config without --yes`
+
+`--yes`를 npx에는 넘겼지만 LitHermes installer에는 넘기지 않은 경우입니다.
+
+```sh
+npx --yes lithermes-ai@latest install --yes
+```
+
+### `No matching version found for lithermes@latest`
+
+npm 패키지는 `lithermes`가 아니라 `lithermes-ai`입니다.
+
+```sh
+npx --yes lithermes-ai@latest install --yes
+```
+
+`lithermes` binary 이름을 꼭 명시하려면 다음처럼 실행하세요.
+
+```sh
+npx --yes --package lithermes-ai@latest lithermes install --yes
+```
+
 ### `Hermes installation not found`
 
 Hermes home을 직접 지정하세요.

package/assets/lithermes-plugin/README.md

@@ -3,6 +3,16 @@
 Hermes-native workflow tools for plan-first execution, evidence ledgers, and
 first-class Hermes skills:
 
+Install from npm with the package name `lithermes-ai`:
+
+```sh
+npx --yes lithermes-ai@latest install --yes
+```
+
+`npx --yes` only approves npm package execution; `install --yes` is the LitHermes
+installer approval to mutate Hermes config. `lithermes` is the installed
+CLI/plugin name, not the npm package name.
+
 - `/lit-plan` and `/litwork-plan` create durable plans in `plans/`, then forward a
   goal bootstrap to the Hermes agent instead of stopping at plan creation.
 - `/lit-loop` and `/litwork-loop` create run state under

package/assets/lithermes-plugin/plugin.yaml

@@ -1,5 +1,5 @@
 name: lithermes
-version: 0.8.6
+version: 0.8.7
 description: "Hermes-native workflow toolkit: litgoal durable runtime, 5-lane review orchestrator, Litwork commands, skills, and prompt steering."
 author: "Hermes Agent"
 kind: standalone

package/assets/lithermes-plugin/skills/programming/SKILL.md

@@ -11,7 +11,40 @@ This skill is an index. The hard per-language rules live under `references/`. Lo
 
 ---
 
-## PHASE 0 — LANGUAGE GATE (RUN THIS FIRST, EVERY TIME)
+## PHASE -1 — BUILD-DECISION GATE (RUN BEFORE PHASE 0)
+
+Before writing or editing a single line of implementation code, work down these
+checks and stop at the first one that cleanly meets the need:
+
+1. Does this need to exist at all? If the outcome does not require it, do not build it.
+2. Does the standard library already do it well? If so, use it.
+3. Is there a native platform, runtime, or framework feature for it? If so, use it.
+4. Does an already-installed dependency cover it cleanly? If so, reuse it — do not add or hand-roll.
+5. Can the remaining gap be one clear line? If so, write the one line.
+6. Only after all of the above fail: write the minimum code that genuinely works — nothing speculative.
+
+Scope and floor (these keep the gate from under-building):
+
+- Judge "minimum that works" over the WHOLE task, not per call site. If the same
+  logic appears at more than one call site, the minimum that works IS one small
+  shared helper — extract it.
+- "Works" includes error handling for any failure the code can realistically hit
+  (network, parse, missing file, bad state) and the tests that prove the behavior
+  you just wrote. Only handling for states that genuinely cannot occur is the
+  speculative part to cut.
+- Reach for a stdlib / native / dependency option only when it fits the need
+  cleanly, not merely because it technically can.
+- Never shorten away, for the sake of fewer lines: input validation at trust
+  boundaries, handling that prevents data loss or corruption, security controls
+  (auth, secret handling, injection/escaping), or accessibility. The point is to
+  remove redundancy and speculation, never to lower the correctness floor.
+
+PHASE -1 decides WHETHER and FROM WHAT to build; PHASE 0 and the per-language iron
+list decide HOW.
+
+---
+
+## PHASE 0 — LANGUAGE GATE (RUN AFTER PHASE -1, EVERY TIME)
 
 **DO NOT WRITE OR EDIT A SINGLE LINE OF CODE BEFORE COMPLETING THIS GATE.**
 
@@ -355,6 +388,7 @@ After every code-writing session, answer these out loud (in your reply) before d
 5. **Defensive layer?** Any null check, try/except, or `isinstance` guarding a value the type system already proves? If yes, delete.
 6. **Helpers for one-off?** Any function, class, or trait introduced for a single caller that will never get a second caller? If yes, inline.
 7. **Tests?** Is the behavior I just introduced locked by a test that would fail if I revert this commit?
+8. **Necessity & reuse?** Did everything I wrote need to exist, and did I confirm the standard library, a native feature, or an already-installed dependency did not already cover it before I hand-rolled? If not, remove it.
 
 **If any answer fails, fix it before declaring done.** This loop is the difference between "the code compiles" and "the code is correct."
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "lithermes-ai",
-  "version": "0.8.6",
+  "version": "0.8.7",
   "description": "npx/bunx installer for the LitHermes Hermes plugin",
   "license": "MIT",
   "repository": {