Fix email verification using Resend API instead of SMTP

[railway-app]

Problem

Email verification was failing with ETIMEDOUT errors because Railway's Singapore region cannot reliably reach smtp.resend.com on port 587. The Nodemailer SMTP transport was the primary delivery path, and the existing partial Resend fallback still used a raw fetch call rather than the official SDK.

Solution

Replaced Nodemailer SMTP entirely with the resend npm SDK (resend@^4.0.0). The resendClient is initialised once at startup with comprehensive logging (ready state, sender address, init errors). sendVerificationEmail now uses resendClient.emails.send() exclusively, logging the recipient, elapsed time, Resend message ID on success, and full error details on failure. isEmailConfigured() now checks only RESEND_API_KEY. The old SMTP_HOST/PORT/USER/PASS/SECURE constants and SmtpNotConfiguredError class are removed; route handlers now reference the new EmailNotConfiguredError. SMTP_FROM is retained as the sender address env var for backward compatibility.

Changes

• Modified package.json
• Modified server.js

---

Generated by Railway