Pup - the AI's own browser

@@ -1,10 +1,10 @@ {   "manifest_version": 1,   "name": "puppeteer",-  "version": "1.9.216",-  "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.216/adom-bridge-puppeteer-v1.9.216.zip",-  "sha256": "fdc6345a40aaf068ae930f06498cdb2a4b226b9a08f893cea295d7b2cbdfc354",-  "size": 442621,+  "version": "1.9.217",+  "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.217/adom-bridge-puppeteer-v1.9.217.zip",+  "sha256": "7cac401e2f82ec56849fdaa8fc1daeb3314f2d41febf4ee6c735f46c08def853",+  "size": 443156,   "verbPrefixes": [     "browser_",     "desktop_recorder_",

@@ -1 +1 @@-1.9.216+1.9.217

@@ -2,7 +2,7 @@   "manifest_version": 1,   "name": "puppeteer",   "displayName": "Puppeteer (Chrome for Testing + Native)",-  "version": "1.9.216",+  "version": "1.9.217",   "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. browser_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. browser_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, browser_alert_window posts a native toast whose click focuses the window, browser_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-desktop",   "author": "Adom Inc.",

@@ -3813,6 +3813,32 @@ async function fetchPageFavicon(page) {       return out;     });   } catch (e) { return null; }+  // v1.9.217 (John: "the website being loaded has its favicon?" — dashboard-v2.adom.inc showed the+  // GENERIC icon). The bridge-side fetch below carries NO COOKIES, so any favicon behind auth returns+  // 401/403 and pup falls back to a generic icon. The old comment called that "rare"; it is not — it+  // hits EVERY authed Adom dashboard and app. So try IN-PAGE first: the page's own fetch carries its+  // cookies and same-origin favicons (the overwhelmingly common case, /favicon.svg on the same host)+  // resolve cleanly. Only if that fails do we fall back to the cookie-less bridge fetch, which is+  // still the right tool for a cross-origin icon the page itself cannot read.+  for (const href of (hrefs || [])) {+    if (href.startsWith('data:')) break;   // handled by the loop below+    try {+      const inPage = await withTimeout(page.evaluate(async (u) => {+        try {+          const r = await fetch(u, { credentials: 'include', cache: 'force-cache' });+          if (!r.ok) return null;+          const b = await r.blob();+          if (!b.size) return null;+          const b64 = await new Promise((res, rej) => { const fr = new FileReader(); fr.onload = () => res(String(fr.result).split(',')[1]); fr.onerror = rej; fr.readAsDataURL(b); });+          return b64 ? { b64, mime: b.type || '' } : null;+        } catch (e) { return null; }+      }, href), 4000, 'favicon-inpage').catch(() => null);+      if (inPage && inPage.b64) {+        console.log(`[overlay] favicon fetched IN-PAGE (with cookies) from ${href.slice(0, 70)}`);+        return { b64: inPage.b64, mime: inPage.mime || '', href };+      }+    } catch (e) {}+  }   for (const href of (hrefs || [])) {     try {       if (href.startsWith('data:')) {