prizmkit 1.0.105 → 1.0.106

package/bundled/VERSION.json

@@ -1,5 +1,5 @@
 {
-  "frameworkVersion": "1.0.105",
-  "bundledAt": "2026-03-25T15:34:22.423Z",
-  "bundledFrom": "c46942e"
+  "frameworkVersion": "1.0.106",
+  "bundledAt": "2026-03-25T15:56:50.507Z",
+  "bundledFrom": "d91f86f"
 }

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

@@ -80,7 +80,7 @@ cat .prizmkit/specs/{{FEATURE_SLUG}}/failure-log.md 2>/dev/null || echo "NO_PREV
 If failure-log.md exists:
 - Read ROOT_CAUSE and SUGGESTION — adjust your approach accordingly
 - Read DISCOVERED_TRAPS — if any are genuine, inject into .prizm-docs/ during Phase 4 retrospective
-- Do NOT delete failure-log.md until this session succeeds
+- Do NOT delete failure-log.md until this session completes all phases and commits successfully
 
 ```bash
 ls .prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md 2>/dev/null && echo "EXISTS" || echo "MISSING"
@@ -193,6 +193,11 @@ If you encounter an unrecoverable error, context overflow, or are about to exit
 
 2. This file is intentionally lightweight — write it BEFORE context runs out.
 
+**Lifecycle**: failure-log.md is a temporary cross-session artifact. Do NOT commit it to git. After a successful session (all phases complete + commit done), delete it:
+```bash
+rm -f .prizmkit/specs/{{FEATURE_SLUG}}/failure-log.md
+```
+
 ## Reminders
 
 - Tier 1: you handle everything directly — no subagents needed

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

@@ -91,7 +91,7 @@ cat .prizmkit/specs/{{FEATURE_SLUG}}/failure-log.md 2>/dev/null || echo "NO_PREV
 If failure-log.md exists:
 - Read ROOT_CAUSE and SUGGESTION — adjust your approach accordingly
 - Read DISCOVERED_TRAPS — if any are genuine, inject into .prizm-docs/ during Phase 5 retrospective
-- Do NOT delete failure-log.md until this session succeeds
+- Do NOT delete failure-log.md until this session completes all phases and commits successfully
 
 ```bash
 ls .prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md 2>/dev/null && echo "EXISTS" || echo "MISSING"
@@ -242,6 +242,11 @@ If you encounter an unrecoverable error, context overflow, or are about to exit
 
 2. This file is intentionally lightweight — write it BEFORE context runs out.
 
+**Lifecycle**: failure-log.md is a temporary cross-session artifact. Do NOT commit it to git. After a successful session (all phases complete + commit done), delete it:
+```bash
+rm -f .prizmkit/specs/{{FEATURE_SLUG}}/failure-log.md
+```
+
 ## Reminders
 
 - Tier 2: orchestrator builds context+plan, Dev implements, Reviewer reviews+tests — use direct Agent spawn for agents

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

@@ -154,7 +154,7 @@ cat .prizmkit/specs/{{FEATURE_SLUG}}/failure-log.md 2>/dev/null || echo "NO_PREV
 If failure-log.md exists:
 - Read ROOT_CAUSE and SUGGESTION — adjust your approach accordingly
 - Read DISCOVERED_TRAPS — if any are genuine, inject into .prizm-docs/ during Phase 6 retrospective
-- Do NOT delete failure-log.md until this session succeeds
+- Do NOT delete failure-log.md until this session completes all phases and commits successfully
 
 Check existing artifacts first:
 ```bash
@@ -422,6 +422,11 @@ If you encounter an unrecoverable error, context overflow, or are about to exit
 
 2. This file is intentionally lightweight — write it BEFORE context runs out.
 
+**Lifecycle**: failure-log.md is a temporary cross-session artifact. Do NOT commit it to git. After a successful session (all phases complete + commit done), delete it:
+```bash
+rm -f .prizmkit/specs/{{FEATURE_SLUG}}/failure-log.md
+```
+
 ## Reminders
 
 - Tier 3: full team — Dev (implementation) → Reviewer (review + test) — spawn agents directly via Agent tool

package/bundled/skills/_metadata.json

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

package/bundled/skills/prizmkit-prizm-docs/assets/PRIZM-SPEC.md

@@ -250,7 +250,7 @@ CONSTRAINTS:
 - TRAPS section is CRITICAL for preventing AI from making known mistakes
 - TRAPS entries MUST have severity prefix ([CRITICAL], [HIGH], or [LOW]). [REVIEW] may precede severity as a temporary staleness marker.
 - TRAPS optional fields: append `| REF: <7-char-hash>` for traceability, `| STALE_IF: <glob>` for auto-expiry detection
-- TRAPS severity guide: CRITICAL = data loss/security/financial/crash, HIGH = functional failure/silent error, LOW = naming/minor quality
+- TRAPS severity: CRITICAL = data loss/security/financial/crash, HIGH = functional failure/silent error, LOW = naming/minor quality (see TRAPS_FORMAT_REFERENCE in Section 3.2)
 - REJECTED entries prevent AI from re-proposing failed approaches
 - FILES lists all files, not just key ones
 - RULES may only SUPPLEMENT root.prizm RULES with module-specific exceptions, never contradict them

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

@@ -78,8 +78,8 @@ While updating an affected L1/L2 doc, if you encounter TRAPS entries **without**
 **1g. TRAPS staleness check** (only when an L2 doc's TRAPS section has > 10 entries):
 
 Perform a quick staleness scan on existing TRAPS to prevent unbounded accumulation:
-1. If a TRAP has `STALE_IF:` and the glob-matched files no longer exist (verified via `ls` or `git status`) → delete the TRAP entry, append CHANGELOG: `remove: archived stale TRAP - <summary>`
-2. If a TRAP has `REF:` and the referenced code has been substantially rewritten (>80% of the original diff is gone, checked via `git log --follow`) → prepend `[REVIEW]` to the severity, signaling it needs manual verification
+1. If a TRAP has `STALE_IF:` and the glob-matched files no longer exist (verified via `ls`) → delete the TRAP entry, append CHANGELOG: `remove: archived stale TRAP - <summary>`
+2. If a TRAP has `REF:` → check if the referenced file still exists and the REF commit is less than 180 days old (via `git log --since="180 days ago" <hash> 2>/dev/null`). If the file is deleted OR the REF commit is older than 180 days → prepend `[REVIEW]` to the severity, signaling it needs verification during the next retrospective Job 2
 3. Process at most 5 of the oldest TRAPS per L2 doc per session (to bound context cost)
 
 This step is lightweight — it only triggers when TRAPS exceed 10 entries, and processes at most 5 per run.
@@ -117,10 +117,10 @@ Extract TRAPS, RULES, and DECISIONS from development work and inject into `.priz
 - Full format: `- [SEVERITY] <description> | FIX: <approach> | REF: <hash> | STALE_IF: <glob>`
 - Source: actual bugs hit, surprising behavior discovered in code, non-obvious coupling
 
-**TRAPS severity classification guide**:
-- `[CRITICAL]`: data loss, security vulnerability, financial error, system crash
+**TRAPS severity classification**:
+- `[CRITICAL]`: data loss, security, financial error, system crash
 - `[HIGH]`: functional failure, silent error, interface incompatibility
-- `[LOW]`: misleading naming, non-intuitive API usage, minor performance issue
+- `[LOW]`: misleading naming, non-intuitive API, minor performance issue
 
 When writing TRAPS:
 - Severity prefix is MANDATORY (e.g., `[CRITICAL]`, `[HIGH]`, `[LOW]`)

package/package.json

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