Pup - the AI's own browser

@@ -1,10 +1,10 @@ {   "manifest_version": 1,   "name": "puppeteer",-  "version": "1.9.54",-  "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.54/adom-bridge-puppeteer-v1.9.54.zip",-  "sha256": "d2eae67164b17c3778081146a3c3c456bd6b9f2aa31d1ab22b42927908c9d225",-  "size": 300830,+  "version": "1.9.55",+  "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.55/adom-bridge-puppeteer-v1.9.55.zip",+  "sha256": "2d7f0d8fec20553ac699db81b3d71d319daebb83f9368a86c19dd96a3c5ee9d2",+  "size": 310486,   "verbPrefixes": [     "browser_",     "desktop_recorder_",

@@ -1 +1 @@-1.9.54+1.9.55

@@ -2,7 +2,7 @@   "manifest_version": 1,   "name": "puppeteer",   "displayName": "Puppeteer (Chrome for Testing + Native)",-  "version": "1.9.54",+  "version": "1.9.55",   "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.",   "homepage": "https://wiki.adom.inc/adom/adom-desktop",   "author": "Adom Inc.",

@@ -1793,7 +1793,12 @@ let _jumplistSupported = null;   // null = unprobed (desktop_set_window_jumplist //   app      window + prompt      an Adom app: localhost or a cloud slug proxy URL //   web      globe                anything else on the internet //   mixed    stacked windows      tabs spanning more than one category-const PUP_ICON_DEFAULT = 'adom-pup-browser3.ico';+// v1.9.54: the RETIRED default was adom-pup-browser3.ico (the old "Adom mark fills the tile + tiny+// corner window" brand). John retired it in favour of the teal-tile category family. The new default+// (pup-cat-default9.ico) matches that family — teal tile + dark-teal window body + a neutral+// browser-chrome glyph — so a category-less window and the base Adom Pup identity no longer wear the+// old art anywhere. The 5 categories still override it via PUP_CAT_ICONS.+const PUP_ICON_DEFAULT = 'pup-cat-default9.ico'; // v1.9.45 — ICON GENERATION. BUMP THIS whenever the icon FILES or the AUMID branding mechanism // change, and every live window gets a freshly-painted taskbar button. //