browser-pilot-cli - npm Package Compare versions

Comparing version 0.3.0-rc.3 to 0.3.0-rc.4

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

+# 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.

docs/plans/v0.3.0-stabilization.md

 # 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`
 
@@ -34,6 +34,8 @@ ## Goal
   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.
@@ -40,0 +42,0 @@ - [ ] Tag `v0.3.0`, publish npm `latest`, and verify upgrade/rollback metadata.

package.json

 {
   "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",
@@ -50,2 +50,3 @@ "repository": "https://github.com/relixiaobo/browser-pilot",
     "docs/releases/v0.3.0-rc.3.md",
+    "docs/releases/v0.3.0-rc.4.md",
     "README.md",
@@ -52,0 +53,0 @@ "LICENSE"

README.md

@@ -185,3 +185,3 @@ # browser-pilot
 ```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
@@ -188,0 +188,0 @@ ```

New alerts

URL strings

Supply chain risk

Package contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.

Fixed alerts

URL strings

Supply chain risk

Package contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.

Improved metrics

Total package byte prevSize

1042561

0.2%

Number of package files

18

5.88%

Lines of code

20522

0.04%

No dependency changes