Fix VRT workflow by installing Playwright browsers directly on runner

[Copilot]

The VRT workflow failed because the Docker container action (docker://mcr.microsoft.com/playwright:v1.56.1-jammy) runs in an isolated environment without access to the checked-out repository, installed dependencies, or built Storybook files.

Changes

Workflow execution model:

• Replaced Docker container action with direct Playwright browser installation on runner
• Added npx playwright install --with-deps step before test execution
• Updated Storybook URLs from Docker bridge network (172.17.0.1) to localhost
• Added cleanup condition to styled-react storybook stop step

This aligns with the existing storybook-tests.yml workflow pattern.

Changelog

Changed

• VRT workflow now installs Playwright browsers directly on the runner instead of using Docker container action

Rollout strategy

• Patch release
• Minor release
• Major release; if selected, include a written rollout or migration plan
• None; CI/CD infrastructure change only

Testing & Reviewing

Verify VRT workflow runs successfully on the next push.

Merge checklist

• Added/updated tests
• Added/updated documentation
• Added/updated previews (Storybook)
• Changes are SSR compatible
• Tested in Chrome
• Tested in Firefox
• Tested in Safari
• Tested in Edge
• (GitHub staff only) Integration tests pass at github/github (Learn more about how to run integration tests)

Original prompt

Fix the failing GitHub Actions workflow vrt-reports / vrt-runner (1)

Analyze the workflow logs, identify the root cause of the failure, and implement a fix.

Job ID: 59110980159

Job URL: https://github.com/primer/react/actions/runs/20581899653/job/59110980159

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0c4fa95

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

[barmo]

Sorry a new hubber here! I was trying out the copilot features on github for the first time to understand a failed check, and accidentally spun up an agent without realizing. Closing this