fix(mobile): defer filesystem navigation - #4799

💭 Looking at this diff, I'm examining a React component that introduces a new useBrowsePathInput hook along with some utility functions for navigation coordination. The code appears to be checking whether Effect service conventions are being followed properly in this mobile app context. I'm looking at the React component changes and noticing new helper functions imported from the runtime state module. I need to trace whether these helpers—createBrowseNavigationCoordinator and canPreloadBrowsePath—were added in this same PR or if they already exist in the branch, since the diff only shows the component file itself. I'm noticing that the React component imports new helpers from @t3tools/client-runtime/state/filesystem, but they're not showing up in the diff itself. Since the code would fail to compile if these functions didn't exist, they must already be defined in the client-runtime package—I should verify whether these helpers are actually present in the repo. I'm checking whether these helper functions were already present in the codebase or if they're new additions in this PR. The diff only shows changes to AddProjectScreen.tsx, so it looks like the filesystem utilities already existed on the main branch rather than being introduced here. These are just plain React hooks and utility functions, not Effect services, so there's no violation of Effect service conventions to worry about. The coordinator returned by createBrowseNavigationCoordinator is a simple object, and canPreloadBrowsePath is a pure predicate function. Since the PR doesn't create, move, refactor, or consume any Effect services, there's nothing to flag here.