chore(release): 0.27.0-fork.31 — Web Store submission ready + two install paths

- extension: popup status page (paired/not-paired) so the listing has standalone
  UI; renamed agent-browser-stealth + new icon (earlier in this line)
- store: upload zip strips manifest "key" (the Web Store forbids it); the unpacked
  dir + .crx keep it. Submitted for review (item knfcmbamhjmaonkfnjhldjedeobeafmk).
- connect: native-messaging allowed_origins lists BOTH the local Load-unpacked id
  (ciiljdlhd…) and the store-assigned id (knfc…), so either install path pairs.
- ci: launch-based jobs opt into AGENT_BROWSER_ALLOW_HEADLESS for display-less
  runners (fixes Native E2E); + version-sync/dashboard/fmt/clippy/flaky-test repairs.
- docs: skill documents both install methods (Load unpacked now, Web Store later).

skill-data/core/references/commands.md

@@ -330,8 +330,19 @@ One-time setup:
 ```bash
 agent-browser extension install        # writes the native-messaging host manifest
 ```
-Then load the extension **once** — this is a GUI step (Chrome's `chrome://extensions`
-is privileged; the CLI can't load an unpacked extension):
+
+The native-messaging host accepts **both** extension origins, so the extension
+can be installed either way:
+
+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.)
+
+For Load unpacked — a GUI step (Chrome's `chrome://extensions` is privileged; the
+CLI can't load an unpacked extension):
 
 > chrome://extensions → enable **Developer mode** (top-right) → **Load unpacked** →
 > select `<repo>/extensions/ab-connect` (it appears in the list as