Pup - the AI's own browser

@@ -1,10 +1,10 @@ {   "manifest_version": 1,   "name": "puppeteer",-  "version": "2.0.182",-  "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.182/adom-bridge-puppeteer-v2.0.182.zip",-  "sha256": "534450e15357aa1e6fe64a07f638b0358efadfe9d325490a33a712eec9f8119c",-  "size": 921349,+  "version": "2.0.183",+  "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.183/adom-bridge-puppeteer-v2.0.183.zip",+  "sha256": "97c99496ae4f7e34af86c6f872ced0e38a4a3d39105ad1f75cfc85d35ec0444f",+  "size": 921642,   "verbPrefixes": [     "browser_",     "desktop_recorder_",

@@ -1 +1 @@-2.0.182+2.0.183

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

@@ -4194,7 +4194,11 @@ async function stampPupIdentity(sessionId, opts) {         // v1.9.245: the stamp DESTROYED and RECREATED the taskbar button, so whatever overlay was         // painted is gone from glass. Mark bare so the 10s enforcer repaints the new button; also         // drop the cached hwnd — the new button may live on a new handle.-        sess._appOverlay = false; sess._overlayEnforceAt = 0; sess._hwnd = null;+        // v2.0.183: keep sess._hwnd. The v1.9.245 comment feared "the new button may live on a new+        // handle", but a taskbar BUTTON is not the window HWND — an AUMID re-stamp never changes the+        // OS window handle, and nulling it here made every sweep re-resolve every window by bounds+        // (an enum_windows storm, John's 2nd spam report). hwndBelongsToPup still validates on use.+        sess._appOverlay = false; sess._overlayEnforceAt = 0;         // The jump list attaches to the AUMID — a new appId starts with NO jump list, so force a         // re-attach on the next updateWikiJumplist pass.         if (pupSettings().jumpLists === 'on') updateWikiJumplist(sess, sessionId).catch(() => {});   // deduped by _wikiJumplistKey@@ -5312,6 +5316,11 @@ async function updateTabCountBadge(session, sessionId) { // every rescan. async function brandSweep(reason) {   if (minimalTouch()) return;   // v1.9.185 minimal-touch: no cosmetic/shell machinery pushed at Chrome+  // v2.0.183 (John, 2nd enum report: "you're spamming enum_windows again"): a sweep re-stamps and+  // NUDGES every window, and each nudge fires a window-opened event whose drain kicked+  // reclaimUnmanagedWindows (an enum) — pup reacting to its own sweep, per window. The per-nudge+  // guard only covered ~6s; a 7-window sweep spans longer. Blanket the whole sweep.+  _nudgeUntil = Date.now() + 45000;   // v1.9.41 (audit): re-stamp CATEGORY icons for every live session. Windows that predate the   // category work, or that were recovered across a bridge restart, kept the plain default tile   // forever because nothing re-evaluated them. Found by auditing my own taskbar: a long-lived