v0.3.0

Changed

• Bumped @bluestep-systems/b6p-core to ^0.3.0. Because core is esbuild-bundled into dist/cli.js, this dependency bump is what ships the release's changes — there are no CLI source changes. Core 0.3.0 adds internal whenReady() async-load race guards in the persistence store/map (awaited inside B6PCore/ScriptRoot) and the new ScriptFile.currentIntegrityStatus() helper. All changes are additive and backward-compatible; commands, flags, and runtime behavior are unchanged.

Standalone binaries (b6p-windows-x64.exe, b6p-macos-arm64) are attached by CI. The macOS Intel (b6p-macos-x64) build is a known-failing job — see TODO.md.

v0.2.1

Fixed

• b6p push no longer fails its pre-flight TypeScript compile with File 'lib.esnext.d.ts' not found
  (cascading into Cannot find global type 'Array') in the bundled npm CLI and the standalone
  binaries. TypeScript's default host resolves its standard library relative to __filename, which
  once bundled points inside the bundle where no lib.*.d.ts exist. The CLI now ships the full
  TypeScript lib set — copied next to the npm bundle and embedded in (then extracted from) the SEA
  binary — and hands it to the core via providers.typescriptLibDirs.
  (#4)

Changed

• Bumped @bluestep-systems/b6p-core to ^0.2.0, which adds the typescriptLibDirs provider and the
  TsLibResolver that consumes it.

v0.2.0

Added

• Standalone binaries. This release ships self-contained, Node-bundling b6p executables for Windows (x64) and macOS (x64 + arm64), built in CI via Node SEA and attached below (b6p-windows-x64.exe, b6p-macos-x64, b6p-macos-arm64, each with a .sha256 checksum sidecar). They run the full CLI on machines with no Node or npm installed — download one file, put it on PATH, and b6p <command> works. The npm package (npm i -g @bluestep-systems/b6p-cli) is unchanged and remains the primary distribution. See the toolchain ADR.

Fixed

• b6p --version now reports the actual package version instead of a hardcoded 0.0.1. The version is injected at build time via an esbuild define (__B6P_VERSION__), so it stays correct in both the npm bundle and the standalone binary — neither of which can read package.json at runtime.

Full changelog: https://github.com/Bluestep-Systems/b6p-cli/blob/v0.2.0/CHANGELOG.md