Pup - the AI's own browser

@@ -1,10 +1,10 @@ {   "manifest_version": 1,   "name": "puppeteer",-  "version": "2.0.361",-  "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.361/adom-bridge-puppeteer-v2.0.361.zip",-  "sha256": "07a7a3dea86e56d8c39641fa0d6bee4679a8130e46d0f50b50a44e02f7d64dea",-  "size": 1529977,+  "version": "2.0.362",+  "url": "https://wiki.adom.inc/download/adom/pup-bridge/2.0.362/adom-bridge-puppeteer-v2.0.362.zip",+  "sha256": "2bd200f10443a80361a1d198dc8de3c59fccfb49d6482131a78dd529886c6d8f",+  "size": 1530388,   "verbPrefixes": [     "browser_",     "desktop_recorder_",@@ -12,5 +12,5 @@   ],   "healthEndpoint": "/status",   "statusVerb": "browser_readiness",-  "released_at": "2026-08-28T10:15:49.271153Z"+  "released_at": "2026-08-28T10:20:53.834333Z" }

@@ -1,6 +1,6 @@ {   "slug": "pup-bridge",-  "version": "2.0.361",+  "version": "2.0.362",   "type": "app",   "description": "The pup SKILL PACK \u2014 the AI skills that teach a cloud/container AI how to drive the Adom Desktop Puppeteer (pup) bridge (browser_* verbs): the everyday `pup` skill plus focused sub-skills for windows/sessions/tabs, screenshots+recording, browsers+Chrome install, and driving the Adom wiki. Installs into ~/.claude/skills + ~/.codex/skills. DOCS ONLY \u2014 this is NOT the bridge runtime. The bridge itself (the Node program that drives the browser) runs on the DESKTOP: Adom Desktop bundles it and auto-installs/updates it, and it's published separately on the Releases tab as adom-bridge-puppeteer-v<ver>.zip. The pkg version is kept in lockstep with the Release version so the page's max version row always carries BOTH a pkg tarball (skills) and a runtime zip (bridge) \u2014 a skills-only or runtime-only bump on the top row breaks constraint installs. TL;DR: pkg install = the skills for your AI; the bridge = the Release zip, which Adom Desktop manages for you.",   "keywords": [

@@ -1 +1 @@-2.0.361\ No newline at end of file+2.0.362\ No newline at end of file

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

@@ -12042,7 +12042,20 @@ function bugReportInvite(isError) {     : 'pup is actively developed and bug reports are genuinely wanted.';   return `${lead} If a pup verb misbehaves (wrong result, a hang, a window that never appears, a hint that turned out to be false, a process left running), file it on pup's own wiki repo so the maintainers see it: \`adom-wiki issue list ${PUP_ISSUES_REF}\` to check for a duplicate first, then \`adom-wiki issue create ${PUP_ISSUES_REF} --title "<one-line symptom>" --category bug-report --body "<what you ran, what you expected, what happened, the VERBATIM response JSON, and the bridge version from bridge_list>"\`. Include the machine's OS and whether it is Windows or macOS. Reports from real machines are the only way this bridge gets correct — the maintainers cannot reproduce every environment, browser install, or concurrency pattern locally. (A Bridge-core problem — the relay, bridge lifecycle, caller identity — belongs on adom/adom-bridge instead.)`; }-function maybeAttachBugInvite(obj, verb) {+// Resolve the session a response is ABOUT, from the caller's own addressing. pup's documented forms+// are zero-id (resolve by ai-thread), {window:"..."} and the legacy {sessionId:"..."}, so all three+// have to be honoured or a notice fires only for whichever form the author happened to test.+function sessionForResponse(obj, argsIn) {+  try {+    const a = argsIn || {};+    const sid = (obj && (obj.sessionId || obj.window)) || a.sessionId || a.window;+    if (sid && sessions.get(sid)) return sessions.get(sid);+    const thread = a['ai-thread'] || a.aiThread;+    if (thread) { for (const [, s2] of sessions) if (s2 && (s2.owner === thread || s2._ownerThread === thread)) return s2; }+    return null;+  } catch (e) { return null; }+}+function maybeAttachBugInvite(obj, verb, argsIn) {   try {     if (!obj || typeof obj !== 'object' || Array.isArray(obj)) return;     if (obj._reportIssues) return;                                   // handler already set one@@ -12085,8 +12098,7 @@ function maybeAttachBugInvite(obj, verb) {     // rather than only on the status verb nobody calls.     try {       if (!isProbe && obj._viewportOverride === undefined && VIEWPORT_SENSITIVE.has(verb)) {-        const _sid2 = obj.sessionId || obj.window || (typeof args !== 'undefined' && args && (args.sessionId || args.window));-        const _s2 = _sid2 && sessions.get(_sid2);+        const _s2 = sessionForResponse(obj, argsIn);         const _ev = _s2 && _s2._emulatedViewport;         if (_ev && _ev.width) {           obj._viewportOverride = `This window has an EMULATED VIEWPORT of ${_ev.width}x${_ev.height}`@@ -12098,8 +12110,7 @@ function maybeAttachBugInvite(obj, verb) {     // #80: the TARGETED notice, delivered to the session it actually happened to.     try {       if (!isProbe && obj._sessionNotice === undefined) {-        const _sid = obj.sessionId || obj.window || (typeof args !== 'undefined' && args && (args.sessionId || args.window));-        const _s = _sid && sessions.get(_sid);+        const _s = sessionForResponse(obj, argsIn);         const _n = _s && drainSessionNotice(_s);         if (_n) obj._sessionNotice = _n;       }@@ -12123,7 +12134,7 @@ function sendJSON(res, obj, status = 200) {     // verb and the handler didn't already set its own _hint, attach the verb's     // canonical hint (+ related) from VERB_META. So EVERY pup_* call carries     // actionable guidance inline, matching the contract AD asks all bridges for.-    maybeAttachBugInvite(obj, res && res._adomCommand);+    maybeAttachBugInvite(obj, res && res._adomCommand, res && res._adomArgs);     if (obj && typeof obj === 'object' && !Array.isArray(obj)) {       const meta = res && res._adomCommand && VERB_META[res._adomCommand];       if (meta) {@@ -14354,6 +14365,12 @@ 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.362: stash the ARGS too. sendJSON's decorator only ever received (obj, verb), so any+      // notice that needs to know WHICH SESSION a call was about had no way to find out: the+      // response body of a verb like pup_screenshot carries no sessionId, and `args` was not in+      // scope. Two notices shipped against that blind spot and neither could ever fire (the #80+      // restart notice and the #79-adjacent viewport warning). This is the missing wire.+      res._adomArgs = args;       // 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