feat(extension): add popup status page (paired/not-paired) for Web Store review

The biggest Web Store rejection risk for a CLI-bridge extension is "non-functional
without external software." Give ab-connect a visible standalone UI: a branded
popup that shows whether the native-messaging link to the local agent-browser CLI
is live (Connected + attached tab count, or Not paired with the install hint),
plus a one-line privacy statement (no tracking, no remote server) and a repo link.

- manifest: action.default_popup = popup.html; bump 0.4.0 -> 0.4.1
- background.js: track hostConnected; respond to {type:'ab-status'} from the popup
  and nudge a reconnect on open
- popup.html/popup.js: dark/cyan branded status page (MV3-CSP-safe: external JS,
  no inline handlers), with a safety timeout so it never hangs on "Checking…"
- repacked ab-connect.zip/.crx

extensions/ab-connect/background.js

@@ -21,6 +21,9 @@ const SKIP_URL = /^(chrome|chrome-extension|devtools|chrome-untrusted|edge|about
 
 /** @type {chrome.runtime.Port|null} */
 let port = null
+/** Whether the native-messaging host (the local agent-browser CLI) is linked.
+ *  Read by the popup status page. */
+let hostConnected = false
 let nextSession = 1
 /** tabId -> { sessionId, targetId } */
 const tabs = new Map()
@@ -92,13 +95,16 @@ function connectHost() {
   if (port) return
   try {
     port = chrome.runtime.connectNative(HOST_NAME)
+    hostConnected = true
   } catch (e) {
     port = null
+    hostConnected = false
     return
   }
   port.onMessage.addListener((msg) => void whenReady(() => onHostMessage(msg)))
   port.onDisconnect.addListener(() => {
     port = null
+    hostConnected = false
     // Sessions are stale once the host is gone; the daemon re-discovers on
     // reconnect. Keep chrome.debugger attached so reconnect is cheap.
     for (const tabId of tabs.keys()) setBadge(tabId, 'connecting')
@@ -343,7 +349,18 @@ chrome.tabs.onRemoved.addListener((tabId) => void whenReady(() => detachTab(tabI
 
 chrome.runtime.onInstalled.addListener(() => void whenReady(connectHost))
 chrome.runtime.onStartup.addListener(() => void whenReady(connectHost))
-chrome.action.onClicked.addListener(() => void whenReady(connectHost))
+
+// Popup status page asks for the live pairing state. Attempt a (re)connect on
+// demand so opening the popup also nudges the link awake, then report.
+chrome.runtime.onMessage.addListener((msg, _sender, sendResponse) => {
+  if (msg && msg.type === 'ab-status') {
+    if (!port) {
+      try { connectHost() } catch (e) {}
+    }
+    sendResponse({ connected: hostConnected, tabCount: tabs.size, host: HOST_NAME })
+  }
+  return true
+})
 
 // MV3 service workers get suspended; an alarm wakes us to keep the host link
 // and badges fresh.