Codex Chrome connector needs reliable background authenticated browser automation

Codex Chrome integration is not reliable enough for real authenticated workflow automation on Windows.\n\nMain issues:\n- Connecting to an existing signed-in Chrome session is fragile.\n- CDP/tab attachment often requires workaround scripts instead of first-class tooling.\n- Browser automation can interfere with the user's visible browser/mouse, which is not acceptable for long-running admin or finance workflows.\n- The agent needs a stable background-browser mode that can use the user's authenticated session without taking over the visible browser.\n- Failures are hard to diagnose: connection state, tab targeting, permissions, profile/session state, and native bridge state need clearer errors and recovery steps.\n\nRequested improvements:\n1. Reliably attach to an authenticated Chrome profile/session.\n2. Support background downloads and API/network observation without controlling the user's mouse.\n3. Enumerate, select, and claim tabs safely.\n4. Preserve login/session state across runs.\n5. Provide clear diagnostics when Chrome/CDP/native-bridge connection fails.\n\nWhy it matters:\nAuthenticated portal workflows are a major Codex use case. When Chrome attachment is flaky or takes over the visible browser, the user cannot keep working while Codex does the background task. This blocks serious workflows involving logged-in business portals, document downloads, and read-only evidence gathering.