Pup - the AI's own browser

@@ -1,10 +1,10 @@ {   "manifest_version": 1,   "name": "puppeteer",-  "version": "2.0.265",-  "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.265/adom-bridge-puppeteer-v2.0.265.zip",-  "sha256": "d07abf4a91708d2c72188e2e36fbf9bcd392309e1287eef9477ca8138a1c0c55",-  "size": 959651,+  "version": "2.0.266",+  "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.266/adom-bridge-puppeteer-v2.0.266.zip",+  "sha256": "59f3af63e37c8a761df998e2b5555fbef8e27c3d05d57db372756e285d86508b",+  "size": 960040,   "verbPrefixes": [     "browser_",     "desktop_recorder_",@@ -12,5 +12,5 @@   ],   "healthEndpoint": "/status",   "statusVerb": "browser_readiness",-  "released_at": "2026-08-21T00:23:06.418256Z"+  "released_at": "2026-08-21T01:02:08.936470Z" }

@@ -1 +1 @@-2.0.265\ No newline at end of file+2.0.266\ No newline at end of file

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

@@ -11988,7 +11988,12 @@ select,input{background:#111b23;color:#e6edf3;border:1px solid #23303c;border-ra .texbase{width:44px;height:44px;border-radius:7px;display:block} .texmatrix{display:grid;grid-template-columns:repeat(3,minmax(70px,1fr));gap:10px;margin-bottom:8px} .mcell{position:relative;display:flex;flex-direction:column;align-items:center;gap:5px;padding:8px 4px;border:1px solid #30363d;border-radius:8px;cursor:pointer}-.mdef{position:absolute;top:4px;right:6px;font:600 8.5px 'Familjen Grotesk',sans-serif;color:#00b8b1;border:1px solid #00b8b1;border-radius:4px;padding:0 4px;letter-spacing:.04em}+/* v2.0.266 (John: "why is there some random 'default' pill in the upper right corner?"): this was+   position:absolute inside .stlbl, which is NOT positioned — so it escaped all the way out to #dlg+   and parked itself on top of the dialog's X button. An absolutely-positioned badge that depends on+   an ancestor nobody made relative is a trap; make it a plain INLINE chip in the label instead, where+   it reads as "1. tiles + overlay (current) default" and has no positioning to get wrong. */+.mdef{display:inline-block;margin-left:6px;vertical-align:1px;font:600 8.5px 'Familjen Grotesk',sans-serif;color:#00b8b1;border:1px solid #00b8b1;border-radius:4px;padding:0 4px;letter-spacing:.04em;white-space:nowrap} .mcell:hover{border-color:#8b949e} .mcell.mcur{border-color:#00b8b1;box-shadow:0 0 0 1px #00b8b1 inset} .mic{position:relative;display:inline-block}@@ -11997,11 +12002,14 @@ select,input{background:#111b23;color:#e6edf3;border:1px solid #23303c;border-ra .texnames{display:flex;flex-wrap:wrap;gap:12px;padding-top:10px;border-top:1px solid #30363d} .texdim{opacity:.45} .st6{display:flex;flex-direction:column;gap:8px}-.strow6{display:flex;align-items:center;gap:12px;padding:7px 10px;border:1px solid #30363d;border-radius:8px;cursor:pointer}+/* v2.0.266: flex-wrap + position:relative. Measured live: this row's content wanted 516px inside a+   439px strip, so the sample icons spilled past .texstrip's dark background and drew a hard vertical+   seam down the panel ("why is the background behind the taskbar identity choices so whacked"). */+.strow6{position:relative;display:flex;align-items:center;flex-wrap:wrap;gap:12px;padding:7px 10px;border:1px solid #30363d;border-radius:8px;cursor:pointer} .strow6:hover{border-color:#8b949e} .strow6.mcur{border-color:#00b8b1;box-shadow:0 0 0 1px #00b8b1 inset}-.stlbl{flex:0 0 175px;font:600 12px 'Familjen Grotesk',sans-serif;color:#c9d1d9}-.sticons{display:flex;gap:10px;flex-wrap:wrap;align-items:center}+.stlbl{flex:0 0 150px;font:600 12px 'Familjen Grotesk',sans-serif;color:#c9d1d9;line-height:1.35}+.sticons{flex:1 1 220px;min-width:0;display:flex;gap:10px;flex-wrap:wrap;align-items:center;padding:7px 7px 0 0} .mbcard{position:absolute;top:-7px;right:-7px;width:20px;height:20px;border-radius:5px;background:#202124;display:flex;align-items:center;justify-content:center;overflow:hidden} .mbcard img{width:16px;height:16px;object-fit:contain} .srow{display:flex;align-items:flex-start;gap:12px;padding:11px 0;border-bottom:1px solid #21262d}@@ -12516,7 +12524,7 @@ function paintThreadExamples(){       var ptxt = ov         ? 'ALL pup windows share this ONE stock Chrome button. They stay separate windows: hover the button and Windows fans out a preview of each (drawn above). You just cannot ungroup them on the bar, because the per-app identity that separates buttons is exactly what plain mode removes. The single badge belongs to the most recently updated window.'         : 'ALL pup windows share this ONE stock Chrome button. They stay separate windows: hover the button and Windows fans out a preview of each (drawn above). You just cannot ungroup them on the bar, because the per-app identity that separates buttons is exactly what plain mode removes.';-      icons=plainGroup(ov)+'<span class="texn" style="align-self:center;max-width:330px;text-align:left">'+ptxt+'</span>';+      icons=plainGroup(ov)+'<span class="texn" style="align-self:center;flex:1 1 190px;min-width:0;max-width:100%;text-align:left">'+ptxt+'</span>';     }     return '<div class="strow6'+(cur?' mcur':'')+'" data-si="'+i+'" title="click to switch to this state">'       +'<span class="stlbl">'+lbl+(cur?' (current)':'')+(isDefault?' <span class="mdef">default</span>':'')+'</span>'