prizmkit 1.1.39 → 1.1.41

package/bundled/dev-pipeline/templates/bootstrap-tier1.md

@@ -342,29 +342,6 @@ Append results to `context-snapshot.md`:
 If verification fails, log the failure details but continue to commit. Failures do NOT block the commit, but you MUST attempt verification and MUST clean up the dev server.
 {{END_IF_BROWSER_INTERACTION}}
 
-### Phase 3.8: Local Deploy Verification
-
-You just implemented this feature — you know the project's tech stack and build tools.
-
-1. **Build**: Run the project's build/compile commands. If a required tool is missing, install it first.
-2. **Fix**: If build fails with code errors (type errors, missing imports, config issues), fix them (max 2 rounds), then re-verify.
-3. **Assess and record** — append to context-snapshot.md:
-   - **ALL builds pass** → `## Deploy Verification: PASS` — proceed to commit
-   - **Some builds fail with fixable errors** → fix and re-verify (already handled in step 2)
-   - **Cannot build locally** (missing system-level deps you cannot install) → Record: `## Deploy Verification: PARTIAL — missing system deps (see below)`
-
-Deploy verification does NOT block the commit, but you MUST attempt it.
-
-**Step 4 — Smoke test** (only if build passed and project can be started):
-1. Start the project locally (e.g., `make dev`, `npm start`, `go run .`, etc.)
-2. Verify basic functionality: hit key endpoints, check health routes, confirm the UI loads
-3. Stop the server process you started — do NOT leave it running
-4. Record smoke test results in `## Deploy Verification` section
-
-If the project cannot be started locally (e.g., requires external services, databases, credentials), skip the smoke test and note why.
-
-**Deploy documentation update** — Run `/prizmkit-deploy` ONLY if this feature introduced new infrastructure or deployment-affecting changes (new database, cache, message queue, new env vars, new build steps, changed ports/protocols). If none apply, skip `/prizmkit-deploy`.
-
 ### Phase 4: Architecture Sync & Commit (SINGLE COMMIT)
 
 **4a.** Run `/prizmkit-retrospective` — maintains `.prizm-docs/` (architecture index):

package/bundled/dev-pipeline/templates/bootstrap-tier2.md

@@ -435,29 +435,6 @@ Append results to `context-snapshot.md`:
 If verification fails, log the failure details but continue to commit. Failures do NOT block the commit, but you MUST attempt verification and MUST clean up the dev server.
 {{END_IF_BROWSER_INTERACTION}}
 
-### Phase 5.8: Local Deploy Verification
-
-You just implemented this feature — you know the project's tech stack and build tools.
-
-1. **Build**: Run the project's build/compile commands. If a required tool is missing, install it first.
-2. **Fix**: If build fails with code errors (type errors, missing imports, config issues), fix them (max 2 rounds), then re-verify.
-3. **Assess and record** — append to context-snapshot.md:
-   - **ALL builds pass** → `## Deploy Verification: PASS` — proceed to commit
-   - **Some builds fail with fixable errors** → fix and re-verify (already handled in step 2)
-   - **Cannot build locally** (missing system-level deps you cannot install) → Record: `## Deploy Verification: PARTIAL — missing system deps (see below)`
-
-Deploy verification does NOT block the commit, but you MUST attempt it.
-
-**Step 4 — Smoke test** (only if build passed and project can be started):
-1. Start the project locally (e.g., `make dev`, `npm start`, `go run .`, etc.)
-2. Verify basic functionality: hit key endpoints, check health routes, confirm the UI loads
-3. Stop the server process you started — do NOT leave it running
-4. Record smoke test results in `## Deploy Verification` section
-
-If the project cannot be started locally (e.g., requires external services, databases, credentials), skip the smoke test and note why.
-
-**Deploy documentation update** — Run `/prizmkit-deploy` ONLY if this feature introduced new infrastructure or deployment-affecting changes (new database, cache, message queue, new env vars, new build steps, changed ports/protocols). If none apply, skip `/prizmkit-deploy`.
-
 ### Phase 6: Architecture Sync & Commit (SINGLE COMMIT)
 
 **6a.** Run `/prizmkit-retrospective` — maintains `.prizm-docs/` (architecture index):

package/bundled/dev-pipeline/templates/bootstrap-tier3.md

@@ -500,29 +500,6 @@ Append results to `context-snapshot.md`:
 If verification fails, log the failure details but continue to commit. Failures do NOT block the commit, but you MUST attempt verification and MUST clean up the dev server.
 {{END_IF_BROWSER_INTERACTION}}
 
-### Phase 5.8: Local Deploy Verification
-
-You just implemented this feature — you know the project's tech stack and build tools.
-
-1. **Build**: Run the project's build/compile commands. If a required tool is missing, install it first.
-2. **Fix**: If build fails with code errors (type errors, missing imports, config issues), fix them (max 2 rounds), then re-verify.
-3. **Assess and record** — append to context-snapshot.md:
-   - **ALL builds pass** → `## Deploy Verification: PASS` — proceed to commit
-   - **Some builds fail with fixable errors** → fix and re-verify (already handled in step 2)
-   - **Cannot build locally** (missing system-level deps you cannot install) → Record: `## Deploy Verification: PARTIAL — missing system deps (see below)`
-
-Deploy verification does NOT block the commit, but you MUST attempt it.
-
-**Step 4 — Smoke test** (only if build passed and project can be started):
-1. Start the project locally (e.g., `make dev`, `npm start`, `go run .`, etc.)
-2. Verify basic functionality: hit key endpoints, check health routes, confirm the UI loads
-3. Stop the server process you started — do NOT leave it running
-4. Record smoke test results in `## Deploy Verification` section
-
-If the project cannot be started locally (e.g., requires external services, databases, credentials), skip the smoke test and note why.
-
-**Deploy documentation update** — Run `/prizmkit-deploy` ONLY if this feature introduced new infrastructure or deployment-affecting changes (new database, cache, message queue, new env vars, new build steps, changed ports/protocols). If none apply, skip `/prizmkit-deploy`.
-
 ### Phase 6: Retrospective & Commit (SINGLE COMMIT) — DO NOT SKIP
 
 **Bug Fix Documentation Policy**:

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/dev-pipeline/tests/test-deploy-safety.sh

@@ -0,0 +1,223 @@
+#!/usr/bin/env bash
+# Test deploy safety check logic across different task status scenarios
+# Run: bash dev-pipeline/tests/test-deploy-safety.sh
+set -euo pipefail
+
+SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
+REPO_ROOT="$(cd "$SCRIPT_DIR/../.." && pwd)"
+
+RED='\033[0;31m'
+GREEN='\033[0;32m'
+YELLOW='\033[1;33m'
+NC='\033[0m'
+
+PASS=0
+FAIL=0
+TOTAL=0
+
+pass() { echo -e "  ${GREEN}PASS${NC} $1"; PASS=$((PASS + 1)); TOTAL=$((TOTAL + 1)); }
+fail() { echo -e "  ${RED}FAIL${NC} $1 — $2"; FAIL=$((FAIL + 1)); TOTAL=$((TOTAL + 1)); }
+
+echo "================================="
+echo " Deploy Safety Check Tests"
+echo "================================="
+echo ""
+
+# --- Test 1: All tasks completed -> deploy should proceed ---
+echo "[Test 1] All 'completed': incomplete_count should be 0"
+cat > /tmp/test-deploy-all-completed.json << 'JSON'
+{"features": [{"id": "F-A", "status": "completed"}, {"id": "F-B", "status": "completed"}]}
+JSON
+count=$(python3 -c "
+import json
+with open('/tmp/test-deploy-all-completed.json') as f:
+    data = json.load(f)
+bad = [f for f in data.get('features', [])
+       if f.get('status') not in ('completed', 'skipped')]
+print(len(bad))
+")
+if [[ "$count" == "0" ]]; then
+    pass "incomplete_count=0, deploy proceeds"
+else
+    fail "incomplete_count=$count, expected 0"
+fi
+
+# --- Test 2: One failed, one completed -> deploy blocked ---
+echo "[Test 2] Mixed 'completed' + 'failed': incomplete_count should be 1"
+cat > /tmp/test-deploy-mixed.json << 'JSON'
+{"features": [{"id": "F-A", "status": "completed"}, {"id": "F-B", "status": "failed"}]}
+JSON
+count=$(python3 -c "
+import json
+with open('/tmp/test-deploy-mixed.json') as f:
+    data = json.load(f)
+bad = [f for f in data.get('features', [])
+       if f.get('status') not in ('completed', 'skipped')]
+print(len(bad))
+")
+if [[ "$count" == "1" ]]; then
+    pass "incomplete_count=1, deploy blocked"
+else
+    fail "incomplete_count=$count, expected 1"
+fi
+
+# --- Test 3: All skipped -> deploy proceeds (skipped is non-blocking) ---
+echo "[Test 3] All 'skipped': incomplete_count should be 0"
+cat > /tmp/test-deploy-all-skipped.json << 'JSON'
+{"features": [{"id": "F-A", "status": "skipped"}, {"id": "F-B", "status": "skipped"}]}
+JSON
+count=$(python3 -c "
+import json
+with open('/tmp/test-deploy-all-skipped.json') as f:
+    data = json.load(f)
+bad = [f for f in data.get('features', [])
+       if f.get('status') not in ('completed', 'skipped')]
+print(len(bad))
+")
+if [[ "$count" == "0" ]]; then
+    pass "incomplete_count=0, deploy proceeds (skipped is non-blocking)"
+else
+    fail "incomplete_count=$count, expected 0"
+fi
+
+# --- Test 4: Timed-out status -> deploy blocked ---
+echo "[Test 4] 'timed_out' status: incomplete_count should be 1"
+cat > /tmp/test-deploy-timeout.json << 'JSON'
+{"features": [{"id": "F-A", "status": "completed"}, {"id": "F-B", "status": "timed_out"}]}
+JSON
+count=$(python3 -c "
+import json
+with open('/tmp/test-deploy-timeout.json') as f:
+    data = json.load(f)
+bad = [f for f in data.get('features', [])
+       if f.get('status') not in ('completed', 'skipped')]
+print(len(bad))
+")
+if [[ "$count" == "1" ]]; then
+    pass "incomplete_count=1, deploy blocked"
+else
+    fail "incomplete_count=$count, expected 1"
+fi
+
+# --- Test 5: tee /dev/stderr | tail -1 pattern extracts only count ---
+echo "[Test 5] Multi-line output extraction: only last line (integer) captured"
+cat > /tmp/test-deploy-tee.json << 'JSON'
+{"features": [{"id": "F-001", "status": "failed", "title": "Broken feature"}, {"id": "F-002", "status": "crashed", "title": "Also broken"}]}
+JSON
+result=$({ python3 -c "
+import json
+with open('/tmp/test-deploy-tee.json') as f:
+    data = json.load(f)
+bad = [f for f in data.get('features', [])
+       if f.get('status') not in ('completed', 'skipped')]
+for f in bad:
+    print(f\"  {f['id']}: {f.get('status', 'unknown')} — {f.get('title', '')}\")
+print(len(bad))
+" /tmp/test-deploy-tee.json 2>/dev/null || echo "0"; } | tail -1)
+if [[ "$result" =~ ^[0-9]+$ ]]; then
+    pass "extracted count is integer: $result"
+else
+    fail "extracted count is not a clean integer: '$result'"
+fi
+
+# --- Test 6: Empty feature list -> deploy proceeds ---
+echo "[Test 6] Empty list: incomplete_count should be 0"
+cat > /tmp/test-deploy-empty.json << 'JSON'
+{"features": []}
+JSON
+count=$(python3 -c "
+import json
+with open('/tmp/test-deploy-empty.json') as f:
+    data = json.load(f)
+bad = [f for f in data.get('features', [])
+       if f.get('status') not in ('completed', 'skipped')]
+print(len(bad))
+")
+if [[ "$count" == "0" ]]; then
+    pass "incomplete_count=0, deploy proceeds"
+else
+    fail "incomplete_count=$count, expected 0"
+fi
+
+# --- Test 7: Bugfix variant with needs_info (non-blocking) ---
+echo "[Test 7] Bugfix: 'needs_info' should NOT block deploy"
+cat > /tmp/test-deploy-bugfix.json << 'JSON'
+{"bugs": [{"id": "B-001", "status": "completed"}, {"id": "B-002", "status": "needs_info"}]}
+JSON
+count=$(python3 -c "
+import json
+with open('/tmp/test-deploy-bugfix.json') as f:
+    data = json.load(f)
+bad = [b for b in data.get('bugs', [])
+       if b.get('status') not in ('completed', 'skipped', 'needs_info')]
+print(len(bad))
+")
+if [[ "$count" == "0" ]]; then
+    pass "incomplete_count=0, deploy proceeds (needs_info non-blocking)"
+else
+    fail "incomplete_count=$count, expected 0"
+fi
+
+# --- Test 8: Refactor variant ---
+echo "[Test 8] Refactor: completed + skipped -> deploy proceeds"
+cat > /tmp/test-deploy-refactor.json << 'JSON'
+{"refactors": [{"id": "R-001", "status": "completed"}, {"id": "R-002", "status": "skipped"}]}
+JSON
+count=$(python3 -c "
+import json
+with open('/tmp/test-deploy-refactor.json') as f:
+    data = json.load(f)
+bad = [r for r in data.get('refactors', [])
+       if r.get('status') not in ('completed', 'skipped')]
+print(len(bad))
+")
+if [[ "$count" == "0" ]]; then
+    pass "incomplete_count=0, deploy proceeds"
+else
+    fail "incomplete_count=$count, expected 0"
+fi
+
+# --- Test 9: Real feature-list.json ---
+echo "[Test 9] Real feature-list.json: both completed -> deploy proceeds"
+if [[ -f "$REPO_ROOT/.prizmkit/plans/feature-list.json" ]]; then
+    count=$(python3 -c "
+import json
+with open('$REPO_ROOT/.prizmkit/plans/feature-list.json') as f:
+    data = json.load(f)
+bad = [f for f in data.get('features', [])
+       if f.get('status') not in ('completed', 'skipped')]
+print(len(bad))
+")
+    if [[ "$count" == "0" ]]; then
+        pass "real list: incomplete_count=0"
+    else
+        fail "real list: incomplete_count=$count, expected 0"
+    fi
+else
+    echo "  ${YELLOW}SKIP${NC} No real feature-list.json found"
+fi
+
+# --- Test 10: ENABLE_DEPLOY=0 skips the entire block ---
+echo "[Test 10] ENABLE_DEPLOY=0: deploy block should be skipped entirely"
+ENABLE_DEPLOY=0
+executed=false
+if [[ "$ENABLE_DEPLOY" == "1" ]]; then
+    executed=true
+fi
+if [[ "$executed" == "false" ]]; then
+    pass "ENABLE_DEPLOY=0: deploy block skipped"
+else
+    fail "ENABLE_DEPLOY=0: deploy block should NOT execute"
+fi
+
+# --- Cleanup ---
+rm -f /tmp/test-deploy-*.json
+
+echo ""
+echo "================================="
+echo " Results: $PASS passed, $FAIL failed ($TOTAL total)"
+echo "================================="
+
+if [[ $FAIL -gt 0 ]]; then
+    exit 1
+fi

package/bundled/skills/_metadata.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.1.39",
+  "version": "1.1.41",
   "skills": {
     "prizm-kit": {
       "description": "Full-lifecycle dev toolkit. Covers spec-driven development, Prizm context docs, code quality, debugging, deployment, and knowledge management.",
@@ -58,10 +58,10 @@
       "hasScripts": false
     },
     "prizmkit-deploy": {
-      "description": "Generate or update deployment documentation (.prizmkit/deploy.md) by scanning project state and deploy strategy. On-demand skill.",
+      "description": "Universal deployment gateway: auto-discovers project type and target, routes to SSH automation (PM2 + Nginx + blue/green), guided cloud/Docker deployment, or documentation fallback. Also operates existing deployments (status/logs/restart/rollback).",
       "tier": "1",
       "category": "prizmkit-skill",
-      "hasAssets": true,
+      "hasAssets": false,
       "hasScripts": false
     },
     "feature-workflow": {

package/bundled/skills/app-planner/SKILL.md

@@ -37,7 +37,6 @@ If you believe the task is better suited for a different workflow, you MUST:
 1. `.prizmkit/plans/project-brief.md` (`.prizmkit/plans/` — accumulated project context brief)
 2. Project conventions and architecture decisions appended to `CLAUDE.md` / `CODEBUDDY.md` (with user consent)
 3. Infrastructure configuration (database conventions + deployment config) appended to `CLAUDE.md` / `CODEBUDDY.md` `### Infrastructure` section
-4. `.prizmkit/deploy.md` — deployment documentation (created or updated with infrastructure config)
 
 **After planning is complete**, you MUST:
 1. Present the summary of captured project-level context (vision, conventions, architecture decisions, project brief)
@@ -199,7 +198,6 @@ Do NOT use this skill when:
      #### Deployment Credentials Reference
      - [platform]: [token/auth method description]
      ```
-   - Update `.prizmkit/deploy.md` if it exists — append deployment details to relevant sections (Prerequisites, Production Deployment, Environment Variables). If it does not exist, create it from the `prizmkit-deploy` template with known information filled in.
    - Items still marked "Skip — decide later" remain as `<!-- [topic]: deferred -->` in CLAUDE.md for `prizmkit-deploy` to pick up later.
 
 4. **Project brief accumulation** — throughout all interactive phases:
@@ -443,7 +441,6 @@ After all checkpoints pass, present a summary and end the session:
    - Infrastructure config → `CLAUDE.md` / `CODEBUDDY.md` `### Infrastructure` (database conventions + deployment config)
    - Tech stack → `.prizmkit/config.json`
    - Architecture decisions (if any) → `CLAUDE.md` / `CODEBUDDY.md` `### Architecture Decisions`
-   - Deployment docs → `.prizmkit/deploy.md` (if created/updated)
    - Project brief → `.prizmkit/plans/project-brief.md`
 
 2. **Suggest possible next steps** (as text, NOT auto-invoked):