@withpica/mcp-server 2.69.0 → 2.73.0

package/CHANGELOG.md

@@ -11,6 +11,260 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [2.73.0] - 2026-06-12
+
+ADR-264 WS2 verify-before-assert + the WS4 front-door prerequisite (bulk
+recording credits) + ADR-268 WS1 party claims / WS2 identifier-based party
+dedup / WS5 ownership transfer types + the ADR-267 calibrated-question voice
+contract. Also removes the never-functional `pica_team_*` tools and the
+long-deprecated `pica_dashboard_pulse`.
+
+### Added
+
+- **`pica_party_claim_invite` + `pica_party_claim_status`** — ADR-268 WS1
+  party org claim spine. `pica_party_claim_invite` sends an artist-anchored
+  claim invite for an unclaimed label/distributor/publisher organisation
+  (the user-supplied recipient email is the consent + identity anchor; the
+  single-use link redeems on the public claim landing — redemption makes the
+  claimant the org's owner, flips verification pending→verified and billing
+  hibernated→trial, and mints an active org-to-org connection with the
+  inviting catalog, never membership). Concurrent claims freeze both sides
+  as `disputed` for founder adjudication, and the tool says so instead of
+  pretending the email went out. `pica_party_claim_status` lists the claims
+  the calling org has sent with their lifecycle status. Registered in the
+  `labels` discovery category; tool count tripwire 282 → 284.
+- **`pica_recording_credits_bulk_update`** — ADR-264 WS4 prerequisite. Apply
+  one credit set across many recordings in a single call: target a release
+  (`release_id` — every recording on its tracklist) or an explicit
+  `recording_ids` list, plus a `credits[]` batch (`credited_name` + `role`
+  per entry, optional `person_id` / `split_percentage` / `split_type` /
+  `notes`). One album's production credits stops being 30 sequential
+  per-recording calls. Existing (recording, credited name, role) rows are
+  skipped, never overwritten — re-running is safe; `dry_run: true` previews
+  the exact per-row `would_create` / `would_skip_existing` decision set the
+  execute path uses. Validation is all-or-nothing with per-problem detail
+  (invalid input applies NOTHING); application returns per-row
+  `created` / `skipped_existing` results. Caps: 100 recordings, 50 credits,
+  500 total rows per call. Backed by the new
+  `POST /api/admin/recording-credits/bulk` route (org-scoped at every step:
+  release, tracklist, recordings, and person_ids must all belong to the
+  caller's organisation).
+- **`pica_works_verify_registrations`** — ADR-264 WS2 truthful diagnosis. Verify
+  the registration status of up to 25 works. `mode: "check"` looks each work up
+  at the MLC (ISWC → title + writer IPI → title + primary-artist name) and
+  records what the lookup PROVED: a found registration is written as a positive
+  society fact (and any stale negative assertion is cleared); a clean not-found
+  becomes a `verified_absent` assertion with a lookup receipt. Lookup errors and
+  works with no usable identifiers write NOTHING (`lookup_failed` /
+  `insufficient_identifiers`). `mode: "confirm_unregistered"` records the user's
+  own confirmation (optional `society_code`; omitted = "not registered with any
+  society"). `works_without_registrations` rows on `pica_dashboard_attention`
+  now carry an `evidence` block (`unverified_absent` / `verified_absent` /
+  `user_confirmed_absent` with `verified_via` + `checked_at`) reflecting these
+  assertions.
+- **`unconnected_collaborators`** attention class (taxonomy gap, f0266f09
+  gap #6): people credited on the org's works with no linked PICA account now
+  appear on `pica_dashboard_attention` / briefing totals / `pica_count_explain`
+  — one shared compute with `briefing.unconnected_collaborators` so the
+  surfaces structurally cannot drift. drill_down_skill null until a skill
+  covers collaborator connection.
+- **Decision blocks (calibrated questions)** — `pica_find_duplicates` groups,
+  the `pica_merge_duplicates` MERGE_BLOCKED_PROVENANCE error, and
+  `pica_works_verify_registrations` mode:"check" (when works couldn't be
+  verified) now carry a `decision` field: a question with 2-3 options,
+  plain-language consequences, and a safe default — no UUIDs in any decision
+  text (a UUID-shaped title degrades by omitting the block, never failing the
+  call). Always additive: the structured payload carries everything the block
+  says. `pica_dashboard_briefing` now carries `user_message` — one
+  ready-to-say lowercase sentence in the curiosity register (no loss framing
+  on unverified counts).
+
+### Changed
+
+- **`pica_recording_custody_assign`** — ownership transfer types are live
+  (ADR-268 WS5, the ADR-262 fast-follow): `transfer_type` now accepts
+  `assignment` (title transfers) and `full_transfer` (ownership AND control)
+  alongside the v1 control/possession types. An ownership leg also moves the
+  recording's master ownership splits append-only in the same transaction —
+  the transferor's active era closes (`end_date`), the transferee's opens —
+  and the credit layer never moves. Honest-gap refusals (400, typed codes):
+  a partial percentage with more than one active owner
+  (`PARTIAL_TRANSFER_AMBIGUOUS`), a transfer exceeding the transferor's
+  share (`INSUFFICIENT_TRANSFEROR_SHARE`), or a percentage outside (0,100]
+  (`INVALID_PERCENTAGE`) — nothing is ever silently lost.
+- **`pica_labels_create`** accepts an optional `identifiers` object
+  (`musicbrainz_label_id` / `isni` / `label_code` / `discogs_label_id` /
+  `wikidata_id` / `deezer_label_id`) — ADR-268 WS2. Dedup is now
+  identifier-first: supplied identifiers resolve to the global label identity
+  and an org already bridged to that identity is returned
+  `already_existed: true` EVEN when the supplied name differs;
+  case-insensitive name matching (ADR-265 behaviour) stays as the fallback,
+  and a name-matched org missing the bridge is backfilled when an identity
+  was resolved. Param addition only — no new tool.
+- **`first-session` skill** now carries the calibrated-question library (ADR-267
+  Step 1): open-over-closed decision questions, diagnosis labels, no-oriented
+  phrasing for destructive moves, options-with-consequences, evidence-gated
+  stakes, and a no-UUIDs-in-user-facing-text contract. Specialist skills adopt
+  the same grammar incrementally; the WS4 front-door skill embeds it at birth.
+- **`pica_works_create` / `pica_works_update` `mood` param description** now
+  states the value is stored on the work's primary recording's audio traits
+  (recording-grain, ADR-266 Stage 2c) — caller contract unchanged.
+
+### Fixed
+
+- **Review-link contract** — server instructions told every agent to share
+  `withpica.com/workspace?type=<entity>&id=<id>` after writes; now the
+  schema-direct `/inspect/<feature>/<id>` shape (both byte-parity copies).
+  uploads/audio/exports tool descriptions point users at `/inspect`.
+
+### Deprecated
+
+- **`pica_import_from_spotify`** — use `pica_import_streaming_link` (same
+  two-step flow, also supports Deezer). Structured
+  `{deprecated, removal_target: "2.74.0"}` in TOOL_METADATA; the new
+  lint-mcp-tools deprecation-expiry check BLOCKS any publish at or past the
+  removal target, so this cannot overstay like pulse did.
+- **`briefing.unverified_writers`** count source — `briefing.unenriched_writers`
+  is the canonical name (matches the actionable-issues taxonomy class); the
+  alias shares one definition and is accepted until 2.74.
+
+### Removed
+
+- **`pica_team_*` (all 5: `pica_team_list` / `pica_team_get` / `pica_team_invite`
+  / `pica_team_update_role` / `pica_team_remove`)** — founder decision
+  2026-06-11. The backing routes (`/api/admin/team/*`) are session-only BY
+  DESIGN (ADR-248: team membership is human-only), so every bearer/MCP caller
+  has always received a hard 401 — the tools never worked for any agent and
+  never could. Removing them is honesty, not a regression: agents stop being
+  advertised a capability that structurally cannot succeed. Team membership
+  stays managed by humans in `/settings`. Also removed: the `team` discovery
+  category, the `pica_team_remove` destructive-confirmation case, recovery
+  hints, cost-model entries, and the `set-up-workspace` skill's Block 5 now
+  points users at `/settings` instead of the tools. Tool count tripwire
+  287 → 282; destructive tripwire 20 → 19.
+- **`pica_dashboard_pulse`** — deprecated since ADR-247 with a removal window
+  that passed (prod telemetry: 3 calls all-time, exploratory).
+  `pica_dashboard_briefing` is the canonical attention surface; pulse's
+  revenue-at-risk/deadline predicates retired with it (they disagreed with
+  the briefing coherence contract). Tool count tripwire 288 → 287.
+- **`suggested_skill`** alias dropped from `pica_dashboard_attention` rows
+  (deprecated 2026-05-22; soak window long passed; zero non-test consumers).
+  `drill_down_skill` is the canonical field.
+
+## [2.72.0] - 2026-06-10
+
+ADR-264 WS1.3 — recordings/releases dedup + merge (last trust-floor gap).
+
+### Changed
+
+- **`pica_find_duplicates`** — `entity_type` now covers `releases` and
+  `recordings` (added in 2.72.0); description explicitly names the UPC and
+  ISRC grouping keys so callers understand the detection basis.
+- **`pica_merge_duplicates`** — extended to cover `recordings` and `releases`
+  (+ singular aliases `recording` / `release` for backwards compatibility).
+  - `recordings`: merges via `merge_recording_atomic` RPC — credits, splits,
+    and release-track links are deduped by their natural keys; winner's NULL
+    fields (ISRC, duration, streaming IDs, artist name, artwork) are back-filled
+    from the first loser that has a value.
+  - `releases`: merges via `merge_release_atomic` RPC — tracks are rehomed
+    (dedup by recording_id within the winner's tracklist); UPC, release date,
+    artwork, and label/distributor org links are gap-filled from losers.
+  - **PROVENANCE BLOCK**: a recording loser with `recording_custodians` rows
+    (ADR-262 append-only custody chain) blocks the merge. The tool returns a
+    structured `MERGE_BLOCKED_PROVENANCE` error with `blocked_ids`, the `remedy`
+    ("custody chains are append-only; transfer custody first or keep both
+    recordings"), and `next_tool: "pica_recording_custody_assign"` so the AI can
+    route directly to the safe resolution path.
+
+### Recovery hints
+
+- `MERGE_BLOCKED_PROVENANCE` added to the `pica_merge_duplicates` hint registry
+  → `pica_recording_custody_assign`.
+
+## [2.71.0] - 2026-06-10
+
+ADR-265 release parties and invites — label/distributor org creation + recording/release-grain invite targets. Requires `@withpica/mcp-sdk@^1.39.0`.
+
+### Added
+
+- **`pica_labels_create`** — create an unclaimed label or distributor organisation.
+  Accepts `name`, `org_type` (`label` | `distributor`), and optional `country` /
+  `website` / `contact_email`. Server-side deduplication is catalog-wide across
+  both party types: a case-insensitive name match returns the existing record
+  with `already_existed: true` rather than creating a duplicate. The returned
+  `id` can be assigned to `releases.label_organization_id` (via
+  `pica_releases_update`) or `releases.distributor_organization_id` to formally
+  link a release's label or distributor.
+- **`recording_id` / `release_id` targets on `pica_collaborators_invite`** — in
+  addition to the existing `work_id`, invite calls now accept exactly one of three
+  target ids (`work_id` | `recording_id` | `release_id`). Recording-grain invites
+  surface a claim scoped to the named recording's credits; release-grain invites
+  surface a claim that verifies all the invitee's credits across every recording on
+  the release. Exactly-one-of validation is enforced server-side (400 if zero or
+  multiple targets are supplied).
+
+### Fixed
+
+- **`pica_labels_query` always returned "Found 0 labels"** — an SDK envelope
+  double-unwrap (`labels.list` read `.data` off the already-unwrapped array)
+  meant the tool had returned empty results regardless of catalog state since
+  it shipped (2026-04-14). Fixed in `@withpica/mcp-sdk@1.39.0`.
+- **`pica_labels_create` dedup messaging now sees `already_existed`** — the
+  same envelope unwrap stripped the `already_existed` sibling flag, so every
+  successful create tripped the no-data guard and the "already exists — link
+  it instead" guidance never fired. The SDK now returns the label object
+  directly with `already_existed` inside it.
+
+## [2.70.0] - 2026-06-10
+
+ADR-264 WS1 trust floor — conservative-by-default enrichment, truthful tool
+outputs, and the reviewable enrichment queue. Requires `@withpica/mcp-sdk@^1.38.0`.
+
+### Added
+
+- `pica_enrichment_proposals_bulk_reject` (mutating, `dry_run` preview):
+  reject up to 100 pending enrichment proposals by explicit ids OR a filter
+  (`rule_id` / `source` / `max_confidence`). Per-proposal effects identical to
+  `pica_enrichment_proposal_reject` (permanent content-hash suppression).
+  `dry_run` resolves the real affected set — the filter path queries the live
+  list, no fake previews.
+- `pica_enrichment_proposals_list` gains `min_confidence`, `max_confidence`,
+  and `created_after` filters, so a caller can isolate the batch they just
+  triggered from accumulated stale low-confidence noise.
+- `pica_releases_list` gains `offset` pagination with an honest envelope
+  (`count`, `offset`, `has_more`, `next_offset`) — every release is reachable;
+  no more mid-array ~100KB truncation dead-end.
+
+### Changed
+
+- Enrichment behaviour (backend, surfaced through proposals): official
+  YouTube " - Topic" channel uploads now classify as `master` and the
+  `artist_title_to_youtube` rule defaults to enriching the existing master
+  recording (UPDATE proposal attaching `youtube_video_id`/`youtube_url`)
+  instead of minting a phantom `alternate` recording; creating a new
+  recording now requires affirmative low-sameness evidence (version markers
+  or >3s duration delta). Proposals carry a `sameness_evidence` signal.
+- `pica_import_from_spotify` preview wording: duplicates are reported as
+  "already in catalog (will be skipped, not modified)" — the preview no
+  longer promises an enrichment the executor does not perform.
+- `pica_execute` hardening: the `WRAPPED_ARGS_MISSING` transport error now
+  fires when ANY required field of the wrapped tool is missing (partial
+  client-side argument strips included), naming `missing_required_fields`.
+  The nested `args` object is the canonical call shape.
+
+### Fixed
+
+- `pica_enrichment_proposals_list` no longer renders the literal
+  `"? pending proposal(s)"` when the backend returns an unexpected shape —
+  that case is now a structured `UNEXPECTED_RESPONSE_SHAPE` error (with
+  `structuredContent`), not a fake count.
+
+### Removed
+
+- Dropped the unused `mppx` runtime dependency. No `src/` consumer has existed
+  since the MPP unit tests were deleted; the earlier cleanup left it in place
+  "to avoid lockfile churn" and asked the next publisher to drop it — done.
+
 ## [2.69.0] - 2026-06-08
 
 ### Added