Pup - the AI's own browser

@@ -1,10 +1,10 @@ {   "manifest_version": 1,   "name": "puppeteer",-  "version": "2.0.30",-  "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.30/adom-bridge-puppeteer-v2.0.30.zip",-  "sha256": "62b46cc099e6f77b4045583e7c88a2939362e90edd5a44aa1c77aec9a1800ca5",-  "size": 641010,+  "version": "2.0.31",+  "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.31/adom-bridge-puppeteer-v2.0.31.zip",+  "sha256": "f53fcfb35402639a3b62d2500d361ed68e2d7e8511bb1d731a254ae1e982153e",+  "size": 641393,   "verbPrefixes": [     "browser_",     "desktop_recorder_",

@@ -1 +1 @@-2.0.30+2.0.31

@@ -2,7 +2,7 @@   "manifest_version": 1,   "name": "puppeteer",   "displayName": "Puppeteer (Chrome for Testing + Native)",-  "version": "2.0.30",+  "version": "2.0.31",   "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.",

@@ -5358,6 +5358,14 @@ async function hwndBelongsToPup(hwnd, session) {   const pid = info && info.pid;   if (!pid) return false;   const prof = session && session.profileName;+  // v2.0.31: STRONGEST PROOF FIRST — a hwnd pup captured at BIRTH (it created that exact off-screen+  // window) is definitively pup's, no pid tracking and no title tag required. This replaces the+  // v1.9.350 title-based shared-profile fallback that 2.0.24 broke by removing the title tag. Learn+  // the owner pid so every sibling window on the shared Chrome process passes instantly afterwards.+  try {+    const born = session && (session.tabs || []).some(t => t && t.page && Number(t.page.__pupHwnd) === Number(hwnd));+    if (born) { learnConfirmedPid(prof, pid); return true; }+  } catch (e) {}   const own = pupBrowserPidSet(prof || undefined);   if (own.has(pid)) return true;   try {@@ -7476,13 +7484,18 @@ async function createPageInNewWindow(browser, profileName) {     // window of this profile at ~birthLeft" is unambiguous. Stash it on the page for the resolver.     if (fresh && process.platform === 'win32' && profileName) {       try {-        const pids = pupBrowserPidSet(profileName);+        // v2.0.31: match by the window's UNIQUE off-screen BIRTH POSITION, not by pid membership.+        // pup births every new window at top:-32000 and a unique birthLeft — no other app parks+        // there — so that coordinate IS the identity. The old pid filter (pupBrowserPidSet) came up+        // empty for the shared adom-you Chrome process (its real pid is often untracked), so birth+        // capture silently failed and the window fell through to the geometry heuristic that cannot+        // disambiguate a crowded profile — the raw-Chrome-icon bug John caught.         let picked = null;         for (let i = 0; i < 12 && !picked; i++) {           const rows = await enumChromeWidgetWindows();-          const off = rows.filter(r => pids.has(r.pid) && r.L < -10000);-          if (off.length === 1) picked = off[0].h;-          else if (off.length > 1) { for (const sc of [1, 1.25, 1.5, 1.75, 2]) { const m = off.find(r => Math.abs(r.L - Math.round(birthLeft * sc)) <= 40); if (m) { picked = m.h; break; } } }+          const off = rows.filter(r => r.T < -10000);   // pup's birth zone (top:-32000)+          for (const sc of [1, 1.25, 1.5, 1.75, 2, 0.8, 1.4]) { const m = off.find(r => Math.abs(r.L - Math.round(birthLeft * sc)) <= 60); if (m) { picked = m.h; break; } }+          if (!picked && off.length === 1) picked = off[0].h;           if (!picked) await new Promise(r => setTimeout(r, 150));         }         if (picked) { fresh.__pupHwnd = picked; console.log(`[hwnd] birth-resolved new window on "${profileName}" -> ${picked} (off-screen L≈${birthLeft})`); }