fix(chat): compare selection ids as sets, not sequences

Cursor Bugbot: sameIds compared rowIds/columnIds by index, but a table
selection's ids iterate in click order (they come from a Set), so the same rows
picked in a different order — or reached via a cell range rather than the
gutter — compared unequal. prepareContextForInsert then added a second
ordinalized chip pointing at rows already referenced instead of no-opping.

More reachable since the previous commit started sourcing rowIds from
rowSel.ids directly, where insertion order tracks the user's clicks.

Author: waleedlatif1

apps/sim/app/workspace/[workspaceId]/w/[workflowId]/components/panel/components/copilot/components/user-input/utils.test.ts

@@ -67,6 +67,14 @@ describe('prepareContextForInsert', () => {
     expect(prepareContextForInsert(other, [fileSelection()])).not.toBeNull()
   })
 
+  it('treats the same rows picked in a different order as one selection', () => {
+    // Row ids iterate in click order, so re-picking the same rows differently
+    // must no-op rather than add a second chip over rows already referenced.
+    const reordered = tableSelection({ rowIds: ['r3', 'r1', 'r2'] })
+
+    expect(prepareContextForInsert(reordered, [tableSelection()])).toBeNull()
+  })
+
   it('distinguishes a cell range from the whole rows it spans', () => {
     const range = tableSelection({ columnIds: ['c_name'] })
 

apps/sim/app/workspace/[workspaceId]/w/[workflowId]/components/panel/components/copilot/components/user-input/utils.ts

@@ -193,11 +193,20 @@ type McpContext = Extract<ChatContext, { kind: 'mcp' }>
 type FileSelectionContext = Extract<ChatContext, { kind: 'file_selection' }>
 type TableSelectionContext = Extract<ChatContext, { kind: 'table_selection' }>
 
-/** Order-sensitive equality for two optional id lists. */
+/**
+ * Set equality for two optional id lists.
+ *
+ * Deliberately order-insensitive: a table selection's row ids come from a Set
+ * whose iteration order follows click order, and the same rows picked in a
+ * different order — or via a cell range rather than the gutter — are the same
+ * selection. Comparing by index would call those distinct and add a duplicate
+ * ordinalized chip pointing at rows already referenced.
+ */
 function sameIds(a: string[] | undefined, b: string[] | undefined): boolean {
   if (a === b) return true
   if (!a || !b || a.length !== b.length) return false
-  return a.every((id, i) => id === b[i])
+  const inA = new Set(a)
+  return b.every((id) => inA.has(id))
 }
 
 /**