fix: remove LIMIT 100 example and unused example_queries from v1 prompt

Remove the explicit LIMIT 100 example from the LIMIT RULES section to
prevent agents from hallucinating that specific value. Remove the
{example_queries} template variable from the v1 prompt and the
example_queries field from SqlPromptContext since it is no longer
referenced by any template.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: UIPath-Harshit

src/uipath_langchain/agent/tools/datafabric_tool/prompts/context.py

@@ -49,11 +49,3 @@ class SqlPromptContext(BaseModel):
         ),
     )
 
-    # ── Example queries (customer-provided or auto-generated) ─────────
-    example_queries: str = Field(
-        default="",
-        description=(
-            "SQL example patterns for the entities. Sourced from customer "
-            "configuration or auto-generated from entity schema as a fallback."
-        ),
-    )

src/uipath_langchain/agent/tools/datafabric_tool/prompts/v1.py

@@ -96,8 +96,7 @@
    - NEVER do: GROUP BY + MIN()/MAX() when the question asks for a single \
 extreme row.
 9. LIMIT RULES — Add LIMIT only when needed:
-   - Queries without WHERE that could return many rows MUST have a LIMIT \
-(e.g. LIMIT 100).
+   - Queries without WHERE that could return many rows MUST have a LIMIT.
    - Do NOT add LIMIT to queries that already naturally return a bounded \
 set: an equality filter on a unique key, an aggregation that returns one row, \
 or a question asking for "all X meeting Y".
@@ -159,4 +158,4 @@
 natural-language answer that directly addresses the user's question, \
 referencing the values from the result. Do not invent or summarise data \
 beyond what the query returned.
-{domain_guidance}{example_queries}"""
+{domain_guidance}"""