Change user_data_dir="auto" to use a package-owned, non-default Chrome user
data directory under the platform app data directory, avoiding Chrome 136+
remote debugging restrictions on Chrome stable's platform default profile root
(#13).
Raise ChromeRemoteDebuggingBlockedError before launch when Chrome stable is
configured with its platform default user data directory, because Playwright's
persistent context depends on Chrome's remote debugging pipe (#13).
Raise ChromeProfileInUseError before launching when the resolved Chrome
user data directory contains known profile lock artifacts. Pass
check_profile_lock=False to skip the advisory stale lock check (#14).
Raise ChromeNotFoundError when automatic Chrome executable detection finds
nothing, with a message listing checked paths and
PLAYWRIGHT_BYOB_CHROME_PATH. Pass browser_path=None to opt into
Playwright's channel="chrome" path explicitly (#15).
Add a signature drift regression test to keep the shared launch options for
launch_chrome(), async_launch_chrome(), and build_chrome_launch_config()
aligned while preserving builder-only sys_platform and env overrides (#16).
Update README and usage guidance to recommend default, temporary, or custom
non-default automation directories instead of the blocked platform Chrome
profile root (#13).
Clarify that using installed Chrome and using a real user profile are separate
choices, and document safer profile patterns such as temporary profiles and
dedicated automation profiles (#9).
Document the relationship between persistent Chrome contexts and Playwright's
storage-state authentication files (#9).
Add a macOS-only local integration test that launches installed Google Chrome
through launch_chrome(), drives a small local HTML app, and verifies cookie
and local storage persistence across browser sessions (#6).
Register a pytest integration marker for tests that launch an installed
browser and are skipped in CI (#6).