v2.1.1

Fixed

Stack traces now point at TypeScript, not compiled output. Every exception reported to error tracking resolved to build/*.js with compiled line numbers — a throw at src/core/connection.ts:1614 showed up as build/core/connection.js:1370, a 244-line drift. A new bootstrap entry enables Node's source-map support before any module is compiled, so frames now carry real src/**/*.ts coordinates. No new dependency and no sourcemap upload pipeline.

Error categories were inverted. The execution category — meant to flag genuine runtime faults — contained only Hermes eval guards ("multi-statement expressions are not supported…"), because those messages mention "Runtime.evaluate". Meanwhile real faults like TypeError: undefined is not a function had no matching rule and fell into unknown, which had grown to 37% of all failures and the single largest category. Categorization now recognises real JS faults, native command failures, app-state problems, and agent-input guards distinctly.

Added

Thrown vs handled failure tracking. Tool failures reach telemetry two ways — a handler returning { isError: true } or a handler throwing — and nothing recorded which. Only thrown failures produce a stack trace, so "how many real crashes are there" was unanswerable except as a range. Both paths are now tagged.

Notes

The executable entry point moved from build/index.js to build/bin.js. This is internal to the package; npx execbro and all MCP client configs are unaffected.