🧹 Refactor long function route_event in personality.rs

[undivisible]

🎯 What: Extracted the hard rules and learned policy logic inside the long function route_event into separate private methods evaluate_hard_rules and evaluate_learned_policy.
💡 Why: route_event was previously heavily nested with hard-to-follow mutable state logic depending on !hard_rule_hit flag. Returning options instead makes control flow clear and the methods more readable and concise, improving maintainability.
✅ Verification: Verified by ensuring the cargo fmt, cargo clippy, and cargo test checks passed smoothly, meaning that behavior remained exactly the same as previously.
✨ Result: A more readable, robust and easily understandable route_event implementation.

---

PR created automatically by Jules for task 13386801703544256970 started by @undivisible

---

Note

Low Risk
Pure refactor of turn-routing control flow with identical decision logic and existing tests covering the same paths.

Overview
Simplifies route_event by extracting its nested hard-rule and learned-policy logic into two private helpers: evaluate_hard_rules and evaluate_learned_policy.

Replaces the mutable hard_rule_hit flag with early Option returns, so hard rules short-circuit cleanly and the learned policy runs only as a fallback. Behavior is unchanged.

^{Reviewed by Cursor Bugbot for commit e6e7eaa. Configure here.}

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

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_c890d259-a9f5-45a9-a646-1bd85f194f3d)

[undivisible]

Superseded by the reviewed and merged integration in #22.

[google-labs-jules]

Superseded by the reviewed and merged integration in #22.

Understood. Acknowledging that this work is now obsolete and stopping work on this task.