NB - Native Browser Bridge

@@ -1,6 +1,6 @@ {   "slug": "adom-browser-extension",-  "version": "0.3.11",+  "version": "0.3.12",   "type": "app",   "title": "Adom Native Browser Extension (Chrome + Edge)",   "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,59 @@   },   "visibility": "public",   "brief": "Your AI's hands in your real, signed-in Chrome & Edge: build, drive, and test web apps, and log past vendor walls, in the browser you already use. The nbrowser_* native-browser bridge (pup's counterpart) - runs in your actual logged-in profile, so cookies/SSO/saved-logins/captcha all work.",-  "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.3.12",+  "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": [+    "install.sh",+    "uninstall.sh",+    "package.json",+    "page.json",+    "README.md",+    "docs/INSTALL-FLOW.md",+    "skills/adom-browser-extension/SKILL.md",+    "skills/cross-platform-dev/SKILL.md",+    "skills/driving-the-extension/SKILL.md",+    "skills/native-browser-safety/SKILL.md",+    "skills/installing-the-extension/SKILL.md",+    "skills/uninstalling-the-extension/SKILL.md",+    "skills/native-browser-recording/SKILL.md",+    "skills/driving-the-extension-demo/SKILL.md",+    "skills/driving-the-desktop/SKILL.md",+    "demo/adom-native-browser-demo.mp4",+    "host/native-host.js",+    "bridge/server.js",+    "skills/driving-sites/SKILL.md",+    "skills/driving-gusto/SKILL.md",+    "skills/reading-google-messages/SKILL.md",+    "screenshots/hero-v5.png",+    "PRIVACY.md",+    "privacy.html",+    "screenshots/usecase-oscilloscope.png",+    "screenshots/usecase-chipfetcher.png",+    "screenshots/usecase-symbol.png",+    "screenshots/usecase-eda.png",+    "screenshots/usecase-board.png",+    "screenshots/usecase-chipsmith.png",+    "screenshots/hero.png",+    "docs/UNINSTALL-FLOW.md",+    "screenshots/extensions-adom-card.png",+    "screenshots/install-folder-picker.png",+    "screenshots/uninstall-confirm-bubble.png",+    "screenshots/hero-v7.png"+  ],+  "scripts": {+    "install": "./install.sh",+    "uninstall": "./uninstall.sh"+  },+  "dependencies": {},+  "org": "adom",+  "author": {+    "name": "John Lauer",+    "email": "[email protected]"+  }+}\ No newline at end of file

@@ -138,10 +138,30 @@ desktop_press_key {hwnd:<PK>, keys:"ctrl+l"}                                # fo desktop_type      {hwnd:<PK>, text:"C:\\Users\\<user>\\adom-browser-extension\\extension"}   # agent types the path - fast desktop_press_key {hwnd:<PK>, keys:"enter"}                                 # navigates INTO the folder desktop_screenshot_window {hwnd:<PK>}                                       # VERIFY breadcrumb shows ...\extension BEFORE committing-desktop_ui_click  {hwnd:<PK>, contains:"Select Folder"}                     # commit -> the page toasts "Extension loaded"+desktop_ui_click  {hwnd:<PK>, automationId:"1"}                             # commit (Select Folder = IDOK) -> page toasts "Extension loaded" desktop_caption  {text:""}                                                  # clear the caption immediately ``` +⚠ **Select Folder may need a REAL click, not a UIA invoke (verified live on Edge / Win11, ADOMBASELINE+2026-07-03).** The picker is a Win32 common dialog (`#32770`), and on Edge its **Select Folder / IDOK+did NOT respond to `desktop_ui_click` (UIA Invoke) - the call returned `success:true` but the dialog+stayed open.** A foreground **SendInput** click closed it. So: after verifying the breadcrumb, try the+UIA click; if `desktop_list_windows` still shows the `#32770` open, fall back to+`desktop_find_control {hwnd:<PK>, contains:"Select Folder"}` -> `desktop_bring_to_front {hwnd:<PK>}` ->+`desktop_click {x:<best.rect.centerX>, y:<best.rect.centerY>}` (SendInput). ALWAYS confirm the picker is+gone (`#32770` count == 0) before believing it committed.++⚠ **The subfolder-drill trap.** After `ctrl+l` -> type path -> Enter you are now standing INSIDE the+extension folder (breadcrumb `...\extension`, Folder field = "extension", list shows the extension's own+`icons/`, `src/`, `manifest.json`). Commit from HERE. Do NOT let a subfolder get selected first - if the+Folder field or breadcrumb reads `...\extension\src`, Select Folder loads `src` (no manifest -> silent+no-load, or a manifest error). If you drilled too far, re-run `ctrl+l` + the full path + Enter to reset+to `...\extension`, re-screenshot, THEN commit.++**Edge vs Chrome are identical here** except the URL scheme (`edge://extensions`) and, on a fresh box, the+Developer-mode toggle is a shadow-DOM switch not exposed as settable - front the window and+`desktop_click` its screen coords (just right of the "Developer mode" label) to flip it.+ **Why `bring_to_front` is the whole game:** the picker opens BEHIND the user's active windows (observed `z:1`/`z:2`). SendInput without fronting it first sends the keys to the USER's foreground window (their editor) - they never reach the picker (learned the hard way: a stray paste/Enter into the user's VS