fix: republish source-aware Kaggle notebooks

[karlwaldman]

Summary

• replace stale notebook code and claims with deterministic source-aware notebooks pinned to oilpriceapi[pandas]==1.10.2
• fail closed on missing secrets, auth/entitlement/rate-limit/timeout, empty, malformed, or timezone-less data
• display execution time, exact API timestamp field, source, symbol, currency, unit, freshness, method, and limitations
• add exact-cell fixture execution, output/claim validation, secret scanning, and Kaggle CLI packaging to CI

Verification

• ./scripts/scan-secrets.sh
• python3 -m unittest discover -s tests -v (5 tests; exact cells executed)
• python3 scripts/generate_notebooks.py (clean worktree after regeneration)
• python3 scripts/package_kaggle.py
• python3 -m compileall -q scripts tests
• ruff check scripts tests
• ruff format --check scripts tests
• jq empty on both notebooks

Publication status

The repository artifacts are ready. Public Kaggle republishing and an attached non-customer OILPRICEAPI_KEY require private Kaggle credentials and remain tracked in #8; this PR intentionally does not claim that external publication is complete.

Refs #8

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 43 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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

Run ID: 67cfbb9f-60ad-4cf6-a99d-1457633c9013

📥 Commits

Reviewing files that changed from the base of the PR and between 4daa738 and aab67f2.

📒 Files selected for processing (12)

• .github/workflows/validate.yml
• .gitignore
• 01_wti_brent_spread_analysis.ipynb
• 02_oil_price_technical_analysis.ipynb
• KAGGLE_SETUP_COMPLETE.md
• KNOWN_ISSUES.md
• README.md
• notebook-1-fixed.md
• scripts/generate_notebooks.py
• scripts/notebook_support.py
• scripts/package_kaggle.py
• tests/test_notebooks.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/p1-source-accuracy-kaggle

---

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