Minor release — v8.0 E2 + E4 (the "Pivot"): completes v8.0 by repositioning every public surface to the chosen framing — "the deterministic, verifiable grounding layer for AI code work" — and framing coding agents as consumers, not competitors. The Evidence Pack code (E1/E3/D3 + mcp install) already shipped in 7.27–7.29; this is the positioning half. Docs/strings only — no runtime behaviour change, zero new dependencies.

Added

• Agent recipes (#389): new README "Agent recipes" section with copy-paste setup for Claude Code, Cursor, Cline, Continue, Aider, OpenHands, and Codex CLI — each via sigmap mcp install <client> or a deterministic Evidence Pack, positioning agents as consumers of SigMap's map.
• Surface docs for shipped commands (#389): README now documents sigmap evidence (deterministic Evidence Pack JSON/Markdown) and sigmap doctor (setup diagnostics), which shipped in code but were undocumented.
• Repositioning gate (#389): test/integration/repositioning.test.js makes the pivot non-regressable — asserts the grounding-layer framing on README/llms.txt/docs <title>, recipes for every named agent, and the documented commands.

Changed

• E2 repositioning (#389): README tagline, "What is SigMap?", "Why SigMap?" (token reduction demoted to proof) and the compare table; docs/index.html title/meta/keywords/JSON-LD + hero (and the stale softwareVersion 5.8.0 → current); llms.txt/llms-full.txt regenerated from scripts/llms-manual.mjs; the per-project adapter tagline in src/format/llms-txt.js (bundle rebuilt, reproducible); docs/_config.yml. The literal context-engine remains only inside the published JetBrains plugin URL slug.
• Structure guards updated (#389): readme-structure.test.js tagline/compare-table assertions moved to the new copy; version-json.test.js now derives the docs softwareVersion from version.json instead of a hardcoded stale value.

Minor release — v8.0 E4: one-command, per-client MCP install so a cold user reaches a working MCP setup fast (the v8.0 <5-minute-quickstart exit gate).

Added

• sigmap mcp install <client> (#385): targeted MCP wiring for a single client — claude, cursor, windsurf, vscode, zed, codex, gemini, opencode, or portable mcp (.mcp.json). Unlike sigmap --setup (which wires every editor at once and only updates configs that already exist), this creates the config dir/file when absent, is idempotent (re-running reports already-registered, never duplicates), and emits the correct shape per client — mcpServers JSON, Zed context_servers, or Codex YAML. --global selects the user-level config for clients that have both a project and a global scope (Windsurf, OpenCode). Composed in the zero-dep src/mcp/install.js — no system-shell spawns, no install scripts.
• sigmap mcp list (#385): lists every supported MCP client and its resolved config path (--json for a machine-readable array).

Changed

• Regenerated llms-full.txt so the published surface lists the new mcp install/mcp list commands.

Fixed

• Hardened two --ci --min-coverage integration tests (#385) that were order- and environment-dependent — they hard-coded an "unreachable" 99% threshold, but once the suite generates a full src/ context the repo's measured coverage reaches 99–100%. They now pin the threshold relative to the actual measured coverage, so the gate-fails-above-achievable property holds deterministically everywhere.

What's Changed

• feat(mcp): one-command per-client MCP install (sigmap mcp install ) by @manojmallick in #386
• chore(release): v7.29.0 — mcp install/list, docs & benchmarks by @manojmallick in #387
• Release v7.29.0 — one-command per-client MCP install (v8.0 E4) by @manojmallick in #388

Full Changelog: v7.28.0...v7.29.0

Minor release — v8.0 E3: a one-shot setup doctor so a cold user reaches a useful answer fast.

Added

• sigmap doctor (#381): a one-shot diagnostic that runs seven resilient checks — git repository, config & source roots, generated context file, signature index, index freshness, coverage, and MCP wiring — and prints an actionable fix for anything wrong (e.g. "run: npx sigmap", "run: sigmap --setup", "increase maxTokens or expand srcDirs"). sigmap doctor --json emits { checks, ok, errors, warnings }; the command exits 1 on a hard failure (no context file / invalid config) and 0 otherwise, so it is usable in CI. Composed from loadConfig, coverageScore, buildSigIndex, and the known adapter-output / MCP-config paths — zero new runtime dependencies, no system-shell spawns.

Changed

• Release CI self-heals develop (#380): the develop→main release PR's head branch is develop, which the repo's delete-branch-on-merge setting removes on every release; the "Sync develop with main" workflow now fetches main and recreates develop from it when the ref is missing (else merges main in), so develop no longer needs manual restoration after a release.

What's Changed

• ci(sync): self-heal develop when auto-deleted by the release PR merge by @manojmallick in #380
• feat(doctor): sigmap doctor diagnostic command (v8.0 E3) by @manojmallick in #382
• chore(release): v7.28.0 — sigmap doctor, docs + benchmarks by @manojmallick in #383
• Release v7.28.0 — sigmap doctor (v8.0 E3) by @manojmallick in #384

Full Changelog: v7.27.0...v7.28.0

Minor release — v8.0 D3: two new MCP tools, taking the server from 15 to 17 tools. Both are composed from data SigMap already computes — zero new runtime dependencies, no system-shell spawns.

Added

• get_diff_context MCP tool (#376): for every changed file (working tree, staged via staged, or vs a base ref via base) returns its current signatures + blast radius (direct importers, transitive count, affected tests/routes) + a risk label — one call gives an agent everything a review or a safe edit needs. Lists changed files shell-free through src/util/git.js (no /bin/sh). Optional depth controls the blast-radius BFS.
• get_architecture_overview MCP tool (#376): a one-call codebase map — module breakdown (files/tokens), the most depended-on hub files, the dependency-cycle count, and route totals. Extends get_map for orienting in an unfamiliar repo. Composed from buildSigIndex, buildFromCwd, and detectCycles.

Changed

• MCP surface count is now 17 tools across --help, README, docs-vp/guide/mcp.md, version.json (mcp_tools), and the generated llms.txt/llms-full.txt.

What's Changed

• feat(mcp): get_diff_context & get_architecture_overview (v8.0 D3, 15→17 tools) by @manojmallick in #377
• chore(release): v7.27.0 — D3 MCP tools, docs + benchmarks by @manojmallick in #378
• Release v7.27.0 — D3 MCP tools (get_diff_context & get_architecture_overview) by @manojmallick in #379

Full Changelog: v7.26.0...v7.27.0

Minor release — v8.0 "The Evidence Pack & the Pivot" (E1): the keystone artifact that makes SigMap consumable by machines instead of copy-paste.

Added

• Evidence Pack JSON v1 (#372): new sigmap evidence "<query>" command emits a deterministic, machine-consumable signature-and-evidence map — a byte-stable JSON artifact (plus a --markdown/--md handoff rendering) that an agent or CI can ingest directly, every entry anchored to a real file, symbol, and line range. Schema v1: { schemaVersion, query, intent, files:[{ path, symbols, reason, confidence, sourceLines, relatedTests, riskLabel }], tokenBudget, droppedFiles, grounding:{ symbolCount, anchoredSymbols, anchorCoverage, contextHash, deterministic } }. Composed entirely from shipped zero-dep modules (ranker, line-anchor parsing, security scanner, sha256 grounding hash). The pack carries no wall-clock timestamp — an unchanged repo yields byte-identical output and a stable grounding.contextHash, so the artifact is auditable. CLI flags: --top, --budget, --out; always writes .context/evidence-pack.json. riskLabel ∈ {generated, test, config, security, source} and relatedTests are best-effort v1 (measured test-discovery and richer labels land in v8.5).

What's Changed

• feat(evidence): Evidence Pack JSON v1 (v8.0 E1) by @manojmallick in #373
• chore(release): v7.26.0 — Evidence Pack (v8.0 E1), docs + benchmarks by @manojmallick in #374
• Release v7.26.0 — Evidence Pack (v8.0 E1) by @manojmallick in #375

Full Changelog: v7.25.2...v7.26.0

Patch release — Trust Hygiene (H2): reproducible bundle build. Completes the v7.25.x "Trust Hygiene" milestone (H1+H2+H3+H4 all shipped).

Added

• Reproducible bundle build (#369): scripts/build-bundle.mjs (npm run build:bundle) deterministically regenerates the embedded __factories of gen-context.js from src/ + packages/adapters/ — sorted and de-duplicated — between two markers, leaving the preamble and the hand-written CLI core byte-identical. build:bundle --check asserts the committed bundle equals a fresh build and is wired into prepublishOnly and CI (next to the existing standalone bundle-smoke test on Node 18/20/22). A new bundle-repro test pins byte-for-byte reproducibility.

Fixed

• Duplicate / missing bundled modules (#369): the bundle carried a duplicate ./src/eval/llm-ablation factory (124 blocks for 115 src/ modules) because check-bundle --fix prepended on each run; it now regenerates the whole section via build-bundle, so duplicates can't recur. The willow adapter — silently never embedded (the integrity check only verified src/) — is now bundled. The canonical bundle is 125 modules, one factory each.

Patch release — Trust Hygiene (H4): document the real CLI / MCP / adapter surface. Completes the v7.25.x milestone's documentation goals (only H2, the reproducible bundle build, remains).

Added

• Document the shipped surface (#366): sigmap --help now lists the five wired-but-undocumented commands — conventions, scaffold, verify-plan, review-pr, and create (the grounded-creation pipeline). The README gains a "Grounded creation & guardrails" section, lists all 15 MCP tools, and adds the willow adapter to the integrations table. A new surface-docs test pins the documented surface to source (--help must list the commands, README's MCP count must equal TOOLS.length, every listAdapters() entry must appear in the README table), so the docs can never silently undersell the product again.

Fixed

• MCP tool undercount (#366): the README advertised "10 on-demand tools" while the server ships 15 — corrected and now gated by the surface-docs test.

Minor release — Trust Hygiene (H1 + H3): one generated source of benchmark truth, gated in CI. First installment of the v7.25.x milestone.

Added

• Single source of benchmark truth (#363): benchmarks/latest.json is now generated from the benchmark reports (scripts/gen-benchmark-latest.mjs), and version.json metrics, README.md (via <!--SM:KEY--> markers), and llms.txt/llms-full.txt all read from it (scripts/sync-metrics.mjs). Every hand-typed metric is removed — published numbers can no longer silently drift from the measured reports. New npm run metrics:sync regenerates the whole chain; npm run check:metrics gates it in prepublishOnly and CI.
• Truthful version.json (#363): languages, extractors, mcp_tools, and tests are auto-derived from source via a shared scripts/lib/source-meta.mjs (the same derivation the llms generator uses, so the language count can never diverge). Added the extractors field.

Changed

• Every published number traces to one fresh, gated benchmark run (#363): the long-standing drift (committed reports vs hand-typed README/version.json/llms.txt) is eliminated — all surfaces now derive from benchmarks/latest.json. This release regenerates that file from a live benchmark run (2026-06-21, sigmap-v7.25-main, 21 repos): hit@5 75.6% (13.6% baseline, 5.6× lift), token reduction 97%, task success 52.2%, prompts/task 1.72 → 2.84, prompt reduction 39.4%. languages corrected 31 → 33; extractors (42) now reported.

Patch release — surface the StarMapper stargazer map in the docs.

Added

• StarMapper stargazer-map badge + link (#360): the README badge row gains a StarMapper badge and the Support section a "stargazers around the world" link; the docs site adds a community link — all pointing to the StarMapper map (517 stars across 37 countries). StarMapper is a client-rendered SPA with no verifiable badge endpoint, so a reliable shields.io static badge links to the map rather than embedding an unverifiable image. A README-structure test pins the StarMapper URL.

Tests: 1,175 passing.

What's Changed

• docs: add StarMapper stargazer-map badge + link by @manojmallick in #361
• release: v7.24.2 — StarMapper stargazer map in docs by @manojmallick in #362

Full Changelog: v7.24.1...v7.24.2

Patch release — publish the first measured §9 grounding result.

Added

• §9 grounding result published (version.json ablation): the first averaged §9 LLM A/B ablation on the fact-question corpus (v7.24.0) — 5 runs × 100 repo-fact tasks, Gemini gemini-2.5-flash. With SigMap's exact-signature grounding, flagged codebase-fact errors fell from 99.8 [99–100] to 0.2 [0–1] per 100 outputs (mean delta 99.6). The ungrounded model, with no repo knowledge, fabricates a plausible-but-wrong file path on essentially every task; the grounded model — given exact signatures grouped by file — states the correct path. This measures factual-recall grounding (faithful use of provided context), not generative code correctness.

Tests: 1,174 passing.

What's Changed

• release: v7.24.1 — publish §9 grounding result (99.8 → 0.2 per 100) by @manojmallick in #359

Full Changelog: v7.24.0...v7.24.1