Context
Some users (not all) are invalidated after one request. This inconsistency can be account/network-specific.
Hypothesis
LinkedIn risk scoring may flag certain IP ranges (VPN, corporate NAT, datacenter-like egress), invalidating session cookies after suspicious requests.
Proposed work
- Add opt-in debug mode that logs sanitized response metadata for invalidation events (status, redirect location, cookie delete markers).
- Collect reproducibility matrix by network type (home, office, VPN on/off).
- Document mitigation guidance (disable VPN/proxy for auth-sensitive commands, retry from residential network).
Acceptance criteria
- We can correlate invalidation frequency with network conditions from debug captures.
- README troubleshooting has a concrete network section for affected users.
Refs: #6
Context
Some users (not all) are invalidated after one request. This inconsistency can be account/network-specific.
Hypothesis
LinkedIn risk scoring may flag certain IP ranges (VPN, corporate NAT, datacenter-like egress), invalidating session cookies after suspicious requests.
Proposed work
Acceptance criteria
Refs: #6