Two navigation fixes, one found the expensive way.
1. Post-recovery BACK bounced users to the Recovery screen, forever. The Home
entry that routed to Recovery stayed on the back stack holding
needsRecovery=true, and its LaunchedEffect re-fires whenever the entry is
returned to — so after a successful recovery, BACK landed on stale-Home,
which instantly redirected to Recovery again. It looks EXACTLY like the
couple key was lost again (it wasn't; verified: the keyset survives process
kill and cold-starts straight to Home). Cost an hour of key-loss ghost
hunting live before the process-alive evidence gave it away. onRecovered and
the partner-restore onDone now popUpTo(HOME) INCLUSIVE + launchSingleTop —
the stale entry is replaced, not buried; BACK from Home exits the app like
every other root tab. C-NAV-002 class; the restore variant was worse (it
left Home AND Recovery underneath).
2. C-TODAY-BACK-001 (open P3 from the report): the Today tab drew a back arrow
the other four tabs don't. DAILY_QUESTION is a bottom-nav tab — the bar IS
the navigation. onBack is now nullable-defaulting-null and the nav wiring
passes none; LocalQuestionContent already renders the arrow only when
non-null. Verified live: no arrow, other tabs unchanged.
Suite green, verified on-device (BACK exits; Today clean).
c636749cf3