null 23c99233b4 fix(notif): game pushes deep-link into the waiting game, not the Play hub (E-003) ... partner_started_game / partner_completed_part now route to the specific game route (gameRouteForType(payload.gameType)) so the game screen auto-joins the couple's active session — fulfilling the 'Tap to join!' promise. Server already sends game_type in the FCM data; client now parses it (AppMessagingService + MainActivity) into PartnerNotificationPayload and routeFor maps it. game_results_ready stays on the hub pending a server change to also send game_session_id (completed sessions aren't returned by getActiveSession, so the plain game route would show setup). Verified live: backgrounded partner tapped the start-game push -> opened This or That at 1/5 (joined), not the hub. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>		2026-06-25 12:02:28 -05:00
..
schemas	fix: use sex column for Desire Sync question filtering instead of fragile ID pattern	2026-06-18 00:32:39 -05:00
src	fix(notif): game pushes deep-link into the waiting game, not the Play hub (E-003)	2026-06-25 12:02:28 -05:00
build.gradle.kts	chore(config): coil-gif dependency, RECORD_AUDIO permission, firestore rules allow voice type	2026-06-24 16:34:53 -05:00
proguard-rules.pro	feat: settings polish, privacy strings, home partner state, proguard rules	2026-06-21 09:49:02 -05:00