@melaya/runner 1.1.45 → 1.1.46

package/dist/connection.js

@@ -78,6 +78,27 @@ export async function connect(opts) {
         reconnectionAttempts: Infinity,
     });
     let relay = null;
+    // ── Disconnect diagnostics (transport-close root-cause) ──────────────
+    // A "transport close" disconnect can be a NETWORK blip OR the Node event loop
+    // being BLOCKED (e.g. relaying big browser screenshots/trees) long enough that
+    // Socket.IO can't service the connection. These need OPPOSITE fixes, so we
+    // sample event-loop lag continuously and print the recent PEAK on disconnect:
+    // a multi-second spike ⇒ event-loop block (in-process work); ~0 ⇒ network/proxy.
+    let connectedAt = 0;
+    let lastHeartbeatAt = 0;
+    let peakLagMs = 0;
+    {
+        let last = Date.now();
+        const TICK = 500;
+        const t = setInterval(() => {
+            const now = Date.now();
+            const lag = now - last - TICK; // how much longer than TICK the loop actually took
+            last = now;
+            if (lag > peakLagMs)
+                peakLagMs = lag;
+        }, TICK);
+        t.unref?.();
+    }
     // ── Melaya Browser bridge state (plan Sections 3/4) ──────────────────
     // The governed browser control bridge is started lazily on the first
     // browser run. Grant public keys arrive over the socket (server push)
@@ -209,6 +230,8 @@ export async function connect(opts) {
     };
     socket.on("connect", async () => {
         spinner.succeed(chalk.green("Connected to Melaya"));
+        connectedAt = Date.now();
+        peakLagMs = 0; // fresh window each connection so the disconnect line reflects THIS session
         // New socket lifetime → new generation. Grants minted for an earlier
         // generation are refused (plan Section 4). Any browser runs from the
         // previous connection are already torn down on the disconnect path.
@@ -269,7 +292,16 @@ export async function connect(opts) {
         }
     });
     socket.on("disconnect", (reason) => {
-        console.log(chalk.yellow(`\n  Disconnected: ${reason}`));
+        const upS = connectedAt ? Math.round((Date.now() - connectedAt) / 1000) : 0;
+        const hbS = lastHeartbeatAt ? Math.round((Date.now() - lastHeartbeatAt) / 1000) : -1;
+        console.log(chalk.yellow(`\n  Disconnected: ${reason} (up ${upS}s, last heartbeat ${hbS}s ago, peak event-loop lag ${peakLagMs}ms)`));
+        // The discriminator: a big peak lag (or a stale heartbeat) means the Node
+        // event loop was BLOCKED while connected — heavy in-process work (big browser
+        // screenshot/tree relay), NOT a network drop → fix is to offload/chunk that
+        // work. A small lag with "transport close" points at the network/proxy path.
+        if (peakLagMs > 2000 || hbS > 45) {
+            console.log(chalk.yellow(`  ↳ event loop was blocked ~${peakLagMs}ms (heartbeat ${hbS}s ago) — this is in-process backpressure (likely big browser payload relay), not a network drop.`));
+        }
         // Melaya Browser: a dropped socket invalidates every browser grant
         // bound to this socket generation. Tear down ALL browser runs
         // (cancels in-flight ops, releases leases, closes owned browsers);
@@ -430,8 +462,10 @@ export async function connect(opts) {
     });
     // ── Heartbeat ──────────────────────────────────────────────────────
     setInterval(() => {
-        if (socket.connected)
+        if (socket.connected) {
             socket.emit("runner:heartbeat");
+            lastHeartbeatAt = Date.now();
+        }
     }, HEARTBEAT_INTERVAL);
     // ── Run command ────────────────────────────────────────────────────
     socket.on("runner:run", async (payload) => {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@melaya/runner",
-  "version": "1.1.45",
+  "version": "1.1.46",
   "description": "Run Melaya AI pipelines locally with your own LM Studio or Ollama models",
   "license": "UNLICENSED",
   "private": false,