feat: trading-rl-2 Wave 3 (liquidation-cascade, reward-misspecification track) + README refresh

[ReverseZoom2151]

Final wave of the trading-rl-2 scan — the remaining medium-value items, plus the README brought current to v0.4.0.

• Liquidation-cascade scenario — deterministic in-step margin_call -> forced_reduce -> cascade_impact chain (impact on liquidated notional, wipe-capable); terminated-on-wipe / truncated-on-survive; events feed the process-check/mandate machinery.
• Reward-misspecification negative-control track — deliberately-flawed rewards + proxy policies, with demonstrate_punishment showing the SharpeBench kernel refuses to reward them (raw-PnL proxy: highest raw return, deflated Sharpe 0.0). The falsifiable wedge. Never touches the production registry or rank key.
• README — capability table updated for the full 0.4.0 feature set; version bumped.

Verification: maturin + pytest 331 passed, 2 skipped. 118 exports. Pure Python, no Rust touched.

This exhausts the high+medium-value extractable backlog from both repo collections (trading-rl + trading-rl-2, 73 repos + 2 PDFs).

[coderabbitai]

Warning

Review limit reached

@ReverseZoom2151, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 19 minutes and 5 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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

🚦 How do rate 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 see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 69935d05-3b86-4613-99d7-913cf499e627

📥 Commits

Reviewing files that changed from the base of the PR and between b337196 and 840a17f.

📒 Files selected for processing (6)

• README.md
• crates/openoutcry-py/python/openoutcry/__init__.py
• crates/openoutcry-py/python/openoutcry/cascade.py
• crates/openoutcry-py/python/openoutcry/reward_misspecification.py
• crates/openoutcry-py/tests/test_cascade.py
• crates/openoutcry-py/tests/test_reward_misspecification.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch rl2-wave3

---

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