prizmkit 1.1.100 → 1.1.102

package/bundled/dev-pipeline-windows/templates/bug-fix-list-schema.json

@@ -1,263 +0,0 @@
-{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "title": "Dev-Pipeline Bug Fix List",
-  "description": "Schema for .prizmkit/plans/bug-fix-list.json — standardized input for the Bug Fix Pipeline",
-  "type": "object",
-  "required": [
-    "$schema",
-    "project_name",
-    "bugs"
-  ],
-  "properties": {
-    "$schema": {
-      "type": "string",
-      "const": "dev-pipeline-bug-fix-list-v1"
-    },
-    "project_name": {
-      "type": "string",
-      "minLength": 1
-    },
-    "project_description": {
-      "type": "string"
-    },
-    "created_at": {
-      "type": "string",
-      "format": "date-time"
-    },
-    "created_by": {
-      "type": "string"
-    },
-    "bugs": {
-      "type": "array",
-      "minItems": 1,
-      "items": {
-        "type": "object",
-        "required": [
-          "id",
-          "title",
-          "description",
-          "severity",
-          "error_source",
-          "verification_type",
-          "acceptance_criteria",
-          "status"
-        ],
-        "properties": {
-          "id": {
-            "type": "string",
-            "pattern": "^B-\\d{3}$",
-            "description": "Bug ID, format B-001, B-002..."
-          },
-          "title": {
-            "type": "string",
-            "minLength": 1,
-            "description": "Bug title — brief description of the symptom"
-          },
-          "description": {
-            "type": "string",
-            "minLength": 1,
-            "description": "Detailed bug description: expected vs actual behavior"
-          },
-          "severity": {
-            "type": "string",
-            "enum": [
-              "critical",
-              "high",
-              "medium",
-              "low"
-            ],
-            "description": "critical=crash/data-loss; high=core-feature-broken; medium=workaround-exists; low=cosmetic"
-          },
-          "priority": {
-            "type": "string",
-            "enum": [
-              "high",
-              "medium",
-              "low"
-            ],
-            "description": "Fix priority. Pipeline processes high before medium before low; within same level, array order determines sequence. Both critical and high severity map to high priority."
-          },
-          "error_source": {
-            "type": "object",
-            "required": [
-              "type"
-            ],
-            "description": "Structured error source information extracted from various input formats",
-            "properties": {
-              "type": {
-                "type": "string",
-                "enum": [
-                  "stack_trace",
-                  "user_report",
-                  "failed_test",
-                  "log_pattern",
-                  "monitoring_alert"
-                ]
-              },
-              "stack_trace": {
-                "type": "string",
-                "description": "Error stack trace (when type=stack_trace)"
-              },
-              "error_message": {
-                "type": "string",
-                "description": "Error message text"
-              },
-              "log_snippet": {
-                "type": "string",
-                "description": "Relevant log snippet (when type=log_pattern)"
-              },
-              "failed_test_path": {
-                "type": "string",
-                "description": "Path to failing test file (when type=failed_test)"
-              },
-              "reproduction_steps": {
-                "type": "array",
-                "items": {
-                  "type": "string"
-                },
-                "description": "User-reported reproduction steps (when type=user_report)"
-              }
-            }
-          },
-          "affected_modules": {
-            "type": "array",
-            "items": {
-              "type": "string"
-            },
-            "description": "Known affected module names (optional, triage will auto-detect)"
-          },
-          "environment": {
-            "type": "object",
-            "description": "Environment where the bug occurs",
-            "properties": {
-              "os": {
-                "type": "string"
-              },
-              "runtime": {
-                "type": "string"
-              },
-              "browser": {
-                "type": "string"
-              },
-              "version": {
-                "type": "string"
-              }
-            }
-          },
-          "verification_type": {
-            "type": "string",
-            "enum": [
-              "automated",
-              "manual",
-              "hybrid"
-            ],
-            "description": "automated=unit/integration-test; manual=human-UAT; hybrid=both"
-          },
-          "acceptance_criteria": {
-            "type": "array",
-            "minItems": 1,
-            "items": {
-              "type": "string"
-            },
-            "description": "Conditions that must be met for the bug to be considered fixed"
-          },
-          "status": {
-            "type": "string",
-            "enum": [
-              "pending",
-              "in_progress",
-              "completed",
-              "failed",
-              "skipped",
-              "needs_info"
-            ],
-            "description": "Bug fix status. Subset of feature status enum plus needs_info."
-          },
-          "critic": {
-            "type": "boolean",
-            "description": "Enable adversarial plan challenge before implementation. Default: true for high severity bugs, false for others.",
-            "default": false
-          },
-          "critic_count": {
-            "type": "integer",
-            "description": "Number of parallel critic agents. 1 = single critic, 3 = multi-critic voting. Default: 1 for high severity, omit for others.",
-            "enum": [
-              1,
-              3
-            ]
-          },
-          "user_context": {
-            "type": "array",
-            "items": { "type": "string" },
-            "description": "User-provided supplementary materials, preserved verbatim. Each entry is either inline content/rules (stored as-is) or a file reference (e.g. 'src/auth/login.ts:42-78', 'src/utils/ — focus on validation logic')."
-          },
-          "model": {
-            "type": "string",
-            "description": "AI model ID for this bug fix. Overrides $MODEL env var."
-          },
-          "browser_interaction": {
-            "type": "object",
-            "description": "Browser verification config for bugs reproducible via UI. Supports playwright-cli and opencli. AI auto-detects dev server command, URL, and port from project config at runtime.",
-            "properties": {
-              "tool": {
-                "type": "string",
-                "enum": ["playwright-cli", "opencli", "auto"],
-                "default": "auto",
-                "description": "Browser tool to use. 'auto' (default) = AI chooses at runtime. 'playwright-cli' = local dev server verification in isolated browser. 'opencli' = reuses Chrome logged-in session, ideal for verifying bugs related to third-party integrations or OAuth flows."
-              },
-              "verify_steps": {
-                "type": "array",
-                "description": "Verification goals describing HOW to reproduce and verify the bug fix (e.g., 'Click login button and verify error message is gone', 'Open dashboard and confirm performance metrics display'). AI decides concrete browser tool actions at runtime. If omitted, AI auto-reproduces from error description.",
-                "items": {
-                  "type": "string"
-                }
-              }
-            }
-          }
-        }
-      }
-    },
-    "global_context": {
-      "type": "object",
-      "description": "Global context for all bug fixes in this batch",
-      "properties": {
-        "tech_stack": {
-          "type": "string"
-        },
-        "language": {
-          "type": "string"
-        },
-        "runtime": {
-          "type": "string"
-        },
-        "frontend_framework": {
-          "type": "string"
-        },
-        "frontend_styling": {
-          "type": "string"
-        },
-        "backend_framework": {
-          "type": "string"
-        },
-        "database": {
-          "type": "string"
-        },
-        "orm": {
-          "type": "string"
-        },
-        "testing_strategy": {
-          "type": "string"
-        },
-        "bundler": {
-          "type": "string"
-        },
-        "project_type": {
-          "type": "string"
-        },
-        "ci_pipeline": {
-          "type": "string"
-        }
-      }
-    }
-  }
-}

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

@@ -1,326 +0,0 @@
-# Dev-Pipeline Bug Fix Session Bootstrap
-
-## Session Context
-
-- **Bug ID**: {{BUG_ID}}
-- **Bug Title**: {{BUG_TITLE}}
-- **Severity**: {{SEVERITY}}
-- **Verification Type**: {{VERIFICATION_TYPE}}
-
-## Your Mission
-
-You are the **bug fix session agent**. Fix Bug {{BUG_ID}}: "{{BUG_TITLE}}".
-
-**CRITICAL**: You MUST NOT exit until ALL work is complete and committed.
-
-**SUBAGENT LIFECYCLE**: Any normal work subagent must be awaited with `run_in_background=false`. Do not spawn persistent background subagents for headless recovery.
-
-**NON-INTERACTIVE MODE**: There is NO human on the other end. NEVER ask for user confirmation, NEVER wait for user input. Make decisions autonomously and move forward.
-
-### Bug Description
-
-{{BUG_DESCRIPTION}}
-
-{{USER_CONTEXT}}
-
-### Error Source
-
-- **Type**: {{ERROR_SOURCE_TYPE}}
-{{ERROR_SOURCE_DETAILS}}
-
-### Acceptance Criteria
-
-{{ACCEPTANCE_CRITERIA}}
-
-### Environment
-
-{{ENVIRONMENT}}
-
-### App Global Context
-
-{{GLOBAL_CONTEXT}}
-
-### Project Conventions
-
-> Read {{PLATFORM_CONVENTIONS}} for project-level coding standards, architecture decisions, and development rules.
-
-## ⚠️ Context Budget Rules (CRITICAL)
-
-0. **NON-INTERACTIVE MODE** — NEVER ask for confirmation. Proceed autonomously.
-1. **context-snapshot.md is your single source of truth** — After it is built, read context-snapshot.md instead of re-reading individual source files.
-2. **Never re-read your own writes** — Trust your write was correct.
-3. **Stay focused** — Do NOT explore code unrelated to this bug.
-4. **Minimize tool output** — Capture to temp file, scan first/last lines, filter with Select-String, regex matching, or PowerShell object filtering. Never load full output.
-5. **No intermediate commits** — All changes committed once at the end via `/prizmkit-committer`.
-
-{{LOG_SIZE_AWARENESS}}
-## Bug Fix Artifacts Directory
-
-```
-.prizmkit/bugfix/{{BUG_ID}}/
-├── spec.md              ← /prizmkit-plan output (root cause, scope, behavior preservation)
-├── plan.md              ← /prizmkit-plan output (fix tasks, first task = reproduction test)
-├── context-snapshot.md  ← Project context for this bug
-└── fix-report.md        ← Final bug resolution report
-```
-
-## Workflow Checkpoint System
-
-**Path**: `{{CHECKPOINT_PATH}}`
-
-**Rules**:
-1. **Before each step**: Read `workflow-checkpoint.json`, verify the previous step is `"completed"`. If not, complete it first.
-2. **Starting a step**: Update to `status: "in_progress"`.
-3. **After step completes**: Update to `status: "completed"`.
-4. **On failure**: Set to `status: "failed"` and continue if possible.
-5. **On resume**: Skip `"completed"` steps. Start from first `"pending"` or `"in_progress"` step.
-
----
-
-## Execution
-
-### Phase 0: Initialize
-
-```powershell
-New-Item -ItemType Directory -Force -Path .prizmkit/bugfix/{{BUG_ID}} | Out-Null
-```
-
-{{IF_BROWSER_INTERACTION}}
-
-#### Browser Verification Protocol
-
-The bug may be reproducible via the UI. Use this single browser protocol for planning, implementation, review, and final reporting:
-
-{{IF_BROWSER_TOOL_AUTO}}
-- **Browser Tool**: Auto-select at runtime based on error type and dev server configuration
-{{END_IF_BROWSER_TOOL_AUTO}}
-
-{{IF_BROWSER_TOOL_PLAYWRIGHT}}
-- **Browser Tool**: playwright-cli (local isolated browser against dev server)
-{{END_IF_BROWSER_TOOL_PLAYWRIGHT}}
-
-{{IF_BROWSER_TOOL_OPENCLI}}
-- **Browser Tool**: opencli (Chrome session with existing login context — ideal for OAuth/third-party integrations)
-{{END_IF_BROWSER_TOOL_OPENCLI}}
-
-**Browser Verification Goals**:
-{{BROWSER_VERIFY_STEPS}}
-
-Use this protocol only when the bug is UI/frontend-reproducible. Evidence must cover: original bug reproduction, post-fix behavior, related UI regression smoke tests, tool used, and any manual verification steps.
-
-{{END_IF_BROWSER_INTERACTION}}
-
-### Phase 1: Diagnose & Plan
-
-**Goal**: Identify root cause, build project context, produce spec.md + plan.md.
-
-**Step 1 — Diagnose the bug**:
-
-1. Read `.prizmkit/prizm-docs/root.prizm` and relevant L1/L2 docs for affected modules
-2. Trace the bug:
-   - Classify error type (Runtime / Network / Auth / Data / Logic / Config / External)
-   - Check `.prizmkit/prizm-docs/` TRAPS sections for matching known issues
-   - Trace call chain from error source to root cause
-   - Identify all affected files and modules
-3. Read the affected source files and related test files
-
-**Step 2 — Build context snapshot** (skip if already exists):
-
-Write `.prizmkit/bugfix/{{BUG_ID}}/context-snapshot.md`:
-- **Section 1 — Bug Brief**: bug description + acceptance criteria + root cause analysis
-- **Section 2 — Affected Files**: full verbatim content of each affected source file
-- **Section 3 — Existing Tests**: full content of related test files
-- **Section 4 — Prizm Context**: relevant TRAPS, RULES from .prizmkit/prizm-docs/
-
-**Step 3 — Plan the fix**:
-
-Run `/prizmkit-plan` with `artifact_dir=.prizmkit/bugfix/{{BUG_ID}}/`:
-- The spec.md should capture: root cause, impact scope, behavior that must be preserved
-- The plan.md Tasks section **MUST start with a reproduction test task** — a test that FAILS with current code (RED state), proving the bug exists
-- Subsequent tasks implement the minimal fix to make the test pass (GREEN state)
-- Resolve any `[NEEDS CLARIFICATION]` markers autonomously — do NOT pause
-
-{{IF_BROWSER_INTERACTION}}
-- **Browser Verification**: If the bug is UI-reproducible, plan.md should reference the Browser Verification Protocol above instead of redefining browser steps.
-{{END_IF_BROWSER_INTERACTION}}
-
-**DECISION GATE — Fast Path Check**:
-- If plan.md has ≤ 2 tasks AND root cause is obvious → mark `FAST_PATH=true`, skip Phase 3 (Review) later
-
-**CP-1**: spec.md and plan.md exist with Tasks section.
-
-**Checkpoint update**: Set step `bug-diagnosis-and-plan` to `"completed"`.
-
-{{IF_VERIFICATION_MANUAL_OR_HYBRID}}
-**NOTE**: verification_type is '{{VERIFICATION_TYPE}}'. The plan.md MUST also include:
-- Manual Verification Plan section with UAT checklist
-- User Review Required section specifying reviewer and blocking behavior
-{{END_IF_VERIFICATION_MANUAL_OR_HYBRID}}
-
----
-
-### Phase 2: Implement & Fix
-
-**Goal**: Execute the fix plan. Reproduction test goes from RED → GREEN.
-
-Run `/prizmkit-implement` with `artifact_dir=.prizmkit/bugfix/{{BUG_ID}}/`:
-- Executes plan.md tasks in order (TDD: first task creates failing test, subsequent tasks fix the code)
-- Marks each task `[x]` on completion
-- Runs test suite after each task
-- Uses convergence-based test failure recovery (keep fixing while progress is being made)
-
-{{IF_BROWSER_INTERACTION}}
-
-**Browser Verification During Implementation**: If the bug is UI-reproducible, apply the Browser Verification Protocol above and document evidence in the implementation notes.
-
-{{END_IF_BROWSER_INTERACTION}}
-
-After implement completes, verify:
-1. All tasks in plan.md are `[x]`
-2. Reproduction test passes (GREEN)
-3. Full test suite passes (no regression)
-4. Each acceptance criterion is met
-
-**CP-2**: All tasks complete, reproduction test passes, no regression.
-
-**Checkpoint update**: Set step `prizmkit-implement` to `"completed"`.
-
----
-
-### Phase 3: Review
-
-If `FAST_PATH=true` (≤ 2 tasks, obvious root cause), skip this phase entirely.
-
-Run `/prizmkit-code-review` with `artifact_dir=.prizmkit/bugfix/{{BUG_ID}}/`:
-- The skill runs an internal review-fix loop (Reviewer → filter → Dev fix, max 3 rounds) and writes `review-report.md`
-- `review-report.md` must contain `## Verdict`
-
-**Gate Check — Review Report**:
-After `/prizmkit-code-review` returns, verify the review report:
-```powershell
-if (Select-String -Path .prizmkit/bugfix/{{BUG_ID}}/review-report.md -Pattern "## Verdict" -Quiet -ErrorAction SilentlyContinue) { "GATE:PASS" } else { "GATE:MISSING" }
-```
-If GATE:MISSING:
-- Do not re-run `/prizmkit-code-review` in an unbounded report-repair loop.
-- Perform one bounded status check; retry `/prizmkit-code-review` at most once only if the missing report appears caused by a transient team/config/lock error.
-- If the report is still missing after that single check/retry, write `failure-log.md` with the spawn/skill error and last observable state, then either perform a safe inline fallback review (spec/plan/diff/tests → write `review-report.md` with `## Verdict`) or stop with a clear recovery failure.
-
-Read `review-report.md` and check the Verdict:
-- `PASS` → proceed
-- `NEEDS_FIXES` → the skill exhausted its max rounds; log remaining findings and proceed
-
-{{IF_BROWSER_INTERACTION}}
-
-**Code Review — Browser Verification Check**: Confirm that UI-reproducible bug evidence follows the Browser Verification Protocol above.
-
-{{END_IF_BROWSER_INTERACTION}}
-
-**CP-3**: Code review complete, `review-report.md` written, and all tests green.
-
-**Checkpoint update**: Set step `prizmkit-code-review` to `"completed"`.
-
-{{IF_VERIFICATION_MANUAL_OR_HYBRID}}
-**MANUAL VERIFICATION GATE**:
-- After automated review passes, write session-status.json with status="partial", resume_from_phase=4
-- Set bug status to `verifying` and STOP — manual UAT required before commit
-{{END_IF_VERIFICATION_MANUAL_OR_HYBRID}}
-
----
-
-### Phase 4: Commit & Learn
-
-**Bug Fix Documentation Policy**:
-- **DEFAULT**: Run `/prizmkit-retrospective` with structural sync only (Job 1). Skip knowledge injection.
-- **Full retrospective** (Job 1 + Job 2): Only when the fix causes interface signature changes, dependency additions/removals, observable behavior changes, or reveals new TRAPs.
-
-**a.** If a new pitfall was discovered (not previously in TRAPS):
-   - Update the affected module's TRAPS section in `.prizmkit/prizm-docs/`
-   - Format: `- TRAP: <description> | FIX: <solution> | DATE: YYYY-MM-DD`
-
-**b.** Run `/prizmkit-retrospective` following the policy above.
-   Stage doc changes: `git add .prizmkit/prizm-docs/`
-
-**c.** Stage all changed files explicitly (NEVER use `git add -A` or `git add .`):
-```powershell
-git add <specific-files-modified>
-git add .prizmkit/prizm-docs/
-```
-
-**d.** Run `/prizmkit-committer --headless`:
-   - Commit message prefix: `fix({{FIX_SCOPE}}): {{BUG_TITLE}}`
-   - Include both fix code and reproduction test
-   - Do NOT push
-
-**e.** Final verification:
-```powershell
-git status --short
-```
-Working tree MUST be clean. If any files remain, amend the commit.
-
-**f.** Write fix report to `.prizmkit/bugfix/{{BUG_ID}}/fix-report.md`:
-
-The fix-report.md MUST contain:
-- **Bug Resolution Summary**: ID, title, status, phases completed
-- **What Was Fixed**: changes made, diff summary, commit hash
-- **Verification Results**: reproduction test before/after, regression tests, review findings
-
-{{IF_BROWSER_INTERACTION}}
-- **Browser Verification Results**: UI flows tested, browser tool used (if any), manual verification steps completed
-{{END_IF_BROWSER_INTERACTION}}
-
-- **Knowledge Captured**: TRAPS updated (if any), prevention recommendation
-- **Acceptance Criteria Verification**: checklist with pass/fail for each criterion
-
-**Checkpoint update**: Set steps `prizmkit-committer` and `bug-report` to `"completed"`.
-
----
-
-### Step 3: Report Session Status
-
-**CRITICAL**: Before exiting, write the session status file.
-
-Write to: `{{SESSION_STATUS_PATH}}`
-
-```json
-{
-  "session_id": "{{SESSION_ID}}",
-  "bug_id": "{{BUG_ID}}",
-  "status": "<success|partial|failed>",
-  "completed_phases": [1, 2, 3, 4],
-  "current_phase": 4,
-  "checkpoint_reached": "CP-4",
-  "fast_path": false,
-  "errors": [],
-  "can_resume": false,
-  "resume_from_phase": null,
-  "artifacts": {
-    "spec_path": ".prizmkit/bugfix/{{BUG_ID}}/spec.md",
-    "plan_path": ".prizmkit/bugfix/{{BUG_ID}}/plan.md",
-    "fix_report_path": ".prizmkit/bugfix/{{BUG_ID}}/fix-report.md"
-  },
-  "git_commit": "<commit hash>",
-  "traps_updated": false,
-  "timestamp": "{{TIMESTAMP}}"
-}
-```
-
-## Critical Paths
-
-| Resource | Path |
-|----------|------|
-| Bug Fix Artifacts Dir | `.prizmkit/bugfix/{{BUG_ID}}/` |
-| Spec | `.prizmkit/bugfix/{{BUG_ID}}/spec.md` |
-| Plan | `.prizmkit/bugfix/{{BUG_ID}}/plan.md` |
-| Fix Report | `.prizmkit/bugfix/{{BUG_ID}}/fix-report.md` |
-| Session Status Output | {{SESSION_STATUS_PATH}} |
-| Project Root | {{PROJECT_ROOT}} |
-
-## Reminders
-
-- Use L1 Skills: `/prizmkit-plan`, `/prizmkit-implement`, `/prizmkit-code-review`, `/prizmkit-committer`, `/prizmkit-retrospective`
-- All skills use `artifact_dir=.prizmkit/bugfix/{{BUG_ID}}/`
-- plan.md first task MUST be reproduction test (RED → GREEN TDD)
-- Commit with `fix(<scope>):` prefix, NOT `feat:`
-- DEFAULT: `/prizmkit-retrospective` structural sync only (Job 1). Full retrospective when fix changes interfaces/dependencies/behavior
-- ALWAYS write session-status.json before exiting
-- Do NOT run `git add`/`git commit` during Phases 1-3 — all committed once in Phase 4