Pup - the AI's own browser

@@ -1,10 +1,10 @@ {   "manifest_version": 1,   "name": "puppeteer",-  "version": "2.0.346",-  "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.346/adom-bridge-puppeteer-v2.0.346.zip",-  "sha256": "aa4903f3ac7b7981f37dd0bf858e0f7188f782a86c0864e886246919d694799d",-  "size": 1520048,+  "version": "2.0.347",+  "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.347/adom-bridge-puppeteer-v2.0.347.zip",+  "sha256": "2eae48c18397872533fc0123442722fcab5ecf396c9f281f8fcb17c96088854e",+  "size": 1520647,   "verbPrefixes": [     "browser_",     "desktop_recorder_",@@ -12,5 +12,5 @@   ],   "healthEndpoint": "/status",   "statusVerb": "browser_readiness",-  "released_at": "2026-08-25T14:33:52.783177Z"+  "released_at": "2026-08-25T14:38:55.779005Z" }

@@ -1 +1 @@-2.0.346\ No newline at end of file+2.0.347\ No newline at end of file

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

@@ -12487,14 +12487,20 @@ header{position:sticky;top:0;z-index:10;background:#161b22;border-bottom:1px sol    old hand-rolled panel declared is DELETED rather than left beside the module: a stray .btn or    .ibtn declared after the module's rules is exactly how other apps silently lost their styling to    source order. What remains here is the status pill row, which is its own contract region. */-/* THE FLEET GUTTER (adom-ui-design 2.3.0): 16px a side on the container the panel mounts into,-   so the panel's border box is the pane MINUS 32. pup was full-bleed at 0px a side, which-   selfCheck could not see while it only measured inside the panel: four apps passed at John's-   identical 744px pane and rendered 735, 734, 702 and 694, and the 694 one dropped to ONE-   column while pup rendered two. Conformant panels, mismatched pages. The gutter belongs HERE-   rather than on the panel because the panel is shared and the page around it is not. */-#newbie{padding:0 16px}-.ledrow{display:flex;flex-wrap:wrap;gap:10px;padding:12px 16px;border-bottom:1px solid #30363d}+/* THE FLEET GUTTER (adom-ui-design 2.4.0). ONE number, declared once, used by the panel's mount+   container AND by every region under it, so they share an edge because there is a single source+   of truth rather than because two literals happen to match. That "by luck rather than by rule"+   distinction was my own observation about this page and it is now a fleet rule.+   pup was full-bleed at ZERO a side, not the ~4px it looked like: #newbie is a direct child of+   body with no padding, so the panel measured exactly clientWidth and the 9px gap from the 744+   pane was entirely the scrollbar. selfCheck could not see it while it only measured inside the+   panel.+   THE PADDING MUST BE ON THE MOUNT DIV, not on an outer wrapper: 2.4.0 measures the panel against+   panel.parentElement.parentElement, which IS #newbie, so wrapping #newbie in a padded container+   would leave #newbie itself flush and fail the row. */+:root{--gutter:16px}+#newbie{padding:0 var(--gutter)}+.ledrow{display:flex;flex-wrap:wrap;gap:10px;padding:12px var(--gutter);border-bottom:1px solid #30363d} .led-pill{display:inline-flex;align-items:center;gap:7px;background:#161b22;border:1px solid #30363d;border-radius:999px;padding:4px 12px;font-size:12.5px;cursor:default} .led-pill .d{width:8px;height:8px;border-radius:50%;flex:none} .led-pill .d.ok{background:#3fb950}.led-pill .d.warn{background:#d29922}.led-pill .d.fail{background:#f85149}