Pup - the AI's own browser

@@ -1,10 +1,10 @@ {   "manifest_version": 1,   "name": "puppeteer",-  "version": "1.9.110",-  "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.110/adom-bridge-puppeteer-v1.9.110.zip",-  "sha256": "86d0aedbf1f584d547a49a7ef3e686a7b61bca6b94540a09c3373231f673b813",-  "size": 380830,+  "version": "1.9.111",+  "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.111/adom-bridge-puppeteer-v1.9.111.zip",+  "sha256": "f79c97f85e9080ae2e5dfe626bbd46fe6392360629bad361b993cdaa1139a7c2",+  "size": 381228,   "verbPrefixes": [     "browser_",     "desktop_recorder_",

@@ -1 +1 @@-1.9.110+1.9.111

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

@@ -2013,6 +2013,27 @@ function savePupSettings(patch) {  const PUP_APP_ID = 'Adom.Pup'; const PUP_DISPLAY_NAME = 'Adom Pup';+// v1.9.111 (John's ask) — SAY WHICH MODE the taskbar icon is showing, in the jump-list header row.+// pup already paints five different category icons (public wiki, signed-in wiki, Adom app, plain web,+// mixed) and already names them in the hover tooltip via CAT_LABEL, but the header row just said+// "Adom Pup", so the icon's meaning was guesswork. The header is width-constrained (the flyout is+// ~440px and "Close ALL Adom Pup windows" is about as long as it comfortably gets), so these are+// SHORTER than CAT_LABEL, which stays as-is for the uncapped tooltip. The per-session AUMID already+// encodes the category, so a category flip mints a new appId and the new name takes effect with it.+const CAT_MODE_SHORT = {+  wiki: 'wiki · logged out',+  'wiki-in': 'wiki · LOGGED IN',+  app: 'Adom app',+  web: 'web page',+  mixed: 'mixed content',+};+function pupDisplayName(sessionId) {+  try {+    const cat = sessionId ? pupCategory(sessionId) : null;+    const mode = cat && CAT_MODE_SHORT[cat];+    return mode ? `${PUP_DISPLAY_NAME} · ${mode}` : PUP_DISPLAY_NAME;+  } catch (e) { return PUP_DISPLAY_NAME; }+} let _identitySupported = null;   // null = unprobed let _identityRegistered = false; let _jumplistSupported = null;   // null = unprobed (desktop_set_window_jumplist, AD ≥1.9.139)@@ -2194,7 +2215,7 @@ async function stampPupIdentity(sessionId) {     }     const r = await chrome.adCommand('desktop_set_window_identity', {       titleContains: `(session: ${sessionId}`, cacheKey: `pup-${sessionId}-${cat}`,-      appId, displayName: PUP_DISPLAY_NAME, iconPath: pupIconPath(sessionId),+      appId, displayName: pupDisplayName(sessionId), iconPath: pupIconPath(sessionId),       // v1.9.11 (AD ≥1.9.141): brand the taskbar RIGHT-CLICK MENU HEADER row (it showed the       // chrome.exe icon for months). There is NO "ApplicationIcon" registry value on AUMID keys       // and the registry cannot brand the header at all — the header obeys the window's@@ -2240,7 +2261,7 @@ async function registerPupAumid(appId, sessionId) {   writeAumidIcon(appId, pupIconPath(sessionId));   try {     const r = await chrome.adCommand('desktop_register_app_identity', {-      appId, displayName: PUP_DISPLAY_NAME, iconPath: pupIconPath(sessionId), shortcut: false,+      appId, displayName: pupDisplayName(sessionId), iconPath: pupIconPath(sessionId), shortcut: false,     }, { timeoutMs: 6000 });     const raw = r && (typeof r.output === 'string' ? r.output : JSON.stringify(r.output || ''));     if (_isUnknownVerb(r, raw)) return; // older AD without #207 — the per-window stamp still brands the taskbar button