fix(main): restore commercial hardening reverted by Sentinel

[seonghobae]

Why

Commit 4e57585 (Sentinel: Fix release_acceptance test failing due to import error) fixed a ModuleNotFoundError but also reverted several already-merged commercial-hardening slices:

• BIFAC2PLM + JMLE fail-closed at FitConfig.validate (test(config): reject unsupported bifactor estimator pairing #702)
• MMLE fail-closed when the compiled Rust core is absent (fix(mmle): fail closed when Rust core is unavailable #642)
• requires-python >=3.12 floor matching the CI matrix (fix(ci): align requires-python floor with installable CI lock #703)
• Git metadata timeouts on evidence builders (fix(reliability): bound Git metadata lookups in evidence builders #704)
• Related contract tests and changelog fragments

What

Restores those contracts on current main while keeping a resilient _bounded_json import path for scripts/release_acceptance.py.

Verification

• Pure-Python restored suite: model/estimator compatibility, git-metadata timeouts, CI Python floor contract, release_acceptance deadline loader
• Product CI: python + rust + package + fuzz required for merge

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 11 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: 60b574d1-505e-4256-9097-d81d6d0638a9

📥 Commits

Reviewing files that changed from the base of the PR and between 56967de and bbb592e.

📒 Files selected for processing (26)

• AGENTS.md
• CHANGELOG.md
• docs/changelog.d/bounded-json-loads.md
• docs/changelog.d/git-metadata-timeouts.md
• docs/changelog.d/python-312-floor.md
• pyproject.toml
• python/fast_mlsirm/config.py
• python/fast_mlsirm/fit.py
• scripts/build_benchmark_report.py
• scripts/build_buyer_packet.py
• scripts/build_commercial_release.py
• scripts/build_figma_evidence_sync.py
• scripts/build_procurement_due_diligence.py
• scripts/release_acceptance.py
• tests/test_benchmark_git_metadata_timeout.py
• tests/test_buyer_packet_git_metadata_timeout.py
• tests/test_ci_python_314_contract.py
• tests/test_commercial_release_git_metadata_timeout.py
• tests/test_cov_f_fit.py
• tests/test_figma_evidence_git_metadata_timeout.py
• tests/test_mmle_eap_projection_contract.py
• tests/test_mmle_rust_fail_closed.py
• tests/test_model_estimator_compatibility.py
• tests/test_paper_features.py
• tests/test_procurement_git_metadata_timeout.py
• tests/test_release_acceptance_subprocess_deadlines.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.}