NB - Native Browser Bridge

@@ -1,6 +1,6 @@ {   "slug": "adom-browser-extension",-  "version": "0.4.6",+  "version": "0.4.7",   "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,38 @@   },   "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.4.7",+  "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,25 @@ 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). +## OS-level window inventory (`nbrowser_os_windows`) + extension-state diagnosis+`nbrowser_os_windows {}` returns every Chrome/Edge/pup window as the LAPTOP sees it (hwnd, title, rect,+z), annotated with `abeSession` (the live ABE session that owns it - NEVER force-close those) and+`kind` (`pup/chrome-for-testing` = browser_open/pup litter). It is measured bridge-side, so it works+when your own `desktop_list_windows` returns 0/null - usually AD mid-self-update-restart, or a wrong+`--target` when several ADs are connected. `ok:false` means "AD link down, data UNKNOWN", never "no+windows". Use it to find litter for the `nbrowser_force_close {hwnd}` gate, and to disambiguate+"separate windows vs tabs" without asking the user.++**No more not-connected mysteries (v0.1.26+):** when a verb is refused `extension not connected` for a+profile that exists locally, the refusal carries a DIAGNOSIS from the browser's own records: the Adom+extension is *not installed* in that profile (fix: installing-the-extension, Load unpacked into THAT+profile) vs *installed but disabled* (fix: enable the toggle) vs *enabled but not dialing* (fix: retry+`nbrowser_wake_profile`; if it never connects, `nbrowser_add_extension_origin {id}` for that browser's+extension id). `nbrowser_wake_profile`'s `woke:false` includes the same `extensionState`, and+`nbrowser_profiles` asleep rows carry `extensionInstalled` / `extensionEnabled` / `fix` - read them+BEFORE trying to wake, and never report "the profile doesn't exist" or "can't be fixed" when these+fields tell you exactly what to do.+ ## Activity log - "who drove what, when" (`nbrowser_activity`) The bridge keeps a bounded in-memory trail (max 600 entries / ~1h TTL; resets on bridge restart) of every forwarded verb: `{agoMs, verb, sessionId, thread, profile, ok, errorCode}` plus an `activeSessions`