Restructure the agent_sdks folder

[nan-yu]

Description

The code is reorganized with the following structure

agent_sdks/python
- src/a2ui
  - core
    - schema
      - manager.py
      - validation.py
      - payload_fixer.py
      - ...
    - template
      - ...
    - inference_stategy.py
  - adk
    - a2a_extension
      - a2ui_extension.py
      - send_a2ui_to_client_toolset.py
- tests
  - core/schema
    - ...
  - adk/a2a_extension
    - ...

Tested:

• All individual sample ADKs are working with connected client.
• The orchestrator sample is also working with all sub-agents.

Pre-launch Checklist

• I signed the CLA.
• I read the Contributors Guide.
• I read the Style Guide.
• I have added updates to the CHANGELOG.
• I updated/added relevant documentation.
• My code changes (if any) have tests.

If you need help, consider asking for advice on the discussion board.

[gemini-code-assist]

Code Review

This pull request is a large-scale refactoring that restructures the Python SDK into the agent_sdks folder, improving project organization. A key design change is that component catalogs are now expected to be standalone, with the SDK no longer resolving $refs to other catalogs. This simplifies the SDK's logic but places more responsibility on catalog creators. The A2uiSchemaManager API has been significantly updated to reflect this new approach. My review includes a couple of suggestions to address a potential regression and improve adherence to Python best practices in the new API.

[jacobsimionato]

SGTM overall! I am wondering:

• does this need to be nested in src/a2ui? I assume that's just a conventional way to structure python packages, if the package name is a2ui?
• Can the tests be closer to the source files? I assume what you've done is just conventional for Python. I'm not familiar!

[wrenj]

a2ui_extension.py only depends on the A2A sdk, not the ADK

could we rename it to a2a.py and put it at base? we'd expect another file mcp.py, and interactions_api.py

[nan-yu]

a2ui_extension.py only depends on the A2A sdk, not the ADK

could we rename it to a2a.py and put it at base? we'd expect another file mcp.py, and interactions_api.py

Makes sense. I also thought about having a top-level a2a package, but to start simple, I put the a2a.py for now.

[nan-yu]

• does this need to be nested in src/a2ui? I assume that's just a conventional way to structure python packages, if the package name is a2ui?

I didn't include the top level a2ui folder initially, but then realized when importing the package, it would look like from core.schema.catalog import A2uiSchemaManager, which didn't have the namespace of a2ui.. I also checked other python SDK, like ADK, it feels like it's better to add a2ui back.

• Can the tests be closer to the source files? I assume what you've done is just conventional for Python. I'm not familiar!

I asked Gemini the same question when structuring this. It sounds like having src and tests as the root is the recommended way in python.

[jacobsimionato]

• does this need to be nested in src/a2ui? I assume that's just a conventional way to structure python packages, if the package name is a2ui?

I didn't include the top level a2ui folder initially, but then realized when importing the package, it would look like from core.schema.catalog import A2uiSchemaManager, which didn't have the namespace of a2ui.. I also checked other python SDK, like ADK, it feels like it's better to add a2ui back.

• Can the tests be closer to the source files? I assume what you've done is just conventional for Python. I'm not familiar!

I asked Gemini the same question when structuring this. It sounds like having src and tests as the root is the recommended way in python.

No problem - that all makes sense! Thanks for educating me!