Skip to content

feat(validation): add paired rating-range evidence on current main - #748

Merged
seonghobae merged 1 commit into
mainfrom
feat/essay-range-compression-evidence-main
Aug 11, 2026
Merged

feat(validation): add paired rating-range evidence on current main#748
seonghobae merged 1 commit into
mainfrom
feat/essay-range-compression-evidence-main

Conversation

@seonghobae

Copy link
Copy Markdown
Contributor

Why

Advances #579 / essay range compression. Stale long stack; surgical re-apply onto protected main.

What

  • Rust core rating_range module with hand-calculated recovery contracts
  • PyO3 binding module + Python paired_rating_range_evidence API
  • Bound onto historical validation namespace without duplicating arithmetic
  • Doctoring + changelog (APA 7th)

Verification

  • Rust rating_range_evidence tests: 3 passed
  • Product gates: python+rust+package+fuzz

Supersedes draft #579 once green.

Rust-owned diagnostic for automated vs reference rating category endpoints,
span, dispersion, and relative compression. Surgical re-application onto
protected main without dropping judge/IRT/inference modules.
@coderabbitai

coderabbitai Bot commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

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

Next review available in: 15 minutes

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: 0d42a3b3-de57-4b0e-9d8f-7dfb2a336ecb

📥 Commits

Reviewing files that changed from the base of the PR and between cd9e55f and 43b1f5f.

📒 Files selected for processing (15)
  • CHANGELOG.md
  • crates/fast-mlsirm-py/src/entrypoint.rs
  • crates/fast-mlsirm-py/src/rating_range_bindings.rs
  • crates/mlsirm-core/src/lib.rs
  • crates/mlsirm-core/src/rating_range.rs
  • crates/mlsirm-core/tests/rating_range_evidence.rs
  • docs/changelog.d/397-paired-rating-range-evidence.md
  • docs/doctoring/paired-rating-range-evidence.md
  • docs/superpowers/plans/2026-08-09-paired-rating-range-evidence.md
  • docs/superpowers/specs/2026-08-09-paired-rating-range-evidence-design.md
  • python/fast_mlsirm/__init__.py
  • python/fast_mlsirm/_rating_range_core_loader.py
  • python/fast_mlsirm/rating_range.py
  • tests/test_paired_rating_range_delegation.py
  • tests/test_paired_rating_range_evidence.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

Comment @coderabbitai help to get the list of available commands.

@seonghobae
seonghobae merged commit 8a56d7b into main Aug 11, 2026
34 checks passed
@seonghobae
seonghobae deleted the feat/essay-range-compression-evidence-main branch August 11, 2026 17:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant