fix(seer): Resolve TOP_N display type before LLM context capture

TOP_N widgets are mutated to AREA later in the render body, but
useLLMContext read the pre-mutation value on first render, producing
a misleading table query hint instead of the correct timeseries hint.

Co-Authored-By: Claude Opus 4.6 <noreply@example.com>

Author: Mihir-Mavalankar

static/app/views/dashboards/widgetCard/index.tsx

@@ -178,20 +178,27 @@ function WidgetCard(props: Props) {
   const {dashboardId: currentDashboardId} = useParams<{dashboardId: string}>();
   const timeoutRef = useRef<NodeJS.Timeout | null>(null);
 
+  // Resolve TOP_N → AREA before capturing context (the render body mutates
+  // this later, but useLLMContext needs the resolved value on first render).
+  const resolvedDisplayType =
+    props.widget.displayType === DisplayType.TOP_N
+      ? DisplayType.AREA
+      : props.widget.displayType;
+
   // Push widget metadata into the LLM context tree for Seer Explorer.
   useLLMContext({
     title: props.widget.title,
-    displayType: props.widget.displayType,
+    displayType: resolvedDisplayType,
     widgetType: props.widget.widgetType,
-    queryHint: getQueryHint(props.widget.displayType),
+    queryHint: getQueryHint(resolvedDisplayType),
     queries: props.widget.queries.map(q => ({
       name: q.name,
       conditions: q.conditions,
       aggregates: q.aggregates,
       columns: q.columns,
       orderby: q.orderby,
     })),
-    ...getWidgetData(props.widget.displayType, data),
+    ...getWidgetData(resolvedDisplayType, data),
   });
 
   const onDataFetched = (newData: Data) => {