@c-d-cc/reap 0.15.1 → 0.15.3

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/dist/templates/hooks/session-start.cjs

@@ -6,7 +6,7 @@ const gl = require('./genome-loader.cjs');
 
 const startTime = Date.now();
 let step = 0;
-const totalSteps = 7;
+const totalSteps = 8;
 
 function log(msg) {
   step++;
@@ -29,6 +29,9 @@ if (!gl.dirExists(reapDir)) {
 }
 
 // Step 0: Install project-level skill files (.claude/skills/{name}/SKILL.md)
+// NOTE: This section is Claude Code-specific. Claude Code uses .claude/skills/ for
+// slash command discovery. Other agents (Codex CLI, OpenCode) use different mechanisms
+// (AGENTS.md, plugins) and this section is safely skipped when the directory doesn't exist.
 const fs = require('fs');
 const os = require('os');
 const userReapCommands = path.join(os.homedir(), '.reap', 'commands');
@@ -198,6 +201,25 @@ if (currentContent && currentContent.trim()) {
   initLines.push('⚪ No active Generation');
 }
 
+// Integrity check via reap fix --check subprocess
+log('Checking integrity...');
+try {
+  require('child_process').execSync('reap fix --check', { encoding: 'utf-8', timeout: 5000, stdio: 'pipe' });
+  initLines.push('🟢 Integrity — OK');
+} catch (integrityErr) {
+  const output = (integrityErr.stdout || '').trim();
+  const errorCount = (output.match(/✗/g) || []).length;
+  const warnCount = (output.match(/⚠/g) || []).length;
+  if (errorCount > 0 || warnCount > 0) {
+    const parts = [];
+    if (errorCount > 0) parts.push(`${errorCount} error${errorCount > 1 ? 's' : ''}`);
+    if (warnCount > 0) parts.push(`${warnCount} warning${warnCount > 1 ? 's' : ''}`);
+    initLines.push(`🔴 Integrity — ${parts.join(', ')}`);
+  } else {
+    initLines.push('🟡 Integrity — check failed');
+  }
+}
+
 const initSummary = initLines.join('\n');
 
 // Load session-init format template and render

package/package.json

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

package/scripts/postinstall.cjs

@@ -40,6 +40,7 @@ try {
   const agentDirs = [
     join(homedir(), ".claude", "commands"),
     join(homedir(), ".config", "opencode", "commands"),
+    join(homedir(), ".codex", "commands"),
   ];
   for (const agentDir of agentDirs) {
     if (!existsSync(agentDir)) continue;