🛡️ Sentinel: [CRITICAL] Fix Werkzeug interactive debugger exposure

[benpiper]

🚨 Severity: CRITICAL
💡 Vulnerability: The Flask app was binding to 0.0.0.0 with debug=True, exposing the Werkzeug interactive debugger to all interfaces and allowing potential Remote Code Execution (RCE).
🎯 Impact: Attackers could execute arbitrary Python code on the server if they caused an error or accessed the debugger endpoint.
🔧 Fix: Disabled debug mode (debug=False) when binding to 0.0.0.0 in web_app/app.py and web_app/run.py. Added security comments.
✅ Verification: Ensure the app runs without exposing the debugger by running uv run pytest and verifying the code.

---

PR created automatically by Jules for task 12645761433155914064 started by @benpiper

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