[Nantha kumar (Nanduu24)]

Summary

The Public API Compatibility check currently fails on PRs with:

griffe...AliasResolutionError: Could not resolve alias
agent_framework._workflows._edge.EdgeGroup.builtin_type pointing at builtins.type
(in python/packages/core/agent_framework/_workflows/_edge.py)

The cause is that from builtins import type as builtin_type is written inside the EdgeGroup class body, so builtin_type becomes a class member (EdgeGroup.builtin_type) aliasing builtins.type. griffe treats it as a public alias and errors trying to resolve it while building the API, which fails the workflow.

Fix

Move the alias to module scope, matching _workflows/_request_info_mixin.py, which already imports builtin_type at module level. The annotations that use it (_TYPE_REGISTRY: ClassVar[dict[str, builtin_type[EdgeGroup]]] and EdgeGroup.register) are unchanged and still resolve, while EdgeGroup no longer exposes a spurious builtin_type member.

This is behavior-preserving: the module uses from __future__ import annotations, and builtin_type is referenced only in annotations — nothing accesses EdgeGroup.builtin_type/self.builtin_type at runtime. (The other occurrences in _executor.py are method-local, so they are not class members and are unaffected.)

Verification

• griffe now loads EdgeGroup cleanly — no AliasResolutionError, and no builtin_type member.
• pyright (strict) and ruff pass on the file.

[Nantha kumar (Nanduu24)]

Note for whoever merges: the failing Public API Compatibility check here is the very bug this PR fixes, observed from the base side. griffe's find_breaking_changes(old_package, new_package) loads the old (base) API first and raises AliasResolutionError: ...EdgeGroup.builtin_type pointing at builtins.type on the pre-fix _edge.py:315, so the check can't pass until the fix is on main. The head/new API in this PR resolves cleanly (verified with griffe + pyright + ruff). It should need an admin merge / override of that one check, after which the check goes green here and on every other open PR.