# Arena collectible review connection and recovery

Arena implements the browser request/status layer for Hybrid-ID's merged private
collection picker (source 47ea7cc, contract 2026-10-08.3). This is **implemented,
inactive**: `ARENA_COLLECTIBLE_REVIEW_ENABLED` defaults false. Identity, Core,
provider and portal deployment plus real personal issuer acceptance are still
required. There is no approval/consume/mint/purchase endpoint in Arena.

## Browser workflow

1. Sign in to Arena and open `/collectibles`. Select an immutable v2 brief
   created from your own permanent replay and verified recording commitment.
2. When enabled, **Continue with Hybrid-ID** establishes a separate short-lived
   `openid` connection. The existing Arena client uses PKCE S256, nonce, state,
   signed ID tokens and its registered form-post callback. It must resolve to
   the same still-active Arena account. This does not disclose asset inventory
   or authorize creation. Ordinary sign-in and Steam consent are unchanged.
3. **Request issuer review** commits one original UUID plus the exact v2 proposal
   before any network call. Browser input is only `{action:"request",brief_id}`.
   Name, metadata, supply and provenance come from the immutable owned brief.
   No issuer vault/profile or collection identifiers are accepted.
4. Follow the exact Hybrid-ID review link. Choose an eligible collection in your
   private Hybrid-ID portal, explicitly share that selection, and separately
   approve or decline the exact terms. Arena cannot browse collection inventory.
5. Return and select **Refresh review status**. A saved status is labeled as a
   last-checked observation. Approved terms are not issuer authority, media
   rights, asset creation, minting, publication or value movement.

## API and failure recovery

`GET /api/collectibles/review?brief_id=<32 lowercase hex>` requires the owning
Arena session. It returns enabled, connected, request:null or an encrypted-store
projection containing request_id, review and observed_at (UTC Unix milliseconds).
Review timestamps come from Hybrid-ID as UTC Unix seconds. GET never creates
requests or contacts the provider. Both methods return private no-store responses.

`POST /api/collectibles/review` requires the same session, exact Origin, current
X-Arena-CSRF and JSON with exactly action and brief_id. Actions:

- `connect`: returns the allowlisted authorization URL and transaction cookie.
- `request`: creates or recovers the one durable request for this brief.
- `refresh`: requires a saved request; retries its original create if the reply
  was lost, otherwise reads its current provider state. Five seconds between
  provider attempts per brief, including failures. No background write occurs.

After network uncertainty, a restart or sign-out, sign in as the same account,
reconnect when needed and refresh. The stable owner and immutable brief recover
**the original UUID and terms**. A new session does not create a replacement.
Different terms, collection changes, expired/declined requests need a new brief.
Provider errors are not a rejection or approval. Stale lower revisions cannot
replace newer observations. Withdrawal and approval expiration remain provider
checks; cached observations cannot be used by a future issuer.

Arena refuses responses with unexpected private fields, changed commitments,
foreign review links or true authority flags. It rechecks the session, connection
and undiscarded brief after async work. Logout/switch/expiry invalidate the
separate AES-GCM connection; the token never enters JSON, URLs or browser storage.
Steam tokens and permission storage are not reused.

Discard removes brief content and hides local review access, but retains the
original encrypted request/evidence for duplicate-prevention and audit. It does
not withdraw an external approval. The user must withdraw in Hybrid-ID; the UI
states this before discard. No issuance worker consumes any of these records.

## Rollout and remaining canonical work

- Deploy/review Identity PR162, Core PR584 and its durable read-nonce migration,
  provider PR2/PR3 and the Hybrid-ID portal. Keep current keys/configuration,
  account behavior and other verification gates intact. Coordinate a dedicated
  private collection-read credential; never reuse general Core admin keys.
- Enable the read/consent services only with actual issuer acceptance and a
  tested backup/revocation policy. Then set Arena's review flag explicitly.
  Keeping it false displays “Awaiting service rollout” and preserves history.
- Validate a real personal collection, wrong account, no eligible collection,
  selection disclosure, separate approval, withdrawal, expiry, disconnect and
  lost-response recovery across the actual services. Synthetic tests do not
  count as the user's permission or real acceptance.
- Implement the narrow purpose/audience-bound canonical consent consumer and
  coordinated studio-rights reservation/consumption. Neither status read is an
  atomic authorization decision. Bind the original UUID, canonical bytes and
  revocation/consumption decision; then use Core's original-request creation
  receipt and read back the actual asset. No duplicate issuance on restart.

Funding, Stripe, purchase, minting and real-value execution remain inactive.

## Accepted consent history

The new provider consumption contract adds `consumed`: the canonical service has
accepted the exact personal approval for its original request. Arena displays
“Accepted for draft creation,” while all issuance/rights/value flags remain false.
It is historical consent acceptance, not proof an asset exists. Only the separate
loopback HMAC canonical service can obtain the native receipt; Arena receives no
issuer profile or consumption credentials and exposes no consumption operation.
The canonical coordinator and studio-rights participant are implemented; connected
rollout and real acceptance remain outstanding. Do not activate this workflow
based on a cached approval or consumed status. See [draft requests](drafts.md).
