@osfactory/har 0.10.0 → 0.12.0

package/dist/templates/agent-skills/har-maintain.md

@@ -14,6 +14,8 @@ This compares the harness against the current templates and repository, refreshe
 
 Read `.har/ADAPT-PROMPT.md` and execute its instructions now, in this session: reconcile `.har/` scripts (`launch.sh`, `verify.sh`, `setup-infra.sh`, `harness.env`, `stages.json`) and `AGENT.md` with the repository's current stack, ports, and commands. Preserve intentional project-specific customizations — fix drift, don't blindly reset.
 
+Also check stage drift: compare the repository's current check commands (package.json scripts, Makefile, CI) against the stages registered in `.har/stages.json`. Register missing checks (`har env add-stage <id> --custom --command "..." --verification`), and remove or fix stages whose commands no longer exist. `.har/STAGES.md` documents the contract.
+
 ## 3. Finalize and prove it works
 
 ```bash

package/dist/templates/agent-skills/setup-har.md

@@ -38,7 +38,18 @@ If `.har/` already exists, stop and suggest `/har-maintain` instead.
 
 `har env init` prints an adaptation prompt and writes it to `.har/ADAPT-PROMPT.md`. Read that file and **execute its instructions yourself, now, in this session** — tailor `.har/` scripts (`launch.sh`, `verify.sh`, `setup-infra.sh`, `harness.env`, `stages.json`) and `AGENT.md` to this repository's real stack, ports, and commands. Do not use `--auto` and do not ask the user to paste anything.
 
-## 5. Prove the harness works
+## 5. Register the project's checks as stages
+
+Convert the repository's real check commands (test, lint, typecheck, whatever CI runs) into registered stages so they run in `verify --full` and are visible to every agent. Read `.har/STAGES.md` for the contract, then:
+
+```bash
+har env add-stage unit-tests --custom --kind test --command "npm test" --verification
+```
+
+- Use `--command` for one-liner checks; use `--script` when a check needs the slot's env, ports, or artifacts (then implement the scaffolded `.har/stages/<id>.sh`).
+- Rich integrations ship as templates: `har env add-stage --list`, then e.g. `har env add-stage playwright` (web) or `har env add-stage rocketsim` (iOS).
+
+## 6. Prove the harness works
 
 ```bash
 har env launch 1
@@ -47,7 +58,7 @@ har env verify 1
 
 Fix the harness scripts until both pass. Then tear down or keep the slot as the user prefers (`har env teardown 1` keeps the branch).
 
-## 6. Commit
+## 7. Commit
 
 After the user confirms, commit the harness:
 

package/dist/templates/har-boilerplate/CLAUDE.agent.md

@@ -39,13 +39,15 @@ is alive; it does not automatically mean an agent can use the app.
 
 - [ ] Full verification returns `"status": "pass"` (`har env verify ${AGENT_ID} --full`, MCP `har_run_verification` with `full: true`, or `./.har/verify.sh ${AGENT_ID} --full`)
 - [ ] The slot is agent-usable for this repo's documented smoke workflow, not only health-check green
-- [ ] When `stages/browser-e2e.sh` exists, full verify includes Playwright — adapt specs under `tests/` for UI changes
+- [ ] Full verify runs every registered stage in `stages.json` `verificationStages` (Playwright, custom checks, …) — when `stages/browser-e2e.sh` exists, adapt specs under `tests/` for UI changes
 - [ ] New behavior has automated test coverage (unit and/or browser as appropriate)
 - [ ] Changes committed **in the session worktree** with a clear message
 - [ ] The user got the preview URLs to test the app themselves
 - [ ] Finish with `har env complete ${AGENT_ID}` (or MCP `har_complete_environment`) — records the validation and tears down while **keeping the session branch** for the user to push / open a PR
 
-Quick loop during development: MCP `har_run_verification`, `har env verify ${AGENT_ID}`, or `./.har/verify.sh ${AGENT_ID}` (stops before lint and browser-e2e).
+Quick loop during development: MCP `har_run_verification`, `har env verify ${AGENT_ID}`, or `./.har/verify.sh ${AGENT_ID}` (smoke + health only; `--full` adds the registered verification stages).
+
+Stages are the harness's single vocabulary for checks: templates and custom stages compile to generic kinds in `.har/stages.json`, and you interact with them only through the registry (`har_run_stage`, `verify`), never stack-specific tooling. Authoring guide: `.har/STAGES.md`.
 
 ## Project commands
 

package/dist/templates/har-boilerplate/STAGES.md

@@ -0,0 +1,91 @@
+# HAR Stages — authoring guide
+
+Stages are the harness's single vocabulary for runnable checks and lifecycle
+actions. Everything — shipped templates (`playwright`, `rocketsim`), your
+project's test/lint commands, bespoke validation scripts — registers in
+`.har/stages.json` with the same schema, and agents interact with stages only
+through that registry (CLI `har env verify`, MCP `har_run_stage` /
+`har_run_verification`), never through stack-specific tooling.
+
+## The registry: `.har/stages.json`
+
+```jsonc
+{
+  "verificationStages": ["typecheck", "unit-tests", "api-health", "browser-e2e"],
+  "stages": [
+    {
+      "id": "browser-e2e",              // stable, shell-friendly slug
+      "kind": "test",                   // setup | launch | verify | test | inspect | reset | teardown | custom
+      "description": "Playwright E2E",
+      "script": "stages/browser-e2e.sh", // relative to .har/ — OR use "command"
+      "requiresAgentId": true,           // default true for test/verify/custom kinds
+      "artifacts": [{ "path": ".har/artifacts/browser-e2e", "kind": "directory" }]
+    },
+    {
+      "id": "unit-tests-fast",
+      "kind": "test",
+      "command": "npm test -- --agent {agentId}"   // {agentId} is substituted at run time
+    }
+  ]
+}
+```
+
+Optional stage fields: `cwd` (working directory), `env` (extra env vars),
+`group`, `acceptsArgs` (extra CLI args the stage accepts, e.g. `["--full"]`).
+
+## Two ways to define a stage
+
+**Command stages** — the default for simple checks (`npm test`, `swiftlint`,
+`make check`). One JSON entry, zero files:
+
+```bash
+har env add-stage unit-tests-fast --custom --kind test --command "npm test" --verification
+```
+
+**Script stages** — for anything that needs the slot's env, ports, or
+artifacts. Scaffold a contract-compliant skeleton:
+
+```bash
+har env add-stage db-integrity --custom --script --description "Check DB invariants"
+```
+
+then implement the TODO block in `.har/stages/db-integrity.sh`.
+
+## The stage script contract
+
+Every script under `.har/stages/` must:
+
+1. Source `harness.env` and `agent-slot.sh` from `.har/`.
+2. Take the agent slot id as `$1` (validate with `validate_agent_id`); extra
+   args may follow.
+3. Load the slot env via `resolve_agent_env_file` and run checks from the
+   agent's work dir (`resolve_agent_work_dir`).
+4. Write artifacts (reports, screenshots, logs) under `.har/artifacts/<id>/`.
+5. Print **only** the normalized JSON result object on stdout
+   (`status`, `stageId`, `agent_id`, `total_ms`, …); log progress to stderr.
+6. Exit with the real status code (0 = pass).
+
+The scaffolded skeleton implements all of this — replace its TODO block.
+
+## Verification membership
+
+Listing a stage id in `verificationStages` is what includes it in
+`har env verify <id> --full`. Ids that match a registered stage run via their
+script/command; ids without a registry entry (e.g. `typecheck`, `api-health`)
+are inline steps owned by `.har/verify.sh`. Lifecycle kinds
+(`setup`/`launch`/`reset`/`teardown`/`inspect`) and `verify` itself never run
+as part of verification, even if listed.
+
+## Commit gate
+
+The registry also holds the optional `commitGate` config (installed via
+`har hooks install`): `{ "commitGate": { "mode": "block" | "warn", "scope":
+"worktrees" | "all" } }` controls whether unverified change batches may be
+committed.
+
+## Shipped stage templates
+
+`har env add-stage --list` shows available templates; `har env add-stage
+playwright` (web) or `har env add-stage rocketsim` (iOS) installs one. A
+template is just packaging: it copies files, merges `package.json` fragments,
+and registers stages through the exact same registry as `--custom`.

package/dist/templates/har-boilerplate/agent-slot.sh

@@ -273,6 +273,17 @@ har_regenerate_agent_env_file() {
   REPO_ROOT="$work_dir" \
     envsubst '${AGENT_ID} ${API_PORT} ${FE_PORT} ${DEBUG_PORT} ${DB_PORT} ${MINIO_PORT} ${BROWSER_PORT} ${REPO_ROOT}' \
     < "$template" > "$env_file"
+  if command -v har >/dev/null 2>&1; then
+    har telemetry write-env \
+      --agent-id "$agent_id" \
+      --repo "${HARNESS_ROOT:-$REPO_ROOT}" \
+      --env-file "$env_file" \
+      --work-dir "$work_dir" \
+      ${SLOT_BRANCH:+--branch "$SLOT_BRANCH"} \
+      ${SLOT_SUFFIX:+--suffix "$SLOT_SUFFIX"} \
+      ${SLOT_PURPOSE:+--purpose "$SLOT_PURPOSE"} \
+      >/dev/null 2>&1 || true
+  fi
 }
 
 # har_launch_preflight <agent_id> <force> <replace> [resume]
@@ -662,14 +673,43 @@ escape_step_output() {
   printf '%s' "$1" | node -e "let d='';process.stdin.on('data',c=>d+=c);process.stdin.on('end',()=>{const s=d.trim().split('\n').slice(0,50).join('\n');process.stdout.write(JSON.stringify(s))})" 2>/dev/null || echo '""'
 }
 
-# Run browser-e2e on verify --full when the Playwright stage template is installed.
-run_browser_e2e_if_present() {
+# Emit "<id>\t<command>" for each registered stage listed in stages.json
+# verificationStages (used by verify --full). Ids without a matching registered
+# stage are inline verify.sh steps and skipped here; lifecycle stages
+# (setup/launch/reset/teardown/inspect) and the verify stage itself never run.
+# Authoring contract: .har/STAGES.md
+list_registered_verification_stage_commands() {
   local script_dir="$1"
   local agent_id="$2"
-  local e2e="$script_dir/stages/browser-e2e.sh"
-  if [ -x "$e2e" ]; then
-    "$e2e" "$agent_id"
-  fi
+  local registry="$script_dir/stages.json"
+  [ -f "$registry" ] || return 0
+  HAR_STAGE_REGISTRY="$registry" HAR_SCRIPT_DIR="$script_dir" HAR_AGENT_ID="$agent_id" node <<'NODE' 2>/dev/null || true
+const fs = require('fs');
+const { HAR_STAGE_REGISTRY, HAR_SCRIPT_DIR, HAR_AGENT_ID } = process.env;
+const shq = (s) => "'" + String(s).replace(/'/g, "'\\''") + "'";
+let reg;
+try { reg = JSON.parse(fs.readFileSync(HAR_STAGE_REGISTRY, 'utf8')); } catch { process.exit(0); }
+const ids = Array.isArray(reg.verificationStages) ? reg.verificationStages : [];
+const stages = Array.isArray(reg.stages) ? reg.stages : [];
+const runnable = new Set(['test', 'custom']);
+for (const id of ids) {
+  const stage = stages.find((s) => s && s.id === id);
+  if (!stage || stage.id === 'verify' || !runnable.has(stage.kind)) continue;
+  const needsAgent = stage.requiresAgentId !== false;
+  let cmd;
+  if (stage.script) {
+    cmd = shq(HAR_SCRIPT_DIR + '/' + stage.script) + (needsAgent ? ' ' + shq(HAR_AGENT_ID) : '');
+  } else if (stage.command) {
+    cmd = stage.command.split('{agentId}').join(HAR_AGENT_ID);
+  } else {
+    continue;
+  }
+  if (stage.cwd) cmd = 'cd ' + shq(stage.cwd) + ' && ' + cmd;
+  const env = stage.env && typeof stage.env === 'object' ? stage.env : {};
+  const prefix = Object.entries(env).map(([k, v]) => k + '=' + shq(v)).join(' ');
+  process.stdout.write(id + '\t' + (prefix ? prefix + ' ' : '') + cmd + '\n');
+}
+NODE
 }
 
 # Optional project-owned "agent usable" smoke beyond health.

package/dist/templates/har-boilerplate/launch.sh

@@ -304,7 +304,8 @@ if [ "$USE_CLAUDE" = true ]; then
   if tmux has-session -t "$TMUX_SESSION" 2>/dev/null; then
     tmux kill-session -t "$TMUX_SESSION"
   fi
-  tmux new-session -d -s "$TMUX_SESSION" -c "$WORK_DIR" "claude"
+  tmux new-session -d -s "$TMUX_SESSION" -c "$WORK_DIR" \
+    "set -a; [ -f '$ENV_FILE' ] && . '$ENV_FILE'; set +a; exec claude"
   log "Claude session: tmux attach -t $TMUX_SESSION"
 fi
 

package/dist/templates/har-boilerplate/stages/README.sh

@@ -1,9 +1,11 @@
 #!/usr/bin/env bash
-# Optional per-stage scripts live here.
-# Example: ./.har/stages/browser-e2e.sh <agent-id>
+# Per-stage scripts live here (e.g. ./.har/stages/browser-e2e.sh <agent-id>).
 #
-# Register custom stages in .har/stages.json with a project-owned command:
-#   "command": "./.har/stages/browser-e2e.sh {agentId}"
+# Read .har/STAGES.md for the authoring guide: the stage script contract,
+# command vs script stages, and how verificationStages controls verify --full.
+#
+# Scaffold a new one with:
+#   har env add-stage <id> --custom --script
 
-echo "Add stage scripts under .har/stages/ and register them in stages.json." >&2
+echo "Add stage scripts under .har/stages/ and register them in stages.json — see .har/STAGES.md." >&2
 exit 1

package/dist/templates/har-boilerplate/verify.sh

@@ -5,7 +5,8 @@
 # Usage: ./.har/verify.sh <agent-id> [--full]
 #
 # Quick (default): ecosystem smoke + health only
-# Full (--full):   + conventional tests, lint, optional readiness + browser-e2e
+# Full (--full):   + conventional tests, lint, readiness, and every registered
+#                  stage in stages.json verificationStages (see .har/STAGES.md)
 # Stock steps are examples. Replace them during adaptation to match this repo.
 set -euo pipefail
 
@@ -229,7 +230,13 @@ run_http_step "api-health" "http://localhost:${API_PORT}${HARNESS_HEALTH_CHECK_P
 if [ -n "$FULL" ]; then
   run_full_checks
   run_step "readiness" "run_readiness_if_configured \"$AGENT_ID\"" || true
-  run_step "browser-e2e" "run_browser_e2e_if_present \"$SCRIPT_DIR\" \"$AGENT_ID\"" || true
+  # Registered verification stages from .har/stages.json (see .har/STAGES.md).
+  # Every stage listed in verificationStages with a registered script/command
+  # runs here -- stage templates and custom stages alike.
+  while IFS=$'\t' read -r STAGE_ID STAGE_CMD; do
+    [ -n "$STAGE_ID" ] || continue
+    run_step "$STAGE_ID" "$STAGE_CMD" || true
+  done < <(list_registered_verification_stage_commands "$SCRIPT_DIR" "$AGENT_ID")
 fi
 
 # ── Output results ────────────────────────────────────────────────────────────

package/dist/templates/har-boilerplate-cli/CLAUDE.agent.md

@@ -26,13 +26,15 @@ workflow, document the required credentials/default data and wire a smoke into
 
 - [ ] Full verification returns `"status": "pass"` (`har env verify ${AGENT_ID} --full`, MCP `har_run_verification` with `full: true`, or `./.har/verify.sh ${AGENT_ID} --full`)
 - [ ] The slot is agent-usable for this repo's documented smoke workflow when runtime services are involved
-- [ ] When `stages/browser-e2e.sh` exists, full verify includes Playwright — adapt specs under `tests/` for UI changes
+- [ ] Full verify runs every registered stage in `stages.json` `verificationStages` (Playwright, custom checks, …) — when `stages/browser-e2e.sh` exists, adapt specs under `tests/` for UI changes
 - [ ] New behavior has automated test coverage
 - [ ] Changes committed **in the session worktree** with a clear message
 - [ ] Finish with `har env complete ${AGENT_ID}` (or MCP `har_complete_environment`) — records the validation and tears down while **keeping the session branch** for the user to push / open a PR
 
 Quick loop: MCP `har_run_verification`, `har env verify ${AGENT_ID}`, or `./.har/verify.sh ${AGENT_ID}`
 
+Stages are the harness's single vocabulary for checks: templates and custom stages compile to generic kinds in `.har/stages.json`, and you interact with them only through the registry (`har_run_stage`, `verify`), never stack-specific tooling. Authoring guide: `.har/STAGES.md`.
+
 ## Project commands
 
 ```bash

package/dist/templates/har-boilerplate-cli/STAGES.md

@@ -0,0 +1,91 @@
+# HAR Stages — authoring guide
+
+Stages are the harness's single vocabulary for runnable checks and lifecycle
+actions. Everything — shipped templates (`playwright`, `rocketsim`), your
+project's test/lint commands, bespoke validation scripts — registers in
+`.har/stages.json` with the same schema, and agents interact with stages only
+through that registry (CLI `har env verify`, MCP `har_run_stage` /
+`har_run_verification`), never through stack-specific tooling.
+
+## The registry: `.har/stages.json`
+
+```jsonc
+{
+  "verificationStages": ["typecheck", "unit-tests", "api-health", "browser-e2e"],
+  "stages": [
+    {
+      "id": "browser-e2e",              // stable, shell-friendly slug
+      "kind": "test",                   // setup | launch | verify | test | inspect | reset | teardown | custom
+      "description": "Playwright E2E",
+      "script": "stages/browser-e2e.sh", // relative to .har/ — OR use "command"
+      "requiresAgentId": true,           // default true for test/verify/custom kinds
+      "artifacts": [{ "path": ".har/artifacts/browser-e2e", "kind": "directory" }]
+    },
+    {
+      "id": "unit-tests-fast",
+      "kind": "test",
+      "command": "npm test -- --agent {agentId}"   // {agentId} is substituted at run time
+    }
+  ]
+}
+```
+
+Optional stage fields: `cwd` (working directory), `env` (extra env vars),
+`group`, `acceptsArgs` (extra CLI args the stage accepts, e.g. `["--full"]`).
+
+## Two ways to define a stage
+
+**Command stages** — the default for simple checks (`npm test`, `swiftlint`,
+`make check`). One JSON entry, zero files:
+
+```bash
+har env add-stage unit-tests-fast --custom --kind test --command "npm test" --verification
+```
+
+**Script stages** — for anything that needs the slot's env, ports, or
+artifacts. Scaffold a contract-compliant skeleton:
+
+```bash
+har env add-stage db-integrity --custom --script --description "Check DB invariants"
+```
+
+then implement the TODO block in `.har/stages/db-integrity.sh`.
+
+## The stage script contract
+
+Every script under `.har/stages/` must:
+
+1. Source `harness.env` and `agent-slot.sh` from `.har/`.
+2. Take the agent slot id as `$1` (validate with `validate_agent_id`); extra
+   args may follow.
+3. Load the slot env via `resolve_agent_env_file` and run checks from the
+   agent's work dir (`resolve_agent_work_dir`).
+4. Write artifacts (reports, screenshots, logs) under `.har/artifacts/<id>/`.
+5. Print **only** the normalized JSON result object on stdout
+   (`status`, `stageId`, `agent_id`, `total_ms`, …); log progress to stderr.
+6. Exit with the real status code (0 = pass).
+
+The scaffolded skeleton implements all of this — replace its TODO block.
+
+## Verification membership
+
+Listing a stage id in `verificationStages` is what includes it in
+`har env verify <id> --full`. Ids that match a registered stage run via their
+script/command; ids without a registry entry (e.g. `typecheck`, `api-health`)
+are inline steps owned by `.har/verify.sh`. Lifecycle kinds
+(`setup`/`launch`/`reset`/`teardown`/`inspect`) and `verify` itself never run
+as part of verification, even if listed.
+
+## Commit gate
+
+The registry also holds the optional `commitGate` config (installed via
+`har hooks install`): `{ "commitGate": { "mode": "block" | "warn", "scope":
+"worktrees" | "all" } }` controls whether unverified change batches may be
+committed.
+
+## Shipped stage templates
+
+`har env add-stage --list` shows available templates; `har env add-stage
+playwright` (web) or `har env add-stage rocketsim` (iOS) installs one. A
+template is just packaging: it copies files, merges `package.json` fragments,
+and registers stages through the exact same registry as `--custom`.

package/dist/templates/har-boilerplate-cli/agent-slot.sh

@@ -248,15 +248,26 @@ har_regenerate_agent_env_file() {
     REPO_ROOT="$work_dir" \
       envsubst '${AGENT_ID} ${API_PORT} ${FE_PORT} ${DEBUG_PORT} ${DB_PORT} ${MINIO_PORT} ${BROWSER_PORT} ${REPO_ROOT}' \
       < "$template" > "$env_file"
-    return 0
-  fi
-  cat > "$env_file" <<EOF
+  else
+    cat > "$env_file" <<EOF
 # Agent environment — generated by launch.sh
 AGENT_ID=${agent_id}
 REPO_ROOT=${work_dir}
 WORKTREE_DIR=${worktree_dir}
 NODE_ENV=test
 EOF
+  fi
+  if command -v har >/dev/null 2>&1; then
+    har telemetry write-env \
+      --agent-id "$agent_id" \
+      --repo "${HARNESS_ROOT:-$REPO_ROOT}" \
+      --env-file "$env_file" \
+      --work-dir "$work_dir" \
+      ${SLOT_BRANCH:+--branch "$SLOT_BRANCH"} \
+      ${SLOT_SUFFIX:+--suffix "$SLOT_SUFFIX"} \
+      ${SLOT_PURPOSE:+--purpose "$SLOT_PURPOSE"} \
+      >/dev/null 2>&1 || true
+  fi
 }
 
 har_launch_preflight() {
@@ -642,14 +653,43 @@ escape_step_output() {
   printf '%s' "$1" | node -e "let d='';process.stdin.on('data',c=>d+=c);process.stdin.on('end',()=>{const s=d.trim().split('\n').slice(0,50).join('\n');process.stdout.write(JSON.stringify(s))})" 2>/dev/null || echo '""'
 }
 
-# Run browser-e2e on verify --full when the Playwright stage template is installed.
-run_browser_e2e_if_present() {
+# Emit "<id>\t<command>" for each registered stage listed in stages.json
+# verificationStages (used by verify --full). Ids without a matching registered
+# stage are inline verify.sh steps and skipped here; lifecycle stages
+# (setup/launch/reset/teardown/inspect) and the verify stage itself never run.
+# Authoring contract: .har/STAGES.md
+list_registered_verification_stage_commands() {
   local script_dir="$1"
   local agent_id="$2"
-  local e2e="$script_dir/stages/browser-e2e.sh"
-  if [ -x "$e2e" ]; then
-    "$e2e" "$agent_id"
-  fi
+  local registry="$script_dir/stages.json"
+  [ -f "$registry" ] || return 0
+  HAR_STAGE_REGISTRY="$registry" HAR_SCRIPT_DIR="$script_dir" HAR_AGENT_ID="$agent_id" node <<'NODE' 2>/dev/null || true
+const fs = require('fs');
+const { HAR_STAGE_REGISTRY, HAR_SCRIPT_DIR, HAR_AGENT_ID } = process.env;
+const shq = (s) => "'" + String(s).replace(/'/g, "'\\''") + "'";
+let reg;
+try { reg = JSON.parse(fs.readFileSync(HAR_STAGE_REGISTRY, 'utf8')); } catch { process.exit(0); }
+const ids = Array.isArray(reg.verificationStages) ? reg.verificationStages : [];
+const stages = Array.isArray(reg.stages) ? reg.stages : [];
+const runnable = new Set(['test', 'custom']);
+for (const id of ids) {
+  const stage = stages.find((s) => s && s.id === id);
+  if (!stage || stage.id === 'verify' || !runnable.has(stage.kind)) continue;
+  const needsAgent = stage.requiresAgentId !== false;
+  let cmd;
+  if (stage.script) {
+    cmd = shq(HAR_SCRIPT_DIR + '/' + stage.script) + (needsAgent ? ' ' + shq(HAR_AGENT_ID) : '');
+  } else if (stage.command) {
+    cmd = stage.command.split('{agentId}').join(HAR_AGENT_ID);
+  } else {
+    continue;
+  }
+  if (stage.cwd) cmd = 'cd ' + shq(stage.cwd) + ' && ' + cmd;
+  const env = stage.env && typeof stage.env === 'object' ? stage.env : {};
+  const prefix = Object.entries(env).map(([k, v]) => k + '=' + shq(v)).join(' ');
+  process.stdout.write(id + '\t' + (prefix ? prefix + ' ' : '') + cmd + '\n');
+}
+NODE
 }
 
 # Optional project-owned "agent usable" smoke beyond health.

package/dist/templates/har-boilerplate-cli/stages/README.sh

@@ -1,9 +1,11 @@
 #!/usr/bin/env bash
-# Optional per-stage scripts live here.
-# Example: ./.har/stages/browser-e2e.sh <agent-id>
+# Per-stage scripts live here (e.g. ./.har/stages/browser-e2e.sh <agent-id>).
 #
-# Register custom stages in .har/stages.json with a project-owned command:
-#   "command": "./.har/stages/browser-e2e.sh {agentId}"
+# Read .har/STAGES.md for the authoring guide: the stage script contract,
+# command vs script stages, and how verificationStages controls verify --full.
+#
+# Scaffold a new one with:
+#   har env add-stage <id> --custom --script
 
-echo "Add stage scripts under .har/stages/ and register them in stages.json." >&2
+echo "Add stage scripts under .har/stages/ and register them in stages.json — see .har/STAGES.md." >&2
 exit 1

package/dist/templates/har-boilerplate-cli/verify.sh

@@ -5,7 +5,8 @@
 # Usage: ./.har/verify.sh <agent-id> [--full]
 #
 # Quick (default): ecosystem smoke — compile/import/build only
-# Full (--full):   + conventional tests, lint, optional readiness + browser-e2e
+# Full (--full):   + conventional tests, lint, readiness, and every registered
+#                  stage in stages.json verificationStages (see .har/STAGES.md)
 # Stock steps are examples. Replace them during adaptation to match this repo.
 set -euo pipefail
 
@@ -185,7 +186,13 @@ run_quick_smoke || { [ -z "$FULL" ] && true; }
 if [ -n "$FULL" ]; then
   run_full_checks
   run_step "readiness" "run_readiness_if_configured \"$AGENT_ID\"" || true
-  run_step "browser-e2e" "run_browser_e2e_if_present \"$SCRIPT_DIR\" \"$AGENT_ID\"" || true
+  # Registered verification stages from .har/stages.json (see .har/STAGES.md).
+  # Every stage listed in verificationStages with a registered script/command
+  # runs here -- stage templates and custom stages alike.
+  while IFS=$'\t' read -r STAGE_ID STAGE_CMD; do
+    [ -n "$STAGE_ID" ] || continue
+    run_step "$STAGE_ID" "$STAGE_CMD" || true
+  done < <(list_registered_verification_stage_commands "$SCRIPT_DIR" "$AGENT_ID")
 fi
 
 END_TOTAL=$(now_ms)

package/dist/templates/har-boilerplate-ios/CLAUDE.agent.md

@@ -35,6 +35,8 @@ seeded data, or a simulator flow, document it here and wire the smoke into
 
 Quick loop: MCP `har_run_verification`, `har env verify ${AGENT_ID}`, or `./.har/verify.sh ${AGENT_ID}`
 
+Stages are the harness's single vocabulary for checks: templates and custom stages compile to generic kinds in `.har/stages.json`, and you interact with them only through the registry (`har_run_stage`, `verify`), never stack-specific tooling. Authoring guide: `.har/STAGES.md`.
+
 ## Project commands
 
 ```bash

package/dist/templates/har-boilerplate-ios/STAGES.md

@@ -0,0 +1,91 @@
+# HAR Stages — authoring guide
+
+Stages are the harness's single vocabulary for runnable checks and lifecycle
+actions. Everything — shipped templates (`playwright`, `rocketsim`), your
+project's test/lint commands, bespoke validation scripts — registers in
+`.har/stages.json` with the same schema, and agents interact with stages only
+through that registry (CLI `har env verify`, MCP `har_run_stage` /
+`har_run_verification`), never through stack-specific tooling.
+
+## The registry: `.har/stages.json`
+
+```jsonc
+{
+  "verificationStages": ["typecheck", "unit-tests", "api-health", "browser-e2e"],
+  "stages": [
+    {
+      "id": "browser-e2e",              // stable, shell-friendly slug
+      "kind": "test",                   // setup | launch | verify | test | inspect | reset | teardown | custom
+      "description": "Playwright E2E",
+      "script": "stages/browser-e2e.sh", // relative to .har/ — OR use "command"
+      "requiresAgentId": true,           // default true for test/verify/custom kinds
+      "artifacts": [{ "path": ".har/artifacts/browser-e2e", "kind": "directory" }]
+    },
+    {
+      "id": "unit-tests-fast",
+      "kind": "test",
+      "command": "npm test -- --agent {agentId}"   // {agentId} is substituted at run time
+    }
+  ]
+}
+```
+
+Optional stage fields: `cwd` (working directory), `env` (extra env vars),
+`group`, `acceptsArgs` (extra CLI args the stage accepts, e.g. `["--full"]`).
+
+## Two ways to define a stage
+
+**Command stages** — the default for simple checks (`npm test`, `swiftlint`,
+`make check`). One JSON entry, zero files:
+
+```bash
+har env add-stage unit-tests-fast --custom --kind test --command "npm test" --verification
+```
+
+**Script stages** — for anything that needs the slot's env, ports, or
+artifacts. Scaffold a contract-compliant skeleton:
+
+```bash
+har env add-stage db-integrity --custom --script --description "Check DB invariants"
+```
+
+then implement the TODO block in `.har/stages/db-integrity.sh`.
+
+## The stage script contract
+
+Every script under `.har/stages/` must:
+
+1. Source `harness.env` and `agent-slot.sh` from `.har/`.
+2. Take the agent slot id as `$1` (validate with `validate_agent_id`); extra
+   args may follow.
+3. Load the slot env via `resolve_agent_env_file` and run checks from the
+   agent's work dir (`resolve_agent_work_dir`).
+4. Write artifacts (reports, screenshots, logs) under `.har/artifacts/<id>/`.
+5. Print **only** the normalized JSON result object on stdout
+   (`status`, `stageId`, `agent_id`, `total_ms`, …); log progress to stderr.
+6. Exit with the real status code (0 = pass).
+
+The scaffolded skeleton implements all of this — replace its TODO block.
+
+## Verification membership
+
+Listing a stage id in `verificationStages` is what includes it in
+`har env verify <id> --full`. Ids that match a registered stage run via their
+script/command; ids without a registry entry (e.g. `typecheck`, `api-health`)
+are inline steps owned by `.har/verify.sh`. Lifecycle kinds
+(`setup`/`launch`/`reset`/`teardown`/`inspect`) and `verify` itself never run
+as part of verification, even if listed.
+
+## Commit gate
+
+The registry also holds the optional `commitGate` config (installed via
+`har hooks install`): `{ "commitGate": { "mode": "block" | "warn", "scope":
+"worktrees" | "all" } }` controls whether unverified change batches may be
+committed.
+
+## Shipped stage templates
+
+`har env add-stage --list` shows available templates; `har env add-stage
+playwright` (web) or `har env add-stage rocketsim` (iOS) installs one. A
+template is just packaging: it copies files, merges `package.json` fragments,
+and registers stages through the exact same registry as `--custom`.