Fix Gemini access and add Real World Reasoning Lab - #154
Merged
Conversation
ryanbaumann
marked this pull request as ready for review
July 27, 2026 20:02
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Root cause
Hairstyle applied its shared limiter before credential selection, so a personal key could still be blocked by shared quota. The imported reasoning demo also carried standalone gateway, analytics, and cost assumptions that needed Fieldwork-native controls.
Security and cost controls
docs/LABS_SECURITY.mdGMP_MCP_KEYbefore settingRWR_GROUNDING_LITE_ENABLED=trueValidation
npm audit: zero vulnerabilitiesNo live or paid provider calls were made during validation. The in-memory daily controls reset on restart, so the documented Google Cloud/Gemini per-API quotas remain the hard distributed cost backstop.