prizmkit 1.1.41 → 1.1.46

package/bundled/skills/refactor-pipeline-launcher/SKILL.md

@@ -11,8 +11,8 @@ Launch the autonomous refactor pipeline from within an AI CLI conversation. The
 
 Three execution modes are available. The user chooses one before configuring other options:
 
-1. **Foreground** (recommended) — `dev-pipeline/run-refactor.sh run`. Visible output, direct error feedback, no orphaned processes.
-2. **Background daemon** — `dev-pipeline/launch-refactor-daemon.sh`. Runs fully detached, survives AI CLI session closure.
+1. **Foreground** (recommended) — `.prizmkit/dev-pipeline/run-refactor.sh run`. Visible output, direct error feedback, no orphaned processes.
+2. **Background daemon** — `.prizmkit/dev-pipeline/launch-refactor-daemon.sh`. Runs fully detached, survives AI CLI session closure.
 3. **Manual** — Display the assembled command(s) only. Do not execute anything. User runs them on their own.
 
 ### When to Use
@@ -45,7 +45,7 @@ Three execution modes are available. The user chooses one before configuring oth
 
 Before any action, validate:
 
-1. **refactor pipeline exists**: Confirm `dev-pipeline/launch-refactor-daemon.sh` and `dev-pipeline/run-refactor.sh` are present and executable
+1. **refactor pipeline exists**: Confirm `.prizmkit/dev-pipeline/launch-refactor-daemon.sh` and `.prizmkit/dev-pipeline/run-refactor.sh` are present and executable
 2. **For start**: `.prizmkit/plans/refactor-list.json` must exist in `.prizmkit/plans/` (or user-specified path)
 3. **Dependencies**: `jq`, `python3`, AI CLI (`cbc` or `claude`) must be in PATH
 4. **Python version**: Requires Python 3.8+ for dev-pipeline scripts
@@ -79,7 +79,7 @@ Detect user intent from their message, then follow the corresponding workflow:
 
 2. **Check not already running**:
    ```bash
-   dev-pipeline/launch-refactor-daemon.sh status 2>/dev/null
+   .prizmkit/dev-pipeline/launch-refactor-daemon.sh status 2>/dev/null
    ```
    If running, inform user and ask: "Refactor pipeline is already running. Want to restart it, check status, or view logs?"
 
@@ -106,7 +106,7 @@ Detect user intent from their message, then follow the corresponding workflow:
    ```
    If pipeline state already exists, use the status command instead:
    ```bash
-   python3 dev-pipeline/scripts/update-refactor-status.py \
+   python3 .prizmkit/dev-pipeline/scripts/update-refactor-status.py \
      --refactor-list .prizmkit/plans/refactor-list.json \
      --state-dir .prizmkit/state/refactor \
      --action status 2>/dev/null
@@ -139,6 +139,13 @@ Detect user intent from their message, then follow the corresponding workflow:
 
 6. **Ask configuration options** ⚠️ MANDATORY INTERACTIVE STEP — applies to ALL execution modes (Foreground, Background, AND Manual). You MUST ask the user to configure options and WAIT for their response BEFORE proceeding to step 7. Do NOT skip this step or merge it with step 7.
 
+   ⛔ **HARD STOP**: You MUST call `AskUserQuestion` with the questions below and WAIT for the user's response. You MUST NOT:
+   - Skip this step and jump to step 7
+   - Merge step 6 and step 7 into one response
+   - Assume default values and show the command without asking
+   - Show the command as text and ask "ready?" without presenting the options
+   If you find yourself writing the final command before the user has answered these questions, STOP — you are violating this rule.
+
    Use `AskUserQuestion` to present the following configuration choices. Each question is a separate selectable option:
 
    **Question 1 — Verbose logging** (multiSelect: false):
@@ -215,34 +222,34 @@ Detect user intent from their message, then follow the corresponding workflow:
 
    **Foreground command:**
    ```bash
-   VERBOSE=1 STRICT_BEHAVIOR_CHECK=1 dev-pipeline/run-refactor.sh run .prizmkit/plans/refactor-list.json
+   VERBOSE=1 STRICT_BEHAVIOR_CHECK=1 .prizmkit/dev-pipeline/run-refactor.sh run .prizmkit/plans/refactor-list.json
    ```
    With all options:
    ```bash
    VERBOSE=1 STRICT_BEHAVIOR_CHECK=1 MAX_RETRIES=5 SESSION_TIMEOUT=3600 ENABLE_DEPLOY=1 \
-     dev-pipeline/run-refactor.sh run .prizmkit/plans/refactor-list.json
+     .prizmkit/dev-pipeline/run-refactor.sh run .prizmkit/plans/refactor-list.json
    ```
 
    **Background daemon command:**
    ```bash
-   dev-pipeline/launch-refactor-daemon.sh start .prizmkit/plans/refactor-list.json --env "VERBOSE=1 STRICT_BEHAVIOR_CHECK=1"
+   .prizmkit/dev-pipeline/launch-refactor-daemon.sh start .prizmkit/plans/refactor-list.json --env "VERBOSE=1 STRICT_BEHAVIOR_CHECK=1"
    ```
    With all options:
    ```bash
-   dev-pipeline/launch-refactor-daemon.sh start .prizmkit/plans/refactor-list.json \
+   .prizmkit/dev-pipeline/launch-refactor-daemon.sh start .prizmkit/plans/refactor-list.json \
      --env "VERBOSE=1 STRICT_BEHAVIOR_CHECK=1 MAX_RETRIES=5 ENABLE_DEPLOY=1"
    ```
 
    **Manual mode**: Print the assembled command(s) and **stop here**. Do not execute anything. Do not proceed to step 8.
    ```
    # To run in foreground:
-   VERBOSE=1 STRICT_BEHAVIOR_CHECK=1 dev-pipeline/run-refactor.sh run .prizmkit/plans/refactor-list.json
+   VERBOSE=1 STRICT_BEHAVIOR_CHECK=1 .prizmkit/dev-pipeline/run-refactor.sh run .prizmkit/plans/refactor-list.json
 
    # To run in background (detached):
-   dev-pipeline/launch-refactor-daemon.sh start .prizmkit/plans/refactor-list.json --env "VERBOSE=1 STRICT_BEHAVIOR_CHECK=1"
+   .prizmkit/dev-pipeline/launch-refactor-daemon.sh start .prizmkit/plans/refactor-list.json --env "VERBOSE=1 STRICT_BEHAVIOR_CHECK=1"
 
    # To check status:
-   dev-pipeline/run-refactor.sh status .prizmkit/plans/refactor-list.json
+   .prizmkit/dev-pipeline/run-refactor.sh status .prizmkit/plans/refactor-list.json
    ```
 
 8. **Confirm and launch** (Foreground and Background only — Manual mode ends at step 7):
@@ -261,7 +268,7 @@ Detect user intent from their message, then follow the corresponding workflow:
    **If background daemon**:
    1. Verify launch:
       ```bash
-      dev-pipeline/launch-refactor-daemon.sh status
+      .prizmkit/dev-pipeline/launch-refactor-daemon.sh status
       ```
    2. Start log monitoring — Use the Bash tool with `run_in_background: true`:
       ```bash
@@ -279,12 +286,12 @@ Detect user intent from their message, then follow the corresponding workflow:
 
 1. **Check daemon status**:
    ```bash
-   dev-pipeline/launch-refactor-daemon.sh status
+   .prizmkit/dev-pipeline/launch-refactor-daemon.sh status
    ```
 
 2. **Show refactor-level progress**:
    ```bash
-   python3 dev-pipeline/scripts/update-refactor-status.py \
+   python3 .prizmkit/dev-pipeline/scripts/update-refactor-status.py \
      --refactor-list .prizmkit/plans/refactor-list.json \
      --state-dir .prizmkit/state/refactor \
      --action status
@@ -303,12 +310,12 @@ Detect user intent from their message, then follow the corresponding workflow:
 
 1. **Stop the daemon**:
    ```bash
-   dev-pipeline/launch-refactor-daemon.sh stop
+   .prizmkit/dev-pipeline/launch-refactor-daemon.sh stop
    ```
 
 2. **Verify stopped**:
    ```bash
-   dev-pipeline/launch-refactor-daemon.sh status 2>/dev/null || true
+   .prizmkit/dev-pipeline/launch-refactor-daemon.sh status 2>/dev/null || true
    ```
 
 3. **Inform user**: "Refactor pipeline stopped. State is preserved -- you can resume later with 'start refactoring' and it will pick up where it left off."
@@ -319,7 +326,7 @@ Detect user intent from their message, then follow the corresponding workflow:
 
 1. **Check if running**:
    ```bash
-   dev-pipeline/launch-refactor-daemon.sh status 2>/dev/null
+   .prizmkit/dev-pipeline/launch-refactor-daemon.sh status 2>/dev/null
    ```
 
 2. **If running** -- Start live tail with Bash tool `run_in_background: true`:
@@ -347,7 +354,7 @@ Detect user intent from their message, then follow the corresponding workflow:
 When user says "retry R-001" or "clean retry R-001":
 
 ```bash
-dev-pipeline/reset-refactor.sh R-001 --clean --run .prizmkit/plans/refactor-list.json
+.prizmkit/dev-pipeline/reset-refactor.sh R-001 --clean --run .prizmkit/plans/refactor-list.json
 ```
 
 Notes:
@@ -369,11 +376,11 @@ Notes:
 | PID file stale (process dead) | `launch-refactor-daemon.sh` auto-cleans, retry start |
 | Launch failed (process died immediately) | Show last 20 lines of log: `tail -20 .prizmkit/state/refactor/pipeline-daemon.log` |
 | Refactor stuck/blocked | Use `reset-refactor.sh <R-XXX> --clean --run` for a fresh retry |
-| All refactors blocked/failed | Show status, suggest recovery: `dev-pipeline/reset-refactor.sh <R-XXX> --clean --run .prizmkit/plans/refactor-list.json` |
+| All refactors blocked/failed | Show status, suggest recovery: `.prizmkit/dev-pipeline/reset-refactor.sh <R-XXX> --clean --run .prizmkit/plans/refactor-list.json` |
 | `playwright-cli` not installed | Browser verification skipped for playwright refactors (non-blocking). Suggest: `npm install -g @playwright/cli@latest && playwright-cli install --skills` |
 | `opencli` not installed | Browser verification skipped for opencli refactors (non-blocking). Install opencli for Chrome session-based browser verification |
 | Deploy session failed | Pipeline completed but deploy session exited non-zero. Check `.prizmkit/state/refactor/deploy/<session_id>/logs/session.log`. Retry manually: `/prizmkit-deploy`. |
-| Permission denied on script | Run `chmod +x dev-pipeline/launch-refactor-daemon.sh dev-pipeline/run-refactor.sh` |
+| Permission denied on script | Run `chmod +x .prizmkit/dev-pipeline/launch-refactor-daemon.sh .prizmkit/dev-pipeline/run-refactor.sh` |
 
 ### Integration Notes
 

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

@@ -92,11 +92,11 @@ Do NOT use this skill when the user wants to:
 ## 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)
 - Existing test suite (critical for behavior preservation assessment)
 - Existing `.prizmkit/plans/refactor-list.json` (if appending additional items)
-- If `.prizm-docs/root.prizm` is absent and the project has existing source code, scan the directory structure:
+- If `.prizmkit/prizm-docs/root.prizm` is absent and the project has existing source code, scan the directory structure:
   ```bash
   find . -maxdepth 2 -type d -not -path '*/node_modules/*' -not -path '*/.git/*' -not -path '*/dist/*' -not -path '*/build/*' -not -path '*/__pycache__/*' -not -path '*/vendor/*' | sed -e 's;[^/]*/;|____;g;s;____|; |;g'
   ```
@@ -132,7 +132,7 @@ Execute the planning workflow in conversation mode with mandatory checkpoints:
 
 **Goal**: Understand the current codebase structure and tech stack.
 
-1. Read `.prizm-docs/root.prizm` and relevant L1 docs
+1. Read `.prizmkit/prizm-docs/root.prizm` and relevant L1 docs
 2. Read `.prizmkit/config.json` for tech stack info
 3. Identify existing test suite and coverage
 4. Summarize project context to the user: "Here's what I found about your project..."
@@ -142,7 +142,7 @@ Execute the planning workflow in conversation mode with mandatory checkpoints:
    > "Do you have any reference materials I should review before planning the refactoring? This can include:
    > - **Code paths** — specific files or directories that are refactoring targets or dependencies
    > - **Documents** — design docs, architecture proposals, refactoring RFCs, or technical debt analyses
-   > - **Knowledge docs** — `.prizm-docs/` files, README files, or internal wiki pages for the affected area
+   > - **Knowledge docs** — `.prizmkit/prizm-docs/` files, README files, or internal wiki pages for the affected area
    > - **Images** — architecture diagrams, dependency graphs, or whiteboard photos
    > - **Web links** — reference implementations, design pattern articles, or migration guides
    >
@@ -307,7 +307,7 @@ If issues found, discuss with user and resolve before proceeding.
 
 | Checkpoint | Artifact/State | Criteria | Phase |
 |-----------|----------------|----------|-------|
-| **CP-RP-0** | Project Context | Tech stack, test suite status, .prizm-docs loaded | 1 |
+| **CP-RP-0** | Project Context | Tech stack, test suite status, .prizmkit/prizm-docs loaded | 1 |
 | **CP-RP-1** | Goals Collected | All refactoring goals understood, no open ambiguities | 2 |
 | **CP-RP-2** | Code Analyzed | Analysis complete, user agrees with approach | 3 |
 | **CP-RP-3** | Items Decomposed | All items have deps, complexity, preservation strategy | 4 |
@@ -324,7 +324,7 @@ If issues found, discuss with user and resolve before proceeding.
 - Non-empty `refactors` array
 - Sequential IDs: `R-001`, `R-002`, ...
 - Valid dependency DAG (no cycles)
-- Each item has a declared `behavior_preservation` object with `strategy` field: `"test-gate"`, `"snapshot"`, or `"manual"`. Optional fields: `existing_tests` (boolean), `new_tests_needed` (string array). See `dev-pipeline/templates/refactor-list-schema.json` for the full schema.
+- Each item has a declared `behavior_preservation` object with `strategy` field: `"test-gate"`, `"snapshot"`, or `"manual"`. Optional fields: `existing_tests` (boolean), `new_tests_needed` (string array). See `.prizmkit/dev-pipeline/templates/refactor-list-schema.json` for the full schema.
 - `priority` must be a string: `"critical"`, `"high"`, `"medium"`, or `"low"`
 - New items default `status: "pending"`
 - English titles for stable slug generation

package/bundled/skills/refactor-workflow/SKILL.md

@@ -132,7 +132,7 @@ Then ask:
 Ask:
 1. **Code paths** — "Which files or directories are the main targets? Any specific files I should look at?"
 2. **Design documents** — "Do you have any design docs, architecture diagrams, or refactoring proposals I should read?"
-3. **Knowledge docs** — "Are there related `.prizm-docs/`, README files, or internal wiki pages for the target area?"
+3. **Knowledge docs** — "Are there related `.prizmkit/prizm-docs/`, README files, or internal wiki pages for the target area?"
 4. **Related issues/PRs** — "Any related issues, PRs, or previous refactoring attempts I should be aware of?"
 
 Record everything the user provides — these become inputs for Step 1.3.
@@ -147,7 +147,7 @@ Record everything the user provides — these become inputs for Step 1.3.
 |-------|-------------|---------|
 | Agent A | User-provided code paths — read full source files | Understand current structure, interfaces, dependencies |
 | Agent B | User-provided documents — design docs, proposals, wiki pages | Understand intended direction and constraints |
-| Agent C | `.prizm-docs/` for affected modules — L1/L2 docs, TRAPS, RULES | Understand existing architecture knowledge and known pitfalls |
+| Agent C | `.prizmkit/prizm-docs/` for affected modules — L1/L2 docs, TRAPS, RULES | Understand existing architecture knowledge and known pitfalls |
 | Agent D | Test files for the target area — find and read existing tests | Understand current test coverage and behavior contracts |
 
 **Also gather** (can be included in any agent's task):
@@ -164,7 +164,7 @@ Record everything the user provides — these become inputs for Step 1.3.
 Present what you learned from the parallel reading:
 - Current code structure and its problems (with specific file/function references)
 - Existing test coverage status (which areas are safe, which are risky)
-- Known TRAPS and pitfalls from `.prizm-docs/`
+- Known TRAPS and pitfalls from `.prizmkit/prizm-docs/`
 - Dependencies and potential impact on other modules
 
 Then ask targeted questions based on what you read. **Adapt question depth to the refactoring complexity** — a simple extract-method refactor needs fewer questions than a full module decomposition.
@@ -184,7 +184,7 @@ Then ask targeted questions based on what you read. **Adapt question depth to th
 - Any undocumented behavior that callers depend on?
 
 **Risk Assessment:**
-- "I found these TRAPS in .prizm-docs/: [list]. Any other known gotchas?"
+- "I found these TRAPS in .prizmkit/prizm-docs/: [list]. Any other known gotchas?"
 - Does this code have external consumers (other teams, published APIs)?
 - Any concurrent development happening in the target area?
 
@@ -249,7 +249,7 @@ Once brainstorming is complete, produce a structured goals summary:
 - [Risk]: [Mitigation strategy]
 
 ### Reference Materials Reviewed
-- [List of code paths, documents, .prizm-docs/ files that were read]
+- [List of code paths, documents, .prizmkit/prizm-docs/ files that were read]
 
 ### Constraints
 - [Timeline, coordination, deployment concerns]
@@ -293,7 +293,7 @@ AskUserQuestion:
   2. Invoke `/prizmkit-implement` to execute the plan (behavior preservation verified by tests)
   3. After implementation, run `/prizmkit-code-review` for quality check
   4. Commit via `/prizmkit-committer` with `refactor(<scope>):` prefix
-  5. Run `/prizmkit-retrospective` to sync `.prizm-docs/`
+  5. Run `/prizmkit-retrospective` to sync `.prizmkit/prizm-docs/`
   6. **End workflow** — skip Phase 2/3/4
 - **Add to refactor list** → Continue to Phase 2 (Plan via pipeline)
 
@@ -394,7 +394,7 @@ AskUserQuestion:
 
 1. **Initial status check**:
    ```bash
-   dev-pipeline/launch-refactor-daemon.sh status
+   .prizmkit/dev-pipeline/launch-refactor-daemon.sh status
    ```
 
 2. **Offer monitoring options**:
@@ -404,7 +404,7 @@ AskUserQuestion:
 
 3. **Periodic progress reports** (when user asks):
    ```bash
-   python3 dev-pipeline/scripts/update-refactor-status.py \
+   python3 .prizmkit/dev-pipeline/scripts/update-refactor-status.py \
      --refactor-list .prizmkit/plans/refactor-list.json \
      --state-dir .prizmkit/state/refactor \
      --action status
@@ -480,4 +480,4 @@ While the pipeline runs, the user can continue the conversation:
 - Pipeline execution (Phase 3)
 - Progress updates (Phase 4)
 - Multiple git commits with `refactor(<scope>):` prefix
-- Updated `.prizm-docs/` (via prizmkit-retrospective per refactor item)
+- Updated `.prizmkit/prizm-docs/` (via prizmkit-retrospective per refactor item)

package/bundled/team/prizm-dev-team.json

@@ -13,7 +13,7 @@
       "name": "dev",
       "role": "developer", 
       "agentDefinition": "prizm-dev-team-dev",
-      "prompt": "You are a Dev Agent of the prizm-dev-team. Follow /prizmkit-implement workflow with TDD. Read plan.md/spec.md, implement task-by-task, mark completed tasks [x]. Check .prizm-docs/ TRAPS before implementing.",
+      "prompt": "You are a Dev Agent of the prizm-dev-team. Follow /prizmkit-implement workflow with TDD. Read plan.md/spec.md, implement task-by-task, mark completed tasks [x]. Check .prizmkit/prizm-docs/ TRAPS before implementing.",
       "subscriptions": ["*"]
     },
     {

package/bundled/templates/hooks/commit-intent.json

@@ -6,7 +6,7 @@
         "hooks": [
           {
             "type": "command",
-            "command": "SRC=$(git diff --cached --name-only 2>/dev/null | grep -cE '\\.(ts|tsx|js|jsx|py|go|rs|java)$'); if [ \"$SRC\" -gt 0 ]; then PRIZM=$(git diff --cached --name-only 2>/dev/null | grep -c '^\\.prizm-docs/'); if [ \"$PRIZM\" -gt 0 ]; then echo \"PRIZMKIT_DOC_STATUS: $SRC source file(s) staged | .prizm-docs/ updated ($PRIZM file(s))\"; else echo \"PRIZMKIT_DOC_STATUS: $SRC source file(s) staged | .prizm-docs/ NOT UPDATED — update if this is a feature change\"; fi; fi"
+            "command": "SRC=$(git diff --cached --name-only 2>/dev/null | grep -cE '\\.(ts|tsx|js|jsx|py|go|rs|java)$'); if [ \"$SRC\" -gt 0 ]; then PRIZM=$(git diff --cached --name-only 2>/dev/null | grep -c '^\\.prizmkit/prizm-docs/'); if [ \"$PRIZM\" -gt 0 ]; then echo \"PRIZMKIT_DOC_STATUS: $SRC source file(s) staged | .prizmkit/prizm-docs/ updated ($PRIZM file(s))\"; else echo \"PRIZMKIT_DOC_STATUS: $SRC source file(s) staged | .prizmkit/prizm-docs/ NOT UPDATED — update if this is a feature change\"; fi; fi"
           }
         ]
       }
@@ -17,7 +17,7 @@
         "hooks": [
           {
             "type": "command",
-            "command": "TOOL_INPUT=\"${CLAUDE_TOOL_INPUT:-${CODEBUDDY_TOOL_INPUT:-}}\"; if echo \"$TOOL_INPUT\" | grep -qE 'git (commit|merge|rebase)' 2>/dev/null; then DRIFT=$(sh .prizmkit/scripts/diff-prizm-docs.sh 2>/dev/null); if [ -n \"$DRIFT\" ]; then echo \"PRIZMKIT_DRIFT_DETECTED: prizm-docs structural differences found:\"; echo \"$DRIFT\"; echo \"Please update affected .prizm-docs/ files.\"; fi; fi"
+            "command": "TOOL_INPUT=\"${CLAUDE_TOOL_INPUT:-${CODEBUDDY_TOOL_INPUT:-}}\"; if echo \"$TOOL_INPUT\" | grep -qE 'git (commit|merge|rebase)' 2>/dev/null; then DRIFT=$(sh .prizmkit/scripts/diff-prizm-docs.sh 2>/dev/null); if [ -n \"$DRIFT\" ]; then echo \"PRIZMKIT_DRIFT_DETECTED: prizm-docs structural differences found:\"; echo \"$DRIFT\"; echo \"Please update affected .prizmkit/prizm-docs/ files.\"; fi; fi"
           }
         ]
       }

package/bundled/templates/hooks/diff-prizm-docs.sh

@@ -1,12 +1,12 @@
 #!/bin/sh
 # PrizmKit: diff-prizm-docs.sh
-# Outputs structural differences between .prizm-docs/ and source code.
-# Silent (exit 0) if no differences or if .prizm-docs doesn't exist.
+# Outputs structural differences between .prizmkit/prizm-docs/ and source code.
+# Silent (exit 0) if no differences or if .prizmkit/prizm-docs doesn't exist.
 # POSIX sh only — no arrays, no bashisms.
 
 set -e
 
-ROOT_PRIZM=".prizm-docs/root.prizm"
+ROOT_PRIZM=".prizmkit/prizm-docs/root.prizm"
 
 # 1. Exit silently if no root.prizm
 [ -f "$ROOT_PRIZM" ] || exit 0
@@ -85,7 +85,7 @@ echo "$REGISTERED_PATHS" | while IFS= read -r source_path; do
   [ -z "$source_path" ] && continue
 
   # Derive L1 prizm file path
-  l1_file=".prizm-docs/${source_path}.prizm"
+  l1_file=".prizmkit/prizm-docs/${source_path}.prizm"
 
   if [ ! -f "$l1_file" ]; then
     continue
@@ -104,7 +104,7 @@ echo "$REGISTERED_PATHS" | while IFS= read -r source_path; do
 done
 
 # 5. Find orphan docs
-find .prizm-docs -name '*.prizm' 2>/dev/null | while IFS= read -r prizm_file; do
+find .prizmkit/prizm-docs -name '*.prizm' 2>/dev/null | while IFS= read -r prizm_file; do
   _basename=$(basename "$prizm_file")
   case "$_basename" in
     root.prizm|changelog.prizm|changelog-archive.prizm)
@@ -112,8 +112,8 @@ find .prizm-docs -name '*.prizm' 2>/dev/null | while IFS= read -r prizm_file; do
       ;;
   esac
 
-  # Derive source path: remove .prizm-docs/ prefix and .prizm suffix
-  source_path=$(echo "$prizm_file" | sed 's|^\.prizm-docs/||' | sed 's|\.prizm$||')
+  # Derive source path: remove .prizmkit/prizm-docs/ prefix and .prizm suffix
+  source_path=$(echo "$prizm_file" | sed 's|^\.prizmkit/prizm-docs/||' | sed 's|\.prizm$||')
 
   if [ ! -d "$source_path" ]; then
     echo "ORPHAN_DOC: $prizm_file | source dir missing"
@@ -131,7 +131,7 @@ find . -mindepth 1 -maxdepth 3 -type d \
   ! -path '*/target/*' ! -path './target' \
   ! -path '*/tests/*' ! -path './tests' \
   ! -path '*/__tests__/*' ! -path './__tests__' \
-  ! -path '*/.prizm-docs/*' ! -path './.prizm-docs' \
+  ! -path '*/.prizmkit/prizm-docs/*' ! -path './.prizmkit/prizm-docs' \
   ! -path '*/.claude/*' ! -path './.claude' \
   ! -path '*/.codebuddy/*' ! -path './.codebuddy' \
   ! -path '*/dev-pipeline/*' ! -path './dev-pipeline' \

package/bundled/templates/hooks/prizm-pre-commit.sh

@@ -1,13 +1,13 @@
 #!/bin/sh
-# prizm-pre-commit.sh — git pre-commit hook for .prizm-docs validation
+# prizm-pre-commit.sh — git pre-commit hook for .prizmkit/prizm-docs validation
 
 PROJECT_ROOT=$(git rev-parse --show-toplevel 2>/dev/null) || exit 0
 
 # Only run in prizm projects
-[ -f "$PROJECT_ROOT/.prizm-docs/root.prizm" ] || exit 0
+[ -f "$PROJECT_ROOT/.prizmkit/prizm-docs/root.prizm" ] || exit 0
 
 VALIDATE_SCRIPT="$PROJECT_ROOT/.prizmkit/scripts/validate-prizm-docs.sh"
-[ -f "$VALIDATE_SCRIPT" ] || VALIDATE_SCRIPT="$PROJECT_ROOT/dev-pipeline/scripts/validate-prizm-docs.sh"
+[ -f "$VALIDATE_SCRIPT" ] || VALIDATE_SCRIPT="$PROJECT_ROOT/.prizmkit/dev-pipeline/scripts/validate-prizm-docs.sh"
 
 if [ -f "$VALIDATE_SCRIPT" ]; then
     sh "$VALIDATE_SCRIPT" --staged
@@ -37,7 +37,7 @@ for FILE in $FILES; do
         *root.prizm) LIMIT=4096 ;;
         *)
             DIR=$(dirname "$FILE")
-            if [ "$DIR" = ".prizm-docs" ]; then
+            if [ "$DIR" = ".prizmkit/prizm-docs" ]; then
                 LIMIT=3072
             else
                 LIMIT=5120

package/bundled/templates/hooks/validate-prizm-docs.sh

@@ -6,11 +6,11 @@ MODE="${1:---staged}"
 ERRORS=0
 
 # Not a prizm project — exit silently
-[ -f ".prizm-docs/root.prizm" ] || exit 0
+[ -f ".prizmkit/prizm-docs/root.prizm" ] || exit 0
 
 # Collect files to check
 if [ "$MODE" = "--all" ]; then
-    FILES=$(find .prizm-docs -name '*.prizm' 2>/dev/null)
+    FILES=$(find .prizmkit/prizm-docs -name '*.prizm' 2>/dev/null)
 elif [ "$MODE" = "--staged" ]; then
     FILES=$(git diff --cached --name-only 2>/dev/null | grep '\.prizm$')
 else
@@ -44,9 +44,9 @@ for FILE in $FILES; do
             HINT="Consolidate MODULE_INDEX, keep top-5 RULES."
             ;;
         *)
-            # L1 = direct child of .prizm-docs/, L2 = nested deeper
+            # L1 = direct child of .prizmkit/prizm-docs/, L2 = nested deeper
             DIR=$(dirname "$FILE")
-            if [ "$DIR" = ".prizm-docs" ]; then
+            if [ "$DIR" = ".prizmkit/prizm-docs" ]; then
                 LIMIT=3072; LEVEL="L1"
                 HINT="Move implementation details to L2."
             else

package/bundled/templates/project-memory-template.md

@@ -4,14 +4,14 @@
 This project uses PrizmKit with the Prizm documentation system for AI-optimized progressive context loading.
 
 ### Progressive Loading Protocol
-- ON SESSION START: Always read `.prizm-docs/root.prizm` first (L0 — project map)
+- ON SESSION START: Always read `.prizmkit/prizm-docs/root.prizm` first (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 referenced in MODULE_INDEX or MODULE_GROUPS. If entries have keyword tags (e.g., `[login, jwt, oauth]`), match user's task against tags to prioritize which modules to load.
-- ON FILE EDIT: Read L2 (`.prizm-docs/<module>/<submodule>.prizm`) before modifying files. Pay attention to TRAPS and DECISIONS.
+- ON TASK: Read L1 (`.prizmkit/prizm-docs/<module>.prizm`) for relevant modules referenced in MODULE_INDEX or MODULE_GROUPS. If entries have keyword tags (e.g., `[login, jwt, oauth]`), match user's task against tags to prioritize which modules to load.
+- ON FILE EDIT: Read L2 (`.prizmkit/prizm-docs/<module>/<submodule>.prizm`) before modifying files. Pay attention to TRAPS and DECISIONS.
 - NEVER load all .prizm docs at once. Load only what is needed for the current task.
 
 ### Auto-Update Protocol
-- BEFORE EVERY COMMIT: Update affected `.prizm-docs/` files
+- BEFORE EVERY COMMIT: Update affected `.prizmkit/prizm-docs/` files
 - Platform hooks (rules or UserPromptSubmit) will remind you automatically
 - Use `/prizmkit-committer` for the complete commit workflow
 

package/package.json

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

package/src/clean.js

@@ -115,8 +115,6 @@ export async function runClean(directory, options = {}) {
   const fullRemoveTargets = [
     '.prizmkit',
     '.dev-team',
-    'dev-pipeline',
-    '.prizm-docs',        // AI-generated project context docs
     'CODEBUDDY.md',
     'CLAUDE.md',
     path.join('.prizmkit', 'plans', 'feature-list.json'),          // feature-planner output
@@ -204,7 +202,7 @@ export async function runClean(directory, options = {}) {
     console.log(chalk.green(`  清理完成：已删除 ${removed} 项。`));
   }
   console.log('');
-  console.log(chalk.gray('  注意：.prizm-docs/ 为 AI 生成的项目上下文文档，已一并清理。'));
+  console.log(chalk.gray('  注意：.prizmkit/prizm-docs/ 为 AI 生成的项目上下文文档，已一并清理。'));
   console.log(chalk.gray('        用户自定义的 agent/skill/rule 文件未受影响。'));
   console.log('');
 }

package/src/config.js

@@ -6,7 +6,7 @@
  *
  * Flow: READ manifest → PROMPT user → COMPUTE DIFF → DISPLAY SUMMARY → EXECUTE
  *
- * Preserves runtime files (.prizm-docs/, dev-pipeline/state/, .prizmkit/specs/).
+ * Preserves runtime files (.prizmkit/prizm-docs/, .prizmkit/state/, .prizmkit/specs/).
  */
 
 import chalk from 'chalk';

package/src/gitignore-template.js

@@ -9,42 +9,22 @@
  * @returns {string}
  */
 export function generateGitignore(options = {}) {
+  void options;
   const lines = [
     '# ===========================',
     '# PrizmKit Runtime Artifacts',
     '# ===========================',
     '',
-    '# PrizmKit 运行时状态（不提交）',
-    '.prizmkit/state/',
+    '# PrizmKit 运行时全部产物（state/、prizm-docs/、.env、logs 等）',
+    '.prizmkit/*',
     '',
     '# 多 Agent 协作临时工作区',
     '.dev-team/',
     '',
-    '# Prizm 文档（按需决定是否提交）',
-    '# .prizm-docs/',
-    '',
-    '# 规划产物（按需决定是否提交）',
-    '# .prizmkit/plans/',
-    '',
-  ];
-
-  if (options.pipeline) {
-    lines.push(
-      '# Dev-Pipeline 运行时状态（已迁移到 .prizmkit/state/）',
-      '.prizmkit/state/features/',
-      '.prizmkit/state/bugfix/',
-      '.prizmkit/state/refactor/',
-      'dev-pipeline/logs/',
-      'dev-pipeline/*.pid',
-      '',
-    );
-  }
-
-  lines.push(
     '# Playwright CLI 快照和截图',
     '.playwright-cli/',
     '',
-  );
+  ];
 
   lines.push(
     '# ===========================',

package/src/scaffold.js

@@ -405,7 +405,7 @@ export async function installSettings(platform, projectRoot, options, dryRun) {
 
     // Settings
     const permissions = [
-      'Bash(python3 dev-pipeline/scripts/*)',
+      'Bash(python3 .prizmkit/dev-pipeline/scripts/*)',
       'Bash(git add *)',
       'Bash(git commit *)',
       'Bash(git diff *)',
@@ -420,7 +420,7 @@ export async function installSettings(platform, projectRoot, options, dryRun) {
         const pipelineEntries = await fs.readdir(pipelineDir);
         const entryScripts = pipelineEntries.filter(f => /^(run-|launch-|retry-|reset-).*\.sh$/.test(f));
         for (const script of entryScripts) {
-          permissions.push(`Bash(./dev-pipeline/${script} *)`);
+          permissions.push(`Bash(./.prizmkit/dev-pipeline/${script} *)`);
         }
       } catch {
         // Fallback: if readdir fails, add no pipeline permissions
@@ -437,7 +437,7 @@ export async function installSettings(platform, projectRoot, options, dryRun) {
             hooks: [
               {
                 type: 'command',
-                command: 'test -f .prizm-docs/root.prizm && echo "PrizmKit: .prizm-docs found. Read root.prizm for project context." || echo "PrizmKit: No .prizm-docs found. Run /prizmkit-init to bootstrap."',
+                command: 'test -f .prizmkit/prizm-docs/root.prizm && echo "PrizmKit: .prizmkit/prizm-docs found. Read root.prizm for project context." || echo "PrizmKit: No .prizmkit/prizm-docs found. Run /prizmkit-init to bootstrap."',
               },
             ],
           },
@@ -634,14 +634,15 @@ export function resolvePipelineFileList() {
 
 /**
  * 安装 dev-pipeline（纯 Copy 模式）
- * Returns an array of installed file relative paths (relative to dev-pipeline/).
+ * 安装目标：.prizmkit/dev-pipeline/
+ * Returns an array of installed file relative paths (relative to .prizmkit/dev-pipeline/).
  */
 export async function installPipeline(projectRoot, dryRun, { forceOverwrite = false } = {}) {
   const pipelineSource = getPipelineDir();
-  const pipelineTarget = path.join(projectRoot, 'dev-pipeline');
+  const pipelineTarget = path.join(projectRoot, '.prizmkit', 'dev-pipeline');
 
   if (dryRun) {
-    console.log(chalk.gray(`      [dry-run] dev-pipeline/`));
+    console.log(chalk.gray(`      [dry-run] .prizmkit/dev-pipeline/`));
     return [];
   }
 
@@ -666,7 +667,7 @@ export async function installPipeline(projectRoot, dryRun, { forceOverwrite = fa
     const srcStat = await fs.stat(src);
 
     if (await fs.pathExists(tgt) && !forceOverwrite) {
-      console.log(chalk.yellow(`      ⚠ dev-pipeline/${item} 已存在，跳过`));
+      console.log(chalk.yellow(`      ⚠ .prizmkit/dev-pipeline/${item} 已存在，跳过`));
       // Still collect existing files for manifest tracking
       if (srcStat.isDirectory()) {
         installedFiles.push(...collectFilesRecursive(src, item));
@@ -687,14 +688,14 @@ export async function installPipeline(projectRoot, dryRun, { forceOverwrite = fa
     }
   }
 
-  console.log(chalk.green(`      ✓ dev-pipeline/ (${installedCount} 项)`));
+  console.log(chalk.green(`      ✓ .prizmkit/dev-pipeline/ (${installedCount} 项)`));
 
-  // Copy .env.example to project root if it exists in pipeline source
+  // Copy .env.example to .prizmkit/.env.example if it exists in pipeline source
   const envExampleSrc = path.join(pipelineSource, '.env.example');
-  const envExampleTgt = path.join(projectRoot, '.env.example');
+  const envExampleTgt = path.join(projectRoot, '.prizmkit', '.env.example');
   if (await fs.pathExists(envExampleSrc) && !await fs.pathExists(envExampleTgt)) {
     await fs.copy(envExampleSrc, envExampleTgt);
-    console.log(chalk.green(`      ✓ .env.example (pipeline environment configuration)`));
+    console.log(chalk.green(`      ✓ .prizmkit/.env.example (pipeline environment configuration)`));
   }
 
   return installedFiles;

package/src/upgrade.js

@@ -125,13 +125,13 @@ export async function removeRuleFiles(platform, projectRoot, ruleFileNames, dryR
  */
 export async function removePipelineFiles(projectRoot, fileList, dryRun) {
   for (const relPath of fileList) {
-    const filePath = path.join(projectRoot, 'dev-pipeline', relPath);
+    const filePath = path.join(projectRoot, '.prizmkit', 'dev-pipeline', relPath);
     if (await fs.pathExists(filePath)) {
       if (dryRun) {
-        console.log(chalk.gray(`      [dry-run] remove dev-pipeline/${relPath}`));
+        console.log(chalk.gray(`      [dry-run] remove .prizmkit/dev-pipeline/${relPath}`));
       } else {
         await fs.remove(filePath);
-        console.log(chalk.red(`      ✗ removed dev-pipeline/${relPath}`));
+        console.log(chalk.red(`      ✗ removed .prizmkit/dev-pipeline/${relPath}`));
       }
     }
   }