Push notifications and inbox

The app includes an in-app inbox and the production Expo Push infrastructure. Your product still decides when a reminder should be sent; the kit handles permission, token ownership, trusted sending, receipts, and safe navigation.

Prompt

Read agent-skills/wire-push.md. Activate Expo Push for my final EAS project.
Configure APNs and FCM, keep sends in trusted server code, deploy the included
send and receipt functions, schedule receipt checks, and test foreground,
background, and killed-state taps on physical iOS and Android devices.

Included behavior

• contextual permission request and Android channel,
• project-scoped Expo token registration and rotation,
• user/device ownership and current-device sign-out cleanup,
• English/Spanish display copy,
• in-app inbox write,
• ticket storage, delayed receipt checks, and dead-token retirement,
• allow-listed routing for notification taps.

Never call the server send function from the mobile app. Keep lock-screen title and body nonsensitive. Delivery is at-least-once, so a retry after an uncertain network outcome can duplicate a notification; tapped actions must be safe to repeat.

Verify

Test undetermined, denied, granted, and revoked permission; token rotation; account switch/sign-out; foreground/background/killed delivery; invalid route; no-token user; immediate ticket error; delayed receipt error; and dead-token cleanup. Expo Go and simulators are not full push proof.