Pup - the AI's own browser

@@ -1,10 +1,10 @@ {   "manifest_version": 1,   "name": "puppeteer",-  "version": "2.0.242",-  "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.242/adom-bridge-puppeteer-v2.0.242.zip",-  "sha256": "75765d4bf426781a833a42075566dcf241b776c57205cbe93f7fec01a1904ff3",-  "size": 945211,+  "version": "2.0.243",+  "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.243/adom-bridge-puppeteer-v2.0.243.zip",+  "sha256": "95ee9fd82a293b1998a7bc2e719f9ea8396a1cdbb7d45cbf93f6057845346679",+  "size": 945595,   "verbPrefixes": [     "browser_",     "desktop_recorder_",@@ -12,5 +12,5 @@   ],   "healthEndpoint": "/status",   "statusVerb": "browser_readiness",-  "released_at": "2026-08-18T14:41:03.506337Z"+  "released_at": "2026-08-18T14:44:24.694924Z" }

@@ -1 +1 @@-2.0.242\ No newline at end of file+2.0.243\ No newline at end of file

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

@@ -9182,7 +9182,7 @@ async function flashViaAD(sessionId, opts) {   // USER-initiated flashes too. minimal-touch exists to stop pup's AUTOMATIC machinery from touching   // the taskbar; a human clicking "flash" in the dashboard is the opposite of automatic. Callers that   // carry explicit user intent pass {force:true} and go through; everything automatic stays gated.-  if (minimalTouch() && !(opts && opts.force)) return;+  if (minimalTouch() && !(opts && opts.force)) return { _skipped: 'minimal-touch' };   opts = opts || {};   if (process.platform !== 'win32' || !sessionId) return null;   // v1.9.242 (John: "i just hit 'clear flashes' and it didn't clear all your flashes"). Same disease@@ -15306,7 +15306,12 @@ const server = http.createServer(async (req, res) => {               return;             }             // v1.8.43: route the FLASH through AD's desktop_flash_window (reliable, native).-            const r = await flashViaAD(session._sessionId || sessionId, { stop });+            // v2.0.243 (pup-bridge#58, real root cause): pup_alert_window is an EXPLICIT request from+            // the caller — never pup's automatic machinery — so it must not be swallowed by the+            // minimal-touch gate. That gate is what made the flash silently no-op on John's box+            // while the response blamed the window title, which sent the investigation at the+            // title/hwnd resolver instead of at the gate.+            const r = await flashViaAD(session._sessionId || sessionId, { stop, force: true });             let applied = false;             try { const o = r && abPayload(r); applied = !!(o && (o.ok || o.count)); } catch (e) {}             // v1.8.45: FLASHW_STOP only stops the PULSE — the Win11 attention tint persists@@ -15327,7 +15332,10 @@ const server = http.createServer(async (req, res) => {               ? (trulyCleared                   ? `Flash truly cleared — activated the window off-screen to drop the Win11 attention tint (${clearMethod}), then handed focus back. No pop, no focus steal.`                   : `Could not fully clear (${clearMethod || 'window not found'}). FLASHW_STOP ran (applied=${applied}) but the persistent tint needs activation and that step failed.`)-              : (applied ? 'Flashed the taskbar (finite 4-count) via AD, no focus steal. Pass {stop:true} to clear.' : 'AD desktop_flash_window did not match the window (title changed? window closed?).');+              : (applied ? 'Flashed the taskbar (finite 4-count) via AD, no focus steal. Pass {stop:true} to clear.'+                : (r && r._skipped === 'minimal-touch'+                  ? 'Skipped: this desktop runs pup in MINIMAL-TOUCH mode, which suppresses pup-initiated taskbar effects. Turn it off in the dashboard Settings (or pup_configure {minimalTouch:"off"}) if you want alerts to flash.'+                  : 'AD desktop_flash_window could not act on this window. pup targets it by HANDLE (title tags are off by default), so this usually means the window closed or the handle went stale — pup_window_info shows the handle pup is using.'));             sendJSON(res, { success: true, output: JSON.stringify({ ok: true, sessionId, alerted: !stop, cleared: stop ? trulyCleared : false, applied, clearMethod, _hint: hint }) });           } catch (e) {             sendJSON(res, { success: false, error: `Alert failed: ${e.message}` });