null c60fa958a5 fix(qa): qa_push.js picks newest FCM token, not docs[0] ... After an APK reinstall a device registers a fresh FCM token alongside stale ones (~33h). The smoke harness grabbed docs[0] (unordered) and could hit a stale token -> FCM 'Requested entity was not found' -> false smoke FAIL. Now sort fcmTokens by updatedAt and try newest-first across all tokens, skipping dead ones, mirroring the app's sendToUser + pruneTokens behavior. Also file two R31 QA-env observations to Future.md (add the RevenueCat test_ key to local.properties so QA can drive the live paywall; FCM token churn note). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>		2026-07-10 10:06:07 -05:00
..
entrypoint_smoke.sh	chore(repo): keep QA fixture docs local-only	2026-07-07 23:28:45 -05:00
qa_push.js	fix(qa): qa_push.js picks newest FCM token, not docs[0]	2026-07-10 10:06:07 -05:00