fix: the Cloud live run stops collecting the Service Management suites

`vitest.config.live.ts` globs everything under tests/live and excluded tests/live/server for exactly this reason —
those need a container brought up first, under their own config and their own global setup. tests/live/jsm needed
the same line and did not get it, so the Cloud run collected thirty-four tests whose fixtures this run's global setup
never provides and which failed on `undefined`.

The comment now names the rule rather than the one directory, so the next self-hosted surface is not a third
instance of this.

Author: MrRefactoring

vitest.config.live.ts

@@ -6,10 +6,13 @@ const repoRoot = import.meta.dirname;
 
 export default defineConfig(({ mode }) => ({
   test: {
-    // Not `tests/live/server` — those run against a container that has to be brought up first, under their own
-    // config and their own global setup. Left in, every one of them fails with a connection refused.
+    // Every suite that runs against a container of its own is excluded here, because each has its own config and its
+    // own global setup and the container has to be brought up first: `tests/live/server` needs `pnpm jira-dc:up`,
+    // `tests/live/jsm` needs `pnpm jsm-dc:up`. Left in, they do not merely fail — they fail with `undefined` where
+    // their fixtures should be, because this run's global setup provides different ones. A new self-hosted surface
+    // belongs on this list the day its directory appears.
     include: ['tests/live/**/*.test.ts'],
-    exclude: ['tests/live/server/**'],
+    exclude: ['tests/live/server/**', 'tests/live/jsm/**'],
     environment: 'node',
     reporters: ['verbose'],
     env: loadEnv(mode, repoRoot, ''),