v0.2.1

0.2.1 - 2026-07-26

Changed

• Replaced the manual multi-dispatch release choreography with a single
  release.yml pipeline triggered by pushing a v<version> tag. The evidence
  workflows (compliance, real-workloads, swebench-lite) run as called
  jobs of the same workflow run as the registry publishes, so the
  same-release-commit audit property holds by construction with no inputs, run
  ids, or ref choices; the npm launcher publishes only when its version is not
  already on the registry; the GitHub Release is created automatically with
  notes from the CHANGELOG section. The dispatch-only publish-pypi and
  publish-npm workflows were removed, the npm tarball is published by local
  path (the previous form was parsed as a GitHub shorthand and failed), and
  final-audit remains as a manual audit tool outside the release path. PyPI
  and npm trusted publishing must point at release.yml.

Added

• Anonymous usage telemetry, on by default, sent to PostHog over HTTPS with
  the standard library only. Events are a closed schema of counters, enums,
  durations, and version/platform strings — session starts, per-tool
  success/error/latency summaries, and individual tool failures capped at 20
  per session — and never contain paths, arguments, command lines, or file
  contents. CODING_TOOLS_MCP_TELEMETRY=off or DO_NOT_TRACK=1 disables it,
  CODING_TOOLS_MCP_TELEMETRY=debug prints events to stderr instead of
  sending, CI environments are excluded automatically, and the anonymous
  install id in ~/.coding-tools-mcp/id can be deleted to reset identity.
  Tool calls never block on delivery: events queue in memory to a daemon
  thread and failures are dropped silently. See docs/telemetry.md.