@litfamily/litgrok 1.0.2 → 1.0.3

package/.grok/hooks/session-start.mjs

@@ -1,6 +1,5 @@
 #!/usr/bin/env node
 
-import { pendingReviewState } from '../skills/skill-observer/scripts/skill-loop.mjs';
 import { renderMark } from './lit-mark.mjs';
 import { claimSessionIgnition } from './record-passive-event.mjs';
 
@@ -20,18 +19,3 @@ try {
 }
 
 process.stdout.write('LitGrok payload present: skills, project rules, hooks, and the npx installer.\n');
-
-try {
-  const sessionId = process.env.GROK_SESSION_ID || event.sessionId;
-  const workspaceRoot = process.env.GROK_WORKSPACE_ROOT || event.workspaceRoot;
-  if (!process.exitCode && sessionId && workspaceRoot && event.sessionId === sessionId && event.workspaceRoot === workspaceRoot) {
-    const state = pendingReviewState({
-      cwd: workspaceRoot,
-      env: { ...process.env, LITGROK_WORKSPACE_ROOT: workspaceRoot },
-      sessionId,
-    });
-    if (state.pending) process.stdout.write(`LitGrok: pending review for session ${sessionId} — run /skill-observer review\n`);
-  }
-} catch {
-  // The installed-payload banner is still useful when optional event state is unavailable.
-}

package/.grok/hooks/stop.mjs

@@ -2,35 +2,27 @@
 
 // No completion-summary field is documented, so this records only the documented turn-end event and identity.
 import { appendSessionRecord, recordPassiveEvent } from './record-passive-event.mjs';
-import { recordTurnEnded } from '../skills/skill-observer/scripts/skill-loop.mjs';
 import { PLAN_GATE_SIGNAL, evaluatePlanGate } from './plan-gate.mjs';
 
-if (process.env.LITGROK_SKILL_REVIEW !== '1') {
-  const observed = await recordPassiveEvent('Stop');
-  if (observed) {
-    recordTurnEnded({
-      cwd: observed.environment.realWorkspaceRoot,
-      env: { ...process.env, LITGROK_WORKSPACE_ROOT: observed.environment.realWorkspaceRoot },
+const observed = await recordPassiveEvent('Stop');
+if (observed) {
+  // Plan gate: a planning turn must persist plans/<slug>.md; evaluated after the ledger record so a block is counted.
+  let gate;
+  try {
+    gate = evaluatePlanGate({
+      event: observed.event,
+      workspaceRoot: observed.environment.realWorkspaceRoot,
       sessionId: observed.environment.sessionId,
+      ledgerFile: observed.ledgerFile,
     });
-    // Plan gate: a planning turn must persist plans/<slug>.md; evaluated after the ledger record so a block is counted.
-    let gate;
-    try {
-      gate = evaluatePlanGate({
-        event: observed.event,
-        workspaceRoot: observed.environment.realWorkspaceRoot,
-        sessionId: observed.environment.sessionId,
-        ledgerFile: observed.ledgerFile,
-      });
-    } catch (error) {
-      process.stderr.write(`LitGrok plan gate: PLAN_GATE_FAILED ${error instanceof Error ? error.message : String(error)}\n`);
-      gate = { block: false };
-    }
-    if (gate.block) {
-      appendSessionRecord(observed.ledgerFile, observed.record, { signal: PLAN_GATE_SIGNAL, reason: gate.reason });
-      process.stdout.write(`${JSON.stringify({ decision: 'block', reason: gate.reason })}\n`);
-    } else if (gate.warning) {
-      process.stderr.write(`${gate.warning}\n`);
-    }
+  } catch (error) {
+    process.stderr.write(`LitGrok plan gate: PLAN_GATE_FAILED ${error instanceof Error ? error.message : String(error)}\n`);
+    gate = { block: false };
+  }
+  if (gate.block) {
+    appendSessionRecord(observed.ledgerFile, observed.record, { signal: PLAN_GATE_SIGNAL, reason: gate.reason });
+    process.stdout.write(`${JSON.stringify({ decision: 'block', reason: gate.reason })}\n`);
+  } else if (gate.warning) {
+    process.stderr.write(`${gate.warning}\n`);
   }
 }

package/.grok/skills/litgoal/SKILL.md

@@ -48,7 +48,7 @@ A useful objective answers:
 
 Example:
 
-    /goal Make the release check pass in 33_litgrok without changing the package version; done when npm test and npm pack --dry-run --json --ignore-scripts both exit 0 and the pack list contains only the approved payload.
+    /goal Make the release check pass in this package checkout without changing the package version; done when npm test and npm pack --dry-run --json --ignore-scripts both exit 0 and the pack list contains only the approved payload.
 
 The example is a command for the operator to run. It is not an invocation performed by this skill.
 

package/.grok/skills/litgrok/SKILL.md

@@ -22,7 +22,7 @@ reader_projection: shared_rule
 
 LitGrok is a dependency-free package containing:
 
-- 34 Grok-native skill folders under `.grok/skills/`, including their owned references;
+- 33 Grok-native skill folders under `.grok/skills/`, including their owned references;
 - a root-level `plugin.json` manifest declaring the shipped skill, agent, and hook surfaces;
 - 11 Grok-native agent definitions under `.grok/agents/`;
 - one project rule under `.grok/rules/`;

package/.grok/skills/litwork/SKILL.md

@@ -88,7 +88,7 @@ A working note can use this compact shape:
 
 Use the ledger only for chronology and identity checks. Confirm that the record's schema, session id, workspace root, hook name, and event name match the session being reviewed. Treat tool input hashes as identifiers, not as recoverable command text. A Stop record means a turn ended; it is not a completion receipt. A SubagentStop record means a boundary was observed; inspect the agent's own artifact before classifying its result.
 
-The separate skill-observer learning loop may have proposal or transaction files under .grok/litgrok. Those files concern skill review and rollback, not the user's work objective. Do not present them as a work ledger.
+Older LitGrok versions may have left skill-review state under .grok/litgrok. Current hooks leave those files untouched; do not present them as a work ledger.
 
 ## Native features and explicit limits
 

package/.grok-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "litgrok",
-  "version": "1.0.2",
+  "version": "1.0.3",
   "description": "Grok Build skills, project rules, and bounded lifecycle hooks for evidence-first lit work.",
   "author": {
     "name": "LitGrok contributors"
@@ -39,7 +39,6 @@
     "./.grok/skills/refactor",
     "./.grok/skills/review-work",
     "./.grok/skills/rules",
-    "./.grok/skills/skill-observer",
     "./.grok/skills/start-work",
     "./.grok/skills/structural-search",
     "./.grok/skills/visual-qa",

package/CHANGELOG.md

@@ -2,6 +2,15 @@
 
 ## Unreleased
 
+## 1.0.3
+
+- Add an animated README cover with a static option for reduced motion.
+- Remove automatic skill review because it never completed a review in practice. Leftover `pending-review.json` and `skill-loop-state.json` files are inactive and may be deleted; no other state is affected.
+- Refuse to publish when the test suite fails.
+- Remove the retired `skill-observer` skill and its empty directories during upgrades while preserving user-owned files. If a user-owned file is inside the retired directory, installation refuses and names its path.
+- List all 33 skills, 11 agents, and 11 hooks in the marketplace manifest so plugin scanners can find every component.
+- Remove the private checkout path from the `litgoal` example.
+
 ## 1.0.2
 
 - Add an explicit marketplace scanner manifest that enumerates all 34 skills, 11 agents, and the native hook manifest while preserving the existing Grok payload manifest.

package/README.md

@@ -1,17 +1,18 @@
-<p align="center"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.2/docs/assets/cover.webp" width="100%" alt="LitGrok v5 armory cover" /></p>
+<p align="center"><picture><source media="(prefers-reduced-motion: reduce)" srcset="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.3/docs/assets/cover.webp" /><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.3/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.3/docs/assets/cover.webp">View the static cover</a></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.2/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.2/docs/assets/litgrok-clay-icon.png" width="160" alt="LitGrok clay mark" /></p>
+<p align="center"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.3/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.3/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.2/docs/assets/readme/badge-version.svg" alt="1.0.2" /></a>
-<a href="./LICENSE"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.2/docs/assets/readme/badge-license.svg" alt="MIT license" /></a>
+<a href="#install-in-30-seconds"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.3/docs/assets/readme/badge-version.svg" alt="1.0.3" /></a>
+<a href="./LICENSE"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.3/docs/assets/readme/badge-license.svg" alt="MIT license" /></a>
 </p>
 
 <p align="center">
@@ -26,9 +27,9 @@ Make something useful in Grok Build. Leave the checked result and the next step
 >
 > **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.
+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.2** · [MIT](./LICENSE)
+Package: **@litfamily/litgrok** · Version: **1.0.3** · [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.
 
@@ -52,7 +53,7 @@ Grok Build uses the explicit `/litwork` route for a bounded task. It owns model
 
 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.
 
-<p align="center"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.2/docs/assets/litgrok-ignition-1600.webp" width="48%" alt="LitGrok ignition apparatus" /><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.2/docs/assets/litgrok-continuity-1600.webp" width="48%" alt="LitGrok continuity apparatus" /></p>
+<p align="center"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.3/docs/assets/litgrok-ignition-1600.webp" width="48%" alt="LitGrok ignition apparatus" /><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.3/docs/assets/litgrok-continuity-1600.webp" width="48%" alt="LitGrok continuity apparatus" /></p>
 
 <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>
 
@@ -75,7 +76,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.2` 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.3` for a pinned install, or add `--user` to install under `~/.grok/`. [Install and upgrade details](./docs/reference.md#install).
 
 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.
 
@@ -142,7 +143,7 @@ The hooks' `.grok/litgrok/session-ledger/` records event order. Judge success fr
 | 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 `/skills` for all 34 skills. [Rename compatibility](./docs/reference.md#skill-rename-compatibility) covers the one-release aliases; old slash routes are not guaranteed.
+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.
 
 ## Safety and uninstall
 
@@ -172,7 +173,6 @@ Match the scope used for installation. Re-run `install` to update. The installer
 ## Documentation
 
 - [Operational reference](./docs/reference.md): installation, hooks, terminal output, payload checks, and source provenance.
-- [Skill learning loop](./docs/reference.md#skill-learning-loop): proposal review, explicit apply, rollback, and macOS/Linux support. Windows learning-loop commands are unsupported.
 - [Project rule](./.grok/rules/00-litgrok.md) and [skill catalog](./.grok/skills/).
 - [Changelog](./CHANGELOG.md) and [license](./LICENSE).
 

package/README_ko-KR.md

@@ -1,17 +1,18 @@
-<p align="center"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.2/docs/assets/cover.webp" width="100%" alt="LitGrok v5 armory cover" /></p>
+<p align="center"><picture><source media="(prefers-reduced-motion: reduce)" srcset="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.3/docs/assets/cover.webp" /><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.3/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.3/docs/assets/cover.webp">정지 표지 보기</a></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.2/docs/assets/litgrok-wordmark.svg" width="480" alt="LITGROK 디스플레이 타입" /></p>
-<p align="center"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.2/docs/assets/litgrok-clay-icon.png" width="160" alt="LitGrok 클레이 마크" /></p>
+<p align="center"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.3/docs/assets/litgrok-wordmark.svg" width="480" alt="LITGROK 디스플레이 타입" /></p>
+<p align="center"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.3/docs/assets/litgrok-clay-icon.png" width="160" alt="LitGrok 클레이 마크" /></p>
 
 Grok Build에서 작은 결과물을 만들고, 확인한 내용과 다음 할 일을 프로젝트에 남기세요.
 
 [English](./README.md) · [설치](#30초-설치) · [처음 사용하기](#첫-lit-작업) · [상세 안내](./docs/reference_ko-KR.md)
 
 <p align="center">
-<a href="#30초-설치"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.2/docs/assets/readme/badge-version.svg" alt="1.0.2" /></a>
-<a href="./LICENSE"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.2/docs/assets/readme/badge-license.svg" alt="MIT 라이선스" /></a>
+<a href="#30초-설치"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.3/docs/assets/readme/badge-version.svg" alt="1.0.3" /></a>
+<a href="./LICENSE"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.3/docs/assets/readme/badge-license.svg" alt="MIT 라이선스" /></a>
 </p>
 
 <p align="center">
@@ -26,9 +27,9 @@ Grok Build에서 작은 결과물을 만들고, 확인한 내용과 다음 할
 >
 > **대화가 끝난 자리에서, 다음 작업이 시작되도록.**
 
-skill 34개, agent 11개, project rule 하나, hook 등록 열한 개를 제공합니다. Installer가 프로젝트에 전체 파일을 복사하고, 세션 실행과 모델 선택은 Grok Build가 담당합니다.
+skill 33개, agent 11개, project rule 하나, hook 등록 열한 개를 제공합니다. Installer가 프로젝트에 전체 파일을 복사하고, 세션 실행과 모델 선택은 Grok Build가 담당합니다.
 
-패키지: **@litfamily/litgrok** · 버전: **1.0.2** · [MIT](./LICENSE)
+패키지: **@litfamily/litgrok** · 버전: **1.0.3** · [MIT](./LICENSE)
 
 과학 시각화 corpus는 `.grok/vendor/scientific-visualization/`에 포함되며, 숫자 `045_scientific-visualization` 표기는 라이선스와 provenance 파일명에만 남습니다.
 
@@ -52,7 +53,7 @@ Grok Build에서는 명시적인 `/litwork` 경로로 작은 작업을 시작합
 
 Grok Build에서 `/litwork`는 범위를 정한 작업 체크리스트를 시작하고, `handoff` 또는 `/lit-handoff`는 확인한 결과와 다음 단계를 건네며, `/lit-plan`은 확인 기준이 있는 계획을 남기고, `/start-work <승인된 계획>`은 그 계획을 실행하며, `/review-work`는 변경과 근거를 검토하고, `/litresearch`는 출처를 추적할 수 있는 범위 있는 조사를 합니다. 기대하는 효과는 확인 결과를 남기고 다음 세션에서 이어갈 수 있는 프로젝트 기록입니다. 호스트 제약도 분명합니다. 실행과 모델 선택은 Grok Build가 담당하고 LitGrok은 `.grok` payload를 설치합니다. Hook은 신뢰한 Git root에서만 제공되며, 일반 폴더에서는 skill과 rule만 로드되고 hook은 없을 수 있습니다. 이 이미지는 실제 호스트 동작을 증명하지 않는 정적 경로 안내입니다.
 
-<p align="center"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.2/docs/assets/litgrok-ignition-1600.webp" width="48%" alt="LitGrok 점화 장치" /><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.2/docs/assets/litgrok-continuity-1600.webp" width="48%" alt="LitGrok 연속 장치" /></p>
+<p align="center"><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.3/docs/assets/litgrok-ignition-1600.webp" width="48%" alt="LitGrok 점화 장치" /><img src="https://cdn.jsdelivr.net/npm/@litfamily/litgrok@1.0.3/docs/assets/litgrok-continuity-1600.webp" width="48%" alt="LitGrok 연속 장치" /></p>
 
 <p align="center"><a href="./docs/assets/readme/ignition-film.mp4"><img src="./docs/assets/readme/ignition-poster.png" width="720" alt="Ignition 모션 포스터" /></a></p>
 
@@ -75,7 +76,7 @@ LITGROK_PACK='/absolute/path/to/the-provided-package.tgz'
 npm exec --yes --package "$LITGROK_PACK" -- litgrok install
 ```
 
-기본 설치 위치는 `<project>/.grok/`입니다. 버전을 고정하려면 `--package @litfamily/litgrok@1.0.2`를 사용하세요. `--user`를 붙이면 `~/.grok/`에 설치합니다. [설치·업데이트 상세 안내](./docs/reference_ko-KR.md#설치).
+기본 설치 위치는 `<project>/.grok/`입니다. 버전을 고정하려면 `--package @litfamily/litgrok@1.0.3`를 사용하세요. `--user`를 붙이면 `~/.grok/`에 설치합니다. [설치·업데이트 상세 안내](./docs/reference_ko-KR.md#설치).
 
 Project hook은 Grok Build에서 신뢰한 Git 프로젝트 루트가 있어야 발견됩니다. 일반 폴더에서도 설치된 skill과 rule은 로드될 수 있지만 hook은 0개로 남을 수 있습니다. 새 disposable project라면 사용자가 직접 `git init`을 실행한 뒤 trust를 허용하세요. 기존 저장소라면 실제 root에서 Grok Build를 여세요. Installer는 `git init`을 실행하거나 trust를 바꾸지 않습니다. 관찰된 Grok Build 1.0.23에서는 `grok --trust inspect --json`이 동작했지만 `grok --help`에는 global `--trust`가 표시되지 않았습니다. 이는 이 버전에서 확인한 동작입니다.
 
@@ -142,7 +143,7 @@ Hook의 `.grok/litgrok/session-ledger/`는 이벤트가 발생한 순서를 남
 | 변경 내용과 근거 검토 | [`/review-work`](./.grok/skills/review-work/SKILL.md) |
 | 다음 세션을 위한 인수인계 | [`/lit-handoff`](./.grok/skills/lit-handoff/SKILL.md) |
 
-전체 skill 34개는 `/skills`에서 확인하세요. 이전 이름을 한 릴리스 동안 별칭으로 유지하는 정책은 [이름 변경과 호환성](./docs/reference_ko-KR.md#skill-이름-변경과-호환성)을 보세요. 이전 slash 경로는 보장되지 않습니다.
+전체 skill 33개는 `/skills`에서 확인하세요. 이전 이름을 한 릴리스 동안 별칭으로 유지하는 정책은 [이름 변경과 호환성](./docs/reference_ko-KR.md#skill-이름-변경과-호환성)을 보세요. 이전 slash 경로는 보장되지 않습니다.
 
 ## 안전과 제거
 
@@ -172,7 +173,6 @@ npm exec --yes --package @litfamily/litgrok@latest -- litgrok uninstall --user
 ## 문서
 
 - [상세 안내](./docs/reference_ko-KR.md): 설치, hook, 터미널 출력, 패키지 검증, 출처.
-- [Skill learning loop](./docs/reference_ko-KR.md#skill-learning-loop): proposal 검토, 명시적 적용, rollback, macOS/Linux 지원. Windows의 learning-loop 명령은 지원하지 않습니다.
 - [Project rule](./.grok/rules/00-litgrok.md)과 [skill 목록](./.grok/skills/).
 - [변경 이력](./CHANGELOG.md)과 [라이선스](./LICENSE).
 

package/bin/litgrok.mjs

@@ -46,6 +46,7 @@ const PRE_MANIFEST_PAYLOAD_HASHES = Object.freeze({
   'agents/litgrok-quality-reviewer.md': 'ed6f2687770f0f31c6821f0ad49d717362807f0bb5f4f27cf4d36be1e7dfd5a2',
   'hooks/record-passive-event.mjs': '9f5bd1d6c8b8e6c0be4cc61cf31f0e26f4f8a41fceb826e88567f22efa2b0090',
   'hooks/session-start.mjs': '5706ccce58340e78e435b9c1fd2224e101872ce1d0f51a9d187feb31b67c3b5d',
+  'hooks/stop.mjs': 'c796f02ac3dc99716d0c2f478bf93ec35cd8a9c725de18d12895957ee261b9c3',
   'rules/00-litgrok.md': 'd46d1672e80250c8748458afa9b0fc1a46c2a318d31c4d58ab1ebc3f8f2eb804',
   'skills/autoconference/SKILL.md': '025e9420ed9986b0466a8d660a4ed7f3e2d2243051ed3622be8ca87cbeba9458',
   'skills/autoconference/references/_canonical-corpus/manifest.json': '4554ee4041b73577a844abc27a97db91e941b8412f1888209203251dc1fee500',
@@ -59,6 +60,7 @@ const PRE_MANIFEST_PAYLOAD_HASHES = Object.freeze({
   'skills/lit-handoff/SKILL.md': '7152d6399fd778ab3d16e1abad2ec97e2f4be4350cd3993cdde038cc1211dd80',
   'skills/lit-scientific-visualization/SKILL.md': 'ffc3b2ea49dd7e7c4c7d4568f289df294a3a30f953c11039f98aaf6f8fb983ee',
   'skills/lit-scientific-visualization/scripts/verify-canonical-corpus.mjs': 'a1cfe0578195098dc4afc2d25f0d391f38aeaa57cd3970fa7dca51e20cbf929d',
+  'skills/litgoal/SKILL.md': 'e3fd76a8f4c91903ab85073b492f3981f76cb17644b840ba22d2a1c5e82178a9',
   'skills/litgrok/SKILL.md': '6ea1fb66d5a1458e182cff5808ccc416487dbbad0341988bcda0f247645081e2',
   'skills/litwork/SKILL.md': '771b7cead03c0d1d1e67af82e308ea0980b8ab18474026516798f559048beda7',
   'skills/lsp-setup/SKILL.md': '313ffd924f00a1523905d2588e0812c8edcaec84b114d2d487506bd905e5376d',
@@ -66,8 +68,6 @@ const PRE_MANIFEST_PAYLOAD_HASHES = Object.freeze({
   'skills/refactor/SKILL.md': '5fd2df1a36eae216f8af4db09e7e7d26231b167907ad19c49465153a1dcadde0',
   'skills/review-work/SKILL.md': 'acfef3ff9c6e243cb9b88169a67e749e27a2e530af09aed07a2d66dd932c3b5d',
   'skills/rules/SKILL.md': 'b880136962faeb3dea93cc42e30f5d3cc461a03fe71f7ff908d4b09170c38c5f',
-  'skills/skill-observer/scripts/skill-loop.mjs': '3f3f5265928c0d71175b0f23f71b836d1dc05e7efba407bfdc2d263c6aaed0ce',
-  'skills/skill-observer/scripts/validate-skills.mjs': 'cd71e88c45e57869114305f048257f3da7ec1dfa66f70d9529314defb5fa1a97',
   'skills/start-work/SKILL.md': 'ddc7357f99c78cd3405c1cb0202f9b13871efbe59f365e9f39727c429791028b',
   'skills/structural-search/SKILL.md': '3bbc13b5d0df58fbae07dd53e7ecbf13f311f12311cc3bd313803d63bd331ee0',
   'skills/visual-qa/references/complete-contract.md': '9562a993b9fc75f8cda5e5f810ff534590f4ace36e696bf60119c0b27ba19cd5',
@@ -152,13 +152,19 @@ const PRE_MANIFEST_LEGACY_PAYLOAD_HASHES = Object.freeze({
   'skills/programming/references/typescript/type-patterns.md': 'a21e27706f5d1e60be8f37d2d47949d0759158c999c4a08628f5f925b184d946',
   'skills/programming/references/worked-cases.md': 'ccb6fb8011cda2391d73c4f85ffc3b8038486d77134b986b046d1f62a2f7a9d2',
   'skills/remove-ai-slops/SKILL.md': 'db2f9e91dfd70a2077a091d1c422cba9f6d576af58868df4279d0e7542c29380',
+  'skills/skill-observer/SKILL.md': '1edf489673d958b3a7c60c5e1a036498510a02859dcf32e68a6d50b21f2fa344',
+  'skills/skill-observer/references/review-contract.md': 'f55dc8334f3b8d8498c84d57725fa03af8fbd689b2dd7cce25e49931629ee54f',
+  'skills/skill-observer/scripts/curator.mjs': '07f48d2160ba64584acd17ae9bd55efd6272546722576c288725b8850e3f0455',
+  'skills/skill-observer/scripts/review.mjs': '5b79fedae7f7c4d2b6d898717ae427bae1bd6d2c7f9f4bbc2f410f86468f7691',
+  'skills/skill-observer/scripts/skill-loop.mjs': '3f3f5265928c0d71175b0f23f71b836d1dc05e7efba407bfdc2d263c6aaed0ce',
+  'skills/skill-observer/scripts/validate-skills.mjs': 'cd71e88c45e57869114305f048257f3da7ec1dfa66f70d9529314defb5fa1a97',
   'skills/teammode/SKILL.md': '23db7152e2ce65cb5f7c52455d6cbd122485bb0fdb13813a8a54b824e8e44f08',
   'skills/teammode/references/explore-packet.md': 'c419c1c84783ddfae272e378c4f7e623ec4fbb437168d2d5cb8436baf4c14e30',
   'skills/teammode/references/general-purpose-packet.md': '45ad9cf82157563ebb20af360bb0b09d7afd7aa0fe114a91816523475ebdc88c',
   'skills/teammode/references/plan-packet.md': '68e292f9a6dc64f7e87a45417d5f92688aac9c2ffb7b519f9e2cab10b5ef4759',
   'skills/text-naturalization/SKILL.md': 'aa1ff8f68ab0bf71cb47818b536c4a2934da65adb413ee43ec5839b540b2df8e',
 });
-const USAGE = 'Usage: litgrok [install|uninstall] [--user|--project] [--dry-run] [--no-color] [--yes]\n       litgrok skill-loop <review|propose|list|apply|reject|rollback|curator> ...\n';
+const USAGE = 'Usage: litgrok [install|uninstall] [--user|--project] [--dry-run] [--no-color] [--yes]\n';
 const BRAILLE_FRAMES = ['⠋', '⠙', '⠹', '⠸', '⠼', '⠴', '⠦', '⠧', '⠇', '⠏'];
 const SPINNER_INTERVAL_MS = 80;
 const CLEAR_LINE = '\r\u001b[2K';
@@ -324,7 +330,7 @@ function receiptCard(options, root, colors, { status, written, current }) {
   ].join('\n');
 }
 
-function failureCard(options, root, colors, step, message) {
+function failureCard(options, root, colors, step, message, { showHookTrust = true } = {}) {
   return [
     '',
     `  ${paint('╭─ INSTALL FAILED', '38;2;230;60;60', colors)}`,
@@ -332,9 +338,11 @@ function failureCard(options, root, colors, step, message) {
     `  │ Scope: ${scopeDescription(options, root)}`,
     `  │ Step: ${step}`,
     `  │ Reason: ${message}`,
-    '  │ Hooks: project hooks require trust from a Git project root',
-    '  │ Trust: use /hooks-trust or, on Grok Build 1.0.13, grok --trust inspect --json',
-    '  │ Installer never runs git init or changes trust',
+    ...(showHookTrust ? [
+      '  │ Hooks: project hooks require trust from a Git project root',
+      '  │ Trust: use /hooks-trust or, on Grok Build 1.0.13, grok --trust inspect --json',
+      '  │ Installer never runs git init or changes trust',
+    ] : []),
     '  │ Next: resolve the issue and rerun the install',
     `  ${paint('╰─', '38;2;230;60;60', colors)}`,
     '',
@@ -348,7 +356,9 @@ function errorText(error) {
 function reportFailure(error, { stderr, stdout, options, root, colors, step }) {
   const lines = Array.isArray(error?.stderrLines) ? error.stderrLines : [`litgrok: ${errorText(error)}`];
   for (const line of lines) stderr.write(`${line}\n`);
-  stdout.write(failureCard(options, root, colors, error?.step ?? step, errorText(error)));
+  stdout.write(failureCard(options, root, colors, error?.step ?? step, errorText(error), {
+    showHookTrust: error?.legacyOwnershipConflict !== true,
+  }));
 }
 
 function normalizedRelativePath(relativePath) {
@@ -489,6 +499,12 @@ function retiredPayload(root, files, manifest) {
   const hashes = new Map([...previous].filter(([path]) => !currentPaths.has(path) && retiredPath(path)));
   for (const path of agentPaths) if (!hashes.has(path)) hashes.set(path, undefined);
   const directories = [];
+  const retiredSkillRoots = new Set(
+    [...hashes.keys()]
+      .filter((path) => path.startsWith('skills/'))
+      .map((path) => path.split('/').slice(0, 2).join('/'))
+      .filter((path) => !currentPaths.has(`${path}/SKILL.md`)),
+  );
 
   function visit(path) {
     const target = join(root, path);
@@ -511,7 +527,7 @@ function retiredPayload(root, files, manifest) {
     }
     directories.push(target);
   }
-  for (const path of skillRoots) visit(path);
+  for (const path of new Set([...skillRoots, ...retiredSkillRoots])) visit(path);
   for (const path of vendorRoots) visit(path);
   const entries = [...hashes].map(([relativePath, expectedHash]) => ({ root, relativePath, expectedHash, target: join(root, relativePath) }));
   return { entries, directories };
@@ -690,10 +706,6 @@ export async function run(args, context = {}) {
     stdout.write(`${renderMark({ size: 'banner', productName: `grok v${packageVersion()}`, env, isTTY: stdout.isTTY, args }).join('\n')}\n\n${USAGE}`);
     return 0;
   }
-  if (args[0] === 'skill-loop') {
-    const { runSkillLoop } = await import('../.grok/skills/skill-observer/scripts/skill-loop.mjs');
-    return runSkillLoop(args.slice(1), { cwd, env, stderr, stdout });
-  }
   const options = parseInstall(args);
   if (!options) {
     stderr.write(USAGE);
@@ -792,7 +804,13 @@ export async function run(args, context = {}) {
           if (owned[index] === 'conflict') stderrLines.push(`Refusing to ${options.command === 'install' ? 'overwrite' : 'remove'} different existing file: ${files[index].target}`);
         }
         for (let index = 0; index < legacyEntries.length; index += 1) {
-          if (legacyStates[index] === 'conflict') stderrLines.push(`Refusing to ${options.command === 'install' ? 'overwrite' : 'remove'} different existing file: ${legacyEntries[index].target}`);
+          if (legacyStates[index] !== 'conflict') continue;
+          const entry = legacyEntries[index];
+          const retiredSkill = retiredDirectories.some((directory) => (
+            directory.startsWith(`${join(root, 'skills')}${sep}`) && entry.target.startsWith(`${directory}${sep}`)
+          ));
+          const retiredDirectory = retiredSkill ? 'the retired skill directory' : 'the retired payload directory';
+          stderrLines.push(`Refusing legacy conflict: ${entry.target} is not package-owned. Move it out of ${retiredDirectory} or remove it yourself, then rerun the install so the directory can be cleaned.`);
         }
         const legacyDetail = legacyEntries.length === 0
           ? ''
@@ -800,6 +818,7 @@ export async function run(args, context = {}) {
         const error = new Error(`${counts.missing} missing · ${counts.current} already-current · ${counts.owned} owned · ${counts.conflicts} conflicts${legacyDetail}`);
         error.step = 'OWNERSHIP';
         error.stderrLines = stderrLines;
+        error.legacyOwnershipConflict = legacyCounts.conflicts > 0;
         throw error;
       }
       const legacyDetail = legacyEntries.length === 0

package/docs/assets/readme/badge-version.svg

@@ -1 +1 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="146" height="20" role="img" aria-label="local: 1.0.2"><title>local: 1.0.2</title><g shape-rendering="crispEdges"><rect width="49" height="20" fill="#080d14"/><rect x="49" width="97" height="20" fill="#ff6337"/></g><g fill="#fff" text-anchor="middle" font-family="Verdana,Geneva,DejaVu Sans,sans-serif" text-rendering="geometricPrecision" font-size="110"><text x="255" y="140" textLength="290" transform="scale(.1)">local</text><text x="965" y="140" textLength="870" transform="scale(.1)" fill="#080D14">1.0.2</text></g></svg>
+<svg xmlns="http://www.w3.org/2000/svg" width="146" height="20" role="img" aria-label="local: 1.0.3"><title>local: 1.0.3</title><g shape-rendering="crispEdges"><rect width="49" height="20" fill="#080d14"/><rect x="49" width="97" height="20" fill="#ff6337"/></g><g fill="#fff" text-anchor="middle" font-family="Verdana,Geneva,DejaVu Sans,sans-serif" text-rendering="geometricPrecision" font-size="110"><text x="255" y="140" textLength="290" transform="scale(.1)">local</text><text x="965" y="140" textLength="870" transform="scale(.1)" fill="#080D14">1.0.3</text></g></svg>

package/docs/privacy.md

@@ -4,9 +4,7 @@ This describes package source behavior, not Grok or a model provider's privacy p
 
 Passive hooks in `.grok/hooks/record-passive-event.mjs` read hook JSON and record session identity, cwd/workspace paths, event names and time, optional prompt IDs, and tool names with input digests. They inspect optional prompt text for planning activation without persisting raw prompt/tool input in those passive records. Hashed filenames do not anonymize the JSON: records retain the session ID. The hedge guard examines proposed paths and content; Stop may record a plan-gate reason.
 
-Project `.grok/litgrok/` can contain session ledgers, pending reviews, proposals, usage data, skill ledgers, and full-content snapshot blobs. The learning loop also uses user `.grok/litgrok/` transaction, staging, and archive data. Proposals can contain rationale, references, and proposed skill text. Approved applications target user skills. These files may reveal project information even when they contain no credentials.
-
-An explicitly requested `skill-loop review` runs `grok export`, scrubs known secret patterns, bounds the transcript excerpt to 64 KiB, and passes it with eligible skill content and session/root references to `grok --single`. This source path is in `.grok/skills/skill-observer/scripts/review.mjs`. Grok may send that input to its configured provider. The prompt is also passed as a command-line argument and may be visible to local process inspection. Pattern-based scrubbing is not a guarantee that all sensitive information is removed. Inspect the source and data before requesting a review of sensitive work. Disabled review tools and web search do not imply offline model execution.
+Project `.grok/litgrok/` contains package-owned session ledgers and may contain other generated data from installed or older package versions. Older skill-review state is no longer read, migrated, rewritten, or deleted by LitGrok; it remains inert for the owner to manage.
 
 Optional helpers may invoke Grok or external scientific tools; their behavior and dependencies remain separate. No blanket claim that all package-guided work stays offline is made.
 

package/docs/reference.md

@@ -35,7 +35,7 @@ flowchart TD
 
 ## What it is
 
-- 34 Grok-native skill documents at `.grok/skills/<name>/SKILL.md`.
+- 33 Grok-native skill documents at `.grok/skills/<name>/SKILL.md`.
 - A project rule at `.grok/rules/00-litgrok.md`.
 - A bounded `SessionStart` hook that prints the standard mark once per validated session and announces the installed payload.
 - A `PreToolUse` hook that rejects hedge phrasing in pending reader-facing writes while skipping quoted state enums, JSON/YAML scalars, fenced code, and status tables. The host treats only an explicit deny with exit 2 as blocking; exit 0 allows, while timeouts, crashes, and malformed output fail-open and the write proceeds.
@@ -62,10 +62,10 @@ flowchart LR
     HK --> PLAN --> LEDGER
     HK --> HEDGE
     RL --> LG
-    LG --> S["34 skills · 11 agents"]
+    LG --> S["33 skills · 11 agents"]
 ```
 
-> **A narrow host boundary.** `plugin.json` exposes the package, hooks feed the plan gate and hedge guard, and rules provide project guidance while the session ledger records bounded state. Together these surfaces carry LitGrok’s 34 skills and 11 agents into Grok Build.
+> **A narrow host boundary.** `plugin.json` exposes the package, hooks feed the plan gate and hedge guard, and rules provide project guidance while the session ledger records bounded state. Together these surfaces carry LitGrok’s 33 skills and 11 agents into Grok Build.
 
 ## Install
 
@@ -76,7 +76,7 @@ npm exec --yes --package @litfamily/litgrok@latest -- litgrok install
 Pin a version when you need a reproducible install:
 
 ```bash
-npm exec --yes --package @litfamily/litgrok@1.0.2 -- litgrok install
+npm exec --yes --package @litfamily/litgrok@1.0.3 -- litgrok install
 ```
 
 Preview without writing files:
@@ -201,8 +201,7 @@ ls ~/.grok/hooks/session-start.json ~/.grok/hooks/deliverable-hedge-guard.json
 
 The session mark uses an atomic, empty `.ignited` marker beside the package-owned
 session ledger under `.grok/litgrok/session-ledger/`. Replayed or concurrent
-SessionStart events keep the presence and pending-review notices without repeating
-the mark. Invalid session identity or unsafe marker state fails before mark output.
+SessionStart events keep the presence notice without repeating the mark. Invalid session identity or unsafe marker state fails before mark output.
 Grok has no per-activation logo hook. The five existing skill activation contracts
 ask the model to begin with exactly one `▲ LIT · <discipline>` probe line; `litwork`
 declares the same advisory line with explicit once-per-request and quoted-content
@@ -210,26 +209,9 @@ exclusions. The SessionStart script writes its standard mark to stdout; this
 prompt requirement is separate from that script output. No hook or parser
 deterministically routes bare `lit`, and native host display remains unverified.
 
-## Skill learning loop
+## Previous review state
 
-LitGrok can turn a durable correction or reusable workflow signal into a reviewable skill proposal. `Stop` records only bounded per-session turn state, and `SessionStart` may add one pending-review notice after its existing payload banner. Neither hook starts a model. The model-backed review runs only when the user invokes `/skill-observer review` or the foreground `skill-loop review` CLI; it exports the selected session, builds a bounded secret-scrubbed packet, disables child tools, and enforces a bounded 65-second process budget (5 seconds for export and 60 seconds for the model) with a recursion guard.
-
-The learning loop is currently supported on macOS and Linux. On Windows, `/skill-observer review` and every `skill-loop` command fail before subprocess launch, project learning-state access, or user-skill access with `WINDOWS_SKILL_LOOP_UNSUPPORTED`. The passive hooks and installer remain available; native Windows learning-loop support requires a dedicated ACL and process-job helper and is not claimed by this release.
-
-Review is proposal-only. `autoApply` is always false, transcript text is inert data, and nothing changes until the user explicitly runs `apply <proposal-id>`. Pending proposals, content-addressed ledger entries, and rollback blobs stay in the installed project's `.grok/litgrok/` state. An approved skill is created or patched only under `$HOME/.grok/skills/<name>/` and carries `metadata: { litgrokAgentGenerated: "true" }`. Packaged skills, project payload targets, symlinks, and existing user skills without that marker are protected.
-
-From an installed project, use the package CLI directly when you want a replayable foreground command:
-
-```bash
-npm exec --yes --package @litfamily/litgrok@1.0.2 -- litgrok skill-loop review <session-id>
-npm exec --yes --package @litfamily/litgrok@1.0.2 -- litgrok skill-loop list
-npm exec --yes --package @litfamily/litgrok@1.0.2 -- litgrok skill-loop apply <proposal-id>
-npm exec --yes --package @litfamily/litgrok@1.0.2 -- litgrok skill-loop reject <proposal-id>
-npm exec --yes --package @litfamily/litgrok@1.0.2 -- litgrok skill-loop rollback <ledger-id>
-npm exec --yes --package @litfamily/litgrok@1.0.2 -- litgrok skill-loop curator
-```
-
-`apply` prints the ledger id needed for rollback. The deterministic curator is also user-invoked: by default it runs at most once every seven days, requires at least two idle hours, marks eligible unpinned agent-owned skills stale after 30 idle days, and archives them outside discovery after 90 idle days. It makes a full backup before a transition and never deletes a skill package; `--force` bypasses only the seven-day run interval for an explicit test or maintenance invocation.
+LitGrok no longer schedules skill reviews or reads, migrates, rewrites, or deletes their old project or user state. Existing review files remain inert and are left for their owners to manage.
 
 ## Verify
 

package/docs/reference_ko-KR.md

@@ -35,7 +35,7 @@ flowchart TD
 
 ## 무엇을 제공하나요?
 
-- `.grok/skills/<name>/SKILL.md`에 Grok-native skill 문서 34개
+- `.grok/skills/<name>/SKILL.md`에 Grok-native skill 문서 33개
 - `.grok/rules/00-litgrok.md` project rule
 - 설치된 payload를 짧게 알리는 `SessionStart` hook
 - reader-facing write의 hedge 표현을 차단하되 quoted state enum, JSON/YAML scalar, fenced code, status table은 제외하는 `PreToolUse` hook. Host는 명시적인 deny와 exit 2만 차단으로 처리합니다. exit 0은 허용이고 timeout, crash, malformed output은 fail-open이므로 write가 진행됩니다.
@@ -62,10 +62,10 @@ flowchart LR
     HK --> PLAN --> LEDGER
     HK --> HEDGE
     RL --> LG
-    LG --> S["34 skills · 11 agents"]
+    LG --> S["33 skills · 11 agents"]
 ```
 
-> **Host 경계는 좁고 명확합니다.** `plugin.json`이 package를 노출하고, hook은 plan gate와 hedge guard로 연결되며, rule은 project guidance가 됩니다. session ledger에는 bounded state를 기록하고, 이 표면들이 34개 skill과 11개 agent를 Grok Build에서 사용할 수 있게 합니다.
+> **Host 경계는 좁고 명확합니다.** `plugin.json`이 package를 노출하고, hook은 plan gate와 hedge guard로 연결되며, rule은 project guidance가 됩니다. session ledger에는 bounded state를 기록하고, 이 표면들이 33개 skill과 11개 agent를 Grok Build에서 사용할 수 있게 합니다.
 
 ## 설치
 
@@ -76,7 +76,7 @@ npm exec --yes --package @litfamily/litgrok@latest -- litgrok install
 재현 가능한 설치는 버전을 고정합니다.
 
 ```bash
-npm exec --yes --package @litfamily/litgrok@1.0.2 -- litgrok install
+npm exec --yes --package @litfamily/litgrok@1.0.3 -- litgrok install
 ```
 
 파일을 쓰지 않고 미리보기:
@@ -197,7 +197,7 @@ mark나 lockup 배열을 복사해 색을 입혀도 글리프와 이름을 보
 
 SessionStart 스크립트는 검증된 세션마다 표준 mark를 stdout에 한 번 씁니다.
 `.grok/litgrok/session-ledger/`의 빈 `.ignited` 파일을 원자적으로 생성해 중복·동시
-이벤트에서도 mark를 반복하지 않습니다. 기존 payload 안내와 검토 대기 알림은 유지합니다.
+이벤트에서도 mark를 반복하지 않습니다. 기존 payload 안내는 유지합니다.
 잘못된 세션 정보나 안전하지 않은 marker가 있으면 mark 출력 전에 실패합니다.
 Grok에는 activation별 logo hook이 없습니다. 기존 다섯 skill의 응답 시작 규약은 모델이
 `▲ LIT · <discipline>` 한 줄로 답변을 시작하도록 요청합니다. `litwork`도
@@ -206,26 +206,9 @@ advisory 계약을 선언하며, 그 스크립트 stdout과 구분됩니다. bar
 결정적으로 라우팅하거나 passive hook 출력으로 활성화를 보장하지 않으며,
 native host의 실제 표시는 검증하지 않았습니다.
 
-## Skill learning loop
+## 이전 review state
 
-LitGrok은 반복해서 쓸 수 있는 correction이나 workflow signal을 검토 가능한 skill proposal로 만들 수 있습니다. `Stop`은 session별 bounded turn state만 기록하고, `SessionStart`는 기존 payload banner 다음에 pending-review 안내 한 줄만 추가할 수 있습니다. 두 hook 모두 model을 시작하지 않습니다. Model review는 사용자가 `/skill-observer review` 또는 foreground `skill-loop review` CLI를 직접 실행할 때만 동작합니다. 선택한 session을 export하고 secret을 제거한 bounded packet을 만든 뒤 child tool을 끄며, recursion guard와 bounded 65초 process budget(export 5초, model 60초)을 적용합니다.
-
-현재 learning loop는 macOS와 Linux에서 지원합니다. Windows에서는 `/skill-observer review`와 모든 `skill-loop` command가 subprocess, project learning state, user skill에 접근하기 전에 `WINDOWS_SKILL_LOOP_UNSUPPORTED`로 중단됩니다. Passive hook과 installer는 계속 사용할 수 있습니다. Native Windows learning loop에는 전용 ACL 및 process-job helper가 필요하며, 이번 release는 그 지원을 주장하지 않습니다.
-
-Review는 proposal만 만듭니다. `autoApply`는 항상 false이고 transcript text는 inert data입니다. 사용자가 `apply <proposal-id>`를 명시적으로 실행하기 전에는 아무것도 바뀌지 않습니다. Pending proposal, content-addressed ledger, rollback blob은 설치된 project의 `.grok/litgrok/` state에 저장됩니다. 승인된 skill은 `$HOME/.grok/skills/<name>/` 아래에서만 생성하거나 수정하며 `metadata: { litgrokAgentGenerated: "true" }` marker를 가집니다. Packaged skill, project payload target, symlink, marker가 없는 기존 user skill은 보호됩니다.
-
-설치된 project에서는 다음 package CLI를 foreground command로 실행할 수 있습니다.
-
-```bash
-npm exec --yes --package @litfamily/litgrok@1.0.2 -- litgrok skill-loop review <session-id>
-npm exec --yes --package @litfamily/litgrok@1.0.2 -- litgrok skill-loop list
-npm exec --yes --package @litfamily/litgrok@1.0.2 -- litgrok skill-loop apply <proposal-id>
-npm exec --yes --package @litfamily/litgrok@1.0.2 -- litgrok skill-loop reject <proposal-id>
-npm exec --yes --package @litfamily/litgrok@1.0.2 -- litgrok skill-loop rollback <ledger-id>
-npm exec --yes --package @litfamily/litgrok@1.0.2 -- litgrok skill-loop curator
-```
-
-`apply`는 rollback에 필요한 ledger id를 출력합니다. Deterministic curator도 user-invoked입니다. 기본적으로 7일에 한 번만 실행되고, 마지막 activity 뒤 최소 2시간이 지나야 하며, pin되지 않은 agent-owned skill을 30일 idle 뒤 stale로 표시하고 90일 idle 뒤 discovery 밖으로 archive합니다. Transition 전에는 전체 backup을 만들고 skill package를 삭제하지 않습니다. `--force`는 명시적인 test 또는 maintenance 실행에서 7일 interval만 건너뜁니다.
+LitGrok은 더 이상 skill review를 예약하지 않으며, 기존 project/user review state를 읽거나 이전·수정·삭제하지 않습니다. 남아 있는 review 파일은 inert 상태로 두며 소유자가 직접 관리합니다.
 
 ## 검증