NB - Native Browser Bridge

@@ -1,11 +1,15 @@ #!/usr/bin/env bash # Adom Native Browser — installs the bundled skills so the AI knows the nbrowser_* surface. # (The extension itself loads into Chrome/Edge via "Load unpacked" from extension/, or the Web Store.)+# Installs to BOTH agent skill homes: ~/.claude/skills AND ~/.codex/skills (a container may run+# Claude OR Codex — Bridge SDK Artifact 2). Only the USER skills ship; dev-skills/ stay source-only. set -e-DEST="${HOME}/.claude/skills"-for name in adom-browser-extension cross-platform-dev driving-the-extension native-browser-safety installing-the-extension uninstalling-the-extension native-browser-recording driving-the-extension-demo driving-the-desktop driving-sites driving-gusto reading-google-messages; do-  mkdir -p "$DEST/$name"-  cp "skills/$name/SKILL.md" "$DEST/$name/SKILL.md"-  echo "installed skill: $name"+SKILLS="adom-browser-extension cross-platform-dev driving-the-extension native-browser-safety installing-the-extension uninstalling-the-extension native-browser-recording driving-the-extension-demo driving-the-desktop driving-sites driving-gusto reading-google-messages"+for HOME_DIR in "${HOME}/.claude/skills" "${HOME}/.codex/skills"; do+  for name in $SKILLS; do+    mkdir -p "$HOME_DIR/$name"+    cp "skills/$name/SKILL.md" "$HOME_DIR/$name/SKILL.md"+  done+  echo "installed ${SKILLS// /, } -> $HOME_DIR" done-echo "Skills installed. Load the extension: chrome://extensions -> Developer mode -> Load unpacked -> the extension/ folder."+echo "Skills installed to Claude + Codex homes. Load the extension: chrome://extensions -> Developer mode -> Load unpacked -> the extension/ folder."

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

@@ -24,13 +24,25 @@ If the user says "log into X for me", "sign in", "use my saved password", "fill site I'm logged into", "grab that file behind the login", or "drive my real Chrome" - that is this bridge. pup cannot do it (fresh profile, no logins). +## FIRST-TIME / COLD-START - read before you panic++A fresh machine may not have the bridge or the extension yet, and the AI's default failure mode is to+declare defeat. Don't. These states are EXPECTED, and each has a move - branch on the state, not on+prose:++| You see | What it means | What you do |+|---|---|---|+| `nbrowser_readiness` errors / unknown verb | the AD bridge isn't installed in adom-desktop yet | `bridge_install {manifestUrl}` (see "three install surfaces") |+| `state:"needs-extension"` | bridge up, but the MV3 extension isn't in Chrome yet | **OFFER to install it** -> `installing-the-extension` (never make the user do it) |+| `state:"ready"` | extension connected, profile(s) listed | go drive it -> `driving-the-extension` |+ ## Step 0 - is it even installed yet? Check readiness FIRST  The extension is a **Level-2, proactively-offered** install: it is often NOT present until someone asks for it. Before you try to drive anything, probe (READ-ONLY, never triggers an install):  ```-adom-desktop nbrowser_readiness+adom-desktop nbrowser_readiness      # THIS bridge: {ready,state,extensionConnected,profiles} ```  - `state:"ready"` (extensionConnected:true, one or more profiles) -> go drive it (**driving-the-extension**).@@ -38,8 +50,10 @@ adom-desktop nbrowser_readiness   your cue to **OFFER to install it** (next section) - do NOT silently give up, and do NOT make the   user do it by hand. -If `nbrowser_readiness` itself errors (verb unknown / bridge missing), the AD bridge isn't installed-in this adom-desktop yet - see "The three install surfaces" below.+**For a broad "what tools do I have / is it ready?" question, call the AD-level aggregate+`adom-desktop bridge_readiness` instead** - it is side-effect-free (never spawns a bridge or installs)+and reports every bridge's `state` at once. Use `nbrowser_readiness` when you specifically care about+THIS bridge; use `bridge_readiness` for the survey. Neither ever triggers work.  ## The install-offer hook - suggest it exactly when the user needs a login 

@@ -1,5 +1,8 @@ #!/usr/bin/env bash-DEST="${HOME}/.claude/skills"-for name in adom-browser-extension cross-platform-dev driving-the-extension native-browser-safety installing-the-extension uninstalling-the-extension native-browser-recording driving-the-extension-demo driving-the-desktop driving-sites driving-gusto reading-google-messages; do-  rm -rf "$DEST/$name" && echo "removed skill: $name"+# Removes the bundled skills from BOTH agent skill homes (Claude + Codex).+SKILLS="adom-browser-extension cross-platform-dev driving-the-extension native-browser-safety installing-the-extension uninstalling-the-extension native-browser-recording driving-the-extension-demo driving-the-desktop driving-sites driving-gusto reading-google-messages"+for HOME_DIR in "${HOME}/.claude/skills" "${HOME}/.codex/skills"; do+  for name in $SKILLS; do+    rm -rf "$HOME_DIR/$name" && echo "removed $name from $HOME_DIR"+  done done