[Bug] Numeric enum values cause 400 Bad Request in Gemini API

[nxxxsooo]

Description

When using opencode-antigravity-auth with the Gemini API, the toGeminiSchema function does not stringify numeric enum values, causing a 400 Bad Request error.

Error Message

Schema.properties[name].enum[2]: enum value must be a STRING

The API returns errors like:

• 1.enum[0]: enum value must be a STRING
• 1.enum[1]: enum value must be a STRING

Root Cause

In gemini.js, the toGeminiSchema function at lines 87-89:

else if (key === "enum" && Array.isArray(value)) {
    result[key] = value; // ❌ Keeps numeric enum values as-is
}

Suggested Fix

else if (key === "enum" && Array.isArray(value)) {
    result[key] = value.map(v => String(v)); // ✅ Convert all values to strings
}

Environment

• Plugin version: 1.4.6
• OpenCode version: latest
• API: Gemini (Google AI)

Workaround

Manually editing gemini.js in the cached plugin directory works temporarily, but gets overwritten on plugin updates.

Thanks for maintaining this plugin! 🙏

[github-actions]

👋 Thanks for opening this issue!

Duplicate of #399. Gemini rejects non-string enum values in tool schemas (enum value must be STRING), and current toGeminiSchema preserves numeric/boolean enums as-is. Temporary workaround: make enum values strings in your tool/MCP schema (or disable the offending MCP server). Also update to latest/beta with opencode update and plugin: ["opencode-antigravity-auth@beta"] until fix ships.

🔗 This appears to be related to #399. Please check that issue for updates.

---

This is an automated response. A maintainer will review your issue soon.