🗲 [Code health] Fix DYNAMIC_SERVER_USAGE build errors on API routes

[thies2005]

🎯 What: Fixed Next.js build failures occurring during Coolify deployments.
💡 Why: Several API routes (/api/health/*, /api/reminders/settings, etc.) were failing during next build with a DYNAMIC_SERVER_USAGE error because they used dynamic functions (like reading request headers or getServerSession) without explicitly being marked as dynamic routes.
✅ Verification: Ran npm run build in the Web/ directory, and the build now succeeds without the errors.
✨ Result: Coolify deployment and Next.js builds should now successfully complete.

---

PR created automatically by Jules for task 11056222579744982428 started by @thies2005

[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.

[coolify-thies]

The preview deployment for thies2005/-run-flow:coolify-kdovuoolli28z74ieumh5dhf failed. 🔴

Open Build Logs | Open Application Logs

Last updated at: 2026-03-21 15:05:20 CET