docs: add Common use cases to chrome_policy page

[Jayko001]

Summary

Adds a "Common use cases" section to browsers/pools/policy-json.mdx before "Available policies", documenting the non-pool path (chrome_policy on browsers.create()) with two recipes:

• Allow pop-ups — DefaultPopupsSetting: 1 for sites that open download dialogs or OAuth windows.
• Control file download behavior — DefaultPopupsSetting: 1 + DownloadRestrictions: 0 for download-permission prompts.

Each use case has Python + TypeScript tabs in a CodeGroup, matching the existing style on the page.

---

Note

Low Risk
Documentation-only MDX additions with no runtime or API behavior changes.

Overview
Adds a Common use cases section to the custom Chrome policies doc (before Available policies), clarifying that chrome_policy works on browsers.create() as well as pools.

Documents two automation-focused recipes with Python/TypeScript CodeGroup examples: allowing pop-ups via DefaultPopupsSetting: 1, and relaxing download prompts with DefaultPopupsSetting: 1 plus DownloadRestrictions: 0.

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

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
Kernel	🟢 Ready	View Preview	Jun 23, 2026, 4:09 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[firetiger-agent]

Firetiger deploy monitoring skipped

This PR didn't match the auto-monitor filter configured on your GitHub connection:

PRs in the kernel, infra, hypeman, and hypeship repos. kernel is a ~mono repo with many logical services underneath, ensure to focus on the implicated service for the PR

Reason: PR is a documentation-only change to a policy documentation page and does not appear to be in the kernel, infra, hypeman, or hypeship repos.

To monitor this PR anyway, reply with @firetiger monitor this.

[cursor]

Risk assessment: Very Low.

Evidence from the diff: this PR only adds documentation examples to browsers/pools/policy-json.mdx (66 added lines), with no executable code, navigation/config changes, infrastructure changes, auth/permissions changes, or production logic modified. I also did not find a CODEOWNERS file in the workspace.

Approval decision: the PR already has an approval recorded, so I’m leaving this assessment as a comment and not re-approving.

  

_{Sent by Cursor Automation: Assign PR reviewers}