prizmkit 1.1.21 → 1.1.24

package/bundled/dev-pipeline/templates/sections/phase-implement-full.md

@@ -2,6 +2,13 @@
 
 **Build artifacts rule** (passed to Dev): After any build/compile command (`go build`, `npm run build`, `tsc`, etc.), ensure the output binary or build directory is in `.gitignore`. Never commit compiled binaries, build output, or generated artifacts.
 
+**Dependency version gate (BLOCKING — pass to Dev agent)**: Before running ANY package install command (`npm install`, `pip install`, `cargo build`, `go mod tidy`, `bundle install`, etc.):
+1. Every version number in the dependency manifest MUST be verified against the real registry (see Context Budget Rules §9)
+2. If a scaffold tool generated a `package.json` / `requirements.txt` / etc., verify the versions it wrote too — scaffold tools can emit outdated versions
+3. Do NOT proceed with install until all versions are confirmed real. Violation = wasted timeout cycles that can crash the session
+
+**Scaffold file rule (pass to Dev agent)**: After running any init/scaffold command, record generated files in context-snapshot.md under `### Scaffold Files (do not re-read)`. Never re-read these files — their content is standard boilerplate (see Context Budget Rules §8). When spawning subagents, explicitly list scaffold files so they skip reading them.
+
 Before spawning Dev, check plan.md Tasks section:
 ```bash
 grep -c '^\- \[ \]' .prizmkit/specs/{{FEATURE_SLUG}}/plan.md 2>/dev/null || true

package/bundled/dev-pipeline/templates/sections/phase-implement-lite.md

@@ -7,6 +7,13 @@ grep -q '^/binary-name$' .gitignore || echo '/binary-name' >> .gitignore
 ```
 Never commit compiled binaries, build output, or generated artifacts.
 
+**Dependency version gate (BLOCKING)**: Before running ANY package install command (`npm install`, `pip install`, `cargo build`, `go mod tidy`, `bundle install`, etc.):
+1. Every version number in your dependency manifest MUST be verified against the real registry (see Context Budget Rules §9)
+2. If you used a scaffold tool that generated a `package.json` / `requirements.txt` / etc., verify the versions it wrote too — scaffold tools can emit outdated versions
+3. Do NOT proceed with install until all versions are confirmed real. Violation = wasted timeout cycles
+
+**Scaffold file rule**: After running any init/scaffold command, record generated files in context-snapshot.md under `### Scaffold Files (do not re-read)`. Never re-read these files — their content is standard boilerplate (see Context Budget Rules §8).
+
 **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`. Then record baseline:

package/bundled/dev-pipeline/tests/test_auto_skip.py

@@ -122,8 +122,13 @@ class TestAutoSkipLinearChain:
 
         auto_skip_blocked_features(fl_path, state_dir, "F-001")
 
+        # status lives in feature-list.json, not status.json
+        statuses = _read_statuses(fl_path)
+        assert statuses["F-002"] == "auto_skipped"
+        # status.json should have updated_at but no status field
         fs = load_feature_status(state_dir, "F-002")
-        assert fs["status"] == "auto_skipped"
+        assert "status" not in fs
+        assert "updated_at" in fs
 
     def test_failing_mid_skips_only_downstream(self, tmp_path):
         features = [
@@ -434,7 +439,6 @@ class TestAutoSkipIntegration:
         with open(fs_path) as f:
             fs = json.load(f)
         fs["retry_count"] = 3
-        fs["status"] = "failed"
         with open(fs_path, "w") as f:
             json.dump(fs, f)
 
@@ -443,4 +447,7 @@ class TestAutoSkipIntegration:
         with open(fs_path) as f:
             fs = json.load(f)
         assert fs["retry_count"] == 0
-        assert fs["status"] == "pending"
+        # status lives in feature-list.json, not status.json
+        assert "status" not in fs
+        statuses = _read_statuses(fl_path)
+        assert statuses["F-001"] == "pending"

package/bundled/skills/_metadata.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.1.21",
+  "version": "1.1.24",
   "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.1.21",
+  "version": "1.1.24",
   "description": "Create a new PrizmKit-powered project with clean initialization — no framework dev files, just what you need.",
   "type": "module",
   "bin": {