perf(campaign): eliminate O(N*M) bottleneck in edge case detection analysis

[theRebelliousNerd]

This commit solves a critical performance vector inside internal/campaign/edge_case_detector.go.

Previously, AnalyzeFiles iterated over N files, invoking queryDependencies and queryComplexity which each fired a broad d.kernel.Query (M facts). This resulted in an O(N * M) explosion in runtime and GC allocations on large repositories.

Changes:

1. Fact Caching: Extracted kernel.Query into an upfront, single evaluation fetching all target facts into a lightweight kernelFacts cache array before any evaluation takes place.
2. Parallelized Execution: AnalyzeFiles now evaluates paths concurrently using a sync.WaitGroup and buffered semaphore (cap: 8 workers) to maximize CPU utilization without memory starvation.
3. Safety & Correctness: Channel results are gracefully collected and sorted. Additional fixes include context timeout adjustments for zero-length slices.

Passes all integration, boundary, and unit tests cleanly.

---

PR created automatically by Jules for task 3185583868423924107 started by @theRebelliousNerd

[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

Rate limit exceeded

@theRebelliousNerd has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 47 minutes and 1 second before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 0b584d99-af93-464c-abf5-94f6a781cb13

📥 Commits

Reviewing files that changed from the base of the PR and between cc0e10f and ce20787.

📒 Files selected for processing (3)

• fix_test.py
• internal/campaign/edge_case_detector.go
• plan.txt

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix-campaign-analysis-performance-3185583868423924107

---

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 and usage tips.}