Improve Playwright CI configuration

[aidenybai]

Summary

• centralize CI detection in the Playwright configuration
• run Playwright with four workers and two retries in CI
• use the Chrome installation preinstalled on GitHub Actions runners
• keep one retry for local runs

Why

The CI configuration previously used a single worker and Playwright's default browser channel. Using the runner's preinstalled Chrome avoids depending on a separately downloaded browser, while four workers improve end-to-end test throughput.

Validation

• vp check
• vp run test — 564 passed, 2 skipped
• CI=1 vp exec playwright test --list — 384 tests discovered

[changeset-bot]

⚠️ No Changeset found

Latest commit: a85363f

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
bippy	Ready	Preview	Jul 31, 2026 1:19am

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/bippy@81

commit: a85363f