prizmkit 1.1.40 → 1.1.41

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

@@ -154,6 +154,10 @@ Detect user intent from their message, then follow the corresponding workflow:
    - 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):
 
    | Config choice | Environment variable |
@@ -164,6 +168,7 @@ Detect user intent from their message, then follow the corresponding workflow:
    | Critic: On | `ENABLE_CRITIC=true` |
    | 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`):
 
@@ -188,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
    ```
 
@@ -199,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.
@@ -334,6 +339,7 @@ dev-pipeline/reset-bug.sh B-001 --clean --run .prizmkit/plans/bug-fix-list.json
 | 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

@@ -173,6 +173,10 @@ Detect user intent from their message, then follow the corresponding workflow:
    - 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 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):
 
    | Config choice | Environment variable |
@@ -183,6 +187,7 @@ Detect user intent from their message, then follow the corresponding workflow:
    | 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`):
 
@@ -208,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
    ```
 
@@ -219,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.
@@ -399,6 +404,7 @@ After pipeline completion, if features have `browser_interaction` fields and the
 | `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