prizmkit 1.1.42 → 1.1.47

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

@@ -81,7 +81,7 @@ If any agent times out:
 ### Phase 0: Project Bootstrap
 - Run `/prizmkit-init` (invoke the prizmkit-init skill)
 - Run `python3 {{INIT_SCRIPT_PATH}} --project-root {{PROJECT_ROOT}} --feature-id {{FEATURE_ID}} --feature-slug {{FEATURE_SLUG}}`
-- **CP-0**: Verify `.prizm-docs/root.prizm`, `.prizmkit/config.json` exist
+- **CP-0**: Verify `.prizmkit/prizm-docs/root.prizm`, `.prizmkit/config.json` exist
 {{END_IF_INIT_NEEDED}}
 {{IF_INIT_DONE}}
 ### Phase 0: Record Test Baseline & Detect Test Commands
@@ -134,7 +134,7 @@ If `EXISTING_CODE` is non-empty: your spec/plan/tasks must reflect this existing
 
 **Step A — Build Context Snapshot** (skip if `context-snapshot.md` already exists):
 
-1. Read `.prizm-docs/root.prizm` and relevant L1/L2 prizm docs
+1. Read `.prizmkit/prizm-docs/root.prizm` and relevant L1/L2 prizm docs
 2. Detect source code directories: read KEY_FILES and STRUCTURE sections from `root.prizm` to identify where source code lives (e.g. `src/`, `app/`, `lib/`, `cmd/`, `packages/`, or project root). If `root.prizm` is missing, scan the project tree:
    ```bash
    find . -maxdepth 2 -type f \( -name "*.js" -o -name "*.ts" -o -name "*.py" -o -name "*.go" -o -name "*.java" -o -name "*.rb" -o -name "*.rs" \) -not -path '*/node_modules/*' -not -path '*/.git/*' -not -path '*/dist/*' -not -path '*/build/*' -not -path '*/vendor/*' | head -30
@@ -159,7 +159,7 @@ If `EXISTING_CODE` is non-empty: your spec/plan/tasks must reflect this existing
      |------|-----------|----------------|
      | `<source-dir>/security/permission-guard.js` | Permission check integration | `checkCommandPermission(userId, cmd)` |
 
-     ### Known TRAPS (from .prizm-docs/)
+     ### Known TRAPS (from .prizmkit/prizm-docs/)
      - <trap entries extracted from L1/L2 docs>
    - **Section 5 — Existing Tests**: full content of related test files as code blocks
 4. Confirm: `ls .prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md`
@@ -221,7 +221,7 @@ Prompt:
 > "Read {{CRITIC_SUBAGENT_PATH}}. For feature {{FEATURE_ID}} (slug: {{FEATURE_SLUG}}):
 > **MODE: Plan Challenge**
 > 1. Read `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` FIRST — Section 3 has project context, Section 4 has file manifest.
-> 2. Read `.prizm-docs/root.prizm` and relevant L1/L2 docs for affected modules.
+> 2. Read `.prizmkit/prizm-docs/root.prizm` and relevant L1/L2 docs for affected modules.
 > 3. Read existing source files in the modules this plan touches.
 > 4. Challenge plan.md against the project's existing architecture, patterns, and style.
 > Write `.prizmkit/specs/{{FEATURE_SLUG}}/challenge-report.md` with findings (or 'No significant challenges')."
@@ -516,23 +516,23 @@ git log --oneline | grep "{{FEATURE_ID}}" | head -3
 - If a commit for `{{FEATURE_ID}}` already exists → **skip 6d** (do NOT run /prizmkit-committer, do NOT run git reset, do NOT stage or unstage anything). Proceed directly to 6e Final verification.
 - If no existing commit → proceed normally with 6b–6d.
 
-**6b.** Run `/prizmkit-retrospective` (**before commit**, maintains `.prizm-docs/` architecture index):
+**6b.** Run `/prizmkit-retrospective` (**before commit**, maintains `.prizmkit/prizm-docs/` architecture index):
 - **Structural sync**: update KEY_FILES/INTERFACES/DEPENDENCIES/file counts for changed modules
-- **Architecture knowledge** (feature sessions only): extract TRAPS, RULES, DECISIONS from completed work into `.prizm-docs/`
+- **Architecture knowledge** (feature sessions only): extract TRAPS, RULES, DECISIONS from completed work into `.prizmkit/prizm-docs/`
 - **L2 coverage check**: For any module/sub-module with source files created or significantly modified in this session but no L2 `.prizm` doc — evaluate whether L2 is warranted and create if so. The current session has the best context for accurate KEY_FILES, TRAPS, and DECISIONS.
-- Stage doc changes: `git add .prizm-docs/`
+- Stage doc changes: `git add .prizmkit/prizm-docs/`
 ⚠️ Do NOT commit here. Only stage.
 - **For bug-fix sessions**: structural sync (Job 1) by default. Run knowledge injection (Job 2) when the fix causes interface signature changes, dependency additions/removals, observable behavior changes, or reveals new TRAPs
 
 **6c.** Stage all feature code explicitly (NEVER use `git add -A` or `git add .`):
 ```bash
 git add <specific-files-created-or-modified>
-git add .prizm-docs/
+git add .prizmkit/prizm-docs/
 ```
 
 **6d.** Run `/prizmkit-committer` → THE ONLY commit for this feature:
 `feat({{FEATURE_ID}}): {{FEATURE_TITLE}}`
-This single commit includes: feature code + tests + .prizm-docs/ updates. Do NOT push.
+This single commit includes: feature code + tests + .prizmkit/prizm-docs/ updates. Do NOT push.
 - MANDATORY: commit must be done via `/prizmkit-committer` skill. Do NOT run manual `git add`/`git commit` as a substitute.
 - Do NOT run `update-feature-status.py` here — the pipeline runner handles feature-list.json updates automatically after session exit.
 

package/bundled/dev-pipeline/templates/bugfix-bootstrap-prompt.md

@@ -116,10 +116,10 @@ If the bug is related to UI/frontend, you may use these tools to:
 
 **Step 1 — Diagnose the bug**:
 
-1. Read `.prizm-docs/root.prizm` and relevant L1/L2 docs for affected modules
+1. Read `.prizmkit/prizm-docs/root.prizm` and relevant L1/L2 docs for affected modules
 2. Trace the bug:
    - Classify error type (Runtime / Network / Auth / Data / Logic / Config / External)
-   - Check `.prizm-docs/` TRAPS sections for matching known issues
+   - Check `.prizmkit/prizm-docs/` TRAPS sections for matching known issues
    - Trace call chain from error source to root cause
    - Identify all affected files and modules
 3. Read the affected source files and related test files
@@ -130,7 +130,7 @@ Write `.prizmkit/bugfix/{{BUG_ID}}/context-snapshot.md`:
 - **Section 1 — Bug Brief**: bug description + acceptance criteria + root cause analysis
 - **Section 2 — Affected Files**: full verbatim content of each affected source file
 - **Section 3 — Existing Tests**: full content of related test files
-- **Section 4 — Prizm Context**: relevant TRAPS, RULES from .prizm-docs/
+- **Section 4 — Prizm Context**: relevant TRAPS, RULES from .prizmkit/prizm-docs/
 
 **Step 3 — Plan the fix**:
 
@@ -228,16 +228,16 @@ Run `/prizmkit-code-review` with `artifact_dir=.prizmkit/bugfix/{{BUG_ID}}/`:
 - **Full retrospective** (Job 1 + Job 2): Only when the fix causes interface signature changes, dependency additions/removals, observable behavior changes, or reveals new TRAPs.
 
 **a.** If a new pitfall was discovered (not previously in TRAPS):
-   - Update the affected module's TRAPS section in `.prizm-docs/`
+   - Update the affected module's TRAPS section in `.prizmkit/prizm-docs/`
    - Format: `- TRAP: <description> | FIX: <solution> | DATE: YYYY-MM-DD`
 
 **b.** Run `/prizmkit-retrospective` following the policy above.
-   Stage doc changes: `git add .prizm-docs/`
+   Stage doc changes: `git add .prizmkit/prizm-docs/`
 
 **c.** Stage all changed files explicitly (NEVER use `git add -A` or `git add .`):
 ```bash
 git add <specific-files-modified>
-git add .prizm-docs/
+git add .prizmkit/prizm-docs/
 ```
 
 **d.** Run `/prizmkit-committer --headless`:

package/bundled/dev-pipeline/templates/refactor-bootstrap-prompt.md

@@ -166,7 +166,7 @@ Include browser verification approach in plan.md:
 - Spawn Dev agent (Agent tool, subagent_type="prizm-dev-team-dev", run_in_background=false)
   Prompt: "Read {{DEV_SUBAGENT_PATH}}. For refactor {{REFACTOR_ID}} ('{{REFACTOR_TITLE}}'):
   1. Read `.prizmkit/refactor/{{REFACTOR_ID}}/spec.md` and `.prizmkit/refactor/{{REFACTOR_ID}}/plan.md`
-  2. Read `.prizm-docs/` for affected modules (TRAPS, RULES, PATTERNS)
+  2. Read `.prizmkit/prizm-docs/` for affected modules (TRAPS, RULES, PATTERNS)
   3. Before making any changes, run the existing test suite to establish a green baseline
   4. Run `/prizmkit-implement` with `artifact_dir=.prizmkit/refactor/{{REFACTOR_ID}}/` — this handles the full implementation cycle:
      - Reads plan.md Tasks section
@@ -233,7 +233,7 @@ Include browser verification approach in plan.md:
 
 **This phase is executed by YOU (the orchestrator), NOT a subagent.**
 
-1. Run `/prizmkit-retrospective` (full sync — Job 1 + Job 2) to update `.prizm-docs/` with structural changes
+1. Run `/prizmkit-retrospective` (full sync — Job 1 + Job 2) to update `.prizmkit/prizm-docs/` with structural changes
 
 2. Run `/prizmkit-committer --headless` with:
    - Commit message: `refactor({{REFACTOR_ID}}): {{REFACTOR_TITLE}}`
@@ -271,7 +271,7 @@ Include browser verification approach in plan.md:
    ```
    Rules: focus on structural changes, new module boundaries, renamed/moved files, changed interfaces. 3-8 notes, each under 120 chars.
 
-- **CP-RF-4**: Commit recorded, refactor-report.md written, .prizm-docs/ updated
+- **CP-RF-4**: Commit recorded, refactor-report.md written, .prizmkit/prizm-docs/ updated
 - **Checkpoint update**: set steps `prizmkit-committer` and `refactor-report` to `"completed"` in `{{CHECKPOINT_PATH}}`
 
 ### Step 3: Report Session Status

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

@@ -7,22 +7,22 @@ git log --oneline | grep "{{FEATURE_ID}}" | head -3
 - If a commit for `{{FEATURE_ID}}` already exists → **skip d** (do NOT run /prizmkit-committer, do NOT run git reset, do NOT stage or unstage anything). Proceed directly to e Final verification.
 - If no existing commit → proceed normally with b–d.
 
-**b.** Run `/prizmkit-retrospective` (**before commit**, maintains `.prizm-docs/` architecture index):
+**b.** Run `/prizmkit-retrospective` (**before commit**, maintains `.prizmkit/prizm-docs/` architecture index):
 1. **Structural sync**: update KEY_FILES/INTERFACES/DEPENDENCIES/file counts for changed modules
-2. **Architecture knowledge**: extract TRAPS, RULES, DECISIONS from completed work into `.prizm-docs/`
+2. **Architecture knowledge**: extract TRAPS, RULES, DECISIONS from completed work into `.prizmkit/prizm-docs/`
 3. **L2 coverage check**: For any module/sub-module with source files created or significantly modified in this session but no L2 `.prizm` doc — evaluate whether L2 is warranted and create if so. The current session has the best context for accurate KEY_FILES, TRAPS, and DECISIONS.
-4. Stage doc changes: `git add .prizm-docs/`
+4. Stage doc changes: `git add .prizmkit/prizm-docs/`
 ⚠️ Do NOT commit here. Only stage.
 
 **c.** Stage all feature code explicitly (NEVER use `git add -A` or `git add .`):
 ```bash
 git add <specific-files-created-or-modified>
-git add .prizm-docs/
+git add .prizmkit/prizm-docs/
 ```
 
 **d.** Run `/prizmkit-committer` → THE ONLY commit for this feature:
 `feat({{FEATURE_ID}}): {{FEATURE_TITLE}}`
-This single commit includes: feature code + tests + .prizm-docs/ updates. Do NOT push.
+This single commit includes: feature code + tests + .prizmkit/prizm-docs/ updates. Do NOT push.
 - MANDATORY: commit must be done via `/prizmkit-committer` skill. Do NOT run manual `git add`/`git commit` as a substitute.
 - Do NOT run `update-feature-status.py` here — the pipeline runner handles feature-list.json updates automatically after session exit.
 

package/bundled/dev-pipeline/templates/sections/phase-commit.md

@@ -1,21 +1,21 @@
 ### Architecture Sync & Commit (SINGLE COMMIT)
 
-**a.** Run `/prizmkit-retrospective` — maintains `.prizm-docs/` (architecture index):
-1. **Structural sync**: Use `git diff --cached --name-status` to locate changed modules, update KEY_FILES/INTERFACES/DEPENDENCIES/file counts in affected `.prizm-docs/` files
-2. **Architecture knowledge** (feature sessions only): Extract TRAPS/RULES/DECISIONS from completed work into `.prizm-docs/`
+**a.** Run `/prizmkit-retrospective` — maintains `.prizmkit/prizm-docs/` (architecture index):
+1. **Structural sync**: Use `git diff --cached --name-status` to locate changed modules, update KEY_FILES/INTERFACES/DEPENDENCIES/file counts in affected `.prizmkit/prizm-docs/` files
+2. **Architecture knowledge** (feature sessions only): Extract TRAPS/RULES/DECISIONS from completed work into `.prizmkit/prizm-docs/`
 3. **L2 coverage check**: For any module/sub-module with source files created or significantly modified in this session but no L2 `.prizm` doc — evaluate whether L2 is warranted and create if so. The current session has the best context for accurate KEY_FILES, TRAPS, and DECISIONS.
-4. Stage doc changes: `git add .prizm-docs/`
+4. Stage doc changes: `git add .prizmkit/prizm-docs/`
 ⚠️ Do NOT commit here. Only stage.
 
 **b.** Stage all feature code explicitly (NEVER use `git add -A` or `git add .`):
 ```bash
 git add <specific-files-created-or-modified>
-git add .prizm-docs/
+git add .prizmkit/prizm-docs/
 ```
 
 **c.** Run `/prizmkit-committer` → THE ONLY commit for this feature:
 `feat({{FEATURE_ID}}): {{FEATURE_TITLE}}`
-This single commit includes: feature code + tests + .prizm-docs/ updates. Do NOT push.
+This single commit includes: feature code + tests + .prizmkit/prizm-docs/ updates. Do NOT push.
 - MANDATORY: commit must be done via `/prizmkit-committer` skill. Do NOT run manual `git add`/`git commit` as a substitute.
 - Do NOT run `update-feature-status.py` here — the pipeline runner handles feature-list.json updates automatically after session exit.
 

package/bundled/dev-pipeline/templates/sections/phase-context-snapshot-agent-suffix.md

@@ -10,7 +10,7 @@
      |------|-----------|----------------|
      | `<source-dir>/security/permission-guard.js` | Permission check integration | `checkCommandPermission(userId, cmd)` |
 
-     ### Known TRAPS (from .prizm-docs/)
+     ### Known TRAPS (from .prizmkit/prizm-docs/)
      - <trap entries extracted from L1/L2 docs>
 
 

package/bundled/dev-pipeline/templates/sections/phase-context-snapshot-base.md

@@ -5,7 +5,7 @@ ls .prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md 2>/dev/null && echo "EXI
 ```
 
 If MISSING — build it now:
-1. Read `.prizm-docs/root.prizm` and relevant L1/L2 prizm docs
+1. Read `.prizmkit/prizm-docs/root.prizm` and relevant L1/L2 prizm docs
 2. Detect source code directories: read KEY_FILES and STRUCTURE sections from `root.prizm` to identify where source code lives (e.g. `src/`, `app/`, `lib/`, `cmd/`, `packages/`, or project root). If `root.prizm` is missing, scan the project tree:
    ```bash
    find . -maxdepth 2 -type f \( -name "*.js" -o -name "*.ts" -o -name "*.py" -o -name "*.go" -o -name "*.java" -o -name "*.rb" -o -name "*.rs" \) -not -path '*/node_modules/*' -not -path '*/.git/*' -not -path '*/dist/*' -not -path '*/build/*' -not -path '*/vendor/*' | head -30

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

@@ -11,7 +11,7 @@ ls .prizmkit/specs/{{FEATURE_SLUG}}/ 2>/dev/null
 
 **Step A — Build Context Snapshot** (skip if `context-snapshot.md` already exists):
 
-1. Read `.prizm-docs/root.prizm` and relevant L1/L2 prizm docs
+1. Read `.prizmkit/prizm-docs/root.prizm` and relevant L1/L2 prizm docs
 2. Detect source code directories: read KEY_FILES and STRUCTURE sections from `root.prizm` to identify where source code lives (e.g. `src/`, `app/`, `lib/`, `cmd/`, `packages/`, or project root). If `root.prizm` is missing, scan the project tree:
    ```bash
    find . -maxdepth 2 -type f \( -name "*.js" -o -name "*.ts" -o -name "*.py" -o -name "*.go" -o -name "*.java" -o -name "*.rb" -o -name "*.rs" \) -not -path '*/node_modules/*' -not -path '*/.git/*' -not -path '*/dist/*' -not -path '*/build/*' -not -path '*/vendor/*' | head -30
@@ -36,7 +36,7 @@ ls .prizmkit/specs/{{FEATURE_SLUG}}/ 2>/dev/null
      |------|-----------|----------------|
      | `<source-dir>/security/permission-guard.js` | Permission check integration | `checkCommandPermission(userId, cmd)` |
 
-     ### Known TRAPS (from .prizm-docs/)
+     ### Known TRAPS (from .prizmkit/prizm-docs/)
      - <trap entries extracted from L1/L2 docs>
    - **Section 5 — Existing Tests**: full content of related test files as code blocks
 5. Confirm: `ls .prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md`

package/bundled/dev-pipeline/templates/sections/phase0-init.md

@@ -1,7 +1,7 @@
 ### Phase 0: Project Bootstrap
 - Run `/prizmkit-init` (invoke the prizmkit-init skill)
 - Run `python3 {{INIT_SCRIPT_PATH}} --project-root {{PROJECT_ROOT}} --feature-id {{FEATURE_ID}} --feature-slug {{FEATURE_SLUG}}`
-- **CP-0**: Verify `.prizm-docs/root.prizm`, `.prizmkit/config.json` exist
+- **CP-0**: Verify `.prizmkit/prizm-docs/root.prizm`, `.prizmkit/config.json` exist
 
 
 **Checkpoint update**: Update `workflow-checkpoint.json` — set step `prizmkit-init` to `"completed"`.

package/bundled/dev-pipeline/tests/test-path-resolution.sh

@@ -0,0 +1,100 @@
+#!/usr/bin/env bash
+# Test path resolution in lib/common.sh across:
+#   1. Framework repo-source layout  (<repo>/dev-pipeline/lib/common.sh)
+#   2. User-install layout           (<proj>/.prizmkit/dev-pipeline/lib/common.sh)
+#   3. Caller pre-set override       (test mocks PRIZMKIT_DIR / PROJECT_ROOT)
+#
+# Run: bash dev-pipeline/tests/test-path-resolution.sh
+set -euo pipefail
+
+SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
+REPO_ROOT="$(cd "$SCRIPT_DIR/../.." && pwd)"
+COMMON_SH="$REPO_ROOT/dev-pipeline/lib/common.sh"
+
+RED='\033[0;31m'
+GREEN='\033[0;32m'
+NC='\033[0m'
+
+PASS=0
+FAIL=0
+
+pass() { echo -e "  ${GREEN}PASS${NC} $1"; PASS=$((PASS + 1)); }
+fail() { echo -e "  ${RED}FAIL${NC} $1 — $2"; FAIL=$((FAIL + 1)); }
+
+# Helper: source common.sh in a clean subshell with given env, echo the three
+# resolved paths as PIPELINE_DIR|PRIZMKIT_DIR|PROJECT_ROOT.
+resolve() {
+    env -i HOME="$HOME" PATH="$PATH" "$@" bash -c "
+        source '$COMMON_SH' >/dev/null 2>&1
+        printf '%s|%s|%s\n' \"\$PIPELINE_DIR\" \"\$PRIZMKIT_DIR\" \"\$PROJECT_ROOT\"
+    "
+}
+
+echo "================================="
+echo " Path Resolution Tests"
+echo "================================="
+
+# --- Test 1: Framework repo-source layout ---
+# common.sh located at <repo>/dev-pipeline/lib/common.sh.
+# PIPELINE_DIR -> <repo>/dev-pipeline
+# PRIZMKIT_DIR -> <repo>/.prizmkit
+# PROJECT_ROOT -> <repo>
+echo "[Test 1] Repo-source layout"
+result=$(resolve)
+IFS='|' read -r pipeline prizmkit project <<<"$result"
+[[ "$pipeline" == "$REPO_ROOT/dev-pipeline" ]] \
+    && pass "PIPELINE_DIR=$pipeline" \
+    || fail "PIPELINE_DIR" "got: $pipeline"
+[[ "$prizmkit" == "$REPO_ROOT/.prizmkit" ]] \
+    && pass "PRIZMKIT_DIR=$prizmkit" \
+    || fail "PRIZMKIT_DIR" "got: $prizmkit"
+[[ "$project" == "$REPO_ROOT" ]] \
+    && pass "PROJECT_ROOT=$project" \
+    || fail "PROJECT_ROOT" "got: $project"
+
+# --- Test 2: User-install layout (.prizmkit/dev-pipeline) ---
+# Build a tmp dir resembling: <tmp>/proj/.prizmkit/dev-pipeline/lib/common.sh
+TMP_INSTALL=$(mktemp -d)
+trap 'rm -rf "$TMP_INSTALL"' EXIT
+mkdir -p "$TMP_INSTALL/proj/.prizmkit/dev-pipeline/lib"
+cp "$COMMON_SH" "$TMP_INSTALL/proj/.prizmkit/dev-pipeline/lib/common.sh"
+
+echo "[Test 2] User-install layout"
+result=$(env -i HOME="$HOME" PATH="$PATH" bash -c "
+    source '$TMP_INSTALL/proj/.prizmkit/dev-pipeline/lib/common.sh' >/dev/null 2>&1
+    printf '%s|%s|%s\n' \"\$PIPELINE_DIR\" \"\$PRIZMKIT_DIR\" \"\$PROJECT_ROOT\"
+")
+IFS='|' read -r pipeline prizmkit project <<<"$result"
+[[ "$pipeline" == "$TMP_INSTALL/proj/.prizmkit/dev-pipeline" ]] \
+    && pass "PIPELINE_DIR=$pipeline" \
+    || fail "PIPELINE_DIR" "got: $pipeline"
+[[ "$prizmkit" == "$TMP_INSTALL/proj/.prizmkit" ]] \
+    && pass "PRIZMKIT_DIR=$prizmkit" \
+    || fail "PRIZMKIT_DIR" "got: $prizmkit"
+[[ "$project" == "$TMP_INSTALL/proj" ]] \
+    && pass "PROJECT_ROOT=$project" \
+    || fail "PROJECT_ROOT" "got: $project"
+
+# --- Test 3: Caller pre-set override (test mocking) ---
+echo "[Test 3] Caller-supplied env vars override detection"
+result=$(resolve \
+    PIPELINE_DIR=/mock/pipeline \
+    PRIZMKIT_DIR=/mock/.prizmkit \
+    PROJECT_ROOT=/mock/proj)
+IFS='|' read -r pipeline prizmkit project <<<"$result"
+[[ "$pipeline" == "/mock/pipeline" ]] \
+    && pass "PIPELINE_DIR honored override" \
+    || fail "PIPELINE_DIR override" "got: $pipeline"
+[[ "$prizmkit" == "/mock/.prizmkit" ]] \
+    && pass "PRIZMKIT_DIR honored override" \
+    || fail "PRIZMKIT_DIR override" "got: $prizmkit"
+[[ "$project" == "/mock/proj" ]] \
+    && pass "PROJECT_ROOT honored override" \
+    || fail "PROJECT_ROOT override" "got: $project"
+
+echo ""
+echo "================================="
+echo " Results: $PASS passed, $FAIL failed"
+echo "================================="
+
+[[ $FAIL -eq 0 ]] || exit 1

package/bundled/rules/USAGE.md

@@ -19,9 +19,9 @@ core/rules/
 
 | File | Description |
 |------|-------------|
-| `prizm-documentation.md` | Sync `.prizm-docs/` when modifying source files |
+| `prizm-documentation.md` | Sync `.prizmkit/prizm-docs/` when modifying source files |
 | `prizm-commit-workflow.md` | Update docs before commit, follow Conventional Commits |
-| `prizm-progressive-loading.md` | Load `.prizm-docs/` progressively on demand, never load all at once |
+| `prizm-progressive-loading.md` | Load `.prizmkit/prizm-docs/` progressively on demand, never load all at once |
 
 ### General Rules (`general/`)
 

package/bundled/rules/_rules-metadata.json

@@ -10,7 +10,7 @@
       "tags": ["prizm", "git"]
     },
     "prizm/prizm-progressive-loading": {
-      "description": "Progressive .prizm-docs context loading protocol",
+      "description": "Progressive .prizmkit/prizm-docs context loading protocol",
       "tags": ["prizm", "context"]
     },
     "general/prefer-linux-commands": {

package/bundled/rules/prizm/prizm-commit-workflow.md

@@ -3,7 +3,7 @@ description: "PrizmKit commit workflow rules"
 ---
 
 Before any git commit in this project:
-1. Run `/prizmkit-retrospective` to sync `.prizm-docs/` (architecture index with TRAPS/RULES/DECISIONS)
+1. Run `/prizmkit-retrospective` to sync `.prizmkit/prizm-docs/` (architecture index with TRAPS/RULES/DECISIONS)
 2. Use Conventional Commits format: type(scope): description
 3. Bug fixes use `fix()` prefix, not `feat()`
 4. Bug fixes run retrospective with structural sync only (Job 1)

package/bundled/rules/prizm/prizm-documentation.md

@@ -1,5 +1,5 @@
 ---
-description: "PrizmKit .prizm-docs maintenance rules — when/how to update structured AI documentation"
+description: "PrizmKit .prizmkit/prizm-docs maintenance rules — when/how to update structured AI documentation"
 globs:
   - "**/*.ts"
   - "**/*.tsx"
@@ -11,11 +11,11 @@ globs:
   - "**/*.java"
 ---
 
-WHEN TO UPDATE .prizm-docs/:
-- Feature development (new interface, new module, new behavior) → UPDATE .prizm-docs/
+WHEN TO UPDATE .prizmkit/prizm-docs/:
+- Feature development (new interface, new module, new behavior) → UPDATE .prizmkit/prizm-docs/
 - Bug fix (fixing broken logic, no structural change) → SKIP, do NOT update
 - Rationale: bugs are incomplete features. Recording bug details causes doc bloat with no AI value.
-- Before modifying any source file, read `.prizm-docs/root.prizm` if it exists to understand project structure.
+- Before modifying any source file, read `.prizmkit/prizm-docs/root.prizm` if it exists to understand project structure.
 
 FORMAT RULES (enforced by pre-commit hook — violations block commit):
 - ALL CAPS section headers: MODULE:, FILES:, RESPONSIBILITY:, etc.

package/bundled/rules/prizm/prizm-progressive-loading.md

@@ -3,10 +3,10 @@ description: "PrizmKit progressive context loading protocol"
 ---
 
 This project uses PrizmKit's progressive loading protocol:
-- ON SESSION START: Read `.prizm-docs/root.prizm` (L0 — project map)
+- ON SESSION START: Read `.prizmkit/prizm-docs/root.prizm` (L0 — project map)
 - ON RESUME (feature/bugfix directory has session-summary.md): Read session-summary.md first for prior context, then load only L1/L2 for modules mentioned in it
-- ON TASK: Read L1 (`.prizm-docs/<module>.prizm`) for relevant modules. If MODULE_INDEX entries have keyword tags (e.g., `[login, jwt, oauth]`), match user's task description against tags to prioritize which modules' L1 to load first. If root.prizm uses MODULE_GROUPS, identify the relevant domain first, then load L1 only for modules in that domain.
-- ON FILE EDIT: Read L2 (`.prizm-docs/<module>/<submodule>.prizm`) before modifying
+- ON TASK: Read L1 (`.prizmkit/prizm-docs/<module>.prizm`) for relevant modules. If MODULE_INDEX entries have keyword tags (e.g., `[login, jwt, oauth]`), match user's task description against tags to prioritize which modules' L1 to load first. If root.prizm uses MODULE_GROUPS, identify the relevant domain first, then load L1 only for modules in that domain.
+- ON FILE EDIT: Read L2 (`.prizmkit/prizm-docs/<module>/<submodule>.prizm`) before modifying
 - NEVER load all .prizm docs at once
 - Arrow notation (->) in .prizm files indicates load pointers
 - DECISIONS and CHANGELOG in .prizm files are append-only

package/bundled/skills/_metadata.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.1.42",
+  "version": "1.1.47",
   "skills": {
     "prizm-kit": {
       "description": "Full-lifecycle dev toolkit. Covers spec-driven development, Prizm context docs, code quality, debugging, deployment, and knowledge management.",
@@ -37,14 +37,14 @@
       "hasScripts": false
     },
     "prizmkit-committer": {
-      "description": "Pure git commit workflow with safety checks. Does NOT modify .prizm-docs/.",
+      "description": "Pure git commit workflow with safety checks. Does NOT modify .prizmkit/prizm-docs/.",
       "tier": "1",
       "category": "prizmkit-skill",
       "hasAssets": false,
       "hasScripts": false
     },
     "prizmkit-retrospective": {
-      "description": "Sole .prizm-docs/ maintainer. Structural sync + TRAPS/RULES/DECISIONS injection to architecture index. Run after code review passes, before committing.",
+      "description": "Sole .prizmkit/prizm-docs/ maintainer. Structural sync + TRAPS/RULES/DECISIONS injection to architecture index. Run after code review passes, before committing.",
       "tier": "1",
       "category": "prizmkit-skill",
       "hasAssets": true,
@@ -180,7 +180,7 @@
       ]
     },
     "minimal": {
-      "description": "Minimal closed-loop workflow: full spec-driven cycle with .prizm-docs/ architecture sync and code review",
+      "description": "Minimal closed-loop workflow: full spec-driven cycle with .prizmkit/prizm-docs/ architecture sync and code review",
       "skills": [
         "prizm-kit",
         "prizmkit-init",

package/bundled/skills/app-planner/SKILL.md

@@ -36,7 +36,7 @@ If you believe the task is better suited for a different workflow, you MUST:
 **Your ONLY writable outputs are:**
 1. `.prizmkit/plans/project-brief.md` (`.prizmkit/plans/` — accumulated project context brief)
 2. Project conventions and architecture decisions appended to `CLAUDE.md` / `CODEBUDDY.md` (with user consent)
-3. Infrastructure configuration (database conventions + deployment config) appended to `CLAUDE.md` / `CODEBUDDY.md` `### Infrastructure` section
+3. Infrastructure configuration (database conventions, deployment config, **cloud services**) appended to `CLAUDE.md` / `CODEBUDDY.md` `### Infrastructure` section
 
 **After planning is complete**, you MUST:
 1. Present the summary of captured project-level context (vision, conventions, architecture decisions, project brief)
@@ -171,6 +171,27 @@ Do NOT use this skill when:
 
    Use `AskUserQuestion` for each batch. Each question MUST include a "Skip — decide later" option.
 
+   **Cloud Services Deep Inquiry** (Two-round AskUserQuestion):
+
+   Many projects depend on third-party cloud services (object storage, CDN, managed DB, auth, domain, email, SMS, payment, AI APIs). Capture them now so feature-planner and prizmkit-deploy can reference them later.
+
+   *Round 1 — Cloud Vendors* (multi-select via `AskUserQuestion`):
+   - "Which cloud vendors will this project integrate with?"
+   - Options: `AWS`, `Aliyun`, `Tencent Cloud`, `Cloudflare`, `Vercel`, `Other` (free text), `None — skip`
+   - If `None — skip`, write `<!-- cloud-services: none -->` to the `#### Cloud Services` subsection and exit this inquiry.
+
+   *Round 2 — Service Types* (multi-select, only if Round 1 returned any vendor):
+   - "Which types of cloud services will you use?"
+   - Options: `Object Storage (COS/S3/OSS)`, `CDN`, `Managed Database`, `Functions/Serverless`, `Auth (OAuth/JWT/IDaaS)`, `Domain & DNS`, `Email`, `SMS`, `Payment`, `AI API (OpenAI/Anthropic/...)`, `Other`
+   - The list is multi-select. Skip the question entirely if user picks "None" in Round 1.
+
+   *After both rounds, write to `#### Cloud Services`*:
+   - For each chosen (vendor × service) pair, append a row to the subsection (see template below)
+   - **Do NOT** prompt for env var names, credentials, region, or SDK details — those belong to `prizmkit-deploy`'s scope, not planning
+   - If the user is unsure of the mapping, store the vendors and service types separately; deploy skill can refine later
+
+   Use `AskUserQuestion` for both rounds. Each question MUST include a "Skip — decide later" option.
+
    **After infrastructure inquiry**:
    - Update `CLAUDE.md` / `CODEBUDDY.md` `### Infrastructure` section with all collected information. Replace `<!-- deferred -->` markers with real values. Preserve any existing values that were confirmed unchanged. Full format:
      ```markdown
@@ -197,6 +218,13 @@ Do NOT use this skill when:
 
      #### Deployment Credentials Reference
      - [platform]: [token/auth method description]
+
+     #### Cloud Services
+     - **Vendors**: [comma-separated list, e.g., "AWS, Cloudflare" or "none"]
+     - **Services**:
+       - [vendor]: [service type] — [optional one-line note, e.g., "user-upload images"]
+       - [vendor]: [service type]
+     <!-- If user picked "None" in Round 1, replace this block with: cloud-services: none -->
      ```
    - Items still marked "Skip — decide later" remain as `<!-- [topic]: deferred -->` in CLAUDE.md for `prizmkit-deploy` to pick up later.
 
@@ -207,7 +235,7 @@ Do NOT use this skill when:
 ## Prerequisites
 
 Before questions, check optional context files (never block if absent):
-- `.prizm-docs/root.prizm` (architecture/project context)
+- `.prizmkit/prizm-docs/root.prizm` (architecture/project context)
 - `.prizmkit/config.json` (existing stack preferences and detected tech stack)
 - `CLAUDE.md` / `CODEBUDDY.md` `### Project Conventions` section (previously answered project conventions)
 - `CLAUDE.md` / `CODEBUDDY.md` `### Infrastructure` section (database and deployment config from prizmkit-init or previous app-planner run)
@@ -221,7 +249,7 @@ Before questions, check optional context files (never block if absent):
 Note:
 - This skill **reads** `.prizmkit/config.json` if present.
 - This skill does **not** create `.prizmkit/config.json` directly.
-- Creation/update is handled by bootstrap/init flows (e.g., `prizmkit-init`, `dev-pipeline/scripts/init-dev-team.py`).
+- Creation/update is handled by bootstrap/init flows (e.g., `prizmkit-init`, `.prizmkit/dev-pipeline/scripts/init-dev-team.py`).
 
 ## Interaction Style (Hard Rule)
 
@@ -306,7 +334,7 @@ Before ANY planning work, check if AI-essential project context files exist:
 
 | File | Purpose | Status |
 |------|---------|--------|
-| `.prizm-docs/root.prizm` | Project architecture context for AI | exists / missing |
+| `.prizmkit/prizm-docs/root.prizm` | Project architecture context for AI | exists / missing |
 | `.prizmkit/config.json` | Tech stack + runtime config | exists / missing |
 | `.prizmkit/plans/project-brief.md` | Product vision checklist | exists / missing |
 
@@ -336,7 +364,7 @@ Do NOT ask the user to describe their project — read it yourself first:
    - `go.mod` → Go module info
    - `README.md` → project description and goals
    - `.prizmkit/config.json` → previously detected tech stack
-   - `.prizm-docs/root.prizm` → existing architecture context
+   - `.prizmkit/prizm-docs/root.prizm` → existing architecture context
 
 3. **Read key source files** (entry points, main routes, core models) to understand what the project actually does — don't rely solely on metadata.
 
@@ -392,7 +420,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 — configured or explicitly deferred | 1-2 |
+| **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-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 |
@@ -405,7 +433,7 @@ After Phase 2, if framework-shaping architecture decisions emerged during planni
 **How it works**:
 1. If decisions are captured → append to `CLAUDE.md` / `CODEBUDDY.md` under `### Architecture Decisions` section
 2. Downstream skills (feature-planner, prizmkit-plan, etc.) read `CLAUDE.md` / `CODEBUDDY.md` as standard context, so they automatically receive these decisions
-3. Do NOT write directly to `.prizm-docs/root.prizm` — that file is maintained by `prizmkit-prizm-docs` and `prizmkit-retrospective`. If the project needs `.prizm-docs/`, recommend the user run `prizmkit-prizm-docs` init after planning.
+3. Do NOT write directly to `.prizmkit/prizm-docs/root.prizm` — that file is maintained by `prizmkit-prizm-docs` and `prizmkit-retrospective`. If the project needs `.prizmkit/prizm-docs/`, recommend the user run `prizmkit-prizm-docs` init after planning.
 
 ## Project Brief Accumulation
 

package/bundled/skills/bug-fix-workflow/SKILL.md

@@ -212,11 +212,11 @@ AskUserQuestion:
 
 **Goal**: Locate affected code, identify root cause, classify severity.
 
-> **Triage**: Classify error into: Runtime / Network / Auth / Data / Resource / Logic / Config / External. Check `.prizm-docs/` TRAPS for known patterns first. If a TRAPS match is found, use documented solution and reference the specific `.prizm-docs/` entry. If no match, trace the call chain from the stack frame to identify root cause from first principles.
+> **Triage**: Classify error into: Runtime / Network / Auth / Data / Resource / Logic / Config / External. Check `.prizmkit/prizm-docs/` TRAPS for known patterns first. If a TRAPS match is found, use documented solution and reference the specific `.prizmkit/prizm-docs/` entry. If no match, trace the call chain from the stack frame to identify root cause from first principles.
 
-1. **Read project context**: `.prizm-docs/root.prizm` → relevant L1/L2 docs for affected modules
+1. **Read project context**: `.prizmkit/prizm-docs/root.prizm` → relevant L1/L2 docs for affected modules
 2. **Locate affected code**: read the files mentioned in the error/stack trace or identified during diagnosis
-3. **Check known issues**: search `.prizm-docs/` TRAPS sections for matching patterns
+3. **Check known issues**: search `.prizmkit/prizm-docs/` TRAPS sections for matching patterns
 4. **If database-related**: read existing schema/model files to understand the data layer
    ```bash
    find . -maxdepth 4 -type f \( -name "*.prisma" -o -name "*.sql" -o -path "*/migrations/*" -o -path "*/models/*" -o -name "schema.*" -o -name "*.entity.*" \) -not -path '*/node_modules/*' -not -path '*/.git/*' | head -20
@@ -259,7 +259,7 @@ If the bug is hard to reproduce automatically (e.g. environment-specific):
 1. **Implement the fix**:
    - Change the minimum amount of code to fix the root cause
    - Do NOT refactor or add unrelated improvements — fix the bug only
-   - Follow existing code conventions (read from `.prizm-docs/` RULES/PATTERNS)
+   - Follow existing code conventions (read from `.prizmkit/prizm-docs/` RULES/PATTERNS)
    - If the fix involves database changes: read existing schema first, follow existing naming/constraint conventions
 2. **Run the reproduction test** → must **pass** (green)
 3. **Run the full module test suite** → must pass (no regressions)
@@ -316,7 +316,7 @@ If user reports the fix is NOT working:
    - Commit message: `fix(<scope>): <description>`
    - Include both fix code and reproduction test
    - Do NOT push (user decides when to push)
-   - `/prizmkit-committer` is a pure commit tool — it does NOT modify `.prizm-docs/` or any project files
+   - `/prizmkit-committer` is a pure commit tool — it does NOT modify `.prizmkit/prizm-docs/` or any project files
    - No `/prizmkit-retrospective` — bug fixes are incomplete features, not new architecture worth documenting
 2. **Ask merge preference**:
    ```
@@ -392,7 +392,7 @@ Only 2 artifact files per bug, consistent with the pipeline convention.
 | Cannot reproduce the bug | Ask for more context, try alternative reproduction |
 | Fix causes regressions | Revert, analyze, retry (max 3 rounds) |
 | Root cause unclear after investigation | Present findings, ask user for guidance |
-| Affected files are in unfamiliar module | Read `.prizm-docs/` L1/L2 for that module first |
+| Affected files are in unfamiliar module | Read `.prizmkit/prizm-docs/` L1/L2 for that module first |
 | Branch conflict during merge | Show conflict, ask user to resolve or keep branch |
 
 ## HANDOFF