v0.3.1 — a first debugging result in one command

FailTrace is now available from the public npm registry. Try it from any directory:

npx --yes failtrace demo

For regular use:

npm install --global failtrace

This patch updates the package README and agent setup instructions to use the shorter registry installation route. It also includes the documented historical Prettier case and packaging checks that keep local investigation evidence and case dependencies out of published archives. The Core investigation behavior is unchanged.

The package includes mcpName and server.json metadata identifying the existing stdio server as io.github.LBarimi/failtrace, ready for official MCP Registry publication.

The Prettier case uses pinned affected/fixed releases and reduced a maintainer-authored 464-character fixture to 11 characters while preserving the upstream formatting defect. The fixed release succeeds on the reduced input. Its relocated bundle was replayed after installing the target dependencies in a fresh directory.

Validation includes 191 Core/CLI/MCP tests, four case-oracle tests, the complete real-case investigation, typecheck/build, and installed-package checks on Windows, macOS, and Linux with Node.js 22 and 24. The attached release.json identifies the exact source commit, successful CI run, and SHA-256 digest; SHA256SUMS covers the package archive.

The same prebuilt archive is available here for users who prefer a versioned GitHub asset. Node.js 22.12+ and npm are required. Runtime dependencies are installed by npm; no source checkout or compiler is needed.

Agent setup · Changes · Results and limits

Successful installation and these maintainer-run examples establish distribution and compatibility. Independent usage and repeat adoption remain to be established.