fix: ensure process exits on uncaught exceptions in src/index.js

[shenald-dev]

Swallowing uncaught exceptions in Node.js leaves the application running in an unpredictable state, which can lead to memory leaks, socket hangs, and corrupted memory. The best practice is to log the error and crash cleanly (process.exit(1)) so a process manager (like PM2 or Docker) can restart the service safely.

This PR addresses this reliability flaw in src/index.js to ensure the One API gateway runs safely and predictably. It also includes an update to the .jules/bolt.md journal.

---

PR created automatically by Jules for task 15671142665141955370 started by @shenald-dev

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