NB - Native Browser Bridge

@@ -9,6 +9,40 @@ assistant can **build, drive, and test web software right alongside you**. Cloud containers, Hydrogen Desktop, and the AD CLI reach it through the exact same `relay → adom-desktop → bridge` path they already use for pup. +## Two layers of control++The system controls your native browser at two layers. You get value at layer 1 with nothing+installed in the browser; installing the extension unlocks layer 2.++**Layer 1: OS-level control, no extension required.** The bridge runs on your machine and knows your+browsers the way Windows does. Without the extension installed in any profile, your AI can already:++- **Map every identity**: every Chrome and Edge profile on the machine, with the email, the display+  label you see on the profile button ("John Personal", "adom.inc"), and whether the extension is+  installed there (`nbrowser_profiles`).+- **Open your real browser at a URL, in the right profile, in the background**+  (`nbrowser_open_os_window`): the window opens minimized with an orange flashing taskbar button, and+  you click it when you are ready. Your focus is never stolen. This is the OAuth workhorse: for flows+  like adom-google or Autodesk sign-in you are already authenticated in your own browser, so the AI+  opens the consent page in the correct profile and you just click Approve.+- **Wake a sleeping profile with no window at all** (`nbrowser_wake_profile`), **inventory every+  browser window with ownership attribution** (`nbrowser_os_windows`), and **clean up windows through+  a deliberately hard two-step attestation gate** (`nbrowser_force_close`).++At this layer the AI can open and manage windows but cannot see inside them: no reading, no clicking,+no screenshots. The user does the in-page work.++**Layer 2: deep control, extension installed.** With the extension in a profile, that profile becomes+fully drivable: navigate, read, click by visible text, type, upload files with no OS picker, run+JavaScript, screenshot and record in the background, wait on selectors and downloads, use saved+logins and TOTP behind strict gates. Layer 2 is also where the trust surface lives: every window is+registered with a purpose, the taskbar shows your profile picture with the Adom mark while the AI is+driving (and returns to native when it stops), spawned windows are tracked and reaped, and windows+you opened yourself are off limits, enforced in code.++Every layer-1 response tells the AI honestly what it could not do and what layer 2 would add, so the+upgrade suggestion arrives at natural moments rather than as a wall.+ ## Who we are, and why this extension needs broad browser capabilities  **Adom Industries is an AI electronics-prototyping company** - a full, AI-native development environment for

@@ -1,6 +1,6 @@ {   "slug": "adom-browser-extension",-  "version": "0.4.10",+  "version": "0.4.11",   "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.11",+  "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

@@ -394,8 +394,9 @@ When a task only needs the user's real browser OPENED at a URL in the right prof 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+window). It opens **BACKGROUND by default**: the window is minimized the instant it exists (a laptop-side+watcher at 30ms resolution, v0.1.35+ - no visible flash of the window) 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.