Clarify API client pattern for external third-party APIs

[Copilot]

Addressed feedback on PR #180 regarding the use of ky vs instance() in src/helpers/musicbrainz.ts.

Analysis

The instance() function from @/api is designed exclusively for Spotify API calls:

• Configured with Spotify Bearer token authentication
• Automatic token refresh on 401 responses
• Hardcoded Spotify API base URL

MusicBrainz (and other external APIs like Discogs, Wikidata) require:

• Different base URLs and authentication mechanisms
• Custom headers (User-Agent for MusicBrainz, Discogs token for Discogs)
• No Spotify credentials

Current Implementation Pattern

External APIs consistently use ky.create() with custom configuration:

// src/helpers/musicbrainz.ts
const musicbrainzClient = ky.create({
  headers: { "User-Agent": USER_AGENT },
  prefixUrl: MUSICBRAINZ_API_URL,
  retry: { limit: 1, statusCodes: [429, 503] },
  timeout: 10000,
});

Using instance() would send Spotify auth tokens to third-party APIs, creating both functional and security issues.

Requested Clarification

Awaiting guidance on whether a different abstraction pattern is desired for external API clients while maintaining proper authentication isolation.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.