Pup - the AI's own browser

@@ -1,10 +1,10 @@ {   "manifest_version": 1,   "name": "puppeteer",-  "version": "2.0.13",-  "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.13/adom-bridge-puppeteer-v2.0.13.zip",-  "sha256": "2563c200160be0ffaacb2fdf518aa35add931d68de8a240f8bb692fc8c53bddb",-  "size": 640581,+  "version": "2.0.14",+  "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.14/adom-bridge-puppeteer-v2.0.14.zip",+  "sha256": "59851ffe2ea81b34c16a2957d21f1700c4daefd7f39bcf5bdf2453614a1f1555",+  "size": 641264,   "verbPrefixes": [     "browser_",     "desktop_recorder_",

@@ -1 +1 @@-2.0.13+2.0.14

@@ -2,7 +2,7 @@   "manifest_version": 1,   "name": "puppeteer",   "displayName": "Puppeteer (Chrome for Testing + Native)",-  "version": "2.0.13",+  "version": "2.0.14",   "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.",@@ -19,7 +19,8 @@   "verbPrefixes": [     "pup_",     "desktop_recorder_",-    "desktop_record_"+    "desktop_record_",+    "browser_"   ],   "verbs": [     "pup_open_window",

@@ -10419,6 +10419,26 @@ const server = http.createServer(async (req, res) => {       const command = body.command;       const args = body.args || {};       res._adomCommand = command; // v1.0.16: lets sendJSON inject this verb's _hint/related+      // v2.0.14 (John): GUIDANCE SHIM for the 2026-08 browser_* -> pup_* clean break. The break is+      // deliberate — nothing executes under the old names, no aliases — but the bare ab-side error+      // ("no installed bridge claims this prefix") MISLED broken callers into reinstalling pup+      // instead of renaming their call, and the CLI's --help / `help <old-verb>` paths were dead ends+      // too. So pup re-claims the browser_ prefix SOLELY to answer with the exact fix. The break+      // still happens (callers must migrate), but now it teaches the new verb instead of stranding+      // the AI. nbrowser_* (the extension) is unaffected — it does not start with "browser_".+      // Delete this shim once the fleet has migrated.+      if (typeof command === 'string' && command.startsWith('browser_')) {+        const newVerb = command.replace(/^browser_/, 'pup_');+        console.log(`[rename-shim] refused '${command}' -> told caller to use '${newVerb}' (thread: ${req.headers['x-adom-caller-thread'] || 'unknown'})`);+        sendJSON(res, {+          success: false,+          error: `'${command}' was RENAMED to '${newVerb}' in the 2026-08 browser_* -> pup_* cutover (clean break, no aliases — this call did NOT execute). Re-issue the SAME call as '${newVerb}' with identical args.`,+          errorCode: 'verb_renamed',+          renamedTo: newVerb,+          _hint: `The whole verb family moved one-for-one: browser_<x> is now pup_<x> (e.g. browser_open_window -> pup_open_window, browser_screenshot -> pup_screenshot). Update your caller/skill to the pup_* names permanently — the old names are gone for good. Full catalog: pup_describe. Docs: https://wiki.adom.inc/adom/pup-bridge`,+        }, 410);+        return;+      }       // v1.9.101 (John's ask) — CAPTURE WHO IS ASKING. AD stamps these on every bridge request it       // relays (caller-identity contract, AD >=1.9.180); pup was throwing them away. A pup window       // effectively IS an AI thread, and John runs ~20 at once, so surfacing "which thread owns this