🛡️ Sentinel: [MEDIUM] Fix Information Exposure via RPC Errors

[DerUntote]

🚨 Severity: MEDIUM
💡 Vulnerability: The application was passing unhandled RPC connection errors directly to users via Discord messages (message.reply(err.message)).
🎯 Impact: This could leak internal daemon/network information or server configurations if an attacker forced an error state or an unexpected network exception occurred.
🔧 Fix: Avoided passing raw err.message objects from backend/RPC providers to untrusted clients. Catch and log the detailed errors internally (console.error(err)), and provide a safe, generic fallback message to the user ("An error occurred during the transaction. Please try again later."). Added .catch to message deletions to prevent unhandled rejections.
✅ Verification: Verified via node -c syntax checks across all modified modules. Formatted via prettier.

---

PR created automatically by Jules for task 11521431954617770280 started by @DerUntote

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