v1.3.0 — NUnit and Unity test evidence for agents

FailTrace 1.3.0 follows an existing NUnit or Unity unit test through a debugging investigation and rechecks it after a proposed fix. Coding agents use the same seven MCP tools, with an exact test name and structured evidence.

• Select an exact NUnit 3 test fullname and optional failure message from Core, CLI or MCP.
• Preserve a fresh XML report for every trial using {testReport} or FAILTRACE_TEST_REPORT. Missing, skipped, ambiguous and unrelated failures remain inconclusive.
• Retain the selected test through Compare, Bisect, Minimize, Verify and replay. Verify rereads saved XML and checks its digest.
• Receive bounded test outcomes, counts and diagnostic reasons through MCP. NUnit replay bundles include the XML parser and its licenses.
• Try the original Unity inventory example. The documented Windows EditMode validation covers a failing baseline, a working serialization fix and a skipped-test control through MCP.

Read the unit-test guide and compatibility notes. Node.js 22.12+ is required; target frameworks, dependencies and Unity licensing remain local prerequisites. PlayMode and player builds were not validated by the example.

The release includes the reviewed CI-built archive, SHA-256 checksum and release receipt. npm and MCP Registry publication are verified separately; the main README records available installation routes.

Publication verified: npm 1.3.0 and the active MCP Registry record. Anonymous downloads matched SHA-256 59c132e256e5832c803e3aaef75c4aff02b9ccc0192af0e022813e2004b30eff. Fresh public installation, all seven MCP tools, NUnit run/Verify/inspection and replay passed.