[FEATURE] Add official non-Python kagent adapters/SDKs (Go, TypeScript, Java)

[wfrank2509]

📋 Prerequisites

• I have searched the existing issues to avoid creating a duplicate
• By submitting this issue, you agree to follow our Code of Conduct

📝 Feature Summary

Add official non-Python kagent adapters/SDKs (Go, TypeScript, Java) with feature parity for BYO session/task management.

❓ Problem Statement / Motivation

kagent’s strongest BYO integration path appears Python-centric today.
For Go/TypeScript/Java teams, critical integration pieces (A2A lifecycle details, task/session persistence, context propagation) need to be reimplemented.

This blocks adoption in organizations with:

• Java/Go/Typescript standard stacks,
• stricter governance/compliance requirements,
• runtime/resource constraints where Python wrappers are undesirable.

Result: duplicated glue code, inconsistent behavior, slower enterprise adoption.

💡 Proposed Solution

Provide official kagent adapters/SDKs for:

• Go
• TypeScript
• Java

with minimum parity:

• A2A server integration compatible with kagent controller/UI
• task/session persistence hooks (so chat history restore works)
• request context propagation
• standardized streaming lifecycle helpers
• model/credential wiring helpers aligned with governance

Suggested rollout:

• publish language-neutral adapter contract + conformance tests
• ship Go/TypeScript first
• add Java adapter (high enterprise value)

🔄 Alternatives Considered

• Keep custom BYO glue per language (high duplication/risk)
• Python sidecar wrappers (adds complexity, not acceptable in some enterprise environments)

🎯 Affected Service(s)

Multiple services / System-wide

📚 Additional Context

This is a strategic adoption enabler: reducing language lock-in and improving enterprise readiness while keeping protocol behavior consistent across runtimes.

🙋 Are you willing to contribute?

• I am willing to submit a PR for this feature