[ScoreSymphony]

Prepares the corrected Fruit Fusion build for GitHub release v1.0.2.

• sets Expo/app version to 1.0.2
• sets package version to 1.0.2
• keeps the corrected transparent Fruit Fusion icon already on main
• advances Android versionCode to 5 and iOS buildNumber to 5 so the build identifiers remain monotonic
• uses the existing docs/RELEASE_V1.0.2.md release notes

After merge, the existing release workflow will build the signed standalone Android APK and create the v1.0.2 GitHub Release if all release checks pass.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: bf06aee68e

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Use a new release version instead of reusing v1.0.2

On merge to main, this package.json change triggers .github/workflows/release.yml, which derives the tag v1.0.2; however, that version was already used by the earlier v1.0.2 release sequence before the repository advanced to v1.0.3. The publish step explicitly checks gh release view "$TAG" and exits with status 1 when the release exists, so this commit cannot publish the intended corrected APK. Keep the release version monotonic and provide corresponding new release notes.

Useful? React with 👍 / 👎.