⚡ Bolt: Replace BFS graph pathfinding with recursive CTEs

[Theory903]

💡 What: Replaced the application-level Breadth-First Search (BFS) pathfinding in find_relationship_path with a Recursive Common Table Expression (CTE) executed inside the database.
🎯 Why: The BFS approach issued a separate SQL query to fetch outgoing relations for each node visited during traversal, causing a severe N+1 query problem. This degraded performance exponentially in deep or highly branched graphs.
📊 Measured Improvement:

• Baseline (BFS): 0.120 seconds
• Improvement (CTE): 0.006 seconds
• Change over baseline: 20x faster by eliminating N+1 queries.
  🔬 Measurement: Using a heavily branched graph generation script with 7 depth levels and nested noise entities, benchmarked via test_perf.py.

---

PR created automatically by Jules for task 5010721220587838206 started by @Theory903

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

[coderabbitai]

Warning

Review limit reached

@Theory903, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 46 minutes and 10 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses rolling per-developer review limits. Reviews become available again as older review attempts age out of the rolling limit window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: eeb6c6f2-b41f-4857-9f67-58828bc294b0

📥 Commits

Reviewing files that changed from the base of the PR and between 29c13ba and d4cf65d.

📒 Files selected for processing (3)

• .jules/bolt.md
• infra/src/mnemosyne/graph/manager.py
• src/ippoc/mnemosyne/graph/manager.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch jules-5010721220587838206-a6900ad5

---

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