[BUG] Go ADK runtime ignores RemoteAgents config - sub-agent tools never registered

[fabidick22]

📋 Prerequisites

• I have searched the existing issues to avoid creating a duplicate
• By submitting this issue, you agree to follow our Code of Conduct
• I am using the latest version of the software
• I have tried to clear cache/cookies or used incognito mode (if ui-related)
• I can consistently reproduce this issue

🎯 Affected Service(s)

App Service

🚦 Impact/Severity

Blocker

🐛 Bug Description

When an agent using runtime: go has a sub-agent configured via type: Agent tool, the Go ADK runtime reads the remote_agents from config.json and logs them correctly, but never registers them as tools in the Google ADK agent.
The LLM cannot delegate to sub-agents because the tool simply doesn't exist in the available tool list.

Switching the same agent to runtime: python with identical config works correctly, the sub-agent tool appears and delegation succeeds.

🔄 Steps To Reproduce

1. Create two agents: a parent agent and a child agent
2. Configure the parent with runtime: go and reference the child as a sub-agent tool:

tools:
  - type: McpServer
    mcpServer:
      name: some-tool-server
      # ... MCP tools
  - type: Agent
    agent:
      name: child-agent
      namespace: kagent

🤔 Expected Behavior

The go runtime should convert remote_agents from config.json into callable tools (A2A), matching the Python runtime behavior. The sub-agent tool should appear in the agent's available tools list.

📱 Actual Behavior

The go runtime reads and logs remote_agents count but never processes them into tools.

Switching runtime: go -> runtime: python on the parent agent (same config) resolves the issue. The Python runtime correctly registers the remote agent as a callable tool.

💻 Environment

• kagent Helm chart version: v0.8.0
• kagent-crds version: v0.8.0
• Go runtime image: golang-adk:0.8.0

🔧 CLI Bug Report

No response

🔍 Additional Context

No response

📋 Logs

📷 Screenshots

No response

🙋 Are you willing to contribute?

• I am willing to submit a PR to fix this issue

[supreme-gg-gg]

Yes, this is a known limitation with our Go runtime right now. This is being worked on and we will add a similar support for remote a2a agents to Go ADK as it is right now in Python.

[supreme-gg-gg]

Completed in #1538