v0.3.0 — a first debugging result in one command

FailTrace turns repeated debugging experiments into inspectable evidence for developers and coding agents. This is the first prebuilt GitHub release.

Try the real demo from any directory:

npm exec --yes --allow-remote=root --package=https://github.com/LBarimi/FailTrace/releases/download/v0.3.0/failtrace-0.3.0.tgz -- failtrace demo

The demo records 7 passes and 3 failures, minimizes six JSON elements to ["BUG"], and creates a replayable bundle. Evidence stays local. It exits 0 when the expected results are verified.

For regular use:

npm install --global --allow-remote=root https://github.com/LBarimi/FailTrace/releases/download/v0.3.0/failtrace-0.3.0.tgz
failtrace demo

Requires Node.js 22.12+ and npm. The archive includes compiled code; no clone or TypeScript build is required. Runtime dependencies are installed by npm. The npm registry package itself has not been published.

Included: repeat/predicate/compare, repeated-trial Git regression isolation, text/JSON/files/environment minimization, reproduction bundles, and five official-SDK MCP tools. New in 0.3.0: guided demo, complete MCP predicate-match counts, agent setup guides, and installed-package CI.

Validation: 191 tests plus typecheck/build and installed-package checks across Windows/macOS/Linux with Node 22 and 24. Exact commit CI. Commit: 823163a.

Check SHA256SUMS before installation if you download the asset separately. Read agent setup, changes, and limits.

Share a real debugging result or first-install problem through the optional workflow report. No telemetry or account is required to use FailTrace.

The command-scoped --allow-remote=root option permits this explicitly requested archive on npm 12, which blocks URL installs by default. It does not change npm settings. Older npm versions that do not recognize it can omit it. See npm's URL install policy. This corrects the install commands recorded in the original archive's documentation and build metadata; the package and checksum are unchanged.