Reuse a persistable Browserbase session across disconnects (keep-alive)

Documented steps

1. Create a session once and store its session id; avoid re-creating for every short task because each creation has a one-minute minimum billing period.
2. To reconnect to an existing session, pass the saved `sessionId` (many integrations accept a sessionId/connectUrl param at connect time).
3. For disconnection-tolerant long workflows, enable the keep-alive feature at session creation so the session survives client disconnects and can be resumed.
4. When reconnecting, continue using the same session for similar workloads to avoid repeated minimum charges.
5. When the task is complete, explicitly stop/end the session so it stops billing (keep-alive availability depends on your plan).
6. Official doc: https://docs.browserbase.com/optimizations/cost/measuring-usage and https://docs.browserbase.com/platform/browser/long-sessions/overview