prizmkit 1.1.70 → 1.1.74

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

@@ -148,12 +148,9 @@ If `EXISTING_CODE` is non-empty: your spec/plan/tasks must reflect this existing
    Identify the top-level source directories from the results.
 3. Scan the detected source directories for files related to this feature; read each one
 4. Write `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md`:
-   - **Section 1 — Feature Brief**: feature description + acceptance criteria (copy from above)
-   - **Section 2 — Project Structure**: run the following to get a visual directory tree, then paste output:
-     ```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'
-     ```
-   - **Section 3 — Prizm Context**: full content of root.prizm and relevant L1/L2 docs
+   - **Section 1 — Feature Brief**: feature description (2-3 lines) + acceptance criteria (copy from above)
+   - **Section 2 — Verification Gates**: copy the gate checklist from the Task Contract above
+   - **Section 3 — Key TRAPS & RULES**: extract only relevant TRAPS/RULES from prizm-docs that apply to files in this scope. Do NOT copy full L0/L1/L2 content.
    - **Section 4 — File Manifest**: For each file relevant to this feature, list: file path, why it's needed (modify/reference/test), key interface signatures (function names + params + return types). Do NOT include full file content — agents read files on-demand. Format:
      ### Files to Modify
      | File | Why Needed | Key Interfaces |
@@ -167,7 +164,6 @@ If `EXISTING_CODE` is non-empty: your spec/plan/tasks must reflect this existing
 
      ### Known TRAPS (from .prizmkit/prizm-docs/)
      - <trap entries extracted from L1/L2 docs>
-   - **Section 5 — Existing Tests**: full content of related test files as code blocks
 4. Confirm: `ls .prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md`
 
 **After Step A**: Use context-snapshot.md Section 4 File Manifest to guide targeted file reads. Do NOT scan directories or read unrelated files.
@@ -200,7 +196,7 @@ Spawn failure cap: for team/config/lock errors, retry at most once for this Revi
 
 Prompt:
 > "Read {{REVIEWER_SUBAGENT_PATH}}. For feature {{FEATURE_ID}} (slug: {{FEATURE_SLUG}}):
-> 1. Read `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` FIRST — Section 3 has project context, Section 4 has file manifest.
+> 1. Read `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` FIRST — Section 3 has TRAPS/RULES, Section 4 has file manifest.
 > 2. Cross-check `spec.md` and `plan.md` (including Tasks section) for consistency.
 > 3. Before flagging CRITICAL or HIGH issues, read the relevant source files listed in the File Manifest to verify.
 > Report: CRITICAL, HIGH, MEDIUM issues found (or 'No issues found')."
@@ -230,7 +226,7 @@ Spawn failure cap: for team/config/lock errors, retry at most once for this Crit
 Prompt:
 > "Read {{CRITIC_SUBAGENT_PATH}}. For feature {{FEATURE_ID}} (slug: {{FEATURE_SLUG}}):
 > **MODE: Plan Challenge**
-> 1. Read `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` FIRST — Section 3 has project context, Section 4 has file manifest.
+> 1. Read `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md` FIRST — Section 3 has TRAPS/RULES, Section 4 has file manifest.
 > 2. Read `.prizmkit/prizm-docs/root.prizm` and relevant L1/L2 docs for affected modules.
 > 3. Read existing source files in the modules this plan touches.
 > 4. Challenge plan.md against the project's existing architecture, patterns, and style.

package/bundled/dev-pipeline/templates/sections/feature-context.md

@@ -4,33 +4,18 @@
 Use this material according to the following priority:
 
 1. **Task Contract** — defines current scope and Verification Gates.
-2. **User Raw Context** — authoritative constraints, but not automatic scope expansion.
-3. **Completed Dependencies** — existing behavior and interfaces; do not re-implement them.
-4. **Project Brief** — product background and architecture alignment.
-5. **App Global Context** — stack, runtime, and testing conventions.
-6. **Project Conventions** — repository-specific rules.
-
-### User Raw Context
-
-{{USER_CONTEXT}}
+2. **Completed Dependencies** — existing interfaces; do not re-implement.
+3. **App Global Context** — stack, runtime, testing conventions.
 
 ### Completed Dependencies
 
-> Use this section to understand available interfaces and avoid duplicating completed work.
-
 {{COMPLETED_DEPENDENCIES}}
 
-### Project Brief
-
-> Use this section for alignment only. Do not treat unrelated backlog items as current feature scope.
-
-{{PROJECT_BRIEF}}
-
 ### App Global Context
 
 {{GLOBAL_CONTEXT}}
 
 ### Project Conventions
 
-> Read {{PLATFORM_CONVENTIONS}} for project-level coding standards, architecture decisions, and development rules. Follow these conventions throughout implementation.
+> Read {{PLATFORM_CONVENTIONS}} for project-level coding standards and architecture decisions.
 </feature-context>

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

@@ -69,3 +69,14 @@ python3 $PIPELINE_DIR/scripts/update-checkpoint.py \
   --step prizmkit-committer \
   --status completed
 ```
+
+### TERMINAL STOP — S09 Completed
+
+After all of the following are true, the session is **TERMINAL**:
+
+- `/prizmkit-committer` has completed
+- `git status --short` is clean (except ignored/local-only pipeline artifacts)
+- `.prizmkit/specs/{{FEATURE_SLUG}}/completion-summary.json` is written
+- the S09 / `prizmkit-committer` checkpoint is marked `completed`
+
+At that point, stop immediately. Do **not** process delayed teammate/reviewer findings, do **not** edit files, do **not** amend the commit, and do **not** start any new tool calls. Any findings that arrive after S09 is completed are follow-up work for a later session, not part of this feature commit.

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

@@ -62,3 +62,14 @@ python3 $PIPELINE_DIR/scripts/update-checkpoint.py \
   --step prizmkit-committer \
   --status completed
 ```
+
+### TERMINAL STOP — S09 Completed
+
+After all of the following are true, the session is **TERMINAL**:
+
+- `/prizmkit-committer` has completed
+- `git status --short` is clean (except ignored/local-only pipeline artifacts)
+- `.prizmkit/specs/{{FEATURE_SLUG}}/completion-summary.json` is written
+- the S09 / `prizmkit-committer` checkpoint is marked `completed`
+
+At that point, stop immediately. Do **not** process delayed teammate/reviewer findings, do **not** edit files, do **not** amend the commit, and do **not** start any new tool calls. Any findings that arrive after S09 is completed are follow-up work for a later session, not part of this feature commit.

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

@@ -1,4 +1,4 @@
-   - **Section 3 — Prizm Context**: full content of root.prizm and relevant L1/L2 docs
+   - **Section 3 — Key TRAPS & RULES**: extract only relevant TRAPS/RULES from prizm-docs. Do NOT copy full L0/L1/L2 content — the orchestrator already loaded them.
    - **Section 4 — File Manifest**: For each file relevant to this feature, list: file path, why it's needed (modify/reference/test), key interface signatures (function names + params + return types). Do NOT include full file content — agents read files on-demand. Format:
      ### Files to Modify
      | File | Why Needed | Key Interfaces |

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

@@ -6,15 +6,9 @@ ls .prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md 2>/dev/null && echo "EXI
 
 If MISSING — build it now:
 1. Read `.prizmkit/prizm-docs/root.prizm` and relevant L1/L2 prizm docs
-2. Detect source code directories: read KEY_FILES and STRUCTURE sections from `root.prizm` to identify where source code lives (e.g. `src/`, `app/`, `lib/`, `cmd/`, `packages/`, or project root). If `root.prizm` is missing, scan the project tree:
-   ```bash
-   find . -maxdepth 2 -type f \( -name "*.js" -o -name "*.ts" -o -name "*.py" -o -name "*.go" -o -name "*.java" -o -name "*.rb" -o -name "*.rs" \) -not -path '*/node_modules/*' -not -path '*/.git/*' -not -path '*/dist/*' -not -path '*/build/*' -not -path '*/vendor/*' | head -30
-   ```
-   Identify the top-level source directories from the results.
-3. Scan the detected source directories for files related to this feature; read each one
-4. Write `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md`:
-   - **Section 1 — Task Contract**: Objective, scope rule, non-scope rule, and Verification Gates from the Task Contract above
-   - **Section 2 — Project Structure**: run the following to get a visual directory tree, then paste output:
-     ```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'
-     ```
+2. Read source files listed in the feature's scope (use prizm-docs KEY_FILES for guidance)
+3. Write `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md`:
+   - **Section 1 — Feature Brief**: 2-3 line feature description from Task Contract
+   - **Section 2 — Verification Gates**: gate checklist from Task Contract
+   - **Section 3 — Key TRAPS & RULES**: extract only relevant TRAPS/RULES from prizm-docs that apply to files in this scope. Do NOT copy full L0/L1/L2 content.
+   - **Section 4 — File Manifest**: file path, why needed, key interfaces. Format: Files to Modify | Files for Reference tables.

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

@@ -1,6 +1,13 @@
-   - **Section 3 — Prizm Context**: content of root.prizm and relevant L1/L2 docs
-   - **Section 4 — Existing Source Files**: **full verbatim content** of each related file in fenced code blocks (with `### path/to/file` heading and line count). Include ALL files needed for implementation and review — downstream phases read this section instead of re-reading individual source files
-   - **Section 5 — Existing Tests**: full content of related test files as code block
+   - **Section 3 — Key TRAPS & RULES**: extract only relevant TRAPS/RULES from prizm-docs that apply to files in this scope. Do NOT copy full L0/L1/L2 content.
+   - **Section 4 — File Manifest**: For each relevant file, list path, why needed, key interface signatures. Use table format:
+
+     ### Files to Modify
+     | File | Why Needed | Key Interfaces |
+     |------|-----------|----------------|
+
+     ### Files for Reference
+     | File | Why Needed | Key Interfaces |
+     |------|-----------|----------------|
 
 
 **Checkpoint update**: Run the update script to set step `context-snapshot` to `"completed"`:

package/bundled/dev-pipeline/templates/sections/phase-implement-agent.md

@@ -7,6 +7,7 @@
 |-----------|-------|
 | subagent_type | prizm-dev-team-dev |
 | run_in_background | false |
+| isolation | Leave empty — Dev works directly in the repo, no worktree |
 
 **Agent spawn failure policy**:
 - If spawning Dev fails with team/config/lock errors, retry at most once.

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

@@ -19,13 +19,10 @@ ls .prizmkit/specs/{{FEATURE_SLUG}}/ 2>/dev/null
    Identify the top-level source directories from the results.
 3. Scan the detected source directories for files related to this feature; read each one
 4. Write `.prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md`:
-   - **Section 1 — Task Contract**: Objective, scope rule, non-scope rule, and Verification Gates from the Task Contract above
-   - **Section 2 — Project Structure**: run the following to get a visual directory tree, then paste output:
-     ```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'
-     ```
-   - **Section 3 — Prizm Context**: full content of root.prizm and relevant L1/L2 docs
-   - **Section 4 — File Manifest**: For each file relevant to this feature, list: file path, why it's needed (modify/reference/test), key interface signatures (function names + params + return types). Do NOT include full file content — agents read files on-demand. Format:
+   - **Section 1 — Feature Brief**: feature description (copy from Task Contract above, 2-3 lines only)
+   - **Section 2 — Verification Gates**: copy the gate checklist from the Task Contract above
+   - **Section 3 — Key TRAPS & RULES**: extract TRAPS and RULES entries from loaded prizm-docs that apply to files in this feature's scope. Do NOT copy full L0/L1/L2 content — only the specific TRAPS/RULES lines relevant to the files listed in Section 4.
+   - **Section 4 — File Manifest**: For each file relevant to this feature, list path, why needed (modify/reference/test), key interface signatures. Do NOT include full file content. Format:
      ### Files to Modify
      | File | Why Needed | Key Interfaces |
      |------|-----------|----------------|
@@ -38,7 +35,6 @@ ls .prizmkit/specs/{{FEATURE_SLUG}}/ 2>/dev/null
 
      ### Known TRAPS (from .prizmkit/prizm-docs/)
      - <trap entries extracted from L1/L2 docs>
-   - **Section 5 — Existing Tests**: full content of related test files as code blocks
 5. Confirm: `ls .prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md`
 
 **After Step A**: Use context-snapshot.md Section 4 File Manifest to guide targeted file reads. Do NOT scan directories or read unrelated files.

package/bundled/dev-pipeline-windows/lib/common.ps1

@@ -3,7 +3,9 @@ $ErrorActionPreference = 'Stop'
 
 $script:PrizmAiProcess = $null
 
-if (-not ('PrizmLineLogBridge' -as [type])) {
+function Initialize-PrizmLineLogBridgeType {
+  if ('PrizmLineLogBridge' -as [type]) { return }
+
   Add-Type -TypeDefinition @'
 using System;
 using System.Diagnostics;
@@ -164,6 +166,63 @@ function Test-PrizmInfraError {
   return ($haystack -match '(?i)auth_unavailable|no auth available|502 Bad Gateway|503 Service Unavailable|504 Gateway Timeout|gateway timeout|upstream (connect )?error|connection reset|ECONNRESET|ETIMEDOUT|ENOTFOUND|EAI_AGAIN|rate limit|rate_limit|temporarily unavailable|overloaded')
 }
 
+function Test-PrizmAiRuntimeError {
+  param([string]$SessionLog, [string]$ProgressJson)
+
+  if ($ProgressJson -and (Test-Path $ProgressJson)) {
+    try {
+      $progress = Get-Content $ProgressJson -Raw -ErrorAction Stop | ConvertFrom-Json -ErrorAction Stop
+      if ($progress.PSObject.Properties['fatal_error_code'] -and $progress.fatal_error_code) {
+        return $true
+      }
+    } catch {}
+  }
+
+  $parts = @()
+  if ($SessionLog -and (Test-Path $SessionLog)) {
+    try {
+      $text = Get-Content $SessionLog -Raw -ErrorAction Stop
+      if ($text.Length -gt 65536) { $text = $text.Substring($text.Length - 65536) }
+      $parts += $text
+    } catch {}
+  }
+  if ($ProgressJson -and (Test-Path $ProgressJson)) {
+    try { $parts += (Get-Content $ProgressJson -Raw -ErrorAction Stop) } catch {}
+  }
+  if ($parts.Count -eq 0) { return $false }
+
+  $haystack = $parts -join "`n"
+  $contextPattern = '(?i)context_too_large|model_context_window_exceeded|input exceeds the context window|context window of this model|context window (was )?exceeded|exceeded (the )?context window|invalid_request_error.*context window|context window.*invalid_request_error'
+  $errorPattern = '(?i)api error|invalid_request_error|api_error_status|api_error_code|status\s*[:=]?\s*(400|413)|last_result_is_error\s*["'':=]?\s*true|is_error\s*["'':=]?\s*true'
+  if (($haystack -match $contextPattern) -and ($haystack -match $errorPattern)) { return $true }
+  return $false
+}
+
+function Get-PrizmProgressFatalErrorCode {
+  param([string]$ProgressFile)
+  if (-not (Test-Path $ProgressFile)) { return '' }
+  try {
+    $progress = Get-Content $ProgressFile -Raw -ErrorAction Stop | ConvertFrom-Json -ErrorAction Stop
+    if ($progress.PSObject.Properties['fatal_error_code'] -and $progress.fatal_error_code) {
+      return [string]$progress.fatal_error_code
+    }
+  } catch {}
+  return ''
+}
+
+function Write-PrizmFatalErrorMarker {
+  param([string]$MarkerPath, [string]$FatalErrorCode, [int]$StaleSeconds, [int]$Threshold)
+  $markerDir = Split-Path $MarkerPath -Parent
+  if ($markerDir) { New-Item -ItemType Directory -Force -Path $markerDir | Out-Null }
+  [ordered]@{
+    killed_at = (Get-Date).ToUniversalTime().ToString('yyyy-MM-ddTHH:mm:ssZ')
+    reason = $FatalErrorCode
+    fatal_error_code = $FatalErrorCode
+    stale_seconds = $StaleSeconds
+    threshold = $Threshold
+  } | ConvertTo-Json -Compress | Set-Content -Path $MarkerPath -Encoding UTF8
+}
+
 function Get-PrizmConfigValue {
   param([string]$ConfigPath, [string]$Key)
   if (-not (Test-Path $ConfigPath)) { return $null }
@@ -638,6 +697,7 @@ function Invoke-PrizmAiSession {
     $psi.Arguments = $argumentString
   }
 
+  Initialize-PrizmLineLogBridgeType
   $process = [System.Diagnostics.Process]::Start($psi)
   $script:PrizmAiProcess = $process
   $logBridge = [PrizmLineLogBridge]::new($LogPath)