browser-pilot-cli 0.3.0-rc.3 → 0.3.0-rc.4

package/README.md

@@ -182,7 +182,7 @@ A project can pin Browser Pilot locally and run the same CLI without a global
 installation:
 
 ```bash
-npm install --save-exact browser-pilot-cli@0.3.0-rc.3
+npm install --save-exact browser-pilot-cli@0.3.0-rc.4
 npx --no-install browser-pilot tabs
 ```
 

package/dist/cli.js

@@ -6,7 +6,7 @@ import { writeFileSync as writeFileSync2, readFileSync as readFileSync4, existsS
 import { resolve as resolvePath } from "path";
 
 // src/version.ts
-var BROWSER_PILOT_VERSION = "0.3.0-rc.3";
+var BROWSER_PILOT_VERSION = "0.3.0-rc.4";
 
 // src/protocol/errors.ts
 var ERROR_CODES = [
@@ -3283,6 +3283,13 @@ var CompatibilityBrokerClient = class _CompatibilityBrokerClient {
     }
     await this.callTool("browser.connect", { browserId: selected.id });
   }
+  async listBrowsers(browser) {
+    const result = await this.callTool("browser.discover", browser ? { browser } : {});
+    if (!Array.isArray(result.browsers)) {
+      throw new BrowserPilotError("internal_error", "browser.discover returned invalid browsers");
+    }
+    return result.browsers;
+  }
   async listTabs(scope = "all") {
     const result = await this.callTool("browser.tabs.list", { scope });
     if (!Array.isArray(result.targets)) {
@@ -3709,7 +3716,8 @@ function readStdin() {
 }
 program.command("browsers").description("List supported local browsers and their setup state").option("-b, --browser <name>", "filter by browser ID, product, or channel").action(action(async (opts) => {
   const filter = typeof opts.browser === "string" ? opts.browser.toLowerCase() : void 0;
-  const browsers = (await discoverBrowserCandidates()).map((discovered) => discovered.candidate).filter((candidate) => !filter || [candidate.id, candidate.product, candidate.channel].some((value) => value?.toLowerCase().includes(filter)));
+  const client = await resumeCompatibility(BROWSER_PILOT_VERSION);
+  const browsers = client ? await client.listBrowsers(filter) : (await discoverBrowserCandidates()).map((discovered) => discovered.candidate).filter((candidate) => !filter || [candidate.id, candidate.product, candidate.channel].some((value) => value?.toLowerCase().includes(filter)));
   if (useJson()) {
     console.log(JSON.stringify({ ok: true, browsers }));
     return;

package/dist/daemon.js

@@ -13979,7 +13979,7 @@ var ManagedTargetJanitorClient = class {
 };
 
 // src/version.ts
-var BROWSER_PILOT_VERSION = "0.3.0-rc.3";
+var BROWSER_PILOT_VERSION = "0.3.0-rc.4";
 
 // src/daemon.ts
 var CLI_EXECUTABLE_PATH = publicExecutablePath(import.meta.url);

package/docs/plans/v0.3.0-stabilization.md

@@ -1,7 +1,7 @@
 # Browser Pilot v0.3.0 Stabilization Plan
 
 Status: **In progress**
-Candidate baseline: `v0.3.0-rc.2`; correction target: `v0.3.0-rc.3`, protocol `1.2`
+Candidate baseline: `v0.3.0-rc.3`; correction target: `v0.3.0-rc.4`, protocol `1.2`
 
 ## Goal
 
@@ -31,10 +31,12 @@ products depend on. No Agent-specific behavior enters Browser Pilot.
   files survive Artifact and Workspace cleanup.
 - [x] Pass TypeScript, 276 Node, 109 Playwright, 13 stdio conformance, three
   distribution-mode, and 13 host integration checks on the candidate source.
-- [ ] Publish the corrected release candidate and rerun the host integration
-  gate against that installed package.
-- [ ] Run one controlled user-Chrome host acceptance with explicit Profile
+- [x] Publish `v0.3.0-rc.3` through trusted publishing and pass all 13 host
+  integration checks against the installed standalone release executable.
+- [x] Run one controlled user-Chrome host acceptance with explicit Profile
   choices and a single authorization attempt.
+- [ ] Publish `v0.3.0-rc.4` with Broker-backed CLI browser status and verify
+  that passive discovery reports the live authorized connection.
 - [ ] Soak several real Agent tasks through the installed candidate.
 - [ ] Tag `v0.3.0`, publish npm `latest`, and verify upgrade/rollback metadata.
 

package/docs/releases/v0.3.0-rc.4.md

@@ -0,0 +1,28 @@
+# Browser Pilot 0.3.0-rc.4
+
+This release candidate fixes a connection-status inconsistency found during
+controlled user-Chrome acceptance of RC.3.
+
+When a Broker already held an authorized Chrome connection, `bp profiles` and
+browser operations worked, but `bp browsers` performed a separate local endpoint
+scan and could report the same browser as `disconnected`. An Agent following
+that result could unnecessarily call `bp connect` and cause another Chrome
+authorization prompt.
+
+RC.4 makes `bp browsers` use the Broker-owned `browser.discover` operation when
+a compatible Broker is running. Local discovery remains the passive fallback
+when no Broker exists. The command still never starts a Broker or requests
+Chrome authorization.
+
+The RC.3 controlled user-Chrome acceptance passed with two independent Agent
+hosts routed to two live Profiles. It verified user-tab handoff, concurrent CLI
+use, native screenshot content, PDF and download export, event replay, managed
+cleanup, and preservation of all existing user tabs. Chrome's original
+download was also confirmed in its default download directory.
+
+RC.4 keeps protocol 1.2, browser control behavior, Profile routing, and the
+Agent-neutral stdio integration contract unchanged.
+
+Automated candidate gates passed with 276 Node tests, 109 isolated Playwright
+tests, all 13 stdio conformance checks, all 13 host integration checks, and npm
+distribution verification in global, local-project, and product-bundled modes.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "browser-pilot-cli",
-  "version": "0.3.0-rc.3",
+  "version": "0.3.0-rc.4",
   "description": "CLI tool to control your browser via Chrome DevTools Protocol",
   "repository": "https://github.com/relixiaobo/browser-pilot",
   "type": "module",
@@ -47,6 +47,7 @@
     "docs/releases/v0.3.0-rc.1.md",
     "docs/releases/v0.3.0-rc.2.md",
     "docs/releases/v0.3.0-rc.3.md",
+    "docs/releases/v0.3.0-rc.4.md",
     "README.md",
     "LICENSE"
   ],