@withpica/mcp-sdk 3.23.1 → 3.25.0

package/CHANGELOG.md

@@ -11,6 +11,81 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [3.25.0] - 2026-10-14
+
+> **Publish order:** `asideFromReport` is imported as a value by
+> `@withpica/mcp-utils`'s billing gate. Publish this package (3.25.0) BEFORE
+> the mcp-utils release that uses it, and raise mcp-utils' range to `^3.25.0`
+> in that release; an mcp-utils on an older SDK fails at load.
+
+### Added
+
+- `asideFromReport(fn)`: run requests that still name the current client
+  catalogue, but leave them off the call's report (a check PICA makes for
+  itself, such as the billing gate reading whether the catalogue is paid for).
+- `pica.handovers`: `create` and `send` for catalogues an organisation prepares for a client
+  (`POST /admin/handovers`, `POST /admin/handovers/{id}/send`), with `HandoverCreatedRecord` and
+  `HandoverRecord`.
+- `runInCatalogue(id, fn)` → `{ value, report }` and `CatalogueCallReport` (ADR-333 D7): what the app
+  did with one call's requests in a client catalogue — how many it answered for that catalogue, and
+  each request it refused with `RELATIONSHIP_REFUSED` (path and `reason_code`, from the one
+  refusal shape: `error.code`, `error.details.reason_code`). The MCP server uses it so a tool that fails its parts soft
+  cannot answer "success" with every part refused. `withCatalogue` is unchanged for callers.
+- `withCatalogue(id, fn)`, `currentCatalogue()`, `CATALOGUE_HEADER`, `CATALOGUE_RESOLVED_HEADER` and
+  `CatalogueNotHonouredError` (ADR-333 D7). Every request made inside `withCatalogue` sends
+  `x-pica-catalogue: <id>`. A successful answer without a matching `x-pica-catalogue-resolved`
+  echo throws `CatalogueNotHonouredError` instead of reporting success, so a route that ignores
+  the header can never pass for having acted for the client. The catalogue is held per call
+  (AsyncLocalStorage), so concurrent calls on one shared client never mix catalogues.
+- `relationships` (ADR-333): `list`, `get`, `invite`, `answer`, `revoke`, `stepDown`, `events`,
+  `activity` and `acceptInvite` over `/admin/relationships/**`, with typed records
+  (`RelationshipRecord`, `RelationshipListPage`, `RelationshipEventRecord`,
+  `RelationshipStepRecord`, `ClaimableInviteRecord`). Every step sends `expected_version`.
+- `portfolio` (ADR-333): `list` and `briefing` over `/admin/portfolio`, with
+  `PortfolioClientRecord` and `PortfolioSection` (a section is checked, out of scope, unavailable
+  or failed, never a bare 0).
+- `duplicates.markDifferent(entityType, ids)` and `duplicates.unmarkDifferent(entityType, ids)`
+  for recordings and releases (`POST` / `DELETE /admin/catalog/duplicates/exclusions`).
+
+## [3.24.0] - 2026-10-09
+
+### Added
+
+- `works.getThemes`, `works.setThemes`, `works.proposeThemes`, `works.reviewThemes` and
+  `directory.untaggedThemes` for a song's directory topics.
+
+### Changed — needs a MINOR bump at release
+
+- ⚠️ **`PaginatedResult.total` is now `number | null`** (type change). An
+  explicit `pagination.total: null` from the server means "unknown" — a
+  platform-wide registry the route will not count, or a filter applied
+  after the read — and is passed through as `null` instead of being turned
+  into the page length. Code that does arithmetic on `total` must handle
+  `null`.
+- `requestPaginated`'s fallback `has_more` (when the server sends none) is
+  now `offset + page < total`; it ignored the offset, so every last page of
+  a multi-page result reported more (row-cap T3).
+
+### Added
+
+- **`syncFit` resource**: `query({ work_id?, screen_project_id?,
+song_facts?, limit?, offset? })` (GET `/admin/sync-fit`), with the
+  `SyncFitPage`, `SyncFitRow`, `SyncFitProduction`, `SyncFitSongFacts` and
+  `SyncFitMeasured` types.
+- `works.getThemes`, `works.setThemes`, `works.proposeThemes`, `works.reviewThemes` and
+  `directory.untaggedThemes` for a song's directory topics.
+- Page methods that return `{ data, total, hasMore }` — the real total —
+  alongside the existing `list()` calls, whose return types are unchanged:
+  `agreements.listPage`, `bookings.listPage`, `licensing.listEnquiriesPage`,
+  `partyClaims.listPage`, `releases.listPage`, `sessions.listPage`,
+  `collaborators.listInvitesPage` / `listIncomingPage`,
+  `publishers.listPage` and `labels.listPage` (total `null`: platform-wide
+  rows are not counted; `labels.listPage` also takes `ids` for a lookup by
+  id). `custody.list` takes `offset`.
+- `works.getAgreements(workId)` — the agreements linked to one work.
+- `enrichment.previewBulkRejectProposals(input)` — what a bulk reject
+  would reject, resolved by the same server-side resolver, writing nothing.
+
 ## [3.23.1] - 2026-10-07
 
 ### Fixed