⚡ Bolt: Concurrent External Requests in Contact Worker

[Snigdh41]

💡 What

Updated the Cloudflare Worker in contact-api to execute independent resend.emails.send API calls concurrently using Promise.all() instead of sequentially. Fixed a pre-existing linting issue where an <a> tag was used instead of Next.js <Link> for internal routing.

🎯 Why

Sequential network requests inside the Cloudflare Worker accumulate latency (e.g., waiting for the notification email to send before starting the auto-reply request). This inflates the worker's total execution time and slows down the client's API response.

📊 Impact

Reduces the external request phase latency by approximately 50%, depending on the Resend API response times.

🔬 Measurement

Deploy the worker to the development environment and measure the /contact endpoint response time using cURL or network dev tools. The duration will reflect the latency of the single slowest external request rather than the sum of both.

---

PR created automatically by Jules for task 11551017041103847775 started by @Snigdh41

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.