test(webapp): isolate redis for streamBatchItems to fix 30s seal-timeout flake

Author: nicktrn

apps/webapp/test/engine/streamBatchItems.test.ts

@@ -16,7 +16,11 @@ vi.mock("~/services/platform.v3.server", async (importOriginal) => {
 
 import { RunEngine } from "@internal/run-engine";
 import { setupAuthenticatedEnvironment } from "@internal/run-engine/tests";
-import { containerTest } from "@internal/testcontainers";
+// Per-test redis (isolated): each test spins up its own RunEngine and runs batch work, which leaves
+// background activity on redis that outlives the test - sharing a worker redis across the 16 cases
+// here caused cross-test interference and 30s seal-timeout flakes. Same carve-out as the run-engine
+// batch tests.
+import { containerTestWithIsolatedRedis as containerTest } from "@internal/testcontainers";
 import { trace } from "@opentelemetry/api";
 import { PrismaClient } from "@trigger.dev/database";
 import { BatchId } from "@trigger.dev/core/v3/isomorphic";

test-timings.json

@@ -74,7 +74,7 @@
   "apps/webapp/test/workerQueueSplit.test.ts": 3,
   "apps/webapp/test/components/DateTime.test.ts": 24,
   "apps/webapp/test/engine/batchPayloads.test.ts": 5018,
-  "apps/webapp/test/engine/streamBatchItems.test.ts": 27262,
+  "apps/webapp/test/engine/streamBatchItems.test.ts": 47000,
   "apps/webapp/test/engine/taskIdentifierRegistry.test.ts": 13152,
   "apps/webapp/test/engine/triggerTask.test.ts": 31630,
   "apps/webapp/test/presenters/mapRunToLiveFields.test.ts": 3,