CodeVetter · Repo Unpack · Contributor handoff
microsoft/playwright
Start with the owning package and follow the relevant client/protocol/server or runner/worker boundary. Preserve generated-source ownership, dependency rules, and platform-specific behavior. Tests and CI were inspected, not executed, and this inventory is bounded rather than exhaustive. The commands below are future validation pointers; the current read-only investigation did not run them.
- Read package.json, CONTRIBUTING.md, CLAUDE.md, and the owning package manifest first: browser API work belongs primarily in playwright-core, runner work in playwright, with Node.js >=20 and npm workspaces.
- Preserve client/server import separation and inspect DEPS.list before moving code; actual client dependency declarations allow shared protocol/isomorphic utilities rather than server implementations.
- Edit API documentation and protocol schemas as source inputs rather than treating generated types/channels/validators as independent implementations; generator checks may write files.
- Place page interaction tests with pageTest fixtures, browser/context lifecycle tests with browserTest, runner tests with playwright-test fixtures, and agent-tool tests with MCP fixtures.
- For later authorized validation, use filtered ctest for Chromium browser behavior, ttest for runner changes, and ctest-mcp for agent tools; broaden to other affected engines after the focused check. Tests and CI in this report were inspected, not executed.
- Use root build/lint scripts when execution is authorized, but do not assume a watcher is running; tsconfig uses strict checking and excludes generated lib directories, extension code, and tool skills from its package compilation scope.
- Treat storage edits as coordinated client, dispatcher, server, and injected-script changes; preserve optional collection flags, initial/API/reuse branches, intercepted navigation, and page/interceptor cleanup.
- Keep tests hermetic and cross-platform, inspect fixme/skip and CI trigger conditions before describing coverage, and follow the documented linked-issue/approval policy before submitting upstream contributions.