feat(scoring): persist PostgreSQL version-pinned request identity

[seonghobae]

Why

ROADMAP Continuous rank 1 is the unfinished participant journey. Open persist PRs occupy snapshots (#55), events (#53), results (#51), and session bind (#47). Version-pinned ScoringRequest identity still exists only in memory, so a completed snapshot cannot be dispatched after process restart.

What

• migrations/0011_scoring_request.sql for immutable scoring_request
• src/postgres_scoring_request.rs persists a domain ScoringRequest under READ COMMITTED
• Exact replay, fail-closed rebinding of session, snapshot, spec, instrument, scoring version, calibration, norm, or schema
• TRACEABILITY/CHANGELOG updated. Live fast-mlsirm execution and HTTP remain Target.

Does not overlap #55 (response snapshots), #51 (result snapshots), or #43 (digest validation). Does not recreate fast-mlsirm kernels.

Test plan

• TEST_DATABASE_URL persistence + error-contract tests
• cargo clippy --all-targets -- -D warnings
• cargo llvm-cov lines 3642/3642; nightly --branch 562/562
• Exact-head required Checks after open

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 4 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: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 92b9e491-a54b-4640-96fd-b9035fd550da

📥 Commits

Reviewing files that changed from the base of the PR and between ed6da43 and cfc742c.

📒 Files selected for processing (7)

• CHANGELOG.md
• docs/TRACEABILITY.md
• migrations/0011_scoring_request.sql
• src/lib.rs
• src/postgres_scoring_request.rs
• tests/postgres_scoring_request_error_contract.rs
• tests/postgres_scoring_request_persistence.rs

---

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