Chrome Process Architecture: Browser/Renderer/GPU + wkappbot CDP Isolation

Reference: Chromium multi-process model (browser/renderer/GPU/utility), Chrome DevTools Protocol surface (HTTP discovery, WebSocket, target/session model), and how wkappbot enforces per-instance CDP isolation via the wkappbot.cdp Win32 window property and ManagedCdpPort scoring. Explains why EnumWindows naturally scopes to the browser process, why renderer child windows never appear in a11y find, and the exact CDP commands behind each web subcommand.

Steps