feat(agent): add ontology binding to Data Fabric context config

[sankalp-uipath]

What

Adds Data Fabric ontology binding to the agent context model: a context can carry one or more ontologies that the runtime fetches to ground Text2SQL.

• agent/models/agent.py — AgentContextResourceConfig.ontology_set (alias ontologySet), a list of DataFabricOntologyItem nested in the context alongside entitySet.
• platform/entities/_entity_ontology_service.py — DataFabricOntologyItem ({name, folderId, description?}) + EntityOntologyService, which fetches one ontology file: GET datafabric_/api/ontologies/{name}/files/{type} on the authenticated, folder-scoped client.
• platform/entities/_entities_service.py — get_ontology_file_async(ontology_name, file_type="owl", folder_key=None) is a thin public wrapper delegating to EntityOntologyService (all ontology logic lives in the ontology sub-service). One file per call; the langchain consumer fetches owl and r2rml as separate calls.

Why

An ontology is part of a Data Fabric context — domain knowledge over the same entities — so it is configured inline on the context (a sibling of entitySet), mirroring how entities are bound. Each ontology carries its own folderId so it can live in a different folder from the entities.

Notes

• Additive + backward compatible: ontology_set defaults to None.
• No referenceKey on ontology items: ontologies are not solution-aware at this point, so there is no solution key to reference. The field is dropped from DataFabricOntologyItem — it was never populated or read (ontologies resolve by name + folderId). Backward compatible: configs that still send referenceKey are tolerated via extra="allow".
• Validation is server-side: file-type/name validation lives in the ontology API (QE), not the client — the SDK forwards the request and surfaces the API's rejection (e.g. an unsupported file type) as EnrichedException (status code + response body + extracted message) rather than swallowing it. Redundant client-side allowlists were removed per review.
• Tests: nested ontologySet parse/dump, required folderId per item, backward-compat default, full-AgentDefinition normalization; get_ontology_file_async covered for spec, folder header, allowed file types, and the negative case (API rejection of an unsupported file type surfaces as EnrichedException).
• Consumed by uipath-langchain PR feat: add integration service invocation support #911.
• Release: uipath → 2.12.5, uipath-platform → 0.1.91, pin uipath-platform>=0.1.91; latest main merged in and lockfiles relocked. Do not merge a .dev pin.

Development Packages

uipath

[project]
dependencies = [
  # Exact version (copy-paste ready):
  "uipath==2.12.9.dev1017287143",

  # Any version from this PR (uncomment to use a range instead):
  # "uipath>=2.12.9.dev1017280000,<2.12.9.dev1017290000",
]

[[tool.uv.index]]
name = "testpypi"
url = "https://test.pypi.org/simple/"
publish-url = "https://test.pypi.org/legacy/"
explicit = true

[tool.uv.sources]
uipath = { index = "testpypi" }
uipath-platform = { index = "testpypi" }

[tool.uv]
override-dependencies = ["uipath-platform==0.1.92.dev1017287143"]

uipath-platform

[project]
dependencies = [
  # Exact version (copy-paste ready):
  "uipath-platform==0.1.92.dev1017287143",

  # Any version from this PR (uncomment to use a range instead):
  # "uipath-platform>=0.1.92.dev1017280000,<0.1.92.dev1017290000",
]

[[tool.uv.index]]
name = "testpypi"
url = "https://test.pypi.org/simple/"
publish-url = "https://test.pypi.org/legacy/"
explicit = true

[tool.uv.sources]
uipath-platform = { index = "testpypi" }

Dev builds (testpypi) are republished by CI on each push. Use the latest .dev pins from the most recent CI publish comment, at base versions uipath==2.12.5 / uipath-platform==0.1.91:

[[tool.uv.index]]
name = "testpypi"
url = "https://test.pypi.org/simple/"
publish-url = "https://test.pypi.org/legacy/"
explicit = true

[tool.uv.sources]
uipath = { index = "testpypi" }
uipath-platform = { index = "testpypi" }

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

[UIPath-Harshit]

Should be called get_onotology_bundle_async

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

🚨 Heads up: uipath-langchain cross-tests are FAILING 🚨

Your changes may break the uipath-langchain-python integration.

⚠️ These checks are NOT enforced by branch protection rules. Please review the failures before merging.

🔍 Inspect the failed run →

[github-actions]

🚨 Heads up: uipath-integrations cross-tests are FAILING 🚨

Your changes may break one or more integrations in uipath-integrations-python:

• uipath-openai-agents
• uipath-google-adk
• uipath-agent-framework
• uipath-llamaindex
• uipath-pydantic-ai

⚠️ These checks are NOT enforced by branch protection rules. Please review the failures before merging.

🔍 Inspect the failed run →