Skip to content

v0.5.0 — verify a proposed fix

Choose a tag to compare

View all tags
@LBarimi LBarimi released this 04 Sep 18:10
v0.5.0
6224d71

FailTrace 0.5.0 connects a reproduced failure to a proposed code change with durable, inspectable evidence.

  • failtrace verify and Core verifyFix run a fixed candidate budget against an eligible captured baseline.
  • The failtrace_verify MCP tool exposes the same Core contract to coding agents.
  • Results distinguish a target that remains, a healthy sample where it was not observed, unrelated command failures, infrastructure failures and inconclusive evidence. They do not claim elimination or statistical improvement.
  • Baselines can hash declared input, setup and source files or capture bounded Git identity with raw tracked-file hashes. The current command, canonical working directory and intentional changes remain explicit.
  • Installed-package tests cover Core, CLI and MCP Verify, cancellation and the unrelated-error guard.
  • Real affected/fixed workflows cover a Prettier formatting defect and the p-memoize pending-call race. The race schedules are controlled, not presented as a natural failure-rate estimate.

Try the guided existing demo:

npx --yes failtrace@0.5.0 demo

Then follow the Verify workflow to capture your own baseline before editing code. Requires Node.js 22.12+ and npm.

The attached release.json records the exact source commit and six-job CI run. The archive was built and installed outside the checkout by the release workflow; SHA256SUMS identifies the reviewed bytes.

Assets 5
Loading