Problem
PRs #106 and #107 set isolate: true in backend/vitest.config.ts to ensure each test file runs in its own module registry. PRs #108 and #109 added vitest configs without this flag, relying instead on inline vi.resetModules() calls per test.
This inconsistency means module state could leak between test files in PRs #108/#109 if tests are added in the future that don't call vi.resetModules() manually.
Fix
Add isolate: true to backend/vitest.config.ts in both the fix/101-102-storage-improvements and fix/103-auth-client-singleton branches.
Affected
Problem
PRs #106 and #107 set
isolate: trueinbackend/vitest.config.tsto ensure each test file runs in its own module registry. PRs #108 and #109 added vitest configs without this flag, relying instead on inlinevi.resetModules()calls per test.This inconsistency means module state could leak between test files in PRs #108/#109 if tests are added in the future that don't call
vi.resetModules()manually.Fix
Add
isolate: truetobackend/vitest.config.tsin both thefix/101-102-storage-improvementsandfix/103-auth-client-singletonbranches.Affected
fix/101-102-storage-improvements→ PR fix: S3Client singleton and R2 error logging #108fix/103-auth-client-singleton→ PR fix: singleton Supabase admin client in requireAuth middleware #109