lazyclaude-ai 0.1.3 → 0.1.4

package/README.md

@@ -48,6 +48,17 @@ Future package releases still require explicit user approval.
 npx --yes lazyclaude-ai install
 ```
 
+If you are currently inside this repository checkout, which has the same
+package name as the registry package, `npx --yes lazyclaude-ai@0.1.3 install`
+can resolve the local same-name source checkout and fail with
+`sh: lazyclaude-ai: command not found`. From a fresh directory, the normal
+install command works:
+
+```bash
+cd /tmp
+npx --yes lazyclaude-ai@0.1.3 install
+```
+
 Validate the installed plugin:
 
 ```bash
@@ -68,8 +79,9 @@ npm install -g lazyclaude-ai
 lazyclaude install
 ```
 
-If you need the explicit `npm exec` form, use a fresh prefix so npm does not
-confuse the registry package with a same-name source checkout:
+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 lazyclaude-ai -- lazyclaude install
@@ -111,9 +123,12 @@ $start-work plans/lazyclaude-retrofit.md
 ```
 
 Expected behavior: LazyClaude's prompt hook adds `ULTRAWORK MODE ENABLED`
-context, 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.
+context and shows `LazyClaude ULW hook active` as a visible hook message. The
+hook also tells Claude to treat plain `ulw` as `/lazyclaude:ulw-loop` /
+`Skill(ulw-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.
 
 LazyClaude does not auto-type `/goal` or send slash command text for you.
 Instead, the hook and ULW skills add run-context guidance: use Claude Code's
@@ -123,9 +138,9 @@ completion or a genuine blocker. For large independent work, the guidance also
 points Claude toward Dynamic workflow orchestration and Dynamic worktree
 isolation.
 
-Plain `ulw` is hook context activation, so it may not show a separate Skill
-tool invocation in Claude Code history. Use visible namespaced commands when
-you want explicit LazyClaude skill activation:
+Plain `ulw` 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 LazyClaude skill activation:
 
 ```text
 /lazyclaude:ulw-loop <what you want executed with evidence>

package/README_ko-KR.md

@@ -52,6 +52,17 @@
 npx --yes lazyclaude-ai install
 ```
 
+현재 위치가 이 저장소 checkout이면, registry package와 같은 package name을
+가진 same-name source checkout 안에 있는 상태입니다. 이 경우
+`npx --yes lazyclaude-ai@0.1.3 install`이 local checkout을 먼저 해석해서
+`sh: lazyclaude-ai: command not found`로 실패할 수 있습니다. 새 폴더에서는
+일반 설치 명령이 정상 동작합니다.
+
+```bash
+cd /tmp
+npx --yes lazyclaude-ai@0.1.3 install
+```
+
 설치 상태를 확인합니다.
 
 ```bash
@@ -73,7 +84,8 @@ lazyclaude install
 ```
 
 현재 checkout처럼 package 이름이 같은 폴더 안에서 `npm exec`를 직접 쓸
-때는 fresh prefix를 주는 편이 안전합니다.
+때는 registry package와 same-name source checkout이 섞이지 않도록 fresh
+prefix를 주는 편이 안전합니다.
 
 ```bash
 npm exec --prefix "$(mktemp -d)" --yes --package lazyclaude-ai -- lazyclaude install
@@ -115,9 +127,11 @@ $start-work plans/lazyclaude-retrofit.md
 ```
 
 기대 동작은 LazyClaude prompt hook이 `ULTRAWORK MODE ENABLED` 컨텍스트를
-추가하고, skill 및 agent 지시문이 Claude를 test-first 작업, native goal
-처리, 실제 수동 QA 증거, cleanup receipt, 향후 release step의 명시적 승인
-쪽으로 유도하는 것입니다.
+추가하고 `LazyClaude ULW hook active`라는 visible hook message를 보여주는
+것입니다. 또한 plain `ulw`를 일반 작업 실행 전 `/lazyclaude:ulw-loop` /
+`Skill(ulw-loop)` semantics로 처리하라고 Claude에게 지시합니다. 그 뒤 skill
+및 agent 지시문이 Claude를 test-first 작업, native goal 처리, 실제 수동 QA
+증거, cleanup receipt, 향후 release step의 명시적 승인 쪽으로 유도합니다.
 
 LazyClaude는 `/goal`을 대신 입력하거나 slash command text를 자동 전송하지
 않습니다. 대신 hook과 ULW skill이 run context를 보강합니다. Claude Code의
@@ -127,9 +141,10 @@ goal이 없을 때만 `create_goal`을 호출하며, `update_goal`은 검증 완
 workflow orchestration과 Dynamic worktree isolation도 함께 고려하도록
 유도합니다.
 
-단순히 `ulw`라고 입력하는 것은 hook context activation이므로 Claude Code
-history에 별도 Skill tool invocation으로 보이지 않을 수 있습니다. 명시적인
-LazyClaude skill activation을 보고 싶다면 namespaced command를 사용합니다.
+단순히 `ulw`라고 입력하는 것은 hook context activation입니다. Claude Code
+history에는 별도 Skill tool invocation이 아니라 hook guidance로 보일 수
+있습니다. 명시적인 LazyClaude skill activation을 보고 싶다면 namespaced
+command를 사용합니다.
 
 ```text
 /lazyclaude:ulw-loop <증거 기반으로 실행할 작업>

package/RELEASE_CHECKLIST.md

@@ -43,6 +43,16 @@ local marketplace metadata needed by `claude plugin details`. Do not ask users
 to type a generated command that shells out to `npx --yes lazyclaude-ai path` for
 normal npm installs.
 
+Run fresh-machine QA from a fresh directory, not from this repository checkout.
+Inside the same-name source checkout, `npx --yes lazyclaude-ai@0.1.3 install`
+can resolve the local package and fail with `sh: lazyclaude-ai: command not
+found`. Use `cd /tmp` for the fresh directory scenario, or use the explicit
+fresh-prefix form:
+
+```bash
+npm exec --prefix "$(mktemp -d)" --yes --package lazyclaude-ai -- lazyclaude install
+```
+
 ## Quiet Public NPM Package Release Or Update
 
 Use this track only when the user explicitly approves making a new package

package/docs/hooks.md

@@ -25,8 +25,11 @@ $start-work
 ```
 
 When a trigger is present, the hook returns additional context containing
-`ULTRAWORK MODE ENABLED`. That context is guidance for Claude Code; it is not
-executed as a command.
+`ULTRAWORK MODE ENABLED` and a visible `LazyClaude ULW hook active` system
+message. That context is guidance for Claude Code; it is not executed as a
+command. The guidance tells Claude to treat plain `ulw` as
+`/lazyclaude:ulw-loop` / `Skill(ulw-loop)` semantics before ordinary task
+execution.
 
 LazyClaude follows the LazyCodex goal pattern as model-facing run context, not
 as slash-command injection. If Claude Code exposes the native goal surface, the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "lazyclaude-ai",
-  "version": "0.1.3",
+  "version": "0.1.4",
   "description": "Claude Code-native LazyCodex-style workflow distribution.",
   "type": "module",
   "bin": {

package/plugins/lazyclaude/bin/lazyclaude-hook.js

@@ -21,20 +21,25 @@ const hookEventNames = {
   "post-compact": "PostCompact",
 };
 
-const writeContext = (additionalContext) => {
+const writeContext = (additionalContext, systemMessage) => {
+  const payload = {
+    continue: true,
+    hookSpecificOutput: {
+      hookEventName: hookEventNames[eventName],
+      additionalContext,
+    },
+  };
+  if (systemMessage) {
+    payload.systemMessage = systemMessage;
+  }
   console.log(
-    JSON.stringify({
-      continue: true,
-      hookSpecificOutput: {
-        hookEventName: hookEventNames[eventName],
-        additionalContext,
-      },
-    }),
+    JSON.stringify(payload),
   );
 };
 
 const ultraworkContext = [
   "ULTRAWORK MODE ENABLED.",
+  "Treat this prompt as an explicit request to use LazyClaude ulw-loop discipline now; load or follow /lazyclaude:ulw-loop / Skill(ulw-loop) semantics before ordinary task execution.",
   "Use evidence-bound planning, tests, manual QA, and cleanup receipts.",
   "Native goal integration: when Claude Code exposes /goal or model-facing goal tools, first inspect get_goal, call create_goal with an objective-only payload when no matching goal is active, and reserve update_goal for verified completion or a genuine blocker.",
   "Do not auto-type or inject the user's slash commands; treat /goal as Claude Code's native goal surface, not as prompt text for this hook to send.",
@@ -54,7 +59,7 @@ switch (eventName) {
     const prompt = typeof input.prompt === "string" ? input.prompt : "";
     const activates = /\b(?:ultrawork|ulw)\b|\$(?:ulw-plan|ulw-loop|start-work)\b/u.test(prompt);
     if (activates) {
-      writeContext(ultraworkContext);
+      writeContext(ultraworkContext, "LazyClaude ULW hook active: ulw-loop guidance injected.");
     } else {
       writeContext("LazyClaude prompt hook checked: no workflow activation.");
     }