mygo/docs/web/decisions/0005-playwright-cli-debugging.md

ADR-0005: Use the Pinned Playwright CLI for Agent Debugging

Status: Accepted
Date: 2026-07-15

Context

The Playwright MCP package introduced a second Playwright core, a second Chromium revision, and a larger agent tool surface. The pinned test runner provides the required interactive commands through its CLI.

Decision

• Use the playwright:cli npm script as the browser-debugging entry point.
• Use @playwright/test as the Playwright dependency for tests and diagnostics.
• Use the bundled Chromium revision selected by the pinned package.
• Load .playwright/cli.config.json for headless, isolated, and sandboxed execution.
• Use the repository-scoped $playwright-cli skill for agent browser work.
• Limit CLI output under .artifacts/playwright-cli/.

Consequences

• E2E tests and interactive diagnostics share one Playwright core and Chromium revision.
• The npm script isolates operators and agents from upstream CLI entry-point changes.
• The repository skill keeps the main workflow concise and exposes detailed references on demand.