feat: ship fact-grounded read-only Gemini extension 2.0

[karlwaldman]

Summary

• pin oilpriceapi-mcp@3.0.0 in read-only scope with a bounded 15-second MCP timeout
• declare OILPRICEAPI_KEY as a sensitive Gemini extension setting with keyless fallback
• replace stale tool names and broad claims with current MCP tools, reviewed product-facts grounding, source timestamps, entitlement boundaries, and explicit recovery
• distinguish connected-session grounding from Gemini Search and pretrained model knowledge
• add official Gemini validation, isolated clean-install smoke, protocol tests, CI, and dependency audit coverage

Verification

• 11/11 manifest and MCP protocol tests pass
• discovery: 25 read tools, zero mutation tools
• product facts and keyless current price pass
• authenticated current price passes with source timestamp
• missing/invalid key, locked dataset, rate limit, timeout, and malformed upstream paths pass
• child diagnostics contain no test keys or customer identifiers
• gemini extensions validate . passes on Gemini CLI 0.49.0
• isolated install and extension listing pass
• npm audit: zero vulnerabilities

Release

After merge, tag/release v2.0.0 and add the gemini-cli-extension repository topic for the official gallery crawler.

Closes #4

[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

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: 46177f98-b0ed-4939-9570-c3ec1193ae9b

📥 Commits

Reviewing files that changed from the base of the PR and between 833e43d and b8d8342.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (10)

• .github/workflows/ci.yml
• .gitignore
• GEMINI.md
• LICENSE
• README.md
• gemini-extension.json
• package.json
• scripts/clean-install-smoke.mjs
• tests/manifest.test.mjs
• tests/protocol.test.mjs

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/gemini-grounded-extension-20260719

---

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