fix: align Gemini provider naming with backend database schema

[TheBluCoder]

The CLI was using 'geminiai' as the provider identifier, but the backend's llm_provider table uses 'google' for Gemini models. This mismatch caused validator creation to fail with 'Requested providers do not match any stored providers' error.

Changes:

• src/lib/config/simulator.ts (L26): Update AiProviders type definition from 'geminiai' to 'google'
• src/lib/config/simulator.ts (L50-L54): Update AI_PROVIDERS_CONFIG object key and cliOptionValue from 'geminiai' to 'google'

This ensures the CLI sends provider names that match the backend's database records, allowing successful validator initialization with Gemini models.

Resolves provider validation error during 'genlayer init' workflow.

Summary by CodeRabbit

• Chores
  • Updated AI provider naming convention from "geminiai" to "google" in configurations. Users referencing "geminiai" must update to "google" to maintain compatibility.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

The AI provider identifier is renamed from "geminiai" to "google" in the simulator configuration file. This updates the AiProviders type definition and the AI_PROVIDERS_CONFIG mapping while preserving all provider details including label, hint, and environment variable.

Changes

Cohort / File(s)	Summary
AI Provider Configuration src/lib/config/simulator.ts	Renamed provider key from geminiai to google in both the AiProviders type and AI_PROVIDERS_CONFIG mapping; updated cliOptionValue accordingly

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related issues

• Gemini provider initialization fails due to provider name mismatch (geminiai vs google) #271: Directly addresses the provider key rename from "geminiai" to "google" in the CLI simulator config, aligning the internal identifier with the provider's brand name.

Poem

A hop, a skip, and a rename so fine,
Gemini becomes Google in the config line,
The rabbit's done twitching the provider's name,
From geminiai to google, same magic, new frame! 🐰✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the main change: renaming the Gemini provider from 'geminiai' to 'google' to align with the backend database schema.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4229f98 and fba79e6.

📒 Files selected for processing (1)

• src/lib/config/simulator.ts

🧰 Additional context used

📓 Path-based instructions (1)

**/*.{ts,tsx,js,jsx}

📄 CodeRabbit inference engine (CLAUDE.md)

Use @/* path alias to reference ./src/* and @@/tests/* path alias to reference ./tests/* in imports

Files:

• src/lib/config/simulator.ts

🔇 Additional comments (2)

src/lib/config/simulator.ts (2)

50-54: LGTM! Config correctly updated to match backend schema.

The configuration object has been properly updated with the "google" key and cliOptionValue, while preserving the appropriate display name "Gemini" and environment variable "GEMINI_API_KEY". This change resolves the provider validation error during validator initialization.

---

26-26: The "geminiai" to "google" identifier migration is complete and correct.

No remaining references to "geminiai" exist in the codebase. The type definition change on line 26 is properly reflected in the configuration object (lines 50-54), with the correct cliOptionValue: "google" for backend alignment. The environment variable GEMINI_API_KEY appropriately remains unchanged.

---

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 and usage tips.}