fix: wrap DISTINCT ON in subquery to restore createdAt ordering

PostgreSQL's DISTINCT ON requires ORDER BY to start with the DISTINCT
column, so the outer query must re-order by createdAt DESC for proper
pagination ordering (most recent threads first).

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

apps/web/app/(app)/[emailAccountId]/reply-zero/fetch-trackers.ts

@@ -25,13 +25,16 @@ export async function getPaginatedThreadTrackers({
 
   const [trackers, total] = await Promise.all([
     prisma.$queryRaw<ThreadTracker[]>`
-      SELECT DISTINCT ON ("threadId") *
-      FROM "ThreadTracker"
-      WHERE "emailAccountId" = ${emailAccountId}
-        AND "resolved" = false
-        AND "type" = ${type}::text::"ThreadTrackerType"
-        ${dateClause}
-      ORDER BY "threadId", "createdAt" DESC
+      SELECT * FROM (
+        SELECT DISTINCT ON ("threadId") *
+        FROM "ThreadTracker"
+        WHERE "emailAccountId" = ${emailAccountId}
+          AND "resolved" = false
+          AND "type" = ${type}::text::"ThreadTrackerType"
+          ${dateClause}
+        ORDER BY "threadId", "createdAt" DESC
+      ) AS distinct_threads
+      ORDER BY "createdAt" DESC
       LIMIT ${PAGE_SIZE}
       OFFSET ${skip}
     `,