v1.1.1

Fixed

• Plain-English signup verification context. Questions such as “where is email verification implemented during signup?” now prioritise the registration controller, OTP verification, and unverified-login flow ahead of generic email operations.
• Readable terminal context reports. otito context now presents its detailed report with colour-aware sections, emojis, ranked hotspots, focused route summaries, tests, commands, and an agent handoff. Markdown artifacts and JSON output remain unchanged.

Added

• Signup verification retrieval evaluation. The scored corpus now protects the plain-English authentication query against future ranking regressions.

v1.1.0

Added

• Harness execution eval. otito eval --harness now proves that Otito infers and can run the encoded install, test, typecheck, and build commands against an isolated, committed fixture. npm run eval:harness is part of the release quality gate.

Safety

• Fixture-only execution boundary. Harness execution accepts only vetted package-manager command forms, disables install lifecycle scripts, applies a timeout, and rejects corpus entries outside Otito's committed evals/fixtures directory. It never executes a command inferred from a customer repository.

v1.0.3

Fixed

• Trustworthy impact evidence. Change impact now surfaces every mapped file from the requested Git diff as exact evidence, preserves the heuristic-only scorecard, and reports unmapped files explicitly.
• Read-only repository inspection. Code-map caching now lives in a per-user external cache rather than creating .otito/index.json inside inspected repositories.
• Composite review statistics. Review summaries now report the actual additions and deletions from the PR comparison.
• Generated artifact hygiene. Formatting ignores legacy generated context reports so source validation reflects the checked-in source.

v1.0.2

Fixed

• MCP Registry ownership namespace. The manifest and published package now use the exact GitHub OIDC namespace granted to Bashbop: io.github.BASHBOP/otito. This allows the signed release workflow to publish the server to the MCP Registry.

v1.0.1

Fixed

• Trusted npm publishing. Releases now use GitHub Actions OIDC for provenance; the temporary bootstrap token path has been removed.
• Colour-stable release validation. Terminal colour settings no longer block the release test suite.

v2.6.0

Added

• Automatic staged pre-commit Gate. repoctx gate --staged now evaluates exactly the files already staged for commit, provides an opt-in Git hook installer, and records scope-aware receipts. The same staged safety check is available through the built-in MCP server for IDE and agent integrations.

v2.5.0

Release note

• Version 2.4.0 was prepared in source but was never tagged or published. Version 2.5.0 is the first public package since 2.3.1 and includes the complete change set below.

Added

• Load-bearing convergence evidence in merge gates. repoctx gate can now recompute a task-to-diff convergence score, enforce --min-convergence, and verify a supplied --receipt; the same options are available through the MCP review gate so agents and humans can require matching intent before merge.
• Tieline contract evidence in local gates. Repositories with tieline.config.json now receive deterministic frontend-to-backend contract-drift results as first-class Gate evidence.
• Bouncer compliance evidence in local gates. Repositories with bouncer.config.json now receive configured compliance-control findings with explicit pass, warning, or fail status.
• Aiglare AI-governance evidence in local gates. Setting REPOCTX_AIGLARE=1 adds irreversible AI-surface checks to the Gate receipt, including blocking guardrail failures.
• TypeScript/JavaScript class methods in the code map so Nest services expose sendX / resolveY symbols (including arrow property methods), not only top-level classes/types.
• Context engine v2 answer-shaped packs: multi-token method hotspots, domain diversification in primary files, plural/British spelling token variants, and topic→domain implementation boosts so queries like email branding land on email.service.ts instead of flooding with booking controllers.
• Index cache version bump to 5 so existing .dev-context/index.json files regenerate and pick up method symbols.
• repoctx-self-improve skill (gated self-eval loop): score context gaps, add corpus/fixture cases, fix ranking/extractors, verify with score-gap.mjs — commit/PR only when asked.

Changed

• Gate evidence engine v2 resolves configured, workspace-local, Repoctx-local, IDE-bundled, or PATH tool binaries without shell-composed commands and records their structured evidence in the durable Gate report.
• Durable post-merge audit reconciliation now runs after successful CI, recovers Dependabot auto-merges that suppress push workflows, validates and backfills missing first-parent commits, archives the incomplete pilot v1 ledger, and persists the verified canonical hash chain on an audit-ledger branch plus per-commit artifacts.
• CI trigger and dependency maintenance policy now runs branch validation once per PR, reserves push validation for main, adopts actions/setup-node@v7, and requires explicit migration work for TypeScript major upgrades.

Fixed

• Historical attestation metadata now resolves the PR, author, and commit time from the commit being attested instead of whichever commit happens to be checked out.
• Blocking audit verdicts are now recorded faithfully instead of treating a valid nonzero FAIL result as unavailable and silently replacing it with diff fallback.
• Release documentation now matches npm and MCP Registry OIDC trusted publishing instead of referring to a removed NPM_TOKEN flow.

v2.3.1

Fixed

• Ship evals/ in the npm package so repoctx eval --accuracy works from a global install; tarball smoke now verifies it.
• Consolidate accuracy eval fixtures under evals/fixtures/ so the published tarball is self-contained (no dependency on codex/skills/.../evals/files).
• Sync MCP docs to 13 canonical tools (agent_experience, convergence_score added in 2.3); README, migration doc, and MCP workflow guide updated.
• Add project .cursor/mcp.json so Cursor loads repoctx MCP from a local checkout without a global install.
• Link audit-pilot from the trust-layer demo walkthrough as the post-merge attestation example.
• Post-merge attestation CI on pushes to main via scripts/post-merge-attest.sh.
• tests/gh.test.js and tests/attest.test.js for gh.js and audit-chain verification.
• Procedure skills under codex/skills/repoctx-{context,review,scope}/.
• docs/MIGRATION-3.0.md pre-migration checklist for the v3.0 alias removal.

v2.3.0

Deprecated

• The dev-context command alias is deprecated and will be removed in v3.0.0. Use repoctx. Invoking the CLI through the dev-context bin now prints a deprecation warning to stderr (never on --json stdout). The .dev-context/ output directory is unaffected — it is not part of the deprecation.

Added

• repoctx dashboard renders a local usage & performance UI. A new opt-in telemetry layer records one JSONL line per CLI run and per MCP tool call to ~/.dev-context/usage.jsonl (command, arg shape — keys only — latency, outcome, and the value signals each command already produces). repoctx dashboard aggregates that log (plus existing .dev-context artifacts and recent git history) into ONE self-contained HTML file — no server, no chart library, no network — with interpretation tooltips on every tile and chart and a "what this can't show" honesty panel. Capture is off by default and strictly local: gated by the telemetry config key or REPOCTX_TELEMETRY, forced off under CI, never written to stdout or the MCP JSON-RPC channel (a determinism-firewall test enforces byte-identical output on/off), and error text is reduced to a code/class so no paths leak. Manage it with repoctx telemetry status|on|off|clear.
• repoctx ax "<task>" --path . scores Agent Experience (AX). A single 0–100 number for "how cheap and safe is it for an agent to make this change here?", blending Changeability (token cost), Containment (blast radius), Guardrails (tests/validation/CODEOWNERS/CI), and Clarity. Deterministic and composed from the existing impact, tokens, and codeowners engines — no new analysis. Supports --json and --out, and is exposed over MCP as the agent_experience tool (the MCP surface bumps from 11 to 12 tools). See docs/07-harness-thesis/ax-score-spec.md.
• repoctx converge "<task>" --base <ref> scores convergence. A deterministic 0–100 measure of the distance between a stated task (intent) and the actual git diff (execution), with sub-scores for Coverage (did the intent happen?), Scope (did only the intent happen?), and Risk alignment (did unrequested drift land on risk-sensitive paths?). Emits a recomputable, timestamp-free receipt as durable evidence. Composed from the change_impact diff comparison and the shared risk vocabulary — no model, no new analysis. Supports --json and --out, and is exposed over MCP as the convergence_score tool (the MCP surface bumps from 12 to 13 tools). See docs/09-convergence-thesis/convergence-score-spec.md.
• postinstall runs repoctx doctor after a global install. npm install -g @nugehs/repoctx now prints an environment readiness summary. The hook is guarded: it runs only for global installs (npm_config_global=true), skips in CI and when REPOCTX_SKIP_POSTINSTALL is set, and always exits 0 so it can never fail an install.

v2.1.0

Release v2.1.0. See CHANGELOG.md for details.