feat(enterprise): bind calibration bundles to shared reports

[seonghobae]

Summary

• add fit_enterprise_issue_facets_calibration_reports() as the smallest post-feat(enterprise): assemble governed calibration bundles #543 issue Implement decision-conditional enterprise issue intelligence vertical #404 slice
• validate report identities and review triggers before replay, assemble the accepted enterprise calibration bundle, and delegate every criterion fit to the canonical shared Rust-backed report boundary
• return the existing shared report objects with exact bundle/design fingerprints and explicit criterion separation
• add complete delegation, validation-order, generator-safety, public-docstring, documentation, doctoring, and changelog coverage

Scientific and product boundary

This PR adds no enterprise-specific estimator, report schema, cross-criterion aggregation, model selection, fairness claim, ranking, utility arithmetic, causal claim, or automated action queue. A successful report establishes provenance and fit-output integrity only.

Advances #404.

[coderabbitai]

Warning

Review limit reached

@github-actions[bot], you've reached your PR review limit, so we couldn't start this review.

Next review available in: 3 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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: c9e72c02-3740-4f41-978e-b47fa339248a

📥 Commits

Reviewing files that changed from the base of the PR and between 84f3251 and c24adb5.

📒 Files selected for processing (8)

• .github/workflows/render-pr-545-changelog.yml
• CHANGELOG.md
• docs/changelog.d/enterprise-issue-calibration-reports.md
• docs/doctoring/enterprise-issue-facets-calibration-reports.md
• docs/enterprise_issue_facets_calibration_reports.md
• python/fast_mlsirm/scoring/enterprise_issue/__init__.py
• python/fast_mlsirm/scoring/enterprise_issue/calibration_reporting.py
• tests/test_scoring_enterprise_issue_calibration_reporting.py

---

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

[seonghobae]

Closing as superseded by #546. Both branches implement the same enterprise issue calibration-report orchestration from the same base, but #546 carries the more complete accepted #544/#404 contract: caller metadata governance and reserved-key rejection, exact bundle/design/criterion provenance, execution-order invariance, realistic Rust-backed integration, compatibility assertions, APA 7 doctoring, and explicit privacy evidence. Keeping both open would create competing module names and overlapping public exports. No commits from this branch are being merged independently.