Pup - the AI's own browser

@@ -1,10 +1,10 @@ {   "manifest_version": 1,   "name": "puppeteer",-  "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,+  "version": "2.0.348",+  "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.348/adom-bridge-puppeteer-v2.0.348.zip",+  "sha256": "661ba99a5d2988f11525754abbcb7acb04226345f04e2f9a2c091ac929fb468b",+  "size": 1521578,   "verbPrefixes": [     "browser_",     "desktop_recorder_",@@ -12,5 +12,5 @@   ],   "healthEndpoint": "/status",   "statusVerb": "browser_readiness",-  "released_at": "2026-08-25T14:38:55.779005Z"+  "released_at": "2026-08-25T14:42:36.014015Z" }

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

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

@@ -12495,9 +12495,16 @@ header{position:sticky;top:0;z-index:10;background:#161b22;border-bottom:1px sol    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. */+   2.5.0 no longer cares WHICH element carries the padding: it finds the nearest scrolling ancestor+   and checks that the panel sits 16px inside it on both sides. The contract is where the edges+   land, not the structure. (Earlier versions named an element and were wrong twice: measuring+   documentElement failed correct app-shell pages by a scrollbar width, and measuring the mount div+   would have red-lined every page that carried the gutter on an outer container.)+   pup stays with the TOKEN rather than nesting, and that is now the fleet ruling for this shape:+   the pill row and filter bar below carry FULL-BLEED bottom borders as separators, and a rule that+   spans the pane reads as a divider between regions, while an inset one reads as a card edge. The+   panel is the only card in that stack, so the separators stay full width and the gutter is shared+   through one token instead. */ :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}