GH#17808: add CI nesting threshold proximity guard to pulse complexity scan#17822
Conversation
Adds _check_ci_nesting_threshold_proximity() to run_weekly_complexity_scan in pulse-wrapper.sh. When the nesting depth violation count is within 5 of the CI threshold, the pulse creates a warning issue before PRs start failing. The CI Complexity Analysis check failed 6 times in a short window (GH#17808) because new scripts pushed the global nesting depth count over the threshold. The threshold was bumped reactively each time. This guard detects proximity proactively so maintainers can reduce nesting or bump the threshold before the next PR fails. Also documents the proximity guard in complexity-thresholds.conf. Resolves #17808
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
Important Review skippedAuto reviews are limited based on label configuration. 🚫 Review skipped — only excluded labels are configured. (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Completion Summary
|
🔍 Code Quality Report�[0;35m[MONITOR]�[0m Code Review Monitoring Report SonarCloud: 0 bugs, 0 vulnerabilities, 647 code smells Wed Apr 8 04:38:32 UTC 2026: Code review monitoring started 📈 Current Quality Metrics
Generated on: Wed Apr 8 04:38:35 UTC 2026 Generated by AI DevOps Framework Code Review Monitoring |
Up to standards ✅🟢 Issues
|
|
Completion Summary
Merged via PR #17822 to main.
|



Summary
Adds a proactive regression guard to the pulse complexity scan that warns before the CI nesting depth threshold is exceeded.
Root cause (GH#17808)
The
Complexity AnalysisCI check failed 6 times in a short window because new scripts pushed the global nesting depth violation count over the threshold (278→279). Each time, the fix was reactive: bump the threshold after PRs started failing. The systemic fix (threshold bump to 279) was already applied to main in commitd531c1d6e.What this PR adds
_check_ci_nesting_threshold_proximity()inpulse-wrapper.sh:.agents/configs/complexity-thresholds.confrun_weekly_complexity_scanindependently of tree-change detection (runs even when no files changed).agents/configs/complexity-thresholds.conf: Documents the proximity guard so maintainers know to bump the threshold with a rationale comment.Files changed
.agents/scripts/pulse-wrapper.sh— new_check_ci_nesting_threshold_proximity()function + call site inrun_weekly_complexity_scan.agents/configs/complexity-thresholds.conf— documents the proximity guardRuntime testing
|| true)Runtime Testing
Resolves #17808
aidevops.sh v3.6.170 plugin for Claude Code spent 10m on this as a headless worker.