Merge pull request #999 from buster-so/Jacob-Fix-Commas-and-Escaped-$

Fixed commas being added and escaping the $ in reports

packages/ai/src/agents/analyst-agent/analyst-agent-prompt.txt

@@ -80,7 +80,6 @@ You operate in a loop to complete tasks:
   - Use markdown for lists or emphasis (but do not use headers)
   - NEVER lie or make things up
   - Be transparent about limitations or aspects of the request that could not be fulfilled
-  - **Do not** escape $ characters (e.g. \\$50)
   - When building a report, your output message should be very concise and only feature a brief overview of the report. Analysis and explanations should be placed in the report.
 - Do not ask clarifying questions
   - If the user's request is ambiguous, make reasonable assumptions based on the available data context and proceed to accomplish the task, noting these assumptions in your final response if significant.
@@ -228,7 +227,6 @@ You operate in a loop to complete tasks:
   - Use **bold** for key words, phrases, as well as data points or ideas that should be highlighted.
   - Use a professional, objective research tone. Be precise and concise; prefer domain-appropriate terminology and plain language; avoid colloquialisms and casual phrasing.
   - Avoid contractions and exclamation points.
-  - ALWAYS escape dollar signs in all `createReports` and `modifyReports` tool calls (including inline/code blocks) by prefixing with a backslash ("\\$") so rendering does not trigger math parsing. Examples: "Total Revenue: \\$1,234,567"; "In Q1, revenue reached \\$250k".
   - Be direct and concise, avoid fluff and state ideas plainly. 
   - Avoid technical explanations in summaries key findings sections. If technical explanations are needed, put them in the methodology section.
   - You can use ``` to create code blocks. This is helpful if you wish to display a SQL query.
@@ -350,6 +348,7 @@ You operate in a loop to complete tasks:
   - Always display names instead of IDs when available (e.g., "Product Name" instead of "Product ID")
   - For comparisons between values, display them in a single chart for visual comparison (e.g., bar chart for discrete periods, line chart for time series)
   - For requests like "show me our top products," consider showing only the top N items (e.g., top 10)
+  - When returning a number that represents and ID or a Year, set the `numberSeparatorStyle` to null. Never set `numberSeparatorStyle` to ',' if the value represents an Id or year.
 - Planning and Description Guidelines
   - When planning grouped or stacked bar charts, specify the field used for grouping or stacking (e.g., "grouped bars side-by-side split by `[field_name]`" or "bars stacked by `[field_name]`").
   - For multi-line charts, indicate if lines represent different categories of a single metric (e.g., "lines split by `[field_name]`") or different metrics (e.g., "separate lines for `[metric1]` and `[metric2]`").