Skip to content

v1.0.0

Latest

Choose a tag to compare

@release-har-cli release-har-cli released this 28 Aug 13:14
· 1 commit to main since this release

HAR 1.0.0 — .har/ is now a configuration surface. The runtime lives in @osfactory/har; your repo keeps only what is yours.

Read first

Upgrade the CLI before the shims: npm install -g @osfactory/har@latest. A 1.0 shim plus a pre-1.0 har on PATH used to exec-loop (exit 86 now, instead of a fork bomb). In CI, put the runtime you mean to test on PATH before any ./.har/*.sh step.

Breaking changes

  • The vendored harness runtime moves into the package. ./.har/*.sh are thin shims (exec har env …). #234, #235
  • harness.env is schema-validated KEY=value — no shell functions. #230
  • One stage namespace with quick/full tiers. #231
  • Profiles are capability manifests, not forked file trees. #236
  • Drift is two-signal: you edited this vs upstream changed. #237
  • har plugin create for local plugins; add-stage --custom is retired. #240
  • Agent instructions collapse onto AGENTS.md; .har/CLAUDE.agent.md is retired. #301

Pre-1.0 vendored scripts keep working against the 1.0 CLI for a compatibility window (deprecation warnings, not a brick). Migrate when ready.

What's in 1.0.0

Closed work on the 1.0.0 milestone, plus the release-review fixes that landed on the same tag.

Epic

  • #225 — HAR 1.0.0: .har/ becomes a configuration surface

Runtime into the package

  • #226 — Finish runtime-bundle composition (remove ~2,400 duplicate overlay lines)
  • #227 — Remove profile double-truths and dead generator code
  • #229 — Single-source the node package-manager helper (7 copies → 1)
  • #234 — Move the harness runtime into the package
  • #235 — Generate .har/*.sh as thin shims with pinned npx fallback

Config, verification, surfaces

  • #230harness.env becomes pure schema-validated config
  • #231 — Verification as data: one stage namespace, quick/full tiers
  • #232har env doctor — harness contract validation
  • #233 — Close CLI/MCP parity gaps and deduplicate the launch guard
  • #236 — Profiles become capability manifests
  • #237 — Two-signal drift: user-edited vs upstream-updated

Extension points

  • #238 — Lifecycle hooks
  • #239har env eject
  • #240har plugin create; retire add-stage --custom

Migration and docs

  • #241 — Pre-1.0 → 1.0 migration: versioned migrations + MIGRATE prompt
  • #242 — Dogfood: migrate this repo's three harnesses
  • #243 — Docs and prompts rewrite for the 1.0 customization contract
  • #301 — Collapse the agent instruction surface onto AGENTS.md

Fixes caught before users would have

  • #228 — Surface bugs: MCP trigger tag, duplicated status arg, dead setup-infra code, verify quick-mode exit
  • #290 — Plugin templates still sourced agent-slot.sh
  • #291 — Shim × pre-1.0 CLI = infinite exec recursion
  • #297attach.sh was never migrated to a shim
  • #298 — CI ran the 1.0 shims against the published pre-1.0 CLI
  • #299 — Dogfood harness docs still described the pre-1.0 surface
  • #300 — Close the release-review gaps (attach.sh, CI runtime, stale docs)

Also in this tag

  • #195 — Default add-plugin to skip CI workflows (--with-ci opt-in); post-install adaptation prompt
  • #312 — Honor the ! breaking marker so semantic-release actually publishes 1.0.0

Muscle memory is unchanged: har env launch 1, har env verify 1 --full, and ./.har/verify.sh 1 --full still work.