feat(gemini): add allowedFunctionNames support to prevent mode switch errors

[hannesrudolph]

Closes #10711

Summary

When switching modes, Gemini needs to see all tool definitions to understand conversation history, but should only be allowed to call tools permitted in the current mode. This PR implements the allowedFunctionNames feature for the Gemini provider to prevent model errors when switching modes.

Problem

When a user switches from one mode (e.g., "code") to another (e.g., "architect"), the conversation history may contain tool calls from the previous mode. Gemini requires the tool definitions to be present to understand the history, but the current mode may not have access to those tools. This causes errors in the Gemini API.

Solution

• Add allowedFunctionNames support to the Gemini provider via toolConfig.functionCallingConfig.allowedFunctionNames
• Pass ALL tool definitions to Gemini (for history compatibility) while restricting callable tools
• Only apply this behavior to Gemini (other providers continue using filtered tools as before)

Changes

• src/api/index.ts: Added allowedFunctionNames?: string[] to ApiHandlerCreateMessageMetadata interface
• src/api/providers/gemini.ts: Implemented toolConfig.functionCallingConfig.allowedFunctionNames when provided
• src/core/task/build-tools.ts: Added buildNativeToolsArrayWithRestrictions function with includeAllToolsWithRestrictions option
• src/core/task/Task.ts: Added provider check (apiProvider === "gemini") to only use the new behavior for Gemini
• src/api/providers/__tests__/gemini-handler.spec.ts: Added 5 comprehensive tests for the new functionality

Provider Support Research

• Gemini: ✅ Supports allowedFunctionNames via toolConfig.functionCallingConfig
• OpenAI: Has allowed_tools via tool_choice.type = "allowed_tools" (not yet implemented)
• Anthropic: ❌ Does not support this feature - only has auto, any, tool (single), none

Test Results

All 5231 tests pass across 376 test files.

---

Important

Adds allowedFunctionNames to Gemini provider to restrict tool usage based on mode while maintaining historical context.

• Behavior:
  • Implements allowedFunctionNames in src/api/providers/gemini.ts to restrict tool usage based on mode.
  • Passes all tool definitions to Gemini for historical context but restricts callable tools.
  • Only affects Gemini; other providers remain unchanged.
• API Changes:
  • Adds allowedFunctionNames?: string[] to ApiHandlerCreateMessageMetadata in src/api/index.ts.
• Tool Building:
  • Adds buildNativeToolsArrayWithRestrictions in src/core/task/build-tools.ts to support tool restrictions.
• Testing:
  • Adds tests in src/api/providers/__tests__/gemini-handler.spec.ts for allowedFunctionNames functionality.

^{This description was created by for f53e096. You can customize this summary. It will automatically update as commits are pushed.}

[roomote]

Oroocle   See task on Roo Cloud

Re-review complete. No new issues found since the alias/canonical consistency fix.

• Ensure allowedFunctionNames and declared tool names stay consistent when tool aliases/renames are involved (Gemini needs allowed names to exist in functionDeclarations).

Previous reviews

• 5a58849: Review #1

_{Mention @roomote in a comment to request specific changes to this pull request or fix all unresolved issues.}

[roomote]

Fixaroo   See task on Roo Cloud

Fixed the reported issue by resolving alias names to canonical names in allowedFunctionNames to ensure consistency with functionDeclarations. All local checks passed.

_{View commit | Revert commit}