prizmkit 1.0.152 → 1.0.153

package/bundled/VERSION.json

@@ -1,5 +1,5 @@
 {
-  "frameworkVersion": "1.0.152",
-  "bundledAt": "2026-04-01T14:11:50.110Z",
-  "bundledFrom": "7fa7136"
+  "frameworkVersion": "1.0.153",
+  "bundledAt": "2026-04-02T01:37:22.899Z",
+  "bundledFrom": "6fee0f0"
 }

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

@@ -41,7 +41,7 @@ You are running in headless mode with a FINITE context window. Exceeding it will
 4. **One task at a time** — In Phase 3 (implement), complete and test one task before starting the next.
 5. **Minimize tool output** — When running commands, use `| head -20` or `| tail -20` to limit output. Never dump entire test suites or logs.
 6. **No intermediate commits** — Do NOT run `git add`/`git commit` during Phase 1-3. All changes are committed once at the end in Phase 4 via `/prizmkit-committer`.
-7. **Capture test output once** — When running the test suite, always use `$TEST_CMD 2>&1 | tee /tmp/test-out.txt | tail -20`. Then grep `/tmp/test-out.txt` for details. Never re-run the suite just to apply a different filter.
+7. **Capture test output once** — When running test suites, always use `$TEST_CMD 2>&1 | tee /tmp/test-out.txt | tail -20`. Then grep `/tmp/test-out.txt` for details. Never re-run the suite just to apply a different filter.
 
 ---
 
@@ -130,14 +130,11 @@ grep -q '^/binary-name$' .gitignore || echo '/binary-name' >> .gitignore
 ```
 Never commit compiled binaries, build output, or generated artifacts.
 
-**3a.** Detect the test command and record baseline:
-```bash
-# Try in order, use first that exits 0
-node --test tests/**/*.test.js 2>&1 | tail -3   # Node built-in
-npm test 2>&1 | tail -3                          # npm fallback
-```
-Record the working command as `TEST_CMD`. Then record baseline failures (if any):
+**3a.** Detect test commands and record baseline:
+
+You know this project's tech stack. Identify ALL test commands that apply (e.g., `go test ./...`, `npm test`, `cargo test`, `pytest`, `make test`, etc.). Record them as `TEST_CMDS` (one or more commands). Then record baseline:
 ```bash
+# Run each test command, capture output
 $TEST_CMD 2>&1 | tee /tmp/test-baseline.txt | tail -20
 ```
 
@@ -191,6 +188,43 @@ You MUST execute this phase. Do NOT skip it. Do NOT mark it as completed without
 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) → Generate `DEPLOY.md` with:
+     ```
+     # Local Development Setup
+
+     ## Prerequisites
+     - [tool]: [install instruction]
+
+     ## Build Steps
+     1. [exact command]
+
+     ## Run / Dev Mode
+     [exact command to start the app locally]
+
+     ## Verify
+     [how to confirm the app is running correctly]
+     ```
+     Record: `## Deploy Verification: PARTIAL — see DEPLOY.md for missing prerequisites`
+
+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.
+
 ### Phase 4: Architecture Sync & Commit (SINGLE COMMIT)
 
 **4a.** Run `/prizmkit-retrospective` — maintains `.prizm-docs/` (architecture index):

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

@@ -41,7 +41,7 @@ You are running in headless mode with a FINITE context window. Exceeding it will
 4. **One task at a time** — In Phase 4 (implement), complete and test one task before starting the next.
 5. **Minimize tool output** — When running commands, use `| head -20` or `| tail -20` to limit output. Never dump entire test suites or logs.
 6. **No intermediate commits** — Do NOT run `git add`/`git commit` during Phase 1-5. All changes are committed once at the end in Phase 6 via `/prizmkit-committer`.
-7. **Capture test output once** — When running the test suite, always use `$TEST_CMD 2>&1 | tee /tmp/test-out.txt | tail -20`. Then grep `/tmp/test-out.txt` for details. Never re-run the suite just to apply a different filter.
+7. **Capture test output once** — When running test suites, always use `$TEST_CMD 2>&1 | tee /tmp/test-out.txt | tail -20`. Then grep `/tmp/test-out.txt` for details. Never re-run the suite just to apply a different filter.
 
 ---
 
@@ -82,6 +82,16 @@ If any agent times out:
 Check `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` — if exists, skip Phase 1 and proceed to Phase {{RESUME_PHASE}}.
 {{END_IF_RESUME}}
 
+### Phase 0.5: Detect Test Commands
+
+You know this project's tech stack. Identify ALL test commands that apply (e.g., `go test ./...`, `npm test`, `cargo test`, `pytest`, `make test`, etc.). Record them as `TEST_CMDS`. Then record baseline:
+```bash
+$TEST_CMD 2>&1 | tee /tmp/test-baseline.txt | tail -20
+```
+Save pre-existing failing tests as `BASELINE_FAILURES`.
+
+> **⚠️ Test Output Rule**: Always capture test output to a temp file (`tee /tmp/test-out.txt`). Then grep the file instead of re-running the suite.
+
 ### Phase 1: Build Context Snapshot (you, the orchestrator)
 
 **Check for previous failure log:**
@@ -302,6 +312,43 @@ You MUST execute this phase. Do NOT skip it. Do NOT mark it as completed without
 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) → Generate `DEPLOY.md` with:
+     ```
+     # Local Development Setup
+
+     ## Prerequisites
+     - [tool]: [install instruction]
+
+     ## Build Steps
+     1. [exact command]
+
+     ## Run / Dev Mode
+     [exact command to start the app locally]
+
+     ## Verify
+     [how to confirm the app is running correctly]
+     ```
+     Record: `## Deploy Verification: PARTIAL — see DEPLOY.md for missing prerequisites`
+
+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.
+
 ### Phase 6: Architecture Sync & Commit (SINGLE COMMIT)
 
 **6a.** Run `/prizmkit-retrospective` — maintains `.prizm-docs/` (architecture index):

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

@@ -75,23 +75,18 @@ If any agent times out:
 - **CP-0**: Verify `.prizm-docs/root.prizm`, `.prizmkit/config.json` exist
 {{END_IF_INIT_NEEDED}}
 {{IF_INIT_DONE}}
-### Phase 0: Record Test Baseline & Detect Test Command
+### Phase 0: Record Test Baseline & Detect Test Commands
 
-**Step 1 — Detect the correct test command** (run once, save as `TEST_CMD`):
-```bash
-# Try in order, use the first one that exits 0
-node --test tests/**/*.test.js 2>&1 | tail -3   # Node built-in
-npm test 2>&1 | tail -3                          # npm script fallback
-```
-Record the working command as `TEST_CMD`. If both fail, record `TEST_CMD="npm test"` as default.
+**Step 1 — Detect test commands**: You know this project's tech stack. Identify ALL test commands that apply (e.g., `go test ./...`, `npm test`, `cargo test`, `pytest`, `make test`, etc.). Record them as `TEST_CMDS`.
 
 **Step 2 — Record pre-existing failure baseline**:
 ```bash
+# Run each test command, capture output
 $TEST_CMD 2>&1 | tee /tmp/test-baseline.txt | tail -20
 ```
 Save the list of **pre-existing failing tests** (if any) as `BASELINE_FAILURES`. These are known failures that existed before this session — Dev must NOT be blamed for them, but must list them in COMPLETION_SIGNAL.
 
-> **⚠️ Test Output Rule**: Always capture test output to a temp file (`tee /tmp/test-out.txt`). Then grep the file instead of re-running the suite. Never run `npm test` multiple times just to apply different grep filters to the output.
+> **⚠️ Test Output Rule**: Always capture test output to a temp file (`tee /tmp/test-out.txt`). Then grep the file instead of re-running the suite.
 {{END_IF_INIT_DONE}}
 
 ### Step 1: Initialize
@@ -400,6 +395,42 @@ You MUST execute this phase. Do NOT skip it. Do NOT mark it as completed without
 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) → Generate `DEPLOY.md` with:
+     ```
+     # Local Development Setup
+
+     ## Prerequisites
+     - [tool]: [install instruction]
+
+     ## Build Steps
+     1. [exact command]
+
+     ## Run / Dev Mode
+     [exact command to start the app locally]
+
+     ## Verify
+     [how to confirm the app is running correctly]
+     ```
+     Record: `## Deploy Verification: PARTIAL — see DEPLOY.md for missing prerequisites`
+
+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.
 
 ### Phase 6: Retrospective & Commit (SINGLE COMMIT) — DO NOT SKIP
 

package/bundled/skills/_metadata.json

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

package/package.json

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