Verified against expo-updates 57.0.19 source: ErrorRecoveryHandler runs
wait-for-remote-update -> launch new update -> relaunch cached older update
-> crash, and CONTENT_APPEARED (Android ReactRootView.onViewAdded, the first
root view render; ExpoUpdatesKit is symmetric) removes the two recovery tasks
at that point. So a render throw that discards the first commit keeps the
whole pipeline available, while any post-first-paint crash never had cached
fallback even before this PR. Comments now say the pipeline, not 'rollback',
and note expo's existing successful-launch-count rule.