@c-d-cc/reap 0.2.2 → 0.3.0

package/README.ja.md

@@ -38,6 +38,7 @@ REAPは**世代ベースの進化モデル**でこれらの問題を解決しま
 - AIエージェントが毎セッション開始時に現在のコンテキストを自動認識（SessionStart Hook）
 - 実装中に発見した設計問題はbacklogに記録、Completionで反映
 - レトロスペクティブ（Completion）で導き出した教訓がGenomeに蓄積
+- 世代を重ねて繰り返される手作業を自動検出し、ユーザー確認の上でHookとして生成
 
 ## インストール
 
@@ -97,7 +98,7 @@ Objective → Planning → Implementation ⟷ Validation → Completion
 | **Planning** | タスク分解、実装アプローチ、依存関係 | `02-planning.md` |
 | **Implementation** | AI+Human協力でコード実装 | `03-implementation.md` |
 | **Validation** | テスト実行、完了条件の確認 | `04-validation.md` |
-| **Completion** | レトロスペクティブ + Genome変更反映 + アーカイブ | `05-completion.md` |
+| **Completion** | レトロスペクティブ + Genome変更反映 + Hook提案 + アーカイブ | `05-completion.md` |
 
 ## コアコンセプト
 
@@ -110,7 +111,8 @@ Objective → Planning → Implementation ⟷ Validation → Completion
 ├── principles.md      # アーキテクチャ原則/決定
 ├── domain/            # ビジネスルール（モジュール別）
 ├── conventions.md     # 開発ルール/コンベンション
-└── constraints.md     # 技術制約/選択
+├── constraints.md     # 技術制約/選択
+└── source-map.md      # C4 Container/Componentダイアグラム（Mermaid）
 ```
 
 **Genome不変原則**: 現在の世代ではGenomeを直接変更しません。問題を発見した場合はbacklogに記録し、Completionステージでのみ反映します。
@@ -193,6 +195,8 @@ REAPはスラッシュコマンドとセッションフックを通じてAIエ
 - REAPワークフロー全体のガイド（Genome、ライフサイクル、4軸構造など）
 - 現在のGeneration状態（どのステージにいるか、次に何をすべきか）
 - REAPライフサイクルに従うルール
+- Genome鮮度検出 — 最後のGenome更新以降にコード関連のコミット（`src/`、`tests/`、`package.json`、`tsconfig.json`、`scripts/`）があったかを確認（ドキュメントのみの変更は除外）
+- Source-mapドリフト検出 — `source-map.md`に記録されたコンポーネントとプロジェクト内の実際のファイルを比較
 
 これにより、新しいセッションを開いてもエージェントがプロジェクトコンテキストを即座に把握します。
 
@@ -220,22 +224,28 @@ Strictモードはデフォルトで無効です（`strict: false`）。
 
 ### REAP Hooks
 
-`.reap/config.yml`にhookを定義して、ライフサイクルイベントでコマンドやAIプロンプトを実行できます：
+Hookはファイルベースで`.reap/hooks/`に保存されます。各Hookは`{event}.{name}.{md|sh}`形式のファイルです：
 
-```yaml
-hooks:
-  onGenerationStart:
-    - command: "echo 'Generation started'"
-  onStageTransition:
-    - command: "echo 'Stage changed'"
-  onGenerationComplete:
-    - command: "reap update"
-    - prompt: "今回のGenerationで変更された機能があればREADMEに反映せよ。"
-  onRegression:
-    - command: "echo 'Regressed'"
+- `.md`ファイルはAIプロンプトを含みます（AIエージェントが実行）
+- `.sh`ファイルはシェルスクリプトを含みます（直接実行）
+
+```
+.reap/hooks/
+├── onGenerationStart.context-load.md
+├── onGenerationComplete.version-bump.md
+├── onGenerationComplete.readme-update.md
+├── onStageTransition.notify.sh
+└── onRegression.alert.sh
 ```
 
-各hookは`command`（シェルコマンド）または`prompt`（AIエージェント指示）のいずれかを使用します。
+各Hookファイルは以下のフィールドを持つfrontmatterをサポートします：
+
+```yaml
+---
+condition: has-code-changes   # always | has-code-changes | version-bumped
+order: 10                     # 実行順序（小さいほど先に実行）
+---
+```
 
 | イベント | トリガー |
 |----------|----------|
@@ -244,7 +254,7 @@ hooks:
 | `onGenerationComplete` | `/reap.next`で完了したGenerationをアーカイブ後 |
 | `onRegression` | `/reap.back`で前のステージに回帰後 |
 
-HookはAIエージェントがプロジェクトルートディレクトリで実行します。
+HookはAIエージェントがプロジェクトルートディレクトリで実行します。`onGenerationComplete` Hookには自動バージョンバンプ判定が含まれています — patchレベルは自動適用され、minor/majorバンプはユーザー確認が必要です。
 
 ## `reap init`後のプロジェクト構造
 
@@ -257,7 +267,9 @@ my-project/
     │   ├── principles.md
     │   ├── domain/
     │   ├── conventions.md
-    │   └── constraints.md
+    │   ├── constraints.md
+    │   └── source-map.md
+    ├── hooks/                    # Lifecycle hooks (.md/.sh)
     ├── environment/              # 外部環境
     ├── life/                     # 現在の世代
     │   ├── current.yml
@@ -275,10 +287,10 @@ my-project/
 
 | レベル | 入力 | 出力 | 最大行数 | トリガー |
 |--------|------|------|----------|----------|
-| **Level 1** | 世代フォルダ（5つの成果物） | `gen-XXX.md` | 40行 | lineage > 10,000行 + 5世代以上 |
+| **Level 1** | 世代フォルダ（5つの成果物） | `gen-XXX.md` | 40行 | lineage > 5,000行 + 5世代以上 |
 | **Level 2** | Level 1ファイル5つ | `epoch-XXX.md` | 60行 | Level 1が5つ以上 |
 
-圧縮は世代完了時に自動実行されます。圧縮されたファイルは目標（Objective）と結果（Completion）を中心に保存し、中間過程は特記事項のみを残します。
+圧縮は世代完了時に自動実行されます。直近3世代は常に圧縮から保護されます。圧縮されたファイルは目標（Objective）と結果（Completion）を中心に保存し、中間過程は特記事項のみを残します。
 
 ## 進化フロー（Evolution Flow）
 

package/README.ko.md

@@ -38,6 +38,7 @@ REAP은 **세대 기반 진화 모델**로 이 문제들을 해결합니다:
 - AI 에이전트가 매 세션 시작 시 현재 맥락을 자동으로 인식 (SessionStart Hook)
 - 구현 중 발견한 설계 문제는 backlog에 기록, Completion에서 반영
 - 회고(Completion)에서 도출한 교훈이 Genome에 축적
+- 세대를 거듭하며 반복되는 수작업을 자동 감지하고, 사용자 확인 후 Hook으로 생성
 
 ## 설치
 
@@ -97,7 +98,7 @@ Objective → Planning → Implementation ⟷ Validation → Completion
 | **Planning** | 태스크 분해, 구현 접근법, 의존관계 | `02-planning.md` |
 | **Implementation** | AI+Human 협업으로 코드 구현 | `03-implementation.md` |
 | **Validation** | 테스트 실행, 완료 조건 점검 | `04-validation.md` |
-| **Completion** | 회고 + Genome 변경 반영 + 아카이빙 | `05-completion.md` |
+| **Completion** | 회고 + Genome 변경 반영 + Hook 제안 + 아카이빙 | `05-completion.md` |
 
 ## 핵심 개념
 
@@ -110,7 +111,8 @@ Application의 유전 정보 — 아키텍처 원칙, 비즈니스 규칙, 개
 ├── principles.md      # 아키텍처 원칙/결정
 ├── domain/            # 비즈니스 규칙 (모듈별)
 ├── conventions.md     # 개발 규칙/컨벤션
-└── constraints.md     # 기술 제약/선택
+├── constraints.md     # 기술 제약/선택
+└── source-map.md      # C4 Container/Component 다이어그램 (Mermaid)
 ```
 
 **Genome 불변 원칙**: 현재 세대에서는 Genome을 직접 수정하지 않습니다. 문제를 발견하면 backlog에 기록하고, Completion 단계에서만 반영합니다.
@@ -193,6 +195,8 @@ Slash command가 `.claude/commands/`에 설치되어 전체 워크플로우를
 - REAP 워크플로우 전체 가이드 (Genome, Life Cycle, 4축 구조 등)
 - 현재 Generation 상태 (어떤 stage인지, 다음에 뭘 해야 하는지)
 - REAP lifecycle을 따르라는 규칙
+- Genome 최신성 감지 — 마지막 Genome 업데이트 이후 코드 관련 커밋(`src/`, `tests/`, `package.json`, `tsconfig.json`, `scripts/`)이 있었는지 확인 (문서 전용 변경은 제외)
+- Source-map 드리프트 감지 — `source-map.md`에 기록된 컴포넌트와 프로젝트의 실제 파일을 비교
 
 이를 통해 새 세션을 열어도 에이전트가 프로젝트 맥락을 즉시 파악합니다.
 
@@ -220,22 +224,28 @@ Strict 모드는 기본적으로 비활성화되어 있습니다 (`strict: false
 
 ### REAP Hooks
 
-`.reap/config.yml`에 hook을 정의하여 lifecycle 이벤트에 명령 또는 AI 프롬프트를 실행할 수 있습니다:
+Hook은 파일 기반이며 `.reap/hooks/`에 저장됩니다. 각 Hook은 `{event}.{name}.{md|sh}` 형식의 파일입니다:
 
-```yaml
-hooks:
-  onGenerationStart:
-    - command: "echo 'Generation started'"
-  onStageTransition:
-    - command: "echo 'Stage changed'"
-  onGenerationComplete:
-    - command: "reap update"
-    - prompt: "이번 Generation 변경사항을 README에 반영하라."
-  onRegression:
-    - command: "echo 'Regressed'"
+- `.md` 파일은 AI 프롬프트를 담고 있습니다 (AI 에이전트가 실행)
+- `.sh` 파일은 셸 스크립트를 담고 있습니다 (직접 실행)
+
+```
+.reap/hooks/
+├── onGenerationStart.context-load.md
+├── onGenerationComplete.version-bump.md
+├── onGenerationComplete.readme-update.md
+├── onStageTransition.notify.sh
+└── onRegression.alert.sh
 ```
 
-각 hook은 `command` (shell 명령) 또는 `prompt` (AI 에이전트 지시) 중 하나를 사용합니다.
+각 Hook 파일은 다음 필드를 가진 frontmatter를 지원합니다:
+
+```yaml
+---
+condition: has-code-changes   # always | has-code-changes | version-bumped
+order: 10                     # 실행 순서 (낮을수록 먼저 실행)
+---
+```
 
 | 이벤트 | 트리거 |
 |--------|--------|
@@ -244,7 +254,7 @@ hooks:
 | `onGenerationComplete` | `/reap.next`로 완료된 Generation 아카이빙 후 |
 | `onRegression` | `/reap.back`으로 이전 stage 복귀 후 |
 
-Hook은 AI 에이전트가 프로젝트 루트 디렉토리에서 실행합니다.
+Hook은 AI 에이전트가 프로젝트 루트 디렉토리에서 실행합니다. `onGenerationComplete` Hook에는 자동 버전 범프 판단이 포함되어 있습니다 — patch 수준은 자동으로 적용되고, minor/major 범프는 사용자 확인을 거칩니다.
 
 ## `reap init` 후 프로젝트 구조
 
@@ -257,7 +267,9 @@ my-project/
     │   ├── principles.md
     │   ├── domain/
     │   ├── conventions.md
-    │   └── constraints.md
+    │   ├── constraints.md
+    │   └── source-map.md
+    ├── hooks/                    # Lifecycle hooks (.md/.sh)
     ├── environment/              # 외부 환경
     ├── life/                     # 현재 세대
     │   ├── current.yml
@@ -275,10 +287,10 @@ my-project/
 
 | 레벨 | 입력 | 출력 | 최대 줄 수 | 트리거 |
 |------|------|------|-----------|--------|
-| **Level 1** | 세대 폴더 (5개 산출물) | `gen-XXX.md` | 40줄 | lineage > 10,000줄 + 5세대 이상 |
+| **Level 1** | 세대 폴더 (5개 산출물) | `gen-XXX.md` | 40줄 | lineage > 5,000줄 + 5세대 이상 |
 | **Level 2** | Level 1 파일 5개 | `epoch-XXX.md` | 60줄 | Level 1이 5개 이상 |
 
-압축은 세대 완료 시 자동 실행됩니다. 압축된 파일은 목표(Objective)와 결과(Completion)를 중심으로 보존하고, 중간 과정은 특이사항만 남깁니다.
+압축은 세대 완료 시 자동 실행됩니다. 가장 최근 3개 세대는 항상 압축에서 보호됩니다. 압축된 파일은 목표(Objective)와 결과(Completion)를 중심으로 보존하고, 중간 과정은 특이사항만 남깁니다.
 
 ## 진화 흐름 (Evolution Flow)
 

package/README.md

@@ -38,6 +38,7 @@ REAP solves these with a **generation-based evolution model**:
 - The AI agent automatically picks up current context at every session start (SessionStart Hook)
 - Design issues discovered during implementation are logged in the backlog and addressed at Completion
 - Lessons drawn from retrospectives (Completion) accumulate in the Genome
+- Repeated manual tasks are automatically detected across generations, with user-confirmed hook creation
 
 ## Installation
 
@@ -96,7 +97,7 @@ Objective → Planning → Implementation ⟷ Validation → Completion
 | **Planning** | Break down tasks, choose approach, map dependencies | `02-planning.md` |
 | **Implementation** | Build with AI + human collaboration | `03-implementation.md` |
 | **Validation** | Run tests, verify completion criteria | `04-validation.md` |
-| **Completion** | Retrospective + apply Genome changes + archive | `05-completion.md` |
+| **Completion** | Retrospective + apply Genome changes + hook suggestion + archive | `05-completion.md` |
 
 ## Core Concepts
 
@@ -109,7 +110,8 @@ The application's genetic information — a collection of architecture principle
 ├── principles.md      # Architecture principles/decisions
 ├── domain/            # Business rules (per module)
 ├── conventions.md     # Development rules/conventions
-└── constraints.md     # Technical constraints/choices
+├── constraints.md     # Technical constraints/choices
+└── source-map.md      # C4 Container/Component diagram (Mermaid)
 ```
 
 **Genome Immutability Principle**: The Genome is never modified directly during the current generation. When an issue is found, it is recorded in the backlog and only applied at the Completion stage.
@@ -192,6 +194,8 @@ Runs automatically at the start of every session, injecting the following into t
 - The full REAP workflow guide (Genome, Life Cycle, Four-Axis Structure, etc.)
 - Current generation state (which stage you're in, what to do next)
 - Rules to follow the REAP lifecycle
+- Genome staleness detection — checks if code-related commits (`src/`, `tests/`, `package.json`, `tsconfig.json`, `scripts/`) have occurred since the last Genome update (docs-only changes are excluded)
+- Source-map drift detection — compares documented components in `source-map.md` against actual files in the project
 
 This ensures the agent immediately understands the project context even in a brand-new session.
 
@@ -219,22 +223,28 @@ Strict mode is disabled by default (`strict: false`).
 
 ### REAP Hooks
 
-Projects can define hooks in `.reap/config.yml` to run commands or AI prompts at lifecycle events:
+Hooks are file-based and stored in `.reap/hooks/`. Each hook is a file named `{event}.{name}.{md|sh}`:
 
-```yaml
-hooks:
-  onGenerationStart:
-    - command: "echo 'Generation started'"
-  onStageTransition:
-    - command: "echo 'Stage changed'"
-  onGenerationComplete:
-    - command: "reap update"
-    - prompt: "Update README if this generation changed any features."
-  onRegression:
-    - command: "echo 'Regressed'"
+- `.md` files contain AI prompts (executed by the AI agent)
+- `.sh` files contain shell scripts (executed directly)
+
+```
+.reap/hooks/
+├── onGenerationStart.context-load.md
+├── onGenerationComplete.version-bump.md
+├── onGenerationComplete.readme-update.md
+├── onStageTransition.notify.sh
+└── onRegression.alert.sh
 ```
 
-Each hook supports `command` (shell) or `prompt` (AI agent instruction).
+Each hook file supports frontmatter with the following fields:
+
+```yaml
+---
+condition: has-code-changes   # always | has-code-changes | version-bumped
+order: 10                     # execution order (lower runs first)
+---
+```
 
 | Event | Trigger |
 |-------|---------|
@@ -243,7 +253,7 @@ Each hook supports `command` (shell) or `prompt` (AI agent instruction).
 | `onGenerationComplete` | After `/reap.next` archives a completed generation |
 | `onRegression` | After `/reap.back` returns to a previous stage |
 
-Hooks are executed by the AI agent in the project root directory.
+Hooks are executed by the AI agent in the project root directory. The `onGenerationComplete` hooks include automatic version bump judgment — patch-level bumps are applied automatically, while minor/major bumps require user confirmation.
 
 ## Project Structure After `reap init`
 
@@ -256,7 +266,9 @@ my-project/
     │   ├── principles.md
     │   ├── domain/
     │   ├── conventions.md
-    │   └── constraints.md
+    │   ├── constraints.md
+    │   └── source-map.md
+    ├── hooks/                    # Lifecycle hooks (.md/.sh)
     ├── environment/              # External context
     ├── life/                     # Current generation
     │   ├── current.yml
@@ -274,10 +286,10 @@ As generations accumulate, the lineage directory grows. REAP manages this with a
 
 | Level | Input | Output | Max lines | Trigger |
 |-------|-------|--------|-----------|---------|
-| **Level 1** | Generation folder (5 artifacts) | `gen-XXX.md` | 40 lines | lineage > 10,000 lines + 5+ generations |
+| **Level 1** | Generation folder (5 artifacts) | `gen-XXX.md` | 40 lines | lineage > 5,000 lines + 5+ generations |
 | **Level 2** | 5 Level 1 files | `epoch-XXX.md` | 60 lines | 5+ Level 1 files |
 
-Compression runs automatically when a generation completes. Compressed files preserve objectives and completion results while retaining only notable findings from intermediate stages.
+Compression runs automatically when a generation completes. The most recent 3 generations are always protected from compression. Compressed files preserve objectives and completion results while retaining only notable findings from intermediate stages.
 
 ## Evolution Flow
 

package/README.zh-CN.md

@@ -38,6 +38,7 @@ REAP通过**基于世代的进化模型**解决这些问题：
 - AI代理在每次会话开始时自动获取当前上下文（SessionStart Hook）
 - 实现过程中发现的设计问题记录在backlog中，在Completion时反映
 - 回顾（Completion）中提取的教训积累在Genome中
+- 跨世代自动检测重复的手动操作，经用户确认后生成Hook
 
 ## 安装
 
@@ -97,7 +98,7 @@ Objective → Planning → Implementation ⟷ Validation → Completion
 | **Planning** | 任务分解、实施方案、依赖关系 | `02-planning.md` |
 | **Implementation** | AI+人类协作编写代码 | `03-implementation.md` |
 | **Validation** | 执行测试、检查完成条件 | `04-validation.md` |
-| **Completion** | 回顾 + 应用Genome变更 + 归档 | `05-completion.md` |
+| **Completion** | 回顾 + 应用Genome变更 + Hook建议 + 归档 | `05-completion.md` |
 
 ## 核心概念
 
@@ -110,7 +111,8 @@ Objective → Planning → Implementation ⟷ Validation → Completion
 ├── principles.md      # 架构原则/决策
 ├── domain/            # 业务规则（按模块）
 ├── conventions.md     # 开发规则/约定
-└── constraints.md     # 技术约束/选择
+├── constraints.md     # 技术约束/选择
+└── source-map.md      # C4 Container/Component图（Mermaid）
 ```
 
 **Genome不变原则**：当前世代不直接修改Genome。发现问题时记录在backlog中，仅在Completion阶段反映。
@@ -193,6 +195,8 @@ REAP通过斜杠命令和会话钩子与AI代理集成。当前支持的代理
 - REAP工作流完整指南（Genome、生命周期、四轴结构等）
 - 当前Generation状态（在哪个阶段、下一步做什么）
 - 遵循REAP生命周期的规则
+- Genome新鲜度检测 — 检查上次Genome更新后是否有代码相关提交（`src/`、`tests/`、`package.json`、`tsconfig.json`、`scripts/`），纯文档变更除外
+- Source-map漂移检测 — 将`source-map.md`中记录的组件与项目中的实际文件进行比对
 
 这确保即使打开新会话，代理也能立即理解项目上下文。
 
@@ -220,22 +224,28 @@ Strict模式默认禁用（`strict: false`）。
 
 ### REAP Hooks
 
-在`.reap/config.yml`中定义hook，在生命周期事件时执行命令或AI提示：
+Hook基于文件，存储在`.reap/hooks/`中。每个Hook是一个以`{event}.{name}.{md|sh}`命名的文件：
 
-```yaml
-hooks:
-  onGenerationStart:
-    - command: "echo 'Generation started'"
-  onStageTransition:
-    - command: "echo 'Stage changed'"
-  onGenerationComplete:
-    - command: "reap update"
-    - prompt: "如果本Generation有功能变更，请更新README。"
-  onRegression:
-    - command: "echo 'Regressed'"
+- `.md`文件包含AI提示词（由AI代理执行）
+- `.sh`文件包含Shell脚本（直接执行）
+
+```
+.reap/hooks/
+├── onGenerationStart.context-load.md
+├── onGenerationComplete.version-bump.md
+├── onGenerationComplete.readme-update.md
+├── onStageTransition.notify.sh
+└── onRegression.alert.sh
 ```
 
-每个hook使用`command`（shell命令）或`prompt`（AI代理指令）之一。
+每个Hook文件支持包含以下字段的frontmatter：
+
+```yaml
+---
+condition: has-code-changes   # always | has-code-changes | version-bumped
+order: 10                     # 执行顺序（数值越小越先执行）
+---
+```
 
 | 事件 | 触发时机 |
 |------|----------|
@@ -244,7 +254,7 @@ hooks:
 | `onGenerationComplete` | `/reap.next`归档已完成的Generation后 |
 | `onRegression` | `/reap.back`回到前一阶段后 |
 
-Hook由AI代理在项目根目录中执行。
+Hook由AI代理在项目根目录中执行。`onGenerationComplete` Hook包含自动版本号升级判断 — patch级别自动应用，minor/major级别需要用户确认。
 
 ## `reap init`后的项目结构
 
@@ -257,7 +267,9 @@ my-project/
     │   ├── principles.md
     │   ├── domain/
     │   ├── conventions.md
-    │   └── constraints.md
+    │   ├── constraints.md
+    │   └── source-map.md
+    ├── hooks/                    # Lifecycle hooks (.md/.sh)
     ├── environment/              # 外部环境
     ├── life/                     # 当前世代
     │   ├── current.yml
@@ -275,10 +287,10 @@ my-project/
 
 | 级别 | 输入 | 输出 | 最大行数 | 触发条件 |
 |------|------|------|----------|----------|
-| **Level 1** | 世代文件夹（5个产出物） | `gen-XXX.md` | 40行 | lineage > 10,000行 + 5个以上世代 |
+| **Level 1** | 世代文件夹（5个产出物） | `gen-XXX.md` | 40行 | lineage > 5,000行 + 5个以上世代 |
 | **Level 2** | 5个Level 1文件 | `epoch-XXX.md` | 60行 | Level 1达到5个以上 |
 
-压缩在世代完成时自动执行。压缩后的文件以目标（Objective）和结果（Completion）为中心保存，中间过程仅保留特别事项。
+压缩在世代完成时自动执行。最近3个世代始终受到保护，不会被压缩。压缩后的文件以目标（Objective）和结果（Completion）为中心保存，中间过程仅保留特别事项。
 
 ## 进化流程（Evolution Flow）
 

package/dist/cli.js

@@ -8840,7 +8840,7 @@ var {
 } = import__.default;
 
 // src/cli/commands/init.ts
-import { mkdir as mkdir3 } from "fs/promises";
+import { mkdir as mkdir3, readdir as readdir3, chmod } from "fs/promises";
 import { join as join4 } from "path";
 
 // src/core/paths.ts
@@ -8943,7 +8943,7 @@ class ReapPaths {
   get legacyTemplates() {
     return join(this.root, "templates");
   }
-  get legacyHooks() {
+  get hooks() {
     return join(this.root, "hooks");
   }
   get legacyClaudeCommands() {
@@ -9178,10 +9178,10 @@ class ClaudeCodeAdapter {
     return { action: "migrated" };
   }
   getHookEntry() {
-    const sessionStartPath = join2(ReapPaths.packageHooksDir, "session-start.sh");
+    const sessionStartPath = join2(ReapPaths.packageHooksDir, "session-start.cjs");
     return {
       matcher: "",
-      hooks: [{ type: "command", command: `bash "${sessionStartPath}"` }]
+      hooks: [{ type: "command", command: `node "${sessionStartPath}"` }]
     };
   }
   hasReapHook(sessionStartHooks) {
@@ -9450,7 +9450,7 @@ async function initProject(projectRoot, projectName, entryMode, preset, onProgre
   };
   await ConfigManager.write(paths, config);
   log("Setting up Genome templates...");
-  const genomeTemplates = ["principles.md", "conventions.md", "constraints.md"];
+  const genomeTemplates = ["principles.md", "conventions.md", "constraints.md", "source-map.md"];
   const genomeSourceDir = preset ? join4(ReapPaths.packageTemplatesDir, "presets", preset) : ReapPaths.packageGenomeDir;
   for (const file of genomeTemplates) {
     const src = join4(genomeSourceDir, file);
@@ -9468,6 +9468,19 @@ async function initProject(projectRoot, projectName, entryMode, preset, onProgre
   const domainGuideSrc = join4(ReapPaths.packageGenomeDir, "domain/README.md");
   const domainGuideDest = join4(ReapPaths.userReapTemplates, "domain-guide.md");
   await writeTextFile(domainGuideDest, await readTextFileOrThrow(domainGuideSrc));
+  log("Installing hook conditions...");
+  const conditionsSourceDir = join4(ReapPaths.packageTemplatesDir, "conditions");
+  const conditionsDestDir = join4(paths.hooks, "conditions");
+  await mkdir3(conditionsDestDir, { recursive: true });
+  const conditionFiles = await readdir3(conditionsSourceDir);
+  for (const file of conditionFiles) {
+    if (!file.endsWith(".sh"))
+      continue;
+    const src = join4(conditionsSourceDir, file);
+    const dest = join4(conditionsDestDir, file);
+    await writeTextFile(dest, await readTextFileOrThrow(src));
+    await chmod(dest, 493);
+  }
   log("Detecting AI agents...");
   const detectedAgents = await AgentRegistry.detectInstalled();
   const sourceDir = ReapPaths.packageCommandsDir;
@@ -9484,7 +9497,7 @@ async function initProject(projectRoot, projectName, entryMode, preset, onProgre
 }
 
 // src/cli/commands/update.ts
-import { readdir as readdir3, unlink as unlink3, rm, mkdir as mkdir4 } from "fs/promises";
+import { readdir as readdir4, unlink as unlink3, rm, mkdir as mkdir4 } from "fs/promises";
 import { join as join5 } from "path";
 
 // src/core/hooks.ts
@@ -9510,7 +9523,7 @@ async function updateProject(projectRoot, dryRun = false) {
   const config = await ConfigManager.read(paths);
   const adapters = await AgentRegistry.getActiveAdapters(config ?? undefined);
   const commandsDir = ReapPaths.packageCommandsDir;
-  const commandFiles = await readdir3(commandsDir);
+  const commandFiles = await readdir4(commandsDir);
   for (const adapter of adapters) {
     const agentCmdDir = adapter.getCommandsDir();
     const label = `${adapter.displayName}`;
@@ -9579,10 +9592,9 @@ async function updateProject(projectRoot, dryRun = false) {
 async function migrateLegacyFiles(paths, dryRun, result) {
   await removeDirIfExists(paths.legacyCommands, ".reap/commands/", dryRun, result);
   await removeDirIfExists(paths.legacyTemplates, ".reap/templates/", dryRun, result);
-  await removeDirIfExists(paths.legacyHooks, ".reap/hooks/", dryRun, result);
   try {
     const claudeCmdDir = paths.legacyClaudeCommands;
-    const files = await readdir3(claudeCmdDir);
+    const files = await readdir4(claudeCmdDir);
     for (const file of files) {
       if (file.startsWith("reap.") && file.endsWith(".md")) {
         if (!dryRun)
@@ -9630,7 +9642,7 @@ async function migrateLegacyFiles(paths, dryRun, result) {
 }
 async function removeDirIfExists(dirPath, label, dryRun, result) {
   try {
-    const entries = await readdir3(dirPath);
+    const entries = await readdir4(dirPath);
     if (entries.length > 0 || true) {
       if (!dryRun)
         await rm(dirPath, { recursive: true });
@@ -9641,7 +9653,7 @@ async function removeDirIfExists(dirPath, label, dryRun, result) {
 
 // src/core/generation.ts
 var import_yaml2 = __toESM(require_dist(), 1);
-import { readdir as readdir5, mkdir as mkdir5, rename } from "fs/promises";
+import { readdir as readdir6, mkdir as mkdir5, rename } from "fs/promises";
 import { join as join7 } from "path";
 
 // src/types/index.ts
@@ -9696,13 +9708,14 @@ class LifeCycle {
 }
 
 // src/core/compression.ts
-import { readdir as readdir4, rm as rm2 } from "fs/promises";
+import { readdir as readdir5, rm as rm2 } from "fs/promises";
 import { join as join6 } from "path";
-var LINEAGE_MAX_LINES = 1e4;
+var LINEAGE_MAX_LINES = 5000;
 var MIN_GENERATIONS_FOR_COMPRESSION = 5;
 var LEVEL1_MAX_LINES = 40;
 var LEVEL2_MAX_LINES = 60;
 var LEVEL2_BATCH_SIZE = 5;
+var RECENT_PROTECTED_COUNT = 3;
 async function countLines(filePath) {
   const content = await readTextFile(filePath);
   if (content === null)
@@ -9713,7 +9726,7 @@ async function countLines(filePath) {
 async function countDirLines(dirPath) {
   let total = 0;
   try {
-    const entries = await readdir4(dirPath, { withFileTypes: true });
+    const entries = await readdir5(dirPath, { withFileTypes: true });
     for (const entry of entries) {
       const fullPath = join6(dirPath, entry.name);
       if (entry.isFile() && entry.name.endsWith(".md")) {
@@ -9728,7 +9741,7 @@ async function countDirLines(dirPath) {
 async function scanLineage(paths) {
   const entries = [];
   try {
-    const items = await readdir4(paths.lineage, { withFileTypes: true });
+    const items = await readdir5(paths.lineage, { withFileTypes: true });
     for (const item of items) {
       const fullPath = join6(paths.lineage, item.name);
       if (item.isDirectory() && item.name.startsWith("gen-")) {
@@ -9911,7 +9924,8 @@ async function compressLineageIfNeeded(paths) {
   if (totalLines <= LINEAGE_MAX_LINES) {
     return result;
   }
-  const dirs = entries.filter((e) => e.type === "dir").sort((a, b) => a.genNum - b.genNum);
+  const allDirs = entries.filter((e) => e.type === "dir").sort((a, b) => a.genNum - b.genNum);
+  const dirs = allDirs.slice(0, Math.max(0, allDirs.length - RECENT_PROTECTED_COUNT));
   for (const dir of dirs) {
     const currentTotal = await countDirLines(paths.lineage);
     if (currentTotal <= LINEAGE_MAX_LINES)
@@ -9998,7 +10012,7 @@ class GenerationManager {
     const genDirName = `${state.id}-${goalSlug}`;
     const genDir = this.paths.generationDir(genDirName);
     await mkdir5(genDir, { recursive: true });
-    const lifeEntries = await readdir5(this.paths.life);
+    const lifeEntries = await readdir6(this.paths.life);
     for (const entry of lifeEntries) {
       if (/^\d{2}-[a-z]+(?:-[a-z]+)*\.md$/.test(entry)) {
         await rename(join7(this.paths.life, entry), join7(genDir, entry));
@@ -10007,13 +10021,13 @@ class GenerationManager {
     const backlogDir = join7(genDir, "backlog");
     await mkdir5(backlogDir, { recursive: true });
     try {
-      const backlogEntries = await readdir5(this.paths.backlog);
+      const backlogEntries = await readdir6(this.paths.backlog);
       for (const entry of backlogEntries) {
         await rename(join7(this.paths.backlog, entry), join7(backlogDir, entry));
       }
     } catch {}
     try {
-      const mutEntries = await readdir5(this.paths.mutations);
+      const mutEntries = await readdir6(this.paths.mutations);
       if (mutEntries.length > 0) {
         const mutDir = join7(genDir, "mutations");
         await mkdir5(mutDir, { recursive: true });
@@ -10031,7 +10045,7 @@ class GenerationManager {
   }
   async listCompleted() {
     try {
-      const entries = await readdir5(this.paths.lineage);
+      const entries = await readdir6(this.paths.lineage);
       return entries.filter((e) => e.startsWith("gen-")).sort();
     } catch {
       return [];
@@ -10133,7 +10147,7 @@ async function fixProject(projectRoot) {
 
 // src/cli/index.ts
 import { join as join8 } from "path";
-program.name("reap").description("REAP — Recursive Evolutionary Autonomous Pipeline").version("0.2.2");
+program.name("reap").description("REAP — Recursive Evolutionary Autonomous Pipeline").version("0.3.0");
 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();

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

@@ -45,10 +45,18 @@ description: "REAP Back — Return to a previous lifecycle stage"
    - **Affected**: [affected subsequent artifacts]
    ```
 
-### Hook Execution
-7. Read `.reap/config.yml` — if `hooks.onRegression` is defined, execute each hook in order:
-   - If hook has `command`: run the shell command
-   - If hook has `prompt`: follow the prompt instructions (AI agent executes the described task)
+### Hook Execution (Regression)
+7. Scan `.reap/hooks/` for files matching `onRegression.*`
+   - For each matched file (sorted by `order` from frontmatter, then alphabetically):
+     1. Read the frontmatter (`condition`, `order`)
+     2. Evaluate `condition` by running `.reap/hooks/conditions/{condition}.sh` (exit 0 = met, non-zero = skip):
+        - If `condition` is absent: treat as `always`
+        - If the condition script doesn't exist: warn and skip the hook
+        - Default conditions: `always`, `has-code-changes`, `version-bumped`
+        - Users can add custom conditions by placing scripts in `.reap/hooks/conditions/`
+     3. Execute based on file extension:
+        - `.md`: read the file content (after frontmatter) as AI prompt and follow the instructions
+        - `.sh`: run as shell script in the project root directory
 
 ## Completion
 - "Returned to [stage] stage. Proceed with `/reap.[stage]`."