Stop forwarding IP headers to Convex ingest-chat endpoint

Forwarding cf-connecting-ip (and possibly x-forwarded-for) from the
browser request to Convex causes Cloudflare to return 403 when the
staging server sits behind Cloudflare (staging.mcpjam.com) — the
forwarded cf-connecting-ip mismatches the actual connecting IP
(Railway server), triggering Cloudflare's WAF. PR previews on
*.up.railway.app work because they don't go through Cloudflare, so
no cf-connecting-ip header exists to forward.

Keep forwarding user-agent and accept-language for device/language
enrichment. The removed IP headers were only used for chatbox visitor
hashing, which can rely on Cloudflare's own cf-connecting-ip on the
Convex side.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: chelojimenez

mcpjam-inspector/server/utils/chat-ingestion.ts

@@ -12,10 +12,6 @@ const MAX_RESPONSE_PREVIEW_CHARS = 200;
 const ENRICHMENT_HEADERS_TO_FORWARD = [
   "user-agent",
   "accept-language",
-  // Client IP headers for visitor hashing
-  "x-forwarded-for",
-  "x-real-ip",
-  "cf-connecting-ip",
 ] as const;
 
 /**