NB - Native Browser Bridge

@@ -1,6 +1,6 @@ {   "slug": "adom-browser-extension",-  "version": "0.4.9",+  "version": "0.4.10",   "type": "app",   "title": "Adom Browser Extension",   "description": "Drive your real, logged-in Chrome/Edge from the Adom ecosystem: the nbrowser_* native-browser bridge (counterpart to pup). Multi-profile driving, a read-only credential-library query over the browser's own saved logins (Chrome + Edge), and hands-free vendor login automation, so chip CAD / datasheets download past every login wall in your real signed-in session.",

@@ -9,11 +9,11 @@     "chrome",     "edge",     "nbrowser",-    "ai-agent",-    "developer-tools",-    "vibe-coding",+    "pup",     "native-messaging",-    "adom-desktop"+    "adom-desktop",+    "credentials",+    "chip-fetcher"   ],   "status": "live",   "discovery_triggers": [@@ -57,5 +57,38 @@   },   "visibility": "public",   "brief": "Your AI's hands in your real, signed-in browser. The Adom Browser Extension (abe) works with both Chrome and Edge: build, drive, and test web apps, and log past vendor walls, in the browser you already use - cookies, SSO, saved logins and captcha trust intact. The nbrowser_* bridge (pup's counterpart) runs in your actual logged-in profile.",-  "discovery_pitch": "The native-browser extension drives the user's REAL signed-in Chrome/Edge via nbrowser_* verbs: use it for LOGGING IN, filling forms, and downloading behind auth with their OWN saved passwords - pup cannot (it is a fresh Chrome-for-Testing with no logins). Next moves: run 'adom-desktop bridge_list' to check it is installed; if not, OFFER to install it (see the installing-the-extension skill) - never make the user do it. If this container lacks the skills, 'adom-wiki pkg install adom/adom-browser-extension'. Check readiness with 'adom-desktop nbrowser_readiness' (state:needs-extension means offer the install)."+  "discovery_pitch": "The native-browser extension drives the user's REAL signed-in Chrome/Edge via nbrowser_* verbs: use it for LOGGING IN, filling forms, and downloading behind auth with their OWN saved passwords - pup cannot (it is a fresh Chrome-for-Testing with no logins). Next moves: run 'adom-desktop bridge_list' to check it is installed; if not, OFFER to install it (see the installing-the-extension skill) - never make the user do it. If this container lacks the skills, 'adom-wiki pkg install adom/adom-browser-extension'. Check readiness with 'adom-desktop nbrowser_readiness' (state:needs-extension means offer the install).",+  "version": "0.4.10",+  "type": "app",+  "description": "Drive your real, logged-in Chrome/Edge from the Adom ecosystem: the nbrowser_* native-browser bridge (counterpart to pup). Multi-profile driving, a read-only credential-library query over the browser's own saved logins (Chrome + Edge), and hands-free vendor login automation, so chip CAD / datasheets download past every login wall in your real signed-in session.",+  "install": {+    "binary_name": "adom-browser-extension"+  },+  "files": [+    "skills/adom-browser-extension/SKILL.md",+    "skills/driving-sites/SKILL.md",+    "skills/driving-the-desktop/SKILL.md",+    "skills/driving-the-extension/SKILL.md",+    "skills/driving-the-extension-demo/SKILL.md",+    "skills/installing-the-extension/SKILL.md",+    "skills/native-browser-recording/SKILL.md",+    "skills/native-browser-safety/SKILL.md",+    "skills/reading-google-messages/SKILL.md",+    "skills/uninstalling-the-extension/SKILL.md",+    "install.sh",+    "uninstall.sh",+    "package.json"+  ],+  "scripts": {+    "install": "./install.sh",+    "uninstall": "./uninstall.sh"+  },+  "dependencies": {+    "adom/adom-desktop": "^1.9.47"+  },+  "org": "adom",+  "author": {+    "name": "John Lauer",+    "email": "[email protected]"+  } }\ No newline at end of file

@@ -389,6 +389,22 @@ natively on the user's machine, and is cached per profile.   `normal`(green) · **`paused`(YELLOW - use for captcha/2FA/login human-gates)** · `error`(red) ·   `indeterminate`(marquee) · `none`. Overlay `badge:"adom"|"none"` (see lifecycle above). +## No extension in the profile? You can still OPEN their real browser (`nbrowser_open_os_window`)+When a task only needs the user's real browser OPENED at a URL in the right profile - above all OAUTH+CONSENT (adom-google, Autodesk APS: the user is already signed in; they just click Approve and your+CLI's token poll picks up the result) - you do NOT need the extension installed:+`nbrowser_open_os_window {sessionId, thread, purpose, profile, url}` (registration required, like every+window). It opens **BACKGROUND by default**: a brief blip, then the window MINIMIZES and its taskbar+button flashes ORANGE - the user clicks it when THEY are ready. `foreground:true` needs+`foregroundReason` + a `notify_user` first, same as everywhere else.+- You CANNOT read, drive, or screenshot that window (no extension there) - poll the outcome+  out-of-band or ask the user.+- Close it when the flow is done: `nbrowser_close_window {sessionId}` (handled bridge-side for these).+- Every response carries the honest limitation + the ABE upsell - relay it to the user at a natural+  moment ("with the extension installed I could have filled this for you"), never mid-auth.+- If the profile HAS the extension, prefer `nbrowser_wake_profile` + `nbrowser_open_window` - full+  control, guards, and cleanup beat a fire-and-forget open every time.+ ## File uploads (`nbrowser_set_file_input`) - never the OS picker Upload into an `<input type=file>` over CDP - background, silent, no OS file dialog (which cannot be driven with the debugger attached and would foreground). Three shapes: