🔒 Fix missing authorization on WordPress Proxy Endpoints

[google-labs-jules]

🎯 What: The vulnerability fixed
The Express backend proxy routes for WordPress (/api/wp/:type and /api/wp/:type/:id) were completely unprotected. Any user with network access to the Node.js server could send requests to these endpoints, which would then be forwarded to the WordPress API using the hardcoded WP_AUTH credentials.

⚠️ Risk: The potential impact if left unfixed
An attacker could bypass the intended frontend UI and directly query the /api/wp/posts (or other) endpoints to create, modify, or delete WordPress content, settings, and media. This could lead to a complete takeover of the site's content.

🛡️ Solution: How the fix addresses the vulnerability
We implemented HTTP Basic Authentication using the express-basic-auth middleware for all routes under /api. This ensures that only authenticated users (who possess the DASHBOARD_USER and DASHBOARD_PASSWORD from the .env file) can access the WordPress proxy and AI generation endpoints. The configuration uses challenge: true to seamlessly integrate with browser prompts. Furthermore, the server now enforces a "fail-closed" mechanism, exiting immediately with a fatal error if these environment variables are missing, preventing the application from starting in an insecure state.

---

PR created automatically by Jules for task 4622422656671740935 started by @instituto-ops

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