Fix stale on_load during websocket connection
Merged
HA
19h ago+302+302+012345678901234567890123456789-31-31-01234567890123456789
Fixes #7487. The websocket’s initial hydration event now uses the route current when the connection begins, preventing navigation during connection setup from running the previous page’s on_load handler or triggering its redirect.
Coalesces queued internal on_load events when the hydration event already covers the current route. Adds unit and dev/production browser regression tests.