Closer/functions/dist/couples
null 39255c8733 fix: prevent invite code enumeration via Cloud Function (batch v0.2.18)
- Remove client-side read access to invites (only inviter can read own invite)
- Deny direct client update to invites (server-side only via Admin SDK)
- Add acceptInviteCallable Cloud Function: validates code, creates couple,
  updates user docs, marks invite accepted, returns wrapped key for local decryption
- Update Android client: FirestoreInviteDataSource calls callable function,
  InviteConfirmViewModel uses acceptInvite + unwrapAndStore flow
- Deprecate CoupleRepositoryImpl.createCouple (client-side path removed)
- Update Firestore rules tests: unpaired read now denied, direct update now denied
- 118/118 tests passing
2026-06-19 21:46:12 -05:00
..
acceptInviteCallable.js fix: prevent invite code enumeration via Cloud Function (batch v0.2.18) 2026-06-19 21:46:12 -05:00
acceptInviteCallable.js.map fix: prevent invite code enumeration via Cloud Function (batch v0.2.18) 2026-06-19 21:46:12 -05:00
leaveCoupleCallable.js feat: Cloud Functions — leaveCoupleCallable, onUserDelete cascade (batch v0.2.8) 2026-06-19 20:04:18 -05:00
leaveCoupleCallable.js.map feat: Cloud Functions — leaveCoupleCallable, onUserDelete cascade (batch v0.2.8) 2026-06-19 20:04:18 -05:00
onCoupleLeave.js feat: partner leave notification, real-time couple state sync, in-app unpair alerts 2026-06-18 00:25:52 -05:00
onCoupleLeave.js.map feat: partner leave notification, real-time couple state sync, in-app unpair alerts 2026-06-18 00:25:52 -05:00