test(webapp): default SESSION_SECRET in setup, not at module scope

Author: kathiekiwi

apps/webapp/test/dashboardAgentWatchErrorFingerprint.test.ts

@@ -42,8 +42,6 @@ vi.mock("~/v3/canAccessDashboardAgent.server", () => ({
   canAccessDashboardAgent: async () => true,
 }));
 
-process.env.SESSION_SECRET = "test-session-secret-for-watch-fingerprints";
-
 const { createDashboardAgentWatch } = await import("~/services/dashboardAgentWatches.server");
 
 /** Replays every migration in order, so a new migration can't leave this file on a stale schema. */

apps/webapp/test/setup.ts

@@ -13,6 +13,7 @@ config({ path: path.resolve(__dirname, "../.env") });
 // the pair — the ioredis mock below forces lazyConnect, so nothing ever dials.
 process.env.REDIS_HOST ??= "localhost";
 process.env.REDIS_PORT ??= "6379";
+process.env.SESSION_SECRET ??= "test-session-secret";
 process.env.PROVIDER_SECRET ??= "test-provider-secret";
 process.env.COORDINATOR_SECRET ??= "test-coordinator-secret";
 process.env.MANAGED_WORKER_SECRET ??= "test-managed-worker-secret";