Skip to content

v0.6.0 — inspect evidence and try the complete debugging workflow

Choose a tag to compare

View all tags
@LBarimi LBarimi released this 05 Sep 00:54
v0.6.0
c696deb

FailTrace 0.6.0 makes a complete failure investigation easier to try and its saved evidence easier for coding agents to inspect.

  • Try the complete workflow: the guided demo measures 7 passing and 3 failing trials, reduces input to ["BUG"], rejects an unrelated crash during Verify, checks a healthy candidate, and packages the original failure for replay.
  • Inspect saved evidence through MCP: the new read-only failtrace_inspect_run tool and Core inspectRunEvidence API page trial records and bounded stdout/stderr chunks without executing saved commands.
  • Connect with one command: version-pinned setup examples cover Codex, Claude Code, Cursor, and generic stdio clients. The installed package exposes seven MCP tools.
  • Reproduce a real race: npm run case:p-memoize runs the pinned affected/fixed case and its negative controls from a source checkout.
  • Review measured performance: the README links sanitized five-sample benchmark evidence, timing ranges, and the limits of concurrency and early classification.

Run the exact GitHub archive with Node.js 22.12+:

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

The command-scoped remote option is for npm 12's URL installation policy. The verified npm installation is:

npx --yes failtrace@0.6.0 demo

The public npm archive matches the attached GitHub archive byte for byte. A fresh-cache public installation passed the demo, bundle replay, Core and CLI Verify, saved-evidence inspection, and all seven tools through an npx-launched MCP server.

Verify reports observations from the recorded sample. A healthy candidate with no target match does not prove elimination or statistical improvement. The published performance measurements are from one Windows/Node host and are not portable timing guarantees.

Validation: 301 tests passed locally, along with type checking, build, fresh installed-package checks, demo and bundle replay, and the p-memoize case. All six Windows/macOS/Linux and Node.js 22/24 CI jobs and all three performance jobs passed on the release commit. The release workflow independently installed and tested the prepared archive.

The attached SHA256SUMS and release.json identify the exact archive and source commit. npm publication uses this public HTTPS archive without repacking it.

Assets 5
Loading