fix(webapp): isolate runTableV2Status from its poller under test; qualify publication probe by schema

Code-review follow-ups on the v2 hardening:
- runTableV2Status no longer starts its background poller under vitest
  (NODE_ENV=test). The module is imported by the mint/read sites, so the
  import-time poll plus setInterval was firing live DB queries against the test
  database and leaking a timer, and the async refresh could race tests that
  drive the cached status directly. Tests exercise the gates by mutating the
  cached state, so the poller only gets in the way.
- The publication-readiness probe now filters pg_publication_tables on
  schemaname = "public", so a same-named table in another published schema
  cannot satisfy the check.

Author: d-cs

apps/webapp/app/v3/runTableV2Status.server.ts

@@ -38,6 +38,15 @@ const status = singleton("runTableV2Status", initialize);
 function initialize(): RunTableV2Status {
   const state: RunTableV2Status = { published: false, hasRows: false };
 
+  // No background poller under vitest: this module is imported by the mint/read
+  // sites, so a live DB poll + setInterval at import time would query the test
+  // database and leak a timer for the test run, and the async refresh could race
+  // tests that drive the cached status directly. Tests exercise the gates by
+  // mutating the cached state, so the poller would only get in the way.
+  if (env.NODE_ENV === "test") {
+    return state;
+  }
+
   // The publication only exists when runs replication is configured. Without it
   // no v2 run can be captured by ClickHouse, so leave published=false: minting
   // stays on legacy regardless of org flags.
@@ -51,6 +60,7 @@ function initialize(): RunTableV2Status {
         SELECT EXISTS (
           SELECT 1 FROM pg_publication_tables
           WHERE pubname = ${env.RUN_REPLICATION_PUBLICATION_NAME}
+            AND schemaname = 'public'
             AND tablename = 'task_run_v2'
         ) AS present`;
       state.published = published[0]?.present ?? false;

apps/webapp/test/runTableV2Status.test.ts

@@ -2,9 +2,10 @@ import { describe, expect, it } from "vitest";
 import { canMintV2Run, v2RunsMayExist } from "~/v3/runTableV2Status.server";
 
 // The module caches its status in a globalThis singleton ("runTableV2Status").
-// In the unit-test env runs replication is unconfigured, so it initializes to
-// { published:false, hasRows:false } with no background poller. Mutate that
-// cached object to exercise the gates deterministically.
+// Under vitest (NODE_ENV=test) it skips the background poller entirely and
+// initializes to { published:false, hasRows:false } — so no live DB query, no
+// leaked interval, and nothing races these assertions. Mutate that cached
+// object to exercise the gates deterministically.
 function setStatus(published: boolean, hasRows: boolean) {
   const singletons = (globalThis as any).__trigger_singletons;
   // Force module init (the singleton is created on first getter call/import).