chore: bump vitest to 5.0.0

Vitest, @vitest/ui and @vitest/coverage-v8 move to 5.0.0 in the root and
the mobile app. vitest-native already supports 5, so it stays at 0.9.

Vitest 5 dropped the bridge from its Assertion type into the global
jest.Matchers namespace. Both matcher libraries we use type themselves
there, so without the bridge every custom matcher fails typecheck while
passing at runtime:

- jest-dom: the tsconfig.spec.json `types` entries switch from
  "@testing-library/jest-dom" (jest globals) to
  "@testing-library/jest-dom/vitest", which augments vitest directly.
- React Native Testing Library ships no vitest entry, so
  apps/mobile/vitest-env.d.ts re-attaches jest.Matchers to vitest's
  Assertion.

The dead vitest.workspace.ts (dropped by vitest 4) becomes a root
vitest.config.ts with a projects list, excluding the backend vite configs
that would otherwise duplicate the vitest ones. .vitest/ is ignored.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

Author: prc5

.gitignore

@@ -57,4 +57,6 @@ test-output
 apps/*/src/db/postgres/generated/
 
 # Workflow run artifacts (generated files)
-workflow-runs/
+workflow-runs/
+# vitest 5 default artifact directory (attachments, blob/json/junit output)
+.vitest/

apps/admin/tsconfig.spec.json

@@ -3,7 +3,14 @@
   "compilerOptions": {
     "outDir": "./out-tsc/vitest",
     "rootDir": "../..",
-    "types": ["vitest/globals", "vitest/importMeta", "vite/client", "node", "vitest", "@testing-library/jest-dom"],
+    "types": [
+      "vitest/globals",
+      "vitest/importMeta",
+      "vite/client",
+      "node",
+      "vitest",
+      "@testing-library/jest-dom/vitest"
+    ],
     "jsx": "react-jsx",
     "strict": true,
     "composite": false,

apps/extension/tsconfig.spec.json

@@ -3,7 +3,14 @@
   "compilerOptions": {
     "outDir": "./out-tsc/vitest",
     "rootDir": "../..",
-    "types": ["vitest/globals", "vitest/importMeta", "vite/client", "node", "vitest", "@testing-library/jest-dom"],
+    "types": [
+      "vitest/globals",
+      "vitest/importMeta",
+      "vite/client",
+      "node",
+      "vitest",
+      "@testing-library/jest-dom/vitest"
+    ],
     "jsx": "react-jsx",
     "strict": true,
     "composite": false,

apps/frontend/tsconfig.spec.json

@@ -3,7 +3,14 @@
   "compilerOptions": {
     "outDir": "./out-tsc/vitest",
     "rootDir": "../..",
-    "types": ["vitest/globals", "vitest/importMeta", "vite/client", "node", "vitest", "@testing-library/jest-dom"],
+    "types": [
+      "vitest/globals",
+      "vitest/importMeta",
+      "vite/client",
+      "node",
+      "vitest",
+      "@testing-library/jest-dom/vitest"
+    ],
     "jsx": "react-jsx",
     "strict": true,
     "composite": false,

apps/mobile/package.json

@@ -84,7 +84,7 @@
     "@types/react": "19.2.14",
     "react-test-renderer": "19.2.3",
     "vite": "8.0.10",
-    "vitest": "^4.1.5",
+    "vitest": "^5.0.0",
     "vitest-native": "^0.9.0"
   },
   "nx": {

apps/mobile/tsconfig.json

@@ -16,6 +16,6 @@
       "@prisma/client": ["../backend/src/db/postgres/generated/client"]
     }
   },
-  "include": ["**/*.ts", "**/*.tsx", ".expo/types/**/*.ts", "expo-env.d.ts", "nativewind-env.d.ts"],
+  "include": ["**/*.ts", "**/*.tsx", ".expo/types/**/*.ts", "expo-env.d.ts", "nativewind-env.d.ts", "vitest-env.d.ts"],
   "exclude": ["node_modules", ".expo", "dist"]
 }

apps/mobile/vitest-env.d.ts

@@ -0,0 +1,14 @@
+/*
+ * React Native Testing Library types its matchers (toHaveTextContent, toBeOnTheScreen, ...) onto
+ * the global `jest.Matchers` namespace. Vitest 4 extended its own `Assertion` from that namespace,
+ * so the matchers were typed for free. Vitest 5 dropped that bridge, and without it every
+ * `expect(el).toHaveTextContent(...)` fails typecheck even though it passes at runtime.
+ *
+ * The import loads RNTL's global declaration; the augmentation re-attaches it to vitest.
+ */
+// oxlint-disable-next-line no-unassigned-import -- loads RNTL's global jest.Matchers declaration
+import "@testing-library/react-native";
+
+declare module "vitest" {
+  interface Assertion<R, T> extends jest.Matchers<R, T> {}
+}

package.json

@@ -51,14 +51,14 @@
     "@testing-library/user-event": "^14.6.1",
     "@types/node": "^25.6.0",
     "@typescript/native": "npm:typescript@^7.0.2",
-    "@vitest/coverage-v8": "4.1.5",
-    "@vitest/ui": "4.1.5",
+    "@vitest/coverage-v8": "5.0.0",
+    "@vitest/ui": "5.0.0",
     "nx": "23.1.2",
     "oxfmt": "^0.46.0",
     "oxlint": "^1.61.0",
     "typescript": "npm:@typescript/typescript6@^6.0.2",
     "vite": "8.0.10",
-    "vitest": "^4.1.5"
+    "vitest": "^5.0.0"
   },
   "workspaces": [
     "apps/*",

pnpm-lock.yaml

@@ -39,3 +39,12 @@ allowBuilds:
   nx: false
   prisma: false
   unrs-resolver: false
+
+minimumReleaseAgeExclude:
+  - "@vitest/coverage-v8@5.0.0"
+  - "@vitest/mocker@5.0.0"
+  - "@vitest/pretty-format@5.0.0"
+  - "@vitest/spy@5.0.0"
+  - "@vitest/ui@5.0.0"
+  - "@vitest/utils@5.0.0"
+  - vitest@5.0.0