Release v3.2.0

fix(plugin): sync plugin manifests to 3.2.0 and gate it locally

The v3 line bumped package.json four times without updating the plugin
manifests, so plugin.json and marketplace.json were still on 2.13.0 and
plugin/.mcp.json still pinned 3.1.0.

Root cause is not the drift, it is that `check:plugin` ran only in CI and not in
`npm run validate`. Every increment of the v3 line reported a green validate
locally while carrying a failure that could only surface after a push. Adding it
to validate makes the local command mean what its name claims.

npm run validate: green, 629 tests, plugin in sync at 3.2.0.

Release v2.13.0

feat: reliability and security hardening, v2.8.0 through v2.13.0

Implements roadmap tasks 052-057, completing the Phase 11 hardening pillars
(task 051 shipped separately as v2.7.0). Squashed into one commit: the original
per-release history carried a Stripe-shaped test fixture that GitHub push
protection correctly refused, and it appeared in every commit of the chain.

v2.8.0 — Response-path secret redaction (task 052)
  redactSecrets runs in callTool on the final payload, before it splits into
  content[0].text and structuredContent, so both channels and tool error
  messages are covered by construction rather than by parallel code paths.
  Exact-match on credentials this process holds, plus shape-match on
  issuer-prefixed formats, PEM blocks, Authorization headers, and secret-named
  assignments. Generic entropy detection was deliberately rejected: this server
  returns git SHAs and sha256: content hashes as normal output, and an entropy
  rule would redact them and corrupt results.

v2.9.0 — Transport hardening for the model hop (task 053)
  Protected per-provider tls_verify, set in the process environment so editable
  preferences cannot weaken it. When enabled, plain HTTP to a non-loopback host
  and NODE_TLS_REJECT_UNAUTHORIZED=0 are refused at adapter construction, so the
  failure surfaces at startup. Fixes a real bug: both adapters discarded the
  transport error and raised a *retryable* endpoint_unreachable, so a rejected
  certificate was retried as though it were a transient blip.

v2.10.0 — Release-qualification gates (task 054)
  npm run release:gates reports each gate as met, unmet, or unverifiable and
  exits non-zero unless all are met; "unverifiable" is a distinct outcome so a
  missing artifact never reads as a pass. npm run release:scenarios drives the
  official fixtures through real harnesses and refuses to fabricate a run. The
  external gates stay operator-only and the task's boxes are left unchecked.

v2.11.0 — Fault-injection test suite (task 055)
  An in-test responder that dies mid-body, truncates SSE, returns HTML error
  pages, answers slowly, or returns empty bodies. Covers transport, stream, and
  capacity-state faults, asserting typed errors and zero residual capacity
  however a task settled.

v2.12.0 — Error-rate observability (task 056, ADR-0015)
  get_offload_stats gains failure, retry, and breaker metrics with live
  per-provider state. Fixes a pre-existing defect in task 032: raw events are
  pruned after seven days and record() prunes on every write, so the advertised
  monthly and lifetime windows could never hold anything older than a week. The
  existing test passed only because the old event happened to be written last.
  Windows now come from a durable daily rollup holding counters alone.

v2.13.0 — Large-monorepo degradation (task 057)
  index_max_files (25,000) and index_max_bytes (512 MiB) bound indexing, which
  stops at the ceiling and reports the shortfall instead of walking an unbounded
  tree. search_semantic attaches an index_limitation so a caller can tell "not
  indexed" from "no match".

Also corrects the stale "Planned" status on task 043, which shipped in v2.2.0.

Credential fixtures are assembled from parts at run time so no scanner-matching
literal exists in source. npm run validate green: 553 tests.

Release v2.7.0

feat(security): fence repository text in nonce-delimited untrusted-da…

Release v2.6.0

feat: add harness context management with result verbosity (v2.6.0)

v2.3.1

Fixes

• Per-response token cap now follows the model context window. The LM Studio provider clamps max_tokens to the model's context (loaded instance context_length, falling back to max_context_length via /api/v1/models and /api/v0/models). Requests no longer ask for more output tokens than the model can produce, which previously caused responses to be rejected during processing (incomplete_response) before the server replied.
• Actionable truncation diagnostics. An incomplete_response error now reports finish_reason, the requested max_tokens, and completion_tokens.

See docs/decisions/0012-derive-max-tokens-from-model-context.md. Full npm run validate green (411 tests).

Release v2.1.0

feat(v2.1.0): minor release version 2.1.0 with sqlite vector storage,…

Release v2.0.0

fix(release): update smoke test expected tools to 14 MCP tools

Release v1.2.0

Release 1.2.0: Multi-provider engine and literal env setup

Release v1.1.0

chore(release): bump version to 1.1.0

The V2.0 write-offloading phase (fix_lint_violations, generate_docs_patch)
is included in the 1.1.0 tarball. Keeps package.json, package-lock.json, and
package-info.ts aligned and updates the README tool list and install URL.

Release v1.0.0-rc.1

fix(ci): update release smoke test tool list and cross-platform npm i…