feat(judge): default to adaptive contextual orchestration

[seonghobae]

Summary

• change ContextualOrchestratorJudge from a forced single-worker route default to contextual-orchestrator auto;
• preserve explicit route/conduct overrides for controlled ablation and rollback;
• add a regression that proves the default mode sent to the injected orchestration boundary;
• document the quality-first, cost-aware ownership split in an ADR and CHANGELOG.

The branch workflow stages the regression before production changes, proves the red/green transition when the implementation is not already present, runs the complete Python and Rust suites, checks the patch, removes its temporary mutation workflow, and publishes only the verified source commit.

Disposition: closed unmerged

Fresh exact-scope inspection found that this branch contains only temporary branch-writing workflows and mutation scripts, including workflows with contents: write that commit and push generated source changes back to agent/adaptive-orchestrator-default. That is a competing/self-modifying writer rather than the bounded product implementation required by repository coordination policy.

The intended product change is already owned by PR #931, which directly changes python/fast_mlsirm/llm_judge.py, its executable tests, ADR, and changelog and is intentionally Draft while its live contextual-orchestrator compatibility boundary is reconciled with #816. Preserve the adaptive auto default intent in #931; do not recreate a branch-writing mutation workflow for the same source lane.

No source or protected gate is weakened by closing this PR.

[coderabbitai]

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 26 minutes

Limit details: You’ve used all 1 included review currently available under your plan.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

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

How do review limits work?

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

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 3645013d-a739-454b-b661-f53b95bf8754

📥 Commits

Reviewing files that changed from the base of the PR and between fb67ced and b4f6443.

📒 Files selected for processing (5)

• .github/workflows/apply-adaptive-judge-default.yml
• .github/workflows/apply-adaptive-orchestrator-default.yml
• scripts/apply_adaptive_judge_default.py
• scripts/apply_adaptive_orchestrator_default.py
• scripts/stage_adaptive_judge_default_test.py

---

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