Navigation history maintains correct screen order

Calling navigation.reset() or popToTop() outside of logout, onboarding, or deep-link landing flows silently erases the user's breadcrumb trail. The back button then jumps past screens the user expects to return to, breaking the fundamental mobile contract that back equals undo. Users blame the app for "losing their place," and funnels that depend on multi-step flows (checkout, signup) report inflated drop-off because the stack is being rebuilt underneath them.

Prefer navigation.navigate() and navigation.push() for forward motion and let React Navigation maintain history automatically. Reserve reset() for intentional stack wipes — auth boundaries, post-onboarding, deep-link landing. In src/screens/LogoutScreen.tsx:

useEffect(() => {
  navigation.reset({ index: 0, routes: [{ name: 'Login' }] })
}, [])

Grep the repo for navigation.reset and confirm each call is tied to a flow boundary, not a routine transition.