Pup - the AI's own browser

@@ -1,10 +1,10 @@ {   "manifest_version": 1,   "name": "puppeteer",-  "version": "2.0.115",-  "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.115/adom-bridge-puppeteer-v2.0.115.zip",-  "sha256": "261fa73b379d119780c4d92baa92739371bf32b7f311f551a2228fbca94f7419",-  "size": 862908,+  "version": "2.0.116",+  "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.116/adom-bridge-puppeteer-v2.0.116.zip",+  "sha256": "b55ff703005a94b1654a6caf3a40e4c5e57f06412198144a02a778e93008bd2e",+  "size": 863336,   "verbPrefixes": [     "browser_",     "desktop_recorder_",

@@ -1 +1 @@-2.0.115+2.0.116

@@ -2,7 +2,7 @@   "manifest_version": 1,   "name": "puppeteer",   "displayName": "Puppeteer (Chrome for Testing + Native)",-  "version": "2.0.115",+  "version": "2.0.116",   "description": "Drives a browser ALREADY on the machine \u2014 installed Chrome, else Microsoft Edge (every Windows PC ships with Edge) \u2014 launched with a FRESH isolated profile, so the common case has NO ~150 MB Chrome-for-Testing download and it never touches the user's real tabs/logins. Binds its local server to LOOPBACK (127.0.0.1) only, so no Windows Firewall 'allow Node through the firewall' prompt ever pops. Chrome for Testing is fetched only as a LAST RESORT if the machine has no Chromium browser at all. SPAWN-VERIFIED fallback: pup tries each detected browser (Chrome \u2192 Edge \u2192 CfT) and actually launches it, falling through to the next if one won't start (and handling browsers like Edge that relaunch onto another PID), so a corrupt/partial install never hard-fails an open. The browser that launches is cached as the default (persisted across restarts) so it isn't re-probed each time. On spawn the bridge SELF-WARMS: detects browsers + disk, and only if the box has no Chrome/Edge and no cached CfT does it background-fetch CfT so the first open is instant. pup_use pins a specific browser (chrome | edge | cft | auto); {browser:'chrome',install:true} downloads & installs REAL Google Chrome (user-scoped, no admin) on an Edge-only box. pup_readiness (READ-ONLY) reports which browser will be used + the full candidate list + the default + free disk. Every failure returns a specific errorCode + _hint (chrome_install_no_disk, chrome_download_network, chrome_install_permission, chrome_stable_not_detected, \u2026). Launches with FULL browser permissions by default for full debug (strictPermissions:true opts out). Headful automation: open/close windows+tabs, navigate, screenshot, eval JS, record. pup is a GENERIC, non-profile browser only \u2014 every session is a fresh isolated Chrome/Edge process, never the user's real signed-in browser; profile defaults to sessionId. To drive the user's REAL Chrome/Edge (their profile, cookies, SSO), use the Adom browser EXTENSION's nbrowser_* verbs \u2014 a separate bridge, not pup's job. macOS (v1.9.74+): full parity with mac-native mechanics \u2014 background-by-default is the app-level hide (windows stay drivable/screenshottable while hidden), raise/lower map to unhide+activate/hide, pup_alert_window posts a native toast whose click focuses the window, pup_use {browser:'chrome',install:true} installs Chrome from the official dmg, and taskbar identity/badging remains Windows-only.",   "homepage": "https://wiki.adom.inc/adom/adom-bridge",   "author": "Adom Inc.",

@@ -2476,7 +2476,10 @@ async function killBrowserProcess(browser, profileName) {     }     // Graceful close, but never let a wedged CDP make close() hang the whole teardown (the reap     // below is what actually guarantees the processes die, so a slow/hung close must not block it).-    try { await Promise.race([browser.close(), new Promise(r => setTimeout(r, 3000))]); }+    // v2.0.116 (John): give it a longer budget than before — a clean exit is what FLUSHES the+    // profile's prefs to disk (toolbar pins, developer_mode, saved logins), and the old 3s race+    // could force-kill mid-flush, which is why the pinned toolbar tiles were lost every relaunch.+    try { await Promise.race([browser.close(), new Promise(r => setTimeout(r, 8000))]); }     catch (e) { console.log(`Graceful close failed for profile "${profileName}": ${e.message}`); }   } @@ -2488,11 +2491,21 @@ async function killBrowserProcess(browser, profileName) {     } catch {}   } -  // Tree-kill the tracked parent first (fast; catches the common case). Non-blocking async taskkill.+  // v2.0.116: DO NOT force-kill a process that already exited on its own — that clean exit is+  // exactly what let Chrome finish writing its prefs. Poll the PID for a short grace window after+  // close() resolves; only tree-kill a genuinely WEDGED process. The profile-scoped reap below+  // still guarantees no reparented renderer lingers (those never write the profile prefs).+  const _pidAlive = (p) => { try { process.kill(p, 0); return true; } catch (e) { return e.code === 'EPERM'; } };   if (pid) {-    if (_isWin) { await _taskkillPids([pid]); }-    else { try { process.kill(pid, 'SIGKILL'); } catch (e) {} }-    console.log(`Force-killed Chrome PID ${pid} for profile "${profileName}"`);+    let alive = _pidAlive(pid);+    for (let i = 0; i < 12 && alive; i++) { await new Promise(r => setTimeout(r, 250)); alive = _pidAlive(pid); }+    if (!alive) {+      console.log(`Chrome PID ${pid} for profile "${profileName}" exited cleanly — prefs (pins/dev-mode/logins) flushed`);+    } else {+      if (_isWin) { await _taskkillPids([pid]); }+      else { try { process.kill(pid, 'SIGKILL'); } catch (e) {} }+      console.log(`Force-killed WEDGED Chrome PID ${pid} for profile "${profileName}" (graceful close did not exit it in time)`);+    }   }    // Then the RELIABLE, AWAITED, VERIFIED profile-scoped reap. taskkill /T kills the parent's tree, but