Pup - the AI's own browser

@@ -1,10 +1,10 @@ {   "manifest_version": 1,   "name": "puppeteer",-  "version": "2.0.160",-  "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.160/adom-bridge-puppeteer-v2.0.160.zip",-  "sha256": "f4b26e4ad682c61a29e8c45fa6b3cdff8f541fb0c5b562f6e739632dbef7527d",-  "size": 907795,+  "version": "2.0.161",+  "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.161/adom-bridge-puppeteer-v2.0.161.zip",+  "sha256": "93e2695653173f79f7fd596cb2ecb1c9098e5d6a296681948b9521a903367c28",+  "size": 908047,   "verbPrefixes": [     "browser_",     "desktop_recorder_",

@@ -1 +1 @@-2.0.160+2.0.161

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

@@ -4173,7 +4173,6 @@ async function stampPupIdentity(sessionId, opts) { // into the id itself (Adom.Pup.<sid>.<cat>), so a Set suffices — a state change is a NEW id. const _registeredPupAumids = new Set(); async function registerPupAumid(appId, sessionId) {-  if (minimalTouch()) return false;   // v1.9.190: minimal-touch — no taskbar work at all   if (_identitySupported === false || appId === PUP_APP_ID || _registeredPupAumids.has(appId)) return;   // v2.0.152 THREAD TILES: a thread AUMID (Adom.Pup.thread.<slug>.<gen>) wears the thread's NAME tile   // instead of the standard/category icon. Render it (once per thread, cached) from a live browser,@@ -4197,7 +4196,15 @@ async function registerPupAumid(appId, sessionId) {   }   // v1.9.44: write IconResource FIRST, before the button can possibly exist. AD's registration does   // not write it (see writeAumidIcon), and an AUMID with no icon is what paints white.+  // v2.0.161 (Thread-Tiles taskbar bug): writeAumidIcon is a ~10ms HKCU reg.exe write — NO button+  // destruction, NO shell/AD roundtrip. It is the NON-RACY "belt" that the per-window Relaunch prop+  // ("braces") only RACES for. So it MUST run even under minimal-touch: with minimal-touch on,+  // registerPupAumid used to bail at the very top, leaving a thread/category AUMID branded ONLY by the+  // racy Relaunch prop — which loses the race against Win11 baking the button art and paints the+  // DEFAULT pup icon (measured: 0 Adom.Pup.thread.* registry keys existed). Write the icon here; only+  // the INVASIVE Start-Menu registration below stays gated under minimal-touch.   writeAumidIcon(appId, iconPath);+  if (minimalTouch()) return;   // registry branded (the belt); skip the AD register_app_identity roundtrip   try {     const r = await chrome.abCommand('desktop_register_app_identity', {       appId, displayName, iconPath, shortcut: false,