FailTrace 1.1.0 makes debugging evidence easier to interpret from the CLI and MCP tools.
- Bisect stops on unrelated nonzero exits instead of treating them as evidence of a good revision. Optional healthy and inconclusive exit policies support commands with intentional nonzero outcomes.
- Automatic same-run comparison prefers a healthy trial and a matching target failure. Selected-trial evidence and warnings explain incomplete or unrelated outcomes.
- Verify option errors include an executable syntax hint.
- The README starts with a runnable demo, a short controlled-demo animation, and coding-agent setup. Installation, performance scope, and voluntary workflow feedback have dedicated guides.
Read the 1.1.0 migration notes before upgrading Bisect workflows or relying on implicit comparison selection. Explicit trial choices remain available. Runtime requirements remain Node.js 22.12+.
This GitHub release contains the reviewed CI-built archive, its SHA-256 checksum, and a release receipt. npm and MCP Registry publication are verified separately; the main README records available installation routes.
Version 1.1.0, commit c7f9e7ce3ebc36b5e72fc9ee88cfbc57ff73781c, passed 374 tests and all seven CI gates. Archive SHA-256 dd52ef2a36ade281c6795fb708765f4f6da509b31f9fce3e10f7d559c68237bb matched the reviewed GitHub asset and the public npm download. Fresh-cache installations exercised the demo, Core, CLI, Verify, saved inspection, bundle manifests and replay. Additional installed CLI/MCP checks verified target-first comparison and Bisect's unrelated/declared exit guards. The server listed all seven tools; calls exercised run limits, comparison, Bisect, Verify and saved inspection. The 1.1.0 MCP Registry record is active. These are distribution checks, not evidence of independent adoption.
Install: npx --yes failtrace@1.1.0 demo.