## Publishing OTA Updates

All OTA updates follow this workflow. No exceptions.

1. Apply the fix to the codebase.
2. Publish to the staging channel:
     npx eas update --channel staging --message "<description>"
3. Verify on physical staging iOS device (minimum 10 minutes of use).
4. Verify on physical staging Android device (minimum 10 minutes of use).
5. Only after both devices pass: publish to production.
     npx eas update --channel production --message "<description>"
6. Monitor Sentry crash rate for 30 minutes post-publish.

If a production update causes crashes: roll back immediately.
     npx eas update:rollback --channel production
Do not attempt to fix-forward on a broken OTA update. Roll back first.
