Pup - the AI's own browser

@@ -1,10 +1,10 @@ {   "manifest_version": 1,   "name": "puppeteer",-  "version": "2.0.140",-  "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.140/adom-bridge-puppeteer-v2.0.140.zip",-  "sha256": "af942116b46504c69563db0f2915c7b32a5ed31fa350685f576aca7cf9bee5a4",-  "size": 891316,+  "version": "2.0.141",+  "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.141/adom-bridge-puppeteer-v2.0.141.zip",+  "sha256": "83dbac9ebf9d93e14060f3fba60b3d0d8cf25640ab7163eeef2041578d08eddd",+  "size": 892474,   "verbPrefixes": [     "browser_",     "desktop_recorder_",

@@ -1 +1 @@-2.0.140+2.0.141

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

@@ -593,10 +593,66 @@ async function neutralizeDebugger(page) {   } catch (e) {} } +// v2.0.141 (John: "surf as normal consumer chrome — that's our right, this really is me surfing+// from a normal chrome, we just use CfT so we can automate it"). Chrome for Testing's UA STRING is+// already indistinguishable from consumer Chrome, but its CLIENT-HINTS brands are not: CfT reports+// only [Not/A)Brand, Chromium] while consumer Google Chrome includes a "Google Chrome" brand.+// Cloudflare/Akamai read exactly that Sec-CH-UA brand list and wall the missing-Google-Chrome case+// as a non-consumer browser (measured live: TI/ST/ams load, but DigiKey/Mouser/Arrow/SnapEDA/CSE/+// Octopart all served "Just a moment…"). This override makes every page present as Google Chrome —+// UA header AND the userAgentData brands, kept CONSISTENT (a UA/brand mismatch is itself a bot+// tell) — via CDP Network.setUserAgentOverride (what page.setUserAgent(ua, meta) drives). The major+// version is read from the live UA so a CfT bump never drifts it. This is not spoofing a different+// device; it is the same Windows Chrome the user runs, correctly declaring itself as Google Chrome.+let _uaOverride = null;   // { ua, metadata } — computed once from the running browser+async function computeConsumerUA(page) {+  if (_uaOverride) return _uaOverride;+  let ua = '';+  try { ua = await page.browser().userAgent(); } catch (e) {}+  if (!ua) { try { ua = await page.evaluate(() => navigator.userAgent); } catch (e) {} }+  if (!ua) return null;+  const m = ua.match(/Chrome\/(\d+)(?:\.\d+)*/);+  const major = m ? m[1] : '148';+  const full = (ua.match(/Chrome\/([\d.]+)/) || [])[1] || (major + '.0.0.0');+  // Consumer Chrome's brand triplet (GREASE brand + Chromium + Google Chrome). Order is not+  // load-bearing; the PRESENCE of "Google Chrome" is what CF checks.+  const brands = [+    { brand: 'Not/A)Brand', version: '99' },+    { brand: 'Google Chrome', version: major },+    { brand: 'Chromium', version: major },+  ];+  _uaOverride = {+    ua,+    metadata: {+      brands,+      fullVersionList: [+        { brand: 'Not/A)Brand', version: '99.0.0.0' },+        { brand: 'Google Chrome', version: full },+        { brand: 'Chromium', version: full },+      ],+      fullVersion: full,+      platform: 'Windows', platformVersion: '15.0.0',+      architecture: 'x86', bitness: '64', model: '', mobile: false,+      wow64: false,+    },+  };+  return _uaOverride;+}+async function applyConsumerUA(page) {+  try {+    const o = await computeConsumerUA(page);+    if (!o) return;+    // page.setUserAgent(ua, metadata) issues Network.setUserAgentOverride with userAgentMetadata,+    // which drives BOTH the UA request header and navigator.userAgentData / Sec-CH-UA consistently.+    await page.setUserAgent(o.ua, o.metadata);+  } catch (e) { /* best-effort — a page that refuses the override just keeps CfT's brands */ }+} function attachTab(session, sessionId, page, { makeActive = true, opener = 'user', openerTabId = null } = {}) {   const tabId = nextTabId(session);   const errors = [];   setupErrorCollection(page, errors);+  // v2.0.141: present as consumer Google Chrome on EVERY tab (see computeConsumerUA).+  applyConsumerUA(page);   // Immunize this tab against debugger-statement / breakpoint freezes (see neutralizeDebugger).   neutralizeDebugger(page);   // v1.9.78 — SURVIVE A RENDERER CRASH (wiki issue #16). Under many heavy-SPA tabs plus rapid