docs(skill): lead extension setup with the published Chrome Web Store build

The extension is now live on the Web Store
(knfcmbamhjmaonkfnjhldjedeobeafmk). Update the skill so agents:
- install from the Store (one-click, restart-stable, auto-updating) as the
  primary path, with Load-unpacked demoted to a dev fallback (it can be disabled
  on Chrome restart, silently dropping the relay).
- when they DO hit the "Allow remote debugging?" dialog (relay not live → raw-port
  fallback), stop retrying and tell the user to install the Store extension once,
  rather than repeatedly popping the consent dialog.

skill-data/core/SKILL.md

@@ -49,17 +49,27 @@ hand-constructed URL often doesn't.
 ### Driving the user's real, already-open Chrome (extension)
 
 When the task needs the user's *live* logged-in window (their real session, the
-window they're looking at — not a fresh browser), use the extension connect flow:
-`agent-browser extension install` once, load `extensions/ab-connect` in
-`chrome://extensions` once (it shows up as **agent-browser-stealth**; a GUI step
-you can perform with a **computer-use / GUI-automation tool** like the
-`cua-driver` skill — see `references/commands.md` → "Drive your real, logged-in
-Chrome"). Once the extension is loaded, plain `agent-browser open <url>`
-auto-connects through it — `auto_connect_cdp` **prefers the live extension relay
-over a raw `--remote-debugging-port`**, so Chrome 136+'s "Allow remote debugging?"
-consent popup never fires. `agent-browser extension connect` is the explicit form
-of the same path. Zero-confirmation, zero-token. Use `--launch` instead when a
-fresh, isolated browser is fine.
+window they're looking at — not a fresh browser), use the extension connect flow.
+One-time setup:
+1. `agent-browser extension install` — registers the native-messaging host.
+2. Install the **agent-browser-stealth** extension. Easiest (and restart-stable):
+   the **Chrome Web Store**, one-click *Add to Chrome*:
+   <https://chromewebstore.google.com/detail/agent-browser-stealth/knfcmbamhjmaonkfnjhldjedeobeafmk>
+   (Dev fallback: `chrome://extensions` → Developer mode → *Load unpacked* →
+   `extensions/ab-connect`. Load-unpacked can be disabled on Chrome restart, so
+   prefer the Store build for unattended setups.)
+
+Once installed, plain `agent-browser open <url>` auto-connects through the
+extension relay — `auto_connect_cdp` **prefers the live relay over a raw
+`--remote-debugging-port`**, so Chrome 136+'s "Allow remote debugging?" consent
+popup never fires. `agent-browser extension connect` is the explicit form of the
+same path. Zero-confirmation, zero-token. Use `--launch` instead when a fresh,
+isolated browser is fine.
+
+**If you DO hit the "Allow remote debugging?" dialog**, the relay wasn't live, so
+`open` fell back to the raw debug port. Don't keep retrying — tell the user to
+install the Store extension above (one click); after that the relay stays up and
+the dialog never returns.
 
 Each `--session` that connects gets its **own colored Chrome tab group** (named
 after the session) and drives only its own tabs — multiple agents share the one

skill-data/core/references/commands.md

@@ -331,15 +331,16 @@ One-time setup:
 agent-browser extension install        # writes the native-messaging host manifest
 ```
 
-The native-messaging host accepts **both** extension origins, so the extension
-can be installed either way:
+The native-messaging host accepts **both** extension origins, so either install
+works — but prefer the Store build:
 
-1. **Load unpacked (works today)** — load `<repo>/extensions/ab-connect` from
-   source; its pinned `key` gives the stable id `ciiljdlhd…`.
-2. **Chrome Web Store (once published)** — one-click *Add to Chrome*; the store
-   strips the `key` and assigns its own id (`knfcmbamhjmaonkfnjhldjedeobeafmk`),
-   which `connect.rs` also allow-lists. (Submitted for review; until it's live,
-   use Load unpacked.)
+1. **Chrome Web Store (recommended)** — one-click *Add to Chrome*:
+   <https://chromewebstore.google.com/detail/agent-browser-stealth/knfcmbamhjmaonkfnjhldjedeobeafmk>
+   Restart-stable and auto-updating (store id `knfcmbamhjmaonkfnjhldjedeobeafmk`).
+2. **Load unpacked (dev)** — load `<repo>/extensions/ab-connect` from source;
+   its pinned `key` gives the stable id `ciiljdlhd…`. NOTE: Load-unpacked
+   extensions can be disabled/dropped on Chrome restart (Developer-mode handling),
+   which silently drops the relay — so for unattended setups use the Store build.
 
 For Load unpacked — a GUI step (Chrome's `chrome://extensions` is privileged; the
 CLI can't load an unpacked extension):