Pup - the AI's own browser

@@ -1,10 +1,10 @@ {   "manifest_version": 1,   "name": "puppeteer",-  "version": "1.9.76",-  "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.76/adom-bridge-puppeteer-v1.9.76.zip",-  "sha256": "7183d1e29b832684698b121a8f32a88a083c333da43a7125119c538c69d4a708",-  "size": 313377,+  "version": "1.9.77",+  "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.77/adom-bridge-puppeteer-v1.9.77.zip",+  "sha256": "ddf72a38c179d85552be2ec16c3d4721a5f625e639eddf2ee8e999e93211c81f",+  "size": 313835,   "verbPrefixes": [     "browser_",     "desktop_recorder_",

@@ -1 +1 @@-1.9.76+1.9.77

@@ -2,7 +2,7 @@   "manifest_version": 1,   "name": "puppeteer",   "displayName": "Puppeteer (Chrome for Testing + Native)",-  "version": "1.9.76",+  "version": "1.9.77",   "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.",   "homepage": "https://wiki.adom.inc/adom/adom-desktop",   "author": "Adom Inc.",

@@ -5572,7 +5572,17 @@ const server = http.createServer(async (req, res) => {             const _pinnedBranded = !!(_def && _def.kind && !/chrome-for-testing|cft/i.test(_def.kind));             const _cftCached = (() => { try { return chrome.detectChrome().installed; } catch (e) { return false; } })();             const _sessionAlive = sessions.has(args.sessionId) || !!(browsers.get(args.profile || args.sessionId) && browsers.get(args.profile || args.sessionId).browser);-            const _needsCft = !_pinnedBranded && !_cftCached && !_sessionAlive;+            // v1.9.77 — NEVER BLOCK ON A CfT DOWNLOAD WHEN A SYSTEM BROWSER EXISTS (wiki issue #15,+            // AdityaAngajala's second report). This gate forced a ~191 MB Chrome-for-Testing download even+            // though browser_readiness reported a healthy system Edge AND Chrome, so a machine with TWO+            // perfectly good browsers could not open a window at all — and the download never finalised+            // because its cache dir was half-populated. It also contradicted our own README: 'Chrome for+            // Testing is auto-fetched only as a last resort when the box has no Chromium browser at all.'+            // CfT is still PREFERRED (launchCandidates orders it first, and prewarm still fetches it in the+            // background) — preference is fine, blocking is not. Only gate when there is genuinely nothing+            // drivable on the machine.+            const _hasSystemBrowser = (rd.candidates || []).some(c => c && c.source === 'system');+            const _needsCft = !_pinnedBranded && !_cftCached && !_sessionAlive && !_hasSystemBrowser;             if (!rd.ready || _needsCft) {               if (rd.installPhase === 'failed') {                 sendJSON(res, {