🛡️ Sentinel: [CRITICAL/HIGH] Fix internal error leakage in RPC replies

[DerUntote]

🚨 Severity: HIGH
💡 Vulnerability: Internal RPC error messages (e.g. from bitcoind-rpc) were being exposed directly to users via message.reply(err.message) when a transaction failed.
🎯 Impact: This could leak sensitive internal information, including network details, specific failure reasons, or connection paths, which an attacker might use for reconnaissance.
🔧 Fix: Replaced message.reply(err.message) with console.error(err); message.reply('An internal error occurred. Please try again later.') across all tipbot modules. This logs the error internally for debugging but returns a generic error message to the user.
✅ Verification: Ran git diff to verify the replacements and node -c on all modified files to ensure no syntax errors were introduced. Checked the formatting of .jules/sentinel.md journal entry.

---

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