fix(prism): autonomous Lium rent pool with 429 requeue

[echobt]

Summary

• Add lium-rent-pool: serialize rents to Lium’s 3/5s + 60/hour caps, parse try again in N seconds, apply cooldown on HTTP 429.
• Wire pool into prism-lium rent path (no blind multi-retry on /rent that burns the hourly budget).
• Orchestrator requeues 429 failures without bumping retry_count / gating attempts; bin recovers failed 429 rows from the last 6h every 2 minutes and soft-opens gating.

Test plan

• cargo test -p lium-rent-pool -p prism-lium --lib
• cargo clippy on touched crates (-D warnings)
• cargo run -p xtask -- loc-cap / external-docs-check
• After deploy: confirm logs show lium rent pool waiting / lium 429 recovery tick, and prior 429 failed rows return to queued without burning retries

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 20 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: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 3ec0f7e3-ab5c-4717-9306-c85fc0634e72

📥 Commits

Reviewing files that changed from the base of the PR and between 901d9f0 and db15e23.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (14)

• bins/prism-challenge/Cargo.toml
• bins/prism-challenge/src/main.rs
• crates/db/src/prism_store.rs
• crates/lium-rent-pool/Cargo.toml
• crates/lium-rent-pool/src/lib.rs
• crates/prism-challenge/Cargo.toml
• crates/prism-challenge/src/api.rs
• crates/prism-challenge/src/orchestrator.rs
• crates/prism-emit/tests/epoch_semantics.rs
• crates/prism-lium/Cargo.toml
• crates/prism-lium/src/client.rs
• crates/prism-store/src/dbprism.rs
• crates/prism-store/src/store.rs
• docs/PRISM.md

---

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