Expose bounded player configuration capabilities

SI
3d ago
+202-3

Authorized player reads and trusted player configuration now expose capabilities v1: Spotify client-ID presence and release-destination presence, with Premium, token, scope and playback observations explicitly unknown. HTTP and MCP use the same actual domain projection. Existing auth, errors, GET no-session behavior, POST acquisition, provider calls and credential boundaries stay unchanged.

Tests written first; 89 player tests pass, including actual HTTP/MCP and public GET consumers, fresh/resumed sessions and unknown-state boundaries. Scoped types/lint pass. Independent exact-head review passed at 18fc2c4afef71dcd0a323c819fbce412db41e835 after extracting the read response and correcting premium eligibility wording. All six successor CI workflows passed, including the full unit-test workflow and final TypeScript checks. Exact-head Codex review completed without findings; Cubic reported zero issues. All review threads are resolved.

Depends on pending Docs contract recoupable/docs#42 merging first. Root owns merge; App consumer is separately draft pending native acceptance. This is a bounded app#2107 slice, not host identity or full Fans/Widgets acceptance.


Summary by cubic

Adds a capabilities block to GET responses on player reads, exposing only configuration observations: whether a Spotify client-ID is configured and whether the release has a destination. Spotify Premium eligibility, token, scope, and playback support are explicitly reported as unknown.

  • Authorized HTTP, MCP, and public GET reads all project the same capabilities.
  • Public metadata GET stays credential-free, creates no session, and performs no provider work.
  • Existing auth, error, no-session, and ownership boundaries are unchanged.