test(run-ops split): repair mollifier claim-resolution db.server mock

The write-path split added static `runOpsLegacyPrisma`/`runOpsNewPrisma`
imports to idempotencyKeys.server.ts, which this test loads. vitest
validates every named import against the `~/db.server` mock, so the mock
now errored on the missing run-ops singletons. Add the four run-ops
exports (empty stubs, same boundary pattern as the batchTriggerV3
residency test) and pin isSplitEnabled() to false so the dedup routing
deterministically returns the injected fake prisma regardless of the
ambient RUN_OPS_SPLIT_ENABLED.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: d-cs

apps/webapp/test/mollifierClaimResolution.test.ts

@@ -3,8 +3,17 @@ import { describe, expect, it, vi } from "vitest";
 // Stub `~/db.server` before importing the concern — the real module
 // eagerly calls `prisma.$connect()` at singleton construction, which
 // would fail without a database. The concern under test receives its
-// prisma via the constructor, so the stub is never used by the code path.
-vi.mock("~/db.server", () => ({ prisma: {}, $replica: {} }));
+// prisma via the constructor, so these empty stubs are never used by the
+// tested path; the run-ops singletons only satisfy the concern's static
+// imports (vitest validates every named import against the mock).
+vi.mock("~/db.server", () => ({
+  prisma: {},
+  $replica: {},
+  runOpsNewPrisma: {},
+  runOpsLegacyPrisma: {},
+  runOpsNewReplica: {},
+  runOpsLegacyReplica: {},
+}));
 
 // The IdempotencyKeyConcern resolves the pre-gate claim through the
 // global mollifier buffer (`getMollifierBuffer`), shared by both
@@ -22,6 +31,13 @@ vi.mock("~/v3/mollifier/mollifierBuffer.server", () => ({
 vi.mock("~/v3/mollifier/mollifierGate.server", () => ({
   makeResolveMollifierFlag: () => async () => h.orgFlag,
 }));
+// Pin the idempotency dedup routing to the injected fake prisma: split OFF
+// makes resolveIdempotencyDedupClient return the concern's constructor client,
+// so these tests exercise claim resolution deterministically regardless of the
+// ambient RUN_OPS_SPLIT_ENABLED (the split path routes to the empty runOps mocks).
+vi.mock("~/v3/runOpsMigration/splitMode.server", () => ({
+  isSplitEnabled: async () => false,
+}));
 
 import type { MollifierBuffer } from "@trigger.dev/redis-worker";
 import { IdempotencyKeyConcern } from "~/runEngine/concerns/idempotencyKeys.server";