browser-tool-routinglisted

# Browser Tool Routing ## Purpose Choose the browser provider before acting. The current provider model is: - Webwright: high-level long-horizon web tasks, reusable scripts, RPA, extraction, comparison, and evidence-first workflows. - Playwright CLI: low-level browser flow validation, deterministic screenshots, snapshots, headed sessions, traces, console/request checks, and final UI proof. - Chrome DevTools MCP: console/network/runtime/performance/memory/Lighthouse debugging and live Chrome inspection. RU triggers: проверь UI, проверь в браузере, визуально, pixel-perfect, сравни с Figma, сравни с фото, скриншот, консоль, сеть, перфоманс, Lighthouse. EN triggers: validate UI, browser check, visual QA, pixel-perfect, compare with Figma, compare with reference image, screenshot, console, network, performance, Lighthouse. ## Routing Use Webwright first for: - Long-horizon web task execution: search, filter, compare, extract, upload, export, repeat. - Reusable RPA or web workflow creation where `plan.md`, logs, screenshots, and `final_script.py` are expected. - Multi-page evidence-first workflows where the result must be rerunnable. Use Playwright CLI first for: - Low-level browser flow validation, route navigation, forms, clicks, keyboard, dialogs, modals, tabs, uploads, waits, and state transitions. - Screenshot capture under `browser/`, accessibility snapshots, responsive viewport matrices, traces, videos when needed, and post-fix revalidation. - Figma/photo/reference-