ranstack query fixes

vitest.config.integration.ts

@@ -2,6 +2,8 @@
 import { defineConfig, mergeConfig } from 'vitest/config';
 import type { UserConfig } from 'vite';
 import viteConfig from './vite.config';
+import * as fs from 'fs';
+import * as path from 'path';
 
 // Ensure NODE_ENV is set to 'test' for all Vitest runs.
 process.env.NODE_ENV = 'test';
@@ -9,7 +11,21 @@ process.env.NODE_ENV = 'test';
 // 1. Separate the 'test' config (which has Unit Test settings)
 //    from the rest of the general Vite config (plugins, aliases, etc.)
 // DEBUG: Use console.error to ensure logs appear in CI/CD output
-console.error('[DEBUG] Loading vitest.config.integration.ts...');
+console.error(`[DEBUG] Loading vitest.config.integration.ts at ${new Date().toISOString()}...`);
+console.error(`[DEBUG] CWD: ${process.cwd()}`);
+
+// Check if the integration test directory exists and list its contents
+const integrationTestDir = path.resolve(process.cwd(), 'src/tests/integration');
+try {
+  const files = fs.readdirSync(integrationTestDir);
+  console.error(
+    `[DEBUG] Integration test directory (${integrationTestDir}) contains ${files.length} files:`,
+  );
+  files.forEach((f) => console.error(`[DEBUG]   - ${f}`));
+} catch (e) {
+  console.error(`[DEBUG] ERROR: Could not read integration test directory: ${integrationTestDir}`);
+  console.error(`[DEBUG] Error: ${e instanceof Error ? e.message : String(e)}`);
+}
 
 // Define a type that includes the 'test' property from Vitest's config.
 // This allows us to destructure it in a type-safe way without using 'as any'.