prizmkit 1.0.45 → 1.0.66

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

@@ -5,7 +5,7 @@
 - **Feature ID**: {{FEATURE_ID}} | **Session**: {{SESSION_ID}} | **Run**: {{RUN_ID}}
 - **Complexity**: {{COMPLEXITY}} | **Retry**: {{RETRY_COUNT}} / {{MAX_RETRIES}}
 - **Previous Status**: {{PREV_SESSION_STATUS}} | **Resume From**: {{RESUME_PHASE}}
-- **Init**: {{INIT_DONE}} | Artifacts: spec={{HAS_SPEC}} plan={{HAS_PLAN}} tasks={{HAS_TASKS}}
+- **Init**: {{INIT_DONE}} | Artifacts: spec={{HAS_SPEC}} plan={{HAS_PLAN}}
 
 ## Your Mission
 
@@ -13,7 +13,7 @@ You are the **session orchestrator**. Implement Feature {{FEATURE_ID}}: "{{FEATU
 
 **CRITICAL**: You MUST NOT exit until ALL work is complete and session-status.json is written. When you spawn subagents, wait for each to finish (run_in_background=false). Do NOT spawn agents in background and exit — that kills the session.
 
-**Tier 3 — Full Team**: Dev + Reviewer agents spawned directly via Task tool. Full 7-phase pipeline.
+**Tier 3 — Full Team**: For complex features, use the full pipeline (Phase 0–6) with Dev + Reviewer agents spawned via the Agent tool.
 
 ### Feature Description
 
@@ -71,7 +71,6 @@ LLM context is frozen at prompt time. Modifying a skill source file during this
 .prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md  ← orchestrator writes, all subagents read
 .prizmkit/specs/{{FEATURE_SLUG}}/spec.md
 .prizmkit/specs/{{FEATURE_SLUG}}/plan.md              ← includes Tasks section
-.prizmkit/specs/REGISTRY.md
 ```
 
 **`context-snapshot.md`** is the shared knowledge base. Orchestrator writes it once; Dev and Reviewer read it instead of re-scanning source files. This eliminates redundant I/O across all agents.
@@ -117,9 +116,7 @@ $TEST_CMD 2>&1 | tail -20
 Save the list of **pre-existing failing tests** (if any) as `BASELINE_FAILURES`. These are known failures that existed before this session — Dev must NOT be blamed for them, but must list them in COMPLETION_SIGNAL.
 {{END_IF_INIT_DONE}}
 
-### Step 1: Team Setup
-
-No TeamCreate required. Agents are spawned directly via the `Task` tool using `subagent_type`.
+### Step 1: Initialize
 
 1. Run init script:
    `python3 {{INIT_SCRIPT_PATH}} --project-root {{PROJECT_ROOT}} --feature-id {{FEATURE_ID}} --feature-slug {{FEATURE_SLUG}}`
@@ -127,10 +124,6 @@ No TeamCreate required. Agents are spawned directly via the `Task` tool using `s
 2. Check for existing artifacts:
    `ls .prizmkit/specs/{{FEATURE_SLUG}}/ 2>/dev/null`
 
-Agent files are at:
-- Dev: `{{DEV_SUBAGENT_PATH}}`
-- Reviewer: `{{REVIEWER_SUBAGENT_PATH}}`
-
 {{IF_FRESH_START}}
 ```bash
 python3 {{INIT_SCRIPT_PATH}} --project-root {{PROJECT_ROOT}} --feature-id {{FEATURE_ID}} --feature-slug {{FEATURE_SLUG}}
@@ -189,32 +182,32 @@ ls .prizmkit/specs/{{FEATURE_SLUG}}/spec.md .prizmkit/specs/{{FEATURE_SLUG}}/pla
 
 **CP-1**: Both spec.md and plan.md exist.
 
-### Phase 4: Analyze — Reviewer Agent
+### Phase 3: Analyze — Reviewer Agent
 
-Spawn Reviewer agent (Task tool, subagent_type="prizm-dev-team-reviewer", run_in_background=false).
+Spawn Reviewer agent (Agent tool, subagent_type="prizm-dev-team-reviewer", run_in_background=false).
 
 Prompt:
 > "Read {{REVIEWER_SUBAGENT_PATH}}. For feature {{FEATURE_ID}} (slug: {{FEATURE_SLUG}}):
 > 1. Read `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` FIRST — all source files and project context are there. Do NOT re-read individual source files.
-> 2. Run prizmkit-analyze: cross-check `spec.md`, `plan.md`, and `tasks.md` for consistency.
+> 2. Run prizmkit-analyze: cross-check `spec.md` and `plan.md` (including Tasks section) for consistency.
 > 3. Before flagging CRITICAL or HIGH issues, verify each against Section 4 of the snapshot. Do NOT report based on incomplete information.
 > Report: CRITICAL, HIGH, MEDIUM issues found (or 'No issues found')."
 
 Wait for Reviewer to return.
-- If CRITICAL issues found: fix them yourself — read `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` for full project context. Fix ONLY the listed CRITICAL issues in spec.md/plan.md/tasks.md. Then re-run analyze (max 1 round).
+- If CRITICAL issues found: fix them yourself — read `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` for full project context. Fix ONLY the listed CRITICAL issues in spec.md/plan.md. Then re-run analyze (max 1 round).
 
 **CP-2**: No CRITICAL issues.
 
-### Phase 5: Implement — Dev Agent
+### Phase 4: Implement — Dev Agent
 
-Before spawning Dev, check tasks.md:
+Before spawning Dev, check plan.md Tasks section:
 ```bash
-grep -c '^\- \[ \]' .prizmkit/specs/{{FEATURE_SLUG}}/tasks.md 2>/dev/null || echo 0
+grep -c '^\- \[ \]' .prizmkit/specs/{{FEATURE_SLUG}}/plan.md 2>/dev/null || echo 0
 ```
-- If result is `0` (all tasks already `[x]`) → **SKIP Phase 5**, go directly to Phase 6. Do NOT spawn Dev.
+- If result is `0` (all tasks already `[x]`) → **SKIP Phase 4**, go directly to Phase 5. Do NOT spawn Dev.
 - If result is non-zero → spawn Dev agent below.
 
-Spawn Dev agent (Task tool, subagent_type="prizm-dev-team-dev", run_in_background=false).
+Spawn Dev agent (Agent tool, subagent_type="prizm-dev-team-dev", run_in_background=false).
 
 {{IF_MODE_SELF_EVOLVE}}
 **Framework Self-Evolve — Dev Extra Instructions**:
@@ -230,8 +223,8 @@ Append the following to the Dev agent prompt:
 Prompt:
 > "Read {{DEV_SUBAGENT_PATH}}. Implement feature {{FEATURE_ID}} (slug: {{FEATURE_SLUG}}) using TDD.
 > 1. Read `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` FIRST — all source files and context are there. Do NOT re-read individual source files.
-> 2. Read `plan.md` and `tasks.md` from `.prizmkit/specs/{{FEATURE_SLUG}}/`.
-> 3. Implement task-by-task. Mark each `[x]` in tasks.md **immediately** after completion (do NOT batch).
+> 2. Read `plan.md` (including Tasks section) from `.prizmkit/specs/{{FEATURE_SLUG}}/`.
+> 3. Implement task-by-task. Mark each `[x]` in plan.md Tasks section **immediately** after completion (do NOT batch).
 > 4. Use `TEST_CMD=<TEST_CMD>` to run tests — do NOT explore alternative test commands.
 > 5. After ALL tasks done, append 'Implementation Log' to context-snapshot.md: files changed/created, key decisions, deviations from plan.
 > 6. Do NOT execute any git commands (no git add/commit/reset/push).
@@ -239,11 +232,11 @@ Prompt:
 > Do NOT exit until all tasks are [x] and the Implementation Log is written."
 
 Wait for Dev to return. **If Dev times out before all tasks are `[x]`**:
-1. Check progress: `grep -c '^\- \[ \]' .prizmkit/specs/{{FEATURE_SLUG}}/tasks.md`
+1. Check progress: `grep -c '^\- \[ \]' .prizmkit/specs/{{FEATURE_SLUG}}/plan.md`
 2. If any tasks remain: re-spawn Dev with this recovery prompt:
    > "Read {{DEV_SUBAGENT_PATH}}. You are resuming implementation of feature {{FEATURE_ID}} (slug: {{FEATURE_SLUG}}).
    > 1. Read `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` — Section 4 has original source, 'Implementation Log' (if present) has what was already done. Do NOT re-read individual source files.
-   > 2. Read `tasks.md` — complete ONLY the remaining `[ ]` tasks. Do NOT redo completed `[x]` tasks.
+   > 2. Read plan.md Tasks section — complete ONLY the remaining `[ ]` tasks. Do NOT redo completed `[x]` tasks.
    > 3. Use `TEST_CMD=<TEST_CMD>` to run tests.
    > 4. Append progress to 'Implementation Log' in context-snapshot.md.
    > 5. Do NOT execute any git commands."
@@ -251,9 +244,9 @@ Wait for Dev to return. **If Dev times out before all tasks are `[x]`**:
 
 All tasks `[x]`, tests pass.
 
-### Phase 6: Review — Reviewer Agent
+### Phase 5: Review — Reviewer Agent
 
-Spawn Reviewer agent (Task tool, subagent_type="prizm-dev-team-reviewer", run_in_background=false).
+Spawn Reviewer agent (Agent tool, subagent_type="prizm-dev-team-reviewer", run_in_background=false).
 
 {{IF_MODE_SELF_EVOLVE}}
 **Framework Self-Evolve — Reviewer Extra Instructions**:
@@ -287,7 +280,8 @@ Wait for Reviewer to return.
 
 **CP-3**: Integration tests pass, verdict is not NEEDS_FIXES.
 
-### Phase 7: Summarize & Commit — DO NOT SKIP
+
+### Phase 6: Retrospective & Commit — DO NOT SKIP
 
 {{IF_MODE_SELF_EVOLVE}}
 **Framework Validation Gate (self-evolve mode)**:
@@ -310,7 +304,7 @@ bash {{VALIDATOR_SCRIPTS_DIR}}/validate-framework.sh
 Then set `"reload_needed": true` in session-status.json.
 {{END_IF_MODE_SELF_EVOLVE}}
 
-**For bug fixes**: skip `/prizmkit-summarize`, skip retrospective, and use `fix(<scope>):` commit prefix.
+**For bug fixes**: run `/prizmkit-retrospective` for structural sync only (skip knowledge injection unless a new TRAPS was discovered). Use `fix(<scope>):` commit prefix.
 
 **7a.** Check if feature already committed:
 ```bash
@@ -319,21 +313,11 @@ git log --oneline | grep "{{FEATURE_ID}}" | head -3
 - If a commit for `{{FEATURE_ID}}` already exists → **skip 7c** (do NOT run /prizmkit-committer, do NOT run git reset, do NOT stage or unstage anything). Proceed directly to Step 3.
 - If no existing commit → proceed normally with 7a–7c.
 
-**7b.** Run `/prizmkit-summarize` → archive to REGISTRY.md
-
-**7b.5.** Update prizm-docs (feature sessions):
-- Read the 'Implementation Log' in `context-snapshot.md` to identify changed files
-- For each changed file, check if any related `.prizm-docs/` L1/L2 doc needs updating (new APIs, changed behavior, new TRAPS)
-- Update `.prizm-docs/changelog.prizm`: append one-line entry `- feat({{FEATURE_ID}}): {{FEATURE_TITLE}}`
-- Stage all modified prizm-docs: `git add .prizm-docs/`
-- Pipeline docs pass condition is `REGISTRY.md` OR `.prizm-docs/` changed in final commit
-
-**7b.6.** Run `/prizmkit-retrospective` (feature sessions only, **before commit**):
-- Extract lessons from completed feature — compare spec/plan/tasks vs actual
-- Update relevant `.prizm-docs/` sections: TRAPS, RULES, DECISIONS
-- Write `.prizmkit/specs/{{FEATURE_SLUG}}/retrospective.md`
-- Stage any `.prizm-docs/` changes: `git add .prizm-docs/`
-- **Skip if this session is bug-fix-only**
+**7b.** Run `/prizmkit-retrospective` (**before commit**, the sole maintainer of `.prizm-docs/`):
+- **Structural sync**: update KEY_FILES/INTERFACES/DEPENDENCIES/file counts for changed modules
+- **Knowledge injection** (feature sessions only): extract TRAPS, RULES, DECISIONS from completed work
+- Stage all doc changes: `git add .prizm-docs/`
+- **For bug-fix sessions**: structural sync only, skip knowledge injection unless a genuinely new pitfall was discovered
 
 **7c.** Run `/prizmkit-committer` → `feat({{FEATURE_ID}}): {{FEATURE_TITLE}}`, do NOT push
 
@@ -354,8 +338,8 @@ Write to: `{{SESSION_STATUS_PATH}}`
   "feature_slug": "{{FEATURE_SLUG}}",
   "exec_tier": 3,
   "status": "<success|partial|failed|commit_missing|docs_missing>",
-  "completed_phases": [0, 1, 2, 3, 4, 5, 6, 7],
-  "current_phase": 7,
+  "completed_phases": [0, 1, 2, 3, 4, 5, 6],
+  "current_phase": 6,
   "checkpoint_reached": "CP-3",
   "tasks_completed": 0,
   "tasks_total": 0,
@@ -367,8 +351,7 @@ Write to: `{{SESSION_STATUS_PATH}}`
   "artifacts": {
     "context_snapshot_path": ".prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md",
     "spec_path": ".prizmkit/specs/{{FEATURE_SLUG}}/spec.md",
-    "plan_path": ".prizmkit/specs/{{FEATURE_SLUG}}/plan.md",
-    "tasks_path": ".prizmkit/specs/{{FEATURE_SLUG}}/tasks.md"
+    "plan_path": ".prizmkit/specs/{{FEATURE_SLUG}}/plan.md"
   },
   "git_commit": "<commit hash>",
   "timestamp": "2026-03-04T10:00:00Z"
@@ -383,19 +366,15 @@ After writing `session-status.json`, verify repository is clean:
 git status --short
 ```
 
-If any files remain, include them in the last commit:
+If any files remain (e.g. session-status.json), stage and create a follow-up commit:
 
 ```bash
 git add -A
-git commit --amend --no-edit
+git commit -m "chore({{FEATURE_ID}}): include session artifacts"
 ```
 
 Re-check `git status --short` and ensure it is empty before exiting.
 
-## Step 4: Team Cleanup
-
-No team cleanup needed — agents were spawned directly without TeamCreate.
-
 ## Critical Paths
 
 | Resource | Path |
@@ -411,7 +390,7 @@ No team cleanup needed — agents were spawned directly without TeamCreate.
 
 ## Reminders
 
-- Tier 3: full team — Dev (implementation) → Reviewer (review) — agents spawned directly via Task tool (no TeamCreate needed)
+- Tier 3: full team — Dev (implementation) → Reviewer (review) — spawn agents directly via Agent tool
 - context-snapshot.md is the team knowledge base: orchestrator writes it once, all agents read it
 - Do NOT use `run_in_background=true` when spawning agents
 - ALWAYS write session-status.json before exiting

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

@@ -18,18 +18,17 @@ You are the **bug fix session orchestrator**. Fix Bug {{BUG_ID}}: "{{BUG_TITLE}}
 
 **CRITICAL SESSION LIFECYCLE RULE**: You MUST NOT exit until ALL work is complete and session-status.json is written. When you spawn subagents, you MUST **wait for each to finish** (run_in_background=false) before proceeding. Do NOT spawn an agent in the background and exit — that kills the session.
 
-**MANDATORY TEAM REQUIREMENT**: You MUST use the `prizm-dev-team` multi-agent team. This is NON-NEGOTIABLE. All implementation and review work MUST be performed by the appropriate team agents (Dev, Reviewer). You are the orchestrator — handle coordination, planning, and commit phases directly.
+**MANDATORY TEAM REQUIREMENT**: You MUST use the `prizm-dev-team` agents (Dev + Reviewer). This is NON-NEGOTIABLE. All implementation and review work MUST be performed by the appropriate team agents (Dev, Reviewer). You are the orchestrator — handle coordination, planning, and commit phases directly.
 
 **BUG FIX DOCUMENTATION POLICY**: Bug fixes MUST NOT be recorded as new documentation entries:
-- Do NOT run `/prizmkit-summarize` (no REGISTRY.md entries)
+- Run `/prizmkit-retrospective` with structural sync only (Job 1) — skip knowledge injection unless a genuinely new TRAP was discovered
 - Do NOT create spec/plan/tasks under `.prizmkit/specs/`
 - Do NOT update `.prizm-docs/` module docs for pure bug fixes (unless TRAPS update is needed)
 - Commit with `fix(<scope>):` prefix, NOT `feat:`
 
 ### Team Definition Reference
 
-- **Source of truth**: `core/team/prizm-dev-team.json`
-- **Installed team config**: `{{TEAM_CONFIG_PATH}}`
+- **Team config**: `{{TEAM_CONFIG_PATH}}`
 
 ### Bug Description
 
@@ -74,16 +73,11 @@ You are the **bug fix session orchestrator**. Fix Bug {{BUG_ID}}: "{{BUG_TITLE}}
 
 ### Step 1: Initialize
 
-#### Team Setup: Reuse or Create
+#### Agent Setup
 
-1. **Check if a team already exists and can be reused**:
-   - Read the team config file at `{{TEAM_CONFIG_PATH}}`
-   - If valid, reuse it. Set `TEAM_REUSED=true`
-
-2. **If no reusable team**, create a new one:
-   - Reference `core/team/prizm-dev-team.json`
-   - Call `TeamCreate` with `team_name="prizm-dev-team-{{BUG_ID}}"` and `description="Fixing {{BUG_TITLE}}"`
-   - Set `TEAM_REUSED=false`
+Reference `{{TEAM_CONFIG_PATH}}` for agent definitions:
+- Dev: `{{DEV_SUBAGENT_PATH}}`
+- Reviewer: `{{REVIEWER_SUBAGENT_PATH}}`
 
 3. Create bug fix artifacts directory:
    ```bash
@@ -96,7 +90,7 @@ You are the **bug fix session orchestrator**. Fix Bug {{BUG_ID}}: "{{BUG_TITLE}}
 
 **Goal**: Classify the bug, identify scope and severity, check known issues, produce fix-plan.md.
 
-- Spawn Dev agent (Task tool, subagent_type="prizm-dev-team-dev", run_in_background=false)
+- Spawn Dev agent (Agent tool, subagent_type="prizm-dev-team-dev", run_in_background=false)
   Prompt: "Read {{DEV_SUBAGENT_PATH}}. For bug {{BUG_ID}} ('{{BUG_TITLE}}'):
   1. Run `/prizmkit-tool-error-triage` with the bug description and error source
   2. Check `.prizm-docs/` TRAPS sections for matching known issues
@@ -133,7 +127,7 @@ You are the **bug fix session orchestrator**. Fix Bug {{BUG_ID}}: "{{BUG_TITLE}}
 
 **Goal**: Create an automated reproduction that proves the bug exists.
 
-- Spawn Dev agent (Task tool, subagent_type="prizm-dev-team-dev", run_in_background=false)
+- Spawn Dev agent (Agent tool, subagent_type="prizm-dev-team-dev", run_in_background=false)
   Prompt: "Read {{DEV_SUBAGENT_PATH}}. For bug {{BUG_ID}}:
   1. Read the fix plan from `.prizmkit/bugfix/{{BUG_ID}}/fix-plan.md`
   2. Run `/prizmkit-tool-bug-reproducer` with the bug description and triage results
@@ -155,7 +149,7 @@ You are the **bug fix session orchestrator**. Fix Bug {{BUG_ID}}: "{{BUG_TITLE}}
 
 **Goal**: Implement the fix. The reproduction test goes from red to green.
 
-- Spawn Dev agent (Task tool, subagent_type="prizm-dev-team-dev", run_in_background=false)
+- Spawn Dev agent (Agent tool, subagent_type="prizm-dev-team-dev", run_in_background=false)
   Prompt: "Read {{DEV_SUBAGENT_PATH}}. For bug {{BUG_ID}}:
   1. Read the fix plan from `.prizmkit/bugfix/{{BUG_ID}}/fix-plan.md`
   2. Read `.prizm-docs/` for affected modules (TRAPS, RULES, PATTERNS)
@@ -177,7 +171,7 @@ You are the **bug fix session orchestrator**. Fix Bug {{BUG_ID}}: "{{BUG_TITLE}}
 
 **Goal**: Ensure fix correctness and no regressions.
 
-- Spawn Reviewer agent (Task tool, subagent_type="prizm-dev-team-reviewer", run_in_background=false)
+- Spawn Reviewer agent (Agent tool, subagent_type="prizm-dev-team-reviewer", run_in_background=false)
   Prompt: "Read {{REVIEWER_SUBAGENT_PATH}}. For bug {{BUG_ID}}:
   1. Run `/prizmkit-code-review` scoped to CHANGED FILES ONLY
   2. Review dimensions (adjusted for bug fix):
@@ -206,17 +200,19 @@ You are the **bug fix session orchestrator**. Fix Bug {{BUG_ID}}: "{{BUG_TITLE}}
 
 **Goal**: Commit the fix, update TRAPS, generate fix-report.md.
 
-- Spawn Dev agent (Task tool, subagent_type="prizm-dev-team-dev", run_in_background=false)
-  Prompt: "Read {{DEV_SUBAGENT_PATH}}. For bug {{BUG_ID}}:
-  1. Run `/prizmkit-committer` with:
-     - Commit message: `fix({{FIX_SCOPE}}): {{BUG_TITLE}}`
-     - Include both fix code and reproduction test
-     - Do NOT run `/prizmkit-summarize`
-     - Do NOT push (user will push manually)
-  2. If a new pitfall was discovered (not previously in TRAPS):
-     - Update the affected module's TRAPS section in `.prizm-docs/`
-     - Format: `- TRAP: <description> | FIX: <solution> | DATE: YYYY-MM-DD`
-  3. Write the complete fix report to `.prizmkit/bugfix/{{BUG_ID}}/fix-report.md`
+**This phase is executed by YOU (the orchestrator), NOT a subagent.**
+
+1. If a new pitfall was discovered (not previously in TRAPS):
+   - Update the affected module's TRAPS section in `.prizm-docs/`
+   - Format: `- TRAP: <description> | FIX: <solution> | DATE: YYYY-MM-DD`
+
+2. Run `/prizmkit-committer` with:
+   - Commit message: `fix({{FIX_SCOPE}}): {{BUG_TITLE}}`
+   - Include both fix code and reproduction test
+   - Do NOT run `/prizmkit-retrospective` with REGISTRY archiving
+   - Do NOT push (user will push manually)
+
+3. Write the complete fix report to `.prizmkit/bugfix/{{BUG_ID}}/fix-report.md`
 
   The fix-report.md MUST contain these sections:
   - Bug Resolution Summary (ID, title, status, phases completed, duration)
@@ -224,8 +220,7 @@ You are the **bug fix session orchestrator**. Fix Bug {{BUG_ID}}: "{{BUG_TITLE}}
   - Verification Results (reproduction test before/after, regression tests, review verdict)
   - Knowledge Captured (TRAPS updated, prevention recommendation)
   - Acceptance Criteria Verification (checklist with pass/fail for each criterion)
-  "
-- **Wait for Dev to return**
+
 - **CP-BF-5**: Commit recorded, fix-report.md written, TRAPS updated (if applicable)
 
 ### Step 3: Report Session Status
@@ -258,17 +253,11 @@ Write to: `{{SESSION_STATUS_PATH}}`
 
 **Status values**: `success` (all phases done) | `partial` (can resume) | `failed` (unrecoverable)
 
-### Step 4: Team Cleanup (conditional)
-
-**Only if you CREATED the team** (`TEAM_REUSED=false`), clean up with `TeamDelete`.
-**If you REUSED an existing team** (`TEAM_REUSED=true`), do NOT call `TeamDelete`.
-
 ## Critical Paths
 
 | Resource | Path |
 |----------|------|
-| Team Definition (source of truth) | `core/team/prizm-dev-team.json` |
-| Team Config (installed) | `{{TEAM_CONFIG_PATH}}` |
+| Team Definition (source of truth) | `{{TEAM_CONFIG_PATH}}` |
 | Bug Fix Artifacts Dir | `.prizmkit/bugfix/{{BUG_ID}}/` |
 | Fix Plan | `.prizmkit/bugfix/{{BUG_ID}}/fix-plan.md` |
 | Fix Report | `.prizmkit/bugfix/{{BUG_ID}}/fix-report.md` |
@@ -279,13 +268,12 @@ Write to: `{{SESSION_STATUS_PATH}}`
 
 ## Reminders
 
-- **MANDATORY**: Use `prizm-dev-team` — single-agent execution is FORBIDDEN
+- **MANDATORY**: Use `prizm-dev-team` agents — single-agent execution is FORBIDDEN
 - **Only 2 artifact files per bug**: fix-plan.md + fix-report.md — NEVER more
-- **Do NOT create** spec.md, plan.md, or tasks.md for bug fixes
-- **Do NOT run** `/prizmkit-summarize` (no REGISTRY.md entries for bugs)
+- **Do NOT create** spec.md or plan.md for bug fixes
+- **Do NOT run** `/prizmkit-retrospective` knowledge injection for bugs (structural sync only, unless genuinely new TRAP discovered)
 - **Commit with** `fix(<scope>):` prefix, NOT `feat:`
 - **Update TRAPS** in `.prizm-docs/` only if a genuinely new pitfall was discovered
 - Dev agents use TDD approach: reproduction test goes from RED → GREEN
 - ALWAYS write session-status.json before exiting
 - Do NOT use `run_in_background=true` when spawning agents
-- Only call `TeamDelete` if you created the team

package/bundled/dev-pipeline/templates/session-status-schema.json

@@ -72,7 +72,7 @@
       "properties": {
         "spec_path": { "type": "string" },
         "plan_path": { "type": "string" },
-        "tasks_path": { "type": "string" }
+        "context_snapshot_path": { "type": "string" }
       }
     },
     "timestamp": {

package/bundled/dev-pipeline/tests/conftest.py

@@ -1,133 +1,26 @@
-"""Shared fixtures for dev-pipeline tests."""
+"""Shared fixtures and import helpers for dev-pipeline tests."""
 
-import json
+import importlib
 import os
-import pytest
+import sys
 
+# Add dev-pipeline/scripts to the import path so tests can import modules
+# without requiring package installation.
+_scripts_dir = os.path.join(os.path.dirname(__file__), "..", "scripts")
+sys.path.insert(0, _scripts_dir)
 
-@pytest.fixture
-def sample_feature_list():
-    """A valid feature-list.json structure."""
-    return {
-        "$schema": "dev-pipeline-feature-list-v1",
-        "app_name": "TestApp",
-        "global_context": {
-            "language": "Python",
-            "framework": "FastAPI",
-        },
-        "features": [
-            {
-                "id": "F-001",
-                "title": "Project Infrastructure Setup",
-                "description": "Set up the project structure.",
-                "priority": 1,
-                "estimated_complexity": "low",
-                "dependencies": [],
-                "acceptance_criteria": ["Has package.json", "Has README.md"],
-                "status": "pending",
-            },
-            {
-                "id": "F-002",
-                "title": "User Authentication",
-                "description": "Implement user login and registration.",
-                "priority": 2,
-                "estimated_complexity": "high",
-                "dependencies": ["F-001"],
-                "acceptance_criteria": ["Login works", "Registration works"],
-                "status": "pending",
-            },
-            {
-                "id": "F-003",
-                "title": "Dashboard View",
-                "description": "Create main dashboard.",
-                "priority": 3,
-                "estimated_complexity": "medium",
-                "dependencies": ["F-001", "F-002"],
-                "acceptance_criteria": ["Dashboard renders"],
-                "status": "pending",
-            },
-        ],
-    }
 
+def _load_hyphenated_module(module_name, filename):
+    """Load a hyphenated .py file and register it as an importable module."""
+    spec = importlib.util.spec_from_file_location(
+        module_name,
+        os.path.join(_scripts_dir, filename),
+    )
+    mod = importlib.util.module_from_spec(spec)
+    sys.modules[module_name] = mod
+    spec.loader.exec_module(mod)
 
-@pytest.fixture
-def sample_bug_list():
-    """A valid bug-fix-list.json structure."""
-    return {
-        "$schema": "dev-pipeline-bug-fix-list-v1",
-        "project_name": "TestProject",
-        "global_context": {
-            "language": "Python",
-        },
-        "bugs": [
-            {
-                "id": "B-001",
-                "title": "Login crash on empty password",
-                "description": "App crashes when password is empty.",
-                "severity": "critical",
-                "priority": 1,
-                "error_source": {
-                    "type": "stack_trace",
-                    "stack_trace": "Traceback ... ValueError",
-                    "error_message": "Password cannot be empty",
-                },
-                "verification_type": "automated",
-                "acceptance_criteria": ["No crash on empty password"],
-                "status": "pending",
-                "affected_feature": "F-002",
-                "affected_modules": ["auth"],
-            },
-            {
-                "id": "B-002",
-                "title": "Slow dashboard loading",
-                "description": "Dashboard takes 10s to load.",
-                "severity": "medium",
-                "priority": 2,
-                "error_source": {
-                    "type": "user_report",
-                    "reproduction_steps": ["Open dashboard", "Wait 10 seconds"],
-                },
-                "verification_type": "manual",
-                "acceptance_criteria": ["Dashboard loads in <2s"],
-                "status": "pending",
-                "affected_feature": "F-003",
-                "environment": {"os": "macOS", "browser": "Chrome"},
-            },
-        ],
-    }
 
-
-@pytest.fixture
-def feature_list_file(tmp_path, sample_feature_list):
-    """Write sample feature list to a temp file and return the path."""
-    path = tmp_path / "feature-list.json"
-    path.write_text(json.dumps(sample_feature_list, indent=2), encoding="utf-8")
-    return str(path)
-
-
-@pytest.fixture
-def bug_list_file(tmp_path, sample_bug_list):
-    """Write sample bug list to a temp file and return the path."""
-    path = tmp_path / "bug-fix-list.json"
-    path.write_text(json.dumps(sample_bug_list, indent=2), encoding="utf-8")
-    return str(path)
-
-
-@pytest.fixture
-def state_dir(tmp_path):
-    """Create and return a basic state directory."""
-    sd = tmp_path / "state"
-    sd.mkdir()
-    features_dir = sd / "features"
-    features_dir.mkdir()
-    return str(sd)
-
-
-@pytest.fixture
-def bugfix_state_dir(tmp_path):
-    """Create and return a basic bugfix state directory."""
-    sd = tmp_path / "bugfix-state"
-    sd.mkdir()
-    bugs_dir = sd / "bugs"
-    bugs_dir.mkdir()
-    return str(sd)
+# Register hyphenated script files so tests can import them with underscores.
+_load_hyphenated_module("generate_bootstrap_prompt", "generate-bootstrap-prompt.py")
+_load_hyphenated_module("generate_bugfix_prompt", "generate-bugfix-prompt.py")