Gateway chat-send failure finals can leave Activity sessions running unless handled like thrown agent errors

Gateway agent run startup failures should terminalize chat sessions and local bundle patches must be idempotent

Custom gateway activity page can race WebSocket hello when client.connected only means raw socket open

Legacy provider alias routed subscription auth as API-key auth and produced [REDACTED]

Node gateway advertised ready while synchronous provider-auth warmup blocked the event loop

Clean-break standalone migration still had dual-mode config defaults and stale tests