Verified in the installed sources: @react-navigation/native 7.3.4
NavigationContainer renders only its (null) fallback until the async linking
getInitialState thenable resolves, while the providers above it already
commit native views. So the first frame — RN's first-native-view marker,
which is also what disarms expo-updates 57's startup-error recovery tasks —
always precedes Home's first render, on every launch, pre-PR included. A
cached-older-update fallback was therefore never available for a Home render
crash even on main (expo logged the crash and waited for a remote update),
and a valve that rethrows only before the first frame can never fire in the
real app. Keeping it would only trade a working fallback for a crash to
match main's already-poor behavior.

Home cold-launch render crashes now take the same path as every other
screen: fallback with Open settings -> Diagnostics. OTA recovery is
unchanged from main and handled by expo's native checkAutomatically ON_LOAD
(next launch downloads and applies the fix), independent of
HomeRouteScreen's effect. Removes fatalIfFirstPaintFails,
FirstCommitSentinel, app-first-commit, childCommitted tracking,
shouldRethrowAsFatal, and their tests; valve-unit tests asserted flags, not
launch order, and missed exactly this.