⚡ Bolt: Optimize sequential code retrieval loops with asyncio.gather

[ishaanxgupta]

💡 What: Refactored the sequential for r in self.repos loops in CodeRetrievalPipeline._search_symbols and _search_files to execute multiple _search_namespace coroutines concurrently using asyncio.gather. The result lists from gather are then flattened and aggregated.

🎯 Why: The previous implementation performed network I/O sequential queries, introducing unnecessary bottlenecks that delayed semantic search responses linearly to the number of tracked repositories.

📊 Measured Improvement: Benchmarked the two functions executing 5 repository namespace searches over a simulated network IO of ~0.10s each. Before changes, the execution time was ~0.5028s sequentially. After changes, execution drops to ~0.1010s representing roughly an 80% decrease in overall latency (O(1) execution time compared to O(N)).

---

PR created automatically by Jules for task 11938463061346092003 started by @ishaanxgupta

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