[kaxil]

Adds openai-agents to the agent-framework CI job, so the OpenAI Agents SDK adapter's tests run on every PR that touches common.ai, as the Strands and ADK adapters' do. Stacked on the adapter PR.

Design rationale

Pull requests cap the SDK below 0.21 while the image holds openai 2.x. PR runs install the framework with uv pip install --override <every installed package>. An override replaces a requirement rather than relaxing a cap, so it would also replace openai-agents' own openai>=3 and test its newest release against the image's openai 2.x, a pairing no user gets. While the image has openai 2.x, PR runs install openai-agents<0.21, the newest line that accepts it and what Airflow's constraints resolve to. The cap is applied only when the image's openai is below 3, so it goes away on its own when the workspace's openai<3 override is dropped.

--framework-pins now ignores the workspace's [tool.uv] settings. Run from the repository root, uv pip install picked up the root override-dependencies = ["openai>=2.47.0,<3"], so canary runs still held openai below 3 and installed openai-agents 0.23.1 against openai 2.54. Canary runs now install with --no-config, keeping only the repository's exclude-newer window, which is the environment a user who installs the framework gets. For Strands the canary install resolved and passed locally the same way (1.59, its own mcp pin, 119 passed); ADK's canary run was not repeated locally.

Locally, through the same breeze shell command the job runs:

Mode	openai-agents	openai	Result
image versions (PR)	0.20.0	2.54.0	93 passed
--framework-pins (canary)	0.23.1	3.28.0	93 passed

breeze verify lists the new job, and a test now checks its framework list against the workflow matrix, so the two cannot drift apart again. The frameworks page's note on why these tests run in a job of their own is updated: it still said CI does not run them.

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.