prizmkit 1.1.39 → 1.1.41

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,31 @@ 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`)
+
+   **Question 3 — Deploy after completion?** (multiSelect: false):
+   - No (default) — Skip deployment after pipeline completes
+   - Yes — Run /prizmkit-deploy automatically after all bugs fixed successfully (`ENABLE_DEPLOY=1`). Deployment is blocked if any bug was not fixed (status not 'completed', 'skipped', or 'needs_info').
 
    **Environment variable mapping** (for translating user responses → env vars):
 
@@ -141,8 +165,10 @@ 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` |
+   | Deploy: Yes | `ENABLE_DEPLOY=1` |
 
    **Advanced environment variables** (not exposed in interactive menu, pass via `--env`):
 
@@ -156,7 +182,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.
 
@@ -168,7 +193,7 @@ Detect user intent from their message, then follow the corresponding workflow:
    ```
    With all options:
    ```bash
-   VERBOSE=1 MAX_RETRIES=5 SESSION_TIMEOUT=3600 \
+   VERBOSE=1 MAX_RETRIES=5 SESSION_TIMEOUT=3600 ENABLE_DEPLOY=1 \
      dev-pipeline/run-bugfix.sh run .prizmkit/plans/bug-fix-list.json
    ```
 
@@ -179,7 +204,7 @@ Detect user intent from their message, then follow the corresponding workflow:
    With all options:
    ```bash
    dev-pipeline/launch-bugfix-daemon.sh start .prizmkit/plans/bug-fix-list.json \
-     --env "VERBOSE=1 MAX_RETRIES=5"
+     --env "VERBOSE=1 MAX_RETRIES=5 ENABLE_DEPLOY=1"
    ```
 
    **Manual mode**: Print the assembled command(s) and **stop here**. Do not execute anything. Do not proceed to step 7.
@@ -312,6 +337,9 @@ 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 |
+| Deploy session failed | Pipeline completed but deploy session exited non-zero. Check `.prizmkit/state/bugfix/deploy/<session_id>/logs/session.log`. Retry manually: `/prizmkit-deploy`. |
 | 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,29 @@ 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.
+   **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`)
 
-   Default Critic to Off unless features have `estimated_complexity: "high"` or above (in which case default to On).
+   **Question 3 — Deploy after completion?** (multiSelect: false):
+   - No (default) — Skip deployment after pipeline completes
+   - Yes — Run /prizmkit-deploy automatically after all features complete successfully (`ENABLE_DEPLOY=1`). Deployment is blocked if any feature did not complete successfully (status not 'completed' or manually 'skipped').
 
    **Environment variable mapping** (for translating user responses → env vars):
 
@@ -169,6 +186,8 @@ 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` |
+   | Deploy: Yes | `ENABLE_DEPLOY=1` |
 
    **Advanced environment variables** (not exposed in interactive menu, pass via `--env`):
 
@@ -183,7 +202,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.
 
@@ -195,7 +213,7 @@ Detect user intent from their message, then follow the corresponding workflow:
    ```
    With all options:
    ```bash
-   VERBOSE=1 ENABLE_CRITIC=true MAX_RETRIES=5 SESSION_TIMEOUT=3600 \
+   VERBOSE=1 ENABLE_CRITIC=true MAX_RETRIES=5 SESSION_TIMEOUT=3600 ENABLE_DEPLOY=1 \
      dev-pipeline/run-feature.sh run .prizmkit/plans/feature-list.json --features F-001:F-005
    ```
 
@@ -206,7 +224,7 @@ Detect user intent from their message, then follow the corresponding workflow:
    With all options:
    ```bash
    dev-pipeline/launch-feature-daemon.sh start .prizmkit/plans/feature-list.json --features F-001:F-005 \
-     --env "VERBOSE=1 ENABLE_CRITIC=true MAX_RETRIES=5"
+     --env "VERBOSE=1 ENABLE_CRITIC=true MAX_RETRIES=5 ENABLE_DEPLOY=1"
    ```
 
    **Manual mode**: Print the assembled command(s) and **stop here**. Do not execute anything. Do not proceed to step 8.
@@ -233,7 +251,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 +353,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 +364,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,9 +400,11 @@ 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` |
+| Deploy session failed | Pipeline completed but deploy session exited non-zero. Check `.prizmkit/state/features/deploy/<session_id>/logs/session.log`. Retry manually: `/prizmkit-deploy`. |
 | `.env.local` missing or incomplete | Warn: database connection variables not found. Suggest creating env file with required connection variables for the project's database |
 | Database unreachable | Warn: database features will produce mock-only tests. Suggest checking database service status and connection credentials |
 | Migrations not applied | Warn: tables or schema referenced in migration files not found in database. Suggest applying pending migrations |

package/bundled/skills/prizmkit-committer/SKILL.md

@@ -17,7 +17,6 @@ description: "Pure git commit workflow with safety checks. Stages files, generat
 | Uncommitted changes exist | `git status` shows modified/added/untracked files | Inform user "nothing to commit" and stop |
 | `.prizm-docs/` synced (feature/refactor) | `/prizmkit-retrospective` has run | Run `/prizmkit-retrospective` first |
 | Code review passed (pipeline mode) | `review-report.md` in artifact directory has `## Verdict: PASS` | Run `/prizmkit-code-review` first |
-| `.prizmkit/deploy.md` updated (if applicable) | If `/prizmkit-deploy` ran, `.prizmkit/deploy.md` is staged | Run `/prizmkit-deploy` or skip if no infrastructure changes |
 
 ### Workflow