From docs/TODO.md Phase A3 (still open on HEAD). FivucsasFirebaseMessagingService.kt builds a plain NotificationCompat with no .addAction() Allow/Deny buttons, there is no ApprovalActionReceiver to POST a signed approval to /api/v1/nfc/approve //deny, and MainActivity.onNewIntent (line 58) only forwards NFC intents — no fivucsas://nfc-session intent-filter or session-id deep-link handler exists. Approve-login itself works in-app (ApproveLoginViewModel/Repository); this is the push-notification UX layer on top. Protocol spec lives in the NFC_PUSH_APPROVAL_PROTOCOL plan (Ed25519 device registration).
From docs/TODO.md Phase A3 (still open on HEAD).
FivucsasFirebaseMessagingService.ktbuilds a plainNotificationCompatwith no.addAction()Allow/Deny buttons, there is noApprovalActionReceiverto POST a signed approval to/api/v1/nfc/approve//deny, andMainActivity.onNewIntent(line 58) only forwards NFC intents — nofivucsas://nfc-sessionintent-filter or session-id deep-link handler exists. Approve-login itself works in-app (ApproveLoginViewModel/Repository); this is the push-notification UX layer on top. Protocol spec lives in the NFC_PUSH_APPROVAL_PROTOCOL plan (Ed25519 device registration).