PolyhydraGames.ScopedAccess 0.1.0

PolyhydraGames.ScopedAccess

Reusable scoped-access and join-code contracts for PolyhydraGames apps.

This package captures the shared pattern used by ChannelCheevos access grants, Batocera resident-agent onboarding, future Kodi/desktop bridges, and player session joins:

join code or bootstrap request -> pending request -> approval queue -> scoped grant -> issued credential -> revoke/expire/audit

Tags

• polyhydra-games-scoped-access
• scoped
• access
• playback
• signalr
• docs

Design rules

• Human-friendly join codes, such as dbc-z41, are locators/request handles, not long-term bearer secrets.
• Runtime apps own controllers, UI, SignalR hubs, storage, and deployment.
• This package owns reusable DTOs, status transitions, scope normalization, join-code formatting, redaction, and small host-pluggable interfaces.
• Hosts define app-specific subject kinds and scopes, e.g. batocera-agent, kodi-agent, player-session, kodi:playback:control.

Join-code UX and security model

• Join codes are short-lived locators for a pending request, not bearer secrets.
• A host should assign a namespace that matches the subject or surface, such as dbc, batocera, kodi, cc, or web.
• Keep the join-code TTL short enough that it is useful for human handoff but not useful as a replay token after approval.
• Treat the namespace + code pair as the lookup key and rate-limit validation attempts; the format is intentionally human-sized, so the security boundary comes from expiry, uniqueness, and throttling rather than code length alone.
• Issue a separate high-entropy credential after approval. Do not reuse the join code as the issued credential, transport token, or session secret.
• Redact issued credentials in logs and UI summaries; if you need a display form, show a redacted credential or fingerprint, not the full value.

First consumer targets

• ChannelCheevos access-grant queue and Batocera-style resident-agent approvals.
• Future Kodi station-agent onboarding.
• cc-desktopbridge connection approval.
• Game/player join-code flows.

Consumer recipe

See docs/consumer-recipe.md for the PackageReference pattern and the host-owned endpoint/UI/storage split.

Build

dotnet test -p:RestoreIgnoreFailedSources=true
dotnet pack src/PolyhydraGames.ScopedAccess/PolyhydraGames.ScopedAccess.csproj -c Release -o artifacts/packages