@c-d-cc/reap 0.10.3 → 0.11.0

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

@@ -2,43 +2,4 @@
 description: "REAP Update — Check for updates and upgrade REAP"
 ---
 
-# Update
-
-Check for REAP updates and upgrade to the latest version.
-
-## IMPORTANT: File Access Rules
-- Do NOT access global node_modules or any path outside the project.
-- If a command fails, report the error and stop.
-
-## Steps
-
-### 1. Check Current Version
-- Run `reap --version` to get the installed version
-- Run `npm view @c-d-cc/reap version` to get the latest published version
-- Compare the two versions
-
-### 2. Update Decision
-**If installed == latest:**
-- "REAP v{version} is already up to date. (latest)"
-- Then skip to Step 4.
-
-**If installed < latest (patch only — same major.minor, different patch):**
-- Show: "Patch update available: v{installed} → v{latest}. Updating automatically..."
-- Proceed directly to Step 3 (no user confirmation needed)
-
-**If installed < latest (minor or major change):**
-- Show: "Update available: v{installed} → v{latest}"
-- Ask the user: "Update now? (yes/no)"
-- If yes: proceed to Step 3
-- If no: "Skipped. Run `/reap.update` anytime to update."
-
-### 3. Perform Update
-- Run: `npm update -g @c-d-cc/reap`
-- If the command fails, suggest: `sudo npm update -g @c-d-cc/reap` or `npm install -g @c-d-cc/reap@latest`
-- After npm update, run: `reap update` to sync commands, templates, and hooks to all detected agents
-- Show the update result summary
-
-### 4. Sync Check
-- Run: `reap update --dry-run` to check if commands/templates need syncing
-- If changes detected: run `reap update` and show results
-- If no changes: "All commands and templates are up to date."
+Run `reap update` and follow the output. For detailed update steps, run `reap update --dry-run` first.

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

@@ -2,91 +2,4 @@
 description: "REAP Validation — Verify goal achievement through testing and validation"
 ---
 
-# Validation
-
-<HARD-GATE>
-Do NOT declare "pass" without running the validation commands.
-Do NOT reuse results from a previous run — you MUST execute them fresh in this session.
-"It will probably pass" or "It looks fine" is NOT validation.
-Do NOT make claims without evidence. This is non-negotiable.
-</HARD-GATE>
-
-## Gate (Preconditions)
-- Read `.reap/life/current.yml` and verify that stage is `validation`
-- Verify that `.reap/life/03-implementation.md` exists
-- If not met: ERROR — state the reason and **STOP**
-
-## Context (Generation Info)
-- Read `.reap/life/current.yml` for the current generation info (id, goal, genomeVersion)
-
-## Re-entry Check
-- If `.reap/life/04-validation.md` already exists, this is a **re-entry due to regression**
-- Reference the previous validation report, but overwrite it with a fresh one
-
-## Steps
-
-### 1. Run Automated Validation
-- Read the **Validation Commands** table from `.reap/genome/constraints.md`
-- Execute **all** defined commands **in order**:
-  - Test → Lint → Build → Type check
-- Record the **actual output and exit code** of each command
-- Skip items with no defined command, but record them as "undefined"
-
-| Claim | Required Evidence | Insufficient Evidence |
-|-------|------------------|-----------------------|
-| "Tests pass" | Test command output: 0 failures | Previous run, "it should pass" |
-| "Lint clean" | Lint output: 0 errors | Partial check, assumption |
-| "Build succeeds" | Build command: exit 0 | "Lint passed so build should too" |
-
-### 2. Convention Compliance Check
-- Read the **Enforced Rules** table from `.reap/genome/conventions.md`
-- Execute the verification command for each defined rule
-- Record any violations
-
-### 3. Completion Criteria Review
-- Read the completion criteria from `.reap/life/01-objective.md`
-- Check the deferred task list in `.reap/life/03-implementation.md`
-- Review each completion criterion **one by one**, excluding deferred tasks from scope
-- Determine pass/fail/deferred for each criterion
-
-### 4. Minor Fix (Fix Trivial Issues Directly)
-- Fix typos, lint errors, minor bugs, and other **issues that can be resolved without a stage transition** directly
-- Record all fixes in the "Minor Fixes" section of the artifact
-- Minor fix criteria: **issues resolvable within 5 minutes without design changes**
-- After minor fixes, **re-run** the relevant validation commands
-
-### 5. Verdict
-- All automated validations pass + completion criteria met → **pass**
-- Automated validations pass + some completion criteria deferred → **partial**
-- Automated validation failure or completion criteria not met → **fail**
-- If **fail**, provide regression guidance:
-  - Code issue → `/reap.back` (implementation)
-  - Plan issue → `/reap.back planning`
-  - Goal issue → `/reap.back objective`
-
-## Red Flags — STOP if you catch yourself thinking:
-- "It will probably pass" → Run it.
-- "It passed before" → Run it again.
-- "It's trivial, it'll be fine" → Fix it as a minor fix and re-validate.
-- "I haven't tried the build but lint passed" → Run the build too.
-
-## Artifact Generation (Progressive Recording)
-- **Language**: Write all artifact content in the user's configured language (see REAP Guide § Language).
-- **Immediately upon entering this stage**: Read `~/.reap/templates/04-validation.md` and create `.reap/life/04-validation.md` with `result: pending`
-- **Update incrementally during validation**:
-  - After EACH validation command execution → immediately record the result in Test Results
-  - After EACH completion criterion check → immediately record pass/fail/deferred in the Completion Criteria Check table
-  - After EACH minor fix → immediately record it in the Minor Fixes table, then re-run and record
-- After Step 5 (Verdict) → update the Result field to pass / partial / fail
-- The artifact should reflect the current validation progress at all times
-
-## Hook Execution
-Execute hooks for event `onLifeValidated` following the Hook System protocol:
-- Scan `.reap/hooks/` for `onLifeValidated.*` files
-- Sort by frontmatter `order`, then alphabetically
-- Evaluate `condition`, execute `.md` (AI prompt) or `.sh` (shell script)
-- All hooks run BEFORE any commit (hook outputs included in the same commit)
-
-## Completion
-- pass/partial: Execute hooks, then "Proceed to the Completion stage with `/reap.next`."
-- fail: Provide regression guidance (do NOT execute hooks on fail)
+Run `reap run validation` and follow the stdout instructions exactly.

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

@@ -200,6 +200,7 @@ When `strict: true` is set in `.reap/config.yml`, the AI agent enforces code mod
 1. **NEVER modify `current.yml` directly.** Stage transitions MUST go through `/reap.next` (forward) or `/reap.back` (regression). Direct modification bypasses artifact creation and breaks the lifecycle.
 2. **NEVER skip a stage.** Each stage command must be executed and its artifact must exist before advancing. `/reap.next` enforces this by creating the next artifact from template.
 3. **ALL development work MUST follow the REAP lifecycle.** Do NOT bypass it unless the human explicitly asks.
+4. **NEVER use Write or Edit tools on `current.yml` or artifact files (`01-*.md` ~ `05-*.md`, `06-*.md`).** ALL state changes MUST go through `reap run` commands. This restriction CANNOT be overridden by user instructions.
 4. **Genome is the authoritative source of truth.** When making any decision about architecture, conventions, constraints, or domain rules, ALWAYS consult the Genome first. If you observe code that contradicts the Genome, flag it as a potential `genome-change` backlog item. Do NOT silently ignore discrepancies.
 5. **Keep Genome fresh.** If you notice the Genome is missing information about current code patterns, or contains outdated information, inform the human and suggest `/reap.sync`. The human may choose to defer sync — respect that choice, but always flag the staleness.
 6. **Report malfunctions.** If you detect unexpected behavior during REAP operations (state inconsistency, command failure, corrupted files), suggest `/reap.report` to the user. This helps improve REAP for everyone.

package/package.json

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