Pup - the AI's own browser

@@ -1,10 +1,10 @@ {   "manifest_version": 1,   "name": "puppeteer",-  "version": "1.9.305",-  "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.305/adom-bridge-puppeteer-v1.9.305.zip",-  "sha256": "a0cc84141ab8976b581a079b05bb6dc3cda151ffdf21b590ef489c2b1bb03a37",-  "size": 727817,+  "version": "1.9.306",+  "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.306/adom-bridge-puppeteer-v1.9.306.zip",+  "sha256": "5635ccf6343aa09366813cc7c7119dfbcb8d127b8c3c2bfe76195c3b03980332",+  "size": 727795,   "verbPrefixes": [     "browser_",     "desktop_recorder_",

@@ -1 +1 @@-1.9.305+1.9.306

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

@@ -8815,22 +8815,23 @@ async function dashboardSnapshot() {     // dev-skills/pup-aumid-decisions). This branch remains ONLY to truthfully model windows that     // were stamped before the revert - the AUMID property lives on the window until it closes, so     // those really do keep their own taskbar buttons. New windows never enter it.-    // v1.9.298 (John, holding up a photo of the real taskbar next to the dashboard: "why is the list-    // of icons in the pup dashboard not matching what's in the windows taskbar?"). He is right, and-    // this was the miss: EVERY pup window on the real taskbar wears the teal pup TILE (measured, at-    // full resolution — not one Chrome-logo pup button exists). But the dashboard drew un-stamped-    // profiles with /dashboard/baseicon, which ExtractAssociatedIcon's the Chrome-for-Testing EXE and-    // returns the multicolor Chrome logo. So the dashboard invented Chrome-logo buttons that the-    // taskbar never shows. The base art is the pup tile for ALL pup windows regardless of stamp state-    // — use it unconditionally so the strip matches reality by construction. (Keying still splits-    // stamped vs process-grouped windows so the tooltip/LED rollup stays truthful.)-    let baseIcon = '/dashboard/stampicon?session=' + encodeURIComponent(w.sessionId);+    // v1.9.306 (John flashed his live windows so I could finally SEE the real taskbar clearly): my+    // 1.9.298 change was WRONG. I claimed "every pup window wears the teal TILE" from a blurry crop,+    // and forced the dashboard to draw teal for all. The flash proved the opposite: with aumidIcons+    // OFF (the settled default), the LIVE pup windows wear the **Chrome-for-Testing exe icon** + the+    // pup overlay — the teal tiles I saw were GHOST buttons from dead AUMID-stamped windows, not the+    // live ones. So the dashboard must show what the window ACTUALLY wears: the teal stamp tile ONLY+    // when the window is genuinely AUMID-stamped (_curAppId), otherwise the real Chrome-for-Testing+    // exe icon. That makes the strip match the glass again.+    let baseIcon;     if (w._curAppId) {       key = 'aumid:' + w._curAppId;       label = w.sessionId;+      baseIcon = '/dashboard/stampicon?session=' + encodeURIComponent(w.sessionId);     } else {       key = 'chrome-process:' + w.profile;       label = 'Chrome (' + w.profile + ')';+      baseIcon = '/dashboard/baseicon?profile=' + encodeURIComponent(w.profile);     }     if (!buttons.has(key)) buttons.set(key, { key, label, kind: 'process', baseIcon, grouping: minimalTouch() ? 'minimal-touch' : grouping, windows: [], badgeSession: null, badgeAt: 0, badgeVia: null });     const btn = buttons.get(key);