Add Web Bot Auth and proxy routes session options

[NikhilShahi]

• CreateSessionParams.webBotAuth (true, or { onlyDomains }) signs the session's requests with Web Bot Auth. It works for sessions and agent tasks; SessionLaunchState.webBotAuth reports how a session signs.
• CreateSessionParams.proxyRoutes chooses, per host, whether traffic goes through the session's proxy ("default") or straight out ("direct"). It only applies when creating a session.
• README sections for both.

Summary

Changes

Validation

• yarn lint
• yarn build

---

Note

Low Risk
SDK surface is additive (types, README, passthrough tests) with no client-side behavior changes beyond sending new JSON fields.

Overview
Adds Web Bot Auth and proxy routes as documented session-creation options in the Node SDK.

CreateSessionParams now accepts webBotAuth (true or { onlyDomains }) and proxyRoutes (per-host direct vs default proxy). SessionLaunchState can expose webBotAuth with signatureAgent and optional onlyDomains. New public types (WebBotAuthParams, ProxyRoute, SessionWebBotAuth) are re-exported from @hyperbrowser/sdk/types. The README documents usage, agent-task sessionOptions support for Web Bot Auth, and constraints (e.g. no mix with ultra stealth / snapshot / certain egress flags).

Unit tests assert sessions.create and agent browserUse.start forward these fields unchanged in the API request body, plus compile-time type checks.

^{Reviewed by Cursor Bugbot for commit 6df60f7. Bugbot is set up for automated code reviews on this repo. Configure here.}