[bmc08gt]

When a user says they aren't getting notifications, support has no way to see why. The iOS permission, the banner and Lock Screen settings, and whether this phone's token ever reached our servers are all invisible from the app, and AddToken failures were dropped without a trace.

This adds Settings › Advanced › Notifications, a page that runs those checks, says which one is failing, and links each failure to its fix. Spec: code-payments/flipcash-client-orchestrator#73. Design: Figma page 12952:56.

• NotificationStatus in FlipcashCore is a pure function from a settings snapshot plus the last registration result to the page's rows and summary. No UIKit or UserNotifications types, so every spec test case it covers is a unit test (NotificationStatusTests).
• PushController.fetchStatus now returns the full UNNotificationSettings instead of only authorizationStatus; its callers in onboarding and the swap completion read .authorizationStatus from it.
• Registration results are saved per account (NotificationRegistrationStore) and cleared on logout. AddToken errors from the Firebase and APNs token callbacks are recorded and reported instead of dropped, and didFailToRegisterForRemoteNotifications saves its error for the page.
• The page runs its own registration attempt (delete token if asked, token fetch, AddToken) under one 10 second deadline. An attempt that never got a token saves nothing; closing the page mid-run drops the attempt and saves nothing.
• The saved record keeps lastRegistrationOkAt, set by any ok and cleared on logout. A failed attempt after an earlier ok shows as a Warning ("Last confirmed …") instead of a Fail.
• Check Again after an INVALID_PUSH_TOKEN result deletes the local token first, as Try Again does.
• The "N checks passed" row toggles the groups open and closed and stays visible while open. During Check Again it shows Checking like the other rows.
• On every re-run (Check Again, Try Again, and the re-run after Turn On is granted) the summary card keeps the previous run's summary and animates to the new one when the run finishes. "Checking…" shows only on the page's first run.
• A refresh action in the navigation bar (accessibility label "Check Again") re-runs every check, including a fresh AddToken. Registration runs on open, on Check Again, on Try Again, and after the in-app Turn On when permission is granted (not on deny); returning from iOS Settings re-reads UNNotificationSettings and leaves the registration row on its last result.
• Rows are laid out as Checking from the first frame and change status in place. Each row reserves a title and two lines of detail, so a result that wraps doesn't move the rows below it.
• At accessibility text sizes the footer buttons scroll with the content instead of staying pinned, and a row's fix button moves under its text.
• Send Test Notification calls SendTestPush with a 10 second deadline, and the button shows its loading state while the call runs. OK switches it to Send Again with a "Test notification sent" toast, and a failed send after that leaves it on Send Again. A transport failure, cancellation or timeout toasts "Couldn't reach Flipcash"; any other failure toasts "Couldn't send a test notification". The footer reads "Flipcash sends the test to every phone signed in to this account." The tap re-reads the permission first and sends nothing if it went away.
• The server's test push carries an empty Payload. NotificationDelegate already presents a push with no chat payload as a foreground banner and routes nothing on tap, so the push needs no special case; NotificationPresentationTests pins the empty-Payload case. The earlier local flipcash_test notification, its delegate branches, its tap route and AppRouter.navigate(to:under:) are gone.
• PushController.withDeadline returns at the deadline even when the call ignores cancellation. A task group would wait for every child, and SendTestPush runs behind a continuation that ignores cancellation, so a hung send would hold the button until the 15 s gRPC deadline. DeadlineRace instead races the call, the deadline and caller cancellation and cancels whichever loses. The same limit covers AddToken and the Firebase token fetch and delete. A timeout still throws CancellationError, so it maps to the same transport result as before. PushControllerDeadlineTests covers a call that ignores cancellation, a caller cancelled mid-call, and a value or error that arrives before the deadline.
• A row's title is its check name in every state, Checking included: Notifications Allowed, Banners and Lock Screen, Sounds and Badges, and Registered for Push, on screen and in the shared report. On a warning or fail the problem sentence moves to the detail's first line, with the explanation, if there is one, on the second: "Notifications are turned off" over "Turned off for Flipcash in iOS Settings". Details stay sentence case.
• Share Report sends a plain-text report with each check's raw value and a truncated copy of the token sent in the latest attempt ("none" if no token was fetched). The registration line describes the page's latest run (pass (statusPage, <time>), fail (noAPNsToken), checking), followed by a separate Last ok: <time> line, or Last ok: never. A zero offset is written UTC+0.
• The summary's "Checked just now" appears once the first run finishes and stays through every later run.
• textWarning already exists in Colors.swift, so the warning rows reuse it rather than adding the token the spec asks for.