prizmkit 1.1.39 → 1.1.40

package/bundled/VERSION.json

@@ -1,5 +1,5 @@
 {
-  "frameworkVersion": "1.1.39",
-  "bundledAt": "2026-04-19T14:24:30.167Z",
-  "bundledFrom": "5d52f7f"
+  "frameworkVersion": "1.1.40",
+  "bundledAt": "2026-04-20T14:02:15.471Z",
+  "bundledFrom": "a703bde"
 }

package/bundled/dev-pipeline/scripts/generate-bugfix-prompt.py

@@ -260,6 +260,39 @@ def build_replacements(args, bug, global_context, script_dir):
     # Determine verification type
     vtype = bug.get("verification_type", "automated")
 
+    # Browser interaction - extract from bug if present
+    browser_interaction = bug.get("browser_interaction")
+    browser_enabled = False
+    browser_verify_steps = ""
+    browser_tool = "auto"
+
+    # Environment override
+    browser_verify_env = os.environ.get("BROWSER_VERIFY", "").lower()
+    if browser_verify_env == "false":
+        browser_interaction = None
+
+    # Extract browser config (same logic as feature pipeline)
+    if browser_interaction and isinstance(browser_interaction, bool):
+        browser_enabled = True
+        browser_tool = "auto"
+        browser_verify_steps = "   # (no specific verify goals — reproduce the bug and verify it's fixed)"
+    elif browser_interaction and isinstance(browser_interaction, dict):
+        browser_tool = browser_interaction.get("tool", "auto")
+        if browser_tool not in ("playwright-cli", "opencli", "auto"):
+            LOGGER.warning("Unknown browser_interaction.tool '%s', defaulting to 'auto'", browser_tool)
+            browser_tool = "auto"
+
+        steps = browser_interaction.get("verify_steps", [])
+        if steps:
+            browser_enabled = True
+            browser_verify_steps = "\n".join(
+                "   # Step {}: {}".format(i + 1, step)
+                for i, step in enumerate(steps)
+            )
+        elif browser_interaction.get("url") or browser_interaction.get("enabled", True):
+            browser_enabled = True
+            browser_verify_steps = "   # (reproduce bug and verify fix)"
+
     replacements = {
         "{{RUN_ID}}": args.run_id,
         "{{SESSION_ID}}": args.session_id,
@@ -284,13 +317,17 @@ def build_replacements(args, bug, global_context, script_dir):
         "{{PROJECT_ROOT}}": project_root,
         "{{FIX_SCOPE}}": fix_scope,
         "{{TIMESTAMP}}": "",  # Placeholder, agent fills in the timestamp
+        "{{BROWSER_ENABLED}}": "true" if browser_enabled else "false",
+        "{{BROWSER_TOOL}}": browser_tool,
+        "{{BROWSER_VERIFY_STEPS}}": browser_verify_steps,
     }
 
     return replacements
 
 
 def process_conditional_blocks(content, bug):
-    """Handle conditional blocks based on verification_type."""
+    """Handle conditional blocks based on verification_type and browser_interaction."""
+    # Handle verification type blocks
     vtype = bug.get("verification_type", "automated")
     is_manual_or_hybrid = vtype in ("manual", "hybrid")
 
@@ -306,6 +343,64 @@ def process_conditional_blocks(content, bug):
             "", content, flags=re.DOTALL,
         )
 
+    # Handle browser interaction blocks
+    browser_interaction = bug.get("browser_interaction")
+    browser_enabled = False
+    browser_tool = "auto"
+
+    # Check environment override
+    browser_verify_env = os.environ.get("BROWSER_VERIFY", "").lower()
+    if browser_verify_env == "false":
+        browser_interaction = None
+
+    # Determine if browser is enabled
+    if browser_interaction:
+        if isinstance(browser_interaction, bool):
+            browser_enabled = True
+        elif isinstance(browser_interaction, dict):
+            steps = browser_interaction.get("verify_steps", [])
+            if steps or browser_interaction.get("url") or browser_interaction.get("enabled", True):
+                browser_enabled = True
+            browser_tool = browser_interaction.get("tool", "auto")
+
+    # Process browser interaction blocks
+    browser_open = "{{IF_BROWSER_INTERACTION}}"
+    browser_close = "{{END_IF_BROWSER_INTERACTION}}"
+
+    if browser_enabled:
+        # Keep content, remove tags
+        content = content.replace(browser_open + "\n", "")
+        content = content.replace(browser_open, "")
+        content = content.replace(browser_close + "\n", "")
+        content = content.replace(browser_close, "")
+    else:
+        # Remove entire block
+        pattern = re.escape(browser_open) + r".*?" + re.escape(browser_close) + r"\n?"
+        content = re.sub(pattern, "", content, flags=re.DOTALL)
+
+    # Process browser tool selection blocks (nested inside browser interaction)
+    tool_variants = ["PLAYWRIGHT", "OPENCLI", "AUTO"]
+    active_variant = {
+        "playwright-cli": "PLAYWRIGHT",
+        "opencli": "OPENCLI",
+        "auto": "AUTO",
+    }.get(browser_tool, "AUTO")
+
+    for variant in tool_variants:
+        tool_open = "{{{{IF_BROWSER_TOOL_{}}}}}".format(variant)
+        tool_close = "{{{{END_IF_BROWSER_TOOL_{}}}}}".format(variant)
+
+        if variant == active_variant and browser_enabled:
+            # Keep content, remove tags
+            content = content.replace(tool_open + "\n", "")
+            content = content.replace(tool_open, "")
+            content = content.replace(tool_close + "\n", "")
+            content = content.replace(tool_close, "")
+        else:
+            # Remove entire block
+            pat = re.escape(tool_open) + r".*?" + re.escape(tool_close) + r"\n?"
+            content = re.sub(pat, "", content, flags=re.DOTALL)
+
     return content
 
 
@@ -529,6 +624,26 @@ def main():
 
     # Success
     bug_model = bug.get("model", "")
+    # Extract browser interaction state for output
+    browser_interaction = bug.get("browser_interaction")
+    browser_enabled = False
+    browser_tool = "auto"
+
+    browser_verify_env = os.environ.get("BROWSER_VERIFY", "").lower()
+    if browser_verify_env == "false":
+        browser_interaction = None
+
+    if browser_interaction:
+        if isinstance(browser_interaction, bool):
+            browser_enabled = True
+        elif isinstance(browser_interaction, dict):
+            steps = browser_interaction.get("verify_steps", [])
+            if steps or browser_interaction.get("url") or browser_interaction.get("enabled", True):
+                browser_enabled = True
+            browser_tool = browser_interaction.get("tool", "auto")
+            if browser_tool not in ("playwright-cli", "opencli", "auto"):
+                browser_tool = "auto"
+
     output = {
         "success": True,
         "output_path": os.path.abspath(args.output),
@@ -537,6 +652,8 @@ def main():
         "pipeline_mode": pipeline_mode,
         "agent_count": agent_count,
         "critic_enabled": critic_enabled,
+        "browser_enabled": browser_enabled,
+        "browser_tool": browser_tool
     }
     print(json.dumps(output, indent=2, ensure_ascii=False))
     sys.exit(0)

package/bundled/dev-pipeline/scripts/generate-refactor-prompt.py

@@ -420,6 +420,39 @@ def build_replacements(args, refactor, refactors, global_context, script_dir):
     else:
         new_tests_str = "- (none specified)"
 
+    # Browser interaction - extract from refactor if present
+    browser_interaction = refactor.get("browser_interaction")
+    browser_enabled = False
+    browser_verify_steps = ""
+    browser_tool = "auto"
+
+    # Environment override
+    browser_verify_env = os.environ.get("BROWSER_VERIFY", "").lower()
+    if browser_verify_env == "false":
+        browser_interaction = None
+
+    # Extract browser config (same logic as feature and bugfix pipelines)
+    if browser_interaction and isinstance(browser_interaction, bool):
+        browser_enabled = True
+        browser_tool = "auto"
+        browser_verify_steps = "   # (no specific verify goals — validate UI renders correctly and feature still works)"
+    elif browser_interaction and isinstance(browser_interaction, dict):
+        browser_tool = browser_interaction.get("tool", "auto")
+        if browser_tool not in ("playwright-cli", "opencli", "auto"):
+            LOGGER.warning("Unknown browser_interaction.tool '%s', defaulting to 'auto'", browser_tool)
+            browser_tool = "auto"
+
+        steps = browser_interaction.get("verify_steps", [])
+        if steps:
+            browser_enabled = True
+            browser_verify_steps = "\n".join(
+                "   # Step {}: {}".format(i + 1, step)
+                for i, step in enumerate(steps)
+            )
+        elif browser_interaction.get("url") or browser_interaction.get("enabled", True):
+            browser_enabled = True
+            browser_verify_steps = "   # (validate UI renders correctly and feature still works)"
+
     replacements = {
         "{{RUN_ID}}": args.run_id,
         "{{SESSION_ID}}": args.session_id,
@@ -452,16 +485,17 @@ def build_replacements(args, refactor, refactors, global_context, script_dir):
         ),
         "{{TIMESTAMP}}": "",  # Placeholder — agent fills in timestamp
         "{{PLATFORM_CONVENTIONS}}": read_platform_conventions(project_root),
+        "{{BROWSER_ENABLED}}": "true" if browser_enabled else "false",
+        "{{BROWSER_TOOL}}": browser_tool,
+        "{{BROWSER_VERIFY_STEPS}}": browser_verify_steps,
     }
 
     return replacements
 
 
-def process_conditional_blocks(content, resume_phase):
-    """Handle conditional blocks based on resume_phase.
-
-    - {{IF_FRESH_START}}...{{END_IF_FRESH_START}} — include only on fresh start (resume_phase == "null")
-    """
+def process_conditional_blocks(content, resume_phase, refactor):
+    """Handle conditional blocks based on resume_phase and browser_interaction."""
+    # Handle fresh start blocks
     is_resume = resume_phase != "null"
 
     if is_resume:
@@ -475,13 +509,72 @@ def process_conditional_blocks(content, resume_phase):
         content = content.replace("{{END_IF_FRESH_START}}\n", "")
         content = content.replace("{{END_IF_FRESH_START}}", "")
 
+    # Handle browser interaction blocks
+    browser_interaction = refactor.get("browser_interaction")
+    browser_enabled = False
+    browser_tool = "auto"
+
+    # Check environment override
+    browser_verify_env = os.environ.get("BROWSER_VERIFY", "").lower()
+    if browser_verify_env == "false":
+        browser_interaction = None
+
+    # Determine if browser is enabled
+    if browser_interaction:
+        if isinstance(browser_interaction, bool):
+            browser_enabled = True
+        elif isinstance(browser_interaction, dict):
+            steps = browser_interaction.get("verify_steps", [])
+            if steps or browser_interaction.get("url") or browser_interaction.get("enabled", True):
+                browser_enabled = True
+            browser_tool = browser_interaction.get("tool", "auto")
+
+    # Process browser interaction blocks
+    browser_open = "{{IF_BROWSER_INTERACTION}}"
+    browser_close = "{{END_IF_BROWSER_INTERACTION}}"
+
+    if browser_enabled:
+        # Keep content, remove tags
+        content = content.replace(browser_open + "\n", "")
+        content = content.replace(browser_open, "")
+        content = content.replace(browser_close + "\n", "")
+        content = content.replace(browser_close, "")
+    else:
+        # Remove entire block
+        pattern = re.escape(browser_open) + r".*?" + re.escape(browser_close) + r"\n?"
+        content = re.sub(pattern, "", content, flags=re.DOTALL)
+
+    # Process browser tool selection blocks (nested inside browser interaction)
+    tool_variants = ["PLAYWRIGHT", "OPENCLI", "AUTO"]
+    active_variant = {
+        "playwright-cli": "PLAYWRIGHT",
+        "opencli": "OPENCLI",
+        "auto": "AUTO",
+    }.get(browser_tool, "AUTO")
+
+    for variant in tool_variants:
+        tool_open = "{{{{IF_BROWSER_TOOL_{}}}}}".format(variant)
+        tool_close = "{{{{END_IF_BROWSER_TOOL_{}}}}}".format(variant)
+
+        if variant == active_variant and browser_enabled:
+            # Keep content, remove tags
+            content = content.replace(tool_open + "\n", "")
+            content = content.replace(tool_open, "")
+            content = content.replace(tool_close + "\n", "")
+            content = content.replace(tool_close, "")
+        else:
+            # Remove entire block
+            pat = re.escape(tool_open) + r".*?" + re.escape(tool_close) + r"\n?"
+            content = re.sub(pat, "", content, flags=re.DOTALL)
+
     return content
 
 
-def render_template(template_content, replacements, resume_phase):
+
+def render_template(template_content, replacements, resume_phase, refactor):
     """Render the template by processing conditionals and replacing placeholders."""
     # Step 1: Process conditional blocks
-    content = process_conditional_blocks(template_content, resume_phase)
+    content = process_conditional_blocks(template_content, resume_phase, refactor)
 
     # Step 2: Replace all {{PLACEHOLDER}} variables
     for placeholder, value in replacements.items():
@@ -560,7 +653,7 @@ def main():
     replacements = build_replacements(args, refactor, refactors, global_context, script_dir)
 
     # Render the template
-    rendered = render_template(template_content, replacements, args.resume_phase)
+    rendered = render_template(template_content, replacements, args.resume_phase, refactor)
 
     # Write the output
     err = write_output(args.output, rendered)
@@ -610,13 +703,35 @@ def main():
 
     # Success
     refactor_model = refactor.get("model", "")
+
+    # Extract browser state for JSON output
+    browser_interaction = refactor.get("browser_interaction")
+    browser_enabled = False
+    browser_tool = "auto"
+
+    browser_verify_env = os.environ.get("BROWSER_VERIFY", "").lower()
+    if browser_verify_env == "false":
+        browser_interaction = None
+
+    if browser_interaction:
+        if isinstance(browser_interaction, bool):
+            browser_enabled = True
+        elif isinstance(browser_interaction, dict):
+            steps = browser_interaction.get("verify_steps", [])
+            if steps or browser_interaction.get("url") or browser_interaction.get("enabled", True):
+                browser_enabled = True
+            browser_tool = browser_interaction.get("tool", "auto")
+
     output = {
         "success": True,
         "output_path": os.path.abspath(args.output),
+        "checkpoint_path": checkpoint_path,
         "model": refactor_model,
         "pipeline_mode": pipeline_mode,
         "agent_count": agent_count,
         "critic_enabled": critic_enabled,
+        "browser_enabled": browser_enabled,
+        "browser_tool": browser_tool,
     }
     print(json.dumps(output, indent=2, ensure_ascii=False))
     sys.exit(0)

package/bundled/dev-pipeline/templates/bug-fix-list-schema.json

@@ -1,7 +1,7 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
   "title": "Dev-Pipeline Bug Fix List",
-  "description": "Schema for .prizmkit/plans/bug-fix-list.json \u2014 standardized input for the Bug Fix Pipeline",
+  "description": "Schema for .prizmkit/plans/bug-fix-list.json — standardized input for the Bug Fix Pipeline",
   "type": "object",
   "required": [
     "$schema",
@@ -51,7 +51,7 @@
           "title": {
             "type": "string",
             "minLength": 1,
-            "description": "Bug title \u2014 brief description of the symptom"
+            "description": "Bug title — brief description of the symptom"
           },
           "description": {
             "type": "string",
@@ -194,6 +194,25 @@
           "model": {
             "type": "string",
             "description": "AI model ID for this bug fix. Overrides $MODEL env var."
+          },
+          "browser_interaction": {
+            "type": "object",
+            "description": "Browser verification config for bugs reproducible via UI. Supports playwright-cli and opencli. AI auto-detects dev server command, URL, and port from project config at runtime.",
+            "properties": {
+              "tool": {
+                "type": "string",
+                "enum": ["playwright-cli", "opencli", "auto"],
+                "default": "auto",
+                "description": "Browser tool to use. 'auto' (default) = AI chooses at runtime. 'playwright-cli' = local dev server verification in isolated browser. 'opencli' = reuses Chrome logged-in session, ideal for verifying bugs related to third-party integrations or OAuth flows."
+              },
+              "verify_steps": {
+                "type": "array",
+                "description": "Verification goals describing HOW to reproduce and verify the bug fix (e.g., 'Click login button and verify error message is gone', 'Open dashboard and confirm performance metrics display'). AI decides concrete browser tool actions at runtime. If omitted, AI auto-reproduces from error description.",
+                "items": {
+                  "type": "string"
+                }
+              }
+            }
           }
         }
       }
@@ -241,4 +260,4 @@
       }
     }
   }
-}
+}

package/bundled/dev-pipeline/templates/bugfix-bootstrap-prompt.md

@@ -82,6 +82,34 @@ You are the **bug fix session agent**. Fix Bug {{BUG_ID}}: "{{BUG_TITLE}}".
 mkdir -p .prizmkit/bugfix/{{BUG_ID}}
 ```
 
+{{IF_BROWSER_INTERACTION}}
+
+#### Browser Verification Setup
+
+The bug may be reproducible via the UI using browser tools:
+
+{{IF_BROWSER_TOOL_AUTO}}
+- **Browser Tool**: Will be auto-selected based on error type and dev server configuration
+{{END_IF_BROWSER_TOOL_AUTO}}
+
+{{IF_BROWSER_TOOL_PLAYWRIGHT}}
+- **Browser Tool**: playwright-cli (local isolated browser against dev server)
+{{END_IF_BROWSER_TOOL_PLAYWRIGHT}}
+
+{{IF_BROWSER_TOOL_OPENCLI}}
+- **Browser Tool**: opencli (Chrome session with existing login context — ideal for OAuth/third-party integrations)
+{{END_IF_BROWSER_TOOL_OPENCLI}}
+
+**Browser Verification Goals**:
+{{BROWSER_VERIFY_STEPS}}
+
+If the bug is related to UI/frontend, you may use these tools to:
+1. Reproduce the bug in a running dev server
+2. Verify the fix after implementation
+3. Smoke-test related UI flows for regression
+
+{{END_IF_BROWSER_INTERACTION}}
+
 ### Phase 1: Diagnose & Plan
 
 **Goal**: Identify root cause, build project context, produce spec.md + plan.md.
@@ -112,6 +140,10 @@ Run `/prizmkit-plan` with `artifact_dir=.prizmkit/bugfix/{{BUG_ID}}/`:
 - Subsequent tasks implement the minimal fix to make the test pass (GREEN state)
 - Resolve any `[NEEDS CLARIFICATION]` markers autonomously — do NOT pause
 
+{{IF_BROWSER_INTERACTION}}
+- **Browser Verification**: If the bug is UI-reproducible, plan.md should include browser-based reproduction as an optional verification step
+{{END_IF_BROWSER_INTERACTION}}
+
 **DECISION GATE — Fast Path Check**:
 - If plan.md has ≤ 2 tasks AND root cause is obvious → mark `FAST_PATH=true`, skip Phase 3 (Review) later
 
@@ -137,6 +169,16 @@ Run `/prizmkit-implement` with `artifact_dir=.prizmkit/bugfix/{{BUG_ID}}/`:
 - Runs test suite after each task
 - Uses convergence-based test failure recovery (keep fixing while progress is being made)
 
+{{IF_BROWSER_INTERACTION}}
+
+**Browser Verification During Implementation**:
+- After each code fix, you may optionally use browser tools to verify the behavior
+- Reproduce the original bug steps and confirm they no longer occur
+- Test related UI flows to ensure no regression
+- Document any manual verification steps in the implementation notes
+
+{{END_IF_BROWSER_INTERACTION}}
+
 After implement completes, verify:
 1. All tasks in plan.md are `[x]`
 2. Reproduction test passes (GREEN)
@@ -158,6 +200,15 @@ Run `/prizmkit-code-review` with `artifact_dir=.prizmkit/bugfix/{{BUG_ID}}/`:
 - If PASS: proceed
 - If NEEDS_FIXES: the skill exhausted its max rounds; log remaining findings and proceed
 
+{{IF_BROWSER_INTERACTION}}
+
+**Code Review — Browser Verification Check**:
+- Verify that browser-based reproduction steps (if applicable) are clearly documented
+- Confirm that the fix maintains the expected UI behavior for all affected flows
+- Validate that any manual verification steps have been completed successfully
+
+{{END_IF_BROWSER_INTERACTION}}
+
 **CP-3**: Code review complete, all tests green.
 
 **Checkpoint update**: Set step `prizmkit-code-review` to `"completed"`.
@@ -206,6 +257,11 @@ The fix-report.md MUST contain:
 - **Bug Resolution Summary**: ID, title, status, phases completed
 - **What Was Fixed**: changes made, diff summary, commit hash
 - **Verification Results**: reproduction test before/after, regression tests, review findings
+
+{{IF_BROWSER_INTERACTION}}
+- **Browser Verification Results**: UI flows tested, browser tool used (if any), manual verification steps completed
+{{END_IF_BROWSER_INTERACTION}}
+
 - **Knowledge Captured**: TRAPS updated (if any), prevention recommendation
 - **Acceptance Criteria Verification**: checklist with pass/fail for each criterion
 

package/bundled/dev-pipeline/templates/refactor-bootstrap-prompt.md

@@ -123,6 +123,37 @@ Run `/prizmkit-plan` with `artifact_dir=.prizmkit/refactor/{{REFACTOR_ID}}/`:
 
 Resolve any `[NEEDS CLARIFICATION]` markers using the refactor description — do NOT pause for interactive input.
 
+{{IF_BROWSER_INTERACTION}}
+
+#### Browser Verification Strategy
+
+The refactor may affect UI behavior. Browser verification can validate:
+- **UI Render**: UI components render identically after refactoring
+- **User Interactions**: Navigation, form submissions, and workflows function as before
+- **Feature Coverage**: Refactored features work end-to-end in real browser environment
+
+{{IF_BROWSER_TOOL_AUTO}}
+Browser tool will be auto-selected at runtime based on dev server and feature complexity.
+{{END_IF_BROWSER_TOOL_AUTO}}
+
+{{IF_BROWSER_TOOL_PLAYWRIGHT}}
+**Tool: playwright-cli** — Local isolated browser instance for dev server verification
+{{END_IF_BROWSER_TOOL_PLAYWRIGHT}}
+
+{{IF_BROWSER_TOOL_OPENCLI}}
+**Tool: opencli** — Chrome session with existing login for testing OAuth/third-party integrations
+{{END_IF_BROWSER_TOOL_OPENCLI}}
+
+**Verification Goals**:
+{{BROWSER_VERIFY_STEPS}}
+
+Include browser verification approach in plan.md:
+- Which UI flows should be smoke-tested after refactoring?
+- Any specific user journeys affected by the structural changes?
+- Should verification be part of review phase or implementation phase?
+
+{{END_IF_BROWSER_INTERACTION}}
+
 - **CP-RF-1**: Both `spec.md` and `plan.md` exist in `.prizmkit/refactor/{{REFACTOR_ID}}/`
 - **Checkpoint update**: set step `prizmkit-plan` to `"completed"` in `{{CHECKPOINT_PATH}}`
 
@@ -144,8 +175,19 @@ Resolve any `[NEEDS CLARIFICATION]` markers using the refactor description — d
      - If tests fail: revert the task, analyze why, try alternative approach
      - Writes '## Implementation Log' to context-snapshot.md (or equivalent)
   5. Do NOT change behavior — only improve structure
-  6. If the refactor involves multiple files: run `/compact` after completing half the tasks to free context budget. If `/compact` is unavailable, continue without it.
-  7. After all tasks complete, run the full test suite one final time
+
+{{IF_BROWSER_INTERACTION}}
+
+  6. **Browser Smoke Tests** (after every major refactor task):
+     - Use browser tools to verify UI still renders correctly
+     - Test the primary user flows affected by the refactoring
+     - Confirm no visual or interactive regressions
+     - Document any manual browser verification steps in implementation notes
+
+{{END_IF_BROWSER_INTERACTION}}
+
+  7. If the refactor involves multiple files: run `/compact` after completing half the tasks to free context budget. If `/compact` is unavailable, continue without it.
+  8. After all tasks complete, run the full test suite one final time
   "
 - **Wait for Dev to return**
 - If Dev reports test failures that cannot be resolved after 3 attempts: escalate, write status="failed"
@@ -164,8 +206,19 @@ Resolve any `[NEEDS CLARIFICATION]` markers using the refactor description — d
   2. Read `.prizmkit/refactor/{{REFACTOR_ID}}/plan.md` for architecture decisions and completed tasks
   3. Run `/prizmkit-code-review` with artifact_dir=.prizmkit/refactor/{{REFACTOR_ID}}/. The skill runs an internal review-fix loop (Reviewer → filter → Dev fix, max 3 rounds) and writes review-report.md.
   4. Run full test suite and verify ALL tests pass
-  5. review-report.md will be written to .prizmkit/refactor/{{REFACTOR_ID}}/ by prizmkit-code-review
-  6. Report: verdict (PASS/NEEDS_FIXES), number of rounds, findings fixed/rejected
+
+{{IF_BROWSER_INTERACTION}}
+
+  5. **Browser Verification Review**:
+     - Verify that critical user workflows still function end-to-end in browser
+     - Confirm UI renders consistently after structural changes
+     - Validate any behavior-sensitive components behave identically
+     - Document browser verification findings in review-report.md
+
+{{END_IF_BROWSER_INTERACTION}}
+
+  6. review-report.md will be written to .prizmkit/refactor/{{REFACTOR_ID}}/ by prizmkit-code-review
+  7. Report: verdict (PASS/NEEDS_FIXES), number of rounds, findings fixed/rejected
   "
 - **Wait for Reviewer to return**
 - Read `review-report.md` — if PASS proceed, if NEEDS_FIXES log remaining findings and proceed.
@@ -193,6 +246,13 @@ Resolve any `[NEEDS CLARIFICATION]` markers using the refactor description — d
    - Refactor Summary (ID, title, type, status, phases completed)
    - What Changed (files modified, structural changes made, diff summary)
    - Behavior Verification (test suite results before/after, specific tests exercised)
+
+{{IF_BROWSER_INTERACTION}}
+
+   - Browser Verification (UI flows tested, tools used, any manual verification performed)
+
+{{END_IF_BROWSER_INTERACTION}}
+
    - Code Quality Metrics (if measurable: files consolidated, duplication reduced, etc.)
    - Acceptance Criteria Verification (checklist with pass/fail for each criterion)
 

package/bundled/dev-pipeline/templates/refactor-list-schema.json

@@ -1,7 +1,7 @@
 {
   "$schema": "http://json-schema.org/draft-07/schema#",
   "title": "Dev-Pipeline Refactor List",
-  "description": "Schema for .prizmkit/plans/refactor-list.json \u2014 standardized input for the Refactor Pipeline",
+  "description": "Schema for .prizmkit/plans/refactor-list.json — standardized input for the Refactor Pipeline",
   "type": "object",
   "required": [
     "$schema",
@@ -54,7 +54,7 @@
           "title": {
             "type": "string",
             "minLength": 1,
-            "description": "Refactor title \u2014 brief description of the change"
+            "description": "Refactor title — brief description of the change"
           },
           "description": {
             "type": "string",
@@ -201,6 +201,25 @@
               1,
               3
             ]
+          },
+          "browser_interaction": {
+            "type": "object",
+            "description": "Browser verification config for refactors affecting UI behavior. Supports playwright-cli and opencli. AI auto-detects dev server command, URL, and port from project config at runtime.",
+            "properties": {
+              "tool": {
+                "type": "string",
+                "enum": ["playwright-cli", "opencli", "auto"],
+                "default": "auto",
+                "description": "Browser tool to use. 'auto' (default) = AI chooses at runtime. 'playwright-cli' = local dev server verification in isolated browser. 'opencli' = reuses Chrome logged-in session, ideal for verifying refactors involving third-party integrations or OAuth flows."
+              },
+              "verify_steps": {
+                "type": "array",
+                "description": "Verification goals describing WHAT to verify after refactoring (e.g., 'Navigation still works', 'Form submission succeeds', 'UI renders identically'). AI decides concrete browser tool actions at runtime. If omitted, AI explores the app and verifies no visual or behavioral regressions.",
+                "items": {
+                  "type": "string"
+                }
+              }
+            }
           }
         }
       }
@@ -248,4 +267,4 @@
       }
     }
   }
-}
+}

package/bundled/skills/_metadata.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.1.39",
+  "version": "1.1.40",
   "skills": {
     "prizm-kit": {
       "description": "Full-lifecycle dev toolkit. Covers spec-driven development, Prizm context docs, code quality, debugging, deployment, and knowledge management.",

package/bundled/skills/bugfix-pipeline-launcher/SKILL.md

@@ -50,10 +50,14 @@ Before any action, validate:
 1. **bugfix pipeline exists**: Confirm `dev-pipeline/launch-bugfix-daemon.sh` and `dev-pipeline/run-bugfix.sh` are present and executable
 2. **For start**: `.prizmkit/plans/bug-fix-list.json` must exist in `.prizmkit/plans/` (or user-specified path)
 3. **Dependencies**: `jq`, `python3`, AI CLI (`cbc` or `claude`) must be in PATH
+4. **Browser tools** (optional): If any bug has `browser_interaction` field, check the corresponding tool is available. Bugs may specify `tool: "playwright-cli"`, `tool: "opencli"`, or `tool: "auto"` (AI chooses at runtime).
 
 Quick check:
 ```bash
 command -v jq && command -v python3 && (command -v cbc || command -v claude) && echo "All dependencies OK"
+# Optional: browser interaction support (check both tools — bugs may use either)
+command -v playwright-cli && echo "playwright-cli OK" || echo "playwright-cli not found (playwright browser verification will be skipped)"
+command -v opencli && echo "opencli OK" || echo "opencli not found (opencli browser verification will be skipped)"
 ```
 
 If `.prizmkit/plans/bug-fix-list.json` is missing, inform user:
@@ -67,6 +71,8 @@ Detect user intent from their message, then follow the corresponding workflow:
 
 #### Intent A: Start Bugfix Pipeline
 
+> **Execution model**: The pipeline processes bugs **sequentially** (one at a time, in severity/priority order). The `dependencies` field in bug-fix-list.json is reserved for future parallel execution support and does NOT affect current execution order.
+
 1. **Check prerequisites**:
    ```bash
    ls .prizmkit/plans/bug-fix-list.json 2>/dev/null && echo "Found" || echo "Missing"
@@ -126,13 +132,27 @@ Detect user intent from their message, then follow the corresponding workflow:
    - 1
    - 5
 
-   **Question 3 — Session timeout** (multiSelect: false):
+   **Question 3 — Critic review** (multiSelect: false):
+   - Off (default) — Skip adversarial review
+   - On — Enable adversarial critic review: an independent AI agent reviews the diagnosis/plan for completeness and the fix for defects, edge cases, and regression risks. Adds ~5-10 min per bug.
+
+   **Question 4 — Advanced config?** (multiSelect: false):
+   - No (default) — Use defaults for session timeout and failure behavior
+   - Yes — Configure session timeout and stop-on-failure options
+
+   Note: Bug filter defaults to all bugs (by severity order). Default Critic to Off unless bugs have `severity: "critical"` or `severity: "high"` (in which case default to On). If the user selects "Other" on any option, handle their custom input.
+
+   **If user chose "Yes" to Advanced config**, ask a second round of `AskUserQuestion`:
+
+   **Question 1 — Session timeout** (multiSelect: false):
    - None (default) — No timeout
    - 30 min — `SESSION_TIMEOUT=1800`
    - 1 hour — `SESSION_TIMEOUT=3600`
    - 2 hours — `SESSION_TIMEOUT=7200`
 
-   Note: Bug filter defaults to all bugs (by severity order). If the user selects "Other" on any option, handle their custom input.
+   **Question 2 — Stop on failure** (multiSelect: false):
+   - Off (default) — Pipeline continues to next task after failure
+   - On — Pipeline halts immediately when a task exhausts all retries (`STOP_ON_FAILURE=1`)
 
    **Environment variable mapping** (for translating user responses → env vars):
 
@@ -141,8 +161,9 @@ Detect user intent from their message, then follow the corresponding workflow:
    | Verbose: Off | `VERBOSE=0` |
    | Verbose: On | `VERBOSE=1` |
    | Max retries: N | `MAX_RETRIES=N` |
+   | Critic: On | `ENABLE_CRITIC=true` |
    | Timeout: value | `SESSION_TIMEOUT=<seconds>` |
-   | Model override | `MODEL=<model-name>` |
+   | Stop on failure: On | `STOP_ON_FAILURE=1` |
 
    **Advanced environment variables** (not exposed in interactive menu, pass via `--env`):
 
@@ -156,7 +177,6 @@ Detect user intent from their message, then follow the corresponding workflow:
    | `LOG_CLEANUP_ENABLED` | `1` | Run periodic log cleanup (`0` to disable) |
    | `LOG_RETENTION_DAYS` | `14` | Delete logs older than N days |
    | `LOG_MAX_TOTAL_MB` | `1024` | Keep total logs under N MB via oldest-first cleanup |
-   | `STOP_ON_FAILURE` | `0` | Stop pipeline when a task exhausts all retries (`1` to stop immediately) |
 
    ⚠️ STOP HERE and wait for user response before continuing to step 6.
 
@@ -312,6 +332,8 @@ dev-pipeline/reset-bug.sh B-001 --clean --run .prizmkit/plans/bug-fix-list.json
 | PID file stale (process dead) | `launch-bugfix-daemon.sh` auto-cleans, retry start |
 | Launch failed (process died immediately) | Show last 20 lines of log: `tail -20 .prizmkit/state/bugfix/pipeline-daemon.log` |
 | All bugs blocked/failed/needs-info | Show status, suggest retrying or providing more info |
+| `playwright-cli` not installed | Browser verification skipped for playwright bugs (non-blocking). Suggest: `npm install -g @playwright/cli@latest && playwright-cli install --skills` |
+| `opencli` not installed | Browser verification skipped for opencli bugs (non-blocking). Install opencli for Chrome session-based browser verification |
 | Permission denied on script | Run `chmod +x dev-pipeline/launch-bugfix-daemon.sh dev-pipeline/run-bugfix.sh` |
 
 ### Integration Notes

package/bundled/skills/feature-pipeline-launcher/SKILL.md

@@ -52,13 +52,14 @@ Before any action, validate:
 2. **For start**: `.prizmkit/plans/feature-list.json` must exist in `.prizmkit/plans/` (or user-specified path)
 3. **Dependencies**: `jq`, `python3`, AI CLI (`cbc` or `claude`) must be in PATH
 4. **Python version**: Requires Python 3.8+ for dev-pipeline scripts
-5. **playwright-cli** (optional): If any feature has `browser_interaction` field, check `playwright-cli` is available
+5. **Browser tools** (optional): If any feature has `browser_interaction` field, check the corresponding tool is available. Features may specify `tool: "playwright-cli"`, `tool: "opencli"`, or `tool: "auto"` (AI chooses at runtime).
 
 Quick check:
 ```bash
 command -v jq && command -v python3 && (command -v cbc || command -v claude) && echo "All dependencies OK"
-# Optional: browser interaction support
-command -v playwright-cli && echo "playwright-cli OK" || echo "playwright-cli not found (browser verification will be skipped)"
+# Optional: browser interaction support (check both tools — features may use either)
+command -v playwright-cli && echo "playwright-cli OK" || echo "playwright-cli not found (playwright browser verification will be skipped)"
+command -v opencli && echo "opencli OK" || echo "opencli not found (opencli browser verification will be skipped)"
 ```
 
 If `.prizmkit/plans/feature-list.json` is missing, inform user:
@@ -72,6 +73,8 @@ Detect user intent from their message, then follow the corresponding workflow:
 
 #### Intent A: Start Pipeline
 
+> **Execution model**: The pipeline processes features **sequentially** (one at a time, in order). The `dependencies` field in feature-list.json is reserved for future parallel execution support and does NOT affect current execution order.
+
 1. **Check prerequisites**:
    ```bash
    ls .prizmkit/plans/feature-list.json 2>/dev/null && echo "Found" || echo "Missing"
@@ -139,7 +142,7 @@ Detect user intent from their message, then follow the corresponding workflow:
 
    **Question 1 — Critic review** (multiSelect: false):
    - Off (default) — Skip adversarial review
-   - On — Enable critic review after planning & implementation (+5-10 min/feature)
+   - On — Enable adversarial critic review: an independent AI agent reviews the spec/plan for completeness and the implementation for defects, edge cases, and missed requirements. Adds ~5-10 min per feature.
 
    **Question 2 — Verbose logging** (multiSelect: false):
    - On (default) — Detailed AI session logs including tool calls and subagent activity
@@ -150,15 +153,25 @@ Detect user intent from their message, then follow the corresponding workflow:
    - 1
    - 5
 
-   **Question 4 — Session timeout** (multiSelect: false):
+   **Question 4 — Advanced config?** (multiSelect: false):
+   - No (default) — Use defaults for session timeout and failure behavior
+   - Yes — Configure session timeout and stop-on-failure options
+
+   Note: Due to the 4-question limit per `AskUserQuestion` call, Feature filter and Browser verify use their defaults (all features, auto-detect browser tools). If the user selects "Other" on any option, handle their custom input.
+
+   Default Critic to Off unless features have `estimated_complexity: "high"` or above (in which case default to On).
+
+   **If user chose "Yes" to Advanced config**, ask a second round of `AskUserQuestion`:
+
+   **Question 1 — Session timeout** (multiSelect: false):
    - None (default) — No timeout
    - 30 min — `SESSION_TIMEOUT=1800`
    - 1 hour — `SESSION_TIMEOUT=3600`
    - 2 hours — `SESSION_TIMEOUT=7200`
 
-   Note: Due to the 4-question limit per `AskUserQuestion` call, Feature filter and Browser verify use their defaults (all features, auto-detect playwright-cli). If the user selects "Other" on any option, handle their custom input.
-
-   Default Critic to Off unless features have `estimated_complexity: "high"` or above (in which case default to On).
+   **Question 2 — Stop on failure** (multiSelect: false):
+   - Off (default) — Pipeline continues to next task after failure
+   - On — Pipeline halts immediately when a task exhausts all retries (`STOP_ON_FAILURE=1`)
 
    **Environment variable mapping** (for translating user responses → env vars):
 
@@ -169,6 +182,7 @@ Detect user intent from their message, then follow the corresponding workflow:
    | Verbose: On | `VERBOSE=1` |
    | Max retries: N | `MAX_RETRIES=N` |
    | Timeout: value | `SESSION_TIMEOUT=<seconds>` |
+   | Stop on failure: On | `STOP_ON_FAILURE=1` |
 
    **Advanced environment variables** (not exposed in interactive menu, pass via `--env`):
 
@@ -183,7 +197,6 @@ Detect user intent from their message, then follow the corresponding workflow:
    | `LOG_CLEANUP_ENABLED` | `1` | Run periodic log cleanup (`0` to disable) |
    | `LOG_RETENTION_DAYS` | `14` | Delete logs older than N days |
    | `LOG_MAX_TOTAL_MB` | `1024` | Keep total logs under N MB via oldest-first cleanup |
-   | `STOP_ON_FAILURE` | `0` | Stop pipeline when a task exhausts all retries (`1` to stop immediately) |
 
    ⚠️ STOP HERE and wait for user response before continuing to step 7.
 
@@ -233,7 +246,7 @@ Detect user intent from their message, then follow the corresponding workflow:
    - Summarize results: total features, succeeded, failed, skipped
    - If all succeeded: each feature session has already run `prizmkit-retrospective` internally. Ask user what's next.
    - If some failed: show failed feature IDs and suggest `reset-feature.sh <F-XXX> --clean --run` for a fresh retry
-   - **Browser verification**: If any completed features have `browser_interaction` and `playwright-cli` is installed, offer to run browser verification (see §Post-Pipeline Browser Verification)
+   - **Browser verification**: If any completed features have `browser_interaction` and the corresponding browser tool (`playwright-cli` or `opencli`) is installed, offer to run browser verification (see Post-Pipeline Browser Verification)
 
    **If background daemon**:
    1. Verify launch:
@@ -335,7 +348,7 @@ Notes:
 
 #### Post-Pipeline Browser Verification
 
-After pipeline completion, if features have `browser_interaction` fields and `playwright-cli` is installed:
+After pipeline completion, if features have `browser_interaction` fields and the corresponding browser tool (`playwright-cli` or `opencli`) is installed:
 
 1. **Check which features qualify**:
    ```bash
@@ -346,21 +359,25 @@ After pipeline completion, if features have `browser_interaction` fields and `pl
    for feat in data.get('features', []):
        bi = feat.get('browser_interaction')
        if bi and feat.get('status') == 'completed':
-           print(f\"  {feat['id']}: {feat.get('title','')} → {bi['url']}\")
+           tool = bi.get('tool', 'auto') if isinstance(bi, dict) else 'auto'
+           print(f\"  {feat['id']}: {feat.get('title','')} (tool: {tool})\")
    " 2>/dev/null
    ```
 
-2. **Ask user**: "N features have browser verification configured. Run playwright-cli verification now? (Y/n)"
+2. **Ask user**: "N features have browser verification configured. Run browser verification now? (Y/n)"
 
 3. **If yes**, for each qualifying feature:
    - Start dev server if `setup_command` is specified
-   - Use `playwright-cli snapshot` to discover element refs, then verify each goal in `verify_steps` using appropriate actions, and take a screenshot
+   - Select browser tool based on `browser_interaction.tool`:
+     - `"playwright-cli"` → Use `playwright-cli snapshot` to discover element refs, then verify each goal in `verify_steps`
+     - `"opencli"` → Use `opencli browser` to interact with Chrome's logged-in session (ideal for OAuth/third-party verification)
+     - `"auto"` → AI chooses the appropriate tool based on context (default: `playwright-cli` for local dev, `opencli` for authenticated flows)
+   - Take a screenshot after verification
    - Close browser and stop dev server
 
 4. **Report results**:
-   - For each feature: URL opened, steps executed, screenshot path
+   - For each feature: URL opened, tool used, steps executed, screenshot path
    - If any step fails: flag as verification failure
-   - Screenshots are saved to `.playwright-cli/` for user review
 
 **Important**: Browser verification is best-effort — failures here do NOT change the feature's pipeline status. They serve as visual confirmation aids for the user.
 
@@ -378,7 +395,8 @@ After pipeline completion, if features have `browser_interaction` fields and `pl
 | Launch failed (process died immediately) | Show last 20 lines of log: `tail -20 .prizmkit/state/features/pipeline-daemon.log` |
 | Feature stuck/blocked | Use `reset-feature.sh <F-XXX> --clean --run` for a fresh retry |
 | All features blocked/failed | Show status, suggest daemon-safe recovery: `dev-pipeline/reset-feature.sh <F-XXX> --clean --run .prizmkit/plans/feature-list.json` |
-| `playwright-cli` not installed | Browser verification skipped (non-blocking). Suggest: `npm install -g @playwright/cli@latest && playwright-cli install --skills` |
+| `playwright-cli` not installed | Browser verification skipped for playwright features (non-blocking). Suggest: `npm install -g @playwright/cli@latest && playwright-cli install --skills` |
+| `opencli` not installed | Browser verification skipped for opencli features (non-blocking). Install opencli for Chrome session-based browser verification |
 | Permission denied on script | Run `chmod +x dev-pipeline/launch-feature-daemon.sh dev-pipeline/run-feature.sh` |
 | Pipeline stop failed (process won't die) | Process may be stuck in I/O wait. Try `kill -9 <PID>` manually. Check for orphaned child processes with `ps aux \| grep claude` |
 | `.env.local` missing or incomplete | Warn: database connection variables not found. Suggest creating env file with required connection variables for the project's database |

package/bundled/skills/recovery-workflow/SKILL.md

@@ -65,9 +65,13 @@ recovery-workflow
   │   ├── Based on artifact presence → infer current phase
   │   └── No match → reject and guide user
   │
-  ├── Phase 1: Report + user choice
-  │   ├── Display detection results
+  ├── Phase 1: Diagnose + report + user choice
+  │   ├── Check branch and working tree state
+  │   ├── Scan all pipelines for failed/in-progress tasks
+  │   ├── Find residual dev branches from failed tasks
+  │   ├── Display diagnosis + detection results
   │   ├── If code changes exist → run test suite
+  │   ├── If multiple failed tasks → ask user which to recover
   │   └── User chooses: run-recovery.sh (recommended) | interactive | start fresh
   │
   └── Phase 2: Execute remaining steps
@@ -119,9 +123,73 @@ To start a new workflow:
 
 ---
 
-## Phase 1: Report + User Confirmation
-
-**Goal**: Show the user what was found and get confirmation before executing.
+## Phase 1: Diagnose + Report + User Confirmation
+
+**Goal**: Assess workspace health, identify failed tasks across all pipelines, and present recovery options.
+
+### 1.0 Workspace & Failure Diagnosis
+
+Before showing the recovery report, run a comprehensive diagnosis:
+
+1. **Check current branch and working tree**:
+   ```bash
+   git branch --show-current
+   git status --porcelain | head -10
+   ```
+   Report: which branch is active, whether there are uncommitted changes.
+
+2. **Scan all pipelines for failed/in-progress tasks**:
+   ```bash
+   # Feature pipeline
+   python3 dev-pipeline/scripts/update-feature-status.py \
+     --feature-list .prizmkit/plans/feature-list.json \
+     --state-dir .prizmkit/state/features \
+     --action status 2>/dev/null
+
+   # Bugfix pipeline
+   python3 dev-pipeline/scripts/update-bug-status.py \
+     --bug-list .prizmkit/plans/bug-fix-list.json \
+     --state-dir .prizmkit/state/bugfix \
+     --action status 2>/dev/null
+
+   # Refactor pipeline
+   python3 dev-pipeline/scripts/update-refactor-status.py \
+     --refactor-list .prizmkit/plans/refactor-list.json \
+     --state-dir .prizmkit/state/refactor \
+     --action status 2>/dev/null
+   ```
+   For each pipeline that has state, extract: total tasks, completed, failed, in-progress, pending.
+
+3. **Find residual dev branches** from failed/interrupted tasks:
+   ```bash
+   git branch --list 'dev/*' 'feat/*' 'fix/*' 'bugfix/*' 'refactor/*'
+   ```
+   Cross-reference with failed task IDs to identify which branches belong to which failed tasks.
+
+4. **Present diagnosis summary** — show all findings before the recovery report:
+   ```
+   ═══════════════════════════════════════════════════
+     Workspace Diagnosis
+   ═══════════════════════════════════════════════════
+
+     Branch:       fix/B-001-login-crash
+     Working tree: 3 uncommitted changes
+
+     Feature pipeline:  2 completed, 1 failed (F-003), 2 pending
+     Bugfix pipeline:   1 completed, 1 failed (B-002), 0 pending
+     Refactor pipeline: (no state found)
+
+     Residual branches:
+       dev/F-003-payment-integration-202604201030
+       fix/B-002-encoding-bug
+
+     Failed tasks:
+       F-003: Payment integration    [FAILED] → branch: dev/F-003-...
+       B-002: CSV encoding bug       [FAILED] → branch: fix/B-002-...
+   ═══════════════════════════════════════════════════
+   ```
+
+   If no pipelines have state and no failed tasks are found, skip to 1.1 (standard recovery report).
 
 ### 1.1 Display Detection Report
 
@@ -160,7 +228,28 @@ Include test results in the report:
 - How many tests pass/fail
 - If failures exist — which tests and why
 
-### 1.3 Ask User to Choose Recovery Approach
+### 1.3 Select Recovery Target (if multiple failed tasks)
+
+If the diagnosis in 1.0 found **multiple failed/interrupted tasks** across pipelines, ask the user which one to recover first before proceeding:
+
+```
+AskUserQuestion:
+  question: "Multiple failed/interrupted tasks found. Which would you like to recover?"
+  header: "Target"
+  options:
+    - label: "F-003: Payment integration"
+      description: "Feature pipeline — FAILED — branch: dev/F-003-payment-integration-202604201030"
+    - label: "B-002: CSV encoding bug"
+      description: "Bugfix pipeline — FAILED — branch: fix/B-002-encoding-bug"
+    - label: "Recover all sequentially"
+      description: "Recover each failed task one by one in priority order"
+```
+
+Generate the options dynamically from the diagnosis results. Include task ID, title, pipeline type, status, and branch name.
+
+If only one failed/interrupted task is found, skip this step — proceed directly to 1.4 with that task as the recovery target.
+
+### 1.4 Ask User to Choose Recovery Approach
 
 **User choice required (mandatory)** — Use `AskUserQuestion` to present interactive selectable options. **NEVER skip this step. NEVER choose for the user.**
 
@@ -208,7 +297,7 @@ End this skill.
 
 **NEVER proceed to Phase 2 without explicit user selection via `AskUserQuestion`. Do NOT render options as plain text — the user must be able to click/select.**
 
-**CHECKPOINT CP-REC-1**: User chose recovery approach.
+**CHECKPOINT CP-REC-1**: User chose recovery target and approach.
 
 ---
 

package/bundled/skills/refactor-pipeline-launcher/SKILL.md

@@ -49,10 +49,14 @@ Before any action, validate:
 2. **For start**: `.prizmkit/plans/refactor-list.json` must exist in `.prizmkit/plans/` (or user-specified path)
 3. **Dependencies**: `jq`, `python3`, AI CLI (`cbc` or `claude`) must be in PATH
 4. **Python version**: Requires Python 3.8+ for dev-pipeline scripts
+5. **Browser tools** (optional): If any refactor has `browser_interaction` field, check the corresponding tool is available. Refactors may specify `tool: "playwright-cli"`, `tool: "opencli"`, or `tool: "auto"` (AI chooses at runtime).
 
 Quick check:
 ```bash
 command -v jq && command -v python3 && (command -v cbc || command -v claude) && echo "All dependencies OK"
+# Optional: browser interaction support (check both tools — refactors may use either)
+command -v playwright-cli && echo "playwright-cli OK" || echo "playwright-cli not found (playwright browser verification will be skipped)"
+command -v opencli && echo "opencli OK" || echo "opencli not found (opencli browser verification will be skipped)"
 ```
 
 If `.prizmkit/plans/refactor-list.json` is missing, inform user:
@@ -66,6 +70,8 @@ Detect user intent from their message, then follow the corresponding workflow:
 
 #### Intent A: Start Pipeline
 
+> **Execution model**: The pipeline processes refactor tasks **sequentially** (one at a time, in priority order). The `dependencies` field in refactor-list.json is reserved for future parallel execution support and does NOT affect current execution order.
+
 1. **Check prerequisites**:
    ```bash
    ls .prizmkit/plans/refactor-list.json 2>/dev/null && echo "Found" || echo "Missing"
@@ -144,17 +150,33 @@ Detect user intent from their message, then follow the corresponding workflow:
    - 1
    - 5
 
-   **Question 3 — Session timeout** (multiSelect: false):
+   **Question 3 — Strict behavior check** (multiSelect: false):
+   - On (default) — Run full test suite after each refactor task to verify behavior preservation
+   - Off — Skip post-task test verification (faster but riskier)
+
+   **Question 4 — Advanced config?** (multiSelect: false):
+   - No (default) — Use defaults for critic review, session timeout, and failure behavior
+   - Yes — Configure critic review, session timeout, and stop-on-failure options
+
+   Note: Refactor filter defaults to all refactor items (by priority order). If the user selects "Other" on any option, handle their custom input.
+
+   **If user chose "Yes" to Advanced config**, ask a second round of `AskUserQuestion`:
+
+   **Question 1 — Session timeout** (multiSelect: false):
    - None (default) — No timeout
    - 30 min — `SESSION_TIMEOUT=1800`
    - 1 hour — `SESSION_TIMEOUT=3600`
    - 2 hours — `SESSION_TIMEOUT=7200`
 
-   **Question 4 — Strict behavior check** (multiSelect: false):
-   - On (default) — Run full test suite after each refactor task to verify behavior preservation
-   - Off — Skip post-task test verification (faster but riskier)
+   **Question 2 — Stop on failure** (multiSelect: false):
+   - Off (default) — Pipeline continues to next task after failure
+   - On — Pipeline halts immediately when a task exhausts all retries (`STOP_ON_FAILURE=1`)
 
-   Note: Refactor filter defaults to all refactor items (by priority order). If the user selects "Other" on any option, handle their custom input.
+   **Question 3 — Critic review** (multiSelect: false):
+   - Off (default) — Skip adversarial review
+   - On — Enable adversarial critic review: an independent AI agent reviews the refactor plan for completeness and the implementation for regressions, missed edge cases, and behavior violations. Adds ~5-10 min per refactor task.
+
+   Default Critic to Off unless refactor items have `priority: "critical"` (in which case default to On).
 
    **Environment variable mapping** (for translating user responses → env vars):
 
@@ -163,9 +185,11 @@ Detect user intent from their message, then follow the corresponding workflow:
    | Verbose: On | `VERBOSE=1` |
    | Verbose: Off | `VERBOSE=0` |
    | Max retries: N | `MAX_RETRIES=N` |
-   | Timeout: value | `SESSION_TIMEOUT=<seconds>` |
    | Strict behavior: On | `STRICT_BEHAVIOR_CHECK=1` |
    | Strict behavior: Off | `STRICT_BEHAVIOR_CHECK=0` |
+   | Critic: On | `ENABLE_CRITIC=true` |
+   | Timeout: value | `SESSION_TIMEOUT=<seconds>` |
+   | Stop on failure: On | `STOP_ON_FAILURE=1` |
 
    **Advanced environment variables** (not exposed in interactive menu, pass via `--env`):
 
@@ -179,7 +203,6 @@ Detect user intent from their message, then follow the corresponding workflow:
    | `LOG_CLEANUP_ENABLED` | `1` | Run periodic log cleanup (`0` to disable) |
    | `LOG_RETENTION_DAYS` | `14` | Delete logs older than N days |
    | `LOG_MAX_TOTAL_MB` | `1024` | Keep total logs under N MB via oldest-first cleanup |
-   | `STOP_ON_FAILURE` | `0` | Stop pipeline when a task exhausts all retries (`1` to stop immediately) |
 
    ⚠️ STOP HERE and wait for user response before continuing to step 7.
 
@@ -342,6 +365,8 @@ Notes:
 | Launch failed (process died immediately) | Show last 20 lines of log: `tail -20 .prizmkit/state/refactor/pipeline-daemon.log` |
 | Refactor stuck/blocked | Use `reset-refactor.sh <R-XXX> --clean --run` for a fresh retry |
 | All refactors blocked/failed | Show status, suggest recovery: `dev-pipeline/reset-refactor.sh <R-XXX> --clean --run .prizmkit/plans/refactor-list.json` |
+| `playwright-cli` not installed | Browser verification skipped for playwright refactors (non-blocking). Suggest: `npm install -g @playwright/cli@latest && playwright-cli install --skills` |
+| `opencli` not installed | Browser verification skipped for opencli refactors (non-blocking). Install opencli for Chrome session-based browser verification |
 | Permission denied on script | Run `chmod +x dev-pipeline/launch-refactor-daemon.sh dev-pipeline/run-refactor.sh` |
 
 ### Integration Notes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "prizmkit",
-  "version": "1.1.39",
+  "version": "1.1.40",
   "description": "Create a new PrizmKit-powered project with clean initialization — no framework dev files, just what you need.",
   "type": "module",
   "bin": {