🔒 Fix Flask debug mode vulnerability

[LebToki]

🎯 What: The Flask application presentapulse_flask.py was running with debug=True, which is a known vulnerability.
⚠️ Risk: Running Flask with debug enabled in a production or public-facing environment allows the interactive Werkzeug debugger to be exposed, which can lead to remote code execution and severe information leaks.
🛡️ Solution: The debug parameter in app.run() was changed from True to False to prevent the exposure of the debugger and remove the vulnerability.

Additionally, updated versions in VERSION, README.md, api_server.py, and added reader.md and revision.md according to project directives.

---

PR created automatically by Jules for task 8145257203787656550 started by @LebToki

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