Product changelog

Every improvement.
Plainly recorded.

New features, important fixes, and the evidence behind each recent FixMap release.

Current package: v0.8.8Read the complete history

August 8, 2026

FixMap v0.8.8

Latest release

Forty-six issues closed across scan correctness, workflow honesty, the Action, documentation, accessibility, and release proof.

Added

  • Exact git-state scan caching accelerates repeated plans and can be bypassed with --no-cache.
  • JSON reports carry reportVersion 1 and a documented additive compatibility policy.
  • The website follows the system colour scheme and includes a persistent theme toggle.

Fixed

  • Scanner, Explain, Compare, Verify, MCP, CLI, and Action diagnostics now distinguish the real failure state and preserve actionable paths.
  • Generated counterparts no longer outrank maintained source or become the recommended next action.
  • The demo workflow, transcript, product illustration, metadata, contrast, focus indicators, and accessibility semantics now match the real product.

Evidence

  • Added 23 release-specific self-evaluation cases and an empty-suite guard.
  • The homepage and evidence page now read the checked-in adversarial record, and CI rejects stale rendered assets.

August 2, 2026

FixMap v0.8.7

Readable vendored dependency bundles stop posing as edit targets.

Fixed

  • Pretty-printed vendored dependency bundles with a source-map marker no longer escape generated-output detection or rank as a high-confidence edit target.

Evidence

  • Added a dedicated adversarial fixture for readable compiled dependencies while keeping Chalk's real vendored implementation ranked first.
  • All 420 workspace tests pass; held-out and external accuracy remain unchanged, and the adversarial suite is now 9/9 with zero false-confidence cases.

August 2, 2026

FixMap v0.8.6

Cleaner implementation rankings without hiding legitimate UI or generated-artifact work.

Fixed

  • Stylesheets are deprioritized for non-UI implementation tasks, while genuine CSS and layout tasks still rank them normally.
  • Explicitly named generated artifacts remain visible, but a maintained source twin caps their confidence and explains the source relationship.

Evidence

  • Added counterexample coverage for real CSS tasks and tasks that genuinely target a stale generated artifact.
  • Held-out accuracy remained 7/12 Top-1, 8/12 Top-3, and 9/12 Top-5.

August 2, 2026

FixMap v0.8.5

A proper installation path and a much shorter everyday command.

Improved

  • The README and website now lead with a global installation followed by the short fixmap command.
  • Install guidance now explains when npm may prefer an older project-local binary and why the running version printed by Doctor is authoritative.

August 2, 2026

FixMap v0.8.4

Doctor can identify an exact-version request that started the wrong installation.

Fixed

  • fixmap doctor reports both the requested and running versions when a local or ancestor installation shadows an exact npm request.
  • The clean verification procedure uses an isolated npm prefix and invokes its shim directly on Windows.

August 2, 2026

FixMap v0.8.3

Stricter MCP comparison inputs, with honest failures instead of false success.

Fixed

  • fixmap_compare rejects truncated report-shaped objects while continuing to accept complete reports that legitimately contain zero matches.
  • Optional rank, score, and confidence fields are type-checked when present.

August 2, 2026

FixMap v0.8.2

A broad reliability release across Windows, test routing, MCP, the Action, and diagnostics.

Added

  • New diagnostics identify unread content, missing tracked paths, duplicate real paths, generated-path dominance, and missing related tests.
  • MCP explain gained working-tree controls, the product page gained Compare, and the site gained robots.txt.

Fixed

  • Windows path normalization, BOM and UTF-16 manifests, common GitHub URL forms, failed diff handling, and additional source languages now behave consistently.
  • Workspace test routing, Action exclusions and comments, and stemming were hardened with regression coverage.

August 1, 2026

FixMap v0.8.1

The first large dogfooding sweep closed gaps across every FixMap surface.

Added

  • Compare and Doctor MCP tools, working-tree controls, browser-safe exports, and Action inputs for limit, exclude, and untracked files.
  • Release gates now verify the npm latest tag, canonical homepage metadata, internal versions, and a clean installation before publishing.

Fixed

  • CLI validation, comparison output, exclusions, confidence, risk evidence, JSON ranks, test routing, and Action comment selection.

August 1, 2026

FixMap v0.8.0

Plan, focus, compare, and verify became one coherent workflow.

Added

  • Go and Rust test routing, fixmap doctor, plan comparison, exclusions, result limits, working-tree mode, progress phases, pull-request URLs, and Action verify mode.
  • MCP explain lets agents investigate a missing file without shell access.

Fixed

  • Confidence now reflects real ranking separation instead of labeling a whole result page high.
  • Language detection, diagnostic bounds, file-mention performance, duplicate flags, verify output, and report consistency were corrected.

Security

  • Unbounded user text no longer flows into JSON reports, CI logs, or pull-request comments.

Nothing hidden

Every release stays inspectable.

The repository contains the full history, exact test evidence, and source for every change.

Browse GitHub releases