Resolve music entities across trusted sources - #310
Open
guidefari wants to merge 3 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds provider-aware music resolution with exact Spotify and Deezer source adapters, Odesli cross-platform link discovery, and typed MusicBrainz identity evidence. Tracks and albums can be conservatively enriched through exact identifiers, while playlists remain bound to exactly one source platform through creation and refresh. Provider provenance, confidence, cancellation, partial-outage behavior, Cover Art Archive fallback, and source attribution are included without changing the public refresh route.
Closes #305
Closes #306
Closes #307
Closes #308
Closes #309
Relates to #300
Test evidence
bun precommitbun run --cwd apps/server test, 464 unit tests and 46 D1 tests passedReview notes
MusicBrainz throttling and caches are shared across service instances within one JavaScript process or Worker isolate. Cross-isolate egress coordination is intentionally deferred at the current scale and must be added before deployment topology or traffic requires a strict global one-request-per-second guarantee. Hosted MusicBrainz use also requires confirming the applicable MetaBrainz terms before commercial production rollout.