fix(sdk): revert to full fire('reset') — _reconnectStopper is needed

The 'skip _reconnectStopper' approach broke force-logout coverage:
e2ee-key-reset, account-manage-devices, admin-device-management all
failed because, even with the ddp-streamer ws.close() server fix, the
notify-user/<uid>/force_logout stream message still races with the
close in microservices (it travels rocketchat-main → broker → ddp-streamer
→ WS, while the close listener fires directly on ddp-streamer). The
graceful close only flushes what's already in the WS buffer at that
moment — if the stream message is still in transit, it's still lost.

So the per-call _reconnectStopper from callLoginMethod IS the
load-bearing failsafe in microservices: it retries login with the
latest stored token and calls makeClientLoggedOut on auth failure,
which is what drives the user to /login when the stream message is
lost.

Restore the full fire('reset'). :87 is the only remaining EE 2/5
regression and a separate problem to solve.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: ggazzo

apps/meteor/client/meteor/overrides/stubMeteorStream.ts

@@ -213,29 +213,27 @@ queueMicrotask(() => {
 });
 
 // When the underlying SDK socket reconnects (e.g. after a server-side
-// ws.terminate / ws.close from force-logout in microservices), Meteor's
+// ws.close / ws.terminate from force-logout in microservices), Meteor's
 // connection sees no transport event because the stub keeps reporting
-// 'connected'. Methods that were sent but not yet completed on the prior
-// SDK session are stranded with sentMessage=true, so any test that fires a
-// method right when the socket churns wedges (message-actions /
-// report-message / e2ee-encryption-decryption all timed out before this).
+// 'connected'. Without help, both the in-flight method machinery and
+// accounts-base's reconnect-time login retry stay dormant — methods sent
+// on the prior SDK session are stranded with sentMessage=true, and the
+// per-call _reconnectStopper from callLoginMethod (accounts_client.js:292)
+// never runs. Force-logout flows then leave the user with stale
+// credentials.
 //
-// Resend the in-flight method blocks on every subsequent SDK 'connected'
-// event. Mirror everything Meteor's `_streamHandlers.onReset` does EXCEPT
-// invoke `DDP._reconnectHook` callbacks: the per-call `_reconnectStopper`
-// that callLoginMethod registers (accounts_client.js:292) retries login
-// with the captured `result.token` from the *original* successful login,
-// which is now the stale token the server just invalidated. That retry
-// runs on a `wait:true` block which queues *ahead of* the test's own
-// loginByUserState login; if it fails (it will), the stopper's userCallback
-// calls `makeClientLoggedOut`, which clobbers the credentials the test
-// just injected — and the test's queued login then never sends a frame
-// because the stopper's wait block drains in a way that confuses the
-// outstanding queue. Force-logout cleanup is now handled by the
-// `useForceLogout` client hook (notify-user/<uid>/force_logout stream
-// message) which arrives reliably since DDPStreamer.ts:62 was switched to
-// ws.close(). The first connect is handled by the queueMicrotask above;
-// skip it here.
+// Fire `reset` on every subsequent SDK 'connected' event: this drives
+// _streamHandlers.onReset → _handleOutstandingMethodsOnReset (resends
+// pending methods so message-actions / report-message tests don't wedge)
+// AND _callOnReconnectAndSendAppropriateOutstandingMethods → DDP._reconnectHook
+// callbacks → the _reconnectStopper that retries login with the latest
+// stored token and calls makeClientLoggedOut on failure (so the
+// account-manage-devices / admin-device-management / e2ee-key-reset
+// force-logout tests recover). The first connect is handled by the
+// queueMicrotask above; skip it here. The "method result but no methods
+// outstanding" / "No callback invoker" warnings the resent blocks
+// occasionally generate are caught by the bridge's async catch in
+// ddpSdkCollectionBridge.
 const sdk = getDdpSdk();
 let firstConnectHandled = false;
 sdk.connection.on('connected', () => {
@@ -244,20 +242,8 @@ sdk.connection.on('connected', () => {
 		return;
 	}
 	try {
-		const c = conn as unknown as {
-			_outstandingMethodBlocks: Array<{ wait: boolean; methods: unknown[] }>;
-			_sendOutstandingMethodBlocksMessages(blocks: Array<{ wait: boolean; methods: unknown[] }>): void;
-			_streamHandlers: {
-				_handleOutstandingMethodsOnReset?: () => void;
-				_resendSubscriptions?: () => void;
-			};
-		};
-		c._streamHandlers._handleOutstandingMethodsOnReset?.();
-		const oldBlocks = c._outstandingMethodBlocks;
-		c._outstandingMethodBlocks = [];
-		c._sendOutstandingMethodBlocksMessages(oldBlocks);
-		c._streamHandlers._resendSubscriptions?.();
+		fire('reset');
 	} catch (err) {
-		console.warn('[stubMeteorStream] custom reset on SDK reconnect failed', err);
+		console.warn('[stubMeteorStream] reset on SDK reconnect failed', err);
 	}
 });