Pup - the AI's own browser

@@ -1,5 +1,21 @@ # Changelog — Adom Desktop Puppeteer Bridge +## 1.9.41 — 2026-07-20 — Self-audit of the live taskbar: two icon bugs found and fixed++John: "look at your taskbar icons and audit yourself." Doing that on the real taskbar found two+defects that no amount of reasoning had surfaced:++1. An Adom app was wearing the WEB globe. classifyUrl demanded BOTH a *.adom.cloud host AND a+   /proxy/ path segment, so an app served at a bare slug host (project-manager-xxxx.adom.cloud)+   fell through to "web". Any *.adom.cloud host is now an Adom app.+2. A long-lived window still wore the plain DEFAULT tile with no category at all. Windows that+   predate the category work, or that were recovered across a bridge restart, were never+   re-evaluated. brandSweep now clears each session's cached category and re-runs the full+   refresh, so every live window converges on a correct category icon.++Also corrected a claim I made to John: the extra split sessions I could not explain came from+adom-tsci, a different window than the hybrid one he was testing, not from his drag.+ ## 1.9.40 — 2026-07-20 — Adopted windows are re-tagged, so they stop being invisible and colliding  John dragged a tab out of a 3-category window and got sloppy results: one new window kept the bare

@@ -1,10 +1,10 @@ {   "manifest_version": 1,   "name": "puppeteer",-  "version": "1.9.40",-  "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.40/adom-bridge-puppeteer-v1.9.40.zip",-  "sha256": "a5544bbbc53d1d1d65eea07b148afb6239880e99f0312fee05e37690f9e984dd",-  "size": 290611,+  "version": "1.9.41",+  "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.41/adom-bridge-puppeteer-v1.9.41.zip",+  "sha256": "e7a6f37d433bd8a930746c8ef756e938fd981c959983e753aa4312ea873cc03f",+  "size": 290954,   "verbPrefixes": [     "browser_",     "desktop_recorder_",

@@ -1 +1 @@-1.9.40\ No newline at end of file+1.9.41\ No newline at end of file

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

@@ -1728,7 +1728,10 @@ function classifyUrl(u) {     if (isAdomUrl(u)) return 'wiki';     const h = new URL(u).hostname;     if (/^(localhost|127\.0\.0\.1|\[::1\])$/i.test(h)) return 'app';-    if (/\.adom\.cloud$/i.test(h) && /\/proxy\//.test(new URL(u).pathname)) return 'app';+    // v1.9.41 (audit): ANY *.adom.cloud slug host is an Adom app, with or without a /proxy/ path.+    // The old rule demanded /proxy/, so an app served at a bare slug (project-manager-xxxx.adom.cloud)+    // was labelled "web" and wore the globe. Caught by auditing my own taskbar.+    if (/\.adom\.cloud$/i.test(h)) return 'app';     if (/^(about|chrome|edge|devtools):/i.test(u) || u.startsWith('file:')) return null; // ignore chrome pages     return 'web';   } catch (e) { return null; }@@ -2072,6 +2075,17 @@ async function updateTabCountBadge(session, sessionId) { // strand a window un-resolvable) then re-stamps it. Runs at startup (post-reattach) and after // every rescan. async function brandSweep(reason) {+  // 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+  // window sat on the default icon while its neighbours showed proper categories.+  try {+    for (const [sid, sess] of [...sessions]) {+      sess._lastCat = undefined;               // force a real re-evaluation+      refreshWindowChrome(sess, sid).catch(() => {});+    }+  } catch (e) {}+   if (process.platform !== 'win32') return;   let n = 0;   for (const [sid, sess] of sessions) {