fix: reject mutable daily allowance claims

[karlwaldman]

Summary

• remove the exact 50 requests/day exception from the public/package claim guard
• replace the numeric allowance in EXAMPLES.md with the reviewed live Product Facts contract
• add a future installed JSON package-data regression for the stale daily allowance
• publish as 1.12.4 because 1.12.3 is already immutable on PyPI

Red-green proof

Red: the new installed-package-data assertion failed because 50 requests/day produced no fixed demo rate finding.

Green:

• 416 passed, 13 skipped; coverage 62.21%
• storefront fixture suite: 4 passed
• Ruff on source and changed guard/tests: green
• mypy on all 46 source files with the hosted configuration: green
• authored/generated scan: 63 readable surfaces
• exact 1.12.4 wheel clean install, pip check, recursive RECORD scan, version match, and production keyless demo: 34 unique rows / all 9 core usable

Release integrity

The smoke selects oilpriceapi-1.12.4-py3-none-any.whl exactly. Local artifact SHA-256 before hosted rebuild: 39f25304c6ff434d7ef9f730cfd185275c8e71b24486bdb7998978c49afd13d9. The public registry hash will be bound after trusted publishing.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 14 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: e3d3d759-4551-41c2-b1b3-0f60f3634bcd

📥 Commits

Reviewing files that changed from the base of the PR and between 82622d1 and 94da813.

📒 Files selected for processing (7)

• CHANGELOG.md
• EXAMPLES.md
• oilpriceapi/version.py
• pyproject.toml
• scripts/validate_storefront_claims.py
• tests/test_release_readiness.py
• tests/test_storefront_claims.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.}