Pup - the AI's own browser

@@ -1,10 +1,10 @@ {   "manifest_version": 1,   "name": "puppeteer",-  "version": "1.9.313",-  "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.313/adom-bridge-puppeteer-v1.9.313.zip",-  "sha256": "15e7805c0bc6b04b7a97884542ff28939251cec2248c33207baa9b3517e667bd",-  "size": 728736,+  "version": "1.9.314",+  "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.314/adom-bridge-puppeteer-v1.9.314.zip",+  "sha256": "bca6dd9cbfdb2b44b63e9c49ed9da1ea23e1c2bb47273cdd137e68633f12f48e",+  "size": 728844,   "verbPrefixes": [     "browser_",     "desktop_recorder_",

@@ -1 +1 @@-1.9.313+1.9.314

@@ -2,7 +2,7 @@   "manifest_version": 1,   "name": "puppeteer",   "displayName": "Puppeteer (Chrome for Testing + Native)",-  "version": "1.9.313",+  "version": "1.9.314",   "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. 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, browser_alert_window posts a native toast whose click focuses the window, browser_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-desktop",   "author": "Adom Inc.",

@@ -3390,7 +3390,6 @@ async function updateWikiJumplist(session, sessionId, opts) {   // opening it, the shell dismisses it. That is the "first right-click does nothing, second works"   // wonkiness. One commit per (button, view), never a redundant one.   const jlKey = `${appId}|${view || 'none'}|${pupSettings().jlViewTasks}|${pupSettings().jlCloseAll}`;-  console.log(`[jl-dbg] "${sessionId}" jl=${pupSettings().jumpLists} identSup=${_identitySupported} jlSup=${_jumplistSupported} url=${url ? url.slice(0,40) : 'null'} view=${view} dedup=${session._wikiJumplistKey === jlKey} appIdReg=${_registeredPupAumids.has(appId)} appId=${appId}`);   if (session._wikiJumplistKey === jlKey) return;   // v1.9.62: CLAIM the key before the await. Two callers (the pre-stamp brand and a timer-driven   // refresh) can both compute the same key and both find it unset, so both commit — a redundant@@ -3453,10 +3452,14 @@ async function updateWikiJumplist(session, sessionId, opts) {   }   if (pupSettings().jlCloseAll === 'on') tasks.push(closeAllTask);   // The shell ignores a jump list on an unregistered AUMID — ensure it's registered first.-  if (!_registeredPupAumids.has(appId)) {-    await registerPupAumid(appId, sessionId);-    if (!_registeredPupAumids.has(appId)) return;-  }+  // v1.9.314 (John: "i turned on jump lists and none of them work"): this guard REQUIRED the appId to+  // be in _registeredPupAumids, but that set is ONLY filled by desktop_register_app_identity, which+  // this AD build silently no-ops (measured: appIdReg=false for every window). So the guard RETURNED+  // before every commit and, because the dedup key is claimed just above, then dedup-skipped forever —+  // the real reason NONE of the jump lists worked. The per-window STAMP already associates the window+  // with this AUMID, and a direct desktop_set_window_jumplist (passing hwnd) commits fine without the+  // registry entry (proven). Register best-effort; NEVER block the commit on it.+  if (!_registeredPupAumids.has(appId)) { try { await registerPupAumid(appId, sessionId); } catch (e) {} }   // v1.9.60 — BRAND THE JUMP-LIST HEADER ROW (AD >= 1.9.153).   //   // The header row (the "Adom Pup" app tile above Pin/Close) is branded by passing `headerIcon` to