[Muawiya-contact]

v1.10.18 — profile photo saving

This release delivers the camera/gallery photo repair from #477 to the production app. It replaces the Android local-file fetch and Blob/FileReader preparation path with checked JPEG bytes from Expo ImagePicker or ImageManipulator. A failed photo save keeps the existing avatar.

What users will see

• App version: 1.10.18 (mobile/app.config.js).
• One-time What's New card: “Save a camera or gallery photo to your profile with smoother handling for larger images.” It uses the existing version-based dismissal.
• Native runtime: remains 1.10.16; this is JavaScript-only and should reach the existing production APK through OTA after the release gate. No reinstall is planned.

Review and verification

• main is an ancestor of develop. The final diff contains the photo repair, its tests, documentation, the version bump and matching card. The already deployed Supabase CI confirmation fix has been reconciled into develop and creates no net production workflow change in this PR.
• Fix Android profile photo preparation after v1.10.17 #477: all four PR gates passed; focused JPEG byte tests, mobile typecheck, Expo web export, and browser gallery/camera/upload recovery passed in both themes.
• Prepare v1.10.18 profile photo release #478: all four PR gates passed; mobile typecheck, Expo web export, and the v1.10.18 card layout/dismissal browser check passed in phone and landscape layouts, both themes, including an offline restart.
• Physical Android result remains unverified. The owner has one phone and will test the production app after the release. The preview OTA was published successfully, but there is no separate device for a preview build.

Manual release work after this PR merges

1. Migrations: none. This diff adds no backend/migrations/*.sql file, so no manual staging or production SQL is required.
2. Dispatch supabase-production-deploy.yml on the exact new main SHA; approve its production-schema gate. Require schema, API/worker deploy, unsigned-worker rejection, API health, and final-main checks to pass. Do not change Cron flags.
3. Dispatch release.yml on the same main SHA using that successful production deploy run ID. Approve its first schema gate. The workflow publishes the preview OTA before the production gate.
4. At the second protected gate, disclose that preview was not tested on a separate device. The owner explicitly chose a production phone check; approve the production OTA only with that understanding. The workflow then creates v1.10.18 and handles the native-gated APK task.
5. On the owner's phone, close and reopen the production app twice; verify the displayed version, sign-in, Today, gallery Save photo, camera Save photo, and the keyboard-safe profile fields. Report any exact on-screen error without account details.

No Railway or database change is part of this release. Merge and each protected deployment gate remain separate owner decisions.

[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	⚠️ Failed 2026-11-02T16:12:14.522511Z We couldn’t complete this review. Comment @codex review to try again.	7347fd1	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.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[netlify]

✅ Deploy Preview for coding-moves-one-concept-review canceled.

Name	Link
🔨 Latest commit	7347fd1
🔍 Latest deploy log	https://app.netlify.com/projects/coding-moves-one-concept-review/deploys/6ae8b65dfe52b05da9eae011