Switch Custom Agents to v1 Flow Registry

Note

This issue was created by Duo Agent and references this thread.

Problem

Custom agents in Duo Chat are currently using an experimental version of Flow Registry, which puts the feature at risk of breaking changes at any time.

This is especially critical for Self-Managed instances that often use a hosted AI Gateway. Shipping to Self-Managed with code against experimental may break for customers when the API changes in the future.

Why This Matters

• Stability: The experimental API can change without notice, potentially breaking custom agents
• Customer Impact: Self-Managed customers using hosted AI Gateway need stable API guarantees
• Production Readiness: Moving to v1 ensures we're using a stable, versioned API

Technical Changes

The migration from experimental to v1 involves:

Backend Changes:

• Rename Experimental → V1 and ExperimentalAgentWrapper → V1AgentWrapper payload builder classes
• Update flow config schema version from experimental to v1
• Make flow_environment an explicit required parameter
• Add required v1 fields to prompt components (name, unit_primitives)
• Update service classes: BuildFlowConfigService and ExecuteService

Frontend Changes:

• Update flowConfigSchemaVersion from experimental to v1 in workflow socket utilities

Testing:

• Update all related specs to reflect v1 schema and renamed classes

Related MR

!213472 (merged)