Browser interactivity and hydration

The RC has no public @tagna/udiot/ssr/hydration entry point. Internal Hydrator, initHydration and getHydrator APIs are not npm consumer APIs. Do not rely on their source implementation as a stable hydration contract.

Use @tagna/udiot/browser for exported browser state/UI APIs and provide your application's client entry point. Server-rendered HTML does not by itself attach event handlers or restore application state.

For an application-owned hydration integration:

1. Define the server/client state format explicitly; serialize only public data.
2. Encode serialized data safely for its HTML context.
3. Load your bundled client script under your Content Security Policy.
4. Attach handlers once, and dispose subscriptions/listeners when unmounting.
5. Test initial rendering, navigation, mismatches and repeated mounts in browsers.

Browser smoke tests cover selected consumers, not a general SSR hydration certification. See rendering and web application configuration.