prizmkit 1.1.41 → 1.1.46

package/bundled/VERSION.json

@@ -1,5 +1,5 @@
 {
-  "frameworkVersion": "1.1.41",
-  "bundledAt": "2026-04-30T09:49:08.976Z",
-  "bundledFrom": "13a2ce9"
+  "frameworkVersion": "1.1.46",
+  "bundledAt": "2026-05-20T14:21:52.729Z",
+  "bundledFrom": "f552940"
 }

package/bundled/adapters/claude/settings-adapter.js

@@ -66,8 +66,8 @@ export async function generateSettings(targetRoot, options = {}) {
 
   if (options.pipeline) {
     prizmkitPermissions.push(
-      'Bash(./dev-pipeline/*)',
-      'Bash(python3 dev-pipeline/*)',
+      'Bash(./.prizmkit/dev-pipeline/*)',
+      'Bash(python3 .prizmkit/dev-pipeline/*)',
     );
   }
 
@@ -82,7 +82,7 @@ export async function generateSettings(targetRoot, options = {}) {
   if (options.hooks !== false) {
     if (!existing.hooks) existing.hooks = {};
 
-    // SessionStart hook: remind about .prizm-docs
+    // SessionStart hook: remind about .prizmkit/prizm-docs
     if (!existing.hooks.SessionStart) {
       existing.hooks.SessionStart = [
         {
@@ -90,7 +90,7 @@ export async function generateSettings(targetRoot, options = {}) {
           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."',
             },
           ],
         },

package/bundled/adapters/codebuddy/settings-adapter.js

@@ -35,7 +35,7 @@ export async function generateSettings(targetRoot, options = {}) {
           hooks: [
             {
               type: 'prompt',
-              prompt: 'You are a commit-intent detector for PrizmKit. Analyze the user prompt and determine if the user intends to COMMIT, PUSH, FINISH, SHIP, MERGE, or create a PULL REQUEST.\n\nUser prompt: $ARGUMENTS\n\nIF commit intent detected, respond with:\n{"ok": true, "reason": "PRIZMKIT_DOC_UPDATE_REQUIRED: Before committing, you MUST update .prizm-docs/ per Prizm auto-update protocol. Steps: 1) Run git diff --cached --name-status. 2) Map changed files to modules via root.prizm MODULE_INDEX. 3) Read and update affected .prizm files (only changed sections). 4) Append to changelog.prizm. 5) Stage .prizm files with git add .prizm-docs/. 6) Then proceed with commit using prizmkit-committer workflow. RULES: Never rewrite entire .prizm files. Never add prose. Only update affected sections."}\n\nIF no commit intent, respond with:\n{"ok": true}\n\nRespond with JSON only. No explanation.',
+              prompt: 'You are a commit-intent detector for PrizmKit. Analyze the user prompt and determine if the user intends to COMMIT, PUSH, FINISH, SHIP, MERGE, or create a PULL REQUEST.\n\nUser prompt: $ARGUMENTS\n\nIF commit intent detected, respond with:\n{"ok": true, "reason": "PRIZMKIT_DOC_UPDATE_REQUIRED: Before committing, you MUST update .prizmkit/prizm-docs/ per Prizm auto-update protocol. Steps: 1) Run git diff --cached --name-status. 2) Map changed files to modules via root.prizm MODULE_INDEX. 3) Read and update affected .prizm files (only changed sections). 4) Append to changelog.prizm. 5) Stage .prizm files with git add .prizmkit/prizm-docs/. 6) Then proceed with commit using prizmkit-committer workflow. RULES: Never rewrite entire .prizm files. Never add prose. Only update affected sections."}\n\nIF no commit intent, respond with:\n{"ok": true}\n\nRespond with JSON only. No explanation.',
             },
           ],
         },

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

@@ -18,15 +18,15 @@ You operate in **Plan Challenge** mode: before implementation, you challenge the
 ### Project Context
 
 Before any challenge, you MUST understand the project:
-1. Read `.prizm-docs/root.prizm` — understand architecture, patterns, conventions
-2. Read relevant L1/L2 `.prizm-docs/` files for affected modules — understand RULES, PATTERNS, TRAPS, DECISIONS
+1. Read `.prizmkit/prizm-docs/root.prizm` — understand architecture, patterns, conventions
+2. Read relevant L1/L2 `.prizmkit/prizm-docs/` files for affected modules — understand RULES, PATTERNS, TRAPS, DECISIONS
 3. Read `context-snapshot.md` if it exists — Section 3 has Prizm Context, Section 4 has File Manifest
 
 **File Reading Rule**: Read actual project source files to compare against. Your challenges must be grounded in evidence from existing code, not theoretical concerns. If you cannot find evidence in the codebase, downgrade the severity.
 
 ### Must Do (MUST)
 
-1. Read `.prizm-docs/root.prizm` and relevant module docs BEFORE writing any challenge
+1. Read `.prizmkit/prizm-docs/root.prizm` and relevant module docs BEFORE writing any challenge
 2. Read existing source files in affected modules for comparison
 3. Ground every challenge in specific evidence (file paths, code patterns, existing conventions)
 4. Write `challenge-report.md` with structured findings
@@ -46,7 +46,7 @@ Before any challenge, you MUST understand the project:
 ### Behavioral Rules
 
 ```
-CRIT-01: Always read .prizm-docs/ and existing source before challenging
+CRIT-01: Always read .prizmkit/prizm-docs/ and existing source before challenging
 CRIT-02: Every challenge must reference a specific file path or code pattern as evidence
 CRIT-03: Maximum 10 challenges per report (focus on highest impact)
 CRIT-04: Severity levels: CRITICAL (architecture mismatch), HIGH (style/robustness gap), MEDIUM (minor inconsistency)
@@ -70,15 +70,15 @@ CRIT-10: In voting mode, write to your assigned report file (challenge-report-{A
 
 | Dimension | What to Challenge | Evidence Source |
 |-----------|------------------|----------------|
-| **Architecture Fit** | Does the plan's approach match the project's existing architectural patterns? Would it feel foreign to someone familiar with the codebase? | `.prizm-docs/` PATTERNS, existing module structure |
+| **Architecture Fit** | Does the plan's approach match the project's existing architectural patterns? Would it feel foreign to someone familiar with the codebase? | `.prizmkit/prizm-docs/` PATTERNS, existing module structure |
 | **Integration Planning** | Do proposed interfaces match existing conventions? Are naming patterns consistent with existing code? | Existing source files in the same module/layer |
-| **Alternative Approaches** | Given the project's tech stack and existing patterns, is there a more natural approach that leverages what's already built? | `.prizm-docs/` KEY_FILES, existing utilities/helpers |
-| **Coupling Risk** | Does the task breakdown hide cross-module dependencies? Will changes bleed into areas the plan doesn't mention? | `.prizm-docs/` DEPENDENCIES, import graphs |
+| **Alternative Approaches** | Given the project's tech stack and existing patterns, is there a more natural approach that leverages what's already built? | `.prizmkit/prizm-docs/` KEY_FILES, existing utilities/helpers |
+| **Coupling Risk** | Does the task breakdown hide cross-module dependencies? Will changes bleed into areas the plan doesn't mention? | `.prizmkit/prizm-docs/` DEPENDENCIES, import graphs |
 
 ### Workflow
 
 1. Read `context-snapshot.md` — understand the feature and file manifest
-2. Read `.prizm-docs/root.prizm` and affected L1/L2 docs
+2. Read `.prizmkit/prizm-docs/root.prizm` and affected L1/L2 docs
 3. Read existing source files in modules the plan touches
 4. For each dimension, compare plan decisions against evidence from existing code
 5. Write `challenge-report.md` to `.prizmkit/specs/<feature-slug>/`
@@ -139,7 +139,7 @@ When spawned as one of 3 parallel critics (Critic-A, Critic-B, Critic-C):
 
 | Scenario | Strategy |
 |----------|----------|
-| No `.prizm-docs/` exists (new project) | Skip architecture comparison, focus on internal consistency and robustness only |
+| No `.prizmkit/prizm-docs/` exists (new project) | Skip architecture comparison, focus on internal consistency and robustness only |
 | Module has no existing code to compare | Note in report: "No baseline for style comparison — challenges are based on general best practices" |
 | All challenges are MEDIUM or lower | Write report with "No significant challenges" summary. Do NOT inflate severity |
 | Cannot determine project conventions | Downgrade all style challenges to MEDIUM. Note the limitation in the report |

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

@@ -20,12 +20,12 @@ You are the team's "construction worker" — you build strictly according to blu
 
 ### Project Context
 
-Project documentation is in `.prizm-docs/`. Before implementation, read `context-snapshot.md` (if it exists in `.prizmkit/specs/###-feature-name/`); its Section 3 contains Prizm Context and Section 4 contains a File Manifest with paths and key interfaces.
+Project documentation is in `.prizmkit/prizm-docs/`. Before implementation, read `context-snapshot.md` (if it exists in `.prizmkit/specs/###-feature-name/`); its Section 3 contains Prizm Context and Section 4 contains a File Manifest with paths and key interfaces.
 
 **⚠️ File Reading Rule**: Do NOT re-read source files already listed in Section 4 File Manifest — the manifest already contains their key interfaces. Only read a source file directly if: (a) it is NOT in the manifest, or (b) you need a specific implementation detail not captured in the manifest's interface column. Unnecessary re-reads waste significant context budget.
 
 If the snapshot does not exist:
-1. Read `.prizm-docs/root.prizm` to understand rules and known traps (TRAPS)
+1. Read `.prizmkit/prizm-docs/root.prizm` to understand rules and known traps (TRAPS)
 2. Read relevant L1/L2 docs for affected modules
 3. Read required source files directly
 
@@ -33,7 +33,7 @@ If the snapshot does not exist:
 
 | Path | Purpose |
 |------|---------|
-| `.prizm-docs/` | Architecture index — module structure, interfaces, dependencies, known traps (TRAPS), design decisions (DECISIONS) |
+| `.prizmkit/prizm-docs/` | Architecture index — module structure, interfaces, dependencies, known traps (TRAPS), design decisions (DECISIONS) |
 | `.prizmkit/specs/###-feature-name/` | Feature artifacts — spec.md / plan.md (with Tasks section) |
 
 ### Must Do (MUST)
@@ -44,11 +44,11 @@ If the snapshot does not exist:
 4. Report interface design ambiguities to the Orchestrator immediately (do not assume)
 5. Follow the `/prizmkit-implement` workflow: read plan.md (with Tasks section) + spec.md, implement task by task
 6. Mark `[x]` in the plan.md Tasks section **immediately** after each task is completed (do not batch-mark)
-7. Read the TRAPS section before implementation to avoid known pitfalls: prefer `context-snapshot.md` Section 3; if no snapshot exists, read `.prizm-docs/`
+7. Read the TRAPS section before implementation to avoid known pitfalls: prefer `context-snapshot.md` Section 3; if no snapshot exists, read `.prizmkit/prizm-docs/`
 8. Checkpoint tasks must verify that build and tests pass before proceeding to the next phase
 9. Execute sequential tasks in order; stop on failure. Parallel `[P]` tasks may continue
-10. When creating a new sub-module, generate the corresponding `.prizm-docs/` L2 document. **Batch independent operations**: combine multiple `mkdir -p` into one command; issue multiple independent `Write` calls for different `.prizm-docs/` files in a single message turn (they have no dependencies between them).
-11. **`.prizm-docs/` write safety**: Before writing ANY `.prizm-docs/` file, check if it already exists (`ls <path>`). If it **exists**: only append or update structural fields (KEY_FILES, INTERFACES, DEPENDENCIES, file counts, UPDATED date) — **never overwrite the full file**. DECISIONS and CHANGELOG sections are **append-only** — never delete or replace existing entries. If it does **not** exist: create it only for sub-modules you are actively creating in this session. Do NOT write `.prizm-docs/` files for modules you are not directly creating.
+10. When creating a new sub-module, generate the corresponding `.prizmkit/prizm-docs/` L2 document. **Batch independent operations**: combine multiple `mkdir -p` into one command; issue multiple independent `Write` calls for different `.prizmkit/prizm-docs/` files in a single message turn (they have no dependencies between them).
+11. **`.prizmkit/prizm-docs/` write safety**: Before writing ANY `.prizmkit/prizm-docs/` file, check if it already exists (`ls <path>`). If it **exists**: only append or update structural fields (KEY_FILES, INTERFACES, DEPENDENCIES, file counts, UPDATED date) — **never overwrite the full file**. DECISIONS and CHANGELOG sections are **append-only** — never delete or replace existing entries. If it does **not** exist: create it only for sub-modules you are actively creating in this session. Do NOT write `.prizmkit/prizm-docs/` files for modules you are not directly creating.
 11. After completing ALL tasks, append '## Implementation Log' to context-snapshot.md: files changed/created, key decisions, notable discoveries
 
 ### Never Do (NEVER)
@@ -59,7 +59,7 @@ If the snapshot does not exist:
 - **Do not execute any git operations** (git commit / git add / git reset / git push are all prohibited — the Orchestrator handles commits via /prizmkit-committer)
 - Do not modify any files in `.prizmkit/specs/` except `plan.md` (marking Tasks [x]) and `context-snapshot.md` (appending Implementation Log)
 - Do not use TaskCreate/TaskUpdate to create or modify Orchestrator-level tasks (Task tools are for internal progress tracking only, and task IDs are not shared across agent sub-sessions)
-- **Do not overwrite existing `.prizm-docs/` files in full** — if a doc already exists, only update structural fields; never replace the entire file. Do NOT write `.prizm-docs/` entries for modules you are not actively creating in this session.
+- **Do not overwrite existing `.prizmkit/prizm-docs/` files in full** — if a doc already exists, only update structural fields; never replace the entire file. Do NOT write `.prizmkit/prizm-docs/` entries for modules you are not actively creating in this session.
 
 ### Behavioral Rules
 
@@ -73,17 +73,17 @@ DEV-06: Do not introduce external dependencies not declared in the task descript
 DEV-07: Follow the /prizmkit-implement workflow
 DEV-08: Mark plan.md Tasks section [x] immediately after each task is completed
 DEV-09: TDD: write tests → implement → verify
-DEV-10: Read the TRAPS section before implementing each module: prefer context-snapshot.md Section 3; if no snapshot, read .prizm-docs/
+DEV-10: Read the TRAPS section before implementing each module: prefer context-snapshot.md Section 3; if no snapshot, read .prizmkit/prizm-docs/
 DEV-11: Checkpoint tasks must verify that build and tests pass
-DEV-12: Generate L2 .prizm-docs/ documentation when creating new sub-modules
+DEV-12: Generate L2 .prizmkit/prizm-docs/ documentation when creating new sub-modules
 DEV-13: Executing any git command is prohibited (git add/commit/reset/push are all forbidden)
 DEV-14: If `npm test` has pre-existing failures, do not ignore them — list them explicitly in COMPLETION_SIGNAL for Orchestrator decision
 DEV-18: When tests fail, run `$TEST_CMD 2>&1 | tee /tmp/test-out.txt` ONCE, then grep `/tmp/test-out.txt` for failure details. Never re-run the full test suite just to apply a different grep filter to its output.
 DEV-15: After ALL tasks, append '## Implementation Log' to context-snapshot.md (files changed, key decisions, discoveries)
-DEV-16: Without context-snapshot: read .prizm-docs/ → read source files directly
+DEV-16: Without context-snapshot: read .prizmkit/prizm-docs/ → read source files directly
 DEV-17: DO NOT re-read source files already listed in context-snapshot.md Section 4 File Manifest — the manifest already has their key interfaces. Only read a file directly if: (a) NOT in the manifest, (b) needing an implementation detail beyond the interface summary, or (c) needing a constant/enum/field-name value not representable as a function signature. Unnecessary re-reads waste significant context budget.
 DEV-18: When tests fail, run `$TEST_CMD 2>&1 | tee /tmp/test-out.txt` ONCE, then grep `/tmp/test-out.txt` for failure details. Never re-run the full test suite just to apply a different grep filter to its output.
-DEV-19: Before writing any `.prizm-docs/` file, check if it exists. If it exists: only update structural fields (KEY_FILES, INTERFACES, DEPENDENCIES, file counts, UPDATED) — never overwrite the full file. DECISIONS/CHANGELOG are append-only. Only create new L2 docs for sub-modules you are actively creating in this session.
+DEV-19: Before writing any `.prizmkit/prizm-docs/` file, check if it exists. If it exists: only update structural fields (KEY_FILES, INTERFACES, DEPENDENCIES, file counts, UPDATED) — never overwrite the full file. DECISIONS/CHANGELOG are append-only. Only create new L2 docs for sub-modules you are actively creating in this session.
 ```
 
 ### Workflow
@@ -91,7 +91,7 @@ DEV-19: Before writing any `.prizm-docs/` file, check if it exists. If it exists
 1. Receive task assignment
 2. Read `.prizmkit/specs/###-feature-name/context-snapshot.md` (if it exists) — Section 3 contains Prizm Context, Section 4 contains a File Manifest.
    **DO NOT re-read source files listed in Section 4** — the manifest already has their interfaces. Only read a source file if it is NOT in the manifest, or you need a specific detail beyond what the interface column provides. If the snapshot does not exist:
-   a. Read `.prizm-docs/root.prizm` and relevant module documentation
+   a. Read `.prizmkit/prizm-docs/root.prizm` and relevant module documentation
    b. Read required source files directly
 3. Read `plan.md` (with Tasks section) and `spec.md` in `.prizmkit/specs/###-feature-name/`
 4. For each assigned task, execute in plan.md Tasks order:
@@ -102,7 +102,7 @@ DEV-19: Before writing any `.prizm-docs/` file, check if it exists. If it exists
    e. Send STATUS_UPDATE to the Orchestrator
 5. For checkpoint tasks, verify that build and tests pass before continuing
 6. On interface design ambiguity, send ESCALATION (do not assume)
-7. If a new sub-module was created, generate the corresponding `.prizm-docs/` L2 document
+7. If a new sub-module was created, generate the corresponding `.prizmkit/prizm-docs/` L2 document
 8. Send COMPLETION_SIGNAL
 
 ### Exception Handling

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

@@ -20,7 +20,7 @@ You are the team's "senior engineer doing code review" — you diagnose problems
    - Section 3: Prizm Context (RULES, PATTERNS, TRAPS to check against)
    - Section 4: File Manifest (original file structure — avoid re-reading files already listed here)
    - `## Implementation Log`: what Dev changed, key decisions, discoveries
-2. If no `context-snapshot.md`: read `spec.md`, `plan.md` from the artifact directory, then `.prizm-docs/root.prizm` and relevant L1/L2 docs
+2. If no `context-snapshot.md`: read `spec.md`, `plan.md` from the artifact directory, then `.prizmkit/prizm-docs/root.prizm` and relevant L1/L2 docs
 3. Identify changed files from `## Implementation Log` or completed tasks in plan.md
 
 **File Reading Rule**: Read ONLY files listed in the Implementation Log for diagnosis — do not explore unrelated files. Exception: during Fix Strategy Formulation, you MAY read additional files to trace impact (callers, dependents, shared patterns).
@@ -66,7 +66,7 @@ When Dev has applied fixes and returns for re-review:
 1. Run `/prizmkit-code-review` for diagnosis and fix strategy
 2. Write and execute integration tests covering all goals from spec.md
 3. Verify implementation conforms to interface designs in plan.md
-4. Check code conforms to `.prizm-docs/` RULES and PATTERNS
+4. Check code conforms to `.prizmkit/prizm-docs/` RULES and PATTERNS
 5. Every finding must include: Root Cause, Impact, Fix Strategy, Code Guidance, Verification Criteria
 6. Group related findings and order Fix Instructions by dependency
 7. On re-review (iteration > 1): check only Verification Criteria + scan for regressions

package/bundled/dev-pipeline/.env.example

@@ -1,15 +1,15 @@
 # PrizmKit Dev-Pipeline Environment Configuration
 # ================================================
-# Copy this file to .env and uncomment the variables you want to set.
+# Copy this file to .prizmkit/.env and uncomment the variables you want to set.
 # All pipeline scripts (run-feature.sh, run-bugfix.sh, etc.) automatically
-# load .env from the project root.
+# load .prizmkit/.env via lib/common.sh.
 #
 # Priority: Environment variables set before script execution ALWAYS take
-# precedence over values in .env. This means you can still do:
-#   MODEL=claude-opus-4 ./dev-pipeline/run-feature.sh run
-# and it will override the .env value.
+# precedence over values in .prizmkit/.env. This means you can still do:
+#   MODEL=claude-opus-4 ./.prizmkit/dev-pipeline/run-feature.sh run
+# and it will override the .prizmkit/.env value.
 #
-# If .env does not exist, all defaults apply — no error is raised.
+# If .prizmkit/.env does not exist, all defaults apply — no error is raised.
 
 # ─── Runtime Environment ──────────────────────────────────────────────
 # PRIZMKIT_ENV=test          # "test" = output bootstrap prompts to console for debugging

package/bundled/dev-pipeline/README.md

@@ -17,18 +17,18 @@ Autonomous development pipeline that drives the `prizm-dev-team` multi-agent tea
 #    Output: .prizmkit/plans/feature-list.json in project root
 
 # 2. Initialize pipeline state
-python3 dev-pipeline/scripts/init-pipeline.py \
+python3 .prizmkit/dev-pipeline/scripts/init-pipeline.py \
   --feature-list .prizmkit/plans/feature-list.json \
   --state-dir .prizmkit/state/features
 
 # 3. Run the pipeline (foreground, Ctrl+C to pause, re-run to resume)
-./dev-pipeline/run-feature.sh run .prizmkit/plans/feature-list.json
+./.prizmkit/dev-pipeline/run-feature.sh run .prizmkit/plans/feature-list.json
 
 # 4. Check progress at any time (from another terminal)
-./dev-pipeline/run-feature.sh status .prizmkit/plans/feature-list.json
+./.prizmkit/dev-pipeline/run-feature.sh status .prizmkit/plans/feature-list.json
 
 # 5. Or run as a background daemon
-./dev-pipeline/launch-feature-daemon.sh start .prizmkit/plans/feature-list.json
+./.prizmkit/dev-pipeline/launch-feature-daemon.sh start .prizmkit/plans/feature-list.json
 ```
 
 ---
@@ -61,19 +61,19 @@ Main entry point. Drives the full feature development pipeline.
 
 ```bash
 # Run all features
-./dev-pipeline/run-feature.sh run .prizmkit/plans/feature-list.json
+./.prizmkit/dev-pipeline/run-feature.sh run .prizmkit/plans/feature-list.json
 
 # Run a single feature
-./dev-pipeline/run-feature.sh run F-007
+./.prizmkit/dev-pipeline/run-feature.sh run F-007
 
 # Dry run — inspect the generated prompt without spawning a session
-./dev-pipeline/run-feature.sh run F-007 --dry-run
+./.prizmkit/dev-pipeline/run-feature.sh run F-007 --dry-run
 
 # Resume from Phase 6 (implementation)
-./dev-pipeline/run-feature.sh run .prizmkit/plans/feature-list.json --resume-phase 6
+./.prizmkit/dev-pipeline/run-feature.sh run .prizmkit/plans/feature-list.json --resume-phase 6
 
 # With timeout per session
-SESSION_TIMEOUT=7200 ./dev-pipeline/run-feature.sh run .prizmkit/plans/feature-list.json
+SESSION_TIMEOUT=7200 ./.prizmkit/dev-pipeline/run-feature.sh run .prizmkit/plans/feature-list.json
 ```
 
 If `.prizmkit/plans/feature-list.json` path is omitted, defaults to `.prizmkit/plans/feature-list.json` in the project root.
@@ -104,10 +104,10 @@ Resets a feature's state so it can be re-executed from scratch.
 **Examples:**
 
 ```bash
-./dev-pipeline/reset-feature.sh F-007                    # Reset status only
-./dev-pipeline/reset-feature.sh F-007 --clean            # Reset + delete artifacts
-./dev-pipeline/reset-feature.sh F-007 --clean --run      # Reset + clean + retry
-./dev-pipeline/reset-feature.sh F-007 --clean my-features.json
+./.prizmkit/dev-pipeline/reset-feature.sh F-007                    # Reset status only
+./.prizmkit/dev-pipeline/reset-feature.sh F-007 --clean            # Reset + delete artifacts
+./.prizmkit/dev-pipeline/reset-feature.sh F-007 --clean --run      # Reset + clean + retry
+./.prizmkit/dev-pipeline/reset-feature.sh F-007 --clean my-features.json
 ```
 
 ---
@@ -138,7 +138,7 @@ Manages `run-feature.sh` as a background daemon process with PID tracking and lo
 **`--env` format:** Pass environment variables as a quoted string:
 
 ```bash
-./dev-pipeline/launch-feature-daemon.sh start .prizmkit/plans/feature-list.json \
+./.prizmkit/dev-pipeline/launch-feature-daemon.sh start .prizmkit/plans/feature-list.json \
   --mode standard \
   --env "MAX_RETRIES=5 SESSION_TIMEOUT=3600 MODEL=claude-sonnet-4.6"
 ```
@@ -564,10 +564,10 @@ Also exports: `log_info`, `log_warn`, `log_error`, `log_success` (with timestamp
 ```bash
 # All env vars in one invocation
 MAX_RETRIES=5 SESSION_TIMEOUT=7200 MODEL=claude-sonnet-4.6 VERBOSE=1 \
-  ./dev-pipeline/run-feature.sh run .prizmkit/plans/feature-list.json
+  ./.prizmkit/dev-pipeline/run-feature.sh run .prizmkit/plans/feature-list.json
 
 # Via daemon with --env
-./dev-pipeline/launch-feature-daemon.sh start .prizmkit/plans/feature-list.json \
+./.prizmkit/dev-pipeline/launch-feature-daemon.sh start .prizmkit/plans/feature-list.json \
   --mode standard \
   --env "MAX_RETRIES=5 SESSION_TIMEOUT=3600 AUTO_PUSH=1"
 ```
@@ -604,13 +604,13 @@ Specify a model for individual features in `.prizmkit/plans/feature-list.json`:
 
 ```bash
 # All features without a per-feature model use Sonnet
-MODEL=claude-sonnet-4.6 ./dev-pipeline/run-feature.sh run .prizmkit/plans/feature-list.json
+MODEL=claude-sonnet-4.6 ./.prizmkit/dev-pipeline/run-feature.sh run .prizmkit/plans/feature-list.json
 
 # Retry with Opus
-MODEL=claude-opus-4.6 ./dev-pipeline/reset-feature.sh F-007 --clean --run
+MODEL=claude-opus-4.6 ./.prizmkit/dev-pipeline/reset-feature.sh F-007 --clean --run
 
 # Test which model the CLI is using
-MODEL=claude-sonnet-4.6 ./dev-pipeline/run-feature.sh test-cli
+MODEL=claude-sonnet-4.6 ./.prizmkit/dev-pipeline/run-feature.sh test-cli
 ```
 
 ### Dry-Run Model Verification
@@ -618,7 +618,7 @@ MODEL=claude-sonnet-4.6 ./dev-pipeline/run-feature.sh test-cli
 Use `--dry-run` to verify which model will be used without spawning a session:
 
 ```bash
-./dev-pipeline/run-feature.sh run F-017 --dry-run
+./.prizmkit/dev-pipeline/run-feature.sh run F-017 --dry-run
 # Output includes: "Feature Model: claude-opus-4.6"
 ```
 
@@ -655,15 +655,15 @@ To permanently configure, create `.prizmkit/config.json`:
 Or override per-invocation:
 
 ```bash
-AI_CLI=claude ./dev-pipeline/run-feature.sh run .prizmkit/plans/feature-list.json
+AI_CLI=claude ./.prizmkit/dev-pipeline/run-feature.sh run .prizmkit/plans/feature-list.json
 ```
 
 ### Testing AI CLI (`test-cli`)
 
 ```bash
-./dev-pipeline/run-feature.sh test-cli
-MODEL=claude-sonnet-4.6 ./dev-pipeline/run-feature.sh test-cli
-AI_CLI=cbc ./dev-pipeline/run-feature.sh test-cli
+./.prizmkit/dev-pipeline/run-feature.sh test-cli
+MODEL=claude-sonnet-4.6 ./.prizmkit/dev-pipeline/run-feature.sh test-cli
+AI_CLI=cbc ./.prizmkit/dev-pipeline/run-feature.sh test-cli
 ```
 
 ---
@@ -758,25 +758,25 @@ cat .prizmkit/state/features/features/F-003/sessions/F-003-*/logs/session.log |
 
 ```bash
 # Check what failed
-./dev-pipeline/run-feature.sh status .prizmkit/plans/feature-list.json
+./.prizmkit/dev-pipeline/run-feature.sh status .prizmkit/plans/feature-list.json
 
 # Review session logs
 cat .prizmkit/state/features/features/F-XXX/sessions/*/logs/session.log
 
 # Option A: Fix manually and mark complete
-python3 dev-pipeline/scripts/update-feature-status.py \
+python3 .prizmkit/dev-pipeline/scripts/update-feature-status.py \
   --feature-list .prizmkit/plans/feature-list.json \
   --state-dir .prizmkit/state/features \
   --feature-id F-XXX --action complete
 
 # Option B: Reset for retry
-python3 dev-pipeline/scripts/update-feature-status.py \
+python3 .prizmkit/dev-pipeline/scripts/update-feature-status.py \
   --feature-list .prizmkit/plans/feature-list.json \
   --state-dir .prizmkit/state/features \
   --feature-id F-XXX --action reset
 
 # Resume
-./dev-pipeline/run-feature.sh run .prizmkit/plans/feature-list.json
+./.prizmkit/dev-pipeline/run-feature.sh run .prizmkit/plans/feature-list.json
 ```
 
 ---
@@ -790,11 +790,11 @@ The bug fix pipeline provides the same autonomous outer-loop as the feature pipe
 ```bash
 # 1. Generate bug fix list (via bug-planner skill)
 # 2. Run foreground
-./dev-pipeline/run-bugfix.sh run .prizmkit/plans/bug-fix-list.json
+./.prizmkit/dev-pipeline/run-bugfix.sh run .prizmkit/plans/bug-fix-list.json
 # 3. Or as daemon
-./dev-pipeline/launch-bugfix-daemon.sh start .prizmkit/plans/bug-fix-list.json
+./.prizmkit/dev-pipeline/launch-bugfix-daemon.sh start .prizmkit/plans/bug-fix-list.json
 # 4. Check progress
-./dev-pipeline/run-bugfix.sh status .prizmkit/plans/bug-fix-list.json
+./.prizmkit/dev-pipeline/run-bugfix.sh status .prizmkit/plans/bug-fix-list.json
 ```
 
 ### Bug Fix Execution Flow
@@ -852,7 +852,7 @@ run-bugfix.sh main loop
 ## Directory Structure
 
 ```
-dev-pipeline/
+.prizmkit/dev-pipeline/
 +-- run-feature.sh                           # Main pipeline runner (features)
 +-- reset-feature.sh                 # Reset & retry failed feature
 +-- reset-feature.sh                 # Reset/clean feature for re-execution

package/bundled/dev-pipeline/assets/prizm-dev-team-integration.md

@@ -37,7 +37,7 @@ Note: The Orchestrator role is handled by the main agent (session orchestrator)
 
 ## Pipeline Scripts
 
-Located at `dev-pipeline/scripts/`:
+Located at `.prizmkit/dev-pipeline/scripts/`:
 
 | Script | Purpose |
 |--------|---------|

package/bundled/dev-pipeline/launch-bugfix-daemon.sh

@@ -24,8 +24,11 @@ set -euo pipefail
 # ============================================================
 
 SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-PROJECT_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)"
-STATE_DIR="${PROJECT_ROOT}/.prizmkit/state/bugfix"
+
+# Source shared common helpers (exports PIPELINE_DIR/PRIZMKIT_DIR/PROJECT_ROOT)
+source "$SCRIPT_DIR/lib/common.sh"
+
+STATE_DIR="${PRIZMKIT_DIR}/state/bugfix"
 PID_FILE="$STATE_DIR/.pipeline.pid"
 LOG_FILE="$STATE_DIR/pipeline-daemon.log"
 RUN_SCRIPT="$SCRIPT_DIR/run-bugfix.sh"

package/bundled/dev-pipeline/launch-feature-daemon.sh

@@ -24,8 +24,11 @@ set -euo pipefail
 # ============================================================
 
 SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-PROJECT_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)"
-STATE_DIR="${PROJECT_ROOT}/.prizmkit/state/features"
+
+# Source shared common helpers (exports PIPELINE_DIR/PRIZMKIT_DIR/PROJECT_ROOT)
+source "$SCRIPT_DIR/lib/common.sh"
+
+STATE_DIR="${PRIZMKIT_DIR}/state/features"
 PID_FILE="$STATE_DIR/.pipeline.pid"
 LOG_FILE="$STATE_DIR/pipeline-daemon.log"
 RUN_SCRIPT="$SCRIPT_DIR/run-feature.sh"

package/bundled/dev-pipeline/launch-refactor-daemon.sh

@@ -24,8 +24,11 @@ set -euo pipefail
 # ============================================================
 
 SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-PROJECT_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)"
-STATE_DIR="${PROJECT_ROOT}/.prizmkit/state/refactor"
+
+# Source shared common helpers (exports PIPELINE_DIR/PRIZMKIT_DIR/PROJECT_ROOT)
+source "$SCRIPT_DIR/lib/common.sh"
+
+STATE_DIR="${PRIZMKIT_DIR}/state/refactor"
 PID_FILE="$STATE_DIR/.pipeline.pid"
 LOG_FILE="$STATE_DIR/pipeline-daemon.log"
 RUN_SCRIPT="$SCRIPT_DIR/run-refactor.sh"

package/bundled/dev-pipeline/lib/common.sh

@@ -23,6 +23,37 @@ log_warn()    { echo -e "${YELLOW}[WARN]${NC}    $(date '+%Y-%m-%d %H:%M:%S') $*
 log_error()   { echo -e "${RED}[ERROR]${NC}   $(date '+%Y-%m-%d %H:%M:%S') $*"; }
 log_success() { echo -e "${GREEN}[SUCCESS]${NC} $(date '+%Y-%m-%d %H:%M:%S') $*"; }
 
+# ============================================================
+# Path resolution (single source of truth)
+# ============================================================
+# Exports three directories used throughout dev-pipeline scripts:
+#   PIPELINE_DIR  — directory containing the dev-pipeline scripts
+#   PRIZMKIT_DIR  — the .prizmkit/ runtime directory
+#   PROJECT_ROOT  — the user's project root
+#
+# Layout detection (no override case):
+#   - If PIPELINE_DIR's parent is named ".prizmkit" → user-install layout
+#       (.prizmkit/dev-pipeline/). PRIZMKIT_DIR = parent.
+#   - Otherwise → framework repo source (<repo>/dev-pipeline/).
+#       PROJECT_ROOT = parent, PRIZMKIT_DIR = <repo>/.prizmkit.
+#
+# Callers (tests) may pre-set any of these env vars to override detection.
+if [[ -z "${PIPELINE_DIR:-}" ]]; then
+    PIPELINE_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
+fi
+if [[ -z "${PRIZMKIT_DIR:-}" || -z "${PROJECT_ROOT:-}" ]]; then
+    _pipeline_parent="$(dirname "$PIPELINE_DIR")"
+    if [[ "$(basename "$_pipeline_parent")" == ".prizmkit" ]]; then
+        : "${PRIZMKIT_DIR:=$_pipeline_parent}"
+        : "${PROJECT_ROOT:=$(dirname "$_pipeline_parent")}"
+    else
+        : "${PROJECT_ROOT:=$_pipeline_parent}"
+        : "${PRIZMKIT_DIR:=$PROJECT_ROOT/.prizmkit}"
+    fi
+    unset _pipeline_parent
+fi
+export PIPELINE_DIR PRIZMKIT_DIR PROJECT_ROOT
+
 # ============================================================
 # .env file loading
 # ============================================================
@@ -96,11 +127,9 @@ prizm_log_bootstrap_prompt() {
 #   PLATFORM
 #   PRIZMKIT_PLATFORM
 prizm_detect_cli_and_platform() {
-    # Load .env from project root if it exists (does not override existing env vars)
-    local _env_root
-    _env_root="$(cd "$(dirname "${BASH_SOURCE[0]}")/../.." 2>/dev/null && pwd)" || true
-    if [[ -n "$_env_root" ]]; then
-        prizm_load_env "$_env_root/.env"
+    # Load .env from .prizmkit/.env if it exists (does not override existing env vars)
+    if [[ -n "${PRIZMKIT_DIR:-}" ]]; then
+        prizm_load_env "$PRIZMKIT_DIR/.env"
     fi
 
     local _raw_cli=""

package/bundled/dev-pipeline/reset-bug.sh

@@ -43,8 +43,11 @@ set -euo pipefail
 # ============================================================
 
 SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-PROJECT_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)"
-STATE_DIR="${PROJECT_ROOT}/.prizmkit/state/bugfix"
+
+# Source shared common helpers (exports PIPELINE_DIR/PRIZMKIT_DIR/PROJECT_ROOT)
+source "$SCRIPT_DIR/lib/common.sh"
+
+STATE_DIR="${PRIZMKIT_DIR}/state/bugfix"
 SCRIPTS_DIR="$SCRIPT_DIR/scripts"
 
 # Colors
@@ -198,7 +201,6 @@ fi
 # Process each bug
 # ============================================================
 
-PROJECT_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)"
 RESET_COUNT=0
 FAIL_COUNT=0
 
@@ -385,9 +387,9 @@ if [[ "$DO_RUN" == true && ${#BUG_IDS[@]} -eq 1 ]]; then
     echo ""
     exec "$SCRIPT_DIR/run-bugfix.sh" run "${BUG_IDS[0]}" "$BUG_LIST"
 else
-    log_info "  ./dev-pipeline/run-bugfix.sh run .prizmkit/plans/bug-fix-list.json         # Resume pipeline from first pending"
+    log_info "  ./.prizmkit/dev-pipeline/run-bugfix.sh run .prizmkit/plans/bug-fix-list.json         # Resume pipeline from first pending"
     if [[ ${#BUG_IDS[@]} -eq 1 ]]; then
-        log_info "  ./dev-pipeline/run-bugfix.sh run ${BUG_IDS[0]}     # Run single bug"
+        log_info "  ./.prizmkit/dev-pipeline/run-bugfix.sh run ${BUG_IDS[0]}     # Run single bug"
     fi
 fi
 echo ""

package/bundled/dev-pipeline/reset-feature.sh

@@ -43,8 +43,11 @@ set -euo pipefail
 # ============================================================
 
 SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-PROJECT_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)"
-STATE_DIR="${PROJECT_ROOT}/.prizmkit/state/features"
+
+# Source shared common helpers (exports PIPELINE_DIR/PRIZMKIT_DIR/PROJECT_ROOT)
+source "$SCRIPT_DIR/lib/common.sh"
+
+STATE_DIR="${PRIZMKIT_DIR}/state/features"
 SCRIPTS_DIR="$SCRIPT_DIR/scripts"
 
 # Colors
@@ -198,7 +201,6 @@ fi
 # Process each feature
 # ============================================================
 
-PROJECT_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)"
 RESET_COUNT=0
 FAIL_COUNT=0
 
@@ -396,9 +398,9 @@ if [[ "$DO_RUN" == true && ${#FEATURE_IDS[@]} -eq 1 ]]; then
     echo ""
     exec "$SCRIPT_DIR/run-feature.sh" run "${FEATURE_IDS[0]}" "$FEATURE_LIST"
 else
-    log_info "  ./dev-pipeline/run-feature.sh run .prizmkit/plans/feature-list.json         # Resume pipeline from first pending"
+    log_info "  ./.prizmkit/dev-pipeline/run-feature.sh run .prizmkit/plans/feature-list.json         # Resume pipeline from first pending"
     if [[ ${#FEATURE_IDS[@]} -eq 1 ]]; then
-        log_info "  ./dev-pipeline/run-feature.sh run ${FEATURE_IDS[0]}     # Run single feature"
+        log_info "  ./.prizmkit/dev-pipeline/run-feature.sh run ${FEATURE_IDS[0]}     # Run single feature"
     fi
 fi
 echo ""