Fix cross-environment thread mixing and unstable atom family key

- Add environmentId check to thread filter in ArchivedThreadsPanel to
  prevent threads from different environments being grouped together
  when they share the same projectId.

- Sort environment IDs before joining in makeArchivedThreadsEnvironmentKey
  to produce a stable atom family key regardless of input order.

Author: cursoragent

apps/web/src/components/settings/SettingsPanels.tsx

@@ -1334,7 +1334,10 @@ export function ArchivedThreadsPanel() {
       .map((project) => ({
         project,
         threads: threads
-          .filter((thread) => thread.projectId === project.id)
+          .filter(
+            (thread) =>
+              thread.projectId === project.id && thread.environmentId === project.environmentId,
+          )
           .toSorted((left, right) => {
             const leftKey = left.archivedAt ?? left.createdAt;
             const rightKey = right.archivedAt ?? right.createdAt;

apps/web/src/lib/archivedThreadsState.ts

@@ -19,7 +19,7 @@ export type ArchivedSnapshotEntry = {
 const knownArchivedThreadEnvironmentKeys = new Set<string>();
 
 function makeArchivedThreadsEnvironmentKey(environmentIds: ReadonlyArray<EnvironmentId>): string {
-  return environmentIds.join(ARCHIVED_THREADS_ENVIRONMENT_KEY_SEPARATOR);
+  return [...environmentIds].sort().join(ARCHIVED_THREADS_ENVIRONMENT_KEY_SEPARATOR);
 }
 
 function parseArchivedThreadsEnvironmentKey(key: string): ReadonlyArray<EnvironmentId> {