effect-browserbase 0.2.0-beta.8 → 0.2.0-beta.9

package/README.md

@@ -2,7 +2,7 @@
 
 `effect-browserbase` supplies Browserbase resources and hosted lifetimes to the shared browser runtime: account identity and transport, session, context and extension resources, one owned browser over Playwright/CDP — allocated or borrowed — with trusted registrations, modeled file selection, bounded live capture, explicit page holds, the provider's recordings, replays, uploads and website downloads, and the platform APIs outside a browser session (projects, certificates, Search, Fetch, Agents, Functions and webhooks).
 
-Its host supplies the required `effect-browser` peer, at the same coordinated `0.2.0-beta.8` version; it has no Effect Agent dependency. Install both packages explicitly so the provider and application share one runtime instance. Playwright is an optional peer of the shared runtime and is loaded only when a browser connects; artifact-only consumers do not need it. The Effect peer range is `^4.0.0-rc.117`, with rc.117 qualified. The package targets trusted Node and Bun hosts. It is published as a beta (`0.2.0-beta.0` on the `beta` dist-tag): hosted provider behavior requires separate validation, and ordinary tests never create a paid Browserbase session or invoke a paid model.
+Its host supplies the required `effect-browser` peer, at the same coordinated `0.2.0-beta.9` version; it has no Effect Agent dependency. Install both packages explicitly so the provider and application share one runtime instance. Playwright is an optional peer of the shared runtime and is loaded only when a browser connects; artifact-only consumers do not need it. The Effect peer is exactly `4.0.0-rc.117`, the tested version: later Effect releases moved the `effect/unstable/*` modules this package imports. Releases through `0.2.0-beta.8` declared a caret range; with one of them, install exactly the Effect it was tested with (`4.0.0-rc.117` from `0.2.0-beta.3`, `4.0.0-rc.115` before). The package targets trusted Node and Bun hosts. It is published as a beta, on the `beta` dist-tag: hosted provider behavior requires separate validation, and ordinary tests never create a paid Browserbase session or invoke a paid model.
 
 ## One account, then resources
 
@@ -172,7 +172,7 @@ Larger files use `BrowserbaseUploads.create`, which places bytes for the exact r
 | Reuse old page/frame metadata after reconnect         | In the same known browser lifetime, read fresh pages and match exactly one saved `targetId`; then read fresh frames. No fallback to order, old ID, URL or title                     |
 | `Adapter.fromSession(session)` or implicit selection  | Supply the owning session and issued Page to `yield* Adapter.fromSession(session, page)`; its lifecycle remains on the original browser owner                                       |
 | `BrowserError.reason` string and optional outcome     | Tagged reason and required outcome. Use `Effect.catchReason`; factual limit/status/retry fields belong to their reason                                                              |
-| All host reason names reach model output              | A compact eleven-reason tool failure; original structured fields and bounded call IDs remain in `ToolHost.toolFailures`                                                             |
+| All host reason names reach model output              | Thirteen tool failure reasons; original structured fields and bounded call IDs remain in `ToolHost.toolFailures`                                                                    |
 | `closeChecked` success is `undefined`                 | Concrete receipt success after the existing ownership check; `close` and `cleanupResult` remain available                                                                           |
 | Capture `dropped`                                     | `discarded = overflow + late + duplicates + rejected`; no change to default capacity or unknown upstream loss                                                                       |
 | Non-supervising helper takes default `BrowserSession` | Use `AnySession`; keep supervising helpers generic in callback error or concrete session                                                                                            |
@@ -182,7 +182,11 @@ Larger files use `BrowserbaseUploads.create`, which places bytes for the exact r
 `resume(token, operatorReleasedControl)` and `reconnect(operatorReleasedControl)` return a
 bounded `Inventory` containing the new owner generation and fresh Page metadata. They do not
 read page content or issue observed references. Acquire an issued Page from `inventory.pages`
-and call `page.observe()` explicitly. `detach` returns its pre-disconnection inventory and exact
+and call `page.observe()` explicitly. A handoff retires Page authority although the connection
+stays open: every Page and Frame issued before `beginHandoff`, `session.initialPage` included,
+belongs to the paused generation, and after `resume` its operations fail `Stale` and
+`undispatched`. Issue each Page again with `session.page(info)` from `inventory.pages`, and its
+Frames with `page.frame(info)`. `detach` returns its pre-disconnection inventory and exact
 selected native `targetId`, preserving bounded target identities for deliberate attachment;
 its Page IDs are old authority and cannot be reused after reconnect. Page metadata is a sequence
 of native reads and is non-atomic.
@@ -239,7 +243,7 @@ const launch = recipe({
 
 A host that does this still selects `Unrestricted` here, and the containment claim is the host's own, made at its proxy. This package keeps refusing `ExactHosts` and `PublicWeb`, because it has no evidence that every connection of a hosted session takes that proxy. The provider documents how rules are ordered, not whether WebRTC, QUIC or name resolution go through one, and no hosted run in this repository has tested it. Accepting either policy needs that evidence first: a hosted session behind one catch-all proxy, exercised through navigation, redirects, frames, subresources, popups, workers, service workers, WebSockets and non-HTTP transports, with nothing arriving anywhere but the proxy.
 
-What this package does check is input, not requests. `controlFacts` and an `admit` policy ([above](#what-is-on-screen-and-what-a-host-may-know-about-it)) let a host that drives the session refuse a link or a form by its resolved destination before anything is sent. That limits what the host's own automation acts on. It does not limit what a page loads, or where it redirects.
+What this package does check is input, not requests. `controlFacts` and an `admit` policy ([common browser guide](../browser/README.md#what-is-on-screen-and-what-a-host-may-know-about-it)) let a host that drives the session refuse a link or a form by its resolved destination before anything is sent. That limits what the host's own automation acts on. It does not limit what a page loads, or where it redirects.
 
 ## Testing against a scripted control plane
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "effect-browserbase",
-  "version": "0.2.0-beta.8",
+  "version": "0.2.0-beta.9",
   "description": "Effect-based Browserbase resources and hosted integration for effect-browser.",
   "license": "MIT",
   "repository": {
@@ -14,8 +14,8 @@
     "node": "^22.18.0 || >=24.11.0"
   },
   "peerDependencies": {
-    "effect": "^4.0.0-rc.117",
-    "effect-browser": "0.2.0-beta.8"
+    "effect": "4.0.0-rc.117",
+    "effect-browser": "0.2.0-beta.9"
   },
   "homepage": "https://github.com/mannyc2/effect-agent-browserbase#readme",
   "bugs": {