@osfactory/har 0.25.0 → 0.27.0

package/dist/templates/adaptation-prompt-init.md

@@ -117,7 +117,7 @@ scripts or document why no substitute is needed. In particular:
   `.env.agent.<id>`, and `verify.sh` resolves env/work dir through `agent-slot.sh`.
 
 ### Optional Playwright stage
-If the user ran `har env add-stage playwright` (or `@playwright/test` is in package.json):
+If the user ran `har env add-plugin playwright` (or `@playwright/test` is in package.json):
 
 - Adapt `tests/**` selectors and API paths for this stack
 - Ensure `HARNESS_HEALTH_CHECK_PATH` matches the app health route used in API smoke tests

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

@@ -47,7 +47,7 @@ har env add-stage unit-tests --custom --kind test --command "npm test" --verific
 ```
 
 - 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).
+- Rich integrations ship as **plugins**: `har env add-plugin --list`, then e.g. `har env add-plugin playwright` (web) or `har env add-plugin rocketsim` (iOS). Plugins install stages; agents only talk to the stage registry.
 
 ## 6. Prove the harness works
 

package/dist/templates/cursor-rule.mdc.template

@@ -31,7 +31,7 @@ When a slot is occupied: prefer `complete` / `teardown` if the previous task is
 - **Never** set `force`/`confirmReplace` without the user explicitly approving replacement.
 - **Commit early and often** in the session worktree — teardown keeps the branch, not uncommitted work.
 - **Gitignored paths are ephemeral** (`state/`, `runs/`, local clones) — they are lost when the worktree is removed.
-- With telemetry prompts enabled, Mission Control derives session purpose from the first captured user prompt.
+- With telemetry on (default, including prompts), Mission Control derives session purpose from the first captured user prompt.
 
 <!-- Monorepo: if this repository contains multiple .har harnesses, list them here
      and pick by the files you are changing. Example:

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

@@ -73,7 +73,7 @@ The stock commands are deliberately generic conventions keyed by
 adaptation; do not leave Node/npm, Python, Go, Rust, Java, or Ruby defaults in
 place when they do not match the project.
 
-Install Playwright stage: `har env add-stage playwright` (optional). UI changes should add or update specs under `tests/`.
+Install Playwright plugin: `har env add-plugin playwright` (optional). UI changes should add or update specs under `tests/`.
 
 ## Readiness layers
 

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

@@ -1,12 +1,14 @@
 # HAR Stages — authoring guide
 
 Stages are the harness's single vocabulary for runnable checks and lifecycle
-actions. Everything — shipped templates (`playwright`, `rocketsim`), your
+actions. Everything — shipped plugins (`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.
 
+Philosophy: *plugins install stages; agents only talk to the stage registry.*
+
 ## The registry: `.har/stages.json`
 
 ```jsonc
@@ -83,9 +85,9 @@ The registry also holds the optional `commitGate` config (installed via
 "worktrees" | "all" } }` controls whether unverified change batches may be
 committed.
 
-## Shipped stage templates
+## Shipped plugins
 
-`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`.
+`har env add-plugin --list` shows available plugins; `har env add-plugin
+playwright` (web) or `har env add-plugin rocketsim` (iOS) installs one. A
+plugin is just packaging: it copies files, merges `package.json` fragments,
+and registers stages through the exact same registry as `add-stage --custom`.

package/dist/templates/har-boilerplate/stages.json

@@ -32,7 +32,7 @@
     {
       "id": "verify",
       "kind": "verify",
-      "description": "Verification pipeline (quick by default; --full adds lint and browser-e2e when installed)",
+      "description": "Verification pipeline (quick smoke by default; --full runs the registry's verificationStages)",
       "command": "./.har/verify.sh {agentId}",
       "acceptsArgs": ["--full"],
       "artifacts": [

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

@@ -233,7 +233,7 @@ if [ -n "$FULL" ]; then
   run_step "readiness" "run_readiness_if_configured \"$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.
+  # runs here -- plugins 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

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

@@ -53,7 +53,7 @@ In Cursor with HAR MCP configured: use `har_launch_environment`, `har_run_verifi
 ./.har/teardown.sh 1
 ```
 
-Read **`stages.json`** and **`verificationStages`**. Optional: `har env add-stage playwright`.
+Read **`stages.json`** and **`verificationStages`**. Optional: `har env add-plugin playwright`.
 
 ## Verification contract
 

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

@@ -1,12 +1,14 @@
 # HAR Stages — authoring guide
 
 Stages are the harness's single vocabulary for runnable checks and lifecycle
-actions. Everything — shipped templates (`playwright`, `rocketsim`), your
+actions. Everything — shipped plugins (`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.
 
+Philosophy: *plugins install stages; agents only talk to the stage registry.*
+
 ## The registry: `.har/stages.json`
 
 ```jsonc
@@ -83,9 +85,9 @@ The registry also holds the optional `commitGate` config (installed via
 "worktrees" | "all" } }` controls whether unverified change batches may be
 committed.
 
-## Shipped stage templates
+## Shipped plugins
 
-`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`.
+`har env add-plugin --list` shows available plugins; `har env add-plugin
+playwright` (web) or `har env add-plugin rocketsim` (iOS) installs one. A
+plugin is just packaging: it copies files, merges `package.json` fragments,
+and registers stages through the exact same registry as `add-stage --custom`.

package/dist/templates/har-boilerplate-cli/stages.json

@@ -32,7 +32,7 @@
     {
       "id": "verify",
       "kind": "verify",
-      "description": "Verification pipeline (quick by default; --full adds lint, build, browser-e2e when installed)",
+      "description": "Verification pipeline (quick smoke by default; --full runs the registry's verificationStages)",
       "command": "./.har/verify.sh {agentId}",
       "acceptsArgs": ["--full"],
       "artifacts": [

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

@@ -189,7 +189,7 @@ if [ -n "$FULL" ]; then
   run_step "readiness" "run_readiness_if_configured \"$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.
+  # runs here -- plugins 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

package/dist/templates/har-boilerplate-ios/ADAPT-PROMPT.md

@@ -30,12 +30,12 @@ Run `./.har/launch.sh 1`, then `./.har/verify.sh 1`.
 Common adaptations:
 - If the project uses a custom test plan, add `-testPlan MyTests` to the `xcodebuild test` invocation.
 - If SwiftLint is not used, remove or comment out the `lint` step.
-- If there are UI tests that require a running app, move them to a RocketSim flow (`har env add-stage rocketsim`) rather than xcodebuild tests.
+- If there are UI tests that require a running app, move them to a RocketSim flow (`har env add-plugin rocketsim`) rather than xcodebuild tests.
 
-## 4 — Add the RocketSim stage template (recommended)
+## 4 — Add the RocketSim plugin (recommended)
 
 ```bash
-har env add-stage rocketsim
+har env add-plugin rocketsim
 ```
 
 Then adapt `flows/example-smoke.sh` to navigate to your app's main screen and verify it loads.

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

@@ -57,7 +57,7 @@ Adapt for your scheme and simulator — see `.har/harness.env`.
 
 ## User-flow validation (RocketSim)
 
-If the RocketSim stage template is installed (`har env add-stage rocketsim`):
+If the RocketSim plugin is installed (`har env add-plugin rocketsim`):
 
 ```bash
 ./.har/stages/rocketsim-flows.sh ${AGENT_ID}

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

@@ -55,10 +55,10 @@ In Cursor with HAR MCP configured: use `har_launch_environment`, `har_run_verifi
 
 ## User-flow validation
 
-Add the RocketSim stage template to get reusable UI flow validation:
+Add the RocketSim plugin to get reusable UI flow validation:
 
 ```bash
-har env add-stage rocketsim
+har env add-plugin rocketsim
 ```
 
 This installs `.har/stages/rocketsim-flows.sh` and a `flows/` directory. Add flow scripts under `flows/` (see `.har/stages/ROCKETSIM.md`). Full verify automatically runs all flows.

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

@@ -1,12 +1,14 @@
 # HAR Stages — authoring guide
 
 Stages are the harness's single vocabulary for runnable checks and lifecycle
-actions. Everything — shipped templates (`playwright`, `rocketsim`), your
+actions. Everything — shipped plugins (`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.
 
+Philosophy: *plugins install stages; agents only talk to the stage registry.*
+
 ## The registry: `.har/stages.json`
 
 ```jsonc
@@ -83,9 +85,9 @@ The registry also holds the optional `commitGate` config (installed via
 "worktrees" | "all" } }` controls whether unverified change batches may be
 committed.
 
-## Shipped stage templates
+## Shipped plugins
 
-`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`.
+`har env add-plugin --list` shows available plugins; `har env add-plugin
+playwright` (web) or `har env add-plugin rocketsim` (iOS) installs one. A
+plugin is just packaging: it copies files, merges `package.json` fragments,
+and registers stages through the exact same registry as `add-stage --custom`.

package/dist/templates/har-boilerplate-ios/stages.json

@@ -32,7 +32,7 @@
     {
       "id": "verify",
       "kind": "verify",
-      "description": "Verification pipeline (quick: build + unit-tests; --full adds lint + rocketsim-flows)",
+      "description": "Verification pipeline (quick smoke by default; --full runs the registry's verificationStages)",
       "command": "./.har/verify.sh {agentId}",
       "acceptsArgs": ["--full"],
       "artifacts": [

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

@@ -154,7 +154,7 @@ if [ -n "$FULL" ]; then
 
   # 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.
+  # runs here -- plugins 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

package/dist/templates/{stage-templates → plugins}/playwright/README.md

@@ -1,6 +1,6 @@
-# Playwright HAR stage template
+# Playwright HAR plugin
 
-This template was added by `har env add-stage playwright`. It registers a `browser-e2e` stage and scaffolds a minimal Playwright test suite.
+This plugin was added by `har env add-plugin playwright`. It registers a `browser-e2e` stage and scaffolds a minimal Playwright test suite.
 
 ## Next steps
 

package/dist/templates/{stage-templates → plugins}/rocketsim/README.md

@@ -1,9 +1,9 @@
-# RocketSim Stage Template
+# RocketSim plugin
 
 Add reusable RocketSim user-flow validation to your iOS harness.
 
 ```bash
-har env add-stage rocketsim
+har env add-plugin rocketsim
 ```
 
 ## What this installs
@@ -42,7 +42,7 @@ Full verify (`verify --full`) runs all flows after lint.
 
 ```bash
 # 1. Install the stage
-har env add-stage rocketsim
+har env add-plugin rocketsim
 
 # 2. Check RocketSim health
 rocketsim doctor

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@osfactory/har",
-  "version": "0.25.0",
+  "version": "0.27.0",
   "description": "LLM-powered CLI for reproducible agent development environments",
   "keywords": [
     "har",
@@ -16,6 +16,7 @@
   },
   "files": [
     "dist",
+    "scripts/ensure-telemetry-default.cjs",
     "control/docker-compose.yml",
     "control/docker-compose.build.yml"
   ],
@@ -26,6 +27,7 @@
     "test:watch": "jest --watch",
     "typecheck": "tsc --noEmit",
     "lint": "eslint src --ext .ts",
+    "postinstall": "node scripts/ensure-telemetry-default.cjs",
     "prepublishOnly": "npm run build",
     "release": "semantic-release"
   },

package/scripts/ensure-telemetry-default.cjs

@@ -0,0 +1,40 @@
+#!/usr/bin/env node
+/**
+ * npm postinstall: persist full default telemetry preference when missing.
+ * Does not overwrite an existing ~/.har/telemetry.json (respects prior off / prompts=false).
+ * Hooks + Mission Control are activated on first `har` / `har env launch` / `har telemetry on`.
+ */
+'use strict';
+
+const fs = require('fs');
+const os = require('os');
+const path = require('path');
+
+function main() {
+  if (process.env.HAR_SKIP_TELEMETRY_POSTINSTALL === '1') return;
+
+  const preferencePath =
+    process.env.HAR_TELEMETRY_CONFIG_PATH || path.join(os.homedir(), '.har', 'telemetry.json');
+
+  if (fs.existsSync(preferencePath)) return;
+
+  const preference = {
+    enabled: true,
+    signals: {
+      metrics: true,
+      logs: true,
+      prompts: true,
+      traces: true,
+    },
+    updatedAt: new Date().toISOString(),
+  };
+
+  fs.mkdirSync(path.dirname(preferencePath), { recursive: true });
+  fs.writeFileSync(preferencePath, `${JSON.stringify(preference, null, 2)}\n`);
+}
+
+try {
+  main();
+} catch {
+  // Never fail npm install over telemetry preference write.
+}