prizmkit 1.0.122 → 1.0.124

package/bundled/VERSION.json

@@ -1,5 +1,5 @@
 {
-  "frameworkVersion": "1.0.122",
-  "bundledAt": "2026-03-27T16:12:14.647Z",
-  "bundledFrom": "69c231a"
+  "frameworkVersion": "1.0.124",
+  "bundledAt": "2026-03-27T18:24:06.959Z",
+  "bundledFrom": "a7ba656"
 }

package/bundled/agents/prizm-dev-team-critic.md

@@ -0,0 +1,177 @@
+---
+name: prizm-dev-team-critic
+description: Adversarial challenger that questions plan fitness and code integration quality. Evaluates whether plans and implementations truly fit the project's existing architecture, style, and patterns. Does NOT verify correctness (that's Reviewer's job) — instead challenges strategic decisions and integration quality. Use when performing adversarial plan or code challenge.
+tools: Read, Glob, Grep, Bash
+model: inherit
+---
+
+You are the **Critic Agent**, the adversarial challenger of the PrizmKit-integrated Multi-Agent software development collaboration team.
+
+### Core Identity
+
+You are the team's "devil's advocate" — you challenge decisions, question assumptions, and find hidden risks that others miss. You do NOT verify correctness (that is Reviewer's job) and you do NOT check document consistency (that is Analyze's job). Your unique value is asking: **"Does this BELONG in this project? Is this the RIGHT approach? What are you NOT seeing?"**
+
+You operate in two modes, determined by the `MODE` field in your prompt:
+1. **Plan Challenge**: Before implementation, challenge the plan's fitness for the project
+2. **Code Challenge**: After implementation, challenge the code's integration quality
+
+### Project Context
+
+Before any challenge, you MUST understand the project:
+1. Read `.prizm-docs/root.prizm` — understand architecture, patterns, conventions
+2. Read relevant L1/L2 `.prizm-docs/` files for affected modules — understand RULES, PATTERNS, TRAPS, DECISIONS
+3. Read `context-snapshot.md` if it exists — Section 3 has Prizm Context, Section 4 has File Manifest
+
+**File Reading Rule**: Read actual project source files to compare against. Your challenges must be grounded in evidence from existing code, not theoretical concerns. If you cannot find evidence in the codebase, downgrade the severity.
+
+### Must Do (MUST)
+
+1. Read `.prizm-docs/root.prizm` and relevant module docs BEFORE writing any challenge
+2. Read existing source files in affected modules for comparison
+3. Ground every challenge in specific evidence (file paths, code patterns, existing conventions)
+4. Write `challenge-report.md` with structured findings
+5. Keep the report ≤50 lines — focus on HIGH and CRITICAL only, skip LOW
+6. Clearly state the MODE you are operating in (Plan Challenge or Code Challenge)
+
+### Never Do (NEVER)
+
+- Do not write implementation code (that is Dev's responsibility)
+- Do not verify correctness or test coverage (that is Reviewer's responsibility)
+- Do not check document consistency (that is Analyze's responsibility)
+- Do not decompose tasks (that is the Orchestrator's responsibility)
+- **Do not execute any git operations** (git commit / git add / git reset / git push are all prohibited)
+- Do not modify source files — write only `challenge-report.md`, `challenge-report-A.md`, `challenge-report-B.md`, or `challenge-report-C.md`
+- Do not raise theoretical concerns without evidence from the codebase
+
+### Behavioral Rules
+
+```
+CRIT-01: Always read .prizm-docs/ and existing source before challenging
+CRIT-02: Every challenge must reference a specific file path or code pattern as evidence
+CRIT-03: Maximum 10 challenges per report (focus on highest impact)
+CRIT-04: Severity levels: CRITICAL (architecture mismatch), HIGH (style/robustness gap), MEDIUM (minor inconsistency)
+CRIT-05: If no significant challenges found, write "No significant challenges — plan/code fits the project well" and exit
+CRIT-06: Do NOT re-raise issues already covered by Analyze (document consistency) or Reviewer (correctness)
+CRIT-07: Read comparable existing code in the same module for style baseline before flagging style issues
+CRIT-08: When challenging a decision, always suggest a concrete alternative
+CRIT-09: Do not use the timeout command (incompatible with macOS). Run commands directly without a timeout prefix
+CRIT-10: In voting mode, write to your assigned report file (challenge-report-{A,B,C}.md) — do NOT read other critics' reports
+```
+
+---
+
+## Mode 1: Plan Challenge
+
+**Precondition**: Orchestrator has completed plan.md (with Tasks section). Analyze has passed (CP-2).
+
+**Goal**: Challenge whether the plan fits the project — not whether the plan is internally consistent (that was Analyze's job).
+
+### Challenge Dimensions
+
+| Dimension | What to Challenge | Evidence Source |
+|-----------|------------------|----------------|
+| **Architecture Fit** | Does the plan's approach match the project's existing architectural patterns? Would it feel foreign to someone familiar with the codebase? | `.prizm-docs/` PATTERNS, existing module structure |
+| **Integration Planning** | Do proposed interfaces match existing conventions? Are naming patterns consistent with existing code? | Existing source files in the same module/layer |
+| **Alternative Approaches** | Given the project's tech stack and existing patterns, is there a more natural approach that leverages what's already built? | `.prizm-docs/` KEY_FILES, existing utilities/helpers |
+| **Coupling Risk** | Does the task breakdown hide cross-module dependencies? Will changes bleed into areas the plan doesn't mention? | `.prizm-docs/` DEPENDENCIES, import graphs |
+
+### Workflow
+
+1. Read `context-snapshot.md` — understand the feature and file manifest
+2. Read `.prizm-docs/root.prizm` and affected L1/L2 docs
+3. Read existing source files in modules the plan touches
+4. For each dimension, compare plan decisions against evidence from existing code
+5. Write `challenge-report.md` to `.prizmkit/specs/<feature-slug>/`
+
+---
+
+## Mode 2: Code Challenge
+
+**Precondition**: Dev has completed implementation. All tasks `[x]`, tests pass. Implementation Log exists in `context-snapshot.md`.
+
+**Goal**: Challenge whether the implemented code integrates well with the existing project — not whether it's correct (that's Reviewer's job).
+
+### Challenge Dimensions
+
+| Dimension | What to Challenge | Evidence Source |
+|-----------|------------------|----------------|
+| **Style Consistency** | Do naming conventions, code structure, and patterns match existing code in the same module? | Read existing files in the same directory/module |
+| **Robustness** | Are edge cases handled? Error paths? Data validation? What happens with unexpected input not covered by the spec? | Read the new code, compare error handling patterns with existing code |
+| **Integration Cohesion** | Does the new code interact naturally with existing code? Are abstractions consistent? Are import patterns standard? | Read call sites, compare with existing integrations |
+| **Hidden Impact** | Could the new code have side effects on existing functionality? Shared state, global config, database constraints, event handlers? | Read shared modules, config files, database schemas |
+
+### Workflow
+
+1. Read `context-snapshot.md` — Implementation Log section for what changed
+2. Read `.prizm-docs/root.prizm` and affected module docs (RULES, PATTERNS)
+3. Read the actual source files changed (from Implementation Log)
+4. Read comparable existing files in the same module for style baseline
+5. For each dimension, compare new code against existing code patterns
+6. Write `challenge-report.md` to `.prizmkit/specs/<feature-slug>/` (overwrite any existing report)
+
+---
+
+## Output Format
+
+Write `challenge-report.md` (or `challenge-report-{A,B,C}.md` in voting mode):
+
+```markdown
+## Challenge Report — [Plan Challenge | Code Challenge]
+Feature: <FEATURE_ID> — <FEATURE_TITLE>
+Mode: [Plan Challenge | Code Challenge]
+Challenges Found: N (X critical, Y high, Z medium)
+
+### CHALLENGE-1: [CRITICAL] Title
+- **Observation**: What was found (with file:line or pattern reference)
+- **Risk**: What could go wrong if this is not addressed
+- **Suggestion**: Concrete alternative or fix approach
+
+### CHALLENGE-2: [HIGH] Title
+- **Observation**: ...
+- **Risk**: ...
+- **Suggestion**: ...
+
+### Summary
+[1-2 sentence overall assessment of project fitness]
+```
+
+**Severity Criteria**:
+- **CRITICAL**: Architecture mismatch — the approach conflicts with established project patterns and would require significant rework later
+- **HIGH**: Style/robustness gap — the code works but doesn't fit the project's conventions or misses important edge cases
+- **MEDIUM**: Minor inconsistency — small deviations that could be improved but aren't urgent
+
+---
+
+## Voting Protocol (3-Critic Mode)
+
+When spawned as one of 3 parallel critics (Critic-A, Critic-B, Critic-C):
+
+1. Each critic is assigned a **focus lens** in the prompt:
+   - **Critic-A**: Architecture & scalability lens
+   - **Critic-B**: Data model & edge cases lens
+   - **Critic-C**: Security & performance lens
+
+2. Write to your assigned file: `challenge-report-A.md`, `challenge-report-B.md`, or `challenge-report-C.md`
+
+3. Do NOT read other critics' reports — independence is the point
+
+4. The Orchestrator will read all 3 reports and apply consensus rules:
+   - Challenge raised by **2/3 or more** critics → **must respond** (fix or justify)
+   - Challenge raised by **1/3 only** → **logged but not blocking**
+
+---
+
+## Exception Handling
+
+| Scenario | Strategy |
+|----------|----------|
+| No `.prizm-docs/` exists (new project) | Skip architecture comparison, focus on internal consistency and robustness only |
+| Module has no existing code to compare | Note in report: "No baseline for style comparison — challenges are based on general best practices" |
+| All challenges are MEDIUM or lower | Write report with "No significant challenges" summary. Do NOT inflate severity |
+| Cannot determine project conventions | Downgrade all style challenges to MEDIUM. Note the limitation in the report |
+
+### Communication Rules
+
+Critic does not communicate directly with Dev or Reviewer. All findings go to the Orchestrator via the challenge-report file.
+- Send COMPLETION_SIGNAL (with challenge count summary) to indicate completion
+- Receive TASK_ASSIGNMENT to get assigned work

package/bundled/dev-pipeline/README.md

@@ -159,7 +159,7 @@ Manages `run.sh` as a background daemon process with PID tracking and log consol
 | `logs` | View pipeline logs. `--follow` for live tail, `--lines N` for last N lines |
 | `restart` | Stop + start |
 
-**`--mode` options:** `lite`, `standard`, `full`, `self-evolve`
+**`--mode` options:** `lite`, `standard`, `full`
 
 **`--env` format:** Pass environment variables as a quoted string:
 
@@ -308,7 +308,7 @@ python3 scripts/generate-bootstrap-prompt.py \
   --output <path> \
   [--state-dir <path>] \
   [--template <path>] \
-  [--mode lite|standard|full|self-evolve]
+  [--mode lite|standard|full]
 ```
 
 **Template auto-selection by complexity:**
@@ -318,7 +318,6 @@ python3 scripts/generate-bootstrap-prompt.py \
 | `low` | lite | `bootstrap-tier1.md` (single agent) |
 | `medium` | standard | `bootstrap-tier2.md` (dual agent) |
 | `high` / `critical` | full | `bootstrap-tier3.md` (full team) |
-| (override) | self-evolve | `bootstrap-tier3.md` + framework guardrails |
 
 **Output (JSON to stdout):**
 
@@ -331,7 +330,8 @@ The `model` field is extracted from the feature's `"model"` field in feature-lis
 **Conditional blocks resolved:**
 - `{{IF_RESUME}}` / `{{IF_FRESH_START}}` — Resume vs fresh start
 - `{{IF_INIT_NEEDED}}` / `{{IF_INIT_DONE}}` — PrizmKit init status
-- `{{IF_MODE_LITE}}` / `{{IF_MODE_STANDARD}}` / `{{IF_MODE_FULL}}` / `{{IF_MODE_SELF_EVOLVE}}` — Pipeline mode blocks
+- `{{IF_MODE_LITE}}` / `{{IF_MODE_STANDARD}}` / `{{IF_MODE_FULL}}` — Pipeline mode blocks
+- `{{IF_CRITIC_ENABLED}}` / `{{END_IF_CRITIC_ENABLED}}` — Critic agent blocks (adversarial review)
 
 ---
 
@@ -570,7 +570,8 @@ Also exports: `log_info`, `log_warn`, `log_error`, `log_success` (with timestamp
 |----------|---------|---------|-------------|
 | `MAX_RETRIES` | `3` | run.sh | Max retry attempts per feature before marking as failed |
 | `SESSION_TIMEOUT` | `0` (none) | run.sh, retry-feature.sh, run-bugfix.sh, retry-bug.sh | Timeout in seconds per AI CLI session. 0 = no timeout |
-| `PIPELINE_MODE` | (auto) | run.sh, launch-daemon.sh | Override mode for all features: `lite\|standard\|full\|self-evolve` |
+| `PIPELINE_MODE` | (auto) | run.sh, launch-daemon.sh | Override mode for all features: `lite\|standard\|full` |
+| `ENABLE_CRITIC` | `false` | run.sh, launch-daemon.sh | Enable adversarial critic review: `true\|false` |
 | `DEV_BRANCH` | auto-generated | run.sh | Custom git branch name (default: `dev/{feature-id}-{timestamp}`) |
 | `AUTO_PUSH` | `0` | run.sh | Set to `1` to auto-push branch to remote after successful session |
 
@@ -920,7 +921,7 @@ dev-pipeline/
 +-- templates/
 |   +-- bootstrap-tier1.md           # Tier 1 prompt template (single agent, lite)
 |   +-- bootstrap-tier2.md           # Tier 2 prompt template (dual agent, standard)
-|   +-- bootstrap-tier3.md           # Tier 3 prompt template (full team, full/self-evolve)
+|   +-- bootstrap-tier3.md           # Tier 3 prompt template (full team, full)
 |   +-- bootstrap-prompt.md          # Legacy monolithic template (fallback)
 |   +-- bugfix-bootstrap-prompt.md   # Bug-fix session prompt template
 |   +-- feature-list-schema.json     # JSON schema for feature-list.json

package/bundled/dev-pipeline/assets/prizm-dev-team-integration.md

@@ -29,8 +29,9 @@ dev-pipeline (outer loop)
 
 | Agent | Definition Path | Type |
 |-------|----------------|------|
-| Dev | `core/agents/prizm-dev-team-dev.md` | prizm-dev-team-dev |
-| Reviewer | `core/agents/prizm-dev-team-reviewer.md` | prizm-dev-team-reviewer |
+| Dev | `.claude/agents/prizm-dev-team-dev.md` (or `.codebuddy/agents/`) | prizm-dev-team-dev |
+| Reviewer | `.claude/agents/prizm-dev-team-reviewer.md` (or `.codebuddy/agents/`) | prizm-dev-team-reviewer |
+| Critic | `.claude/agents/prizm-dev-team-critic.md` (or `.codebuddy/agents/`) | prizm-dev-team-critic |
 
 Note: The Orchestrator role is handled by the main agent (session orchestrator) directly — no separate agent definition needed.
 

package/bundled/dev-pipeline/launch-daemon.sh

@@ -94,6 +94,7 @@ cmd_start() {
     local env_overrides=""
     local mode_override=""
     local features_filter=""
+    local critic_enabled=""
 
     # Parse arguments
     while [[ $# -gt 0 ]]; do
@@ -110,15 +111,15 @@ cmd_start() {
             --mode)
                 shift
                 if [[ $# -eq 0 ]]; then
-                    log_error "--mode requires a value (lite|standard|full|self-evolve)"
+                    log_error "--mode requires a value (lite|standard|full)"
                     exit 1
                 fi
                 case "$1" in
-                    lite|standard|full|self-evolve)
+                    lite|standard|full)
                         mode_override="$1"
                         ;;
                     *)
-                        log_error "Invalid mode: $1 (must be lite, standard, full, or self-evolve)"
+                        log_error "Invalid mode: $1 (must be lite, standard, or full)"
                         exit 1
                         ;;
                 esac
@@ -133,6 +134,14 @@ cmd_start() {
                 features_filter="$1"
                 shift
                 ;;
+            --critic)
+                critic_enabled="true"
+                shift
+                ;;
+            --no-critic)
+                critic_enabled="false"
+                shift
+                ;;
             *)
                 feature_list="$1"
                 shift
@@ -187,6 +196,9 @@ cmd_start() {
     if [[ -n "$mode_override" ]]; then
         env_parts="${env_parts:+$env_parts }PIPELINE_MODE=$mode_override"
     fi
+    if [[ -n "${critic_enabled:-}" ]]; then
+        env_parts="${env_parts:+$env_parts }ENABLE_CRITIC=$critic_enabled"
+    fi
     if [[ -n "$env_parts" ]]; then
         env_cmd="env $env_parts"
     fi
@@ -578,7 +590,9 @@ Commands:
   help                                            Show this help
 
 Options:
-  --mode <lite|standard|full|self-evolve>   Override pipeline mode for all features
+  --mode <lite|standard|full>              Override pipeline mode for all features
+  --critic                                 Enable adversarial critic review for all features
+  --no-critic                              Disable critic review (overrides feature-list setting)
   --features <filter>                       Run only specified features (e.g. F-001,F-003 or F-001:F-010)
   --env "KEY=VAL ..."                        Set environment variables
 
@@ -587,9 +601,10 @@ Examples:
   ./launch-daemon.sh start my-features.json       # Start with custom feature list
   ./launch-daemon.sh start --features F-001:F-005  # Run only features F-001 through F-005
   ./launch-daemon.sh start --features F-001,F-003,F-007  # Run specific features
-  ./launch-daemon.sh start --mode self-evolve     # Self-evolve mode (framework development)
+  ./launch-daemon.sh start --mode full              # Full mode for complex features
+  ./launch-daemon.sh start --critic                  # Enable adversarial critic review
   ./launch-daemon.sh start --env "MAX_RETRIES=5 SESSION_TIMEOUT=7200"
-  ./launch-daemon.sh start feature-list.json --mode self-evolve --env "VERBOSE=1"
+  ./launch-daemon.sh start feature-list.json --mode full --critic --env "VERBOSE=1"
   ./launch-daemon.sh status                       # Check if running (JSON on stdout)
   ./launch-daemon.sh logs --follow                # Live log tailing
   ./launch-daemon.sh logs --lines 100             # Last 100 lines

package/bundled/dev-pipeline/retry-feature.sh

@@ -183,15 +183,25 @@ mkdir -p "$SESSION_DIR/logs"
 BOOTSTRAP_PROMPT="$SESSION_DIR/bootstrap-prompt.md"
 
 log_info "Generating bootstrap prompt..."
-GEN_OUTPUT=$(python3 "$SCRIPTS_DIR/generate-bootstrap-prompt.py" \
-    --feature-list "$FEATURE_LIST" \
-    --feature-id "$FEATURE_ID" \
-    --session-id "$SESSION_ID" \
-    --run-id "$RUN_ID" \
-    --retry-count 0 \
-    --resume-phase "null" \
-    --state-dir "$STATE_DIR" \
-    --output "$BOOTSTRAP_PROMPT" 2>/dev/null) || {
+GEN_ARGS=(
+    --feature-list "$FEATURE_LIST"
+    --feature-id "$FEATURE_ID"
+    --session-id "$SESSION_ID"
+    --run-id "$RUN_ID"
+    --retry-count 0
+    --resume-phase "null"
+    --state-dir "$STATE_DIR"
+    --output "$BOOTSTRAP_PROMPT"
+)
+
+# Support ENABLE_CRITIC env var
+if [[ "${ENABLE_CRITIC:-}" == "true" || "${ENABLE_CRITIC:-}" == "1" ]]; then
+    GEN_ARGS+=(--critic "true")
+elif [[ "${ENABLE_CRITIC:-}" == "false" || "${ENABLE_CRITIC:-}" == "0" ]]; then
+    GEN_ARGS+=(--critic "false")
+fi
+
+GEN_OUTPUT=$(python3 "$SCRIPTS_DIR/generate-bootstrap-prompt.py" "${GEN_ARGS[@]}" 2>/dev/null) || {
     log_error "Failed to generate bootstrap prompt"
     exit 1
 }

package/bundled/dev-pipeline/run.sh

@@ -27,7 +27,7 @@ set -euo pipefail
 #   LOG_CLEANUP_ENABLED   Run periodic log cleanup (default: 1)
 #   LOG_RETENTION_DAYS    Delete logs older than N days (default: 14)
 #   LOG_MAX_TOTAL_MB      Keep total logs under N MB via oldest-first cleanup (default: 1024)
-#   PIPELINE_MODE         Override mode for all features: lite|standard|full|self-evolve (used by daemon)
+#   PIPELINE_MODE         Override mode for all features: lite|standard|full (used by daemon)
 #   DEV_BRANCH            Custom dev branch name (default: auto-generated dev/{feature_id}-YYYYMMDDHHmm)
 #   AUTO_PUSH             Auto-push to remote after successful feature (default: 0). Set to 1 to enable.
 # ============================================================
@@ -393,6 +393,7 @@ run_one() {
     local dry_run=false
     local resume_phase=""
     local mode_override=""
+    local critic_override=""
     local do_clean=false
     local no_reset=false
 
@@ -419,11 +420,11 @@ run_one() {
                     exit 1
                 fi
                 case "$1" in
-                    lite|standard|full|self-evolve)
+                    lite|standard|full)
                         mode_override="$1"
                         ;;
                     *)
-                        log_error "Invalid mode: $1 (must be lite, standard, full, or self-evolve)"
+                        log_error "Invalid mode: $1 (must be lite, standard, or full)"
                         exit 1
                         ;;
                 esac
@@ -437,6 +438,14 @@ run_one() {
                 no_reset=true
                 shift
                 ;;
+            --critic)
+                critic_override="true"
+                shift
+                ;;
+            --no-critic)
+                critic_override="false"
+                shift
+                ;;
             --timeout)
                 shift
                 if [[ $# -eq 0 ]]; then
@@ -513,14 +522,6 @@ run_one() {
         log_success "Pipeline initialized with $features_count features"
     fi
 
-    # Auto-detect framework repo: if scripts/bundle.js exists, enable self-evolve mode
-    local project_root
-    project_root=$(git -C "$SCRIPT_DIR" rev-parse --show-toplevel 2>/dev/null || echo "")
-    if [[ -z "$mode_override" && -n "$project_root" && -f "$project_root/scripts/bundle.js" ]]; then
-        log_info "Detected PrizmKit framework repo — auto-enabling self-evolve mode"
-        mode_override="self-evolve"
-    fi
-
     # Verify feature exists
     local feature_title
     feature_title=$(python3 -c "
@@ -629,6 +630,14 @@ sys.exit(1)
         prompt_args+=(--mode "$mode_override")
     fi
 
+    if [[ -n "${critic_override:-}" ]]; then
+        prompt_args+=(--critic "$critic_override")
+    elif [[ "${ENABLE_CRITIC:-}" == "true" || "${ENABLE_CRITIC:-}" == "1" ]]; then
+        prompt_args+=(--critic "true")
+    elif [[ "${ENABLE_CRITIC:-}" == "false" || "${ENABLE_CRITIC:-}" == "0" ]]; then
+        prompt_args+=(--critic "false")
+    fi
+
     log_info "Generating bootstrap prompt..."
     local gen_output
     gen_output=$(python3 "$SCRIPTS_DIR/generate-bootstrap-prompt.py" "${prompt_args[@]}" 2>/dev/null) || {
@@ -752,37 +761,6 @@ sys.exit(1)
 
     echo ""
     if [[ "$session_status" == "success" ]]; then
-        # Self-evolve mode: run framework validation after successful session
-        if [[ "$mode_override" == "self-evolve" ]]; then
-            log_info "Self-evolve mode: running framework validation..."
-            if bash "$SCRIPTS_DIR/validate-framework.sh" 2>&1; then
-                log_success "Framework validation passed"
-            else
-                log_warn "Framework validation failed — review issues above"
-                session_status="framework_validation_failed"
-            fi
-
-            # Check for reload_needed marker in session status
-            local session_status_file="$session_dir/session-status.json"
-            if [[ -f "$session_status_file" ]]; then
-                local reload_needed
-                reload_needed=$(python3 -c "
-import json, sys
-with open(sys.argv[1]) as f:
-    data = json.load(f)
-print(data.get('reload_needed', False))
-" "$session_status_file" 2>/dev/null || echo "False")
-                if [[ "$reload_needed" == "True" ]]; then
-                    echo ""
-                    log_warn "╔══════════════════════════════════════════════════════════════╗"
-                    log_warn "║  RELOAD NEEDED: This session modified pipeline skills or     ║"
-                    log_warn "║  templates that are used by the dev-pipeline itself.          ║"
-                    log_warn "║  Changes will take effect in the NEXT session.                ║"
-                    log_warn "╚══════════════════════════════════════════════════════════════╝"
-                fi
-            fi
-        fi
-
         log_success "════════════════════════════════════════════════════"
         log_success "  $feature_id completed successfully!"
         log_success "════════════════════════════════════════════════════"
@@ -991,16 +969,11 @@ for f in data.get('stuck_features', []):
             main_prompt_args+=(--mode "$PIPELINE_MODE")
         fi
 
-        # Auto-detect framework repo: if scripts/bundle.js exists, enable self-evolve mode
-        if [[ -z "${PIPELINE_MODE:-}" ]]; then
-            local _project_root
-            _project_root=$(git -C "$SCRIPT_DIR" rev-parse --show-toplevel 2>/dev/null || echo "")
-            if [[ -n "$_project_root" && -f "$_project_root/scripts/bundle.js" ]]; then
-                if [[ $session_count -eq 0 ]]; then
-                    log_info "Detected PrizmKit framework repo — auto-enabling self-evolve mode"
-                fi
-                main_prompt_args+=(--mode "self-evolve")
-            fi
+        # Support ENABLE_CRITIC env var (set by launch-daemon.sh --critic)
+        if [[ "${ENABLE_CRITIC:-}" == "true" || "${ENABLE_CRITIC:-}" == "1" ]]; then
+            main_prompt_args+=(--critic "true")
+        elif [[ "${ENABLE_CRITIC:-}" == "false" || "${ENABLE_CRITIC:-}" == "0" ]]; then
+            main_prompt_args+=(--critic "false")
         fi
 
         local gen_output
@@ -1102,7 +1075,9 @@ show_help() {
     echo "Single Feature Options (run <feature-id>):"
     echo "  --dry-run                   Generate bootstrap prompt only, don't spawn session"
     echo "  --resume-phase N            Override resume phase (default: auto-detect)"
-    echo "  --mode <lite|standard|full|self-evolve> Override pipeline mode (bypasses estimated_complexity)"
+    echo "  --mode <lite|standard|full> Override pipeline mode (bypasses estimated_complexity)"
+    echo "  --critic                    Enable adversarial critic review for this feature"
+    echo "  --no-critic                 Disable critic review (overrides feature-list setting)"
     echo "  --clean                     Delete artifacts and reset before running"
     echo "  --no-reset                  Skip feature status reset step"
     echo "  --timeout N                 Session timeout in seconds (default: 0 = no limit)"
@@ -1117,7 +1092,8 @@ show_help() {
     echo "  LOG_CLEANUP_ENABLED   Run log cleanup before execution (default: 1)"
     echo "  LOG_RETENTION_DAYS    Delete logs older than N days (default: 14)"
     echo "  LOG_MAX_TOTAL_MB      Keep total logs under N MB (default: 1024)"
-    echo "  PIPELINE_MODE         Override mode for all features: lite|standard|full|self-evolve"
+    echo "  PIPELINE_MODE         Override mode for all features: lite|standard|full"
+    echo "  ENABLE_CRITIC         Enable critic review for all features: true|false"
     echo ""
     echo "Examples:"
     echo "  ./run.sh run                                         # Run all features"