@c-d-cc/reap 0.9.0 → 0.9.1

package/dist/cli.js

@@ -9771,6 +9771,7 @@ var COMMAND_NAMES = [
   "reap.sync.environment",
   "reap.help",
   "reap.update",
+  "reap.report",
   "reap.merge.start",
   "reap.merge.detect",
   "reap.merge.mate",
@@ -9806,11 +9807,21 @@ async function initProject(projectRoot, projectName, entryMode, preset, onProgre
   await mkdir3(paths.backlog, { recursive: true });
   await mkdir3(paths.lineage, { recursive: true });
   log("Writing config.yml...");
+  let hasGhCli = false;
+  try {
+    const { execSync } = await import("child_process");
+    execSync("which gh", { stdio: "ignore" });
+    hasGhCli = true;
+  } catch {}
+  if (!hasGhCli) {
+    log("GitHub CLI(gh) not found. Install from https://cli.github.com for auto issue reporting.");
+  }
   const config = {
     version: "0.1.0",
     project: projectName,
     entryMode,
     autoUpdate: true,
+    autoIssueReport: hasGhCli,
     ...preset && { preset }
   };
   await ConfigManager.write(paths, config);
@@ -11059,7 +11070,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.0");
+program.name("reap").description("REAP — Recursive Evolutionary Autonomous Pipeline").version("0.9.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.report.md

@@ -0,0 +1,127 @@
+---
+description: "REAP Report — Report a bug or issue to the REAP project"
+---
+
+# Report
+
+Report a bug, malfunction, or feedback to the REAP project via GitHub Issue.
+**Language**: All user-facing messages must follow the user's configured language setting (see REAP Guide § Language).
+
+## Gate (Preconditions)
+- Check if `gh` CLI is available: `which gh`
+- If not available: inform user that GitHub CLI is required (https://cli.github.com), then `gh auth login`. **STOP**
+- Check if authenticated: `gh auth status`
+- If not authenticated: inform user to run `gh auth login`. **STOP**
+- Read `.reap/config.yml` — check `autoIssueReport` is not explicitly `false`
+- If `autoIssueReport: false`: inform user that issue reporting is disabled and how to enable it in config.yml. **STOP**
+
+## Mode Detection
+
+**Auto mode** (called by agent when malfunction detected):
+- The agent provides error context as arguments
+- Skip to Step 2 with pre-filled context
+
+**Manual mode** (user calls `/reap.report` directly):
+- Ask the user what they want to report:
+  - Bug / malfunction
+  - Feature request
+  - Other feedback
+- Gather description from the user
+
+## Steps
+
+### 1. Collect Context
+Automatically gather (do NOT ask the user for these):
+- REAP version: `reap --version`
+- Node version: `node --version`
+- OS: `uname -sr`
+- Agent: detect from environment (Claude Code, OpenCode, etc.)
+- Generation state: read `.reap/life/current.yml` (id, stage — if active)
+- Genome hash: compute from `.reap/genome/`
+- Config: read `.reap/config.yml`
+
+### 2. Draft Issue
+
+<PRIVACY_GATE>
+**BEFORE writing any issue content, apply these rules:**
+- Do NOT include: file contents, source code, environment variables, API keys,
+  tokens, passwords, usernames, email addresses, IP addresses, domain names,
+  database URLs, project-specific business logic, or any proprietary information.
+- ONLY include: REAP version, Node version, OS, generation ID, stage name,
+  command name, genome hash, generic error messages, and REAP config structure
+  (with all values masked).
+- When in doubt, OMIT the information rather than include it.
+</PRIVACY_GATE>
+
+Draft the issue using this template (issue body is always in English for the public repo):
+
+```markdown
+## {Bug Report / Feature Request / Feedback} (Auto-generated by REAP)
+
+**REAP Version**: v{version}
+**Node Version**: v{nodeVersion}
+**OS**: {os}
+**Agent**: {agentName}
+
+### Context
+- **Generation**: {genId or "none"} (stage: {stage or "n/a"})
+- **Command**: {command that triggered the issue}
+- **Genome Hash**: {genomeHash}
+
+### Description
+{user description or auto-detected malfunction description}
+
+### Expected Behavior
+{what should have happened}
+
+### Actual Behavior
+{what actually happened}
+
+### Steps to Reproduce
+1. {step}
+
+### Config
+```yaml
+version: {version}
+project: {projectName}
+strict: {on/off}
+autoUpdate: {on/off}
+# all other values masked
+```
+
+---
+*Auto-reported by REAP agent. Repository: c-d-cc/reap*
+```
+
+### 3. Post-format Sanitization
+Scan the drafted issue body and mask/remove:
+- Email patterns: `*@*.*` → `[REDACTED_EMAIL]`
+- API key/token patterns: `sk-*`, `ghp_*`, `Bearer *`, `token:*` → `[REDACTED]`
+- URLs with credentials: `https://user:pass@` → `https://[REDACTED]@`
+- Environment variable values: `KEY=value` → `KEY=[REDACTED]`
+- User paths: `/Users/{name}/` or `/home/{name}/` → `/Users/***/`
+- IP addresses: digit patterns like `\d+\.\d+\.\d+\.\d+` → `[REDACTED_IP]`
+- Source code blocks: if any project source code is included, remove it
+
+### 4. User Confirmation
+Show the sanitized issue to the user (in user's language):
+- Explain that this report greatly helps improve the REAP project
+- Ask the user to verify no sensitive information is included
+- Present the full issue body
+- Ask: yes / no / edit
+  - **yes**: proceed to Step 5
+  - **no**: report cancelled
+  - **edit**: let user modify, then re-run Step 3 sanitization and re-confirm
+
+### 5. Submit
+- Determine labels (comma-separated, always include `auto-reported`):
+  - Bug: `bug,auto-reported`
+  - Feature request: `enhancement,auto-reported`
+  - Feedback: `feedback,auto-reported`
+  - Add context labels if applicable: `lifecycle`, `genome`, `cli`
+- Run: `gh issue create --repo c-d-cc/reap --title "{title}" --label "{labels}" --body "{sanitized body}"`
+- Show the issue URL to the user
+- Thank the user for their contribution to improving REAP
+
+## Completion
+- "Issue #{number} reported: {url}"

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

@@ -21,7 +21,11 @@ description: "REAP Start — Start a new Generation"
 
 1. Ask the human for the goal of this generation (or use selected backlog item's goal)
 2. Count existing generations in `.reap/lineage/` to determine the genomeVersion
-3. Generate the next generation ID (existing count + 1, in `gen-XXX-{hash}` format where `{hash}` is a short content hash)
+3. Generate the next generation ID:
+   - Format: `gen-{NNN}-{hash}` (e.g. `gen-042-a3f8c2`)
+   - `{NNN}`: zero-padded 3-digit sequence (existing count + 1)
+   - `{hash}`: 6-character hex (0-9a-f only) — first 6 chars of `sha256(JSON.stringify({parents, goal, genomeHash, machineId, startedAt}))`
+   - Generate: `node -e "const c=require('crypto'),o=require('os');console.log(c.createHash('sha256').update(JSON.stringify({parents:[],goal:'YOUR_GOAL',genomeHash:'',machineId:o.hostname(),startedAt:new Date().toISOString()})).digest('hex').slice(0,6))"`
 4. **If a backlog item was selected in Step 0**: now mark it as `status: consumed` and add `consumedBy: gen-XXX-{hash}` (using the ID just generated)
 6. Write the following to `current.yml`:
    ```yaml

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

@@ -58,6 +58,11 @@ Objective → Planning → Implementation ⟷ Validation → Completion
 ### Generation
 A single generation. Carries one goal through the Life Cycle. State is tracked in `life/current.yml`.
 
+**Generation ID format**: `gen-{NNN}-{hash}` (e.g. `gen-042-a3f8c2`)
+- `{hash}`: 6-char hex from sha256. **MUST be real hex (0-9a-f), NEVER words/slugs.**
+- Lineage directory appends a goal slug: `gen-042-a3f8c2-fix-login-bug`
+- See `/reap.start` for generation details.
+
 ### Backlog
 All items to be carried forward to the next generation are stored in `.reap/life/backlog/`. Each item uses markdown + frontmatter format:
 - `type: genome-change` — Applied to genome during Completion (genome defects discovered mid-generation)
@@ -199,3 +204,4 @@ When `strict: true` is set in `.reap/config.yml`, the AI agent enforces code mod
 3. **ALL development work MUST follow the REAP lifecycle.** Do NOT bypass it unless the human explicitly asks.
 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.9.0",
+  "version": "0.9.1",
   "description": "Recursive Evolutionary Autonomous Pipeline — AI and humans evolve software across generations",
   "type": "module",
   "license": "MIT",