Evite via curl (no MCP)

Evite has no public API — this hits the site's own internal /services/ (+ /ajax/, /tsunami/) layer using session cookies, exactly like evite-mcp does. This is a curl skill, not fpx: Evite's login is a plain CSRF-protected Django form POST, and reads/writes with the resulting cookies are not bot-walled (Cloudflare sits in front but doesn't trip on a plain curl/Node request carrying a valid session) — so the whole flow runs server-side with a cookie jar. No signed-in browser tab, no Transporter extension, no bridge.

Auth model: session cookies x-evite-session + evtsession, plus a CSRF cookie csrftoken sent back as the X-CSRFToken header on every write. The CSRF cookie rotates — re-read it from the jar immediately before each write, never cache it.

One-time login (per shell session, until the jar's session expires)