prizmkit 1.1.108 → 1.1.110

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

@@ -70,7 +70,7 @@ You are the **bug fix session agent**. Fix Bug {{BUG_ID}}: "{{BUG_TITLE}}".
 ### Phase 0: Initialize
 
 ```bash
-mkdir -p .prizmkit/bugfix/{{BUG_ID}}
+{{RUNTIME_HELPER_CMD}} artifact ensure-dir .prizmkit/bugfix/{{BUG_ID}}
 ```
 
 {{IF_BROWSER_INTERACTION}}
@@ -186,7 +186,7 @@ Run `/prizmkit-code-review` with `artifact_dir=.prizmkit/bugfix/{{BUG_ID}}/`:
 **Gate Check — Review Report**:
 After `/prizmkit-code-review` returns, verify the review report:
 ```bash
-grep -q "## Verdict" .prizmkit/bugfix/{{BUG_ID}}/review-report.md && echo "GATE:PASS" || echo "GATE:MISSING"
+{{RUNTIME_HELPER_CMD}} text contains .prizmkit/bugfix/{{BUG_ID}}/review-report.md --pattern "## Verdict"
 ```
 If GATE:MISSING:
 - Do not re-run `/prizmkit-code-review` in an unbounded report-repair loop.

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

@@ -96,7 +96,7 @@ Reference `{{TEAM_CONFIG_PATH}}` for agent definitions:
 
 Create refactor artifacts directory:
 ```bash
-mkdir -p .prizmkit/refactor/{{REFACTOR_ID}}
+{{RUNTIME_HELPER_CMD}} artifact ensure-dir .prizmkit/refactor/{{REFACTOR_ID}}
 ```
 
 ### Step 2: Pipeline Phases
@@ -208,7 +208,7 @@ Evidence must cover affected UI render, primary user interactions, behavior-sens
 - **Gate Check — Review Report**:
   After Reviewer returns, verify the review report contains a verdict:
   ```bash
-  grep -q "## Verdict" .prizmkit/refactor/{{REFACTOR_ID}}/review-report.md && echo "GATE:PASS" || echo "GATE:MISSING"
+  {{RUNTIME_HELPER_CMD}} text contains .prizmkit/refactor/{{REFACTOR_ID}}/review-report.md --pattern "## Verdict"
   ```
   If GATE:MISSING:
   - Do not enter an unbounded report-repair loop and do not repeatedly re-spawn Reviewer.

package/bundled/dev-pipeline/templates/sections/checkpoint-system.md

@@ -9,7 +9,7 @@ A checkpoint file tracks your progress through this workflow:
 Use this helper to update checkpoint status. Do not hand-edit `workflow-checkpoint.json` directly.
 
 ```bash
-python3 .prizmkit/dev-pipeline/scripts/update-checkpoint.py \
+{{CHECKPOINT_PYTHON_CMD}} \
   --checkpoint-path {{CHECKPOINT_PATH}} \
   --step <step-id-or-skill-name> \
   --status <in_progress|completed|failed|skipped> \

package/bundled/dev-pipeline/templates/sections/context-budget-rules.md

@@ -6,18 +6,18 @@ You are running in **headless non-interactive mode** with a FINITE context windo
 
 1. **context-snapshot.md is your single source of truth** — After it is built, ALWAYS read context-snapshot.md instead of re-reading individual source files
 2. **Never re-read your own writes** — After you create/modify a file, do NOT read it back to verify. Trust your write was correct.
-3. **Never re-read unmodified files** — Once you have read a file into context, do NOT read it again unless it was modified by an Edit/Write operation after your last read. Use `grep -n '<pattern>' <file>` or `sed -n '<start>,<end>p' <file>` for targeted line lookups instead of full-file Read. Before issuing a Read, ask yourself: "Have I read this file before, and has it changed since?" If the answer is "no, it hasn't changed" — do NOT read it. This applies to all files including those summarized in context-snapshot.md Section 4. Subagents (Critic, Reviewer) must receive context-snapshot.md and rely on it rather than independently re-reading the same files the orchestrator already read.
+3. **Never re-read unmodified files** — Once you have read a file into context, do NOT read it again unless it was modified by an Edit/Write operation after your last read. Use platform file/search tools for targeted lookup; when shell-free helper lookup is needed, run `{{RUNTIME_HELPER_CMD}} text search <file> --pattern "<pattern>" --json`, then read only the smallest bounded range with the platform file-reading tool instead of full-file Read. Before issuing a Read, ask yourself: "Have I read this file before, and has it changed since?" If the answer is "no, it hasn't changed" — do NOT read it. This applies to all files including those summarized in context-snapshot.md Section 4. Subagents (Critic, Reviewer) must receive context-snapshot.md and rely on it rather than independently re-reading the same files the orchestrator already read.
 4. **Stay focused** — Do NOT explore code unrelated to this feature. No curiosity-driven reads.
 5. **One task at a time** — Complete and test one task before starting the next.
-6. **Minimize tool output** — Never load full command output into context. First capture to a temp file (`cmd 2>&1 | tee /tmp/out.txt | tail -20`), then scan the head/tail to identify relevant fields, and use targeted filtering (`grep`, `sed`, `awk`) to extract only the information needed for the current task. Only read the filtered result — never the raw full output.
+6. **Minimize tool output** — Never load full command output into context. First capture command output to a temp file using the command/tool output option or the host-appropriate redirection, then inspect only the final relevant lines and use targeted search helpers to extract the information needed for the current task. Only read the filtered result — never the raw full output.
 7. **No intermediate commits** — Do NOT run `git add`/`git commit` during implementation phases. All changes are committed once at the end via `/prizmkit-committer`.
-8. **Capture test output once** — When running test suites during the post-review gate, capture with `<test-command> 2>&1 | tee /tmp/test-out.txt | tail -20`. Then grep `/tmp/test-out.txt` for details. Never re-run the suite just to apply a different filter.
+8. **Capture test output once** — When running test suites during the post-review gate, capture output once to `/tmp/test-out.txt` using the command/tool output option or the host-appropriate redirection, surface only the final relevant lines, then search `/tmp/test-out.txt` for details. Never re-run the suite just to apply a different filter.
 9. **Package version verification (HARD CONSTRAINT — BLOCKING)** — Before writing ANY dependency version in `package.json`, `requirements.txt`, `Cargo.toml`, `go.mod`, `Gemfile`, `pyproject.toml`, or any other dependency manifest:
    - You MUST verify the real version exists by querying the package registry first:
-     - npm/Node.js: `npm view <package> dist-tags.latest 2>/dev/null`
-     - Python/pip: `pip index versions <package> 2>/dev/null | head -1`
-     - Go: `go list -m -versions <module>@latest 2>/dev/null`
-     - Rust: `cargo search <crate> --limit 1 2>/dev/null`
+     - npm/Node.js: `npm view <package> dist-tags.latest`
+     - Python/pip: `pip index versions <package>` and use the first result line
+     - Go: `go list -m -versions <module>@latest`
+     - Rust: `cargo search <crate> --limit 1`
    - **NEVER guess or hallucinate version numbers**. If you cannot verify a version, use `"latest"` or `"*"` as a placeholder, or omit the version constraint entirely and let the package manager resolve it
    - If the registry query fails (network issue, package not found), you MUST either:
      (a) Use a known-safe version you have high confidence in, OR
@@ -26,4 +26,4 @@ You are running in **headless non-interactive mode** with a FINITE context windo
    - **This is a BLOCKING gate**: do NOT run `npm install` / `pip install` / `cargo build` / `go mod tidy` until ALL versions in the manifest have been verified or use open constraints
    - Batch version lookups: query multiple packages in parallel to save time (e.g., run multiple `npm view` commands concurrently)
 10. **Build artifact hygiene** — After any build/compile command (`go build`, `npm run build`, `tsc`, etc.), ensure the output binary, build directory, generated bundle, or cache directory is ignored by git before the commit phase. Never commit compiled binaries, build output, or generated artifacts.
-11. **Read offset safety (BLOCKING)** — If Read returns "shorter than offset"/"File is empty"/"Wasted call" — do NOT retry same offset. Run `wc -l <file>` to get real line count, then `sed -n '<start>,<end>p' <file>` for exact range. 2 consecutive offset errors → STOP Reading that file. Never guess offsets — `grep -n '<anchor>'` first.
+11. **Read offset safety (BLOCKING)** — If Read returns "shorter than offset"/"File is empty"/"Wasted call" — do NOT retry same offset. Use the platform file-reading tool to refresh bounded line information, or locate an anchor with `{{RUNTIME_HELPER_CMD}} text search <file> --pattern "<anchor>" --json` before reading a small bounded range. 2 consecutive offset errors → STOP Reading that file. Never guess offsets or prescribe POSIX-only lookup commands.

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

@@ -6,10 +6,8 @@ You MUST attempt this phase. Mark it as skipped only when no usable browser tool
 
 0a. Check which browser tools are available:
 ```bash
-echo "=== playwright-cli ==="
-which playwright-cli 2>/dev/null && playwright-cli --version 2>/dev/null || echo "PLAYWRIGHT_CLI:NOT_INSTALLED"
-echo "=== opencli ==="
-which opencli 2>/dev/null && opencli --version 2>/dev/null || echo "OPENCLI:NOT_INSTALLED"
+{{RUNTIME_HELPER_CMD}} executable version playwright-cli --arg=--version
+{{RUNTIME_HELPER_CMD}} executable version opencli --arg=--version
 ```
 
 0b. Use this single decision tree:
@@ -18,19 +16,15 @@ which opencli 2>/dev/null && opencli --version 2>/dev/null || echo "OPENCLI:NOT_
 3. Else install `playwright-cli` as the default:
    ```bash
    npm install -g @playwright/cli@latest
-   playwright-cli --version
+   {{RUNTIME_HELPER_CMD}} executable version playwright-cli --arg=--version
    ```
 4. If no browser tool is usable after these steps, append `## Browser Verification: SKIPPED — no usable browser tool` to `context-snapshot.md`, then continue to reporting/checkpoint.
 
 Use `opencli` instead of `playwright-cli` only when the scenario requires an existing Chrome login/session or third-party integration cookies.
 
-Record your choice:
-```bash
-BROWSER_TOOL="playwright-cli"   # or "opencli" or "skipped"
-echo "Selected browser tool: $BROWSER_TOOL"
-```
+Record your choice in the Browser Verification report as `Tool: playwright-cli`, `Tool: opencli`, or `Tool: skipped`.
 
-If `BROWSER_TOOL="skipped"`, do NOT start a dev server and do NOT run browser commands. Go directly to Step 4 Reporting and the checkpoint update.
+If tool is `skipped`, do NOT start a dev server and do NOT run browser commands. Go directly to Step 4 Reporting and the checkpoint update.
 
 ---
 
@@ -38,27 +32,15 @@ If `BROWSER_TOOL="skipped"`, do NOT start a dev server and do NOT run browser co
 
 0d. Check if playwright-cli skill is installed for the current AI platform:
 ```bash
-CURRENT_PLATFORM=""
-if which claude >/dev/null 2>&1; then
-  CURRENT_PLATFORM="claude"; SKILL_DIR="$HOME/.claude/skills"
-elif which cbc >/dev/null 2>&1; then
-  CURRENT_PLATFORM="codebuddy"; SKILL_DIR="$HOME/.cbc/skills"
-else
-  CURRENT_PLATFORM="unknown"
-fi
-if [ -d "$SKILL_DIR/playwright-cli" ] || ls "$SKILL_DIR"/playwright* 2>/dev/null | grep -q .; then
-  echo "SKILL_EXISTS"
-else
-  echo "SKILL_MISSING"
-fi
+{{RUNTIME_HELPER_CMD}} platform skill playwright-cli --prefix
 ```
-If `SKILL_MISSING`: run `playwright-cli install --skills`. If current platform is NOT claude, copy installed skill from `$HOME/.claude/skills/playwright-cli` to `$SKILL_DIR/playwright-cli`.
+If `SKILL_MISSING`: run `playwright-cli install --skills`. If current platform is NOT claude, copy the installed skill from the Claude user skills directory to the path shown by the helper output for the current platform.
 
 0e. Read the installed playwright-cli skill (SKILL.md) for workflow guidance. Learn usage: `playwright-cli --help`.
 
 **Step 1 — Start Dev Server + Open (playwright-cli)**:
-1. Identify and start the dev server (see port detection below)
-2. Open: `playwright-cli open http://localhost:$DEV_PORT`
+1. Identify and start the dev server (see shared helper commands below)
+2. Open: `playwright-cli open http://localhost:<DEV_PORT>`
 3. If auth needed, use playwright-cli to register a test user and log in
 
 **Step 2 — Verification (playwright-cli)**:
@@ -69,18 +51,19 @@ Construct your verification workflow based on: (1) the playwright-cli skill docu
 
 **Step 3 — Cleanup (playwright-cli)**:
 1. `playwright-cli close`
-2. `kill $DEV_SERVER_PID 2>/dev/null || true`
-3. `lsof -ti:$DEV_PORT | xargs kill -9 2>/dev/null || true`
+2. `{{RUNTIME_HELPER_CMD}} process cleanup-pid <pid-from-.prizmkit/state/browser-dev-server.pid>`
+3. `{{RUNTIME_HELPER_CMD}} port check <DEV_PORT>`
 
 ---
 
 **If you chose `opencli`**, follow this workflow:
 
-0d. Learn usage: `opencli browser --help 2>/dev/null || opencli --help`
+0d. Learn usage: `opencli browser --help`
 
 **Step 1 — Start Dev Server + Open (opencli)**:
-1. Identify and start the dev server (see port detection below)
-2. Open and inspect: `opencli browser open http://localhost:$DEV_PORT && opencli browser state`
+1. Identify and start the dev server (see shared helper commands below)
+2. Open: `opencli browser open http://localhost:<DEV_PORT>`
+3. Inspect: `opencli browser state`
 3. If auth needed, opencli reuses Chrome cookies — SSO/OAuth may already be active
 
 **Step 2 — Verification (opencli)**:
@@ -89,36 +72,32 @@ Use `opencli browser state` to discover elements with `[N]` indices, then verify
 
 Key commands: `state`, `click <N>`, `type <N> "text"`, `get text <N>`, `get value <N>`, `wait text "..."`, `wait selector "..."`, `scroll down`, `eval "(function(){ ... })()"`.
 
-**Chain commands with `&&`**: `opencli browser type 3 "hello" && opencli browser click 7`
+Run page-changing commands sequentially; for example, run `opencli browser type 3 "hello"`, then run `opencli browser click 7`.
 
 Always run `state` after page-changing actions to get fresh indices.
 
 **Step 3 — Cleanup (opencli)**:
 1. `opencli browser close`
-2. `kill $DEV_SERVER_PID 2>/dev/null || true`
-3. `lsof -ti:$DEV_PORT | xargs kill -9 2>/dev/null || true`
+2. `{{RUNTIME_HELPER_CMD}} process cleanup-pid <pid-from-.prizmkit/state/browser-dev-server.pid>`
+3. `{{RUNTIME_HELPER_CMD}} port check <DEV_PORT>`
 
 ---
 
-**Shared: Dev Server Port Detection** (used by both tools):
-
-```bash
-DEV_PORT={{DEV_PORT}}
-if [ "$DEV_PORT" = "{{DEV_PORT}}" ]; then
-  DEV_PORT=$(node -e "const s=require('./package.json').scripts.dev; const m=s.match(/-p\s+(\d+)/); console.log(m?m[1]:'')")
-  if [ -z "$DEV_PORT" ]; then
-    DEV_PORT=$(echo "$NEXT_PUBLIC_SITE_URL" | sed -nE 's|.*:([0-9]+).*|\1|p')
-  fi
-  DEV_PORT=${DEV_PORT:-3000}
-fi
-echo "Detected DEV_PORT=$DEV_PORT"
-```
-
-Verify port available: `lsof -ti:$DEV_PORT 2>/dev/null && echo "PORT_IN_USE" || echo "PORT_FREE"`
-
-Start dev server: `<start-command> & DEV_SERVER_PID=$!`
+**Shared: Dev Server Port / Process Helpers** (used by both tools):
 
-Wait for ready: poll `http://localhost:$DEV_PORT` with `curl -s -o /dev/null -w "%{http_code}"` until 200/302 (max 30s, 2s interval).
+1. Determine `DEV_PORT` from the pipeline value (`{{DEV_PORT}}`) or project config; do not guess.
+2. Verify port available:
+   ```bash
+   {{RUNTIME_HELPER_CMD}} port check <DEV_PORT>
+   ```
+3. Start dev server:
+   ```bash
+   {{RUNTIME_HELPER_CMD}} process start --pid-file .prizmkit/state/browser-dev-server.pid -- <start-command tokens>
+   ```
+4. Wait for ready:
+   ```bash
+   {{RUNTIME_HELPER_CMD}} web wait-ready --url http://localhost:<DEV_PORT> --timeout 30 --interval 2
+   ```
 
 ---
 
@@ -128,7 +107,7 @@ Append results to `context-snapshot.md`:
    ```
    ## Browser Verification
    Tool: <playwright-cli or opencli>
-   URL: http://localhost:$DEV_PORT
+   URL: http://localhost:<DEV_PORT>
    Dev Server Command: <actual command used>
    Tool version: <version>
    Steps executed: [list of commands used]
@@ -140,4 +119,3 @@ Append results to `context-snapshot.md`:
 
 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.
 
-

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

@@ -12,13 +12,13 @@ You MUST execute this phase. Do NOT skip it. Do NOT mark it as completed without
 
 0a. Check if `opencli` is installed:
 ```bash
-which opencli 2>/dev/null && opencli --version 2>/dev/null || echo "NOT_INSTALLED"
+{{RUNTIME_HELPER_CMD}} executable version opencli --arg=--version
 ```
 If output is `NOT_INSTALLED`, install it:
 ```bash
 npm install -g @jackwener/opencli@latest
 ```
-Then verify installation succeeded: `opencli --version`. If installation fails, log `## Browser Verification: SKIPPED — opencli installation failed` in context-snapshot.md and proceed to the next phase.
+Then verify installation succeeded: `{{RUNTIME_HELPER_CMD}} executable version opencli --arg=--version`. If installation fails, log `## Browser Verification: SKIPPED — opencli installation failed` in context-snapshot.md and proceed to the next phase.
 
 0b. Verify Browser Bridge connectivity:
 ```bash
@@ -28,7 +28,7 @@ If `opencli doctor` fails (Chrome not running or extension not installed), log `
 
 0c. Learn opencli browser usage (run once per session):
 ```bash
-opencli browser --help 2>/dev/null || opencli --help
+opencli browser --help
 ```
 
 **Step 1 — Start Dev Server**:
@@ -36,31 +36,23 @@ opencli browser --help 2>/dev/null || opencli --help
 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:
+2. Determine the dev server port from the pre-detected pipeline value (`{{DEV_PORT}}`) or project config. Do NOT hardcode or guess the port. Record it as `DEV_PORT` in your notes.
+3. Verify the port is available:
    ```bash
-   DEV_PORT={{DEV_PORT}}
-   if [ "$DEV_PORT" = "{{DEV_PORT}}" ]; then
-     DEV_PORT=$(node -e "const s=require('./package.json').scripts.dev; const m=s.match(/-p\s+(\d+)/); console.log(m?m[1]:'')")
-     if [ -z "$DEV_PORT" ]; then
-       DEV_PORT=$(echo "$NEXT_PUBLIC_SITE_URL" | sed -nE 's|.*:([0-9]+).*|\1|p')
-     fi
-     DEV_PORT=${DEV_PORT:-3000}
-   fi
-   echo "Detected DEV_PORT=$DEV_PORT"
+   {{RUNTIME_HELPER_CMD}} port check <DEV_PORT>
    ```
-3. Verify the port is available:
+4. Start the dev server with the runtime helper and capture a PID file:
    ```bash
-   lsof -ti:$DEV_PORT 2>/dev/null && echo "PORT_IN_USE" || echo "PORT_FREE"
+   {{RUNTIME_HELPER_CMD}} process start --pid-file .prizmkit/state/browser-dev-server.pid -- <start-command tokens>
    ```
-4. Start the dev server in background, capture PID:
+5. Wait for server to be ready:
    ```bash
-   <start-command> &
-   DEV_SERVER_PID=$!
+   {{RUNTIME_HELPER_CMD}} web wait-ready --url http://localhost:<DEV_PORT> --timeout 30 --interval 2
    ```
-5. Wait for server to be ready: poll `http://localhost:$DEV_PORT` with `curl -s -o /dev/null -w "%{http_code}"` until it returns 200 or 302 (max 30 seconds, 2s interval)
 6. Open the app in opencli and inspect page state:
    ```bash
-   opencli browser open http://localhost:$DEV_PORT && opencli browser state
+   opencli browser open http://localhost:<DEV_PORT>
+   opencli browser state
    ```
 7. If the page requires authentication, use opencli browser to interact with login forms (opencli reuses Chrome cookies, so SSO/OAuth may already be active)
 
@@ -80,16 +72,14 @@ Key opencli browser commands for verification:
 - `opencli browser scroll down` — scroll page
 - `opencli browser eval "(function(){ ... })()"` — read-only JS evaluation for data extraction
 
-**Chain commands aggressively with `&&`** to minimize tool calls:
+**Run commands sequentially and refresh state after page-changing actions**:
 ```bash
-# GOOD: open + inspect in one call
-opencli browser open http://localhost:$DEV_PORT && opencli browser state
-
-# GOOD: fill form in one call
-opencli browser type 3 "hello" && opencli browser type 4 "world" && opencli browser click 7
-
-# GOOD: click + wait + re-inspect
-opencli browser click 12 && opencli browser wait time 1 && opencli browser state
+opencli browser open http://localhost:<DEV_PORT>
+opencli browser state
+opencli browser type 3 "hello"
+opencli browser type 4 "world"
+opencli browser click 7
+opencli browser state
 ```
 
 **IMPORTANT**: Always run `opencli browser state` after page-changing actions (open, click on links, scroll) to get fresh element indices. Never guess indices.
@@ -99,8 +89,14 @@ Construct your verification workflow based on: (1) the `opencli browser --help`
 **Step 3 — Cleanup (REQUIRED — you started it, you stop it)**:
 
 1. Close the opencli browser session: `opencli browser close`
-2. Kill the dev server process: `kill $DEV_SERVER_PID 2>/dev/null || true`
-3. Verify port is released: `lsof -ti:$DEV_PORT | xargs kill -9 2>/dev/null || true`
+2. Stop the dev server process using the PID file written in Step 1:
+   ```bash
+   {{RUNTIME_HELPER_CMD}} process cleanup-pid <pid-from-.prizmkit/state/browser-dev-server.pid>
+   ```
+3. Verify port is released:
+   ```bash
+   {{RUNTIME_HELPER_CMD}} port check <DEV_PORT>
+   ```
 
 **Step 4 — Reporting**:
 
@@ -108,7 +104,7 @@ Append results to `context-snapshot.md`:
    ```
    ## Browser Verification
    Tool: opencli
-   URL: http://localhost:$DEV_PORT
+   URL: http://localhost:<DEV_PORT>
    Dev Server Command: <actual command used>
    opencli version: <version>
    Steps executed: [list of opencli browser commands used]
@@ -120,4 +116,3 @@ Append results to `context-snapshot.md`:
 
 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.
 
-

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

@@ -10,9 +10,9 @@ You MUST execute this phase. Do NOT skip it. Do NOT mark it as completed without
 
 **Step 0 — Playwright CLI Readiness Check (BLOCKING — must pass before any browser action)**:
 
-0a. Check if `playwright-cli` is installed:
+0a. Check if `playwright-cli` is installed using the runtime helper:
 ```bash
-which playwright-cli 2>/dev/null && playwright-cli --version 2>/dev/null || echo "NOT_INSTALLED"
+{{RUNTIME_HELPER_CMD}} executable version playwright-cli --arg=--version
 ```
 If output is `NOT_INSTALLED`, install it:
 ```bash
@@ -20,7 +20,7 @@ npm install -g @playwright/cli@latest
 ```
 Then verify installation succeeded:
 ```bash
-playwright-cli --version
+{{RUNTIME_HELPER_CMD}} executable version playwright-cli --arg=--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.
 
@@ -32,43 +32,9 @@ Use this output to determine the correct commands for your verification steps. D
 
 0c. Check if playwright-cli skill is installed for the current AI platform:
 ```bash
-# Detect AI CLI platform
-CURRENT_PLATFORM=""
-if which claude >/dev/null 2>&1; then
-  CURRENT_PLATFORM="claude"
-  SKILL_DIR="$HOME/.claude/skills"
-elif which cbc >/dev/null 2>&1; then
-  CURRENT_PLATFORM="codebuddy"
-  SKILL_DIR="$HOME/.cbc/skills"
-else
-  # Try to detect from environment or config
-  CURRENT_PLATFORM="unknown"
-fi
-
-# Check if playwright-cli skill exists
-if [ -d "$SKILL_DIR/playwright-cli" ] || ls "$SKILL_DIR"/playwright* 2>/dev/null | grep -q .; then
-  echo "SKILL_EXISTS"
-else
-  echo "SKILL_MISSING"
-fi
-```
-If `SKILL_MISSING`:
-```bash
-# Install playwright-cli skills (defaults to claude platform)
-playwright-cli install --skills
-```
-If the current platform is NOT claude, move the installed skill files to the correct location:
-```bash
-# Skills are installed to claude's default location — move to current platform's skill dir
-if [ "$CURRENT_PLATFORM" != "claude" ] && [ "$CURRENT_PLATFORM" != "unknown" ]; then
-  CLAUDE_SKILL_DIR="$HOME/.claude/skills"
-  if [ -d "$CLAUDE_SKILL_DIR/playwright-cli" ]; then
-    mkdir -p "$SKILL_DIR"
-    cp -r "$CLAUDE_SKILL_DIR/playwright-cli" "$SKILL_DIR/"
-    echo "Moved playwright-cli skill from claude to $CURRENT_PLATFORM"
-  fi
-fi
+{{RUNTIME_HELPER_CMD}} platform skill playwright-cli --prefix
 ```
+If `SKILL_MISSING`: run `playwright-cli install --skills`. If current platform is NOT claude, copy the installed skill from the Claude user skills directory to the path shown by the helper output for the current platform.
 
 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.
@@ -78,31 +44,20 @@ After skill installation, read the skill's SKILL.md to understand recommended wo
 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:
+2. Use the pre-detected port if available, otherwise determine the dev server port from project config. Do NOT hardcode or guess the port. Record it as `DEV_PORT` in your notes.
+3. Verify the port is available:
    ```bash
-   # Use pipeline-injected port if available, otherwise extract from package.json
-   DEV_PORT={{DEV_PORT}}
-   # If DEV_PORT is still a placeholder, detect at runtime:
-   if [ "$DEV_PORT" = "{{DEV_PORT}}" ]; then
-     DEV_PORT=$(node -e "const s=require('./package.json').scripts.dev; const m=s.match(/-p\s+(\d+)/); console.log(m?m[1]:'')")
-     if [ -z "$DEV_PORT" ]; then
-       DEV_PORT=$(echo "$NEXT_PUBLIC_SITE_URL" | sed -nE 's|.*:([0-9]+).*|\1|p')
-     fi
-     DEV_PORT=${DEV_PORT:-3000}
-   fi
-   echo "Detected DEV_PORT=$DEV_PORT"
+   {{RUNTIME_HELPER_CMD}} port check {{DEV_PORT}}
    ```
-3. Verify the port is available:
+4. Start the dev server with the runtime helper and capture a PID file:
    ```bash
-   lsof -ti:$DEV_PORT 2>/dev/null && echo "PORT_IN_USE" || echo "PORT_FREE"
+   {{RUNTIME_HELPER_CMD}} process start --pid-file .prizmkit/state/browser-dev-server.pid -- <start-command tokens>
    ```
-4. Start the dev server in background, capture PID:
+5. Wait for server to be ready:
    ```bash
-   <start-command> &
-   DEV_SERVER_PID=$!
+   {{RUNTIME_HELPER_CMD}} web wait-ready --url http://localhost:{{DEV_PORT}} --timeout 30 --interval 2
    ```
-5. Wait for server to be ready: poll `http://localhost:$DEV_PORT` with `curl -s -o /dev/null -w "%{http_code}"` until it returns 200 or 302 (max 30 seconds, 2s interval)
-6. Open the app in playwright-cli: `playwright-cli open http://localhost:$DEV_PORT`
+6. Open the app in playwright-cli: `playwright-cli open http://localhost:{{DEV_PORT}}`
 7. If the page requires authentication, use playwright-cli to register a test user and log in first
 
 **Step 2 — Verification**:
@@ -122,15 +77,21 @@ 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. Kill the dev server process: `kill $DEV_SERVER_PID 2>/dev/null || true`
-3. Verify port is released: `lsof -ti:$DEV_PORT | xargs kill -9 2>/dev/null || true`
+2. Stop the dev server process using the PID file written in Step 1:
+   ```bash
+   {{RUNTIME_HELPER_CMD}} process cleanup-pid <pid-from-.prizmkit/state/browser-dev-server.pid>
+   ```
+3. Verify port is released:
+   ```bash
+   {{RUNTIME_HELPER_CMD}} port check {{DEV_PORT}}
+   ```
 
 **Step 4 — Reporting**:
 
 Append results to `context-snapshot.md`:
 ```
 ## Browser Verification
-URL: http://localhost:$DEV_PORT
+URL: http://localhost:<DEV_PORT>
 Dev Server Command: <actual command used>
 playwright-cli version: <version>
 Steps executed: [list of playwright-cli commands used]
@@ -142,4 +103,3 @@ 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.
 
-

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

@@ -2,7 +2,7 @@
 
 **a.** Check if feature already committed:
 ```bash
-git log --oneline | grep "{{FEATURE_ID}}" | head -3
+git log --oneline
 ```
 - 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.
@@ -30,7 +30,7 @@ This single commit includes: feature code + tests + .prizmkit/prizm-docs/ update
 ```bash
 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> && git commit --amend --no-edit`, do NOT create a separate commit.
+Working tree MUST be clean after this step. If any feature-related files remain, stage them explicitly and amend the SAME commit with `git commit --amend --no-edit`; do NOT create a separate commit.
 
 **f.** Write completion summary for downstream dependency context:
 

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

@@ -23,7 +23,7 @@ This single commit includes: feature code + tests + .prizmkit/prizm-docs/ update
 ```bash
 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> && git commit --amend --no-edit`, do NOT create a separate commit.
+Working tree MUST be clean after this step. If any feature-related files remain, stage them explicitly and amend the SAME commit with `git commit --amend --no-edit`; do NOT create a separate commit.
 
 **e.** Write completion summary for downstream dependency context:
 

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

@@ -1,7 +1,7 @@
 ### Build Context Snapshot
 
 ```bash
-ls .prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md 2>/dev/null && echo "EXISTS" || echo "MISSING"
+{{RUNTIME_HELPER_CMD}} artifact exists .prizmkit/specs/{{FEATURE_SLUG}}/context-snapshot.md
 ```
 
 If MISSING — build it now:

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

@@ -2,7 +2,7 @@
 
 **Guard**: Verify critic agent file exists before spawning:
 ```bash
-ls {{CRITIC_SUBAGENT_PATH}} 2>/dev/null && echo "CRITIC:READY" || echo "CRITIC:MISSING"
+{{RUNTIME_HELPER_CMD}} artifact exists {{CRITIC_SUBAGENT_PATH}} --exists-marker CRITIC:READY --missing-marker CRITIC:MISSING
 ```
 If CRITIC:MISSING — skip this phase entirely and proceed. Log: "Critic agent not installed — skipping Plan Challenge."
 

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

@@ -2,7 +2,7 @@
 
 **Guard**: Verify critic agent file exists before spawning:
 ```bash
-ls {{CRITIC_SUBAGENT_PATH}} 2>/dev/null && echo "CRITIC:READY" || echo "CRITIC:MISSING"
+{{RUNTIME_HELPER_CMD}} artifact exists {{CRITIC_SUBAGENT_PATH}} --exists-marker CRITIC:READY --missing-marker CRITIC:MISSING
 ```
 If CRITIC:MISSING — skip this phase entirely and proceed. Log: "Critic agent not installed — skipping Plan Challenge."
 

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

@@ -4,7 +4,7 @@
 
 Before starting, check plan.md Tasks:
 ```bash
-grep -c '^\- \[ \]' .prizmkit/specs/{{FEATURE_SLUG}}/plan.md 2>/dev/null || true
+{{RUNTIME_HELPER_CMD}} text count .prizmkit/specs/{{FEATURE_SLUG}}/plan.md --pattern "- [ ]"
 ```
 - If result is `0` (all tasks already `[x]`) → **SKIP to Review**.
 - If non-zero → implement directly below.

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

@@ -4,7 +4,7 @@
 
 Before starting, check plan.md Tasks:
 ```bash
-grep -c '^\- \[ \]' .prizmkit/specs/{{FEATURE_SLUG}}/plan.md 2>/dev/null || true
+{{RUNTIME_HELPER_CMD}} text count .prizmkit/specs/{{FEATURE_SLUG}}/plan.md --pattern "- [ ]"
 ```
 - If result is `0` (all tasks already `[x]`) → **SKIP to Review**.
 - If non-zero → implement directly below.

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

@@ -1,7 +1,7 @@
 ### Plan & Tasks
 
 ```bash
-ls .prizmkit/specs/{{FEATURE_SLUG}}/plan.md 2>/dev/null
+{{RUNTIME_HELPER_CMD}} artifact exists .prizmkit/specs/{{FEATURE_SLUG}}/plan.md
 ```
 
 If missing, run `/prizmkit-plan` with `artifact_dir=.prizmkit/specs/{{FEATURE_SLUG}}/` to generate `plan.md`:

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

@@ -1,7 +1,7 @@
 ### Plan & Tasks
 
 ```bash
-ls .prizmkit/specs/{{FEATURE_SLUG}}/ 2>/dev/null
+{{RUNTIME_HELPER_CMD}} artifact exists .prizmkit/specs/{{FEATURE_SLUG}}
 ```
 
 If plan.md missing, run `/prizmkit-plan` with `artifact_dir=.prizmkit/specs/{{FEATURE_SLUG}}/`:

package/bundled/dev-pipeline/templates/sections/phase-prizmkit-test.md

@@ -5,8 +5,8 @@
 Create a current-run marker immediately before invoking the skill:
 
 ```bash
-mkdir -p .prizmkit/specs/{{FEATURE_SLUG}}
-touch .prizmkit/specs/{{FEATURE_SLUG}}/.prizmkit-test-started
+{{RUNTIME_HELPER_CMD}} artifact ensure-dir .prizmkit/specs/{{FEATURE_SLUG}}
+{{RUNTIME_HELPER_CMD}} artifact touch .prizmkit/specs/{{FEATURE_SLUG}}/.prizmkit-test-started
 ```
 
 Run `/prizmkit-test` with the feature artifact directory:

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

@@ -9,7 +9,7 @@ The skill runs an internal review-fix loop (Reviewer Agent → filter → orches
 **Gate Check — Review Report**:
 After `/prizmkit-code-review` returns, verify the review report:
 ```bash
-grep -q "## Verdict" .prizmkit/specs/{{FEATURE_SLUG}}/review-report.md && echo "GATE:PASS" || echo "GATE:MISSING"
+{{RUNTIME_HELPER_CMD}} text contains .prizmkit/specs/{{FEATURE_SLUG}}/review-report.md --pattern "## Verdict"
 ```
 If GATE:MISSING:
 - Do not re-run `/prizmkit-code-review` in an unbounded report-repair loop.