← Commit history

Record the native-input hard rule in the SUB-SKILL and BOTH maintainer skills, not just the main SKILL.md (John: 'have you recorded this in skills and dev skills?' — I had only done the main one). pup-vendor-login now opens its real-cursor/FedCM section with the warn-and-wait protocol, since that skill is what teaches the native-click path and is therefore the highest-risk place to omit it. pup-bridge-dev records three more lessons paid for today: autonomous machinery needs direct evidence + two consecutive observations + a hard cap or it becomes the bug (the tab reconciler destroyed live windows; the unstick misfired and clicked the user's screen every 30s); never invent UI Adom already has (the canonical AI cursor is the extension's cursorScript, a byte-faithful copy of HD's AI_CURSOR_JS); and prove taskbar/visual work ON GLASS because the badge API reported success on an invisible badge through three revisions. pup-bridge-test records that a TEST may never fire native OS input without warning, since every scenario runs on the user's real machine while he works, and that a green API result is not a passing test.

John Lauer ·4711dd1ab3 ·3mo ago ·parent e55040e
3 files changed +6−6
adom-bridge-puppeteer-manifest.json+4−4
@@ -1,10 +1,10 @@ {   "manifest_version": 1,   "name": "puppeteer",-  "version": "1.9.199",-  "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.199/adom-bridge-puppeteer-v1.9.199.zip",-  "sha256": "3021bdf03073ae6c5328017ebd098f08c7a5ab3e142383b9af15e1975d56c9e9",-  "size": 432928,+  "version": "1.9.200",+  "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.200/adom-bridge-puppeteer-v1.9.200.zip",+  "sha256": "98fb76e43dfd664ccce6f3bf9d46d257c6dd20b2e1d5a4e776f505ebb55cf02b",+  "size": 432927,   "verbPrefixes": [     "browser_",     "desktop_recorder_",
src/BRIDGE_VERSION+1−1
@@ -1 +1 @@-1.9.199+1.9.200
src/bridge.json+1−1
@@ -2,7 +2,7 @@   "manifest_version": 1,   "name": "puppeteer",   "displayName": "Puppeteer (Chrome for Testing + Native)",-  "version": "1.9.199",+  "version": "1.9.200",   "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.",