3a50a6bea8
host.openSession awaited ensureGatewayProfile with no deadline. That await gates waitForFocusedSessionHydration, which arms the only timer on the path, so a profile dial that never settles left the open pending for the life of the window: the pane froze with no error, no Retry and - the part that made this hard to recognise - no timeout either. The gateway log signature is a bare `ws accepted` with no matching `ws closed`. Bound the activation with its own copy of the wake budget rather than folding it into the hydration one. A cold profile backend can legitimately spend most of the hydration budget painting a large transcript, and that race is already tight enough to lose, so charging activation to the same clock would trade a wedge for a regression. The timeout reuses the hydration message prefix on purpose - openSession keys the core stranded-session surface off it - and the [bot-wake] support log now names which phase expired, so a stuck dial is not read as a slow transcript. Scoped to callers that passed awaitHydration. A plain open never asked for a deadline and has nowhere to render one, so its behaviour is unchanged. Two existing tests counted microtask ticks between the call and the core open. The bounded activation adds a tick, so they now flush a macrotask instead, which asserts the same thing without depending on the await count. Refs #89556