browser-pilot-cli 0.3.0-rc.6 → 0.3.0

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.6
+npm install --save-exact browser-pilot-cli@0.3.0
 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.6";
+var BROWSER_PILOT_VERSION = "0.3.0";
 
 // src/protocol/errors.ts
 var ERROR_CODES = [

package/dist/daemon.js

@@ -14015,7 +14015,7 @@ var ManagedTargetJanitorClient = class {
 };
 
 // src/version.ts
-var BROWSER_PILOT_VERSION = "0.3.0-rc.6";
+var BROWSER_PILOT_VERSION = "0.3.0";
 
 // 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.5`; correction target: `v0.3.0-rc.6`, protocol `1.2`
+Candidate baseline: `v0.3.0-rc.6`; release target: `v0.3.0`, protocol `1.2`
 
 ## Goal
 
@@ -29,7 +29,7 @@ products depend on. No Agent-specific behavior enters Browser Pilot.
   downloads, controlled Page-event ownership, browser-level completion paths,
   and copy-only Artifacts. Verify unowned downloads are ignored and user source
   files survive Artifact and Workspace cleanup.
-- [x] Pass TypeScript, 276 Node, 109 Playwright, 13 stdio conformance, three
+- [x] Pass TypeScript, 277 Node, 109 Playwright, 13 stdio conformance, three
   distribution-mode, and 13 host integration checks on the candidate source.
 - [x] Publish `v0.3.0-rc.3` through trusted publishing and pass all 13 host
   integration checks against the installed standalone release executable.
@@ -40,9 +40,14 @@ products depend on. No Agent-specific behavior enters Browser Pilot.
 - [x] Publish `v0.3.0-rc.5` and verify text-targeted scrolling plus annotated
   capture on GitHub. Managed cleanup preserved all user tabs but exposed a
   transient closing-target inventory race.
-- [ ] Publish `v0.3.0-rc.6` with generation-scoped managed-target tombstones and
-  rerun managed cleanup against the installed standalone release.
-- [ ] Soak several real Agent tasks through the installed candidate.
+- [x] Publish `v0.3.0-rc.6` with generation-scoped managed-target tombstones.
+  The installed standalone returned `closed: 1, remaining: 6` immediately after
+  managed cleanup and left all six user tabs available, with no managed, busy,
+  controlled, or automatically active target.
+- [x] Soak real Agent tasks through the installed candidates across multiple
+  Chrome Profiles: public GitHub reading, search, precise scrolling, screenshot
+  annotation, PDF export, a disposable form with verified input and submission,
+  and managed-only cleanup. User tabs and exported files were preserved.
 - [ ] Tag `v0.3.0`, publish npm `latest`, and verify upgrade/rollback metadata.
 
 ## Stable decision
@@ -54,3 +59,9 @@ an uncontrolled user tab. `v0.3.0-rc.2` must not be promoted. RC.3 preserves
 Chrome's default download destination and creates an Artifact only after a
 session-scoped Page event proves ownership and a browser-level completion event
 provides the final path.
+
+RC.4 through RC.6 then closed the remaining real-browser gaps in passive
+connection status, text-targeted scroll verification, restrictive-CSP screenshot
+annotation, and asynchronous managed-target closure. The published RC.6
+standalone now satisfies every pre-stable source, distribution, Host, and live
+Chrome gate above. Stable publication remains a separate explicit release step.

package/docs/releases/v0.3.0.md

@@ -0,0 +1,68 @@
+# Browser Pilot 0.3.0
+
+Browser Pilot 0.3.0 promotes the tested protocol 1.2 release candidate without
+runtime changes. It provides Agent-neutral control of the user's real Chromium
+browser through a CLI and a versioned stdio bridge, without a browser
+extension.
+
+## Universal Agent integration
+
+- Agents with shell access can install or bundle the official executable and
+  use the one-shot `bp` commands.
+- Long-lived Agent products can launch `browser-pilot bridge --stdio` and use
+  the same canonical browser tools, lifecycle, events, and Artifacts.
+- One per-user Broker coordinates concurrent CLI and embedded clients through
+  isolated Connections, Workspaces, Leases, opaque target IDs, serialized
+  per-target commands, idempotency keys, deadlines, and event cursors.
+- Browser Pilot contains no Tenon-, OpenClaw-, Codex-, or model-specific
+  behavior. Hosts adapt the public protocol rather than importing private
+  source modules.
+
+## Real browser control
+
+- Eligible tabs opened by the user are visible and explicitly controllable;
+  independently created managed tabs remain separately owned and
+  managed-only cleanup never closes or acquires a user tab.
+- One authorized Chrome endpoint can expose several live Profiles. Agents can
+  inspect Profile context and route new managed work explicitly without
+  changing access to existing tabs.
+- Observations fuse accessibility semantics with DOM state and geometry into
+  bounded, page-scoped numbered refs. Navigation, frame, document, target, and
+  Lease changes invalidate stale refs deterministically.
+- Dedicated tools cover navigation, reading, targeted search, DOM queries,
+  click, verified native input, keyboard operations, scrolling, dropdowns,
+  frames, dialogs, uploads, cookies, HTTP authentication, and bounded network
+  observation or interception.
+- Screenshots and PDFs are returned as protected Artifacts through stdio and
+  can be exported to explicit local paths through the CLI. Annotated
+  screenshots render in an isolated world and work on restrictive-CSP sites.
+- Completed controlled downloads are copied into protected Artifacts while the
+  user's original Chrome download remains in place.
+
+## Reliability and isolation
+
+- Passive browser discovery never requests authorization. Concurrent explicit
+  connects share one in-flight connection attempt instead of multiplying
+  Chrome prompts.
+- User-tab control is exclusive between unrelated Agent Leases and transfers
+  only through explicit release or cleanup.
+- Browser restart advances the connection generation and invalidates old
+  Profile, target, session, frame, and Observation identities.
+- Managed target identity remains generation-scoped while Chrome finishes an
+  asynchronous close, preventing a closing managed tab from briefly appearing
+  as a user tab.
+- Action results include browser evidence and typed mismatch or unknown-outcome
+  states so an Agent can inspect before retrying a possibly mutating command.
+
+## Validation
+
+The published RC.6 standalone passed real multi-Profile Chrome tasks covering
+public GitHub reading, search, precise text scrolling, restrictive-CSP
+annotation, screenshot and PDF export, verified disposable form input and
+submission, and managed-only cleanup. All six pre-existing user tabs remained
+available and none was acquired during cleanup.
+
+The stable source passed TypeScript checking, 277 Node tests, 109 isolated
+Playwright tests, all three npm distribution modes, 13 stdio conformance checks,
+and 13 isolated multi-Host integration checks. The stable version keeps the
+same protocol 1.2 and runtime behavior as `v0.3.0-rc.6`.

package/package.json

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