⚡ Bolt: Optimize reputation lookup in MemStorage with O(1) user ID map

[Pmaster-dev]

💡 What: Optimized getReputation(userId) in MemStorage by maintaining a secondary reputationsByUserId Map index.
🎯 Why: getReputation previously performed an O(N) linear array scan (Array.from(this.reputations.values()).find(...)) on every call, creating a performance bottleneck during frequent reputation and transaction checks.
📊 Impact: Reduces lookup complexity from O(N) to O(1) constant time, eliminating linear memory allocation overhead during reputation queries.
🔬 Measurement: Verified with pnpm tsx script and lint checks.

---

PR created automatically by Jules for task 288146119262644293 started by @Pmaster-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.