NB - Native Browser Bridge

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

@@ -25,7 +25,12 @@ them - never to drive or navigate it.  ## ⛔ Background by default - NEVER foreground unless the user asks -The user is working in other windows. **Never raise a window to the foreground** for your own needs.+**The user is almost always doing something else on their computer** - reading, typing, on a call,+in another app. So your work MUST **default to the background, especially when you open new browser+windows**: a window that jumps to the front interrupts whatever they were doing and (worse) their next+keystrokes land in the control you just surfaced. Background is not politeness, it is the **default+posture**; foreground is **opt-in, only when the user explicitly asks to watch.**+**Never raise a window to the foreground** for your own needs. The verbs are built for this: `nbrowser_open_window` opens **unfocused**, `open_tab` opens `active:false`, `switch_window` does **not** raise - leave those defaults alone. Capture without foregrounding: **`nbrowser_screenshot` (CDP) and `desktop_screenshot_window` (WGC) both capture a

@@ -28,7 +28,12 @@ The only thing you may do to one of the user's existing windows is `desktop_brin it for them - and only when they explicitly ask to see it.  ## ⛔ Background by default - never foreground unless asked-The user is working in other windows. The verbs are built to stay out of their way:+**The user is almost always doing something else on their computer** - reading, typing, on a call, in+another app. Your work has to **DEFAULT to the background, especially when you open new browser+windows**: a window that jumps in front of them interrupts what they were doing, and their next+keystrokes land in whatever control you just surfaced. Opening in the background is therefore the+**default posture, not a nicety**; foregrounding is **opt-in and happens ONLY when the user explicitly+asks to watch.** The verbs are built to stay out of their way: `nbrowser_open_window` opens **unfocused**, `nbrowser_open_tab` opens `active:false`, `nbrowser_switch_window` does **not** raise. **Leave those defaults alone.** You can fully see and drive a window without foregrounding it: `nbrowser_screenshot` (CDP) and `desktop_screenshot_window`