Pup - the AI's own browser

@@ -1,10 +1,10 @@ {   "manifest_version": 1,   "name": "puppeteer",-  "version": "2.0.281",-  "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.281/adom-bridge-puppeteer-v2.0.281.zip",-  "sha256": "aae294f0317f53f1bdec53218ccd6af397f5d075c5e1c058c069cf978852ce69",-  "size": 968320,+  "version": "2.0.282",+  "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.282/adom-bridge-puppeteer-v2.0.282.zip",+  "sha256": "f5f5935df9f91ba5ebbed962cda5398607910be644d61e7c28c77ffbe07c497d",+  "size": 968557,   "verbPrefixes": [     "browser_",     "desktop_recorder_",@@ -12,5 +12,5 @@   ],   "healthEndpoint": "/status",   "statusVerb": "browser_readiness",-  "released_at": "2026-08-22T19:39:37.207155Z"+  "released_at": "2026-08-22T20:04:02.403396Z" }

@@ -1 +1 @@-2.0.281\ No newline at end of file+2.0.282\ No newline at end of file

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

@@ -10531,13 +10531,19 @@ async function createPageInNewWindow(browser, profileName) {       try {         const _cl = typeof fresh._client === 'function' ? fresh._client() : fresh._client;         if (_cl) {+          // MEASURED (2026-08-22, DWM-thumbnail test): the one-shot pulse FAILED — Chrome RELEASES an+          // occluded window's page-render surface, so a single painted frame is discarded and the+          // window goes blank again (toolbar persists, page area blank). Foregrounding renders it+          // fully, proving only the occluded state drops the surface. So keep focus-emulation ON: the+          // renderer treats the page as the active tab and RETAINS its composited surface while+          // occluded, so the taskbar thumbnail and an instant reveal show the page, not blank. A STATIC+          // page schedules no rAF and composites once then idles, so this is not a continuous render+          // (verified separately) — unlike the highFps anti-throttle LAUNCH flags that also unthrottle+          // every timer fleet-wide (the issue-#14 drain).           await _cl.send('Emulation.setFocusEmulationEnabled', { enabled: true });-          // wait for TWO animation frames so a frame is actually painted+composited between them-          try { await fresh.evaluate(() => new Promise(r => requestAnimationFrame(() => requestAnimationFrame(() => r())))); } catch (e) {}-          await _cl.send('Emulation.setFocusEmulationEnabled', { enabled: false });-          console.log(`[render] pulsed ONE frame on the new window, then RELEASED focus-emulation — content is painted but the window is back to throttled/idle (battery-safe, not a continuous render)`);+          console.log(`[render] focus-emulation ON (retained) for the new window — its page-render surface is kept while occluded, so the taskbar thumbnail / reveal shows content, not blank`);         }-      } catch (e) { console.log(`[render] one-shot paint pulse failed: ${e && e.message}`); }+      } catch (e) { console.log(`[render] could not enable focus-emulation on the new window: ${e && e.message}`); }     }     return fresh;   } catch (e) {