[ejsmith]

Why

Production errors were reaching Exceptionless only partly. Many were caught and shown to players, or logged and dropped, and the server never reported its own failures. Unrelated failures also piled into a few big stacks. This PR closes that loop so every real error a player hits arrives with enough context to fix it, without flooding the project with noise. It also fixes the top crashes found in the data.

Crash and bug fixes

• "Something went wrong" after returning to a game (still hitting build 49). Realtime channels were reused by name, so returning to a game got back an already-subscribed channel and crashed. Every subscription now gets a unique topic.
• Cannot read property 'scorecard' of undefined. Opening your own invite before a friend joined mounted a one-player board. That case now shows "Waiting for Friend" instead.
• iOS keychain errors on background wake. Sessions are now stored readable after first unlock. Existing items are migrated once, and the old session is restored if the migration write fails.
• Notifications broken for the next account on a device. New claim_push_token / claim_web_push_subscription functions let the signed-in account take over a stale device registration.
• Moves stuck after a resume. Moves that fail during background recovery stay pending and retry at 5s, 15s and 45s. They're reported only if every retry fails, and concurrent recovery triggers share one pass.

Telemetry

• Coverage: every on-screen error, swallowed error, error-carrying console.warn/console.error, realtime channel error and render crash is reported. Render crashes are marked critical.
• Policy (src/monitoring/errorPolicy.ts, unit tested):
  • Expected player mistakes and game rule rejections are skipped.
  • Network failures are sent at most once per operation every 10 minutes.
  • Library and coded errors group by operation, code and normalized message. App errors keep stack-trace grouping.
• Server: game-action reports unexpected faults even when it responds 4xx, with GameId and RequestId. Game rules reject with a plain Error, and InternalServerError marks server invariants. The reporter never throws and times out its submissions. Unregistered Expo push tokens are removed, and other ticket failures are reported.
• Privacy: messages, stacks and details are redacted on both sides (shared/redaction.ts): emails, push tokens and endpoints, JWTs and database row values. Credential fields are excluded on the client.
• Context: game screen events carry GameId. Native versions include the over-the-air update ID, and web versions include the commit (EXPO_PUBLIC_RELEASE_ID, set by the web build).
• Tooling: npm run errors lists stacks and events for an AI agent or developer. The rules are documented in docs/release-quality.md.

Deploy order (required)

The app no longer reports 4xx game-action errors itself; it relies on the server to report real faults. Before the web deploy or any over-the-air update that carries this client:

1. Apply migration 20261023130000_claim_push_destinations.sql. The new client calls these functions, so push registration fails without it.
2. Set the Supabase secret EXCEPTIONLESS_API_KEY.
3. Deploy game-action and delete-account.

Validation

• npm run typecheck, npm run typecheck:edge, npm run lint
• npm run test: 228 pass, including the new errorPolicy tests
• npm run test:edge: 49 pass, including the new server classification and reporter tests
• Web e2e against local Supabase: all behavioral tests pass, including the new invite and push-takeover tests. remote-turn-reveal was updated for the per-subscription topic names. Screenshot baselines are Linux-rendered, so this PR's CI is what verifies them.

Known follow-ups

• Any signed-in user who knows a device's push token or endpoint can claim it. Those are long random strings other users can't read, so the risk is low.
• The Waiting for Friend screen has no share or cancel button yet.
• Adopting the unreleased Exceptionless client (breadcrumbs, error causes, source-mappable native frames) and native source map uploads.

🤖 Generated with Claude Code

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-24T02:42:14.506523Z	f2a2a13	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.