React Navigation is properly initialized

Without a single NavigationContainer at the root, React Navigation has no scene graph to mount — screens render as disconnected components, deep links resolve to nothing, and the back button bubbles to the OS and closes the app. Users who tap a push notification or share-sheet link land on a blank route or a cold Home, destroying the user-experience contract the rest of the app depends on. Duplicated containers create competing state trees that silently drop navigation events.

Mount exactly one NavigationContainer at the app root and pass it a linking config. Put this in App.tsx so every screen is a descendant:

import { NavigationContainer } from '@react-navigation/native'

export default function App() {
  return (
    <NavigationContainer linking={linking}>
      <RootNavigator />
    </NavigationContainer>
  )
}

Delete any secondary NavigationContainer instances — nested ones must be replaced by plain Navigator components.