prizmkit 1.1.100 → 1.1.101

package/bundled/dev-pipeline-windows/templates/sections/phase-browser-verification-auto.md

@@ -1,283 +0,0 @@
-### Browser Verification (Auto-Select Tool) — MANDATORY
-
-You MUST execute this phase. Do NOT skip it. Select the best available browser tool at runtime and use PowerShell-native commands for setup, server lifecycle, and cleanup.
-
-**Tool Selection**: Choose the best browser tool at runtime.
-
-**Step 0 — Detect available tools**:
-```powershell
-"=== playwright-cli ==="
-$playwright = Get-Command playwright-cli -ErrorAction SilentlyContinue
-if ($playwright) { playwright-cli --version } else { "NOT_INSTALLED" }
-"=== opencli ==="
-$opencli = Get-Command opencli -ErrorAction SilentlyContinue
-if ($opencli) { opencli --version } else { "NOT_INSTALLED" }
-if ($opencli) {
-  opencli doctor 2>$null
-  if ($LASTEXITCODE -ne 0) { "OPENCLI_BRIDGE_FAILED" }
-}
-```
-
-**Decision table**:
-| Condition | Tool |
-|-----------|------|
-| Only playwright-cli available | playwright-cli |
-| Only opencli available (doctor passes) | opencli |
-| Both — local dev server, forms, components | playwright-cli |
-| Both — needs real login state (OAuth/SSO) | opencli |
-| Both — third-party integration verification | opencli |
-| Neither available | Install playwright-cli as default |
-
-Then follow the corresponding tool's workflow above (Steps 1-3).
-
-If you choose playwright-cli, follow this workflow:
-
-**Using: playwright-cli**
-
-**CRITICAL CONSTRAINT — playwright-cli ONLY, NO Playwright MCP**:
-- You MUST use `playwright-cli` (the CLI tool) for ALL browser interactions in this phase
-- **NEVER** use Playwright MCP server, Playwright MCP tools, or any MCP-based browser automation
-- If you have Playwright MCP configured, IGNORE it entirely — use the CLI command `playwright-cli` exclusively
-- All browser actions go through `playwright-cli <command>` in the PowerShell tool, not through any MCP tool call
-
-**Step 0 — Playwright CLI Readiness Check (BLOCKING — must pass before any browser action)**:
-
-0a. Check if `playwright-cli` is installed:
-```powershell
-$playwright = Get-Command playwright-cli -ErrorAction SilentlyContinue
-if ($playwright) { playwright-cli --version } else { "NOT_INSTALLED" }
-```
-If output is `NOT_INSTALLED`, install it:
-```powershell
-npm install -g @playwright/cli@latest
-```
-Then verify installation succeeded:
-```powershell
-playwright-cli --version
-```
-If installation fails, log the error in context-snapshot.md under `## Browser Verification: SKIPPED — playwright-cli installation failed` and proceed to the next phase. Do NOT attempt browser verification without playwright-cli.
-
-0b. Learn playwright-cli usage (run once per session to understand available commands):
-```powershell
-playwright-cli --help
-```
-Use this output to determine the correct commands for your verification steps. Do NOT guess command syntax — refer to the help output.
-
-0c. Check if playwright-cli skill is installed for the current AI platform:
-```powershell
-$currentPlatform = "unknown"
-$skillDir = $null
-if (Get-Command claude -ErrorAction SilentlyContinue) {
-  $currentPlatform = "claude"
-  $skillDir = Join-Path $HOME ".claude\skills"
-} elseif (Get-Command cbc -ErrorAction SilentlyContinue) {
-  $currentPlatform = "codebuddy"
-  $skillDir = Join-Path $HOME ".cbc\skills"
-}
-
-$skillExists = $false
-if ($skillDir) {
-  $directSkill = Join-Path $skillDir "playwright-cli"
-  $matchingSkills = Get-ChildItem -Path $skillDir -Filter "playwright*" -ErrorAction SilentlyContinue
-  $skillExists = (Test-Path -LiteralPath $directSkill) -or [bool]$matchingSkills
-}
-if ($skillExists) { "SKILL_EXISTS" } else { "SKILL_MISSING" }
-```
-If `SKILL_MISSING`:
-```powershell
-playwright-cli install --skills
-```
-If the current platform is NOT claude, move the installed skill files to the correct location:
-```powershell
-$claudeSkillDir = Join-Path $HOME ".claude\skills"
-$sourceSkill = Join-Path $claudeSkillDir "playwright-cli"
-if ($currentPlatform -ne "claude" -and $currentPlatform -ne "unknown" -and $skillDir -and (Test-Path -LiteralPath $sourceSkill)) {
-  New-Item -ItemType Directory -Force -Path $skillDir | Out-Null
-  Copy-Item -Recurse -Force -Path $sourceSkill -Destination $skillDir
-  "Moved playwright-cli skill from claude to $currentPlatform"
-}
-```
-
-0d. Read the installed playwright-cli skill for workflow guidance:
-After skill installation, read the skill's SKILL.md to understand recommended workflows and patterns. Use these patterns to construct your verification flow — do NOT invent your own patterns if the skill provides them.
-
-**Step 1 — Start Dev Server**:
-
-You know this project's tech stack. Detect and start the dev server yourself:
-
-1. Identify the dev server start command from project config (`package.json` scripts, `Makefile`, `docker-compose.yml`, etc.)
-2. **Detect the dev server port** — use the pre-detected port from pipeline if available, otherwise extract from project config. Do NOT hardcode or guess the port:
-   ```powershell
-   $DEV_PORT = "{{DEV_PORT}}"
-   if ($DEV_PORT -eq "{{DEV_PORT}}" -or [string]::IsNullOrWhiteSpace($DEV_PORT)) {
-     $detectedPort = ""
-     if (Test-Path -LiteralPath "package.json") {
-       $detectedPort = node -e "const p=require('./package.json'); const s=(p.scripts?.dev) || ''; const m=s.match(/-p\s+(\d+)/); console.log(m?m[1]:'')"
-     }
-     if (-not $detectedPort -and $env:NEXT_PUBLIC_SITE_URL -match ':([0-9]+)') {
-       $detectedPort = $Matches[1]
-     }
-     if ($detectedPort) { $DEV_PORT = $detectedPort } else { $DEV_PORT = "3000" }
-   }
-   "Detected DEV_PORT=$DEV_PORT"
-   ```
-3. Verify the port is available and start the dev server in the background, capturing its process id:
-   ```powershell
-   $portBusy = Get-NetTCPConnection -LocalPort ([int]$DEV_PORT) -ErrorAction SilentlyContinue
-   if ($portBusy) { "PORT_IN_USE" } else { "PORT_FREE" }
-   $devServerCommand = "<start-command>"
-   $server = Start-Process -FilePath "powershell" -ArgumentList @("-NoProfile", "-Command", $devServerCommand) -PassThru
-   $DEV_SERVER_PID = $server.Id
-   ```
-
-   Wait for server to be ready: poll `http://localhost:$DEV_PORT` until it returns 200 or 302 (max 30 seconds, 2s interval):
-   ```powershell
-   $ready = $false
-   for ($i = 0; $i -lt 15; $i++) {
-     try {
-       $response = Invoke-WebRequest -Uri "http://localhost:$DEV_PORT" -UseBasicParsing -TimeoutSec 2
-       if ($response.StatusCode -in @(200, 302)) { $ready = $true; break }
-     } catch {
-       Start-Sleep -Seconds 2
-     }
-   }
-   if (-not $ready) { "DEV_SERVER_NOT_READY" }
-   ```
-4. Open the app in playwright-cli: `playwright-cli open "http://localhost:$DEV_PORT"`
-5. If the page requires authentication, use playwright-cli to register a test user and log in first
-
-**Step 2 — Verification**:
-
-Use `playwright-cli snapshot` on the running app to discover actual element refs, then verify these goals:
-{{BROWSER_VERIFY_STEPS}}
-
-Construct your verification workflow based on:
-1. The playwright-cli skill documentation (read in Step 0d)
-2. The `playwright-cli --help` output (captured in Step 0b)
-3. The current task's Verification Gates and implemented features
-
-Decide the concrete playwright-cli actions (click, fill, snapshot, screenshot, etc.) yourself based on the snapshot output and your knowledge of the implemented code. The goals above describe WHAT to verify — you determine HOW using playwright-cli commands.
-
-Take a final screenshot for evidence: `playwright-cli screenshot`
-
-**Step 3 — Cleanup (REQUIRED — you started it, you stop it)**:
-
-1. Close the playwright-cli browser: `playwright-cli close`
-2. Stop the dev server process and any remaining process bound to the dev server port:
-   ```powershell
-   if ($DEV_SERVER_PID) { Stop-Process -Id $DEV_SERVER_PID -Force -ErrorAction SilentlyContinue }
-   Get-NetTCPConnection -LocalPort ([int]$DEV_PORT) -ErrorAction SilentlyContinue |
-     Select-Object -ExpandProperty OwningProcess -Unique |
-     ForEach-Object { Stop-Process -Id $_ -Force -ErrorAction SilentlyContinue }
-   ```
-
-If you choose opencli, follow this workflow:
-
-**Using: opencli** (reuses Chrome logged-in sessions)
-
-**CRITICAL CONSTRAINT — opencli browser ONLY**:
-- You MUST use `opencli browser` for ALL browser interactions in this phase
-- All browser actions go through `opencli browser <command>` in the PowerShell tool
-
-**Step 0 — OpenCLI Readiness Check (BLOCKING)**:
-
-0a. Check if `opencli` is installed:
-```powershell
-$opencli = Get-Command opencli -ErrorAction SilentlyContinue
-if ($opencli) { opencli --version } else { "NOT_INSTALLED" }
-```
-If `NOT_INSTALLED`: `npm install -g @jackwener/opencli@latest`. If installation fails, log `## Browser Verification: SKIPPED — opencli installation failed` and proceed.
-
-0b. Verify Browser Bridge: `opencli doctor`. If fails, log skip and proceed.
-
-0c. Learn usage:
-```powershell
-opencli browser --help 2>$null
-if ($LASTEXITCODE -ne 0) { opencli --help }
-```
-
-**Step 1 — Start Dev Server**: use the same port detection and server lifecycle pattern as the playwright-cli path:
-```powershell
-$DEV_PORT = "{{DEV_PORT}}"
-if ($DEV_PORT -eq "{{DEV_PORT}}" -or [string]::IsNullOrWhiteSpace($DEV_PORT)) {
-  $detectedPort = ""
-  if (Test-Path -LiteralPath "package.json") {
-    $detectedPort = node -e "const p=require('./package.json'); const s=(p.scripts?.dev) || ''; const m=s.match(/-p\s+(\d+)/); console.log(m?m[1]:'')"
-  }
-  if (-not $detectedPort -and $env:NEXT_PUBLIC_SITE_URL -match ':([0-9]+)') {
-    $detectedPort = $Matches[1]
-  }
-  if ($detectedPort) { $DEV_PORT = $detectedPort } else { $DEV_PORT = "3000" }
-}
-"Detected DEV_PORT=$DEV_PORT"
-```
-```powershell
-$portBusy = Get-NetTCPConnection -LocalPort ([int]$DEV_PORT) -ErrorAction SilentlyContinue
-if ($portBusy) { "PORT_IN_USE" } else { "PORT_FREE" }
-$devServerCommand = "<start-command>"
-$server = Start-Process -FilePath "powershell" -ArgumentList @("-NoProfile", "-Command", $devServerCommand) -PassThru
-$DEV_SERVER_PID = $server.Id
-```
-
-Wait for server to be ready: poll `http://localhost:$DEV_PORT` until it returns 200 or 302 (max 30 seconds, 2s interval):
-```powershell
-$ready = $false
-for ($i = 0; $i -lt 15; $i++) {
-  try {
-    $response = Invoke-WebRequest -Uri "http://localhost:$DEV_PORT" -UseBasicParsing -TimeoutSec 2
-    if ($response.StatusCode -in @(200, 302)) { $ready = $true; break }
-  } catch {
-    Start-Sleep -Seconds 2
-  }
-}
-if (-not $ready) { "DEV_SERVER_NOT_READY" }
-```
-
-Start server, wait for ready, then:
-```powershell
-opencli browser open "http://localhost:$DEV_PORT"
-if ($LASTEXITCODE -eq 0) { opencli browser state }
-```
-
-**Step 2 — Verification**:
-
-Use `opencli browser state` to discover elements with `[N]` indices, then verify:
-{{BROWSER_VERIFY_STEPS}}
-
-Chain commands in PowerShell with semicolons and inspect each result, for example: `opencli browser click <N>; opencli browser wait time 1; opencli browser state`
-
-**Step 3 — Cleanup**:
-1. `opencli browser close`
-2. Stop the dev server process and any remaining process bound to the dev server port:
-   ```powershell
-   if ($DEV_SERVER_PID) { Stop-Process -Id $DEV_SERVER_PID -Force -ErrorAction SilentlyContinue }
-   Get-NetTCPConnection -LocalPort ([int]$DEV_PORT) -ErrorAction SilentlyContinue |
-     Select-Object -ExpandProperty OwningProcess -Unique |
-     ForEach-Object { Stop-Process -Id $_ -Force -ErrorAction SilentlyContinue }
-   ```
-
-**Step 4 — Reporting**:
-
-Append results to `context-snapshot.md`:
-```
-## Browser Verification
-Tool: <playwright-cli or opencli>
-URL: http://localhost:$DEV_PORT
-Dev Server Command: <actual command used>
-Tool version: <version>
-Steps executed: [list of commands used]
-Screenshot: [path]
-Result: PASS / FAIL (reason)
-Server cleanup: confirmed
-Browser cleanup: confirmed
-```
-
-If verification fails, log the failure details but continue to commit. Failures do NOT block the commit, but you MUST attempt verification and MUST clean up the dev server.
-
-**Checkpoint update**: Run the update script to set step `browser-verification` to `"completed"`:
-```powershell
-Invoke-PrizmPython {{PIPELINE_DIR}}\scripts\update-checkpoint.py `
-  --checkpoint-path {{CHECKPOINT_PATH}} `
-  --step browser-verification `
-  --status completed
-```

package/bundled/dev-pipeline-windows/templates/sections/phase-browser-verification-opencli.md

@@ -1,112 +0,0 @@
-### Browser Verification (opencli) — MANDATORY
-
-You MUST execute this phase. Do NOT skip it. Do NOT mark it as completed without actually running opencli.
-
-**Using: opencli** (reuses Chrome logged-in sessions)
-
-**CRITICAL CONSTRAINT — opencli browser ONLY**:
-- You MUST use `opencli browser` for ALL browser interactions in this phase
-- All browser actions go through `opencli browser <command>` in the PowerShell tool
-
-**Step 0 — OpenCLI Readiness Check (BLOCKING)**:
-
-0a. Check if `opencli` is installed:
-```powershell
-$opencli = Get-Command opencli -ErrorAction SilentlyContinue
-if ($opencli) { opencli --version } else { "NOT_INSTALLED" }
-```
-If `NOT_INSTALLED`: `npm install -g @jackwener/opencli@latest`. If installation fails, log `## Browser Verification: SKIPPED — opencli installation failed` and proceed.
-
-0b. Verify Browser Bridge: `opencli doctor`. If fails, log skip and proceed.
-
-0c. Learn usage:
-```powershell
-opencli browser --help 2>$null
-if ($LASTEXITCODE -ne 0) { opencli --help }
-```
-
-**Step 1 — Start Dev Server**: use the same port detection and server lifecycle pattern as the playwright-cli path:
-```powershell
-$DEV_PORT = "{{DEV_PORT}}"
-if ($DEV_PORT -eq "{{DEV_PORT}}" -or [string]::IsNullOrWhiteSpace($DEV_PORT)) {
-  $detectedPort = ""
-  if (Test-Path -LiteralPath "package.json") {
-    $detectedPort = node -e "const p=require('./package.json'); const s=(p.scripts?.dev) || ''; const m=s.match(/-p\s+(\d+)/); console.log(m?m[1]:'')"
-  }
-  if (-not $detectedPort -and $env:NEXT_PUBLIC_SITE_URL -match ':([0-9]+)') {
-    $detectedPort = $Matches[1]
-  }
-  if ($detectedPort) { $DEV_PORT = $detectedPort } else { $DEV_PORT = "3000" }
-}
-"Detected DEV_PORT=$DEV_PORT"
-```
-```powershell
-$portBusy = Get-NetTCPConnection -LocalPort ([int]$DEV_PORT) -ErrorAction SilentlyContinue
-if ($portBusy) { "PORT_IN_USE" } else { "PORT_FREE" }
-$devServerCommand = "<start-command>"
-$server = Start-Process -FilePath "powershell" -ArgumentList @("-NoProfile", "-Command", $devServerCommand) -PassThru
-$DEV_SERVER_PID = $server.Id
-```
-
-Wait for server to be ready: poll `http://localhost:$DEV_PORT` until it returns 200 or 302 (max 30 seconds, 2s interval):
-```powershell
-$ready = $false
-for ($i = 0; $i -lt 15; $i++) {
-  try {
-    $response = Invoke-WebRequest -Uri "http://localhost:$DEV_PORT" -UseBasicParsing -TimeoutSec 2
-    if ($response.StatusCode -in @(200, 302)) { $ready = $true; break }
-  } catch {
-    Start-Sleep -Seconds 2
-  }
-}
-if (-not $ready) { "DEV_SERVER_NOT_READY" }
-```
-
-Start server, wait for ready, then:
-```powershell
-opencli browser open "http://localhost:$DEV_PORT"
-if ($LASTEXITCODE -eq 0) { opencli browser state }
-```
-
-**Step 2 — Verification**:
-
-Use `opencli browser state` to discover elements with `[N]` indices, then verify:
-{{BROWSER_VERIFY_STEPS}}
-
-Chain commands in PowerShell with semicolons and inspect each result, for example: `opencli browser click <N>; opencli browser wait time 1; opencli browser state`
-
-**Step 3 — Cleanup**:
-1. `opencli browser close`
-2. Stop the dev server process and any remaining process bound to the dev server port:
-   ```powershell
-   if ($DEV_SERVER_PID) { Stop-Process -Id $DEV_SERVER_PID -Force -ErrorAction SilentlyContinue }
-   Get-NetTCPConnection -LocalPort ([int]$DEV_PORT) -ErrorAction SilentlyContinue |
-     Select-Object -ExpandProperty OwningProcess -Unique |
-     ForEach-Object { Stop-Process -Id $_ -Force -ErrorAction SilentlyContinue }
-   ```
-
-**Step 4 — Reporting**:
-
-Append results to `context-snapshot.md`:
-```
-## Browser Verification
-Tool: <playwright-cli or opencli>
-URL: http://localhost:$DEV_PORT
-Dev Server Command: <actual command used>
-Tool version: <version>
-Steps executed: [list of commands used]
-Screenshot: [path]
-Result: PASS / FAIL (reason)
-Server cleanup: confirmed
-Browser cleanup: confirmed
-```
-
-If verification fails, log the failure details but continue to commit. Failures do NOT block the commit, but you MUST attempt verification and MUST clean up the dev server.
-
-**Checkpoint update**: Run the update script to set step `browser-verification` to `"completed"`:
-```powershell
-Invoke-PrizmPython {{PIPELINE_DIR}}\scripts\update-checkpoint.py `
-  --checkpoint-path {{CHECKPOINT_PATH}} `
-  --step browser-verification `
-  --status completed
-```

package/bundled/dev-pipeline-windows/templates/sections/phase-browser-verification.md

@@ -1,168 +0,0 @@
-### Browser Verification (playwright-cli) — MANDATORY
-
-You MUST execute this phase. Do NOT skip it. Do NOT mark it as completed without actually running playwright-cli.
-
-**Using: playwright-cli**
-
-**CRITICAL CONSTRAINT — playwright-cli ONLY, NO Playwright MCP**:
-- You MUST use `playwright-cli` (the CLI tool) for ALL browser interactions in this phase
-- **NEVER** use Playwright MCP server, Playwright MCP tools, or any MCP-based browser automation
-- If you have Playwright MCP configured, IGNORE it entirely — use the CLI command `playwright-cli` exclusively
-- All browser actions go through `playwright-cli <command>` in the PowerShell tool, not through any MCP tool call
-
-**Step 0 — Playwright CLI Readiness Check (BLOCKING — must pass before any browser action)**:
-
-0a. Check if `playwright-cli` is installed:
-```powershell
-$playwright = Get-Command playwright-cli -ErrorAction SilentlyContinue
-if ($playwright) { playwright-cli --version } else { "NOT_INSTALLED" }
-```
-If output is `NOT_INSTALLED`, install it:
-```powershell
-npm install -g @playwright/cli@latest
-```
-Then verify installation succeeded:
-```powershell
-playwright-cli --version
-```
-If installation fails, log the error in context-snapshot.md under `## Browser Verification: SKIPPED — playwright-cli installation failed` and proceed to the next phase. Do NOT attempt browser verification without playwright-cli.
-
-0b. Learn playwright-cli usage (run once per session to understand available commands):
-```powershell
-playwright-cli --help
-```
-Use this output to determine the correct commands for your verification steps. Do NOT guess command syntax — refer to the help output.
-
-0c. Check if playwright-cli skill is installed for the current AI platform:
-```powershell
-$currentPlatform = "unknown"
-$skillDir = $null
-if (Get-Command claude -ErrorAction SilentlyContinue) {
-  $currentPlatform = "claude"
-  $skillDir = Join-Path $HOME ".claude\skills"
-} elseif (Get-Command cbc -ErrorAction SilentlyContinue) {
-  $currentPlatform = "codebuddy"
-  $skillDir = Join-Path $HOME ".cbc\skills"
-}
-
-$skillExists = $false
-if ($skillDir) {
-  $directSkill = Join-Path $skillDir "playwright-cli"
-  $matchingSkills = Get-ChildItem -Path $skillDir -Filter "playwright*" -ErrorAction SilentlyContinue
-  $skillExists = (Test-Path -LiteralPath $directSkill) -or [bool]$matchingSkills
-}
-if ($skillExists) { "SKILL_EXISTS" } else { "SKILL_MISSING" }
-```
-If `SKILL_MISSING`:
-```powershell
-playwright-cli install --skills
-```
-If the current platform is NOT claude, move the installed skill files to the correct location:
-```powershell
-$claudeSkillDir = Join-Path $HOME ".claude\skills"
-$sourceSkill = Join-Path $claudeSkillDir "playwright-cli"
-if ($currentPlatform -ne "claude" -and $currentPlatform -ne "unknown" -and $skillDir -and (Test-Path -LiteralPath $sourceSkill)) {
-  New-Item -ItemType Directory -Force -Path $skillDir | Out-Null
-  Copy-Item -Recurse -Force -Path $sourceSkill -Destination $skillDir
-  "Moved playwright-cli skill from claude to $currentPlatform"
-}
-```
-
-0d. Read the installed playwright-cli skill for workflow guidance:
-After skill installation, read the skill's SKILL.md to understand recommended workflows and patterns. Use these patterns to construct your verification flow — do NOT invent your own patterns if the skill provides them.
-
-**Step 1 — Start Dev Server**:
-
-You know this project's tech stack. Detect and start the dev server yourself:
-
-1. Identify the dev server start command from project config (`package.json` scripts, `Makefile`, `docker-compose.yml`, etc.)
-2. **Detect the dev server port** — use the pre-detected port from pipeline if available, otherwise extract from project config. Do NOT hardcode or guess the port:
-   ```powershell
-   $DEV_PORT = "{{DEV_PORT}}"
-   if ($DEV_PORT -eq "{{DEV_PORT}}" -or [string]::IsNullOrWhiteSpace($DEV_PORT)) {
-     $detectedPort = ""
-     if (Test-Path -LiteralPath "package.json") {
-       $detectedPort = node -e "const p=require('./package.json'); const s=(p.scripts?.dev) || ''; const m=s.match(/-p\s+(\d+)/); console.log(m?m[1]:'')"
-     }
-     if (-not $detectedPort -and $env:NEXT_PUBLIC_SITE_URL -match ':([0-9]+)') {
-       $detectedPort = $Matches[1]
-     }
-     if ($detectedPort) { $DEV_PORT = $detectedPort } else { $DEV_PORT = "3000" }
-   }
-   "Detected DEV_PORT=$DEV_PORT"
-   ```
-3. Verify the port is available and start the dev server in the background, capturing its process id:
-   ```powershell
-   $portBusy = Get-NetTCPConnection -LocalPort ([int]$DEV_PORT) -ErrorAction SilentlyContinue
-   if ($portBusy) { "PORT_IN_USE" } else { "PORT_FREE" }
-   $devServerCommand = "<start-command>"
-   $server = Start-Process -FilePath "powershell" -ArgumentList @("-NoProfile", "-Command", $devServerCommand) -PassThru
-   $DEV_SERVER_PID = $server.Id
-   ```
-
-   Wait for server to be ready: poll `http://localhost:$DEV_PORT` until it returns 200 or 302 (max 30 seconds, 2s interval):
-   ```powershell
-   $ready = $false
-   for ($i = 0; $i -lt 15; $i++) {
-     try {
-       $response = Invoke-WebRequest -Uri "http://localhost:$DEV_PORT" -UseBasicParsing -TimeoutSec 2
-       if ($response.StatusCode -in @(200, 302)) { $ready = $true; break }
-     } catch {
-       Start-Sleep -Seconds 2
-     }
-   }
-   if (-not $ready) { "DEV_SERVER_NOT_READY" }
-   ```
-4. Open the app in playwright-cli: `playwright-cli open "http://localhost:$DEV_PORT"`
-5. If the page requires authentication, use playwright-cli to register a test user and log in first
-
-**Step 2 — Verification**:
-
-Use `playwright-cli snapshot` on the running app to discover actual element refs, then verify these goals:
-{{BROWSER_VERIFY_STEPS}}
-
-Construct your verification workflow based on:
-1. The playwright-cli skill documentation (read in Step 0d)
-2. The `playwright-cli --help` output (captured in Step 0b)
-3. The current task's Verification Gates and implemented features
-
-Decide the concrete playwright-cli actions (click, fill, snapshot, screenshot, etc.) yourself based on the snapshot output and your knowledge of the implemented code. The goals above describe WHAT to verify — you determine HOW using playwright-cli commands.
-
-Take a final screenshot for evidence: `playwright-cli screenshot`
-
-**Step 3 — Cleanup (REQUIRED — you started it, you stop it)**:
-
-1. Close the playwright-cli browser: `playwright-cli close`
-2. Stop the dev server process and any remaining process bound to the dev server port:
-   ```powershell
-   if ($DEV_SERVER_PID) { Stop-Process -Id $DEV_SERVER_PID -Force -ErrorAction SilentlyContinue }
-   Get-NetTCPConnection -LocalPort ([int]$DEV_PORT) -ErrorAction SilentlyContinue |
-     Select-Object -ExpandProperty OwningProcess -Unique |
-     ForEach-Object { Stop-Process -Id $_ -Force -ErrorAction SilentlyContinue }
-   ```
-
-**Step 4 — Reporting**:
-
-Append results to `context-snapshot.md`:
-```
-## Browser Verification
-Tool: <playwright-cli or opencli>
-URL: http://localhost:$DEV_PORT
-Dev Server Command: <actual command used>
-Tool version: <version>
-Steps executed: [list of commands used]
-Screenshot: [path]
-Result: PASS / FAIL (reason)
-Server cleanup: confirmed
-Browser cleanup: confirmed
-```
-
-If verification fails, log the failure details but continue to commit. Failures do NOT block the commit, but you MUST attempt verification and MUST clean up the dev server.
-
-**Checkpoint update**: Run the update script to set step `browser-verification` to `"completed"`:
-```powershell
-Invoke-PrizmPython {{PIPELINE_DIR}}\scripts\update-checkpoint.py `
-  --checkpoint-path {{CHECKPOINT_PATH}} `
-  --step browser-verification `
-  --status completed
-```

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

@@ -1,82 +0,0 @@
-### Architecture Sync & Commit (SINGLE COMMIT) — DO NOT SKIP
-
-**a.** Check if feature already committed:
-```powershell
-git log --oneline | Select-String -Pattern "{{FEATURE_ID}}" | Select-Object -First 3
-```
-- If a commit for `{{FEATURE_ID}}` already exists → **skip d** (do NOT run /prizmkit-committer, do NOT run git reset, do NOT stage or unstage anything). Proceed directly to e Final verification.
-- If no existing commit → proceed normally with b–d.
-
-**b.** Run `/prizmkit-retrospective` (**before commit**, maintains `.prizmkit/prizm-docs/` architecture index):
-1. **Structural sync**: update KEY_FILES/INTERFACES/DEPENDENCIES/file counts for changed modules
-2. **Architecture knowledge**: extract TRAPS, RULES, DECISIONS from completed work into `.prizmkit/prizm-docs/`
-3. **L2 coverage check**: For any module/sub-module with source files created or significantly modified in this session but no L2 `.prizm` doc — evaluate whether L2 is warranted and create if so. The current session has the best context for accurate KEY_FILES, TRAPS, and DECISIONS.
-4. Stage doc changes: `git add .prizmkit/prizm-docs/`
-⚠️ Do NOT commit here. Only stage.
-
-**c.** Stage all feature code explicitly (NEVER use `git add -A` or `git add .`):
-```powershell
-git add <specific-files-created-or-modified>
-git add .prizmkit/prizm-docs/
-```
-
-**d.** Run `/prizmkit-committer` → THE ONLY commit for this feature:
-`feat({{FEATURE_ID}}): {{FEATURE_TITLE}}`
-This single commit includes: feature code + tests + .prizmkit/prizm-docs/ updates. Do NOT push.
-- MANDATORY: commit must be done via `/prizmkit-committer` skill. Do NOT run manual `git add`/`git commit` as a substitute.
-- Do NOT run `update-feature-status.py` here — the pipeline runner handles feature-list.json updates automatically after session exit.
-
-**e.** Final verification:
-```powershell
-git status --short
-```
-Working tree MUST be clean after this step. If any feature-related files remain, stage them into the SAME commit via `git add <file>; if ($LASTEXITCODE -eq 0) { git commit --amend --no-edit }`, do NOT create a separate commit.
-
-**f.** Write completion summary for downstream dependency context:
-
-Write `.prizmkit/specs/{{FEATURE_SLUG}}/completion-summary.json` with the key changes from this session. This file is NOT committed to git — the pipeline runner reads it to propagate context to dependent features.
-
-```json
-{
-  "completion_notes": [
-    "<each item: one key change, API, model, or integration point that downstream features may need>",
-    "Example: Added User model (id, email, password_hash, display_name) in prisma/schema.prisma",
-    "Example: POST /api/auth/register and POST /api/auth/login endpoints in src/api/auth.ts",
-    "Example: Auth middleware in src/middleware/auth.ts — validates JWT on protected routes"
-  ]
-}
-```
-
-Rules for writing completion notes:
-- Focus on **what downstream features need to know**: new APIs, models, exported functions, key file paths
-- Each note should be self-contained and concise (one line, under 120 characters preferred)
-- Include 3-8 notes covering the most important changes
-- Do NOT include test files, config changes, or internal implementation details unless they affect other features
-- If this feature has no downstream dependents, still write the summary (it serves as documentation)
-
-
-**Checkpoint update**: After `/prizmkit-retrospective` completes, run the update script to set step `prizmkit-retrospective` to `"completed"`:
-```powershell
-Invoke-PrizmPython {{PIPELINE_DIR}}\scripts\update-checkpoint.py `
-  --checkpoint-path {{CHECKPOINT_PATH}} `
-  --step prizmkit-retrospective `
-  --status completed
-```
-After `/prizmkit-committer` completes, set step `prizmkit-committer` to `"completed"`:
-```powershell
-Invoke-PrizmPython {{PIPELINE_DIR}}\scripts\update-checkpoint.py `
-  --checkpoint-path {{CHECKPOINT_PATH}} `
-  --step prizmkit-committer `
-  --status completed
-```
-
-### TERMINAL STOP — Commit 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 `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.