Merge pull request #4915 from RSSNext/release/mobile/0.4.0

release(mobile): Release v0.4.0

Author: DIYgod

.agents/settings.local.json

@@ -0,0 +1,24 @@
+{
+  "permissions": {
+    "allow": [
+      "Bash(gh pr view:*)",
+      "Bash(pnpm bump:*)",
+      "Bash(git add:*)",
+      "Bash(git commit:*)",
+      "Bash(ls:*)",
+      "Bash(npx:*)",
+      "Bash(git stash:*)",
+      "Bash(git show:*)",
+      "Bash(git -C /Users/diygod/Code/Projects/Folo status --short)",
+      "Bash(git -C /Users/diygod/Code/Projects/Folo add apps/mobile/changelog/next.md)",
+      "Bash(git -C /Users/diygod/Code/Projects/Folo commit:*)",
+      "Bash(git checkout:*)",
+      "Bash(git fetch:*)",
+      "Bash(git merge:*)",
+      "Bash(git rm:*)",
+      "Bash(git push:*)",
+      "Bash(gh api:*)",
+      "Bash(pnpm exec vv:*)"
+    ]
+  }
+}

.claude/skills/desktop-release/SKILL.md .agents/skills/desktop-release/SKILL.md.claude/skills/desktop-release/SKILL.md renamed to .agents/skills/desktop-release/SKILL.md

@@ -60,7 +60,21 @@ Perform a regular desktop release. This skill handles the full release workflow
 
 5. Keep `NEXT_VERSION` as the placeholder - it will be replaced by `apply-changelog.ts` during bump.
 
-## Step 3: Evaluate mainHash
+## Step 3: Commit changelog updates before bump
+
+`nbump` requires a clean working tree. Commit changelog edits before running bump.
+
+1. Stage the changelog update:
+   ```bash
+   git add apps/desktop/changelog/next.md
+   ```
+2. Commit it on `dev`:
+   ```bash
+   git commit -m "docs(desktop): prepare release changelog"
+   ```
+3. If there are no changes to commit, continue without creating an extra commit.
+
+## Step 4: Evaluate mainHash
 
 This is critical for determining whether users need a full app update or can use the lightweight renderer hot update.
 
@@ -86,14 +100,18 @@ Present your analysis to the user with:
 - Your recommendation (update or skip mainHash)
 - Ask for explicit confirmation
 
-## Step 4: Save old mainHash and execute bump
+## Step 5: Save old mainHash and execute bump
 
 1. Save the current mainHash from `apps/desktop/package.json` for later comparison.
-2. Change directory to `apps/desktop/` and run the bump:
+2. Verify working tree is clean before bump:
+   ```bash
+   git status --short
+   ```
+3. Change directory to `apps/desktop/` and run the bump:
    ```bash
    cd apps/desktop && pnpm bump
    ```
-3. This command will:
+4. This command will:
    - Pull latest changes
    - Apply changelog (rename next.md to {version}.md, create new next.md)
    - Recalculate mainHash and write to package.json
@@ -103,11 +121,11 @@ Present your analysis to the user with:
    - Create branch `release/desktop/{NEW_VERSION}`
    - Push branch and create PR to `main`
 
-## Step 5: Restore mainHash if skipping update
+## Step 6: Restore mainHash if skipping update
 
-If Step 3 decided mainHash should NOT be updated, restore the old value now. The bump has already committed, pushed, and created the PR on a new release branch, so we amend the commit and force push. This is safe because the release branch was just created.
+If Step 4 decided mainHash should NOT be updated, restore the old value now. The bump has already committed, pushed, and created the PR on a new release branch, so we amend the commit and force push. This is safe because the release branch was just created.
 
-1. Change back to the repo root first (Step 4 left the working directory at `apps/desktop/`):
+1. Change back to the repo root first (Step 5 left the working directory at `apps/desktop/`):
    ```bash
    cd ../..
    ```
@@ -122,9 +140,9 @@ If Step 3 decided mainHash should NOT be updated, restore the old value now. The
    git push --force origin release/desktop/{NEW_VERSION}
    ```
 
-If Step 3 decided mainHash SHOULD be updated, skip this step entirely — the bump already wrote the correct new value.
+If Step 4 decided mainHash SHOULD be updated, skip this step entirely — the bump already wrote the correct new value.
 
-## Step 6: Verify
+## Step 7: Verify
 
 1. Confirm the PR was created successfully by checking the output.
 2. Report the new version number and PR URL to the user.

…nstalling-mobile-preview-builds/SKILL.md …nstalling-mobile-preview-builds/SKILL.md.claude/skills/installing-mobile-preview-builds/SKILL.md renamed to .agents/skills/installing-mobile-preview-builds/SKILL.md .claude/skills/installing-mobile-preview-builds/SKILL.md renamed to .agents/skills/installing-mobile-preview-builds/SKILL.md

@@ -0,0 +1,175 @@
+---
+name: mobile-e2e
+description: Run apps/mobile Maestro end-to-end tests in this repo. Use when an agent needs to validate mobile auth flows on iOS Simulator or Android Emulator. Current maintained coverage is register, sign out, and sign in.
+disable-model-invocation: true
+allowed-tools: Bash, Read, Write, Edit, Glob, Grep
+---
+
+# Mobile E2E
+
+Run the mobile Maestro tests for `apps/mobile`.
+
+## Files that matter
+
+- Runner: `apps/mobile/e2e/run-maestro.sh`
+- iOS auth flow: `apps/mobile/e2e/flows/ios/auth.yaml`
+- Android auth flow: `apps/mobile/e2e/flows/android/core.yaml`
+- Shared auth flows: `apps/mobile/e2e/flows/shared/*.yaml`
+- Artifacts: `apps/mobile/e2e/artifacts/`
+
+## Always do first
+
+From repo root:
+
+```bash
+cd apps/mobile
+pnpm run e2e:doctor
+pnpm run typecheck
+```
+
+## iOS
+
+Use a simulator `.app` build, not an Expo development client.
+
+### Preferred simulator
+
+Prefer the **latest installed iOS runtime** and a **latest-generation iPhone simulator**.
+
+When multiple simulators are available, bias toward the newest iPhone model on the newest installed iOS version.
+
+### Boot simulator
+
+```bash
+xcrun simctl boot <IOS_UDID>
+xcrun simctl bootstatus <IOS_UDID> -b
+open -a Simulator --args -CurrentDeviceUDID <IOS_UDID>
+```
+
+### App bundle
+
+`run-maestro.sh` can resolve the app bundle from one of these sources:
+
+- `MAESTRO_IOS_APP_PATH`
+- a local `build-*.tar.gz` in `apps/mobile`
+- an existing `DerivedData/.../Release-iphonesimulator/Folo.app`
+
+If none of those exist, build one first.
+
+### Build simulator app when missing
+
+If `Folo.app` is not available yet:
+
+```bash
+cd apps/mobile/ios
+pod install
+xcodebuild -workspace Folo.xcworkspace \
+  -scheme Folo \
+  -configuration Release \
+  -sdk iphonesimulator \
+  -destination 'id=<IOS_UDID>' \
+  build
+```
+
+### Apple Silicon simulator optimization
+
+When running on an Apple Silicon Mac and building only for the simulator used in the current run, prefer compiling only the active `arm64` simulator architecture:
+
+```bash
+xcodebuild ... \
+  ONLY_ACTIVE_ARCH=YES \
+  ARCHS=arm64
+```
+
+Use this optimization only for local self-test / e2e simulator builds tied to the current machine. Do not use it when you need a universal simulator app for other machines or when running on Intel Macs.
+
+Expected output pattern:
+
+```bash
+~/Library/Developer/Xcode/DerivedData/.../Build/Products/Release-iphonesimulator/Folo.app
+```
+
+### Run iOS auth flow
+
+```bash
+cd apps/mobile
+MAESTRO_IOS_DEVICE_ID=<IOS_UDID> \
+MAESTRO_IOS_APP_PATH=<PATH_TO_Folo.app> \
+pnpm run e2e:ios
+```
+
+## Android
+
+Use a **release APK**, not an Expo development build.
+
+### Java
+
+Use Android Studio bundled JBR:
+
+```bash
+export JAVA_HOME="/Applications/Android Studio.app/Contents/jbr/Contents/Home"
+export PATH="$JAVA_HOME/bin:$PATH"
+```
+
+### Android SDK
+
+```bash
+export ANDROID_HOME="$HOME/Library/Android/sdk"
+export ANDROID_SDK_ROOT="$HOME/Library/Android/sdk"
+```
+
+If `apps/mobile/android/local.properties` is missing, create it with:
+
+```bash
+echo "sdk.dir=$HOME/Library/Android/sdk" > apps/mobile/android/local.properties
+```
+
+### Build release APK
+
+If `apps/mobile/android` does not exist locally, generate it first with Expo prebuild / run-android tooling.
+
+Then build the release APK:
+
+```bash
+cd apps/mobile/android
+./gradlew app:assembleRelease --console=plain
+```
+
+Expected APK path:
+
+```bash
+apps/mobile/android/app/build/outputs/apk/release/app-release.apk
+```
+
+### Install to emulator
+
+```bash
+adb -s emulator-5554 install -r apps/mobile/android/app/build/outputs/apk/release/app-release.apk
+```
+
+### Run Android auth flow
+
+Start a booted emulator first, then:
+
+```bash
+cd apps/mobile
+pnpm run e2e:android
+```
+
+## Result checks
+
+Successful auth validation means:
+
+- register flow finishes
+- sign-out reaches `login-screen`
+- login flow makes `login-screen` disappear
+
+## Debugging output
+
+Inspect these folders after a run:
+
+```bash
+apps/mobile/e2e/artifacts/ios/
+apps/mobile/e2e/artifacts/android/
+```
+
+For a one-off focused run, invoke Maestro directly against a single flow and a custom debug directory.

.agents/skills/mobile-e2e/SKILL.md

@@ -64,13 +64,31 @@ Perform a regular mobile release. This skill handles the full release workflow f
 
 5. Keep `NEXT_VERSION` as the placeholder - it will be replaced by `apply-changelog.ts` during bump.
 
-## Step 3: Execute bump
+## Step 3: Commit changelog updates before bump
 
-1. Change directory to `apps/mobile/` and run the bump:
+`nbump` requires a clean working tree. Commit changelog edits before running bump.
+
+1. Stage the changelog update:
+   ```bash
+   git add apps/mobile/changelog/next.md
+   ```
+2. Commit it on `dev`:
+   ```bash
+   git commit -m "docs(mobile): prepare release changelog"
+   ```
+3. If there are no changes to commit, continue without creating an extra commit.
+
+## Step 4: Execute bump
+
+1. Verify working tree is clean before bump:
+   ```bash
+   git status --short
+   ```
+2. Change directory to `apps/mobile/` and run the bump:
    ```bash
    cd apps/mobile && pnpm bump
    ```
-2. This is an interactive `nbump` command that prompts for version selection. It will:
+3. This is an interactive `nbump` command that prompts for version selection. It will:
    - Pull latest changes
    - Apply changelog (rename next.md to {version}.md, create new next.md from template)
    - Format package.json with eslint + prettier
@@ -82,7 +100,7 @@ Perform a regular mobile release. This skill handles the full release workflow f
    - Create branch `release/mobile/{NEW_VERSION}`
    - Push branch and create PR to `mobile-main`
 
-## Step 4: Verify
+## Step 5: Verify
 
 1. Confirm the PR was created successfully by checking the output.
 2. Report the new version number and PR URL to the user.