test(run-ops): stub org-data-stores registry singleton + deterministic empty CH window

Two webapp unit-test shards were red on this branch:

- Shard 6 (apiRetrieveRunPresenter.readroute.test.ts): the
  organizationDataStoresRegistry singleton is constructed at import (pulled in
  transitively via the ClickHouse factory instance) and immediately fires a
  `forever` pRetry(loadFromDatabase) plus a setInterval reload against
  db.server's $replica. In CI (no Postgres on localhost) those retry forever and
  saturate the worker event loop, timing out an awaiting test's hook. Mock the
  instance module to a no-op in test/setup.ts, mirroring the other eager-singleton
  stubs. No unit test uses this singleton — the registry-behavior tests construct
  the class directly — so this is safe and should also help other shards/branches
  that import the presenter graph.

- Shard 2 (nextRunListPresenter.readthrough.test.ts): the two empty-state tests
  seeded a run then assumed it had NOT yet replicated to ClickHouse within the page
  window, so result.runs would be empty. That held on a slow local stack but raced
  on CI, where replication had completed and the run surfaced (length 1, not 0).
  Scope those two calls to a `to` one hour in the past; the CH page filters
  created_at <= to, so a just-created run is deterministically excluded regardless
  of replication timing. The PG existence probe has no time filter, so it still
  finds the row and hasAnyRuns stays true — the exact behavior each test verifies.

Reproduced both failures and verified the fix under a CI-faithful env (DATABASE_URL
+ REDIS at dead ports, GITHUB_ACTIONS=true, --no-file-parallelism): shard 2 now
18 files / 118 tests green, shard 6 now 16 files / 212 tests green.

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

Author: d-cs

apps/webapp/test/nextRunListPresenter.readthrough.test.ts

@@ -169,7 +169,17 @@ function throwingFindFirst(prisma: PrismaClient, label: string): PrismaClient {
   }) as unknown as PrismaClient;
 }
 
-const callOptions = (ctx: SeedContext) => ({ projectId: ctx.projectId, pageSize: 10 });
+const callOptions = (ctx: SeedContext, overrides?: { to?: number }) => ({
+  projectId: ctx.projectId,
+  pageSize: 10,
+  ...overrides,
+});
+
+// `to` one hour in the past. The CH page filters `created_at <= to`, so a just-created run is
+// deterministically excluded regardless of replication timing — the empty-state tests otherwise
+// raced on the run not having replicated yet (held locally, failed on CI). The PG existence probe
+// has no time filter, so it still finds the row and `hasAnyRuns` stays true.
+const emptyPageWindow = (): { to: number } => ({ to: Date.now() - 60 * 60 * 1000 });
 
 describe("NextRunListPresenter dual-DB empty-state probe + routed hydrate (legacy + new Postgres)", () => {
   // no-false-empty. Runs ONLY on legacy, none on new. Empty CH page -> listRuns returns [].
@@ -209,7 +219,7 @@ describe("NextRunListPresenter dual-DB empty-state probe + routed hydrate (legac
         const result = await presenter.call(
           ctx.organizationId,
           ctx.environmentId,
-          callOptions(ctx)
+          callOptions(ctx, emptyPageWindow())
         );
 
         // CH id-set is empty within the page window, but the legacy probe finds the row.
@@ -337,7 +347,11 @@ describe("NextRunListPresenter dual-DB empty-state probe + routed hydrate (legac
       // (passthrough) and the probe is one plain `this.replica.taskRun.findFirst`.
       const presenter = new NextRunListPresenter(prisma, clickhouse);
 
-      const result = await presenter.call(ctx.organizationId, ctx.environmentId, callOptions(ctx));
+      const result = await presenter.call(
+        ctx.organizationId,
+        ctx.environmentId,
+        callOptions(ctx, emptyPageWindow())
+      );
 
       expect(result.runs).toHaveLength(0);
       expect(result.hasAnyRuns).toBe(true);

apps/webapp/test/setup.ts

@@ -140,6 +140,22 @@ vi.mock("~/services/taskMetadataCacheInstance.server", async () => {
   return { taskMetadataCacheInstance: new NoopTaskMetadataCache() };
 });
 
+// The org-data-stores registry singleton is constructed at import (transitively via
+// the ClickHouse factory instance, which many presenters pull in). Its ctor fires a
+// `forever` pRetry(loadFromDatabase) plus a setInterval reload against db.server's
+// $replica; in CI (no Postgres) those retry forever, blocking the worker until any
+// awaiting test's hook times out. Stub the instance to a no-op — no unit test uses
+// this singleton (the registry-behavior tests construct the class directly).
+vi.mock("~/services/dataStores/organizationDataStoresRegistryInstance.server", () => ({
+  organizationDataStoresRegistry: {
+    isReady: Promise.resolve(),
+    isLoaded: true,
+    get: vi.fn().mockReturnValue(null),
+    reload: vi.fn().mockResolvedValue(undefined),
+    loadFromDatabase: vi.fn().mockResolvedValue(undefined),
+  },
+}));
+
 vi.mock("~/v3/runEngine.server", () => ({ engine: noopProxy() }));
 vi.mock("~/v3/marqs/index.server", () => ({ marqs: noopProxy(), MarQS: class {} }));
 vi.mock("~/v3/marqs/devPubSub.server", () => ({ devPubSub: noopProxy() }));