Add chargepoint domain skill: Datadome blocks password login, use coulomb_sess cookie

[garyo]

ChargePoint fronts login with Datadome bot protection, so server-side password logins (e.g. the Home Assistant chargepoint integration's reauth flow) fail even with correct credentials. The reliable path is the coulomb_sess cookie from a logged-in browser session at driver.chargepoint.com — this skill documents the cookie, how to grab it via Storage.getCookies, and the trap in the HA reauth dialog.

Field-tested today while re-authenticating the HA chargepoint integration after an upgrade.

🤖 Generated with Claude Code

---

Summary by cubic

Add a ChargePoint auth guide: Datadome blocks server-side password logins; use the coulomb_sess cookie from driver.chargepoint.com. Includes a Storage.getCookies snippet, the auth-session SSO JWT fallback when coulomb_sess is missing, and to use the token field (not password) in Home Assistant chargepoint reauth.

^{Written for commit 240ec04. Summary will update on new commits.}

[browser-harness-review]

✅ Skill review passed

Reviewed 1 file(s) — no findings.

[cubic-dev-ai]

All reported issues were addressed across 1 file

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[garyo]

Both points addressed in cb5b766's follow-up: the snippet now uses next(..., None) with an explicit missing-cookie path, and the doc notes that auth-session works via login_with_sso_session() (verified against python-chargepoint's client.py) rather than implying coulomb_sess is the only accepted token.