@withpica/mcp-server 2.48.0 → 2.50.0

package/CHANGELOG.md

@@ -11,6 +11,31 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+### Changed
+
+- **Tool registry catch path now forwards `error_message` to the audit log (PR #308).**
+  When a tool throws, the registry calls `formatError()` and now passes the
+  parsed `message` through to `logToolExecution` as `error_message`. Pre-fix,
+  every error row in `mcp_audit_log` landed with `error_message=null` because
+  the wire shape stripped the field — even when the wrapper held the
+  underlying cause. Net effect for diagnostics: rows like the 116 silent
+  `pica_merge_duplicates` failures on 2026-04-09 (which couldn't be
+  attributed to any specific cause) will now carry the message going forward.
+  Sister change in `@withpica/mcp-utils` adds the field to `McpAuditEntry`.
+
+- **`pica_integrations_status` advertisement updated to current tools (PR #308).**
+  ADR-179 (commit `dc1bfca72`, 2026-04-21) folded the six per-source
+  `pica_enrich_*` tools into `pica_resolve_work` / `pica_resolve_person` /
+  `pica_resolve_recording` with a `sources:[...]` parameter, then removed
+  them. But `mcp-server/src/tools/integrations.ts` continued to advertise
+  the removed names in the `platformReads` list, the tool description, and
+  the summary prose. Agents reading the advertisement called names that no
+  longer existed → UNKNOWN_ERROR loops on every catalog-enrichment ask
+  routed through MLC/Spotify/MusicBrainz/YouTube/Discogs/ISNI. Now points
+  at the surviving tools with the correct source value. Two regression
+  tests in `integrations.test.ts` lock down that no removed
+  `pica_enrich_*` tool name appears in the advertised `use_via` strings.
+
 ## [2.48.0] - 2026-05-03
 
 ### Changed