feat: add Browser Session lifecycle authority

ARCHITECTURE.md

@@ -149,10 +149,17 @@ surfaces do not silently fall back to ambient host values.
 
 Owns the narrow WebDriver BiDi adapter contract that is expressible by one explicit specification revision. The active slice pins the W3C WebDriver BiDi Working Draft published on 3 September 2026 at `https://www.w3.org/TR/2026/WD-webdriver-bidi-20260903/` and delegates complete-profile admission back to `originweave-fingerprint`. Standard BiDi covers viewport, device-pixel-ratio, timezone, and reduced-motion surfaces. Its width/height screen command cannot prove the kernel's complete screen-and-color-depth surface, and its single locale cannot prove ordered language preferences; hardware concurrency and the complete Chromium platform/User-Agent Client Hints surface also remain outside the standard set. The adapter therefore fails first on `Screen` rather than inheriting ambient Chromium values. It can plan two typed reusable-context commands—viewport/DPR and timezone—for one bounded opaque browsing-context identifier. Reduced motion remains an expressible protocol capability, but the reusable plan does not install it because `features: null` removes the target's complete media-feature override configuration rather than restoring prior state. Generic cleanup therefore resets only viewport/DPR and timezone. No caller-mintable exclusive-reset type is exposed; a Browser Session owner must instead prove a disposable context lifecycle or restore the complete prior media configuration. Planning sends nothing and proves neither acknowledgement, cleanup, ownership, nor page-visible state. Transport, post-condition observation, and reusable-context media restoration require the pinned Chromium/BiDi path and, for Chromium-only surfaces, a separate versioned `originweave-cdp` adapter.
 
+### `originweave-browser-session` (active PR)
+
+Owns the Browser Session aggregate boundary for disposable context lifecycle and presentation-mutation authority. Raw `BrowserSessionId` and `BrowsingContextId` values are transport addressability only. A context enters the owned set only after the narrow `DisposableContextPort` reports a fresh disposable isolation boundary together with its browsing-context address. The aggregate stores that exact handle and issues a non-caller-constructible `PresentationMutationAuthority` bound to browser-session identity, disposable-isolation identity, browsing context, and monotonic context epoch.
+
+The isolation identity prevents distinct aggregate incarnations from aliasing authority when external session/context identifiers and local epoch values are reused. Destruction validates the full authority before adapter I/O and passes the stored isolation handle back to the port; cleanup authority is never reconstructed from `(BrowserSessionId, BrowsingContextId)`. For a WebDriver BiDi adapter, the port contract requires a one-to-one mapping from the domain's `DisposableIsolationId` to the specification-defined unique user-context id created for that live boundary. The protocol identifier is lifecycle addressability, not OriginWeave policy authority. Stale, foreign-session, foreign-isolation, unknown, destroyed, or uncertain authority fails closed; failed destruction makes the context uncertain; browser transport loss invalidates active authority; and normal session end is rejected until every owned boundary has proven destruction.
+
+This active slice deliberately stops before browser transport. WebDriver BiDi/CDP remain adapters and do not mint policy authority. The current proposal does not yet bridge domain authority into `originweave-bidi`'s private presentation/screen-area witnesses, implement the real `browser.createUserContext`/`browsingContext.create`/`browser.removeUserContext` adapter, prove exact-boundary cleanup post-conditions in Chromium, or establish protected-main behavior. ADR 0114, the Browser Session traceability dossier, and the lifecycle UML record those remaining boundaries.
+
 ## 6. Planned modules
 
 ```text
-originweave-session       isolated browser contexts and checkpoints
 originweave-proxy         separately approved proxy and final-target routing
 originweave-http          request, response, redirect, and elapsed-time budgets
 originweave-observation   AX + DOM + layout + network semantic snapshots
@@ -285,6 +292,7 @@ WARC stores source exchanges and resources; relational storage holds sessions, p
 - Proxy and PAC routing cannot be inherited ambiently by the direct-only or TLS kernels.
 - Redirects cannot inherit ambient origin or network authority.
 - TCP peer equality does not substitute for TLS server identity, and TLS identity does not substitute for HTTP safety.
+- Disposable Browser Session mutation and destruction authority is bound to the exact owned isolation identity as well as session, context, and epoch; raw driver identifiers alone cannot cross that boundary.
 - Arbitrary script evaluation is absent from the standard action interface.
 - Crawler policy is not treated as access authorization.
 - High-risk actions fail closed when context, canonical intent, or approval evidence is incomplete.

Cargo.toml

@@ -10,6 +10,7 @@ members = [
     "crates/originweave-tls",
     "crates/originweave-fingerprint",
     "crates/originweave-bidi",
+    "crates/originweave-browser-session",
 ]
 resolver = "3"
 

crates/originweave-browser-session/Cargo.toml

@@ -0,0 +1,17 @@
+[package]
+name = "originweave-browser-session"
+description = "OriginWeave Browser Session lifecycle and mutation-authority contracts."
+version.workspace = true
+edition.workspace = true
+rust-version.workspace = true
+license.workspace = true
+authors.workspace = true
+repository.workspace = true
+homepage.workspace = true
+publish = false
+
+[dependencies]
+originweave-core = { path = "../originweave-core" }
+
+[lints]
+workspace = true