prizmkit 1.0.34 → 1.0.35

package/bundled/VERSION.json

@@ -1,5 +1,5 @@
 {
-  "frameworkVersion": "1.0.34",
-  "bundledAt": "2026-03-17T12:56:01.113Z",
-  "bundledFrom": "68ce087"
+  "frameworkVersion": "1.0.35",
+  "bundledAt": "2026-03-17T13:12:38.845Z",
+  "bundledFrom": "2597a15"
 }

package/bundled/agents/prizm-dev-team-dev.md

@@ -101,12 +101,3 @@ DEV-14: 若 `npm test` 中存在 pre-existing 失败，不得忽略——必须
 - 发送 ESCALATION 上报接口歧义或任务阻塞
 - 接收 TASK_ASSIGNMENT 获取分配的工作
 
-### Framework Self-Development Rules (self-evolve mode)
-
-When working in self-evolve mode (developing the PrizmKit framework itself), these additional rules apply:
-
-1. **Skill metadata sync**: If you modify any file in `core/skills/<skill-name>/`, you MUST also update `core/skills/<skill-name>/_metadata.json` to reflect changes (description, version, dependencies).
-2. **Template variable check**: If you modify any file in `dev-pipeline/templates/`, verify all `{{PLACEHOLDER}}` markers are resolvable by checking `dev-pipeline/scripts/generate-bootstrap-prompt.py` for matching entries.
-3. **Pre-completion validation**: Before marking implementation complete, run `node tests/validate-all.js` and fix any failures.
-4. **Bundle protection**: NEVER directly modify files in `create-prizmkit/bundled/`. These are auto-generated by `scripts/bundle.js` — your changes would be overwritten.
-5. **Reload tracking**: If you modify files in `dev-pipeline/scripts/`, `dev-pipeline/templates/`, or `core/skills/` that the pipeline actively uses, note this in your Implementation Log so the orchestrator can set `reload_needed: true`.

package/bundled/agents/prizm-dev-team-reviewer.md

@@ -122,12 +122,3 @@ REV-10: 禁止使用 timeout 命令（macOS 不兼容）。运行测试时直接
 - 发送 ISSUE_REPORT 报告 CRITICAL 发现
 - 接收 TASK_ASSIGNMENT 获取分配的工作
 
-### Framework Self-Development Review (self-evolve mode)
-
-When reviewing in self-evolve mode (framework is modifying itself), add these review dimensions:
-
-1. **`_metadata.json` ↔ skill directory 1:1 mapping**: Verify every `core/skills/*/` has a `_metadata.json`, and every `_metadata.json` references a valid skill directory. Run `node tests/validate-all.js` to automate this check.
-2. **Template variable completeness**: For modified `dev-pipeline/templates/*.md` files, verify all `{{PLACEHOLDER}}` markers have matching open/close tags and are resolvable by `generate-bootstrap-prompt.py`.
-3. **Agent frontmatter validation**: For modified `core/agents/*.md` files, validate YAML frontmatter contains required fields: `name`, `description`, `tools`. Optionally check `model`, `skills`.
-4. **CI gate execution**: Run `npm run ci` and report the full result. Any failure here is **CRITICAL** severity — the framework must always ship green.
-5. **Bundle safety check**: Verify no files in `create-prizmkit/bundled/` were directly modified (use `git diff --name-only` to check). Direct modifications to bundled assets are always CRITICAL.

package/bundled/skills/_metadata.json

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

package/bundled/dev-pipeline/scripts/validate-framework.sh

@@ -1,87 +0,0 @@
-#!/usr/bin/env bash
-set -euo pipefail
-
-# ============================================================
-# validate-framework.sh — Framework CI Pipeline for Self-Evolve Mode
-#
-# Runs the full PrizmKit framework validation pipeline step by step,
-# reporting each stage individually so agents can pinpoint failures.
-#
-# Steps:
-#   1. validate-all.js  — structural validation (skills, agents, metadata)
-#   2. bundle.js        — rebuild bundled assets
-#   3. verify-bundle.js — verify bundle integrity
-#   4. eslint           — lint check
-#   5. vitest           — unit tests
-#
-# Usage:
-#   bash dev-pipeline/scripts/validate-framework.sh
-# ============================================================
-
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-PROJECT_ROOT="$(cd "$SCRIPT_DIR/../.." && pwd)"
-
-RED='\033[0;31m'
-GREEN='\033[0;32m'
-YELLOW='\033[1;33m'
-BOLD='\033[1m'
-NC='\033[0m'
-
-pass_count=0
-fail_count=0
-failed_steps=()
-
-run_step() {
-    local step_name="$1"
-    shift
-    local cmd="$*"
-
-    echo ""
-    echo -e "${BOLD}[$step_name]${NC} Running: $cmd"
-    echo "────────────────────────────────────────"
-
-    if (cd "$PROJECT_ROOT" && eval "$cmd"); then
-        echo -e "${GREEN}✓ $step_name passed${NC}"
-        pass_count=$((pass_count + 1))
-    else
-        echo -e "${RED}✗ $step_name FAILED${NC}"
-        fail_count=$((fail_count + 1))
-        failed_steps+=("$step_name")
-    fi
-}
-
-echo ""
-echo -e "${BOLD}════════════════════════════════════════════════════${NC}"
-echo -e "${BOLD}  PrizmKit Framework Validation Pipeline${NC}"
-echo -e "${BOLD}════════════════════════════════════════════════════${NC}"
-
-# Step 1: Structural validation
-run_step "validate-all" "node tests/validate-all.js"
-
-# Step 2: Bundle rebuild
-run_step "bundle" "node scripts/bundle.js"
-
-# Step 3: Verify bundle integrity
-run_step "verify-bundle" "node scripts/verify-bundle.js"
-
-# Step 4: Lint
-run_step "eslint" "npx eslint . --max-warnings 0 2>/dev/null || npx eslint ."
-
-# Step 5: Unit tests
-run_step "vitest" "npx vitest run --reporter=verbose 2>&1 || npx vitest run"
-
-# Summary
-echo ""
-echo -e "${BOLD}════════════════════════════════════════════════════${NC}"
-if [[ $fail_count -eq 0 ]]; then
-    echo -e "${GREEN}  All $pass_count steps passed ✓${NC}"
-    echo -e "${BOLD}════════════════════════════════════════════════════${NC}"
-    exit 0
-else
-    echo -e "${RED}  $fail_count/$((pass_count + fail_count)) steps FAILED:${NC}"
-    for step in "${failed_steps[@]}"; do
-        echo -e "${RED}    - $step${NC}"
-    done
-    echo -e "${BOLD}════════════════════════════════════════════════════${NC}"
-    exit 1
-fi