[VibeDash 6ef758f1] Mobile platform and audio API are obsolete

[rapidstartup]

Upgraded the mobile app to Expo SDK 57 and migrated call audio from expo-av to expo-audio.

VibeDash task: 6ef758f1-f16c-4388-905c-a1282cb1b47c
Runner: House Codex — gpt-5.6-luna / xhigh

Validation:

• passed: npm exec -- expo install --check — Dependencies are up to date.
• passed: npm exec -- tsc --noEmit — TypeScript compilation passed.
• passed: npm ci --dry-run --ignore-scripts --no-audit --no-fund — Lockfile is consistent.
• failed: npm exec -- expo export --platform web — Metro bundled successfully, but export failed on pre-existing placeholder image/audio assets.

This PR was opened as a draft for human review.

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[netlify]

✅ Deploy Preview for zesty-pavlova-54b539 ready!

Name	Link
🔨 Latest commit	eaf7a89
🔍 Latest deploy log	https://app.netlify.com/projects/zesty-pavlova-54b539/deploys/6a5aa785c124fc00080bac7f
😎 Deploy Preview	https://deploy-preview-9--zesty-pavlova-54b539.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[vibedash-agent]

VibeDash Codex Agent Reviewer

The dependency migration is aligned with Expo 57, but call audio remains nonfunctional and the mobile build is not releasable.

Recommendation: changes requested
Risk: high
Model: gpt-5.6-sol

Findings

• HIGH — Ringtone handlers are immediately overwritten
  CallService registers handlers that play and stop the ringtone, but CallsScreen replaces both callbacks after init. Incoming calls therefore update the UI without invoking the new expo-audio player. Support multiple subscribers or consolidate socket event handling.
  Evidence: mobile/services/callService.ts:31-32 registers handleIncomingCall/handleCallEnded; mobile/app/(app)/(tabs)/calls.tsx:31-47 immediately replaces both through SocketService's single-callback setters.
• HIGH — Referenced release assets are invalid placeholders
  The ringtone and application images are text files rather than valid media. The ringtone cannot play, and Expo export/prebuild cannot produce a releasable application. Replace them with valid assets before accepting the migration.
  Evidence: mobile/assets/sounds/ringtone.mp3 begins with // This would be a ringtone file; mobile/assets/images/icon.png and favicon.png similarly contain placeholder text. They are referenced by mobile/services/callService.ts:27 and mobile/app.json:7,22,32.

Validation reviewed

• passed: git diff --check 6607f7c64f19c00522a26605323c6002afbac6e8..eaf7a89b8804f27b8d92368185db8f49369707af — No whitespace errors.
• failed: npm exec -- expo export --platform web — PR validation reports bundling completed but export failed on the invalid placeholder assets; their invalid contents were independently inspected.
• not_run: npm run lint -- --no-cache — Node and npm are unavailable in the review environment.
• passed: npm exec -- tsc --noEmit — Reported by the PR validation; not independently rerun because Node is unavailable.
• passed: npm exec -- expo install --check — Reported by the PR validation; dependency versions also match Expo 57's bundled-module manifest.

This agent does not merge or close tasks; final closure remains with a human.