add BrowserRun types

[Refaerds]

Summary

Adds TypeScript type definitions for the existing browser binding:

• BrowserRun — abstract class with fetch() and overloaded quickAction() method supporting 8 action types
• Action-specific option types: BrowserRunScreenshotOptions, BrowserRunPDFOptions, BrowserRunScrapeOptions, BrowserRunLinksOptions, BrowserRunSnapshotOptions, BrowserRunJsonOptions, BrowserRunMarkdownOptions, BrowserRunContentOptions
• Quick action response types: BrowserRunContentSuccessResponse, BrowserRunLinksSuccessResponse, BrowserRunScrapeSuccessResponse, BrowserRunSnapshotSuccessResponse, BrowserRunJsonSuccessResponse, BrowserRunMarkdownSuccessResponse, BrowserRunErrorResponse, BrowserRunJsonErrorResponse

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[Refaerds]

I have read the CLA Document and I hereby sign the CLA

[jamesopstad]

/bonk review this PR

[ask-bonk]

Review: BrowserRun types

Good addition overall — the types are well-documented with JSDoc, follow the BrowserRun product prefix convention correctly, and the overloaded quickAction pattern is a solid approach for discriminated-union-style APIs.

I have a few issues to flag, one of which is a type system anti-pattern explicitly called out in this repo's guidelines.

Summary of issues

1. result: object is a repo anti-pattern — types/AGENTS.md says "Never use bare object as a type."
2. BrowserRunJsonOptions union doesn't enforce the documented constraint — both prompt and response_format can be provided in either branch.
3. cacheTTL placement — @ruifigueira already flagged this; needs confirmation.
4. generated-snapshot/ files should be regenerated, not hand-edited — types/AGENTS.md states: "Do not edit files in generated-snapshot/ directly — they are overwritten by just generate-types." Please run just generate-types and commit the resulting files instead of manually editing the snapshots.
5. Minor: inconsistent meta presence across response types (may be intentional, but worth confirming).
6. Minor: fetch() method has no JSDoc.

[ask-bonk]

Review posted successfully. Here's a summary of what I flagged:

Review posted on PR #6771

6 issues identified, 5 inline comments:

1. result: object anti-pattern (line 327) — types/AGENTS.md explicitly forbids bare object. Suggested Record<string, unknown> instead.

2. BrowserRunJsonOptions union doesn't enforce exclusivity (lines 237-253) — The JSDoc says "exactly one of prompt or response_format" but the union allows both. Suggested using never on the excluded branch, or updating the doc if both are actually allowed.

3. cacheTTL placement (line 119) — Flagged alignment with @ruifigueira's existing comment about whether cacheTTL was moved into options.

4. generated-snapshot/ manually edited (top-level comment) — Per types/AGENTS.md, these files should be regenerated via just generate-types, not hand-edited.

5. Inconsistent meta field (lines 273-277) — Some success responses have meta: BrowserRunResponseMeta (content, snapshot) while others don't (links, scrape, json, markdown). Requested confirmation this is intentional.

6. Missing fetch() JSDoc (line 354) — Suggested adding a brief description to match other binding classes.

github run

[jamesopstad]

Please can you add comments when marking conversations as resolved. Otherwise it's difficult to know what the resolution was.

[Refaerds]

Please can you add comments when marking conversations as resolved. Otherwise it's difficult to know what the resolution was.

re-added them. Didn't realize that clicking Resolve doesn't automatically save the comment that I typed :)

[jamesopstad]

The snapshot needs updating but otherwise looks good.

[Refaerds]

The snapshot needs updating but otherwise looks good.

Updated, can you re-approve please?