Task

Make the Azure AI Agents extension consistently read and execute the unified azure.yaml service configuration across local run, deploy, provision, synthesis, and brownfield validation.

Why

Agent configuration can be inline, in the deprecated config: block, or stored in local files referenced by $ref. These shapes are not currently resolved consistently across runtime paths, so the same project can behave differently between run, deploy, and provision. Referenced resources may be missed, environment expressions or typed values may be changed too early, and container operations may use the unresolved service directory.

Scope

• Resolve one effective service configuration from inline, legacy config:, and local $ref forms.
• Preserve raw environment expressions until runtime and normalize supported scalar environment values.
• Use the same resolved configuration for local run, deploy, provision, synthesis, and brownfield validation.
• Support both azure.yaml and azure.yml project files.
• Pass the resolved service directory to core container build, package, and publish operations without rewriting project configuration on disk.
• Preserve compatibility with legacy agent.yaml and agent.manifest.yaml projects.
• Keep hosted-agent deploy session carryover disabled until it is restored or redesigned in separate follow-up work.

Acceptance criteria

• Inline, legacy, and $ref service configurations produce consistent runtime behavior.
• Container operations use the resolved project-relative service path without mutating azure.yaml or cached project configuration.
• Invalid service paths outside the project are rejected.
• Existing legacy agent projects continue to work.
• Relevant unit, build, spelling, and required CI checks pass.

Implemented by #9149.