Pup - the AI's own browser

@@ -1,10 +1,10 @@ {   "manifest_version": 1,   "name": "puppeteer",-  "version": "1.9.347",-  "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.347/adom-bridge-puppeteer-v1.9.347.zip",-  "sha256": "5a97672de93fa2d498d1fd1c50aaf83b9d66514d984827e6838fc932000e9498",-  "size": 636551,+  "version": "1.9.348",+  "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.348/adom-bridge-puppeteer-v1.9.348.zip",+  "sha256": "fe9211573dc66b4ac4513a407b9016fe3aa887dd4809ed705ffeb2839f5e864d",+  "size": 636666,   "verbPrefixes": [     "browser_",     "desktop_recorder_",

@@ -1 +1 @@-1.9.347+1.9.348

@@ -2,7 +2,7 @@   "manifest_version": 1,   "name": "puppeteer",   "displayName": "Puppeteer (Chrome for Testing + Native)",-  "version": "1.9.347",+  "version": "1.9.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. 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. 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, browser_alert_window posts a native toast whose click focuses the window, browser_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-desktop",   "author": "Adom Inc.",

@@ -3154,7 +3154,7 @@ const PUP_ICON_DEFAULT = 'pup-cat-default9.ico'; // already-created ones white, because their tiles were baked while the AUMID was still unbranded. // Folding a generation token into the appId turns an icon change into a NEW appId, which forces the // shell to create a NEW button, which is the ONLY thing that repaints. Cost is one button rebuild.-const PUP_ICON_GEN = 'i6';   // i6: EMPTY transparent notch (removed the baked Adom-mark that bled through the overlay). BUMPED because the+const PUP_ICON_GEN = 'i7';   // i7 (John): NO NOTCH — base tile is a FULL solid icon; the overlay carries its own background now. BUMPED because the // icon FILES changed — the AUMID appId carries this token, so a new gen forces Windows to CREATE A NEW // BUTTON that reads the new (notched) icon. Same-appId re-stamps do NOT repaint a baked Win11 tile, which // is why the notch never appeared on the live button until this bump. (i3 = pre-notch PNG-frame icons.)@@ -3263,18 +3263,13 @@ async function _buildNotchedIco(sharp, srcPath, destPath) {   if (!largest) throw new Error('no PNG frame in ' + path.basename(srcPath));   const frames = [];   for (const N of [256, 128, 64, 48, 32, 16]) {-    const base = await sharp(largest).resize(N, N, { fit: 'contain', background: { r: 0, g: 0, b: 0, alpha: 0 } }).png().toBuffer();-    const s = Math.round(N * NOTCH.frac), over = Math.round(N * NOTCH.over), rx = Math.round(N * NOTCH.rx);-    // SQUARE notch: the rect extends `over` px above the top and past the right edge, so only the inner-    // (bottom-left) corner stays on-canvas and shows the radius — the notch reads as a square opening,-    // not a circular blob. Matches the square overlay favicon.-    const mask = Buffer.from(`<svg xmlns="http://www.w3.org/2000/svg" width="${N}" height="${N}"><rect x="${N - s}" y="${-over}" width="${s + over}" height="${s + over}" rx="${rx}" ry="${rx}" fill="#fff"/></svg>`);-    // v1.9.337 — REVERT the baked Adom-mark fallback (John, rightly): baking a mark into the notch-    // sabotages the whole point (the taskbar showing through cleanly) AND it BLEEDS THROUGH the often--    // transparent overlay favicon painted on top. The notch stays a clean, EMPTY transparent cutout —-    // nothing goes in it. The overlay is kept reliably present by the 4s enforcer + the per-event-    // recompute triggers, so a persistently-empty notch isn't a real state to paper over.-    const png = await sharp(base).composite([{ input: mask, blend: 'dest-out' }]).png().toBuffer();   // dest-out punches a transparent notch; nothing else+    // v1.9.348 (John): NO NOTCH. The base taskbar tile is a FULL, solid icon again. The notch was the+    // wrong place to put the overlay's background — it carved a hole in the base tile (so a transparent+    // overlay favicon had *something* behind it), but that made the base icon look chewed-up AND the+    // hole bled through the favicon painted on top. The background now lives ON THE OVERLAY badge itself+    // (see applyAppOverlay: a dark, teal-edged card behind the favicon), so the base stays a clean full+    // tile and every overlay favicon reads well regardless of its own transparency.+    const png = await sharp(largest).resize(N, N, { fit: 'contain', background: { r: 0, g: 0, b: 0, alpha: 0 } }).png().toBuffer();     frames.push({ size: N, png });   }   fs.mkdirSync(path.dirname(destPath), { recursive: true });@@ -4905,9 +4900,19 @@ async function applyAppOverlay(session, sessionId) {           const BSZ = 48, MSZ = 18;   // 18/48 = 3/8           let img = sharpMod({ create: { width: BSZ, height: BSZ, channels: 4, background: { r: 0, g: 0, b: 0, alpha: 0 } } });           const layers = [];+          // v1.9.348 (John): the overlay carries its OWN background now that the base tile has no notch.+          // Site favicons are frequently transparent, and painted straight onto the taskbar tile they+          // looked terrible (floating fragments over whatever was behind). Put a solid, dark, teal-edged+          // rounded CARD behind the favicon so every badge reads as one clean unit and transparent+          // favicons get a proper, consistent backdrop. This is where the "notch background" belongs.+          const _bg = `<svg xmlns="http://www.w3.org/2000/svg" width="${BSZ}" height="${BSZ}"><rect x="1.5" y="1.5" width="${BSZ - 3}" height="${BSZ - 3}" rx="9" ry="9" fill="#0d1117" stroke="#00b8b1" stroke-width="2.5"/></svg>`;+          layers.push({ input: await sharpMod(Buffer.from(_bg)).png().toBuffer(), gravity: 'northwest' });+          // Favicon inset inside the card so the card's dark fill + teal edge frame it (and any+          // transparent area of the favicon shows the card, not the taskbar behind it).+          const FIN = 5;           // Use the ALREADY-DECODED bytes — re-decoding src.b64 here is what broke .ico (sharp throws           // on the raw container), silently dropping the favicon and leaving the Adom mark alone.-          if (iconPng) layers.push({ input: await sharpMod(iconPng).resize(BSZ, BSZ, { fit: 'cover' }).png().toBuffer(), gravity: 'northwest' });+          if (iconPng) layers.push({ input: await sharpMod(iconPng).resize(BSZ - FIN * 2, BSZ - FIN * 2, { fit: 'cover' }).png().toBuffer(), top: FIN, left: FIN });           // v1.9.331 (John: "why put an EXTRA adom mark on the overlay when AUMID is ON? the teal           // category tile is already the 'this is Adom pup' indicator"). Right. The Adom mark on the           // favicon exists ONLY to brand the badge when the BASE icon is plain Chrome (AUMID off). When