Pup - the AI's own browser

@@ -1,5 +1,15 @@ # Changelog — Adom Desktop Puppeteer Bridge +## 1.8.63 — 2026-07-15 — force:true adopted (AD 1.9.115): the launch park is one AD call++AD 1.9.115 shipped the follow-up: `desktop_set_window_state {state:'bottom', force:true}` bottoms+the window EVEN IF it is currently foreground (verified on ADOMGPU: sentToBack:true despite+wasForeground:true). pup now always passes force:true — the launch park is a single AD call in+the common case. The legacy PS fallback is RETAINED but auto-obsoletes: it only fires on AD+1.9.114 (force ignored, skip-on-foreground) or older (no state:'bottom' at all); delete it once+the fleet is ≥1.9.115. It was kept deliberately — removing it while AdomLapper was still on+1.9.114 would have regressed the post-restart foreground-reassignment case on John's primary box.+ ## 1.8.61 — 2026-07-14 — 100% direct-API window management (AD shipped state:'bottom')  AD 1.9.114 shipped pup's feature request: `desktop_set_window_state {state:'bottom'}` — native

@@ -1,10 +1,10 @@ {   "manifest_version": 1,   "name": "puppeteer",-  "version": "1.8.62",-  "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.8.62/adom-bridge-puppeteer-v1.8.62.zip",-  "sha256": "18c6d4e21f59380bbb5c95a16d41d829c7288aca6b47a09899d9d20893c2fced",-  "size": 171665,+  "version": "1.8.63",+  "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.8.63/adom-bridge-puppeteer-v1.8.63.zip",+  "sha256": "9beca556e04963de8d5e0b37922751cc1a14da4d324e45f54f2169c8cec382ea",+  "size": 171785,   "verbPrefixes": [     "browser_",     "desktop_recorder_",@@ -12,5 +12,5 @@   ],   "healthEndpoint": "/status",   "statusVerb": "browser_readiness",-  "released_at": "2026-07-14T00:00:00Z"+  "released_at": "2026-07-15T00:00:00Z" }

@@ -1 +1 @@-1.8.62\ No newline at end of file+1.8.63\ No newline at end of file

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

@@ -2028,7 +2028,11 @@ async function parkSessionWindowDirect(page, sessionId) {     // that rejects state:'bottom'): the old find_window + osBottomUnlessForeground PS pair.     const adBottom = async () => {       try {-        const r = await chrome.adCommand('desktop_set_window_state', { titleContains: `(session: ${sessionId}`, state: 'bottom' }, { timeoutMs: 5000 });+        // v1.8.63: force:true (AD ≥1.9.115) — bottom even if the window is currently foreground.+        // At launch, foreground is NOT a user signal (post-restart reassignment), so pup always+        // forces. On AD 1.9.114 the arg is ignored (skip-on-foreground) and the wasForeground+        // fallback below covers it; that fallback auto-obsoletes as desktops update.+        const r = await chrome.adCommand('desktop_set_window_state', { titleContains: `(session: ${sessionId}`, state: 'bottom', force: true }, { timeoutMs: 5000 });         if (r && r.success === false) return { ok: false, err: r.error || 'error' };         const raw = r && (typeof r.output === 'string' ? r.output : JSON.stringify(r.output || ''));         const o = raw ? JSON.parse(raw) : {};@@ -2041,13 +2045,12 @@ async function parkSessionWindowDirect(page, sessionId) {       const z = await adBottom();       if (z.ok) { bottomed = true; break; }       lastErr = z.err || 'error';-      // Two cases need the legacy PS path:+      // Two cases need the legacy PS path (BOTH auto-obsolete as desktops update to AD ≥1.9.115,+      // whose force:true is honored above — delete this block once the fleet is there):       //  (a) older AD that rejects state:'bottom' entirely;-      //  (b) AD ≥1.9.114 SKIPS a foreground window (wasForeground:true, sentToBack:false — the-      //      exact skip-on-foreground semantics pup requested). But at LAUNCH, foreground is-      //      NOT a user signal (post-restart foreground reassignment — the v61-3 case), and-      //      pup's doctrine is force-bottom. Until AD grows a force:true flag (follow-up-      //      filed), force via the legacy PS for this rare case.+      //  (b) AD 1.9.114 exactly: has state:'bottom' but ignores force and SKIPS a foreground+      //      window (wasForeground:true, sentToBack:false). At LAUNCH, foreground is NOT a user+      //      signal (post-restart foreground reassignment — the v61-3 case), so force via PS.       if (z.wasForeground || /invalid|unknown|must be one of|maximize\|minimize/i.test(lastErr)) {         let hwnd = null;         try {