v0.9.2

Browser routing boundary fixes

• Require explicit host: "local" before materializing browser captures or reports into local files. Remote and unresolved hosts fail clearly instead of treating a remote path as local.
• Reuse browser caches, approvals and tab journals only with a complete account/host selection. Inherited browsing still works, but incomplete identity cannot reuse persistent state.
• Validate administrative command arguments before changing settings. Reject unknown flags, malformed selectors and flag-shaped/control-character host names.
• Preserve the 0.9.1 per-call MCP account/host API, browserContext reports and browse.context().
• Make report-routing regression tests portable across Windows and Node 18/20/22.

Migration

For local captures/reports, pass --host local in CLI calls or host: "local" in supported MCP calls. To reuse caches or approvals, also select the intended account. Configured defaults may use:

{"browseContext":{"account":"u1","host":"local"}}

Replace the account with the one intended for the task. This configuration does not change native Aside defaults. Context reports describe selection, not proof of live authentication.

Verification

Local suite: 1,097 passed, 0 failed, 1 platform-specific skip. Release requires the exact main SHA to pass the five-combination Linux/macOS/Windows CI matrix, followed by the existing OIDC dry-run and publish workflow. No new dependencies.

Includes #50; release promotion #51. npm provenance identifies the publishing workflow and source commit. The attached CycloneDX SBOM describes the dependency-free package.