docs/reference/playwright.md: version "v1.52.0" in visual regression example uses Docker image format, not npm semver

[github-actions]

Problem

docs/src/content/docs/reference/playwright.md contains a version format inconsistency in the Visual Regression Testing example.

Line 154 specifies version: "v1.52.0" for mode: cli:

tools:
  playwright:
    mode: cli
    version: "v1.52.0"

However, the configuration table in the same file (line 46–56) documents that CLI mode pins the @playwright/cli npm package, with a default of 0.1.13 — standard npm semver without a v prefix. The v1.52.0 format is used for Playwright browser Docker image releases (MCP/Docker mode), not the npm package.

There is no @playwright/cli npm version 1.52.0.

Impact

Enterprise users copying the visual regression example will apply a Docker-image version string to an npm package pin. This creates confusion when:

• Debugging version pinning failures
• Cross-referencing the configuration table in the same file
• Understanding which package version is actually resolved

Fix

Single file change: docs/src/content/docs/reference/playwright.md

Change line 154 from:

    version: "v1.52.0"

to:

    version: "0.1.13"  # pins `@playwright/cli` npm package; see Configuration > Version

This aligns the example with the format documented in the configuration table and removes the ambiguous v prefix.

Acceptance Criteria

• Visual regression example uses version: "0.1.13" (or another valid @playwright/cli npm version)
• No v prefix in any CLI mode version example
• Only docs/src/content/docs/reference/playwright.md is changed

📊 User experience analysis by Delight · 302.9 AIC · ⌖ 26.3 AIC · ⊞ 19.9K · ◷

• expires on Jun 16, 2026, 7:29 AM UTC-08:00

[github-actions]

Caution

agentic threat detected
Threat detection flagged this output in warn mode. Manual review is REQUIRED before any follow-up automation.

Details

The threat detection results could not be parsed.

Review the workflow run logs for details.

🍪 Issue Monster selected this for Copilot

I've identified this issue as a good candidate for automated resolution and requested assignment to the Copilot coding agent.

If assignment succeeds, the Copilot coding agent will analyze the issue and create a pull request with the fix.

Om nom nom! 🍪

🍪 Om nom nom by Issue Monster · 28.7 AIC · ⌖ 4.54 AIC · ⊞ 23.3K · ◷

[github-actions]

This issue was automatically closed because it expired on 2026-06-16T15:29:45.889Z.

Closed by Workflow