Update agent models to match TypeSpec definition

[trangevi]

Motivation

Our Go agent model structs (AgentObject, AgentEndpoint) were outdated compared to the service TypeSpec at azure-rest-api-specs. Missing fields meant the CLI silently dropped properties returned by the API.

Changes

AgentObject -- added fields present in the TypeSpec but missing from Go:

• State (operational state: enabled/disabled)
• InstanceIdentity, Blueprint, BlueprintReference (identity/blueprint info already on AgentVersionObject but missing at the agent level)

AgentEndpoint -- added ProtocolConfiguration field and supporting types:

• ProtocolConfiguration struct with per-protocol config pointers (activity, responses, a2a, mcp, invocations, invocations_ws)
• ActivityProtocolConfiguration with EnableM365PublicEndpoint
• Empty marker structs for the other protocols (matching the TypeSpec which reserves them for future fields)

Constants -- added AgentEndpointAuthSchemeBotServiceTenant to match the TypeSpec AgentEndpointAuthorizationSchemeType union.

Tests -- added two round-trip tests covering the new fields:

• TestAgentObject_RoundTrip_AllFields
• TestAgentEndpoint_ProtocolConfiguration_RoundTrip

Notes

• AgentVersionObject was already aligned with TypeSpec -- no changes needed there.
• The agent show command calls GetAgentVersion (returns AgentVersionObject), so its output is unaffected. The AgentObject changes benefit commands that use GetAgent (e.g., list).

Fixes: #8338

[github-actions]

📋 Prioritization Note

Thanks for the contribution! The linked issue isn't in the current milestone yet.
Thank you for logging this issue; our team is reviewing it. If you need urgent prioritization, tag @RickWinter and @kristenwomack to let us know.

[Copilot]

Pull request overview

This PR updates the azure.ai.agents extension’s Go agent API model structs to better match the Foundry service TypeSpec, preventing fields returned by the service from being silently dropped during JSON unmarshaling.

Changes:

• Added missing AgentObject fields (State, InstanceIdentity, Blueprint, BlueprintReference).
• Added AgentEndpoint.ProtocolConfiguration and per-protocol configuration types (including marker structs for future expansion).
• Added round-trip JSON tests to cover the newly introduced fields.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
cli/azd/extensions/azure.ai.agents/internal/pkg/agents/agent_api/models.go	Extends agent/endpoint model structs with additional TypeSpec-aligned fields and protocol configuration types.
cli/azd/extensions/azure.ai.agents/internal/pkg/agents/agent_api/models_test.go	Adds JSON round-trip tests validating the new fields serialize/deserialize correctly.

[jongio]

Solid TypeSpec sync. The model additions are well-scoped, the resolveEndpointProtocols extraction is a clean refactor, and the round-trip tests cover the new shapes thoroughly. One CI fix needed before merge.

CI: golangci-lint is failing on gofmt. The ProtocolConfiguration and AgentEndpoint structs have manually-padded spaces aligning struct tags. Running gofmt -s -w models.go will fix it. Same likely applies to the AgentObject struct fields added in this PR.

[jongio]

gofmt is flagging this struct (CI failure). The spaces between each type and its struct tag are manually padded for alignment, but gofmt expects tab-based alignment here. Run gofmt -s -w on this file to fix.

The same applies to the AgentEndpoint and AgentObject struct field blocks you reformatted below.

[huimiu]

When ProtocolConfiguration is non-nil but all fields are nil (e.g. the server returns "protocol_configuration": {}), this guard causes the function to fall through and surface the deprecated Protocols list. A non-nil pc should be treated as authoritative - return protocols even if empty, so older data doesn't silently override the new shape:

go if pc := endpoint.ProtocolConfiguration; pc != nil { // ... build list ... return protocols // return even if empty }