⚡ Bolt: Resolve N+1 query bottleneck in grievance evaluation

[RohanExploit]

⚡ Bolt Performance Optimization

💡 What: Added joinedload(Grievance.jurisdiction) to the _get_grievances_for_evaluation method in backend/escalation_engine.py.
🎯 Why: During periodic grievance evaluation, iterating over active grievances and accessing grievance.jurisdiction.level was causing an N+1 query problem, severely degrading performance as the number of open grievances grows.
📊 Impact: Reduces the number of database queries during escalation evaluation from O(N) to O(1) by eagerly fetching related jurisdiction data in a single SQL JOIN.
🔬 Measurement: Verified that tests pass. Memory and execution time during high-volume scheduled evaluation sweeps will drop significantly.

Also documented this finding in .jules/bolt.md.

---

PR created automatically by Jules for task 12810709853448038691 started by @RohanExploit

---

Summary by cubic

Eager-load Grievance.jurisdiction in periodic evaluation to remove N+1 queries when reading jurisdiction.level, cutting DB calls from O(N) to O(1) and speeding up SLA sweeps. Added a note in .jules/bolt.md to document this pattern for future periodic jobs.

^{Written for commit 7a751c5. Summary will update on new commits.}

Summary by CodeRabbit

• Performance
  • Improved background escalation evaluations by loading related jurisdiction data more efficiently.
  • Reduced unnecessary database queries during periodic grievance processing.

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

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[github-actions]

🙏 Thank you for your contribution, @RohanExploit!

PR Details:

• Title: ⚡ Bolt: Resolve N+1 query bottleneck in grievance evaluation
• Number: ⚡ Bolt: Resolve N+1 query bottleneck in grievance evaluation #929

Quality Checklist:
Please ensure your PR meets the following criteria:

• Code follows the project's style guidelines
• Self-review of code completed
• Code is commented where necessary
• Documentation updated (if applicable)
• No new warnings generated
• Tests added/updated (if applicable)
• All tests passing locally
• No breaking changes to existing functionality

Review Process:

1. Automated checks will run on your code
2. A maintainer will review your changes
3. Address any requested changes promptly
4. Once approved, your PR will be merged! 🎉

Note: The maintainers will monitor code quality and ensure the overall project flow isn't broken.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: f6e81d6b-399c-486a-9a74-f6d1f79666fc

📥 Commits

Reviewing files that changed from the base of the PR and between 3a74e60 and 7a751c5.

📒 Files selected for processing (2)

• .jules/bolt.md
• backend/escalation_engine.py

---

📝 Walkthrough

Walkthrough

The escalation evaluation query now eagerly loads each grievance’s jurisdiction using SQLAlchemy joinedload. A dated .jules/bolt.md entry documents the N+1 query issue and recommends eager loading.

Changes

Escalation Query Loading

Layer / File(s)	Summary
Eager-load grievance jurisdictions backend/escalation_engine.py, .jules/bolt.md	The grievance evaluation query applies joinedload(Grievance.jurisdiction), and the new dated guidance documents eager loading for periodic jobs.

Estimated code review effort: 2 (Simple) | ~5 minutes

Possibly related PRs

• RohanExploit/VishwaGuru#913: Applies the same eager-loading change and documentation update.
• RohanExploit/VishwaGuru#915: Adds joinedload to the same grievance evaluation query.
• RohanExploit/VishwaGuru#918: Contains the same Grievance.jurisdiction eager-loading fix and related documentation.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the main change: fixing an N+1 query bottleneck in grievance evaluation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch bolt-fix-n1-query-12810709853448038691

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[cubic-dev-ai]

No issues found across 2 files

_{Re-trigger cubic}

[RohanExploit]

Closing as duplicate of #938, which covers the same N+1 fix in the escalation engine.

[google-labs-jules]

Closing as duplicate of #938, which covers the same N+1 fix in the escalation engine.

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