Cookie bridge imports only auth cookies, losing session state

[andrema2]

Problem

The cross-platform cookie bridge (import_cookies) only imports li_at and li_rm cookies, discarding all other LinkedIn session cookies (JSESSIONID, bcookie, lidc, bscookie, liap, etc.).

This causes authentication to fail silently when the native Chromium profile can't decrypt cookies (e.g., macOS → Docker). The cookie bridge recovers auth tokens but the missing session cookies cause LinkedIn to return empty/partial responses.

Expected Behavior

All LinkedIn cookies should be imported during the cookie bridge flow, not just the two auth tokens.

Steps to Reproduce

1. Login on macOS with --login
2. Run MCP server in Docker (or after Cookies DB becomes unreadable)
3. Cookie bridge activates, imports only li_at + li_rm
4. LinkedIn returns empty responses despite valid auth tokens

Proposed Fix

Change import_cookies() to import all LinkedIn domain cookies while still validating that li_at/li_rm are present.

[stickerdaniel]

Hey, I tried converting the cookies ony initially and then storing the Docker session after successful login but had less stable results than recreating the session every time. The uvx installation is the better method by architecture, creating a session on a different host and using it to login on a different environment is always more brittle than creating the session with uvx and running the scraper with the same profile.