prizmkit 1.1.55 → 1.1.57

package/bundled/VERSION.json

@@ -1,5 +1,5 @@
 {
-  "frameworkVersion": "1.1.55",
-  "bundledAt": "2026-05-25T01:36:43.012Z",
-  "bundledFrom": "0664e65"
+  "frameworkVersion": "1.1.57",
+  "bundledAt": "2026-05-30T08:56:07.192Z",
+  "bundledFrom": "1692276"
 }

package/bundled/skills/_metadata.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.1.55",
+  "version": "1.1.57",
   "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/app-planner/SKILL.md

@@ -240,16 +240,54 @@ After Infrastructure configuration is complete (CP-AP-1.5), check whether the pr
 
 Rules are optional. If the user skips, AI uses general best practices freely — no reminders, no blocking.
 
-### Step 1: Detect missing rules
+### Step 1: Detect which layers need rules
 
 1. Read `.prizmkit/config.json` to get `detected_layers` (written by `prizmkit-init` Phase 4.5).
-   - If `detected_layers` field is absent or empty → skip this entire section, proceed to Prerequisites.
-2. For each layer in `detected_layers`, check if `.prizmkit/rules/<layer>-rules.md` exists:
+   - If `detected_layers` is present and non-empty → use it directly, jump to step 3.
+   - If `detected_layers` is absent or empty → run self-detection (step 2). Do NOT skip rules configuration just because this field is missing — the project may still have layers that need rules.
+
+2. **Self-detection** (only when `detected_layers` is absent/empty from config.json):
+
+   Scan the project to determine which development layers exist. Combine signal matching with your own judgment — the signals below are a guide, not exhaustive.
+
+   | Layer | Where to Look | Signals |
+   |-------|---------------|---------|
+   | **frontend** | `package.json` deps | `react`, `vue`, `angular`, `next`, `nuxt`, `svelte`, `solid-js`, `preact`, `remix`, `astro`, `qwik` |
+   | **frontend** | `package.json` devDeps | `vite`, `webpack`, `parcel`, `turbo` |
+   | **frontend** | Directory | `src/components/`, `pages/`, `app/` with `.tsx`/`.jsx`/`.vue` files |
+   | **backend** | `package.json` deps | `express`, `fastify`, `koa`, `hono`, `nest` |
+   | **backend** | `pyproject.toml`/`requirements.txt` | `fastapi`, `django`, `flask`, `sanic`, `litestar` |
+   | **backend** | `go.mod` | `gin-gonic`, `echo`, `fiber`, `chi` |
+   | **backend** | `pom.xml`/`build.gradle` | `spring-boot`, `quarkus`, `micronaut`, `ktor` |
+   | **backend** | Directory | `routes/`, `controllers/`, `handlers/`, `api/` with server code |
+   | **database** | `package.json` deps | `prisma`, `typeorm`, `sequelize`, `mongoose`, `knex`, `drizzle-orm`, `kysely` |
+   | **database** | `pyproject.toml`/`requirements.txt` | `sqlalchemy`, `pony`, `peewee`, `tortoise-orm` |
+   | **database** | `go.mod` | `gorm`, `sqlx`, `sqlc`, `ent`, `bun` |
+   | **database** | Directory/Env | `migrations/`, `prisma/`, `alembic/`; `.env*` with `DATABASE_URL`, `DB_HOST`, `MONGO_URI` |
+   | **mobile** | File | `pubspec.yaml` (Flutter) |
+   | **mobile** | `package.json` deps | `react-native`, `expo` |
+   | **mobile** | Directory | Both `ios/*.xcodeproj` + `android/build.gradle` simultaneously |
+
+   **Apply your own judgment**: if you see clear evidence of a layer not covered above, include it. If a signal matches but context suggests it's misleading (e.g., a dependency present but not used as the primary tech), downgrade or ignore it.
+
+   After scanning, present findings via `AskUserQuestion`:
+
+   **Question**: "I detected these development layers: [list with brief evidence]. Is this correct?"
+   - **Yes, looks correct (Recommended)** — use detected layers
+   - **Mostly correct, adjust** — I'll note changes
+   - **No layers apply** — skip rules configuration (library/CLI project)
+
+   If user picks "No layers apply" → skip this entire section, proceed to Prerequisites.
+   If user picks "Mostly correct, adjust" → ask what to add, remove, or change, then reassemble `detected_layers`. Continue to step 3.
+   If user confirms → assemble `detected_layers` array and continue to step 3.
+
+3. For each layer in `detected_layers`, check if `.prizmkit/rules/<layer>-rules.md` exists:
    - `frontend` → `.prizmkit/rules/frontend-rules.md`
    - `backend` → `.prizmkit/rules/backend-rules.md`
    - `database` → `.prizmkit/rules/database-rules.md`
    - `mobile` → `.prizmkit/rules/mobile-rules.md`
-3. Display status:
+
+4. Display status:
 
    ```
    Rules Status Check:
@@ -258,8 +296,8 @@ Rules are optional. If the user skips, AI uses general best practices freely —
      [missing] database-rules.md — database interaction detected, no rules configured
    ```
 
-4. If all detected layers already have rules → skip to Prerequisites.
-5. If missing rules found, proceed to Step 2.
+5. If all detected layers already have rules → skip to Prerequisites.
+6. If missing rules found, proceed to Step 2.
 
 ### Step 2: Ask configuration mode
 
@@ -323,7 +361,7 @@ After all selected layers are configured:
 2. **If root.prizm exists**:
    - Read the file.
    - Check if `RULES:` line exists:
-     - If present: append new rules file paths to the existing line.
+     - If present: append new rules file paths to the existing line (check for duplicates first — skip paths already on the line).
      - If absent: add `RULES: .prizmkit/rules/<layer>-rules.md, ...` at the end (after PROJECT_BRIEF line).
 3. **If root.prizm does not exist** (e.g., project without prizm-docs init):
    - Create a minimal `root.prizm` with:
@@ -529,7 +567,7 @@ Checkpoints catch cascading errors early — skipping one means the next phase b
 | **CP-AP-0** | Intent Confirmed | User confirmed session goal (produce / explore) | 1 |
 | **CP-AP-1** | Conventions Checked | Project conventions loaded or asked; `### Project Conventions` section in `CLAUDE.md` / `CODEBUDDY.md` up to date | 1 |
 | **CP-AP-1.5** | Infrastructure Checked | Infrastructure config loaded or asked; `### Infrastructure` section in `CLAUDE.md` / `CODEBUDDY.md` addressed — database, deployment **and cloud services** each configured or explicitly deferred | 1-2 |
-| **CP-AP-1.6** | Rules Configured | For each layer in `detected_layers`, rules file exists in `.prizmkit/rules/` or user explicitly skipped. `root.prizm` `RULES:` pointer up-to-date. | 2 |
+| **CP-AP-1.6** | Rules Configured | For each detected layer (from config.json or self-detection), rules file exists in `.prizmkit/rules/` or user explicitly skipped. `root.prizm` `RULES:` pointer up-to-date. | 2 |
 | **CP-AP-2** | Vision Summary | Goal/users/differentiators confirmed by user. For brownfield: existing purpose confirmed or refined. | 1-2 |
 | **CP-AP-3** | Frontend Design Evaluated | For frontend projects: checked for existing UI/UX design system; user was asked if missing. **Auto-pass** for backend-only or non-UI projects. | 2 |
 | **CP-AP-4** | Project Brief Accumulated | `.prizmkit/plans/project-brief.md` exists at `.prizmkit/plans/` with at least 3 ideas listed. For brownfield: already-implemented items marked `[x]` count toward this total. | 3 |

package/bundled/skills/prizmkit-code-review/SKILL.md

@@ -32,7 +32,8 @@ The loop repeats until the Reviewer finds no issues or the max round limit is re
 
 1. **Read spec.md** from the artifact directory — extract goals and acceptance criteria.
 2. **Read plan.md** from the artifact directory — extract architecture decisions and completed tasks.
-3. **Capture workspace diff**: run `git diff` (unstaged) + `git diff --cached` (staged) + `git status` to understand the full scope of changes. For new files in git status, note their paths for the Reviewer to read.
+3. **Read dev rules** (if configured): Read `.prizmkit/prizm-docs/root.prizm` and check for a `RULES:` line. If present, read all referenced `.prizmkit/rules/<layer>-rules.md` files. If a referenced file does not exist, skip it silently and continue. These define per-layer conventions that the code should follow.
+4. **Capture workspace diff**: run `git diff` (unstaged) + `git diff --cached` (staged) + `git status` to understand the full scope of changes. For new files in git status, note their paths for the Reviewer to read.
    - If no changes are detected, output PASS and stop.
 
 ## Phase 1: Review-Fix Loop
@@ -41,7 +42,7 @@ The loop repeats until the Reviewer finds no issues or the max round limit is re
 ┌─── Loop (max 3 rounds) ──────────────────────────────┐
 │                                                        │
 │  Step 1: Spawn Reviewer Agent (read-only)              │
-│    → Input: git diff + spec goals + plan decisions     │
+│    → Input: git diff + spec goals + plan decisions + dev rules│
 │    → Output: structured findings or PASS               │
 │                                                        │
 │  Step 2: Check result                                  │
@@ -66,10 +67,10 @@ The loop repeats until the Reviewer finds no issues or the max round limit is re
 
 ### Step 1: Spawn Reviewer Agent
 
-Spawn a **read-only** agent (subagent_type: `Explore`) with the following prompt:
+Include the dev rules read in Phase 0 step 3 in the `## Dev Rules` section of the prompt below. Spawn a **read-only** agent (subagent_type: `Explore`) with the following prompt:
 
 ```
-You are a code reviewer. Review workspace changes against the spec goals and plan decisions.
+You are a code reviewer. Review workspace changes against the spec goals, plan decisions, and per-layer dev rules.
 
 ## Spec Goals
 {goals and acceptance criteria from spec.md}
@@ -77,6 +78,9 @@ You are a code reviewer. Review workspace changes against the spec goals and pla
 ## Plan Decisions
 {architecture decisions and task list from plan.md}
 
+## Dev Rules (per-layer conventions)
+{rules from .prizmkit/rules/<layer>-rules.md, or "No custom dev rules configured — use general best practices."}
+
 ## Review Round
 Round {N}. {round_context}
 
@@ -97,6 +101,7 @@ Evaluate the changes across these dimensions (focus on what's relevant):
 3. **Completeness**: Files that should have been changed but weren't? Missing tests, types, imports, exports?
 4. **Consistency**: Do changes follow the project's existing patterns, naming conventions, and code style?
 5. **Security**: Hardcoded secrets, injection vulnerabilities, unsafe operations.
+6. **Rules compliance**: (Skip this dimension if no dev rules were provided.) Do changes follow the per-layer dev rules? Flag violations of framework conventions, naming patterns, state management, or other rules defined for that layer.
 
 ## Output Format
 Respond with EXACTLY this format:
@@ -108,7 +113,7 @@ Respond with EXACTLY this format:
 
 #### Finding N
 - **Severity**: high | medium | low
-- **Dimension**: goal-alignment | defect | completeness | consistency | security
+- **Dimension**: goal-alignment | defect | completeness | consistency | security | rules-compliance
 - **Location**: filepath:line (or "project-level")
 - **Problem**: What is wrong and why it matters
 - **Suggestion**: Recommended fix approach

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

@@ -31,6 +31,7 @@ Before implementation, load context once:
 
 1. **Task context**: Read `plan.md` (including Tasks section) and `spec.md` from the artifact directory. If other companion documents exist in the directory (e.g., `refactor-analysis.md`), read them for additional context.
 2. **Architecture context**: Read `.prizmkit/prizm-docs/root.prizm` (L0 — project overview, module index, tech stack, conventions) and relevant L1/L2 docs for affected modules. Pay special attention to TRAPS (known pitfalls) and DECISIONS (architectural choices).
+3. **Dev rules** (if configured): Check `.prizmkit/prizm-docs/root.prizm` for a `RULES:` line — if present, read all referenced `.prizmkit/rules/<layer>-rules.md` files. If a referenced file does not exist, skip it silently and continue. These define per-layer conventions (frameworks, naming, patterns, state management, etc.) that AI must follow when generating code for that layer. Apply these rules during implementation — if a rule conflicts with what plan.md describes, call it out and ask the user.
 
 > `.prizmkit/prizm-docs/` uses a 3-level hierarchy: L0 (`root.prizm`) is the project-wide index. L1 (e.g., `auth.prizm`) covers a module — its key files, interfaces, dependencies, traps, and decisions. L2 is for sub-modules with their own complexity. Implement reads these docs to avoid repeating known mistakes; `/prizmkit-retrospective` is responsible for updating them after implementation.
 

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

@@ -181,8 +181,8 @@ Invoke prizmkit-prizm-docs (Init operation), passing the two-tier module structu
   - Generate `root.prizm` (L0) with project meta and MODULE_INDEX listing only top-level modules. If module count > 15, use MODULE_GROUPS format instead (group by functional domain).
   - For each module entry in MODULE_INDEX/MODULE_GROUPS, include keyword tags extracted from the module's source files — scan for: exported symbols, imported packages, domain terms in file/directory names. Format: `- module-name [tag1, tag2, tag3]: ...`. Tags help AI match user intent to relevant modules.
   - Generate L1 docs for top-level modules at `.prizmkit/prizm-docs/<M>.prizm` and for sub-modules at `.prizmkit/prizm-docs/<M>/<S>.prizm`
-  - Create `changelog.prizm`
   - Skip L2 (lazy generation) — L2 is generated on first file modification, saving tokens upfront
+  - Do not create auxiliary `changelog.prizm` or date/time metadata fields; git history is the source of change history
 
 **Phase 6: Workspace Initialization**
 6a. Create `.prizmkit/` directory structure (if missing):
@@ -314,7 +314,7 @@ Modules discovered:
 Project brief: inferred from codebase → confirmed by user
   → .prizmkit/plans/project-brief.md
 
-Generated: root.prizm + 4 L1 docs + changelog.prizm
+Generated: root.prizm + 4 L1 docs
 Saved: .prizmkit/config.json (tech_stack + detected_layers recorded)
 
 Next: Use /prizmkit-plan to start your first feature

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

@@ -86,7 +86,7 @@ OUTPUT: Migration report with list of source docs processed, generated .prizm fi
 
 - **root.prizm is corrupted or invalid format**: Back up the existing file, then run Rebuild on all modules to regenerate from source code.
 - **Broken pointers (-> references to non-existent files)**: Create the missing .prizm file if the source module exists; remove the pointer if the source module was deleted.
-- **Size limit exceeded**: For L0, consolidate MODULE_INDEX entries. For L1, move implementation details to L2. For L2, archive CHANGELOG entries older than 90 days.
+- **Size limit exceeded**: For L0, consolidate MODULE_INDEX entries. For L1, move implementation details to L2. For L2, trim non-essential derived detail and keep only durable project knowledge.
 - **No git history available**: Fall back to filesystem timestamps for freshness checks; warn user that accuracy may be reduced.
 
 ### Key Protocols (reference)
@@ -104,7 +104,6 @@ Generated .prizmkit/prizm-docs/:
   routes.prizm (L1) — 12 files, 4 interfaces
   models.prizm (L1) — 8 files, 3 interfaces
   services.prizm (L1) — 15 files, 6 interfaces
-  changelog.prizm — initial entry
 ```
 
 **Update after adding new API endpoint:**
@@ -113,5 +112,4 @@ Changed: src/routes/avatar.ts (A), src/models/user.ts (M)
 Updated: .prizmkit/prizm-docs/routes.prizm — added avatar.ts to KEY_FILES, new POST /api/avatar interface
 Updated: .prizmkit/prizm-docs/models.prizm — updated User interface with avatar_url field
 Skipped: .prizmkit/prizm-docs/services.prizm — no changes in services module
-Appended: changelog.prizm — "routes | add: avatar upload endpoint"
 ```

package/bundled/skills/prizmkit-prizm-docs/assets/prizm-docs-format.md

@@ -36,7 +36,7 @@ CORE_PRINCIPLES:
 - Progressive disclosure (load only what is needed)
 - Self-updating (docs stay fresh via commit-time hooks)
 - Universal (language and framework agnostic)
-- Append-only history (decisions and changelog never lose information)
+- Durable project knowledge over auxiliary history (decisions, traps, interfaces, dependencies)
 - Size-enforced (hard limits per level prevent bloat)
 - Lazy L2 generation (detail docs created on first modification or deep read, not during init)
 - Rules hierarchy (root.prizm RULES are authoritative, module RULES supplement only)
@@ -61,9 +61,6 @@ LEVELS:
   FILE: .prizmkit/prizm-docs/<mirrored-path>/<submodule>.prizm
   CONTAINS: interface signatures, data flow, full rules, TRAPS, DECISIONS, domain-specific sections, rejected approaches
 
-- Changelog: Append-only change log. Loaded at L0. No size limit but keep last 50 entries.
-  FILE: .prizmkit/prizm-docs/changelog.prizm
-
 ## 2.2 Directory Layout
 
 STRUCTURE: Mirrors source tree under .prizmkit/prizm-docs/
@@ -71,7 +68,6 @@ STRUCTURE: Mirrors source tree under .prizmkit/prizm-docs/
 EXAMPLE (Go project):
   .prizmkit/prizm-docs/
     root.prizm                            # L0
-    changelog.prizm                       # L0
     internal/
       logic.prizm                         # L1 for internal/logic/
       model.prizm                         # L1 for internal/model/
@@ -92,7 +88,6 @@ EXAMPLE (Go project):
 EXAMPLE (JS/TS project):
   .prizmkit/prizm-docs/
     root.prizm                            # L0
-    changelog.prizm                       # L0
     src/
       components.prizm                    # L1 for src/components/
       hooks.prizm                         # L1 for src/hooks/
@@ -104,7 +99,6 @@ EXAMPLE (JS/TS project):
 EXAMPLE (Python project):
   .prizmkit/prizm-docs/
     root.prizm                            # L0
-    changelog.prizm                       # L0
     app/
       models.prizm                        # L1 for app/models/
       views.prizm                         # L1 for app/views/
@@ -286,9 +280,6 @@ TEMPLATE:
   - <decision made within this module> — <rationale>
   - REJECTED: <approach that was tried/considered and abandoned + why>
 
-  CHANGELOG:
-  - <verb>: <description of recent change to this module>
-
 DOMAIN_SPECIFIC_SECTION_EXAMPLES:
 - For state machines: STATES, TRIGGERS, TRANSITIONS
 - For API handlers: ENDPOINTS, REQUEST_FORMAT, RESPONSE_FORMAT, ERROR_CODES
@@ -312,23 +303,11 @@ CONSTRAINTS:
 - FILES lists all files, not just key ones
 - RULES may only SUPPLEMENT root.prizm RULES with module-specific exceptions, never contradict them
 
-## 3.4 changelog.prizm
-
-TEMPLATE:
-
-  CHANGELOG:
-  - <module-path> | <verb>: <one-line description>
-
-VERBS: add, update, fix, remove, refactor, rename, deprecate
-RETENTION: Keep last 50 entries. Archive older entries to changelog-archive.prizm if needed.
-TEMPORAL_INFO: Git commit history is the authoritative source for when changes happened. No dates in changelog entries — git log on .prizmkit/prizm-docs/changelog.prizm provides the timeline.
+## 3.4 Metadata Policy
 
-EXAMPLE:
-  CHANGELOG:
-  - internal/logic/timer | add: retry logic with exponential backoff
-  - internal/service/sso | update: create_robot handler validates chatbot config
-  - internal/model/chatbot | add: DeepSeek provider model definition
-  - internal/repo/rpc | fix: Hunyuan API timeout not respected
+TEMPORAL_INFO: Git history is the authoritative source for change timing and edit history.
+AUXILIARY_FIELDS: Do not generate CHANGELOG or UPDATED fields in .prizm files.
+RATIONALE: Keep project memory focused on durable architecture, interfaces, dependencies, traps, rules, and decisions.
 
 ---
 
@@ -338,7 +317,6 @@ HEADERS: ALL CAPS followed by colon (MODULE:, FILES:, RESPONSIBILITY:, etc.)
 VALUES: Single space after colon, value on same line (KEY: value)
 LISTS: Dash-space prefix for items within a section (- item)
 POINTERS: Arrow notation (->) to reference other .prizm files
-CHANGELOG_SEPARATOR: Pipe (|) between module and description
 NESTING: Indent 2 spaces for sub-keys within a section
 COMMENTS: None. Every line carries information. No comments in .prizm files.
 TIMESTAMPS: No date/time fields in .prizm files. Git is the authoritative source for temporal information. Use `git log` or `git blame` on .prizm files when needed.
@@ -353,7 +331,6 @@ RULE: Mirror the source directory tree under .prizmkit/prizm-docs/
 RULE: L1 file for directory D = .prizmkit/prizm-docs/<D>.prizm
 RULE: L2 file for subdirectory D/S = .prizmkit/prizm-docs/<D>/<S>.prizm
 RULE: Root index = .prizmkit/prizm-docs/root.prizm (always)
-RULE: Changelog = .prizmkit/prizm-docs/changelog.prizm (always)
 
 ## 5.2 Examples
 
@@ -448,11 +425,11 @@ SUMMARY: Get changed files → map to modules → classify (A/D/M/R) → update
 
 DETAILED_STEPS: → ${SKILL_DIR}/references/op-update.md
 
-## 7.3 Changelog Update
+## 7.3 Auxiliary Metadata Policy
 
-ALWAYS append to .prizmkit/prizm-docs/changelog.prizm after any doc update.
-FORMAT: - <module-path> | <verb>: <one-line description>
-VERBS: add, update, fix, remove, refactor, rename, deprecate
+NEVER: Add CHANGELOG sections or changelog.prizm during doc sync.
+NEVER: Add UPDATED/date/time fields to .prizm files.
+RATIONALE: Git already provides history; .prizm files should store only durable project memory.
 
 ---
 
@@ -484,9 +461,9 @@ OPERATION: Init (invoked via prizmkit-prizm-docs skill)
 PRECONDITION: No .prizmkit/prizm-docs/ directory exists (or user confirms overwrite)
 
 INPUT: Project root directory
-OUTPUT: .prizmkit/prizm-docs/ with root.prizm, changelog.prizm, and L1 docs for discovered modules
+OUTPUT: .prizmkit/prizm-docs/ with root.prizm and L1 docs for discovered modules
 
-SUMMARY: Detect project type → discover modules (MODULE_DISCOVERY_CRITERIA) → create mirrored directory structure → generate root.prizm (L0) → generate L1 docs → skip L2 (lazy) → create changelog → configure hook → validate → report.
+SUMMARY: Detect project type → discover modules (MODULE_DISCOVERY_CRITERIA) → create mirrored directory structure → generate root.prizm (L0) → generate L1 docs → skip L2 (lazy) → configure hook → validate → report.
 
 DETAILED_STEPS: → ${SKILL_DIR}/references/op-init.md
 

package/bundled/skills/prizmkit-prizm-docs/references/op-init.md

@@ -13,7 +13,7 @@ STEPS:
    - HIERARCHY RULE: directory X inside top-level module M maps to .prizmkit/prizm-docs/<M>/<X>.prizm, never to .prizmkit/prizm-docs/<X>.prizm.
    - Exclude .git/, node_modules/, vendor/, build/, dist/, __pycache__/, target/, bin/, .claude/, .codebuddy/, .prizmkit/, .prizmkit/prizm-docs/, dev-pipeline/. If total module count > 30, ask user for include/exclude patterns.
 3. Create .prizmkit/prizm-docs/ directory structure mirroring the source tree exactly. For each top-level module M that has sub-modules, create the subdirectory .prizmkit/prizm-docs/<M>/.
-4. Generate root.prizm (L0) with PROJECT, LANG, FRAMEWORK, BUILD, TEST, ENTRY, MODULE_INDEX with multi-level entries as needed for efficient navigation (constrained by 4KB limit), RULES extracted from CODEBUDDY.md/CLAUDE.md/README/linter configs, PATTERNS, and CROSS_CUTTING (cross-module concerns spanning 2+ modules). Set PRIZM_VERSION: 4. Max 4KB. No UPDATED timestamp — git tracks modification times.
+4. Generate root.prizm (L0) with PROJECT, LANG, FRAMEWORK, BUILD, TEST, ENTRY, MODULE_INDEX with multi-level entries as needed for efficient navigation (constrained by 4KB limit), RULES extracted from CODEBUDDY.md/CLAUDE.md/README/linter configs, PATTERNS, and CROSS_CUTTING (cross-module concerns spanning 2+ modules). Set PRIZM_VERSION: 4. Max 4KB. No date/time metadata fields — git tracks modification times.
    - If `.prizmkit/plans/project-brief.md` exists: add `PROJECT_BRIEF: .prizmkit/plans/project-brief.md` to root.prizm (generated by prizmkit-init). If not present, skip — prizmkit-init Phase 7 will add it later.
    - If module count > 15: use MODULE_GROUPS format instead of MODULE_INDEX — group modules by functional domain (3-8 domains, inferred from directory structure and module responsibilities). See prizm-docs-format.md for MODULE_GROUPS format.
    - For each module entry, auto-generate 3-6 keyword tags by scanning the module's key source files for: exported function/class names, imported library names, domain-specific terms in file/directory names. Add tags in square brackets after the module name (e.g., `- auth [login, session, jwt]: ...`). Tags are optional but recommended for projects with 10+ modules.
@@ -22,10 +22,9 @@ STEPS:
    - Sub-module S inside M → write .prizmkit/prizm-docs/<M>/<S>.prizm
    Each L1 includes MODULE (full relative path), FILES count, RESPONSIBILITY, SUBDIRS with pointers, KEY_FILES (5-10 most important), DEPENDENCIES (imports, imported-by, external), RULES (1-3 most critical only). L1 does NOT include INTERFACES, DATA_FLOW, TRAPS, or DECISIONS (those are L2, generated lazily). Max 4KB each.
 6. Skip L2 docs during init — L2 is created lazily on first file modification or when AI needs deep understanding (ON_DEEP_READ trigger). L2 contains behavioral detail: INTERFACES, DATA_FLOW, TRAPS, DECISIONS, full RULES, domain-specific sections.
-7. Create changelog.prizm with initial entry: `- root | add: initialized prizm documentation framework`
-8. Configure UserPromptSubmit hook in platform settings per ${SKILL_DIR}/assets/prizm-docs-format.md.md Section 11.
-9. Validate all generated docs: size limits (L0 <= 4KB, L1 <= 4KB), pointer resolution (every -> reference resolves), no circular dependencies, KEY: value format compliance, no anti-patterns (prose, code blocks, markdown headers), L1 does not contain INTERFACES/DATA_FLOW/TRAPS/DECISIONS, no UPDATED timestamps (git is authority).
-10. Report summary: modules discovered, L1 docs generated, files excluded, warnings.
+7. Configure UserPromptSubmit hook in platform settings per ${SKILL_DIR}/assets/prizm-docs-format.md.md Section 11.
+8. Validate all generated docs: size limits (L0 <= 4KB, L1 <= 4KB), pointer resolution (every -> reference resolves), no circular dependencies, KEY: value format compliance, no anti-patterns (prose, code blocks, markdown headers), L1 does not contain INTERFACES/DATA_FLOW/TRAPS/DECISIONS, no date/time metadata fields (git is authority).
+9. Report summary: modules discovered, L1 docs generated, files excluded, warnings.
 
 OUTPUT: List of generated files, module count, and validation results.
 

package/bundled/skills/prizmkit-prizm-docs/references/op-rebuild.md

@@ -10,7 +10,6 @@ STEPS:
 3. Generate fresh L1 doc with full module analysis.
 4. Generate L2 docs for all sub-modules immediately (unlike init, rebuild generates L2 right away to capture current state).
 5. Update MODULE_INDEX (or MODULE_GROUPS) in root.prizm with new file counts and pointers. Re-evaluate grouping: if total module count > 15 and currently using MODULE_INDEX, convert to MODULE_GROUPS. Regenerate keyword tags for rebuilt modules. **Preserve** any `PROJECT_BRIEF:` line in root.prizm.
-6. Append rebuild entry to changelog.prizm: `- <module-path> | refactor: rebuilt module documentation from scratch`
-7. Validate regenerated docs against size limits and format rules.
+6. Validate regenerated docs against size limits and format rules.
 
 OUTPUT: Regenerated doc summary with before/after comparison.

package/bundled/skills/prizmkit-prizm-docs/references/op-update.md

@@ -8,12 +8,11 @@ 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 — this includes checking for modules that have source files but no L2 doc.
 2. Map changed files to modules by matching against MODULE_INDEX or MODULE_GROUPS 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 or MODULE_GROUPS counts, CROSS_CUTTING) only if structural change. No UPDATED timestamps — git tracks modification times. **Preserve** any `PROJECT_BRIEF:` line in root.prizm — it is managed by prizmkit-init, not by this skill.
+4. Update affected docs: L2 first (KEY_FILES, INTERFACES, DATA_FLOW, DEPENDENCIES, TRAPS, DECISIONS), then L1 (FILES count, KEY_FILES, DEPENDENCIES — L1 does NOT contain INTERFACES/DATA_FLOW/TRAPS/DECISIONS), then L0 (MODULE_INDEX or MODULE_GROUPS counts, CROSS_CUTTING) only if structural change. No date/time metadata fields — git tracks modification times. **Preserve** any `PROJECT_BRIEF:` line in root.prizm — it is managed by prizmkit-init, not by this skill.
 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 with sections: MODULE, FILES, RESPONSIBILITY, INTERFACES, DATA_FLOW, KEY_FILES, DEPENDENCIES, RULES, TRAPS, DECISIONS, CHANGELOG. 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 with sections: MODULE, FILES, RESPONSIBILITY, INTERFACES, DATA_FLOW, KEY_FILES, DEPENDENCIES, RULES, TRAPS, DECISIONS, CHANGELOG. This ensures Update fills documentation gaps left by previous sessions.
-7. Append entries to changelog.prizm using format: `- <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 .prizmkit/prizm-docs/`
+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 with sections: MODULE, FILES, RESPONSIBILITY, INTERFACES, DATA_FLOW, KEY_FILES, DEPENDENCIES, RULES, TRAPS, DECISIONS. 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 with sections: MODULE, FILES, RESPONSIBILITY, INTERFACES, DATA_FLOW, KEY_FILES, DEPENDENCIES, RULES, TRAPS, DECISIONS. This ensures Update fills documentation gaps left by previous sessions.
+7. Enforce size limits: L0 > 4KB -> consolidate. L1 > 4KB -> trim KEY_FILES descriptions, ensure RULES <= 3 entries. L2 > 5KB -> trim non-essential derived detail or split oversized cross-cutting detail.
+8. Stage updated .prizm files via `git add .prizmkit/prizm-docs/`
 
 OUTPUT: List of updated/created/skipped docs with reasons.

package/bundled/skills/prizmkit-prizm-docs/references/op-validate.md

@@ -5,7 +5,7 @@ Check format compliance and consistency of all .prizm docs.
 PRECONDITION: .prizmkit/prizm-docs/ exists.
 
 STEPS:
-1. FORMAT CHECK: Verify all .prizm files use KEY: value format. Flag any prose paragraphs, code blocks (```), markdown headers (##), emoji, ASCII art, or horizontal rules. Flag TRAPS entries missing severity prefix ([CRITICAL], [HIGH], or [LOW]). Note: [REVIEW] preceding severity (e.g., `[REVIEW][HIGH]`) is a valid temporary staleness marker, not a format violation.
+1. FORMAT CHECK: Verify all .prizm files use KEY: value format. Flag any prose paragraphs, code blocks (```), markdown headers (##), emoji, ASCII art, or horizontal rules. Flag TRAPS entries missing severity prefix ([CRITICAL], [HIGH], or [LOW]). Flag CHANGELOG/UPDATED/date-time metadata fields as auxiliary noise. Note: [REVIEW] preceding severity (e.g., `[REVIEW][HIGH]`) is a valid temporary staleness marker, not a format violation.
 2. SIZE CHECK: Verify size limits: L0 <= 4KB, L1 <= 4KB, L2 <= 5KB. Report files exceeding limits with current size.
 3. POINTER CHECK: Verify all arrow (->) references resolve to existing .prizm files. Report broken pointers.
 4. STALENESS CHECK: Compare git modification time of each .prizm file against source directory. Flag docs where source was modified more recently.

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

@@ -41,7 +41,7 @@ For initial doc setup, validation, or migration, use `/prizmkit-prizm-docs` inst
 Synchronize `.prizmkit/prizm-docs/` structure with actual codebase changes from this session.
 → Read `${SKILL_DIR}/references/structural-sync-steps.md` for the detailed procedure.
 
-**Key outputs**: Updated L1 file counts, L2 INTERFACES/DATA_FLOW, changelog entries, stale TRAPS cleanup.
+**Key outputs**: Synced L1 file counts, L2 INTERFACES/DATA_FLOW, DEPENDENCIES, and stale TRAPS cleanup.
 
 ---
 
@@ -70,14 +70,9 @@ Inject newly discovered project knowledge (TRAPS, RULES, DECISIONS) into archite
 
 ---
 
-## Final: Changelog + Stage
+## Final: Stage
 
-**3a.** Append to `.prizmkit/prizm-docs/changelog.prizm`:
-- Format: `<module-path> | <verb>: <one-line description>`
-- Verbs: add, update, fix, remove, refactor, rename, deprecate
-- One entry per meaningful change, not one per file
-
-**3b.** Stage all doc changes:
+**3a.** Stage all doc changes:
 ```bash
 git add .prizmkit/prizm-docs/
 ```
@@ -87,5 +82,4 @@ git add .prizmkit/prizm-docs/
 ## Output
 
 - `.prizmkit/prizm-docs/*.prizm` — Structurally synced + TRAPS/RULES/DECISIONS enriched
-- `.prizmkit/prizm-docs/changelog.prizm` — Appended entries
 - All `.prizmkit/prizm-docs/` changes staged via `git add`

package/bundled/skills/prizmkit-retrospective/references/knowledge-injection-steps.md

@@ -26,7 +26,7 @@ When writing TRAPS:
 - OPTIONAL: append `| STALE_IF: <glob>` when the TRAP is tightly coupled to specific files (for auto-expiry detection)
 
 **Consuming [REVIEW] markers** (from staleness check 1g):
-- If you encounter a TRAP prefixed with `[REVIEW]` (e.g., `[REVIEW][HIGH] ...`), verify whether the trap is still valid by checking the current code. If still valid: remove the `[REVIEW]` prefix, keeping the severity. If no longer relevant: delete the TRAP entry and append CHANGELOG.
+- If you encounter a TRAP prefixed with `[REVIEW]` (e.g., `[REVIEW][HIGH] ...`), verify whether the trap is still valid by checking the current code. If still valid: remove the `[REVIEW]` prefix, keeping the severity. If no longer relevant: delete the TRAP entry.
 
 **RULES** — conventions established or constraints discovered:
 - Format: `- MUST/NEVER/PREFER: <rule>`

package/bundled/skills/prizmkit-retrospective/references/structural-sync-steps.md

@@ -15,7 +15,7 @@ git diff HEAD --name-status
 
 **1d.** Update affected docs (bottom-up: L2 → L1 → L0):
 
-- **L2**: If L2 exists → update **only the sections affected by the diff files in this module**. For example, if only `api.js` changed: update its KEY_FILES entry, its INTERFACES (if exports changed), its DEPENDENCIES (if imports changed). Do NOT re-scan unchanged files in the module. If L2 does NOT exist AND the module has Added or Modified source files in the current diff with meaningful logic (not trivial config) → create L2 with these sections: MODULE, FILES, RESPONSIBILITY, INTERFACES, DATA_FLOW, KEY_FILES, DEPENDENCIES, RULES, TRAPS, DECISIONS, CHANGELOG. Populate **only from the diff files** (the Added/Modified files in this module from step 1a), not from the entire module directory.
+- **L2**: If L2 exists → update **only the sections affected by the diff files in this module**. For example, if only `api.js` changed: update its KEY_FILES entry, its INTERFACES (if exports changed), its DEPENDENCIES (if imports changed). Do NOT re-scan unchanged files in the module. If L2 does NOT exist AND the module has Added or Modified source files in the current diff with meaningful logic (not trivial config) → create L2 with these sections: MODULE, FILES, RESPONSIBILITY, INTERFACES, DATA_FLOW, KEY_FILES, DEPENDENCIES, RULES, TRAPS, DECISIONS. Populate **only from the diff files** (the Added/Modified files in this module from step 1a), not from the entire module directory.
 - **L1**: Update FILES count, KEY_FILES (if major files added/removed), DEPENDENCIES (if module-level deps changed). **L1 does NOT contain INTERFACES, DATA_FLOW, TRAPS, or DECISIONS** — those belong in L2 only.
 - **L0 root.prizm**: Update MODULE_INDEX file counts only if counts changed. Update CROSS_CUTTING if cross-module concerns changed. Update only if structural change (module added/removed). **Preserve** any `PROJECT_BRIEF:` line — it is managed by prizmkit-init.
 
@@ -27,14 +27,14 @@ git diff HEAD --name-status
 **1f.** Enforce size limits:
 - L0 > 4KB → if using MODULE_INDEX with > 15 entries, convert to MODULE_GROUPS format (group by functional domain). Otherwise, consolidate MODULE_INDEX descriptions.
 - L1 > 4KB → trim KEY_FILES descriptions, ensure RULES <= 3 entries
-- L2 > 5KB → archive old CHANGELOG entries
+- L2 > 5KB → trim non-essential detail, split oversized cross-cutting detail, or move derived context back to source references
 
 **SKIP structural sync if**: only internal implementation changed (no interface/dependency impact), only comments/whitespace, only .prizm files. **DO NOT skip** test file changes or bug fixes — they may reveal TRAPS worth capturing in L2.
 
 **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`) → delete the TRAP entry, append CHANGELOG: `remove: archived stale TRAP - <summary>`
+1. If a TRAP has `STALE_IF:` and the glob-matched files no longer exist (verified via `ls`) → delete the TRAP entry
 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)
 

package/package.json

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