rebrand: agent-browser-stealth → chrome-use, de-fork, reset to v1.0.0

Standalone product rename across the whole repo (issue: project identity):

- Binary/package/repo/skill/docs: agent-browser[-stealth] → chrome-use
  (single binary name `chrome-use`; old aliases agent-browser/abs dropped).
- Version: 0.27.0-fork.51 → 1.0.0 (drop the upstream-fork counter).
- Native-messaging host: com.agent_browser.connect → com.leeguoo.chrome_use
  (CLI + ab-connect extension in lockstep — this is a breaking handshake change,
  extension bumped 0.4.2 → 0.5.0, needs a Web Store republish).
- Config dir: ~/.agent-browser → ~/.chrome-use.
- README/zh: reframed from "stealth fork of agent-browser" to a standalone
  product with a small `originally based on vercel-labs/agent-browser` credit.
- Kept AGENT_BROWSER_* env vars working (63 vars across the codebase; renaming
  them would break every existing script/skill for no user-facing gain).

Build green, 802 unit tests pass, fmt + clippy clean. Upstream attribution to
vercel-labs/agent-browser preserved.

extensions/ab-connect/background.js

@@ -1,6 +1,6 @@
-// agent-browser connect — MV3 service worker.
+// chrome-use connect — MV3 service worker.
 //
-// Bridges the user's real Chrome tabs to the local agent-browser daemon over a
+// Bridges the user's real Chrome tabs to the local chrome-use daemon over a
 // Chrome **native messaging** channel (no localhost port, no token: Chrome
 // authenticates this extension to the host by id). It attaches chrome.debugger
 // to eligible tabs and relays CDP both ways via a tiny envelope:
@@ -16,12 +16,12 @@
 // attach + Target handling; the transport is rewritten from WebSocket+token to
 // native messaging.
 
-const HOST_NAME = 'com.agent_browser.connect'
+const HOST_NAME = 'com.leeguoo.chrome_use'
 const SKIP_URL = /^(chrome|chrome-extension|devtools|chrome-untrusted|edge|about):/i
 
 /** @type {chrome.runtime.Port|null} */
 let port = null
-/** Whether the native-messaging host (the local agent-browser CLI) is linked.
+/** Whether the native-messaging host (the local chrome-use CLI) is linked.
  *  Read by the popup status page. */
 let hostConnected = false
 let nextSession = 1