GoldenMatch

Controller telemetry visible from every surface. No algorithm changes vs 1.13.0 — same DQbench / DBLP-ACM / Febrl3 / NCVR numbers — but you can now read what the AutoConfigController decided from every interface and round-trip the committed config (including Path Y negative-evidence) through SQL.

Surfaces aligned in this release

• Web — ControllerPanel in Workbench + GET /api/v1/controller/telemetry (PR #156)
• TUI — new Controller tab + Ctrl+A keybinding (PR #157)
• CLI — new goldenmatch autoconfig subcommand + --show/hide-controller on dedupe (PR #158)
• Postgres + DuckDB extensions — goldenmatch_autoconfig + gm_telemetry + goldenmatch_dedupe_full (PR #159)
• MCP — auto_configure rewired to the controller + new controller_telemetry tool (PR #161)
• A2A — new autoconfig + controller_telemetry skills (10 → 12 skills) (PR #161)
• REST — POST /autoconfig + GET /controller/telemetry on goldenmatch serve (PR #161)
• AgentSession — .autoconfigure() + last_telemetry cached on .deduplicate() / .match_sources() (PR #161, #169)

Every surface delegates to goldenmatch.web.controller_telemetry.serialize_telemetry. Write one parser, reuse across all of them.

Infrastructure

• New CI lanes rust_pgrx (matrix PG 15/16/17) + duckdb_extensions (PR #160) cover previously-unverified surface area.
• New publish-mcp.yml auto-syncs the MCP Registry on every PyPI publish (PR #165, #167).

Fixed

• AgentSession.deduplicate(config=None) / match_sources(config=None) were passing a legacy heuristic config explicitly, which suppressed the controller. Now fixed (PR #169). Explicit-config calls now clear last_telemetry to prevent stale-blob leaks across calls.

See CHANGELOG.md for the full per-PR breakdown.