test(run-engine): build the replica-lag test's middle snapshot on the primary

startRunAttempt resolves the background worker task through readOnlyPrisma,
and this test configures a deliberately empty schema-only replica, so using it
to add a snapshot failed on the replica read instead of exercising the lag
scenario. Write the snapshot with the file's own primary-side helper.

Author: ericallam

internal-packages/run-engine/src/engine/tests/getSnapshotsSince.test.ts

@@ -7,7 +7,7 @@ import type { PrismaClient } from "@trigger.dev/database";
 import { RunEngine } from "../index.js";
 import { getExecutionSnapshotsSince } from "../systems/executionSnapshotSystem.js";
 import { copySnapshotsToReplica, createTestMetricsMeter } from "./helpers/replicaTestHelpers.js";
-import { setupTestScenario } from "./helpers/snapshotTestHelpers.js";
+import { createTestSnapshot, setupTestScenario } from "./helpers/snapshotTestHelpers.js";
 import { setupAuthenticatedEnvironment, setupBackgroundWorker } from "./setup.js";
 
 vi.setConfig({ testTimeout: 120_000 });
@@ -1149,14 +1149,18 @@ describe("RunEngine getSnapshotsSince", () => {
         );
 
         await setTimeout(500);
-        const dequeued = await engine.dequeueFromWorkerQueue({
+        await engine.dequeueFromWorkerQueue({
           consumerId: "test_replica_stale_tail",
           workerQueue: "main",
         });
 
-        await engine.startRunAttempt({
-          runId: dequeued[0].run.id,
-          snapshotId: dequeued[0].snapshot.id,
+        await createTestSnapshot(prisma, {
+          runId: run.id,
+          status: "EXECUTING",
+          environmentId: authenticatedEnvironment.id,
+          environmentType: authenticatedEnvironment.type,
+          projectId: authenticatedEnvironment.project.id,
+          organizationId: authenticatedEnvironment.organization.id,
         });
 
         const allSnapshots = await prisma.taskRunExecutionSnapshot.findMany({