ReleaseChannel mismatch and auto-install trigger conditions

The Expo Updates API evaluates update eligibility by comparing the remote manifest's releaseChannel against the app's currently assigned releaseChannel. When a mismatch occurs, the service may reject the update or continue to display the installed version string, but the decision logic that governs whether auto‑install is suppressed in favor of explicit user approval via exupdates.installAsync remains unspecified. The foreground‑launch auto‑install flow depends on network availability and bundle size, and platform cautions note that large background downloads can interrupt user workflow. This ambiguity affects developers relying on channel‑separated update streams for development, staging, and production environments.

What exact conditions cause the Updates API to defer auto‑install when the manifest's releaseChannel diverges from the installed app's channel? How does the manifest's available field interact with a mismatched releaseChannel to influence the update flow? Can network state at foreground launch override the releaseChannel comparison or determine whether the update is queued, rejected, or presented for explicit installation?