Document pending player capability observations
Player configuration reads do not yet distinguish client/destination configuration from unknown premium eligibility. This documents an optional pending capabilities v1 projection for authorized GET/MCP get and trusted metadata/session responses, without changing create/update schemas or existing operation availability. Corrects both metadata GET and session POST descriptions: GET never creates or resumes a session; POST requires provider and parent.
All 166 docs tests, types, lint, contract checks and production build passed. Generated docs are included; the existing API source pin is retained and only the changed specification hash is refreshed. This is the Docs-first contract for app#2107, not a claim of deployed capabilities or host identity. Root controls merge; API and App companions follow.
Summary by cubic
Documents a pending optional capabilities v1 configuration projection for player reads and trusted player responses, without changing create/update schemas or current operation behavior.
Also corrects two existing API descriptions: metadata GET never creates a session, and session POST requires provider and parent. Added a test verifying that pending capabilities do not alter existing availability and that create/update responses still use the base PlayerResource schema.
Migration
- The
capabilitiesfield is optional; clients that omit or get an unsupported version keep existing behavior. - Premium eligibility, token status, scope status, and playback support are always
unknownin v1 and grant no permission.