@withpica/mcp-server 2.98.0 → 2.99.0

package/CHANGELOG.md

@@ -11,6 +11,104 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [2.99.0] - 2026-09-30
+
+### Added
+
+- **Platform-presence waivers on `pica_integrity_waive`.** New `gap_code`
+  values `PLATFORM_SPOTIFY`, `PLATFORM_YOUTUBE`, `PLATFORM_APPLE_MUSIC` with a
+  required `kind` (`not_applicable` | `restricted`) and reason mark a work that
+  is deliberately not on that platform (e.g. no YouTube by design, a licence
+  rules out Content ID). The platform then drops out of the work's
+  completeness instead of counting as missing; the answer carries the
+  re-scored `completeness`. Owner/admin only. Identifiers and registrations
+  (ISWC, ISRC, IPI, society registrations, writers, splits) can never be
+  waived, and the description says so.
+
+- `original_work_id` on `pica_works_create` / `pica_works_update`: links a
+  modified version (a remix that added writers) to the work it modifies. Same
+  catalogue only; `null` clears it.
+
+### Changed
+
+- **A remix is a recording of the same song unless it adds writers (ADR-324).**
+  `pica_works_create` on a remix-titled work now suggests a recording under the
+  original (`pica_recordings_create`, `version_type: "remix"`, remixer credited
+  on the recording) with the modified-version path beside it
+  (`if_new_writers`), instead of a separate derivative work.
+  `pica_find_duplicates` (works) no longer groups a remix with its original as
+  a duplicate: each remix is paired with its original as
+  `match_kind: "remix_recording"` (move its recordings) or
+  `"remix_modified_version"` (link it), with a `remix` block naming the
+  recordings, any added writers and the action — never "fold the copies".
+  The `catalog-modelling` skill carries the rule.
+
+- `pica_rights_inspect` no longer says amounts are "not computed yet"; it points
+  to `pica_rights_statements` for them.
+
+### Removed
+
+- **The last 11 deprecated tool aliases** (removal target 2.99.0). Each had
+  been a hidden, callable alias of the tool named beside it — ten since the
+  MCP tool-surface consolidation, `pica_royalties_summary` since 2026-09-25
+  (ADR-321 Phase 0). Calling an old name now fails with `TOOL_NOT_FOUND`;
+  the answer (from `pica_execute`, `pica_tool_details` and the hosted
+  connector alike) says the tool was retired in 2.99.0, names its
+  replacement and any argument change, and lists the replacement first in
+  `did_you_mean` when the caller can call it. Use the replacement instead:
+  - `pica_releases_list` → `pica_releases_query`
+  - `pica_releases_get` → `pica_releases_inspect`
+  - `pica_releases_bulk_attach_tracks` → `pica_releases_attach_track` with
+    `items[]` (the old `tracks` field is now `items`)
+  - `pica_releases_attach_track_by_identifier` → `pica_releases_attach_track`
+    with `identifier_type` + `value`
+  - `pica_projects_list` → `pica_projects_query`
+  - `pica_notes_list` → `pica_notes_query`
+  - `pica_documents_list` → `pica_documents_query`
+  - `pica_documents_read` → `pica_documents_inspect`
+  - `pica_statements_list` → `pica_statements_query`
+  - `pica_royalties_summary` → `pica_royalties_blockers` (`work_id` and
+    `limit` carry over; `gap_type` and `priority` have no equivalent)
+  - `pica_recording_credits_bulk_update` → `pica_recording_credits_update`
+    with a `credits` array (same arguments)
+
+  Production use over the 60 days before removal was 4 calls in total.
+
+- **`verified` on `pica_works_query`.** It filtered on a work-level
+  `is_verified` flag that PICA has never stored, so it matched no works
+  whichever way it was set. Passing it now returns `NO_WORK_VERIFIED_FLAG`
+  (the same code `pica_works_verify` returns) and names the filters that do
+  exist: `health_filter: 'low_completeness'`, `completeness_score_lt`, and
+  `pica_works_inspect` for one work.
+- **`verified` / `unverified` counts in the `catalog://stats` resource, and
+  `is_verified` in `works://list`.** Both read the same missing flag, so every
+  work counted as unverified.
+- **`musicbrainz_recording_id` on `pica_works_update` / `pica_works_create` /
+  `pica_works_bulk_update`.** An update used to pass it to the work's
+  recording, but only when the work had exactly one recording, so the same
+  call silently stopped working once a second recording was added (a create,
+  with no recording yet, never stored it). It is now refused with
+  `PHANTOM_FIELD` naming the tool to use instead:
+  `pica_recordings_update {id, musicbrainz_recording_id}`. Work reads still
+  show the recording's MusicBrainz id, and the completeness benchmark still
+  reads it.
+
+### Fixed
+
+- `pica_integrity_waive`'s `gap_code` enum now lists `WORK_SPLITS_ABSENT` and
+  `WORK_SPLITS_INVALID`, which the app has accepted since 2026-08-16.
+- **`pica_rights_statements`** (read:finances) — ADR-321 Phase 3, COMPUTED NOT
+  PAID: direct income and what each party would receive under the song's
+  locked split in force when it was earned, PICA's proposed fee as its own line
+  (shown, never charged), every hold with why / who clears it / since when, and
+  the four measures. With `work_id`, that song's imported society statements
+  checked against the split: each co-writer's EXPECTED amount and the
+  registration check for writer societies; line-up completeness for PPL /
+  SoundExchange.
+- **`pica_rights_record_income`** (write:finances) — record a figure the user
+  gave (or a quoted licensing enquiry's fee), labelled "entered by your agent".
+  No money moves.
+
 ## [2.98.0] - 2026-09-29
 
 ### Deprecated

package/README.md

@@ -65,7 +65,7 @@ Read tools are annotated read-only and are safe to call freely. Write tools repo
 
 ## Tools
 
-341 tools, grouped below by the taxonomy `pica_discover` uses. The server's own `tools/list` is authoritative — not every registered tool is filed under a category yet, so the names below are a map, not a census.
+343 tools, grouped below by the taxonomy `pica_discover` uses. The server's own `tools/list` is authoritative — not every registered tool is filed under a category yet, so the names below are a map, not a census.
 
 **works** — manage your musical works
 
@@ -235,9 +235,9 @@ Read tools are annotated read-only and are safe to call freely. Write tools repo
 
 `pica_royalties_list`, `pica_royalties_get`, `pica_statements_query`, `pica_statements_inspect`, `pica_ingest_statement`, `pica_statements_pending`, `pica_statement_ingest_document`, `pica_royalties_blockers`, `pica_royalties_unmatched`, `pica_royalties_attribute`
 
-**rights** — programmable rights — propose a song, master or share rule for the parties to confirm, check who has confirmed, and see what money would be held and why
+**rights** — programmable rights — propose a song, master or share rule for the parties to confirm, check who has confirmed, see what money would be held and why, and what income would pay each party (computed, never paid)
 
-`pica_rights_inspect`, `pica_rights_status`, `pica_rights_propose`
+`pica_rights_inspect`, `pica_rights_status`, `pica_rights_propose`, `pica_rights_statements`, `pica_rights_record_income`
 
 **selections** — save, recall, and resolve named catalog selections — persisted predicates over the catalogue with an honest coverage report
 
@@ -293,4 +293,4 @@ Read tools are annotated read-only and are safe to call freely. Write tools repo
 
 ---
 
-Generated for `@withpica/mcp-server@2.97.5`. © 2024-2026 Withpica Ltd. All rights reserved. MIT licensed.
+Generated for `@withpica/mcp-server@2.99.0`. © 2024-2026 Withpica Ltd. All rights reserved. MIT licensed.