@withpica/mcp-server 2.95.4 → 2.96.1

package/.claude/settings.local.json

@@ -0,0 +1,5 @@
+{
+  "disabledMcpjsonServers": [
+    "pica-directory"
+  ]
+}

package/CHANGELOG.md

@@ -11,6 +11,40 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [2.96.1] - 2026-08-31
+
+First npm release since 2.95.4 — carries everything below (the discover
+changes have been live on the hosted connector since promote #2061; stdio
+clients get them here). 2.96.0 was published from an unmerged branch and is
+deprecated; do not use it.
+
+### Fixed
+
+- **`pica_import_validate` surfaces warnings on a VALID result.** A warning
+  does not make a row invalid, so `valid: true` can carry warnings — e.g. a
+  works CSV mapped to `release_year` (release-level data; a newly created
+  work has no release) is receipted at row 0. The tool used to answer "All N
+  rows are valid. Ready to import" and drop the warning, so the agent
+  executed blind (2026-08-30 production finding, PR #2072 / promote #2074).
+  Warnings now ride the valid branch in the text and as `warnings` in the
+  structured data. The SDK's `ImportValidation.errors` rows carry the wire
+  field `error` (with `message` kept for normalising callers).
+
+### Changed
+
+- **The ten tools slated for removal in 2.96.0 remain, `removal_target`
+  extended to 2.97.0** (`pica_recording_credits_bulk_update`,
+  `pica_statements_list`, `pica_documents_list`, `pica_documents_read`,
+  `pica_projects_list`, `pica_releases_list`, `pica_releases_get`,
+  `pica_releases_bulk_attach_tracks`,
+  `pica_releases_attach_track_by_identifier`, `pica_notes_list`). This
+  release exists to ship the validate-warnings fix; removing tools is its
+  own change with its own review, not a rider on it.
+
+- **`pica_discover({ query })` no longer scores the asker's own words as the entity.** Determiners, pronouns, prepositions and light verbs (`my`, `the`, `get`, `list`, `find` …) are dropped before ranking. "start my music catalogue and import my songs" led with three `pica_my_*` tools because "my" matched their domain segment; it now leads with the import tools. A query made only of such words matches nothing.
+- **Query mode carries the fresh-org import line.** The ADR-294 hint ("on a fresh or empty org, run `pica_dashboard_briefing` first … paste a spotify album or playlist link") was only on the no-args category map; it is now on every query response, hit or miss.
+- **Tools the caller cannot run on this connection rank last and are flagged.** Shortlist rows and `pica_tool_details` gain `callable_on_this_surface: false` plus a `surface_note` when the tool is on another surface (stdio / lobby) or needs a scope the connection does not hold — the judgement the HTTP dispatcher enforces at `pica_execute` time (installed only while the inner gate is in enforce mode). An existing scope or destructive-tier `callable_note` is kept beside it, and the `invoke` line on a flagged detail says the call will be refused instead of "pica_execute executes every tool returned here". Rows for callable tools are unchanged (no new keys). A capped shortlist keeps at least five tail rows for flagged tools and lets them fill what visible rows leave, so a gated capability reads as gated, not missing, and a narrow scope never shrinks the list. Query-mode `cache_until` is now one hour (the rows are per-connection); the full map keeps its day.
+
 ## [2.95.4] - 2026-08-25
 
 An agent-readability release. Nothing about auth, tiers or tool behaviour changes; what changes is what a tool **tells** an agent about itself, and the shape of a refusal.