The drop-in Playwright SDK is the part I would test first. We run headless Chromium on a small droplet to post content across a dozen platforms, and our worst failure was never detection, it was lifecycle: when a job crashed mid-upload, the renderer and GPU processes outlived the Python parent, and after a few days the box ran out of file descriptors while monitoring showed everything green. We ended up writing our own watchdog that kills orphaned process groups. Since Clearcote ships its own binary and SDK wrapper, does it launch the browser in its own process group and clean it up when the controlling script dies, or is that still left to the caller?