logged-in-google-chromelisted

# Logged In Google Chrome Use a dedicated Chrome user-data-dir and attach Playwright only after Chrome is already running. ## Quick Start 1. Run [scripts/launch_logged_in_chrome.ps1](./scripts/launch_logged_in_chrome.ps1) to start normal Chrome with a dedicated profile folder and a CDP port. The script now waits for the dedicated-profile Chrome process and the CDP endpoint before it reports success. 2. Let the user log in manually if the profile is not logged in yet. 3. In `js_repl`, attach Playwright with `chromium.connectOverCDP("http://127.0.0.1:<port>")`. 4. Reuse the attached browser and page handles for the rest of the task. ## Defaults - Default user-data-dir: `D:\Prj\onizuka-playwright-profile` - Default CDP port: `9222` - Default login URL: `https://accounts.google.com/` ## Rules - Do not log into Google from a Playwright-launched Chrome window. - Do not point Playwright at `%LOCALAPPDATA%\Google\Chrome\User Data`. - Do use a dedicated user-data-dir that is separate from the user's everyday Chrome profile. - Do launch Chrome first as a normal browser, then attach Playwright over CDP. - Do keep the attached CDP browser alive across steps instead of reconnecting unless the process changed. ## Launch Run: ```powershell powershell -ExecutionPolicy Bypass -File .\scripts\launch_logged_in_chrome.ps1 ``` Do not assume launch succeeded just because a command returned. Only continue when the launch script exits successfully or [scripts/check_cdp_port.ps1](./scri