Respect explicit Spotify configuration availability

Draft
SI
2d ago
+200-1

The release chooser currently offers Spotify sign-in even when the provider client is unconfigured. It now consumes the optional v1 projection, offers Open Spotify for that explicit state, and preserves the uploaded-audio player link without bypassing its existing eligibility checks. Legacy/unknown versions keep existing behavior; malformed v1 fails through the existing unavailable path. The trusted runtime adds a deny-only configuration check.

Tests written first; 53 selected player/callback/recovery tests pass, including real parser/chooser/runtime paths. Scoped types and lint pass. Local production compilation and TypeScript passed after installing exact locked dependencies; page collection is blocked by missing Supabase environment at /api/chat-scope. All four PR CI checks and exact-head Codex source review passed. Bounded native review passed on exact commit a16ad5b8b5edeb0fb24806549a298bc745c78fc9: eight static synthetic fixture pages at desktop and narrow widths, with 16 screenshots, keyboard/focus checks, and eight complete request captures. Independent review found no visual blocker; the coordinator accepted these bounded observations. No live provider journey or host-login proof is claimed.

DRAFT: browser cleanup verification remains incomplete (owned fixture tab closure and temporary viewport reset); the fixture server is stopped. The static synthetic review does not establish authenticated account, host, provider or playback behavior. Delivery order remains recoupable/docs#42 → recoupable/api#1283 → this PR. The coordinator owns final acceptance and all merges. Keep draft and unmerged pending that decision. No publication or provider/settings changes.


Summary by cubic

Stops offering Spotify sign-in when the provider client is explicitly unconfigured.

  • Consumes the optional v1 capabilities projection in player config; strict validation fails closed on malformed shapes, and legacy/unknown shapes keep existing behavior.
  • The release chooser now shows only the Open Spotify fallback with an unconfigured note, except uploaded-audio playback, which keeps its Open player link without bypassing eligibility checks.
  • The sites runtime disables Spotify connect when capabilities report clientConfiguration: "unconfigured", leaving configured and legacy paths unchanged.