Close packaged claim spelling variants

[karlwaldman]

Problem

The v1.12.2 exact wheel scan discovered every readable file, but the claim vocabulary matched free tier only with a space and did not reject universal catalog wording. The shipped demo docstring therefore exposed free-tier and full commodity catalog variants after the otherwise green release.

Red / green

Red before implementation:

• the future installed .pyi regression failed to match hyphenated free-tier wording
• the same regression failed to identify full commodity catalog and all latest prices
• expanding the guard exposed three more universal variants in current docs/package source
• the release-readiness test failed because the local wheel smoke selected the first wheel in dist instead of the exact project version

Green at f4b1b96:

• release unit suite: 416 passed, 13 skipped, 62.26% coverage
• focused claim/release/telemetry tests: 17 passed
• authored/generated scan: 63 readable surfaces
• Ruff and mypy: green, 46 source files
• exact built 1.12.3 wheel: clean install, pip check, recursive RECORD-derived claim scan, and production demo smoke green
• git diff check: clean

Change

• match space and hyphen variants of free-tier/free-api-key wording
• reject universal price/commodity catalog claims
• replace remaining package/doc variants with current-account and runtime-response terminology
• bind the clean wheel smoke to the exact versioned wheel name
• release as 1.12.3; v1.12.2 remains immutable and superseded

No runtime request behavior, entitlement, credential, email, or customer mutation is included.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 30 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: 7e759c8d-856d-4d1f-86dd-d6a96e58ece5

📥 Commits

Reviewing files that changed from the base of the PR and between 4e7e8ec and f4b1b96.

📒 Files selected for processing (16)

• CHANGELOG.md
• EXAMPLES.md
• docs/DATAFRAMES.md
• docs/index.md
• oilpriceapi/async_client.py
• oilpriceapi/resources/bunker_fuels.py
• oilpriceapi/resources/commodities.py
• oilpriceapi/resources/data_quality.py
• oilpriceapi/resources/demo.py
• oilpriceapi/resources/prices.py
• oilpriceapi/version.py
• pyproject.toml
• scripts/clean-wheel-smoke.sh
• 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.}