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

[benpiper]

🚨 Severity: CRITICAL
💡 Vulnerability: The Flask app is configured to run with debug=True while binding to host='0.0.0.0'. This exposes the Werkzeug interactive debugger publicly.
🎯 Impact: An attacker can exploit the exposed interactive debugger to execute arbitrary Python code on the server, leading to a full system compromise.
🔧 Fix: Changed debug=True to debug=False in app.run() calls inside web_app/app.py and web_app/run.py to disable the interactive debugger.
✅ Verification: Run uv run pytest to verify functionality.

---

PR created automatically by Jules for task 15645201364899716673 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.