prizmkit 1.0.139 → 1.0.140

package/bundled/VERSION.json

@@ -1,5 +1,5 @@
 {
-  "frameworkVersion": "1.0.139",
-  "bundledAt": "2026-03-28T16:00:11.932Z",
-  "bundledFrom": "ce5323e"
+  "frameworkVersion": "1.0.140",
+  "bundledAt": "2026-03-28T16:26:29.027Z",
+  "bundledFrom": "7a812fc"
 }

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

@@ -36,7 +36,7 @@ Project takeover and bootstrap skill. Scans any project (brownfield or greenfiel
 MODE DETECTION:
 - If `.prizm-docs/` exists: Ask user if they want to reinitialize or update
   - **Reinitialize**: overwrites `.prizm-docs/` and `config.json` tech_stack (fresh start)
-  - **Update**: re-scans tech stack and merges changes into existing `config.json` (see Step 3b merge strategy); updates `root.prizm` TECH_STACK if changed; preserves existing `.prizm-docs/` L1/L2 docs
+  - **Update**: re-scans tech stack and merges changes into existing `config.json` (see Step 3b merge strategy); updates `root.prizm` TECH_STACK if changed; preserves existing `.prizm-docs/` L1/L2 docs; checks for missing L1/L2 docs and creates them for modules with source files (see Update Supplement below)
 - If project has source code: brownfield mode
 - If project is nearly empty: greenfield mode
 
@@ -242,6 +242,14 @@ Saved: .prizmkit/config.json (tech_stack recorded)
 Next: Use /prizmkit-specify to start your first feature
 ```
 
+UPDATE SUPPLEMENT (runs after tech stack merge in Update mode):
+
+1. **Module scan**: Re-scan project directories using the same TWO-TIER model from Step 1. Compare discovered modules against existing MODULE_INDEX in root.prizm.
+2. **Missing L1 check**: For any discovered module with no corresponding L1 `.prizm` doc → create L1 immediately and add to MODULE_INDEX.
+3. **Missing L2 check**: For any module/sub-module that has source files with meaningful logic but no L2 `.prizm` doc → create L2 using the L2 GENERATION TEMPLATE. Judgment call: skip trivial wrapper directories or single-config modules.
+4. **Stale L1 check**: For existing L1 docs, verify FILES count and KEY_FILES are still accurate. Update if source directory contents have changed significantly.
+5. **Report**: Include in the Update report: modules added, L1 docs created, L2 docs created, stale docs refreshed.
+
 **Re-init after PrizmKit upgrade (existing config preserved):**
 ```
 $ /prizmkit-init
@@ -255,6 +263,11 @@ Tech stack changes detected:
   = language: TypeScript (unchanged)
   = frontend: React (unchanged)
 
+Documentation gap-fill:
+  + app/share/[token].prizm (L2) — created (3 source files, meaningful logic)
+  = routes.prizm (L1) — up to date
+  ~ models.prizm (L1) — FILES count updated (8 → 10)
+
 Merged into .prizmkit/config.json (2 fields updated, user overrides preserved)
 ```
 

package/bundled/skills/prizmkit-prizm-docs/SKILL.md

@@ -71,12 +71,13 @@ Update .prizm-docs/ to reflect recent code changes.
 PRECONDITION: .prizm-docs/ exists with root.prizm.
 
 STEPS:
-1. Get changed files via `git diff --cached --name-status`. If nothing staged, use `git diff --name-status`. If no git changes at all, do full rescan comparing code against existing docs.
+1. Get changed files via `git diff --cached --name-status`. If nothing staged, use `git diff --name-status`. If no git changes at all, do full rescan comparing code against existing docs — this includes checking for modules that have source files but no L2 doc.
 2. Map changed files to modules by matching against MODULE_INDEX in root.prizm. Group changes by module.
 3. Classify each change: A (added) -> new KEY_FILES entries. D (deleted) -> remove entries, update counts. M (modified) -> check dependency changes. R (renamed) -> update all path references.
 4. Update affected docs: L2 first (KEY_FILES, INTERFACES, DATA_FLOW, DEPENDENCIES, TRAPS, CHANGELOG), then L1 (FILES count, KEY_FILES, DEPENDENCIES — L1 does NOT contain INTERFACES/DATA_FLOW/TRAPS/DECISIONS), then L0 (MODULE_INDEX counts, CROSS_CUTTING) only if structural change. No UPDATED timestamps — git tracks modification times.
 5. Skip updates if: only internal implementation changed (no interface/dependency change), only comments/whitespace/formatting, only .prizm files changed. DO NOT skip test file changes or bug fixes — they may reveal TRAPS worth capturing in L2.
 6. If new directory qualifies as a module (per MODULE_DISCOVERY_CRITERIA) and matches no existing module: create L1 immediately, add to MODULE_INDEX. If the current diff includes Added or Modified source files in this module → also create L2 immediately using the L2 GENERATION TEMPLATE. Otherwise defer L2.
+6a. **L2 gap check** (runs during full rescan mode only — when no git changes detected): For each existing module in MODULE_INDEX, check if L2 doc exists. If L2 is missing and the module has source files with meaningful logic (not trivial config/wrapper) → create L2 using the L2 GENERATION TEMPLATE. This ensures Update fills documentation gaps left by previous sessions.
 7. Append entries to changelog.prizm using format: `- YYYY-MM-DD | <module-path> | <verb>: <description>`
 8. Enforce size limits: L0 > 4KB -> consolidate. L1 > 4KB -> trim KEY_FILES descriptions, ensure RULES <= 3 entries. L2 > 5KB -> split or archive.
 9. Stage updated .prizm files via `git add .prizm-docs/`

package/package.json

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