test(cat): preserve selection input immutability on current main

[seonghobae]

Clean-lineage replacement for #749 / issue #629

Protected main advanced after #749 was created. Fresh compare proved #749 is now three protected-main commits behind and its only unique delta is tests/test_cat_selection_input_immutability.py. This PR recreates that exact verification slice directly on current protected main without transferring predecessor checks/reviews.

Exact identity

• protected base at creation: 8a56d7b1b024e18a5a96a94db4ede1bf6648ead1;
• exact source head: 52710bb5bdb1fd405fcc06cf04e51549da2951da;
• compare to protected main: direct one-commit descendant, ahead 1 / behind 0;
• changed path: tests/test_cat_selection_input_immutability.py only.

Verification contract

Exercise the installed Rust-backed public CAT item-information and next-item-selection paths and prove they do not mutate caller-owned theta, factor-map, or administered-item arrays. This changes no psychometric formula, ranking/selection policy, production source, dependency, workflow, provider, canonical documentation authority, version, or release state.

Acceptance

Require one unchanged exact head with full applicable Python 3.12/3.14 CI, Rust/PyO3/package/reinstall, existing GPU/fuzz where triggered, Security Scan, SAST and current-head review/governance evidence. Predecessor #749 checks/reviews do not transfer. Keep Draft until exact-current evidence is complete.

Once this clean replacement is established, close #749 as superseded with lineage preserved. Advances #629.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 3 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: 0fb20814-7ed2-43b9-a076-94a2e8df1d39

📥 Commits

Reviewing files that changed from the base of the PR and between 8a56d7b and 52710bb.

📒 Files selected for processing (1)

• tests/test_cat_selection_input_immutability.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.}