Terminate a running Browserbase session early via the session update endpoint to stop usage charges

Documented steps

1. Authenticate with headers X-BB-API-Key: <api-key> and Content-Type: application/json. Reference: https://docs.browserbase.com/reference/api/update-a-session
2. Send POST https://api.browserbase.com/v1/sessions/{id} - note this is POST, not PATCH or PUT, despite being an update operation.
3. Send the JSON body {"status": "REQUEST_RELEASE"}. REQUEST_RELEASE is the only documented value for this field; it requests that the session complete.
4. Expect HTTP 200 with the updated Session object in the response.
5. Confirm the transition by listing sessions with a status filter (GET /v1/sessions?status=COMPLETED) and matching on the session id.
6. Understand the lifecycle: a session runs, then lands in one of the terminal states COMPLETED, TIMED_OUT or ERROR. A successful release should land in COMPLETED, not ERROR.
7. Wire the release call into a finally block or equivalent cleanup path so an exception in your automation still ends the session.
8. If the session was created with keepAlive: true, the release call is the mechanism that actually ends it - simply disconnecting your client will not.