refine: tighten unknown-session handling to events only

The previous fix suppressed all messages for unregistered sessions.
A command *response* arriving on an unknown session would indicate a
real bug (we only send commands after createSession()) and should still
throw so it isn't silently swallowed. Only CDP events (object.method is
set) are safe to drop — they are fire-and-forget with no waiting caller.

Author: noorez

src/cdp/connection.ts

@@ -105,15 +105,24 @@ export default class Connection {
     if (!session) {
       const disposedDate = this._disposedSessions.get(object.sessionId);
       if (!disposedDate) {
-        // This can happen when Chrome sends events on a new session (e.g. an
-        // extension service worker) before our createSession() call has run —
-        // a race between Target.attachToTarget's response and early CDP events.
-        this.logger.warn(
-          LogTag.Internal,
-          `Got message for unknown session, ignoring`,
-          { sessionId: object.sessionId, method: object.method },
+        if (object.method) {
+          // Event (not a response) on an unregistered session. This can happen
+          // when Chrome pushes events (e.g. Inspector.workerScriptLoaded) on a
+          // new session before our createSession() call completes — a race
+          // between Target.attachToTarget's response and early CDP events.
+          // Safe to drop: events are fire-and-forget with no waiting caller.
+          this.logger.warn(
+            LogTag.Internal,
+            `Got event for unknown session, ignoring`,
+            { sessionId: object.sessionId, method: object.method },
+          );
+          return;
+        }
+        // A command response on an unregistered session is a real bug — we
+        // only send commands after createSession(), so this should never happen.
+        throw new Error(
+          `Unknown session id: ${object.sessionId} while processing response`,
         );
-        return;
       } else {
         const secondsAgo = (Date.now() - disposedDate.getTime()) / 1000.0;
         this.logger.warn(