@osfactory/har 1.0.0-rc.2 → 1.1.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@osfactory/har",
-  "version": "1.0.0-rc.2",
+  "version": "1.1.0",
   "description": "HAR: open agent harness CLI and MCP server for coding agents, isolated worktrees, and software-factory workflows",
   "keywords": [
     "har",
@@ -61,6 +61,7 @@
     "@types/yargs": "^17.0.33",
     "@typescript-eslint/eslint-plugin": "^8.62.0",
     "@typescript-eslint/parser": "^8.62.0",
+    "conventional-changelog-conventionalcommits": "^9.3.1",
     "esbuild": "^0.23.0",
     "eslint": "^8.57.1",
     "jest": "^29.7.0",

package/dist/prompts/system-authoring.md

@@ -1,155 +0,0 @@
-# Harness Authoring Agent
-
-You are a harness authoring agent. Your job is to adapt a copied `.har/` boilerplate to match a specific software repository, so AI coding agents can run the project in isolated development environments.
-
-## Your Mission
-
-Explore the target repository, then edit files in `.har/` directly to make the harness runnable for this project. When done, call `finishAuthoring` with a summary.
-
-**Do NOT** create a YAML config or JSON mapping file for runtime behavior. Put behavior directly in the harness scripts and templates.
-
-## Discovery for coding agents
-
-Coding agents discover the harness through two files:
-
-1. **`AGENT.md`** (repo root) — short pointer, always read first. Propose via `proposeAgentMd` — never write it directly.
-2. **`.har/README.md`** — full index of what's in the harness. **You must maintain this** on every init/maintain run.
-
-## Tools Available
-
-**Repository exploration:**
-- `readRepoFile(path)` — read files from the target repo
-- `listRepoDir(path)` — list repo directories
-
-**Harness editing (.har/):**
-- `readHarnessFile(path)` — read files in .har/
-- `listHarnessDir(path)` — list .har/ contents
-- `writeHarnessFile(path, content)` — full file rewrite
-- `editHarnessFile(path, old_string, new_string)` — targeted edit
-- `deleteHarnessFile(path)` — remove unnecessary files
-
-**Root agent guide:**
-- `proposeAgentMd(content, rationale)` — propose AGENT.md changes for user approval
-
-**Other:**
-- `ask(question, options?)` — ask user when genuinely ambiguous
-- `finishAuthoring(summary, language?, packageManager?, database?)` — submit when done
-
-## Primary application & shared services (decide FIRST)
-
-Identify the **primary application** — the ONE app coding agents modify and run per-slot. Everything else runs once, shared by all slots:
-
-- **Primary app** → `HARNESS_PRIMARY_APP` in `harness.env`; only its dev processes go in `ecosystem.agent.template.cjs`.
-- **External dependencies** (database, cache, mail, ...) → services in `docker-compose.agent.yml`, listed in `HARNESS_INFRA_SERVICES` (e.g. `"db redis"`), started once by `setup-infra.sh` on fixed ports. Delete unused menu services.
-- **Internal supporting services** of a monolith/monorepo (needed but not modified) → shared as compose services, or PM2 processes in optional `.har/ecosystem.shared.config.cjs` (`har-shared-<name>`, auto-started by `setup-infra.sh`). Never per-slot.
-
-## Files to adapt
-
-### `.har/README.md` (required — maintain every run)
-Clear index of the harness: what each file does, quick start, architecture, how to maintain.
-Update when anything in the harness changes.
-
-### `.har/harness.env`
-Primary app, ports, `HARNESS_INFRA_SERVICES`, migrate/seed commands, health check path.
-
-### `.har/ecosystem.agent.template.cjs`
-PM2 processes for the primary application only, matching how it runs in dev.
-
-### `.har/verify.sh`
-Real typecheck, lint, test, and health check commands — replace all TODOs.
-
-## Readiness vs liveness (required)
-Do not treat a passing health check as adaptation complete. A usable agent
-environment has layered readiness:
-
-1. **Infra ready** — shared services and template data stores exist.
-2. **Slot data ready** — every per-slot data store is created or cloned.
-3. **Process ready** — primary app processes are online and health passes.
-4. **Agent usable** — documented credentials/workflows work, required default
-   data exists, and UI/API smoke is not blocked by asset/dev-server issues.
-
-Compare the harness against the repository's full local-dev setup. If you skip
-heavy steps such as full seed, optional services, asset compilation modes, or
-background daemons, add the minimum substitute in `.har/` scripts or document
-why no substitute is needed. If the app has multiple databases/stores, provision
-all per-slot state. If launch generates config, validate the nested keys the app
-actually reads. Put agent-usability checks in full verify, a project-owned
-readiness script, or documented smoke URLs. Health alone is not sufficient for
-UI/auth apps.
-
-Ensure `launch.sh` writes the slot registry before slow or fragile steps, and
-`verify.sh` resolves env/work dir through `agent-slot.sh` so partial launches are
-recoverable.
-
-### `.har/CLAUDE.agent.md`
-Detailed agent instructions: commands, credentials, architecture, definition of done.
-
-### `.har/env.template`, `setup-infra.sh`, `docker-compose.agent.yml`
-As needed for the project's infra.
-
-### `AGENT.md` (repo root — via proposeAgentMd only)
-Short pointer document. Structure:
-- Link to `.har/README.md` and `.har/CLAUDE.agent.md`
-- State plainly: **the harness is how you run this project** — to see the app live (manual testing, browser, screenshots), `launch` a slot; never hand-roll docker/dev-server startup; fix or report a failing harness command instead of working around it
-- Preferred: HAR MCP tools or `har env launch/verify/teardown`
-- Fallback: `./.har/launch.sh`, `./.har/verify.sh`, etc. (when CLI is not installed)
-- Rules (no hardcoded ports, use agent-cli.sh)
-- Project-specific notes section
-
-If AGENT.md already exists, read it first and propose minimal updates — don't replace unrelated content.
-
-### Monorepos / multiple harnesses
-If the repository contains more than one project or `.har` harness (check for `.har/` directories above or below the one you are adapting):
-- Propose a **"Harnesses in this repo"** table for the ROOT `AGENT.md` — one row per harness: path, profile, what it runs, launch/verify commands, link to its `.har/README.md`. Lead with "pick the harness that owns the files you are changing."
-- Keep a small `AGENT.md` / `CLAUDE.md` pointer inside each project directory (local discovery), back-linking to the root index.
-- One Cursor rule at repo root listing all harnesses — never one rule per project.
-
-## Port allocation & shared services
-
-Document ports in `.har/README.md` and configure them in `.har/harness.env`. Resolved values land in `.env.agent.<id>` and `.har/slots/agent-<id>.json` at launch — never hardcode defaults in app code or tests.
-
-### Per-slot app ports (default / PM2 profile)
-
-| Layer | Scope | Rule | On conflict |
-|-------|-------|------|-------------|
-| Frontend | Per slot | `HARNESS_FE_BASE_PORT + (AGENT_ID × HARNESS_PORT_STEP)` | Scan `STEP` increments within the slot lane |
-| API | Per slot | `HARNESS_API_BASE_PORT + (AGENT_ID × STEP)` | Same scan policy |
-| Node debug | Per slot | `9200 + (AGENT_ID × STEP)` | Same scan policy |
-
-### Shared infra ports (when listed in `HARNESS_INFRA_SERVICES`)
-
-| Service | Default var | On conflict |
-|---------|-------------|-------------|
-| Postgres | `HARNESS_DB_PORT_DEFAULT` | Scan `HARNESS_DB_PORT_SCAN_START..END` |
-| MinIO | `HARNESS_MINIO_PORT_DEFAULT` (+ console) | Scan configured ranges in `harness.env` |
-| Mailpit | `HARNESS_MAILPIT_*_PORT_DEFAULT` | Scan configured ranges |
-| Headless browser | `HARNESS_BROWSER_PORT_DEFAULT` | Scan configured ranges |
-
-CLI and iOS profiles typically have no per-slot app ports; optional backends still use the shared-infra model.
-
-Set slot limits in `.har/stages.json` (`agentSlots`) based on machine capacity. `har env maintain --finalize` syncs legacy `HARNESS_AGENT_SLOT_*` exports in `harness.env`.
-
-### Do not
-
-- Hardcode `3000`, `15432`, `3847`, or other defaults in application code, tests, or agent docs
-- Run raw `docker compose` for harness infrastructure — use `setup-infra.sh` / `launch.sh`
-
-## Rules
-
-1. **Edit .har/ files directly** — no YAML runtime config
-2. **Always update README.md** in .har/ to reflect current harness state
-3. **Always call proposeAgentMd** with AGENT.md content (create or update proposal)
-4. **Reuse existing project commands** from package.json, Makefile, etc.
-5. **Replace all TODO placeholders**
-6. **Do not edit manifest.json** — managed by har CLI
-7. **Run the cleanup checklist before finishing** — keep strictly what this repository needs:
-   - compose file has only used services; `HARNESS_INFRA_SERVICES` matches exactly
-   - `harness.env` has port documentation vars for every enabled infra service; `.har/README.md` explains allocation and shared vs per-slot
-   - `env.template` has no blocks for removed services; no dead branches left in scripts
-   - unused harness files deleted (`deleteHarnessFile`), e.g. `attach.sh` when unused
-   - `.har/README.md` file table matches the files that actually exist
-   - `CLAUDE.agent.md` shows only real URLs/ports and commands that run
-   - skipped full-dev setup has a minimal bootstrap or clearly documented limitation
-   - all per-slot data stores are provisioned, not only the primary database
-   - `CLAUDE.agent.md` defines what "agent usable" means, including credentials or smoke checks when applicable
-8. **Call finishAuthoring** when complete

package/dist/templates/profiles/default/docs/claude-agent/environment.md

@@ -1,19 +0,0 @@
-## Environment
-
-| | |
-|--|--|
-| **Agent ID** | ${AGENT_ID} |
-| **Frontend** | http://localhost:${FE_PORT} |
-| **API** | http://localhost:${API_PORT} |
-| **Database** | `agent_${AGENT_ID}` on `localhost:${DB_PORT}` (when `db` is in `HARNESS_INFRA_SERVICES`) |
-| **Work dir** | Fresh session worktree per launch — see the launch output or `.har/slots/agent-${AGENT_ID}.json` |
-
-**Never edit the main checkout** — launch FIRST, then make ALL file edits under the work dir from the launch output. Edits there hot-reload in the running slot; use `./.har/agent-cli.sh ${AGENT_ID} restart` if a change doesn't take. An occupied slot always blocks a new launch — run `./.har/teardown.sh ${AGENT_ID}` (or `complete`) first, then launch again.
-
-This slot runs **only the primary application** (`HARNESS_PRIMARY_APP`). External dependencies and any supporting services run once, shared by all slots — `setup-infra.sh` manages them; never start them yourself.
-
-```bash
-./.har/agent-cli.sh ${AGENT_ID} status
-./.har/agent-cli.sh ${AGENT_ID} logs api
-./.har/agent-cli.sh ${AGENT_ID} health
-```

package/dist/templates/profiles/ios/docs/claude-agent/intro.md

@@ -1,3 +0,0 @@
-# Agent ${AGENT_ID} — iOS Development Environment
-
-> [`AGENTS.md`](../AGENTS.md) · [`.har/README.md`](./README.md) · [`stages.json`](./stages.json)

package/dist/templates/runtime-bundles/pm2-runtime/attach.sh

@@ -1,15 +0,0 @@
-#!/usr/bin/env bash
-# Attach to the tmux session for an agent.
-# The runtime lives in the HAR package (#234) — this file only forwards to it.
-# Usage: ./.har/attach.sh <agent-id>
-set -euo pipefail
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-REPO_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)"
-AGENT_ID="${1:?Usage: attach.sh <agent-id>}"
-if command -v har >/dev/null 2>&1; then
-  exec har env agent "$AGENT_ID" attach
-elif [ -x "$REPO_ROOT/node_modules/.bin/har" ]; then
-  exec "$REPO_ROOT/node_modules/.bin/har" env agent "$AGENT_ID" attach
-fi
-echo "Error: the 'har' CLI is not available. Install @osfactory/har (npm i -D @osfactory/har) or run: npx @osfactory/har env agent" >&2
-exit 127

package/dist/templates/runtime-bundles/shared-kernel/agent-cli.sh

@@ -1,35 +0,0 @@
-#!/usr/bin/env bash
-# Namespaced CLI for managing a running agent environment.
-# The runtime lives in the HAR package (#234) — this file only forwards to it.
-# Usage: ./.har/agent-cli.sh <agent-id> <command> [args...]
-set -euo pipefail
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-REPO_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)"
-# Loop guard (#291): a pre-1.0 har does not own this runtime kind in the
-# package — it executes this script as authoritative, which would exec back
-# into har forever (one node process per cycle). Trip on re-entry for this
-# harness root, and skip har binaries older than the pinned runtime's major.
-HAR_SHIM_GUARD="agent@${REPO_ROOT}"
-case ":${HAR_SHIM_REENTRY:-}:" in *":${HAR_SHIM_GUARD}:"*)
-  echo "Error: runtime loop detected — the har CLI that ran this shim delegated back into it." >&2
-  echo "  The har runtime handling this repo is older than the harness contract (pinned: @osfactory/har@__HAR_VERSION__)." >&2
-  echo "  Fix: npm i -g @osfactory/har@latest    # or in this repo: npm i -D @osfactory/har" >&2
-  exit 86
-  ;;
-esac
-export HAR_SHIM_REENTRY="${HAR_SHIM_REENTRY:-}:${HAR_SHIM_GUARD}"
-har_runtime_compatible() {
-  local v pinned="__HAR_VERSION__"
-  v="$("$1" --version 2>/dev/null | head -n1)" || return 1
-  [ "${v%%.*}" -ge "${pinned%%.*}" ] 2>/dev/null
-}
-if command -v har >/dev/null 2>&1 && har_runtime_compatible har; then
-  exec har env agent "$@"
-elif [ -x "$REPO_ROOT/node_modules/.bin/har" ] && har_runtime_compatible "$REPO_ROOT/node_modules/.bin/har"; then
-  exec "$REPO_ROOT/node_modules/.bin/har" env agent "$@"
-elif command -v npx >/dev/null 2>&1; then
-  exec npx --yes @osfactory/har@__HAR_VERSION__ env agent "$@"
-fi
-echo "Error: cannot run the HAR runtime — 'har' is not on PATH and Node.js (npx) is unavailable." >&2
-echo "  Install Node.js, then: npm i -D @osfactory/har   # or: npx @osfactory/har@__HAR_VERSION__ env agent" >&2
-exit 127

package/dist/templates/runtime-bundles/shared-kernel/launch.sh

@@ -1,35 +0,0 @@
-#!/usr/bin/env bash
-# Launch an isolated agent environment slot (fresh suffixed worktree; occupied slots block).
-# The runtime lives in the HAR package (#234) — this file only forwards to it.
-# Usage: ./.har/launch.sh <agent-id> [--no-worktree] [--resume]
-set -euo pipefail
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-REPO_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)"
-# Loop guard (#291): a pre-1.0 har does not own this runtime kind in the
-# package — it executes this script as authoritative, which would exec back
-# into har forever (one node process per cycle). Trip on re-entry for this
-# harness root, and skip har binaries older than the pinned runtime's major.
-HAR_SHIM_GUARD="launch@${REPO_ROOT}"
-case ":${HAR_SHIM_REENTRY:-}:" in *":${HAR_SHIM_GUARD}:"*)
-  echo "Error: runtime loop detected — the har CLI that ran this shim delegated back into it." >&2
-  echo "  The har runtime handling this repo is older than the harness contract (pinned: @osfactory/har@__HAR_VERSION__)." >&2
-  echo "  Fix: npm i -g @osfactory/har@latest    # or in this repo: npm i -D @osfactory/har" >&2
-  exit 86
-  ;;
-esac
-export HAR_SHIM_REENTRY="${HAR_SHIM_REENTRY:-}:${HAR_SHIM_GUARD}"
-har_runtime_compatible() {
-  local v pinned="__HAR_VERSION__"
-  v="$("$1" --version 2>/dev/null | head -n1)" || return 1
-  [ "${v%%.*}" -ge "${pinned%%.*}" ] 2>/dev/null
-}
-if command -v har >/dev/null 2>&1 && har_runtime_compatible har; then
-  exec har env launch "$@"
-elif [ -x "$REPO_ROOT/node_modules/.bin/har" ] && har_runtime_compatible "$REPO_ROOT/node_modules/.bin/har"; then
-  exec "$REPO_ROOT/node_modules/.bin/har" env launch "$@"
-elif command -v npx >/dev/null 2>&1; then
-  exec npx --yes @osfactory/har@__HAR_VERSION__ env launch "$@"
-fi
-echo "Error: cannot run the HAR runtime — 'har' is not on PATH and Node.js (npx) is unavailable." >&2
-echo "  Install Node.js, then: npm i -D @osfactory/har   # or: npx @osfactory/har@__HAR_VERSION__ env launch" >&2
-exit 127

package/dist/templates/runtime-bundles/shared-kernel/preflight.sh

@@ -1,35 +0,0 @@
-#!/usr/bin/env bash
-# Launch readiness gate — run before launch.sh or standalone.
-# The runtime lives in the HAR package (#234) — this file only forwards to it.
-# Usage: ./.har/preflight.sh <agent-id>
-set -euo pipefail
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-REPO_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)"
-# Loop guard (#291): a pre-1.0 har does not own this runtime kind in the
-# package — it executes this script as authoritative, which would exec back
-# into har forever (one node process per cycle). Trip on re-entry for this
-# harness root, and skip har binaries older than the pinned runtime's major.
-HAR_SHIM_GUARD="preflight@${REPO_ROOT}"
-case ":${HAR_SHIM_REENTRY:-}:" in *":${HAR_SHIM_GUARD}:"*)
-  echo "Error: runtime loop detected — the har CLI that ran this shim delegated back into it." >&2
-  echo "  The har runtime handling this repo is older than the harness contract (pinned: @osfactory/har@__HAR_VERSION__)." >&2
-  echo "  Fix: npm i -g @osfactory/har@latest    # or in this repo: npm i -D @osfactory/har" >&2
-  exit 86
-  ;;
-esac
-export HAR_SHIM_REENTRY="${HAR_SHIM_REENTRY:-}:${HAR_SHIM_GUARD}"
-har_runtime_compatible() {
-  local v pinned="__HAR_VERSION__"
-  v="$("$1" --version 2>/dev/null | head -n1)" || return 1
-  [ "${v%%.*}" -ge "${pinned%%.*}" ] 2>/dev/null
-}
-if command -v har >/dev/null 2>&1 && har_runtime_compatible har; then
-  exec har env preflight "$@"
-elif [ -x "$REPO_ROOT/node_modules/.bin/har" ] && har_runtime_compatible "$REPO_ROOT/node_modules/.bin/har"; then
-  exec "$REPO_ROOT/node_modules/.bin/har" env preflight "$@"
-elif command -v npx >/dev/null 2>&1; then
-  exec npx --yes @osfactory/har@__HAR_VERSION__ env preflight "$@"
-fi
-echo "Error: cannot run the HAR runtime — 'har' is not on PATH and Node.js (npx) is unavailable." >&2
-echo "  Install Node.js, then: npm i -D @osfactory/har   # or: npx @osfactory/har@__HAR_VERSION__ env preflight" >&2
-exit 127

package/dist/templates/runtime-bundles/shared-kernel/setup-infra.sh

@@ -1,35 +0,0 @@
-#!/usr/bin/env bash
-# Set up shared infrastructure for all agent slots. Idempotent.
-# The runtime lives in the HAR package (#234) — this file only forwards to it.
-# Usage: ./.har/setup-infra.sh 
-set -euo pipefail
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-REPO_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)"
-# Loop guard (#291): a pre-1.0 har does not own this runtime kind in the
-# package — it executes this script as authoritative, which would exec back
-# into har forever (one node process per cycle). Trip on re-entry for this
-# harness root, and skip har binaries older than the pinned runtime's major.
-HAR_SHIM_GUARD="setup-infra@${REPO_ROOT}"
-case ":${HAR_SHIM_REENTRY:-}:" in *":${HAR_SHIM_GUARD}:"*)
-  echo "Error: runtime loop detected — the har CLI that ran this shim delegated back into it." >&2
-  echo "  The har runtime handling this repo is older than the harness contract (pinned: @osfactory/har@__HAR_VERSION__)." >&2
-  echo "  Fix: npm i -g @osfactory/har@latest    # or in this repo: npm i -D @osfactory/har" >&2
-  exit 86
-  ;;
-esac
-export HAR_SHIM_REENTRY="${HAR_SHIM_REENTRY:-}:${HAR_SHIM_GUARD}"
-har_runtime_compatible() {
-  local v pinned="__HAR_VERSION__"
-  v="$("$1" --version 2>/dev/null | head -n1)" || return 1
-  [ "${v%%.*}" -ge "${pinned%%.*}" ] 2>/dev/null
-}
-if command -v har >/dev/null 2>&1 && har_runtime_compatible har; then
-  exec har env setup-infra "$@"
-elif [ -x "$REPO_ROOT/node_modules/.bin/har" ] && har_runtime_compatible "$REPO_ROOT/node_modules/.bin/har"; then
-  exec "$REPO_ROOT/node_modules/.bin/har" env setup-infra "$@"
-elif command -v npx >/dev/null 2>&1; then
-  exec npx --yes @osfactory/har@__HAR_VERSION__ env setup-infra "$@"
-fi
-echo "Error: cannot run the HAR runtime — 'har' is not on PATH and Node.js (npx) is unavailable." >&2
-echo "  Install Node.js, then: npm i -D @osfactory/har   # or: npx @osfactory/har@__HAR_VERSION__ env setup-infra" >&2
-exit 127

package/dist/templates/runtime-bundles/shared-kernel/teardown.sh

@@ -1,35 +0,0 @@
-#!/usr/bin/env bash
-# Tear down one agent slot: stop processes, release resources, keep the session branch.
-# The runtime lives in the HAR package (#234) — this file only forwards to it.
-# Usage: ./.har/teardown.sh <agent-id> [--delete-branch]
-set -euo pipefail
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-REPO_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)"
-# Loop guard (#291): a pre-1.0 har does not own this runtime kind in the
-# package — it executes this script as authoritative, which would exec back
-# into har forever (one node process per cycle). Trip on re-entry for this
-# harness root, and skip har binaries older than the pinned runtime's major.
-HAR_SHIM_GUARD="teardown@${REPO_ROOT}"
-case ":${HAR_SHIM_REENTRY:-}:" in *":${HAR_SHIM_GUARD}:"*)
-  echo "Error: runtime loop detected — the har CLI that ran this shim delegated back into it." >&2
-  echo "  The har runtime handling this repo is older than the harness contract (pinned: @osfactory/har@__HAR_VERSION__)." >&2
-  echo "  Fix: npm i -g @osfactory/har@latest    # or in this repo: npm i -D @osfactory/har" >&2
-  exit 86
-  ;;
-esac
-export HAR_SHIM_REENTRY="${HAR_SHIM_REENTRY:-}:${HAR_SHIM_GUARD}"
-har_runtime_compatible() {
-  local v pinned="__HAR_VERSION__"
-  v="$("$1" --version 2>/dev/null | head -n1)" || return 1
-  [ "${v%%.*}" -ge "${pinned%%.*}" ] 2>/dev/null
-}
-if command -v har >/dev/null 2>&1 && har_runtime_compatible har; then
-  exec har env teardown "$@"
-elif [ -x "$REPO_ROOT/node_modules/.bin/har" ] && har_runtime_compatible "$REPO_ROOT/node_modules/.bin/har"; then
-  exec "$REPO_ROOT/node_modules/.bin/har" env teardown "$@"
-elif command -v npx >/dev/null 2>&1; then
-  exec npx --yes @osfactory/har@__HAR_VERSION__ env teardown "$@"
-fi
-echo "Error: cannot run the HAR runtime — 'har' is not on PATH and Node.js (npx) is unavailable." >&2
-echo "  Install Node.js, then: npm i -D @osfactory/har   # or: npx @osfactory/har@__HAR_VERSION__ env teardown" >&2
-exit 127

package/dist/templates/runtime-bundles/shared-kernel/verify.sh

@@ -1,35 +0,0 @@
-#!/usr/bin/env bash
-# Verification pipeline (stages.json verificationStages; quick by default, --full for the whole list).
-# The runtime lives in the HAR package (#234) — this file only forwards to it.
-# Usage: ./.har/verify.sh <agent-id> [--full] [--json]   (human output; pass --json for the structured result)
-set -euo pipefail
-SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
-REPO_ROOT="$(cd "$SCRIPT_DIR/.." && pwd)"
-# Loop guard (#291): a pre-1.0 har does not own this runtime kind in the
-# package — it executes this script as authoritative, which would exec back
-# into har forever (one node process per cycle). Trip on re-entry for this
-# harness root, and skip har binaries older than the pinned runtime's major.
-HAR_SHIM_GUARD="verify@${REPO_ROOT}"
-case ":${HAR_SHIM_REENTRY:-}:" in *":${HAR_SHIM_GUARD}:"*)
-  echo "Error: runtime loop detected — the har CLI that ran this shim delegated back into it." >&2
-  echo "  The har runtime handling this repo is older than the harness contract (pinned: @osfactory/har@__HAR_VERSION__)." >&2
-  echo "  Fix: npm i -g @osfactory/har@latest    # or in this repo: npm i -D @osfactory/har" >&2
-  exit 86
-  ;;
-esac
-export HAR_SHIM_REENTRY="${HAR_SHIM_REENTRY:-}:${HAR_SHIM_GUARD}"
-har_runtime_compatible() {
-  local v pinned="__HAR_VERSION__"
-  v="$("$1" --version 2>/dev/null | head -n1)" || return 1
-  [ "${v%%.*}" -ge "${pinned%%.*}" ] 2>/dev/null
-}
-if command -v har >/dev/null 2>&1 && har_runtime_compatible har; then
-  exec har env verify "$@"
-elif [ -x "$REPO_ROOT/node_modules/.bin/har" ] && har_runtime_compatible "$REPO_ROOT/node_modules/.bin/har"; then
-  exec "$REPO_ROOT/node_modules/.bin/har" env verify "$@"
-elif command -v npx >/dev/null 2>&1; then
-  exec npx --yes @osfactory/har@__HAR_VERSION__ env verify "$@"
-fi
-echo "Error: cannot run the HAR runtime — 'har' is not on PATH and Node.js (npx) is unavailable." >&2
-echo "  Install Node.js, then: npm i -D @osfactory/har   # or: npx @osfactory/har@__HAR_VERSION__ env verify" >&2
-exit 127

package/dist/templates/shared-docs/claude-agent/intro.md

@@ -1,3 +0,0 @@
-# Agent ${AGENT_ID} — Development Environment
-
-> [`AGENTS.md`](../AGENTS.md) · [`.har/README.md`](./README.md) · [`stages.json`](./stages.json)