feat: add ArgumentEmail and ArgumentGroupName escalation recipient types

[dushyant-uipath]

Summary

Adds two new recipient types to the escalation data model to support argument-driven assignees — where the assignee is resolved from a named input argument at runtime rather than being fixed at design time.

Type value	Name	Wire field (argumentName)	Resolves to
7	ArgumentEmail	argument_path: str	Email recipient
8	ArgumentGroupName	argument_path: str	Group-name recipient

Both extend BaseEscalationRecipient and are included in the AgentEscalationRecipient discriminated union.

Note on field naming: the Python field is argument_path (supports dot-notation for nested fields e.g. user.email). The JSON alias on the wire remains argumentName — wire format is unchanged.

Changed files

File	Change
src/uipath/agent/models/agent.py	ARGUMENT_EMAIL = "ArgumentEmail", ARGUMENT_GROUP_NAME = "ArgumentGroupName" enum values; normalization map entries (int 7, 8); ArgumentEmailRecipient and ArgumentGroupNameRecipient classes; discriminated union updated

Failure modes & what was tested

What can fail

These model classes have no runtime logic — they are pure data containers. The only failure modes are deserialization:

1. Unknown type value: a recipient with type not in the normalization map raises a Pydantic validation error. This is existing behavior, unchanged.
2. Missing argumentName field: argument_path is required with no default — a recipient missing the field raises a Pydantic validation error at parse time, before any tool runs.

Both are fail-fast at agent startup, not at task creation time.

What was tested

• Deserialized { "type": 7, "argumentName": "assigneeEmail" } → ArgumentEmailRecipient(argument_path="assigneeEmail") ✓
• Deserialized { "type": 8, "argumentName": "assigneeGroup" } → ArgumentGroupNameRecipient(argument_path="assigneeGroup") ✓
• Deserialized via integer type 7/8 (normalization map path) ✓
• Deserialized via string "ArgumentEmail"/"ArgumentGroupName" (enum path) ✓
• Existing recipient types 1–6 unaffected ✓
• Full end-to-end HC run: agent with ArgumentEmail recipient created Action Center task with correct assignee ✓

Related

• Agents repo PR: UiPath/Agents#4835
• Consumed by: UiPath/uipath-langchain-python PR feat: wire tool evals, add mocked tool sample agent #735 (runtime resolution)
• Design doc: https://uipath.atlassian.net/wiki/spaces/BPA/pages/90469990611/Dynamic+Assignee

Test plan

• Deserialize { "type": 7, "argumentName": "assigneeEmail" } → ArgumentEmailRecipient(argument_path="assigneeEmail")
• Same for type 8 → ArgumentGroupNameRecipient
• Deserialize via integer type and string type for both
• Verify existing recipient types 1–6 unaffected

Tested locally using HackedCoded

[dianagrecu-uipath]

Please also add tests for the deserialization of the new recipient types. test_agent.py only covers StandardRecipient and AssetRecipient.

[dianagrecu-uipath]

Maybe argument_path would be a better choice for this parameter, since the argument isn't necessarily top level.