@c-d-cc/reap 0.15.1 → 0.15.2

package/README.ja.md

@@ -329,7 +329,7 @@ autoIssueReport: true    # デフォルト: true（gh CLIがある場合）
 | `/reap.merge.sync` | Genome-ソース間の整合性を検証（AI比較、ユーザー確認） |
 | `/reap.merge.validation` | 機械的テストを実行（bun test、tsc、build） |
 | **`/reap.merge.evolve`** | **マージライフサイクル全体を自動実行** |
-| `/reap.refreshKnowledge` | サブエージェント用REAPコンテキストのロード（Genome、Environment、状態） |
+| `/reap.refreshKnowledge` | REAPコンテキストの再ロード（Genome、Environment、状態）。context compaction後やサブエージェントで使用 |
 
 ### SessionStart Hook [↗](https://reap.cc/docs/hooks)
 
@@ -363,7 +363,7 @@ strict:
 |------|------|
 | アクティブGenerationなし / 実装ステージ外 | コード変更は完全にブロック |
 | Implementationステージ | `02-planning.md`の範囲内でのみ変更許可 |
-| エスケープハッチ | ユーザーが「override」「bypass strict」等を明示的に要求した場合に許可 |
+| エスケープハッチ | ユーザーが「override」「bypass strict」等を明示的に要求した場合、その特定のアクションに限り許可。完了後strictモード再適用 |
 
 **`strict.merge`** — Gitコマンド制御：有効にすると`git pull`/`push`/`merge`の直接使用が制限されます。エージェントが`/reap.pull`、`/reap.push`、`/reap.merge`の使用を案内します。
 

package/README.ko.md

@@ -329,7 +329,7 @@ Slash command가 `.claude/commands/`에 설치되어 전체 워크플로우를
 | `/reap.merge.sync` | Genome-소스 간 일관성 검증 (AI 비교, 사용자 확인) |
 | `/reap.merge.validation` | 기계적 테스트 실행 (bun test, tsc, build) |
 | **`/reap.merge.evolve`** | **전체 머지 라이프사이클 자동 실행** |
-| `/reap.refreshKnowledge` | 서브에이전트용 REAP 컨텍스트 로드 (Genome, Environment, 상태) |
+| `/reap.refreshKnowledge` | REAP 컨텍스트 재로드 (Genome, Environment, 상태). context compaction 후 또는 서브에이전트에서 사용 |
 
 ### SessionStart Hook [↗](https://reap.cc/docs/hooks)
 
@@ -363,7 +363,7 @@ strict:
 |------|------|
 | 활성 Generation 없음 / 구현 단계 외 | 코드 수정 완전 차단 |
 | Implementation 단계 | `02-planning.md` 범위 내에서만 수정 허용 |
-| Escape hatch | 사용자가 "override", "bypass strict" 등 명시적 요청 시 허용 |
+| Escape hatch | 사용자가 "override", "bypass strict" 등 명시적 요청 시 해당 작업에 한해 허용, 완료 후 strict 모드 재적용 |
 
 **`strict.merge`** — Git 명령 제어: 활성화 시 `git pull`/`push`/`merge` 직접 사용이 제한됩니다. 에이전트가 `/reap.pull`, `/reap.push`, `/reap.merge` 사용을 안내합니다.
 

package/README.md

@@ -328,7 +328,7 @@ Slash commands are installed in `.claude/commands/` and drive the entire workflo
 | `/reap.merge.sync` | Verify genome–source consistency (AI compares, user confirms) |
 | `/reap.merge.validation` | Run mechanical testing (bun test, tsc, build) |
 | **`/reap.merge.evolve`** | **Run the full merge lifecycle automatically** |
-| `/reap.refreshKnowledge` | Load REAP context for subagents (Genome, Environment, state) |
+| `/reap.refreshKnowledge` | Reload REAP context (Genome, Environment, state). Useful after context compaction or in subagents |
 
 ### SessionStart Hook [↗](https://reap.cc/docs/hooks)
 
@@ -364,7 +364,7 @@ strict:
 |---------|----------|
 | No active generation / non-implementation stage | Code modifications are fully blocked |
 | Implementation stage | Only modifications within the scope of `02-planning.md` are allowed |
-| Escape hatch | User explicitly requests "override" or "bypass strict" to allow modifications |
+| Escape hatch | User explicitly requests "override" or "bypass strict" — bypass applies to that specific action only, then strict mode re-engages |
 
 **`strict.merge`** — Git command control: when enabled, direct `git pull`/`push`/`merge` are restricted. The agent guides users to use `/reap.pull`, `/reap.push`, `/reap.merge` instead.
 

package/README.zh-CN.md

@@ -329,7 +329,7 @@ autoIssueReport: true    # 默认值: true（检测到gh CLI时）
 | `/reap.merge.sync` | 验证Genome与源代码的一致性（AI比较，用户确认） |
 | `/reap.merge.validation` | 运行机械化测试（bun test、tsc、build） |
 | **`/reap.merge.evolve`** | **自动运行完整的合并生命周期** |
-| `/reap.refreshKnowledge` | 为子代理加载REAP上下文（Genome、Environment、状态） |
+| `/reap.refreshKnowledge` | 重新加载REAP上下文（Genome、Environment、状态）。context compaction后或在子代理中使用 |
 
 ### SessionStart Hook [↗](https://reap.cc/docs/hooks)
 
@@ -363,7 +363,7 @@ strict:
 |------|------|
 | 无活跃Generation / 非实现阶段 | 代码修改完全阻止 |
 | Implementation阶段 | 仅允许`02-planning.md`范围内的修改 |
-| 逃生舱 | 用户明确请求"override"或"bypass strict"时允许 |
+| 逃生舱 | 用户明确请求"override"或"bypass strict"时，仅对该特定操作允许，完成后strict模式重新生效 |
 
 **`strict.merge`** — Git命令控制：启用后，直接使用`git pull`/`push`/`merge`将被限制。代理会引导用户使用`/reap.pull`、`/reap.push`、`/reap.merge`。
 

package/dist/cli.js

@@ -12359,7 +12359,7 @@ async function execute15(paths) {
   const gm = new GenerationManager(paths);
   const state = await gm.current();
   const configContent = await readTextFile(paths.config);
-  const installedVersion = "0.15.1";
+  const installedVersion = "0.15.2";
   const autoUpdate = configContent?.match(/autoUpdate:\s*(true|false)/)?.[1] === "true";
   const versionDisplay = formatVersionLine(installedVersion, !autoUpdate);
   const rawLang = detectLanguage(configContent);
@@ -14403,7 +14403,7 @@ async function runCommand(command, phase, argv = []) {
     try {
       const config = await ConfigManager.read(paths);
       if (config.autoIssueReport) {
-        const version = "0.15.1";
+        const version = "0.15.2";
         const errMsg = err instanceof Error ? err.message : String(err);
         const title = `[auto] reap run ${command}: ${errMsg.slice(0, 80)}`;
         const body = [
@@ -15034,7 +15034,7 @@ async function initProject(projectRoot, projectName, entryMode, preset, onProgre
   }
   const detectedLanguage = await AgentRegistry.readLanguage();
   const config = {
-    version: "0.15.1",
+    version: "0.15.2",
     project: projectName,
     entryMode,
     strict: false,
@@ -15641,7 +15641,7 @@ async function updateProject(projectRoot, dryRun = false) {
       }
     } catch {}
     await migrateLegacyFiles(paths, dryRun, result);
-    const currentVersion = "0.15.1";
+    const currentVersion = "0.15.2";
     const migrationResult = await MigrationRunner.run(paths, currentVersion, dryRun);
     for (const m of migrationResult.migrated) {
       result.updated.push(`[migration] ${m}`);
@@ -16439,7 +16439,7 @@ init_fs();
 init_version();
 init_config();
 import { join as join32 } from "path";
-program.name("reap").description("REAP — Recursive Evolutionary Autonomous Pipeline").version("0.15.1");
+program.name("reap").description("REAP — Recursive Evolutionary Autonomous Pipeline").version("0.15.2");
 program.command("init").description("Initialize a new REAP project (Genesis)").argument("[project-name]", "Project name (defaults to current directory name)").option("-m, --mode <mode>", "Entry mode: greenfield, migration, adoption", "greenfield").option("-p, --preset <preset>", "Bootstrap with a genome preset (e.g., bun-hono-react)").action(async (projectName, options) => {
   try {
     const cwd = process.cwd();
@@ -16496,7 +16496,7 @@ program.command("status").description("Show current project and Generation statu
     const paths = new ReapPaths(cwd);
     const config = await ConfigManager.read(paths);
     const skipCheck = config.autoUpdate === false;
-    const installedVersion = "0.15.1";
+    const installedVersion = "0.15.2";
     const versionLine = formatVersionLine(installedVersion, skipCheck);
     console.log(`${versionLine} | Project: ${status.project} (${status.entryMode})`);
     console.log(`Completed Generations: ${status.totalGenerations}`);

package/dist/templates/commands/reap.refreshKnowledge.md

@@ -3,4 +3,4 @@ description: "REAP Refresh Knowledge — Load REAP context (Genome, Environment,
 ---
 
 Run `reap run refreshKnowledge` and incorporate the returned REAP context into your working knowledge.
-This is useful when you don't have REAP context loaded (e.g., in a subagent or after context compaction).
+This is useful when REAP context is lost or not loaded (e.g., after context compaction, in a subagent, or when starting without a session-start hook).

package/dist/templates/help/en.txt

@@ -22,7 +22,7 @@ Slash Commands (use in Claude Code):
   /reap.status         Show current state
   /reap.sync           Synchronize Genome with source code
   /reap.help           Contextual help (AI-powered)
-  /reap.refreshKnowledge  Load REAP context for subagents
+  /reap.refreshKnowledge  Reload REAP context (Genome, Environment, state)
 
 Quick Start:
   1. reap init my-project

package/dist/templates/help/ko.txt

@@ -22,7 +22,7 @@ CLI 명령어:
   /reap.status         현재 상태 확인
   /reap.sync           Genome을 소스 코드와 동기화
   /reap.help           상황별 도움말 (AI 기반)
-  /reap.refreshKnowledge  서브에이전트용 REAP 컨텍스트 로드
+  /reap.refreshKnowledge  REAP 컨텍스트 재로드 (Genome, Environment, 상태)
 
 빠른 시작:
   1. reap init my-project

package/dist/templates/hooks/genome-loader.cjs

@@ -222,16 +222,16 @@ function buildStrictSection(strictEdit, strictMerge, genStage) {
 
   if (strictEdit) {
     if (genStage === 'implementation') {
-      sections += "\n\n## Strict Mode — Edit (ACTIVE — SCOPED MODIFICATION ALLOWED)\n<HARD-GATE>\nStrict mode is enabled. Code modification is ALLOWED only within the scope of the current Generation's plan.\n- You MUST read `.reap/life/02-planning.md` before writing any code.\n- You may ONLY modify files and modules listed in the plan's task list.\n- Changes outside the plan's scope are BLOCKED. If you discover out-of-scope work is needed, add it to the backlog instead of implementing it.\n- If the user explicitly requests to bypass strict mode (e.g., \"override\", \"bypass strict\"), you may proceed — but inform them that strict mode is being bypassed.\n</HARD-GATE>";
+      sections += "\n\n## Strict Mode — Edit (ACTIVE — SCOPED MODIFICATION ALLOWED)\n<HARD-GATE>\nStrict mode is enabled. Code modification is ALLOWED only within the scope of the current Generation's plan.\n- You MUST read `.reap/life/02-planning.md` before writing any code.\n- You may ONLY modify files and modules listed in the plan's task list.\n- Changes outside the plan's scope are BLOCKED. If you discover out-of-scope work is needed, add it to the backlog instead of implementing it.\n- If the user explicitly requests to bypass strict mode (e.g., \"override\", \"bypass strict\"), you may proceed for that specific action only — but inform them that strict mode is being bypassed. The bypass does NOT persist; strict mode re-engages immediately after the requested action is complete.\n</HARD-GATE>";
     } else if (genStage === 'none') {
-      sections += "\n\n## Strict Mode — Edit (ACTIVE — CODE MODIFICATION BLOCKED)\n<HARD-GATE>\nStrict mode is enabled and there is NO active Generation.\nYou MUST NOT write, edit, or create any source code files.\nAllowed actions: reading files, analyzing code, answering questions, running commands.\nTo start coding, the user must first run `/reap.start` and advance to the implementation stage.\nIf the user explicitly requests to bypass strict mode (e.g., \"override\", \"bypass strict\", \"just do it\"), you may proceed — but inform them that strict mode is being bypassed.\n</HARD-GATE>";
+      sections += "\n\n## Strict Mode — Edit (ACTIVE — CODE MODIFICATION BLOCKED)\n<HARD-GATE>\nStrict mode is enabled and there is NO active Generation.\nYou MUST NOT write, edit, or create any source code files.\nAllowed actions: reading files, analyzing code, answering questions, running commands.\nTo start coding, the user must first run `/reap.start` and advance to the implementation stage.\nIf the user explicitly requests to bypass strict mode (e.g., \"override\", \"bypass strict\", \"just do it\"), you may proceed for that specific action only — but inform them that strict mode is being bypassed. The bypass does NOT persist; strict mode re-engages immediately after the requested action is complete.\n</HARD-GATE>";
     } else {
-      sections += `\n\n## Strict Mode — Edit (ACTIVE — CODE MODIFICATION BLOCKED)\n<HARD-GATE>\nStrict mode is enabled. Current stage is '${genStage}', which is NOT the implementation stage.\nYou MUST NOT write, edit, or create any source code files.\nAllowed actions: reading files, analyzing code, answering questions, running commands, writing REAP artifacts.\nAdvance to the implementation stage via the REAP lifecycle to unlock code modification.\nIf the user explicitly requests to bypass strict mode (e.g., \"override\", \"bypass strict\", \"just do it\"), you may proceed — but inform them that strict mode is being bypassed.\n</HARD-GATE>`;
+      sections += `\n\n## Strict Mode — Edit (ACTIVE — CODE MODIFICATION BLOCKED)\n<HARD-GATE>\nStrict mode is enabled. Current stage is '${genStage}', which is NOT the implementation stage.\nYou MUST NOT write, edit, or create any source code files.\nAllowed actions: reading files, analyzing code, answering questions, running commands, writing REAP artifacts.\nAdvance to the implementation stage via the REAP lifecycle to unlock code modification.\nIf the user explicitly requests to bypass strict mode (e.g., \"override\", \"bypass strict\", \"just do it\"), you may proceed for that specific action only — but inform them that strict mode is being bypassed. The bypass does NOT persist; strict mode re-engages immediately after the requested action is complete.\n</HARD-GATE>`;
     }
   }
 
   if (strictMerge) {
-    sections += "\n\n## Strict Mode — Merge (ACTIVE)\nDirect git pull, git push, and git merge commands are restricted.\nUse REAP slash commands instead: `/reap.pull`, `/reap.push`, `/reap.merge.start`.\nThis ensures genome-first conflict resolution and proper lineage tracking.\nIf the user explicitly requests to bypass (e.g., \"override\", \"bypass strict\"), you may proceed — but inform them that strict merge mode is being bypassed.";
+    sections += "\n\n## Strict Mode — Merge (ACTIVE)\nDirect git pull, git push, and git merge commands are restricted.\nUse REAP slash commands instead: `/reap.pull`, `/reap.push`, `/reap.merge.start`.\nThis ensures genome-first conflict resolution and proper lineage tracking.\nIf the user explicitly requests to bypass (e.g., \"override\", \"bypass strict\"), you may proceed for that specific action only — but inform them that strict merge mode is being bypassed. The bypass does NOT persist; strict mode re-engages immediately after the requested action is complete.";
   }
 
   return sections;

package/dist/templates/hooks/reap-guide.md

@@ -200,7 +200,7 @@ When `strict: true` is set in `.reap/config.yml`, the AI agent enforces code mod
 | Active Generation, not implementation stage | **BLOCKED** | Read, analyze, answer questions, write REAP artifacts |
 | Active Generation, implementation stage | **SCOPED** — only files/modules listed in 02-planning.md | Full development within plan scope |
 
-- **Escape hatch**: If the user explicitly requests to bypass strict mode (e.g., "override", "bypass strict", "just do it"), the agent may proceed but must inform the user that strict mode is being bypassed.
+- **Escape hatch**: If the user explicitly requests to bypass strict mode (e.g., "override", "bypass strict", "just do it"), the agent may proceed **for that specific action only** and must inform the user that strict mode is being bypassed. The bypass does NOT persist — strict mode re-engages immediately after the requested action is complete.
 - **Default**: `strict: false` (no restrictions beyond normal REAP workflow guidance).
 
 ## Critical Rules

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@c-d-cc/reap",
-  "version": "0.15.1",
+  "version": "0.15.2",
   "description": "Recursive Evolutionary Autonomous Pipeline — AI and humans evolve software across generations",
   "type": "module",
   "license": "MIT",