(MOT-3250) fix(harness): share Playwright browser cache

[ytallo]

Summary

• give the quickstart job one explicit Playwright browser cache outside its isolated HOME
• make the browser installation step and Console validator resolve the same Chromium executable

Root cause

The workflow installed Chromium under the runner's default HOME, then the quickstart validator replaced HOME with a temporary secret-safe directory. Playwright consequently searched the isolated cache and failed before launching the Console browser.

Failure evidence: https://github.com/iii-hq/workers/actions/runs/31763504042/job/94654571775

Impact

The Console first-message quickstart can launch Chromium while preserving the isolated quickstart HOME.

Validation

• actionlint 1.7.12
• ShellCheck 0.10.0
• installed Chromium in an explicit cache, changed HOME, and launched the browser successfully
• Playwright collected the focused quickstart test
• git diff --check

Refs MOT-3250

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
workers	Building	Preview	Aug 14, 2026 2:30am
workers-tech-spec	Ready	Preview	Aug 14, 2026 2:30am

[coderabbitai]

Warning

Review limit reached

@ytallo, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 42 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 4e54eacd-4bd9-444f-a2a4-c9faa1a8d845

📥 Commits

Reviewing files that changed from the base of the PR and between 9ad4e3b and 85844b5.

📒 Files selected for processing (1)

• .github/workflows/harness-quickstart.yml

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

skill-check — worker

0 verified, 59 skipped (no docs/).

Layer	Result
structure	✓
vale	✓
ai	✓
render	✓

Four for four. Nicely done.