Pup - the AI's own browser

@@ -12444,6 +12444,55 @@ server.listen(PORT, BIND_HOST, async () => {   const _healingIds = new Set();          // sessionIds with a relaunch in flight (guards the 15s re-tick)   const MAX_HEAL_ATTEMPTS = 2;   const HEAL_COOLDOWN_MS = 5 * 60 * 1000;+  // v1.9.256 SLEEP/WAKE + LOST-BROWSER RECOVERY (John, after a day away with the lid closed: "a+  // laptop going to sleep is quite a common occurrence so you need to make sure after a wake that+  // you are able to get back to the previous state you were in, i.e. all your browsers should not+  // be lost anymore"). His dashboard sat on 'browser lost' for a day because the crash-recovery+  // loop lived inside the minimalTouch-gated health interval - the THIRD critical feature silently+  // killed by that one gate (overlay enforcer, user-activity watcher, now recovery). Recovery runs+  // UNGATED here: minimal-touch forbids KILLING or RESTARTING a live Chrome behind the user's back;+  // it does not forbid resurrecting DEAD windows to restore the user's state - that restoration is+  // exactly what the user wants after a sleep. (Hung-Chrome teardown, which DOES kill, stays gated.)+  let _lastRecoveryTick = Date.now();+  setInterval(async () => {+    if (process.platform !== 'win32') return;+    const now = Date.now();+    const gap = now - _lastRecoveryTick;+    _lastRecoveryTick = now;+    if (gap > 90000) console.log(`[wake] system appears to have SLEPT ~${Math.round(gap / 60000)}min (timer gap) — checking every session for lost browsers`);+    for (const [sid, sess] of [...sessions]) {+      if (!sess._lostBrowser || _healingIds.has(sid)) continue;+      const rec = _healRelaunch.get(sid) || { count: 0, last: 0, gaveUp: false };+      if (rec.count >= MAX_HEAL_ATTEMPTS) {+        if (now - rec.last < HEAL_COOLDOWN_MS) {+          if (!rec.gaveUp) {+            rec.gaveUp = true; _healRelaunch.set(sid, rec);+            console.log(`[heal] "${sid}" exceeded ${MAX_HEAL_ATTEMPTS} relaunch attempts — backing off ${Math.round(HEAL_COOLDOWN_MS / 60000)}m`);+            recordCleanup(`pup tried to bring your "${sid}" window back but it kept failing — pup has stopped retrying for now. Reopen it manually when ready; your logins are safe on disk.`);+          }+          continue;+        }+        rec.count = 0; rec.gaveUp = false;+      }+      _healingIds.add(sid);+      rec.count += 1; rec.last = now; _healRelaunch.set(sid, rec);+      console.log(`[heal] "${sid}" browser lost (crash or sleep) — recovering (attempt ${rec.count}/${MAX_HEAL_ATTEMPTS}) at its last URL`);+      try {+        const r = await recoverOrRelaunchSession({ sessionId: sid });+        if (r && r.session) {+          console.log(`[heal] "${sid}" recovered — window is back, signed in, where it left off`);+          recordCleanup(`pup auto-recovered your "${sid}" window (lost to a crash or the machine sleeping) — relaunched in the background, signed in, at where it left off.`);+        } else {+          console.log(`[heal] "${sid}" recovery did not resolve a live session yet — will retry next tick`);+        }+      } catch (e) {+        console.log(`[heal] "${sid}" recovery failed: ${e.message} — will retry next tick`);+      } finally {+        _healingIds.delete(sid);+      }+    }+  }, 20000);+   // v1.9.255 NO-FAULT WATCH (John: "if the window does get foreground by chrome itself or a focus   // or some other reason, you do watch it for 20 seconds and put up a caption saying something like   // 'it wasn't my fault, the javascript, or focus, or chrome caused the foreground. not me!'").@@ -12528,40 +12577,6 @@ server.listen(PORT, BIND_HOST, async () => {       try { await killOrphanChromesForProfile(profileName); } catch (e) {}       for (const [, sess] of sessions) { if (sess.profileName === profileName) sess._lostBrowser = true; }     }-    // (1) CRASH recovery — proactively relaunch every `_lostBrowser` session (from a crash OR from the-    // hung-teardown above) so the user's windows come back on their own, signed in, where they left off.-    for (const [sid, sess] of [...sessions]) {-      if (!sess._lostBrowser || _healingIds.has(sid)) continue;-      const rec = _healRelaunch.get(sid) || { count: 0, last: 0, gaveUp: false };-      const now = Date.now();-      if (rec.count >= MAX_HEAL_ATTEMPTS) {-        if (now - rec.last < HEAL_COOLDOWN_MS) {-          if (!rec.gaveUp) {-            rec.gaveUp = true; _healRelaunch.set(sid, rec);-            console.log(`[heal] "${sid}" exceeded ${MAX_HEAL_ATTEMPTS} relaunch attempts — backing off ${Math.round(HEAL_COOLDOWN_MS/60000)}m (the page looks like it destabilizes Chrome)`);-            recordCleanup(`pup tried to bring your "${sid}" window back after a Chrome crash but it kept crashing on load — that page may be destabilizing Chrome, so pup has stopped retrying it. Reopen it manually when you're ready; your logins are safe on disk.`);-          }-          continue;-        }-        rec.count = 0; rec.gaveUp = false;   // cooldown elapsed — allow a fresh round-      }-      _healingIds.add(sid);-      rec.count += 1; rec.last = now; _healRelaunch.set(sid, rec);-      console.log(`[heal] "${sid}" lost to a Chrome crash — proactively relaunching (attempt ${rec.count}/${MAX_HEAL_ATTEMPTS}) at its last URL`);-      try {-        const r = await recoverOrRelaunchSession({ sessionId: sid });-        if (r && r.session) {-          console.log(`[heal] "${sid}" relaunched OK — window is back signed-in`);-          recordCleanup(`pup auto-recovered your "${sid}" window after a Chrome crash — it relaunched in the background, signed in, at where it left off (logins are safe on disk).`);-        } else {-          console.log(`[heal] "${sid}" relaunch did not resolve a live session yet — will retry next tick`);-        }-      } catch (e) {-        console.log(`[heal] "${sid}" relaunch failed: ${e.message} — will retry next tick`);-      } finally {-        _healingIds.delete(sid);-      }-    }     // (3) USER-ACTIVITY WATCHER + STUCK-OCCLUSION check (v1.9.180/181). One OS foreground read per     // tick. When the foreground IS a pup window: (a) stamp it user-active + foreground (PERSISTED),     // so no park/recovery/adoption path ever demotes a window the user chose to bring up — the