Pup - the AI's own browser

@@ -1,10 +1,10 @@ {   "manifest_version": 1,   "name": "puppeteer",-  "version": "1.9.107",-  "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.107/adom-bridge-puppeteer-v1.9.107.zip",-  "sha256": "52f44879120850d700b4ae7f89df1e0fbd718466cb99477716f8c54d070dde88",-  "size": 377689,+  "version": "1.9.108",+  "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.108/adom-bridge-puppeteer-v1.9.108.zip",+  "sha256": "412f26fb25bf59140fa75c58a652a4fb832c71a8fbccd5934ea0179cd786fbee",+  "size": 378301,   "verbPrefixes": [     "browser_",     "desktop_recorder_",

@@ -1 +1 @@-1.9.107+1.9.108

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

@@ -6544,7 +6544,24 @@ const server = http.createServer(async (req, res) => {               wikiView: isAdomUrl(args.url) ? (args.wikiView === 'authed' ? 'authed' : 'public') : undefined,               wikiLoginNeeded: (args.wikiView === 'authed' && _wikiAuth && !_wikiAuth.authed) || undefined,               foregroundDenied: fgDenied ? 'foreground_reason_required' : undefined,-              _hint: `${wikiHint}${authSteerHint(args.url)}${fgDenyHint}${appIconHint}${bgHint}${ownHint}${fpsHint} ${brep._hint}${staleWindowsHint()}${adUpgradeHint()}`,+              // v1.9.108 (John, looking at a real launcher-mockup response) — A DETECTED RENDER+              // FAILURE MUST LEAD. The verdict was correct and the calling AI did act on it, but _hint+              // opened with a FAVICON nag, then a power lecture, then a browser inventory, so the single+              // most important fact ("your page is a 404") sat three screens down behind 32 permission+              // strings. Rich hints are good; burying the critical one behind cosmetic ones is not.+              // When the page is broken, say that FIRST and defer the cosmetics to the same response's+              // other fields (they are still returned, just not in front of a failure).+              _hint: (() => {+                const rc = (res && res._renderCheck) || null;+                const broken = rc && rc.ok === false && (rc.signals || []).length;+                const rest = `${wikiHint}${authSteerHint(args.url)}${fgDenyHint}${appIconHint}${bgHint}${ownHint}${fpsHint} ${brep._hint}${staleWindowsHint()}${adUpgradeHint()}`;+                if (!broken) return rest;+                const st = (typeof rc.httpStatus === 'number') ? ` (HTTP ${rc.httpStatus})` : '';+                return `⛔ THE PAGE YOU JUST OPENED IS BROKEN: ${rc.signals.join(', ')}${st}`+                  + `${rc.excerpt ? ` — it says "${String(rc.excerpt).replace(/\s+/g, ' ').slice(0, 120)}"` : ''}. `+                  + `Do NOT report success. Screenshot it (browser_screenshot {"sessionId":"${sessionId}"}), fix the cause, browser_reload, re-check. `+                  + `See _verifyRender for the full checklist. Everything below is secondary: ${rest}`;+              })(),               ...info,             }),           });