Store geo on ticket at creation, drop GeoLite reads

Shipped

April 25, 2026 at 11:25 PM UTC

Author

Kamo

Commit

10f70de

**************** now captures the visitor's geo once (via GeoLookupService) and persists ip/country/city/subdivision on the SupportTicket itself. SupportTicketService.toDTO reads geo straight off the ticket — no live GeoLite range scan, no visitor-table fallback for geo (visitor is still loaded for the latest displayName, in bulk for the list endpoint). Legacy tickets without the snapshot fall back to visitor.countryCode.