litcodex-ai 0.3.16 → 0.3.18

package/README.md

@@ -61,7 +61,7 @@ every success criterion passes. Durable loop state lives under `.litcodex/lit-lo
 
 LitCodex also ships a sibling family of triggers and phrases — `litwork`, `lit-plan`, `litgoal`,
 `review-work`, `litresearch`, plus `lit plan` / `lit review` / `lit research` / `lit goal` and the
-`lit start work` handoff — alongside a 25-skill library and hook components, all registered as a
+`lit start work` handoff — alongside a 27-skill library and hook components, all registered as a
 single Codex plugin.
 
 The bundled `public-page-reader` skill adds a public-only Node stdlib runtime with safety preflight,

package/node_modules/@litcodex/lit-loop/directives/lit-recap.md

@@ -0,0 +1,83 @@
+<lit-recap-mode>
+
+**MANDATORY**: First user-visible line this turn MUST be exactly:
+`🔥 LIT-RECAP ENABLED 🔥`
+
+Print that line verbatim, then produce the recap. You are now in lit-recap: the
+read-only work-RECAP surface. Your one job is to merge the durable LitCodex
+ledgers with what you already know from THIS session and present one honest
+Korean work recap under the locked headers below. You summarize; you never
+advance the work.
+
+# Read-only contract — 읽기 전용 (절대 규칙)
+lit-recap은 읽기 전용이다. You MUST NOT write, create, edit, delete, or move any
+file, ledger, or state; MUST NOT run any state-mutating command; and MUST NOT
+bind, advance, or complete any goal. Reading files and summarizing is the entire
+job. If the user wants to change or continue the work, point them to the
+matching lit mode (`lit`, `litwork`, `litgoal`) — do not do it here.
+
+# Step 1 — Read the durable ledgers (존재하는 것만 읽는다)
+Read whichever of these exist in the project root with your read-only file
+tools; silently skip any that are missing:
+
+- `.litcodex/boulder.json` — work ledger: a `works` map (or a single object)
+  with `active_plan`, `plan_name`, `status` (`active|completed|paused|abandoned`),
+  `session_ids`, `worktree_path`.
+- `.litcodex/lit-loop/brief.md` — the original task brief.
+- `.litcodex/lit-loop/goals.json` — goals: each has `objective`, `status`
+  (`pending|in_progress|complete|failed|blocked`) and `successCriteria[]`
+  (each: `scenario`, `userModel`, `expectedEvidence`, `capturedEvidence`, `status`).
+- `.litcodex/lit-loop/ledger.jsonl` — append-only event log, one JSON object per
+  line (`at`, `kind`, …).
+- `.litcodex/lit-loop/evidence/` — captured real-surface evidence artifacts
+  (report their paths; do not modify them).
+- `.litcodex/lit-loop/<sessionId>/…` — per-session copies of the same files,
+  when present.
+- `.litcodex/start-work/ledger.jsonl` — start-work task ledger
+  (`task-completed` entries with evidence paths).
+
+# Step 2 — Fold in the current session (하이브리드)
+The ledgers are durable but blind to the live session. Merge in what actually
+happened in THIS conversation — files touched, commands run, results observed,
+decisions made — and reconcile: when the session state is newer than a ledger
+entry, say so instead of pretending the ledger is current. Never invent items
+that appear in neither source; an empty section stays under its header as
+`없음`.
+
+# Step 3 — Output template (헤더는 아래 문구 그대로, verbatim)
+
+# 작업 리캡 (lit-recap)
+
+## ✅ 완료된 작업
+- 완료 항목마다 기술 종류 태그를 앞에 붙인다: `[TypeScript]`, `[npm]`, `[docs]`,
+  `[test]` 등. 근거(원장 항목 또는 세션 관찰)가 있는 것만 적는다.
+
+## 🔄 진행 중
+- 시작되었지만 끝나지 않은 작업과 현재 상태.
+
+## ⛔ 블로커
+- 진행을 막고 있는 항목. `blocked`/`failed` 상태와 이유를 그대로 보고한다.
+
+## 📁 증거 경로
+- `.litcodex/lit-loop/evidence/` 등 실제 존재하는 증거 파일 경로 목록.
+
+## ➡️ 다음 단계
+- 원장과 세션 상태가 가리키는 가장 작은 다음 행동 1–3개.
+
+# Language & brevity switches
+- 기본 언어는 한국어다. Switch the whole recap to English ONLY when the prompt
+  carries `--en` / `--english` or asks naturally ("in English", "영어로").
+- If the prompt carries `--brief` or asks naturally ("짧게"), output ONLY the
+  `## ⚡ 요약` digest — at most 5 lines covering done / in-progress / blockers /
+  next step — instead of the full template.
+- 커밋 해시, 파일 경로, 패키지·명령 이름 같은 기술 토큰은 번역하지 말고 그대로
+  (verbatim) 쓴다.
+
+# Stop rules
+- Emit the recap and stop. Do NOT start implementing, testing, or planning the
+  next step you just recommended.
+- If NO ledger file exists and the session carries no work state, say exactly
+  that under `# 작업 리캡 (lit-recap)` (모든 섹션 `없음`) rather than inventing
+  history.
+
+</lit-recap-mode>

package/node_modules/@litcodex/lit-loop/dist/markers.d.ts

@@ -12,4 +12,6 @@ export declare const LITRESEARCH_DIRECTIVE_MARKER: "<litresearch-mode>";
 export declare const LITRESEARCH_DIRECTIVE_CLOSE: "</litresearch-mode>";
 export declare const START_WORK_DIRECTIVE_MARKER: "<start-work-mode>";
 export declare const START_WORK_DIRECTIVE_CLOSE: "</start-work-mode>";
+export declare const LIT_RECAP_DIRECTIVE_MARKER: "<lit-recap-mode>";
+export declare const LIT_RECAP_DIRECTIVE_CLOSE: "</lit-recap-mode>";
 export type LitLoopDirectiveMarker = typeof LIT_LOOP_DIRECTIVE_MARKER;

package/node_modules/@litcodex/lit-loop/dist/markers.js

@@ -18,3 +18,5 @@ export const LITRESEARCH_DIRECTIVE_MARKER = "<litresearch-mode>";
 export const LITRESEARCH_DIRECTIVE_CLOSE = "</litresearch-mode>";
 export const START_WORK_DIRECTIVE_MARKER = "<start-work-mode>";
 export const START_WORK_DIRECTIVE_CLOSE = "</start-work-mode>";
+export const LIT_RECAP_DIRECTIVE_MARKER = "<lit-recap-mode>";
+export const LIT_RECAP_DIRECTIVE_CLOSE = "</lit-recap-mode>";

package/node_modules/@litcodex/lit-loop/dist/modes.d.ts

@@ -1,6 +1,6 @@
 import type { LitTriggerToken } from "./trigger.js";
 /** Lit-family modes. Multiple tokens may map to one mode (lit/litcodex/lit-loop → lit-loop). */
-export type LitMode = "lit-loop" | "litwork" | "lit-plan" | "litgoal" | "review-work" | "litresearch" | "start-work";
+export type LitMode = "lit-loop" | "litwork" | "lit-plan" | "litgoal" | "review-work" | "litresearch" | "start-work" | "lit-recap";
 /** Per-mode routing spec: its marker pair (guard) + resolved directive path (loader). */
 export interface LitModeSpec {
     readonly mode: LitMode;

package/node_modules/@litcodex/lit-loop/dist/modes.js

@@ -14,7 +14,7 @@
 //
 // Imports markers + the trigger token type only (no cycle: hook → modes → {markers, trigger}).
 import { fileURLToPath } from "node:url";
-import { LIT_LOOP_DIRECTIVE_CLOSE, LIT_LOOP_DIRECTIVE_MARKER, LIT_PLAN_DIRECTIVE_CLOSE, LIT_PLAN_DIRECTIVE_MARKER, LITGOAL_DIRECTIVE_CLOSE, LITGOAL_DIRECTIVE_MARKER, LITRESEARCH_DIRECTIVE_CLOSE, LITRESEARCH_DIRECTIVE_MARKER, LITWORK_DIRECTIVE_CLOSE, LITWORK_DIRECTIVE_MARKER, REVIEW_WORK_DIRECTIVE_CLOSE, REVIEW_WORK_DIRECTIVE_MARKER, START_WORK_DIRECTIVE_CLOSE, START_WORK_DIRECTIVE_MARKER, } from "./markers.js";
+import { LIT_LOOP_DIRECTIVE_CLOSE, LIT_LOOP_DIRECTIVE_MARKER, LIT_PLAN_DIRECTIVE_CLOSE, LIT_PLAN_DIRECTIVE_MARKER, LIT_RECAP_DIRECTIVE_CLOSE, LIT_RECAP_DIRECTIVE_MARKER, LITGOAL_DIRECTIVE_CLOSE, LITGOAL_DIRECTIVE_MARKER, LITRESEARCH_DIRECTIVE_CLOSE, LITRESEARCH_DIRECTIVE_MARKER, LITWORK_DIRECTIVE_CLOSE, LITWORK_DIRECTIVE_MARKER, REVIEW_WORK_DIRECTIVE_CLOSE, REVIEW_WORK_DIRECTIVE_MARKER, START_WORK_DIRECTIVE_CLOSE, START_WORK_DIRECTIVE_MARKER, } from "./markers.js";
 /** Resolve a path relative to this module (percent-decoding, space/#/Hangul-safe). */
 function resolveFromHere(rel) {
     return fileURLToPath(new URL(rel, import.meta.url));
@@ -67,6 +67,12 @@ export const MODE_BY_TOKEN = Object.freeze({
         closeMarker: START_WORK_DIRECTIVE_CLOSE,
         directivePath: resolveFromHere("../directives/start-work.md"),
     }),
+    "lit-recap": Object.freeze({
+        mode: "lit-recap",
+        openMarker: LIT_RECAP_DIRECTIVE_MARKER,
+        closeMarker: LIT_RECAP_DIRECTIVE_CLOSE,
+        directivePath: resolveFromHere("../directives/lit-recap.md"),
+    }),
 });
 /** The mode spec for a matched token. Total over the token union (every token has a spec). */
 export function modeForToken(token) {

package/node_modules/@litcodex/lit-loop/dist/skill-mention-scope.js

@@ -39,6 +39,8 @@ function tokenForSkillName(skillName) {
             return "litgoal";
         case "litresearch":
             return "litresearch";
+        case "lit-recap":
+            return "lit-recap";
         case "start-work":
             return "start-work";
         case "review-work":

package/node_modules/@litcodex/lit-loop/dist/trigger.d.ts

@@ -1,5 +1,5 @@
 /** The accepted bounded lit-family tokens, longest-first (ordering is load-bearing — see below). */
-export type LitTriggerToken = "start-work" | "review-work" | "litresearch" | "lit-loop" | "lit-plan" | "litcodex" | "litgoal" | "litwork" | "lit";
+export type LitTriggerToken = "start-work" | "review-work" | "litresearch" | "lit-recap" | "lit-loop" | "lit-plan" | "litcodex" | "litgoal" | "litwork" | "lit";
 /**
  * Frozen tuple of the accepted tokens in match-priority (longest-first) order.
  * Exported so tests and the mode router (modes.ts) can enumerate without re-deriving.
@@ -14,9 +14,12 @@ export declare const LIT_TRIGGER_TOKENS: readonly LitTriggerToken[];
  *
  * MUST NOT carry the /g or /y flag: a global regex retains `lastIndex` between calls and would
  * make `.test()` return alternating results for the same input. Longest-first alternation
- * (`start-work|review-work|litresearch|lit-loop|lit-plan|litcodex|litgoal|litwork|lit`) guarantees a longer family token wins over a
- * bare `lit` at the same start; the trailing-`-` lookahead means `lit work` (space) is a bare `lit`
- * while `litwork` (glued) is the work mode. No nested quantifiers / no backreferences ⇒ ReDoS-free.
+ * (`start-work|review-work|litresearch|lit-recap|lit-loop|lit-plan|litcodex|litrecap|litgoal|litwork|recap|리캡|lit`)
+ * guarantees a longer family token wins over a bare `lit` at the same start; the trailing-`-`
+ * lookahead means `lit work` (space) is a bare `lit` while `litwork` (glued) is the work mode.
+ * The `litrecap` / `recap` / `리캡` alternatives are ROUTING ALIASES normalized to the canonical
+ * `lit-recap` token by `matchLitTrigger` (they are not members of the token union).
+ * No nested quantifiers / no backreferences ⇒ ReDoS-free.
  */
 export declare const LIT_TRIGGER_PATTERN: RegExp;
 /** Structured result of a successful match. */

package/node_modules/@litcodex/lit-loop/dist/trigger.js

@@ -2,9 +2,10 @@
 //
 // Single source of truth for deciding whether a user prompt activates the LitCodex `lit-loop`
 // workflow. Pure, side-effect-free, Unicode-aware. Accepts the bounded tokens `lit`, `lit-loop`,
-// and `litcodex` (case-insensitive) and rejects every substring collision (`split`, `literal`,
-// `litmus`, `lithium`, `glitter`, `flit`, `slit`, `litter`, …) while respecting Korean (Hangul)
-// and English boundaries.
+// and `litcodex` (case-insensitive), the sibling mode tokens (incl. `lit-recap` with its
+// `litrecap` / `recap` / `리캡` aliases, all normalized to the single `lit-recap` token), and
+// rejects every substring collision (`split`, `literal`, `litmus`, `lithium`, `glitter`, `flit`,
+// `slit`, `litter`, `recapture`, …) while respecting Korean (Hangul) and English boundaries.
 //
 // This module imports NOTHING from `state-store`, `directive`, `guards`, `markers`, or
 // `codex-hook` (one-way: hook → trigger, never the reverse). It reads no files, touches no state,
@@ -18,6 +19,7 @@ export const LIT_TRIGGER_TOKENS = Object.freeze([
     "start-work",
     "review-work",
     "litresearch",
+    "lit-recap",
     "lit-loop",
     "lit-plan",
     "litcodex",
@@ -34,11 +36,14 @@ export const LIT_TRIGGER_TOKENS = Object.freeze([
  *
  * MUST NOT carry the /g or /y flag: a global regex retains `lastIndex` between calls and would
  * make `.test()` return alternating results for the same input. Longest-first alternation
- * (`start-work|review-work|litresearch|lit-loop|lit-plan|litcodex|litgoal|litwork|lit`) guarantees a longer family token wins over a
- * bare `lit` at the same start; the trailing-`-` lookahead means `lit work` (space) is a bare `lit`
- * while `litwork` (glued) is the work mode. No nested quantifiers / no backreferences ⇒ ReDoS-free.
+ * (`start-work|review-work|litresearch|lit-recap|lit-loop|lit-plan|litcodex|litrecap|litgoal|litwork|recap|리캡|lit`)
+ * guarantees a longer family token wins over a bare `lit` at the same start; the trailing-`-`
+ * lookahead means `lit work` (space) is a bare `lit` while `litwork` (glued) is the work mode.
+ * The `litrecap` / `recap` / `리캡` alternatives are ROUTING ALIASES normalized to the canonical
+ * `lit-recap` token by `matchLitTrigger` (they are not members of the token union).
+ * No nested quantifiers / no backreferences ⇒ ReDoS-free.
  */
-export const LIT_TRIGGER_PATTERN = /(?:^|[^\p{L}\p{N}_])(start-work|review-work|litresearch|lit-loop|lit-plan|litcodex|litgoal|litwork|lit)(?![\p{L}\p{N}_-])/iu;
+export const LIT_TRIGGER_PATTERN = /(?:^|[^\p{L}\p{N}_])(start-work|review-work|litresearch|lit-recap|lit-loop|lit-plan|litcodex|litrecap|litgoal|litwork|recap|리캡|lit)(?![\p{L}\p{N}_-])/iu;
 const NOT_A_STRING = "lit trigger: prompt must be a string";
 /**
  * Returns true iff `prompt` contains at least one bounded lit trigger.
@@ -65,14 +70,18 @@ export function matchLitTrigger(prompt) {
         throw new TypeError(NOT_A_STRING);
     }
     const searchable = maskMarkdownCode(prompt);
-    const scan = /(?:^|[^\p{L}\p{N}_])(start-work|review-work|litresearch|lit-loop|lit-plan|litcodex|litgoal|litwork|lit)(?![\p{L}\p{N}_-])/giu;
+    const scan = /(?:^|[^\p{L}\p{N}_])(start-work|review-work|litresearch|lit-recap|lit-loop|lit-plan|litcodex|litrecap|litgoal|litwork|recap|리캡|lit)(?![\p{L}\p{N}_-])/giu;
     for (const m of searchable.matchAll(scan)) {
         const raw = m[1];
         if (raw === undefined) {
             continue;
         }
         const index = (m.index ?? 0) + m[0].length - raw.length;
-        const token = raw.toLowerCase();
+        const lowered = raw.toLowerCase();
+        // Canonicalize the recap routing aliases (D1): litrecap / recap / 리캡 → the lit-recap token.
+        const token = lowered === "litrecap" || lowered === "recap" || lowered === "리캡"
+            ? "lit-recap"
+            : lowered;
         if (isSlashCommandOrPathToken(prompt, index, token)) {
             continue;
         }
@@ -94,7 +103,7 @@ export function matchLitTrigger(prompt) {
 function naturalPhraseAfterLit(prompt, searchable, index, rawLength) {
     const start = index + rawLength;
     const rest = searchable.slice(start);
-    const m = /^(\s+)(start\s+work|plan|review|research|goal)(?![\p{L}\p{N}_-])/iu.exec(rest);
+    const m = /^(\s+)(start\s+work|plan|review|research|goal|recap)(?![\p{L}\p{N}_-])/iu.exec(rest);
     if (m === null || m[1] === undefined || m[2] === undefined) {
         return null;
     }
@@ -105,6 +114,7 @@ function naturalPhraseAfterLit(prompt, searchable, index, rawLength) {
         review: "review-work",
         research: "litresearch",
         goal: "litgoal",
+        recap: "lit-recap",
     };
     const token = tokenByPhrase[normalized];
     if (token === undefined) {

package/node_modules/@litcodex/lit-loop/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@litcodex/lit-loop",
-	"version": "0.3.16",
+	"version": "0.3.18",
 	"description": "LitCodex Lit-Loop runtime: durable repo-native multi-goal orchestration with embedded success criteria and observable evidence audit.",
 	"type": "module",
 	"bin": {

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "litcodex-ai",
-	"version": "0.3.16",
+	"version": "0.3.18",
 	"description": "Codex loop harness installer. Run `npx litcodex-ai install` to set up the LitCodex Codex platform: the bare `lit` hook and the durable lit-loop runtime.",
 	"keywords": ["codex", "litcodex", "lit-loop", "ai-agents", "orchestration"],
 	"author": "LitCodex Authors",
@@ -15,7 +15,7 @@
 	},
 	"files": ["bin", "dist", "model-catalog.json", "README.md", "LICENSE"],
 	"dependencies": {
-		"@litcodex/lit-loop": "0.3.16"
+		"@litcodex/lit-loop": "0.3.18"
 	},
 	"bundledDependencies": ["@litcodex/lit-loop"],
 	"scripts": {