🧹 [Code Health] Fix EdgeCaseDetector Max File Size boundary limits

[theRebelliousNerd]

🎯 What: The code health issue concerning missing bounds checks and float64 precision/overflow issues for LineCount in EdgeCaseDetector was resolved.

💡 Why: By capping extremely large line counts internally (e.g., up to 1,000,000 rather than allowing values near math.MaxInt32), we prevent integer multiplication overflows and stop heuristic metrics (like Cyclomatic Complexity estimations) from ballooning. This improves edge case safety and reliability in large-scale codebase evaluations.

✅ Verification: Verified by checking out the new test TestEdgeCaseDetector_DetermineAction_ExtremeValues which ensures LineCount = math.MaxInt32 triggers ActionModularize properly and maintains bounded downstream complexity estimations without precision panics. Confirmed by running the complete codeNERD test suite safely.

✨ Result: Safe handling of extreme file size values for EdgeCase detection algorithms with full test coverage for the gap.

---

PR created automatically by Jules for task 18305077969538400693 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 44 minutes and 14 seconds 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: 6dcb6093-7059-4e00-8fe1-bdf50e792ee2

📥 Commits

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

📒 Files selected for processing (2)

• internal/campaign/edge_case_detector.go
• internal/campaign/edge_case_detector_test.go

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix-edge-case-detector-max-file-boundaries-18305077969538400693

---

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