@c-d-cc/reap 0.9.1 → 0.10.1

package/README.ja.md

@@ -101,7 +101,7 @@ claude
 > ...
 ```
 
-## ライフサイクル
+## ライフサイクル [↗](https://reap.cc/docs/lifecycle)
 
 各Generation（世代）は5段階のライフサイクルを経ます：
 
@@ -118,9 +118,9 @@ Objective → Planning → Implementation ⟷ Validation → Completion
 | **Validation** | テスト実行、完了条件の確認 | `04-validation.md` |
 | **Completion** | レトロスペクティブ + Genome変更反映 + Hook提案 + アーカイブ | `05-completion.md` |
 
-## コアコンセプト
+## コアコンセプト [↗](https://reap.cc/docs/core-concepts)
 
-### Genome
+### Genome [↗](https://reap.cc/docs/genome)
 
 アプリケーションの遺伝情報 — アーキテクチャ原則、ビジネスルール、開発コンベンション、技術制約の集合。
 
@@ -137,7 +137,7 @@ Objective → Planning → Implementation ⟷ Validation → Completion
 
 **Environment不変原則**: 現在の世代ではEnvironmentを直接変更しません。外部環境の変化を発見した場合はbacklogに記録し、Completionステージで反映します。
 
-### Backlog
+### Backlog [↗](https://reap.cc/docs/backlog)
 
 `.reap/life/backlog/`に次に反映するすべての項目を保存します。各項目はmarkdown + frontmatter形式：
 
@@ -154,13 +154,13 @@ Objective → Planning → Implementation ⟷ Validation → Completion
 
 **部分完了は正常** — Genome変更に依存するタスクは`[deferred]`とマークし、次の世代に引き継ぎます。
 
-### 4軸構造
+### 4軸構造 [↗](https://reap.cc/docs/core-concepts)
 
 ```
 .reap/
 ├── genome/        # 遺伝情報（世代を超えて進化）
 ├── environment/   # 外部環境（APIドキュメント、インフラ、ビジネス制約）
-├── life/          # 現在の世代の状態と成果物
+├── life/          # ライフサイクル — 現在の世代の状態と成果物
 └── lineage/       # 完了した世代のアーカイブ
 ```
 
@@ -213,7 +213,7 @@ Machine A:
 - **サーバー不要** — すべてがローカル + Git。外部サービスは不要です。
 - **DAG lineage** — 各世代はハッシュベースのID（`gen-046-a3f8c2`）で親を参照し、有向非巡回グラフを形成するため、並行作業を自然にサポートします。
 
-## CLIコマンド
+## CLIコマンド [↗](https://reap.cc/docs/cli-reference)
 
 | コマンド | 説明 |
 |----------|------|
@@ -235,7 +235,7 @@ reap update --dry-run                   # 変更のプレビュー
 
 REAPはスラッシュコマンドとセッションフックを通じてAIエージェントと統合します。現在サポートされているエージェント：**Claude Code**、**OpenCode**。
 
-### スラッシュコマンド
+### スラッシュコマンド [↗](https://reap.cc/docs/command-reference)
 
 スラッシュコマンドが`.claude/commands/`にインストールされ、ワークフロー全体を駆動します：
 
@@ -246,13 +246,17 @@ REAPはスラッシュコマンドとセッションフックを通じてAIエ
 | `/reap.planning` | タスク分解 + 実装計画 |
 | `/reap.implementation` | AI+Human協力でコード実装 |
 | `/reap.validation` | テスト実行、完了条件の確認 |
-| `/reap.completion` | レトロスペクティブ + Genome変更反映 |
+| `/reap.completion` | レトロスペクティブ + Genome変更反映 + lineage圧縮 |
 | `/reap.next` | 次のライフサイクルステージへ前進 |
 | `/reap.back` | 前のステージに回帰（micro loop） |
+| `/reap.abort` | 現在のGenerationを中断（rollback/stash/hold + backlog保存） |
 | `/reap.status` | 現在のGeneration状態とプロジェクト健全性を表示 |
-| `/reap.sync` | ソースコードベースでGenomeを最新化 |
-| `/reap.help` | 24+トピックのcontextual AIヘルプ（workflow, genome, backlog, strict, agents, hooks, config, evolve, regression, authorおよび全コマンド名） |
-| `/reap.update` | REAPのアップデート確認と最新バージョンへのアップグレード |
+| `/reap.sync` | GenomeとEnvironmentを同時に同期 |
+| `/reap.sync.genome` | ソースコードベースでGenomeを最新化 |
+| `/reap.sync.environment` | 外部環境依存関係の発見と文書化 |
+| `/reap.report` | REAPプロジェクトにバグ/フィードバックを報告（プライバシー保護） |
+| `/reap.help` | 24+トピックのcontextual AIヘルプ |
+| `/reap.update` | REAPパッケージのアップグレード + コマンド/テンプレート/hook同期 |
 | **`/reap.evolve`** | **1つのGeneration全体を最初から最後まで実行（推奨）** |
 | **`/reap.pull <branch>`** | **Fetch + マージGeneration全体を実行（分散版 `/reap.evolve`）** |
 | **`/reap.merge <branch>`** | **ローカルブランチのマージGeneration全体を実行（fetchなし）** |
@@ -265,7 +269,7 @@ REAPはスラッシュコマンドとセッションフックを通じてAIエ
 | `/reap.merge.validation` | 機械的テストを実行（bun test、tsc、build） |
 | **`/reap.merge.evolve`** | **マージライフサイクル全体を自動実行** |
 
-### SessionStart Hook
+### SessionStart Hook [↗](https://reap.cc/docs/hooks)
 
 毎セッション開始時に自動実行され、AIエージェントに以下を注入します：
 
@@ -305,7 +309,7 @@ strict:
 
 Strictモードはデフォルトで無効です（`strict: false`）。
 
-### REAP Hooks
+### REAP Hooks [↗](https://reap.cc/docs/hooks)
 
 Hookはファイルベースで`.reap/hooks/`に保存されます。各Hookは`{event}.{name}.{md|sh}`形式のファイルです：
 
@@ -314,33 +318,47 @@ Hookはファイルベースで`.reap/hooks/`に保存されます。各Hookは`
 
 ```
 .reap/hooks/
-├── onGenerationStart.context-load.md
-├── onGenerationComplete.version-bump.md
-├── onGenerationComplete.readme-update.md
-├── onStageTransition.notify.sh
-└── onRegression.alert.sh
+├── onLifeStarted.context-load.md
+├── onLifeCompleted.version-bump.md
+├── onLifeCompleted.readme-update.md
+├── onLifeTransited.notify.sh
+└── onLifeRegretted.alert.sh
 ```
 
 各Hookファイルは以下のフィールドを持つfrontmatterをサポートします：
 
 ```yaml
 ---
-condition: has-code-changes   # always | has-code-changes | version-bumped
+condition: has-code-changes   # .reap/hooks/conditions/内のスクリプト名
 order: 10                     # 実行順序（小さいほど先に実行）
 ---
 ```
 
+**Normal Lifecycle Events:**
+
+| イベント | トリガー |
+|----------|----------|
+| `onLifeStarted` | `/reap.start`で新しいGeneration作成後 |
+| `onLifeObjected` | objectiveステージ完了後 |
+| `onLifePlanned` | planningステージ完了後 |
+| `onLifeImplemented` | implementationステージ完了後 |
+| `onLifeValidated` | validationステージ完了後 |
+| `onLifeCompleted` | completion + archiving後（git commit後に実行） |
+| `onLifeTransited` | すべてのstage遷移時（汎用） |
+| `onLifeRegretted` | `/reap.back` regression時 |
+
+**Merge Lifecycle Events:**
+
 | イベント | トリガー |
 |----------|----------|
-| `onGenerationStart` | `/reap.start`で新しいGeneration作成後 |
-| `onStageTransition` | `/reap.next`で次のステージに前進後 |
-| `onGenerationComplete` | `/reap.next`で完了したGenerationをアーカイブ後 |
-| `onRegression` | `/reap.back`で前のステージに回帰後 |
-| `onMergeStart` | `/reap.merge.start`でマージGeneration作成後 |
-| `onGenomeResolved` | マージ中にGenomeの競合が解決された後 |
-| `onMergeComplete` | マージGenerationがアーカイブされた後 |
-
-HookはAIエージェントがプロジェクトルートディレクトリで実行します。`onGenerationComplete` Hookには自動バージョンバンプ判定が含まれています — patchレベルは自動適用され、minor/majorバンプはユーザー確認が必要です。
+| `onMergeStarted` | `/reap.merge.start`でマージGeneration作成後 |
+| `onMergeDetected` | detectステージ完了後 |
+| `onMergeMated` | mateステージ完了後（genome確定） |
+| `onMergeMerged` | mergeステージ完了後（ソースマージ） |
+| `onMergeSynced` | syncステージ完了後 |
+| `onMergeValidated` | merge validation完了後 |
+| `onMergeCompleted` | merge completion + archiving後 |
+| `onMergeTransited` | すべてのmerge stage遷移時（汎用） |
 
 ## `reap init`後のプロジェクト構造
 

package/README.ko.md

@@ -118,9 +118,9 @@ Objective → Planning → Implementation ⟷ Validation → Completion
 | **Validation** | 테스트 실행, 완료 조건 점검 | `04-validation.md` |
 | **Completion** | 회고 + Genome 변경 반영 + Hook 제안 + 아카이빙 | `05-completion.md` |
 
-## 핵심 개념
+## 핵심 개념 [↗](https://reap.cc/docs/core-concepts)
 
-### Genome
+### Genome [↗](https://reap.cc/docs/genome)
 
 Application의 유전 정보 — 아키텍처 원칙, 비즈니스 규칙, 개발 컨벤션, 기술 제약의 집합.
 
@@ -137,7 +137,7 @@ Application의 유전 정보 — 아키텍처 원칙, 비즈니스 규칙, 개
 
 **Environment 불변 원칙**: 현재 세대에서는 Environment를 직접 수정하지 않습니다. 외부 환경 변화를 발견하면 backlog에 기록하고, Completion 단계에서 반영합니다.
 
-### Backlog
+### Backlog [↗](https://reap.cc/docs/backlog)
 
 `.reap/life/backlog/`에 다음에 반영할 모든 항목을 저장합니다. 각 항목은 markdown + frontmatter 형식:
 
@@ -154,13 +154,13 @@ Application의 유전 정보 — 아키텍처 원칙, 비즈니스 규칙, 개
 
 **부분 완료는 정상** — Genome 변경에 의존하는 태스크는 `[deferred]`로 마킹하고 다음 세대로 인계합니다.
 
-### 4축 구조
+### 4축 구조 [↗](https://reap.cc/docs/core-concepts)
 
 ```
 .reap/
 ├── genome/        # 유전 정보 (세대를 거치며 진화)
 ├── environment/   # 외부 환경 (API 문서, 인프라, 비즈니스 제약)
-├── life/          # 현재 세대의 상태와 산출물
+├── life/          # 라이프사이클 — 현재 세대의 상태와 산출물
 └── lineage/       # 완료된 세대들의 아카이브
 ```
 
@@ -246,13 +246,17 @@ Slash command가 `.claude/commands/`에 설치되어 전체 워크플로우를
 | `/reap.planning` | 태스크 분해 + 구현 계획 |
 | `/reap.implementation` | AI+Human 협업 코드 구현 |
 | `/reap.validation` | 테스트 실행, 완료 조건 점검 |
-| `/reap.completion` | 회고 + Genome 변경 반영 |
+| `/reap.completion` | 회고 + Genome 변경 반영 + lineage 압축 |
 | `/reap.next` | 다음 Life Cycle stage로 전진 |
 | `/reap.back` | 이전 stage로 복귀 (micro loop) |
+| `/reap.abort` | 현재 Generation 중단 (rollback/stash/hold + backlog 저장) |
 | `/reap.status` | 현재 Generation 상태 및 프로젝트 건강 상태 표시 |
-| `/reap.sync` | 소스 코드 기반 Genome 최신화 |
-| `/reap.help` | 24+ 주제의 contextual AI 도움말 (workflow, genome, backlog, strict, agents, hooks, config, evolve, regression, author 및 모든 커맨드 이름) |
-| `/reap.update` | REAP 업데이트 확인 및 최신 버전으로 업그레이드 |
+| `/reap.sync` | Genome + Environment 동시 동기화 |
+| `/reap.sync.genome` | 소스 코드 기반 Genome 최신화 |
+| `/reap.sync.environment` | 외부 환경 의존성 탐색 및 문서화 |
+| `/reap.report` | REAP 프로젝트에 버그/피드백 보고 (개인정보 보호) |
+| `/reap.help` | 24+ 주제의 contextual AI 도움말 |
+| `/reap.update` | REAP 패키지 업그레이드 + 커맨드/템플릿/훅 동기화 |
 | **`/reap.evolve`** | **한 Generation 전체를 처음부터 끝까지 실행 (권장)** |
 | **`/reap.pull <branch>`** | **Fetch + 전체 머지 Generation 실행 (분산 `/reap.evolve`)** |
 | **`/reap.merge <branch>`** | **로컬 브랜치 전체 머지 Generation 실행 (fetch 없음)** |
@@ -265,7 +269,7 @@ Slash command가 `.claude/commands/`에 설치되어 전체 워크플로우를
 | `/reap.merge.validation` | 기계적 테스트 실행 (bun test, tsc, build) |
 | **`/reap.merge.evolve`** | **전체 머지 라이프사이클 자동 실행** |
 
-### SessionStart Hook
+### SessionStart Hook [↗](https://reap.cc/docs/hooks)
 
 매 세션 시작 시 자동으로 실행되어 AI 에이전트에게 다음을 주입합니다:
 
@@ -305,7 +309,7 @@ strict:
 
 Strict 모드는 기본적으로 비활성화되어 있습니다 (`strict: false`).
 
-### REAP Hooks
+### REAP Hooks [↗](https://reap.cc/docs/hooks)
 
 Hook은 파일 기반이며 `.reap/hooks/`에 저장됩니다. 각 Hook은 `{event}.{name}.{md|sh}` 형식의 파일입니다:
 
@@ -314,33 +318,47 @@ Hook은 파일 기반이며 `.reap/hooks/`에 저장됩니다. 각 Hook은 `{eve
 
 ```
 .reap/hooks/
-├── onGenerationStart.context-load.md
-├── onGenerationComplete.version-bump.md
-├── onGenerationComplete.readme-update.md
-├── onStageTransition.notify.sh
-└── onRegression.alert.sh
+├── onLifeStarted.context-load.md
+├── onLifeCompleted.version-bump.md
+├── onLifeCompleted.readme-update.md
+├── onLifeTransited.notify.sh
+└── onLifeRegretted.alert.sh
 ```
 
 각 Hook 파일은 다음 필드를 가진 frontmatter를 지원합니다:
 
 ```yaml
 ---
-condition: has-code-changes   # always | has-code-changes | version-bumped
+condition: has-code-changes   # .reap/hooks/conditions/ 내 스크립트 이름
 order: 10                     # 실행 순서 (낮을수록 먼저 실행)
 ---
 ```
 
+**Normal Lifecycle Events:**
+
+| 이벤트 | 트리거 |
+|--------|--------|
+| `onLifeStarted` | `/reap.start`로 새 Generation 생성 후 |
+| `onLifeObjected` | objective 단계 완료 후 |
+| `onLifePlanned` | planning 단계 완료 후 |
+| `onLifeImplemented` | implementation 단계 완료 후 |
+| `onLifeValidated` | validation 단계 완료 후 |
+| `onLifeCompleted` | completion + archiving 후 (git commit 이후 실행) |
+| `onLifeTransited` | 모든 stage 전환 시 (범용) |
+| `onLifeRegretted` | `/reap.back` regression 시 |
+
+**Merge Lifecycle Events:**
+
 | 이벤트 | 트리거 |
 |--------|--------|
-| `onGenerationStart` | `/reap.start`로 새 Generation 생성 후 |
-| `onStageTransition` | `/reap.next`로 다음 stage 전진 후 |
-| `onGenerationComplete` | `/reap.next`로 완료된 Generation 아카이빙 후 |
-| `onRegression` | `/reap.back`으로 이전 stage 복귀 후 |
-| `onMergeStart` | `/reap.merge.start`로 머지 Generation 생성 후 |
-| `onGenomeResolved` | 머지 중 Genome 충돌 해결 완료 후 |
-| `onMergeComplete` | 머지 Generation 아카이빙 후 |
-
-Hook은 AI 에이전트가 프로젝트 루트 디렉토리에서 실행합니다. `onGenerationComplete` Hook에는 자동 버전 범프 판단이 포함되어 있습니다 — patch 수준은 자동으로 적용되고, minor/major 범프는 사용자 확인을 거칩니다.
+| `onMergeStarted` | `/reap.merge.start`로 머지 Generation 생성 후 |
+| `onMergeDetected` | detect 단계 완료 후 |
+| `onMergeMated` | mate 단계 완료 후 (genome 확정) |
+| `onMergeMerged` | merge 단계 완료 후 (소스 병합) |
+| `onMergeSynced` | sync 단계 완료 후 |
+| `onMergeValidated` | merge validation 완료 후 |
+| `onMergeCompleted` | merge completion + archiving 후 |
+| `onMergeTransited` | 모든 merge stage 전환 시 (범용) |
 
 ## `reap init` 후 프로젝트 구조
 

package/README.md

@@ -101,7 +101,7 @@ You can also drive each stage manually if you need finer control:
 > ...
 ```
 
-## Life Cycle
+## Life Cycle [↗](https://reap.cc/docs/lifecycle)
 
 Each generation goes through a five-stage life cycle:
 
@@ -117,9 +117,9 @@ Objective → Planning → Implementation ⟷ Validation → Completion
 | **Validation** | Run tests, verify completion criteria | `04-validation.md` |
 | **Completion** | Retrospective + apply Genome changes + hook suggestion + archive | `05-completion.md` |
 
-## Core Concepts
+## Core Concepts [↗](https://reap.cc/docs/core-concepts)
 
-### Genome
+### Genome [↗](https://reap.cc/docs/genome)
 
 The application's genetic information — a collection of architecture principles, business rules, development conventions, and technical constraints.
 
@@ -136,7 +136,7 @@ The application's genetic information — a collection of architecture principle
 
 **Environment Immutability Principle**: The Environment is never modified directly during the current generation. External changes are recorded in the backlog and applied at the Completion stage.
 
-### Backlog
+### Backlog [↗](https://reap.cc/docs/backlog)
 
 All items to be addressed next are stored in `.reap/life/backlog/`. Each item uses markdown + frontmatter format:
 
@@ -153,17 +153,17 @@ At archiving time (`/reap.next` from Completion), `consumed` items move to linea
 
 **Partial completion is normal** — Tasks that depend on Genome changes are marked `[deferred]` and handed off to the next generation.
 
-### Four-Axis Structure
+### Four-Axis Structure [↗](https://reap.cc/docs/core-concepts)
 
 ```
 .reap/
 ├── genome/        # Genetic information (evolves across generations)
 ├── environment/   # External context (API docs, infra, business constraints)
-├── life/          # Current generation's state and artifacts
+├── life/          # Lifecycle — current generation's state and artifacts
 └── lineage/       # Archive of completed generations
 ```
 
-## Distributed Workflow for Parallel Development
+## Distributed Workflow [↗](https://reap.cc/docs/distributed-workflow)
 
 > **⚠ Early Stage** — The distributed workflow requires further testing. Use with caution in production. We're collecting feedback — [open an issue](https://github.com/c-d-cc/reap/issues).
 
@@ -212,7 +212,7 @@ All distributed operations run through your AI agent:
 - **No server** — Everything is local + Git. No external services.
 - **DAG lineage** — Each generation references its parents via a hash-based ID (`gen-046-a3f8c2`), forming a directed acyclic graph that naturally supports parallel work.
 
-## CLI Commands
+## CLI Commands [↗](https://reap.cc/docs/cli-reference)
 
 | Command | Description |
 |---------|-------------|
@@ -234,7 +234,7 @@ reap update --dry-run                   # Preview changes before applying
 
 REAP integrates with AI agents through slash commands and session hooks. Currently supported agents: **Claude Code** and **OpenCode**.
 
-### Slash Commands
+### Slash Commands [↗](https://reap.cc/docs/command-reference)
 
 Slash commands are installed in `.claude/commands/` and drive the entire workflow:
 
@@ -245,13 +245,17 @@ Slash commands are installed in `.claude/commands/` and drive the entire workflo
 | `/reap.planning` | Task decomposition + implementation plan |
 | `/reap.implementation` | Code implementation with AI + human |
 | `/reap.validation` | Run tests, verify completion criteria |
-| `/reap.completion` | Retrospective + apply Genome changes |
+| `/reap.completion` | Retrospective + apply Genome changes + lineage compression |
 | `/reap.next` | Advance to the next life cycle stage |
 | `/reap.back` | Return to a previous stage (micro loop) |
+| `/reap.abort` | Abort current generation (rollback/stash/hold + backlog save) |
 | `/reap.status` | Show current generation state and project health |
-| `/reap.sync` | Synchronize Genome with current source code |
-| `/reap.help` | Contextual AI help with 24+ topics (workflow, genome, backlog, strict, agents, hooks, config, evolve, regression, author, and all command names) |
-| `/reap.update` | Check for REAP updates and upgrade to the latest version |
+| `/reap.sync` | Synchronize both Genome and Environment |
+| `/reap.sync.genome` | Synchronize Genome with current source code |
+| `/reap.sync.environment` | Discover and document external environment dependencies |
+| `/reap.report` | Report a bug or feedback to the REAP project (privacy-safe) |
+| `/reap.help` | Contextual AI help with 24+ topics |
+| `/reap.update` | Upgrade REAP package + sync commands/templates/hooks |
 | **`/reap.evolve`** | **Run an entire generation from start to finish (recommended)** |
 | **`/reap.pull <branch>`** | **Fetch + run full merge generation (distributed `/reap.evolve`)** |
 | **`/reap.merge <branch>`** | **Run full merge generation for a local branch (no fetch)** |
@@ -264,19 +268,21 @@ Slash commands are installed in `.claude/commands/` and drive the entire workflo
 | `/reap.merge.validation` | Run mechanical testing (bun test, tsc, build) |
 | **`/reap.merge.evolve`** | **Run the full merge lifecycle automatically** |
 
-### SessionStart Hook
+### SessionStart Hook [↗](https://reap.cc/docs/hooks)
 
 Runs automatically at the start of every session, injecting the following into the AI agent:
 
 - The full REAP workflow guide (Genome, Life Cycle, Four-Axis Structure, etc.)
 - Current generation state (which stage you're in, what to do next)
+- Environment summary (`environment/summary.md`) — external system context
 - 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
+- Genome staleness detection — checks if code-related commits have occurred since the last Genome update
+- Source-map drift detection — compares documented components against actual files
+- Slash command installation — copies commands from `~/.reap/commands/` to project `.claude/commands/`
 
 This ensures the agent immediately understands the project context even in a brand-new session.
 
-### Strict Mode
+### Strict Mode [↗](https://reap.cc/docs/configuration)
 
 Strict mode controls what the AI agent is allowed to do. It supports two granular options:
 
@@ -304,7 +310,7 @@ Both are disabled by default. `strict: true` enables both.
 
 Strict mode is disabled by default (`strict: false`).
 
-### REAP Hooks
+### REAP Hooks [↗](https://reap.cc/docs/hooks)
 
 Hooks are file-based and stored in `.reap/hooks/`. Each hook is a file named `{event}.{name}.{md|sh}`:
 
@@ -313,33 +319,47 @@ Hooks are file-based and stored in `.reap/hooks/`. Each hook is a file named `{e
 
 ```
 .reap/hooks/
-├── onGenerationStart.context-load.md
-├── onGenerationComplete.version-bump.md
-├── onGenerationComplete.readme-update.md
-├── onStageTransition.notify.sh
-└── onRegression.alert.sh
+├── onLifeStarted.context-load.md
+├── onLifeCompleted.reap-update.sh
+├── onLifeCompleted.docs-update.md
+├── onLifeTransited.notify.sh
+└── onLifeRegretted.alert.sh
 ```
 
 Each hook file supports frontmatter with the following fields:
 
 ```yaml
 ---
-condition: has-code-changes   # always | has-code-changes | version-bumped
+condition: has-code-changes   # script name in .reap/hooks/conditions/
 order: 10                     # execution order (lower runs first)
 ---
 ```
 
+**Normal Lifecycle Events:**
+
 | Event | Trigger |
 |-------|---------|
-| `onGenerationStart` | After `/reap.start` creates a new generation |
-| `onStageTransition` | After `/reap.next` advances to the next stage |
-| `onGenerationComplete` | After `/reap.next` archives a completed generation |
-| `onRegression` | After `/reap.back` returns to a previous stage |
-| `onMergeStart` | After `/reap.merge.start` creates a merge generation |
-| `onGenomeResolved` | After genome conflicts are resolved in a merge |
-| `onMergeComplete` | After a merge generation is archived |
+| `onLifeStarted` | After `/reap.start` creates a new generation |
+| `onLifeObjected` | After objective stage completes |
+| `onLifePlanned` | After planning stage completes |
+| `onLifeImplemented` | After implementation stage completes |
+| `onLifeValidated` | After validation stage completes |
+| `onLifeCompleted` | After completion + archiving (runs after git commit) |
+| `onLifeTransited` | After any stage transition (generic) |
+| `onLifeRegretted` | After `/reap.back` regression |
+
+**Merge Lifecycle Events:**
 
-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.
+| Event | Trigger |
+|-------|---------|
+| `onMergeStarted` | After `/reap.merge.start` creates a merge generation |
+| `onMergeDetected` | After detect stage completes |
+| `onMergeMated` | After mate stage completes (genome resolved) |
+| `onMergeMerged` | After merge stage completes (source merged) |
+| `onMergeSynced` | After sync stage completes |
+| `onMergeValidated` | After merge validation completes |
+| `onMergeCompleted` | After merge completion + archiving |
+| `onMergeTransited` | After any merge stage transition (generic) |
 
 ## Project Structure After `reap init`
 
@@ -355,27 +375,38 @@ my-project/
     │   ├── constraints.md
     │   └── source-map.md
     ├── hooks/                    # Lifecycle hooks (.md/.sh)
-    ├── environment/              # External context
+    ├── environment/              # External context (3-layer)
+    │   ├── summary.md            # Session context (~100 lines, auto-loaded)
+    │   ├── docs/                 # Main reference docs
+    │   └── resources/            # Raw materials (user-managed)
     ├── life/                     # Current generation
     │   ├── current.yml
     │   └── backlog/
     └── lineage/                  # Completed generation archive
 
-~/.claude/                        # User-level (installed by reap init)
-├── commands/                     # Slash commands (/reap.*)
-└── settings.json                 # SessionStart hook registration
+~/.reap/                            # User-level (installed by reap init)
+├── commands/                       # Slash command originals
+└── templates/                      # Artifact templates
+
+~/.claude/
+└── settings.json                   # SessionStart hook registration
+
+.claude/commands/                   # Project-level (copied by session-start hook)
+└── reap.*.md                       # Active slash commands (auto-synced)
 ```
 
-## Lineage Compression
+## Lineage Compression [↗](https://reap.cc/docs/lineage)
+
+As generations accumulate, the lineage directory grows. REAP manages this with automatic two-level compression during the Completion stage:
 
-As generations accumulate, the lineage directory grows. REAP manages this with automatic two-level compression:
+| Level | Input | Output | Trigger | Protection |
+|-------|-------|--------|---------|------------|
+| **Level 1** | Generation folder (5 artifacts) | `gen-XXX-{hash}.md` (40 lines) | lineage > 5,000 lines + 5+ generations | Recent 3 generations + DAG leaf nodes |
+| **Level 2** | 100+ Level 1 files | Single `epoch.md` | Level 1 files > 100 | Recent 9 Level 1 files + fork points |
 
-| Level | Input | Output | Max lines | Trigger |
-|-------|-------|--------|-----------|---------|
-| **Level 1** | Generation folder (5 artifacts) | `gen-XXX-{hash}.md` | 40 lines | lineage > 5,000 lines + 5+ generations |
-| **Level 2** | 5 Level 1 files | `epoch-XXX.md` | 60 lines | 5+ Level 1 files |
+**DAG preservation**: Level 1 files retain DAG metadata (id, parents, genomeHash) in frontmatter. Level 2 `epoch.md` stores a `generations` hash chain in frontmatter for DAG traversal.
 
-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.
+**Fork guard**: Before Level 2 compression, all local and remote branches are scanned. Generations that serve as fork points for other branches are protected from epoch compression. Epoch-compressed generations cannot be used as merge bases.
 
 ## Evolution Flow
 

package/README.zh-CN.md

@@ -101,7 +101,7 @@ claude
 > ...
 ```
 
-## 生命周期
+## 生命周期 [↗](https://reap.cc/docs/lifecycle)
 
 每个Generation经历5个阶段的生命周期：
 
@@ -118,9 +118,9 @@ Objective → Planning → Implementation ⟷ Validation → Completion
 | **Validation** | 执行测试、检查完成条件 | `04-validation.md` |
 | **Completion** | 回顾 + 应用Genome变更 + Hook建议 + 归档 | `05-completion.md` |
 
-## 核心概念
+## 核心概念 [↗](https://reap.cc/docs/core-concepts)
 
-### Genome
+### Genome [↗](https://reap.cc/docs/genome)
 
 应用程序的遗传信息 — 架构原则、业务规则、开发约定、技术约束的集合。
 
@@ -137,7 +137,7 @@ Objective → Planning → Implementation ⟷ Validation → Completion
 
 **Environment不变原则**：当前世代不直接修改Environment。发现外部环境变化时记录在backlog中，在Completion阶段反映。
 
-### Backlog
+### Backlog [↗](https://reap.cc/docs/backlog)
 
 `.reap/life/backlog/`中存储所有待反映的项目。每个项目使用markdown + frontmatter格式：
 
@@ -154,13 +154,13 @@ Objective → Planning → Implementation ⟷ Validation → Completion
 
 **部分完成是正常的** — 依赖Genome变更的任务标记为`[deferred]`并交接到下一个世代。
 
-### 四轴结构
+### 四轴结构 [↗](https://reap.cc/docs/core-concepts)
 
 ```
 .reap/
 ├── genome/        # 遗传信息（跨世代进化）
 ├── environment/   # 外部环境（API文档、基础设施、业务约束）
-├── life/          # 当前世代的状态和产出物
+├── life/          # 生命周期 — 当前世代的状态和产出物
 └── lineage/       # 已完成世代的归档
 ```
 
@@ -213,7 +213,7 @@ Machine A:
 - **无需服务器** — 一切基于本地 + Git，无需外部服务。
 - **DAG lineage** — 每个世代通过基于哈希的ID（`gen-046-a3f8c2`）引用其父代，形成有向无环图，天然支持并行工作。
 
-## CLI命令
+## CLI命令 [↗](https://reap.cc/docs/cli-reference)
 
 | 命令 | 说明 |
 |------|------|
@@ -235,7 +235,7 @@ reap update --dry-run                   # 预览变更
 
 REAP通过斜杠命令和会话钩子与AI代理集成。当前支持的代理：**Claude Code**、**OpenCode**。
 
-### 斜杠命令
+### 斜杠命令 [↗](https://reap.cc/docs/command-reference)
 
 斜杠命令安装在`.claude/commands/`中，驱动整个工作流：
 
@@ -246,13 +246,17 @@ REAP通过斜杠命令和会话钩子与AI代理集成。当前支持的代理
 | `/reap.planning` | 任务分解 + 实施计划 |
 | `/reap.implementation` | AI+人类协作编写代码 |
 | `/reap.validation` | 执行测试、检查完成条件 |
-| `/reap.completion` | 回顾 + 应用Genome变更 |
+| `/reap.completion` | 回顾 + 应用Genome变更 + lineage压缩 |
 | `/reap.next` | 前进到下一个生命周期阶段 |
 | `/reap.back` | 回到前一个阶段（micro loop） |
+| `/reap.abort` | 中止当前Generation（rollback/stash/hold + backlog保存） |
 | `/reap.status` | 显示当前Generation状态和项目健康度 |
-| `/reap.sync` | 基于源代码同步Genome |
-| `/reap.help` | 24+主题的上下文AI帮助（workflow, genome, backlog, strict, agents, hooks, config, evolve, regression, author及所有命令名） |
-| `/reap.update` | 检查REAP更新并升级到最新版本 |
+| `/reap.sync` | 同时同步Genome和Environment |
+| `/reap.sync.genome` | 基于源代码同步Genome |
+| `/reap.sync.environment` | 发现和记录外部环境依赖 |
+| `/reap.report` | 向REAP项目报告bug/反馈（隐私保护） |
+| `/reap.help` | 24+主题的上下文AI帮助 |
+| `/reap.update` | 升级REAP包 + 同步命令/模板/hook |
 | **`/reap.evolve`** | **从头到尾运行一个完整的Generation（推荐）** |
 | **`/reap.pull <branch>`** | **Fetch + 运行完整合并Generation（分布式 `/reap.evolve`）** |
 | **`/reap.merge <branch>`** | **本地分支完整合并Generation（无需fetch）** |
@@ -265,7 +269,7 @@ REAP通过斜杠命令和会话钩子与AI代理集成。当前支持的代理
 | `/reap.merge.validation` | 运行机械化测试（bun test、tsc、build） |
 | **`/reap.merge.evolve`** | **自动运行完整的合并生命周期** |
 
-### SessionStart Hook
+### SessionStart Hook [↗](https://reap.cc/docs/hooks)
 
 每次会话开始时自动运行，向AI代理注入以下内容：
 
@@ -305,7 +309,7 @@ strict:
 
 Strict模式默认禁用（`strict: false`）。
 
-### REAP Hooks
+### REAP Hooks [↗](https://reap.cc/docs/hooks)
 
 Hook基于文件，存储在`.reap/hooks/`中。每个Hook是一个以`{event}.{name}.{md|sh}`命名的文件：
 
@@ -314,33 +318,47 @@ Hook基于文件，存储在`.reap/hooks/`中。每个Hook是一个以`{event}.{
 
 ```
 .reap/hooks/
-├── onGenerationStart.context-load.md
-├── onGenerationComplete.version-bump.md
-├── onGenerationComplete.readme-update.md
-├── onStageTransition.notify.sh
-└── onRegression.alert.sh
+├── onLifeStarted.context-load.md
+├── onLifeCompleted.version-bump.md
+├── onLifeCompleted.readme-update.md
+├── onLifeTransited.notify.sh
+└── onLifeRegretted.alert.sh
 ```
 
 每个Hook文件支持包含以下字段的frontmatter：
 
 ```yaml
 ---
-condition: has-code-changes   # always | has-code-changes | version-bumped
+condition: has-code-changes   # .reap/hooks/conditions/中的脚本名称
 order: 10                     # 执行顺序（数值越小越先执行）
 ---
 ```
 
+**Normal Lifecycle Events:**
+
+| 事件 | 触发时机 |
+|------|----------|
+| `onLifeStarted` | `/reap.start`创建新Generation后 |
+| `onLifeObjected` | objective阶段完成后 |
+| `onLifePlanned` | planning阶段完成后 |
+| `onLifeImplemented` | implementation阶段完成后 |
+| `onLifeValidated` | validation阶段完成后 |
+| `onLifeCompleted` | completion + 归档后（git commit之后运行） |
+| `onLifeTransited` | 所有stage转换时（通用） |
+| `onLifeRegretted` | `/reap.back` regression时 |
+
+**Merge Lifecycle Events:**
+
 | 事件 | 触发时机 |
 |------|----------|
-| `onGenerationStart` | `/reap.start`创建新Generation后 |
-| `onStageTransition` | `/reap.next`前进到下一阶段后 |
-| `onGenerationComplete` | `/reap.next`归档已完成的Generation后 |
-| `onRegression` | `/reap.back`回到前一阶段后 |
-| `onMergeStart` | `/reap.merge.start`创建合并Generation后 |
-| `onGenomeResolved` | 合并过程中Genome冲突解决完成后 |
-| `onMergeComplete` | 合并Generation归档后 |
-
-Hook由AI代理在项目根目录中执行。`onGenerationComplete` Hook包含自动版本号升级判断 — patch级别自动应用，minor/major级别需要用户确认。
+| `onMergeStarted` | `/reap.merge.start`创建合并Generation后 |
+| `onMergeDetected` | detect阶段完成后 |
+| `onMergeMated` | mate阶段完成后（genome确定） |
+| `onMergeMerged` | merge阶段完成后（源代码合并） |
+| `onMergeSynced` | sync阶段完成后 |
+| `onMergeValidated` | merge validation完成后 |
+| `onMergeCompleted` | merge completion + 归档后 |
+| `onMergeTransited` | 所有merge stage转换时（通用） |
 
 ## `reap init`后的项目结构
 

package/dist/cli.js

@@ -9817,7 +9817,7 @@ async function initProject(projectRoot, projectName, entryMode, preset, onProgre
     log("GitHub CLI(gh) not found. Install from https://cli.github.com for auto issue reporting.");
   }
   const config = {
-    version: "0.1.0",
+    version: "0.10.1",
     project: projectName,
     entryMode,
     autoUpdate: true,
@@ -10758,6 +10758,98 @@ async function migrateLineage(paths) {
   return result;
 }
 
+// src/core/migrations/0.0.0-to-0.10.0.ts
+var migration_0_0_0_to_0_10_0 = {
+  fromVersion: "0.0.0",
+  toVersion: "0.10.0",
+  description: "Lineage DAG migration — legacy gen-NNN directories to gen-NNN-HASH format",
+  async check(paths) {
+    return needsMigration(paths);
+  },
+  async up(paths) {
+    const result = await migrateLineage(paths);
+    const messages = [];
+    for (const m of result.migrated) {
+      messages.push(`[lineage] ${m}`);
+    }
+    if (result.errors.length > 0) {
+      throw new Error(`Lineage migration errors: ${result.errors.join("; ")}`);
+    }
+    return messages;
+  }
+};
+
+// src/core/migrations/index.ts
+var MIGRATIONS = [
+  migration_0_0_0_to_0_10_0
+];
+function compareSemver(a, b) {
+  const pa = a.split(".").map(Number);
+  const pb = b.split(".").map(Number);
+  for (let i = 0;i < 3; i++) {
+    const na = pa[i] ?? 0;
+    const nb = pb[i] ?? 0;
+    if (na < nb)
+      return -1;
+    if (na > nb)
+      return 1;
+  }
+  return 0;
+}
+function normalizeVersion(version) {
+  if (!version)
+    return "0.0.0";
+  if (version === "0.1.0")
+    return "0.0.0";
+  return version.replace(/\+.*$/, "");
+}
+
+class MigrationRunner {
+  static async run(paths, currentPackageVersion, dryRun = false) {
+    const config = await ConfigManager.read(paths);
+    const configVersion = normalizeVersion(config.version);
+    const targetVersion = normalizeVersion(currentPackageVersion);
+    const result = {
+      migrated: [],
+      skipped: [],
+      errors: [],
+      fromVersion: configVersion,
+      toVersion: targetVersion
+    };
+    if (compareSemver(configVersion, targetVersion) >= 0) {
+      return result;
+    }
+    const applicable = MIGRATIONS.filter((m) => compareSemver(configVersion, m.toVersion) < 0).filter((m) => compareSemver(m.toVersion, targetVersion) <= 0).sort((a, b) => compareSemver(a.toVersion, b.toVersion));
+    for (const migration of applicable) {
+      const needs = await migration.check(paths);
+      if (!needs) {
+        result.skipped.push(migration.description);
+        continue;
+      }
+      if (dryRun) {
+        result.migrated.push(`[dry-run] ${migration.description}`);
+        continue;
+      }
+      try {
+        const messages = await migration.up(paths);
+        result.migrated.push(...messages);
+      } catch (err) {
+        const errorMsg = `${migration.description}: ${err instanceof Error ? err.message : String(err)}`;
+        result.errors.push(errorMsg);
+        break;
+      }
+    }
+    if (result.errors.length === 0 && !dryRun) {
+      config.version = currentPackageVersion;
+      await ConfigManager.write(paths, config);
+    }
+    return result;
+  }
+  static getMigrations() {
+    return MIGRATIONS;
+  }
+}
+
 // src/cli/commands/update.ts
 function selfUpgrade() {
   try {
@@ -10900,18 +10992,25 @@ async function updateProject(projectRoot, dryRun = false) {
       result.skipped.push(`.claude/commands/ (${reapCmdFiles.length} unchanged)`);
     }
     await migrateLegacyFiles(paths, dryRun, result);
-    if (await needsMigration(paths)) {
-      if (!dryRun) {
-        const migrationResult = await migrateLineage(paths);
-        for (const m of migrationResult.migrated) {
-          result.updated.push(`[lineage] ${m}`);
-        }
-        for (const e of migrationResult.errors) {
-          result.removed.push(`[lineage error] ${e}`);
-        }
-      } else {
-        result.updated.push("[lineage] DAG migration pending (dry-run)");
-      }
+    const currentVersion = "0.10.1";
+    const migrationResult = await MigrationRunner.run(paths, currentVersion, dryRun);
+    for (const m of migrationResult.migrated) {
+      result.updated.push(`[migration] ${m}`);
+    }
+    for (const s of migrationResult.skipped) {
+      result.skipped.push(`[migration] ${s}`);
+    }
+    for (const e of migrationResult.errors) {
+      result.removed.push(`[migration error] ${e}`);
+    }
+    if (migrationResult.errors.length > 0 && config?.autoIssueReport) {
+      try {
+        const { execSync: execSync3 } = await import("child_process");
+        const errorSummary = migrationResult.errors.join("\\n");
+        const title = `Migration failure: ${migrationResult.fromVersion} → ${migrationResult.toVersion}`;
+        const body = `## Migration Error\\n\\nFrom: ${migrationResult.fromVersion}\\nTo: ${migrationResult.toVersion}\\n\\n### Errors\\n\\n${errorSummary}`;
+        execSync3(`gh issue create --repo c-d-cc/reap --title "${title}" --label "auto-reported,migration" --body "${body}"`, { encoding: "utf-8", timeout: 15000, stdio: "pipe" });
+      } catch {}
     }
   }
   return result;
@@ -11070,7 +11169,7 @@ async function fixProject(projectRoot) {
 // src/cli/index.ts
 init_fs();
 import { join as join12 } from "path";
-program.name("reap").description("REAP — Recursive Evolutionary Autonomous Pipeline").version("0.9.1");
+program.name("reap").description("REAP — Recursive Evolutionary Autonomous Pipeline").version("0.10.1");
 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

@@ -46,7 +46,7 @@ description: "REAP Back — Return to a previous lifecycle stage"
    ```
 
 ### Hook Execution (Regression)
-7. Scan `.reap/hooks/` for files matching `onRegression.*`
+7. Scan `.reap/hooks/` for files matching `onLifeRegretted.*`
    - 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):

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

@@ -81,10 +81,10 @@ Do NOT finalize Genome changes without running Validation Commands.
     a. **Describe the pattern**: "최근 N개 generation에서 '[작업 설명]'이 반복적으로 수행되었습니다."
     b. **Ask if it should be a hook**: "이 작업을 hook으로 자동화할까요? (yes/no)"
     c. If yes, ask **event**: "어떤 이벤트에서 실행할까요?"
-       - `onGenerationComplete` — generation 완료 후
-       - `onStageTransition` — stage 전환 시
-       - `onGenerationStart` — generation 시작 시
-       - `onRegression` — stage 회귀 시
+       - `onLifeCompleted` — generation 완료 후
+       - `onLifeTransited` — stage 전환 시
+       - `onLifeStarted` — generation 시작 시
+       - `onLifeRegretted` — stage 회귀 시
     d. Ask **condition**: "실행 조건은 무엇인가요?"
        - `always` — 항상
        - `has-code-changes` — src/ 변경이 있을 때

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

@@ -82,7 +82,7 @@ For command-name topics: read `reap.{name}.md` from the same directory as this f
 - **backlog** — `.reap/life/backlog/`. genome-change, environment-change, task. status: pending/consumed. consumed → lineage, pending → 이월.
 - **strict** — `strict: true`: no generation = 코드 수정 차단, non-implementation = 차단, implementation = plan scope만. Escape: "override"/"bypass strict".
 - **agents** — AgentAdapter 추상화. auto-detect (Claude Code, OpenCode). config.yml `agents` 오버라이드.
-- **hooks** — config.yml: onGenerationStart, onStageTransition, onGenerationComplete, onRegression. command/prompt 타입.
+- **hooks** — config.yml: onLifeStarted, onLifeTransited, onLifeCompleted, onLifeRegretted. command/prompt 타입.
 - **config** — `.reap/config.yml`: version, project, entryMode, strict, language, agents, autoUpdate, hooks.
 - **evolve** — `/reap.evolve`: 전체 lifecycle 자율 실행. 사람 확인 없이 objective~completion 순차 진행.
 - **regression** — `/reap.back`: 이전 stage 회귀. timeline + artifact에 Regression 섹션 기록.

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

@@ -23,8 +23,17 @@ This command is the **ONLY legitimate way** to advance the lifecycle stage. All
 - Immediately create the next stage's artifact file from template (empty, ready to fill)
 
 ### Hook Execution (Stage Transition)
-- Scan `.reap/hooks/` for files matching `onStageTransition.*`
-- For each matched file (sorted by `order` from frontmatter, then alphabetically):
+Execute two sets of hooks in order:
+
+1. **Stage-specific hook** — based on the stage that just completed:
+   - objective → planning: `onLifeObjected.*`
+   - planning → implementation: `onLifePlanned.*`
+   - implementation → validation: `onLifeImplemented.*`
+   - validation → completion: `onLifeValidated.*`
+
+2. **Generic transition hook** — `onLifeTransited.*` (fires on every transition)
+
+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`
@@ -64,7 +73,7 @@ This command is the **ONLY legitimate way** to advance the lifecycle stage. All
   - If there are no code changes (REAP-only generation), use `chore(reap): [goal summary]`
 
 ### Hook Execution (Generation Complete)
-- Scan `.reap/hooks/` for files matching `onGenerationComplete.*`
+- Scan `.reap/hooks/` for files matching `onLifeCompleted.*`
 - 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):

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

@@ -41,7 +41,7 @@ description: "REAP Start — Start a new Generation"
 7. Immediately create `.reap/life/01-objective.md` from the artifact template with the Goal section filled in
 
 ### Hook Execution (Generation Start)
-8. Scan `.reap/hooks/` for files matching `onGenerationStart.*`
+8. Scan `.reap/hooks/` for files matching `onLifeStarted.*`
    - 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):

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

@@ -110,19 +110,18 @@ Hooks are defined as individual files in `.reap/hooks/` with the naming conventi
 
 ```
 .reap/hooks/
-├── onGenerationComplete.version-bump.md
-├── onGenerationComplete.reap-update.sh
-├── onGenerationComplete.docs-update.md
-└── onGenerationComplete.release-notes.md
+├── onLifeCompleted.reap-update.sh
+├── onLifeCompleted.docs-update.md
+├── onLifeImplemented.lint-check.sh
+└── onMergeMated.notify.md
 ```
 
 File naming: `{event}.{name}.{extension}`
-- Event: onGenerationStart, onStageTransition, onGenerationComplete, onRegression
 - Extension: `.md` (AI prompt) or `.sh` (shell script)
+- Frontmatter: `condition` (default: `always`), `order` (default: 50, lower runs first)
 
-Frontmatter (`.md` files) or comment headers (`.sh` files):
-- `condition`: name of a script in `.reap/hooks/conditions/` (default: `always`)
-- `order`: execution order within the same event (default: 50, lower runs first)
+Normal events: `onLifeStarted`, `onLifeObjected`, `onLifePlanned`, `onLifeImplemented`, `onLifeValidated`, `onLifeCompleted`, `onLifeTransited`, `onLifeRegretted`
+Merge events: `onMergeStarted`, `onMergeDetected`, `onMergeMated`, `onMergeMerged`, `onMergeSynced`, `onMergeValidated`, `onMergeCompleted`, `onMergeTransited`
 
 ### Conditions
 
@@ -135,14 +134,13 @@ Default conditions (installed by `reap init`):
 
 Custom conditions: add any `.sh` script to `.reap/hooks/conditions/`. The hook's `condition` field matches the filename (without `.sh`).
 
-| Event | Trigger |
-|-------|---------|
-| `onGenerationStart` | After `/reap.start` creates a new generation |
-| `onStageTransition` | After `/reap.next` advances to the next stage |
-| `onGenerationComplete` | After `/reap.next` archives a completed generation (after commit) |
-| `onRegression` | After `/reap.back` returns to a previous stage |
+### Execution
 
-Hooks are executed by the AI agent by scanning `.reap/hooks/` for files matching the current event.
+Hooks are executed by the AI agent by scanning `.reap/hooks/` for files matching the current event:
+- `.md` files: read as AI prompt and follow the instructions
+- `.sh` files: run as shell script in the project root directory
+- Within the same event, hooks run in `order` (lower first), then alphabetically
+- `onLifeCompleted`/`onMergeCompleted` hooks run after git commit — changes are uncommitted
 
 ## Multi-Agent Support
 

package/package.json

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