Astro hydration mismatch behavior when switching output modes from static to server

The goal is to determine whether a single component that fails to hydrate in an Astro application causes the entire page to lose interactivity when the project is built with output: server instead of output: static. In static builds, hydration mismatches are rare because there is no client‑side JavaScript, but SSR introduces a boundary where environment‑dependent code may run only on the server.

Current logs show a hydration mismatch warning, yet it is unclear if Astro isolates the faulty component or falls back to a non‑interactive placeholder. The documentation does not specify a recovery strategy for such mismatches in SSR mode, leaving the behavior ambiguous.

Does Astro isolate the failing component and keep the rest of the page interactive in SSR mode?

Is there a configuration option to enable fallback UI or graceful degradation for hydration mismatches?