ci(web): exclude #374-blocked tests from vitest module discovery

describe.skip inside the file doesn't help — the SvelteKit
`notifiable_store is not a function` failure happens at module-load,
before vitest evaluates describe blocks. Add the two paths to
vitest's exclude list so the files aren't loaded at all. The skip
markers stay inside the files as a triage signal for M7 #374.

web/vitest.config.ts

@@ -1,12 +1,25 @@
 import { sveltekit } from '@sveltejs/kit/vite';
 import { svelteTesting } from '@testing-library/svelte/vite';
-import { defineConfig } from 'vitest/config';
+import { configDefaults, defineConfig } from 'vitest/config';
 
 export default defineConfig({
   plugins: [sveltekit(), svelteTesting()],
   test: {
     environment: 'jsdom',
     include: ['src/**/*.test.ts', 'src/**/*.svelte.test.ts'],
+    // M7 #374: these two test files explode at module-load with
+    // `TypeError: notifiable_store is not a function` from SvelteKit's
+    // internal client.js — the import chain triggers SvelteKit's client
+    // runtime init in a way the dev-push vitest invocation can't satisfy.
+    // describe.skip inside the files doesn't help because vitest must
+    // load the file before it can see the describe block. Excluded here
+    // until the triage in #374 lands a real fix (probably a $app/paths
+    // mock in vitest.setup.ts).
+    exclude: [
+      ...configDefaults.exclude,
+      'src/routes/discover/discover.test.ts',
+      'src/routes/requests/requests.test.ts'
+    ],
     setupFiles: ['./vitest.setup.ts']
   }
 });