@warlock.js/core 4.13.0 → 4.14.0

package/esm/tests/vitest-setup.d.mts

@@ -1,14 +1,70 @@
-import { ConnectorName } from "../connectors/types.mjs";
+import { TestConnectorsSelection } from "./test-connectors-selection.mjs";
+
 //#region ../core/src/tests/vitest-setup.d.ts
-type TestSetup = {
-  connectors?: boolean | ConnectorName[];
+type TestSetupOptions = {
+  /**
+   * Which connectors to start.
+   *
+   * Precedence is `explicit non-undefined option > tests.connectors config >
+   * true`. Omitting the property, or passing `undefined`, lets project config
+   * apply — so an optional variable that happens to be `undefined` cannot erase
+   * it.
+   */
+  connectors?: TestConnectorsSelection;
 };
 /**
- * Setup function that runs once per worker thread
+ * Raised by the lifecycle itself, never by the runtime it manages — a conflict
+ * between two calls, or a refusal to reuse a runtime that did not close.
  */
-declare function setupTest({
-  connectors
-}?: TestSetup): Promise<void>;
+declare class TestLifecycleError extends Error {
+  constructor(message: string);
+}
+/**
+ * Bootstrap the test runtime and start the selected connectors.
+ *
+ * ⚠ Runs once per TEST FILE, not once per worker: `setupFiles` is executed for
+ * every file and its module registry is rebuilt with it, measured across both
+ * pools with isolation on and off. The lifecycle state lives on the runtime
+ * context rather than in this module precisely so that a rebuild cannot hide a
+ * runtime that is still up.
+ *
+ * Repeated calls:
+ *
+ * - concurrent calls with the same effective selection share one startup;
+ * - while ready, the same effective selection is a no-op;
+ * - while starting or ready, a DIFFERENT effective selection rejects and leaves
+ *   the live runtime untouched;
+ * - a failed setup unwinds and returns to idle, so a clean retry is allowed;
+ * - after a successful `teardownTest`, a later setup may use a different
+ *   selection.
+ *
+ * @example
+ * // let project config decide, falling back to the default set
+ * await setupTest();
+ *
+ * @example
+ * // bootstrap only — no connectors, whatever config says
+ * await setupTest({ connectors: false });
+ */
+declare function setupTest(options?: TestSetupOptions): Promise<void>;
+/**
+ * Shut the test runtime down and release the lifecycle.
+ *
+ * - idle is a no-op;
+ * - concurrent calls share one attempt;
+ * - a call made while setup is still running waits for that attempt to settle,
+ *   then closes the runtime if it succeeded;
+ * - the local "ready" state is always cleared, including when shutdown rejects;
+ * - a shutdown rejection is surfaced, never swallowed, and poisons the
+ *   lifecycle — a reported close failure is not proof that anything closed, so
+ *   later `setupTest` calls refuse until the worker is restarted or a retry
+ *   fully succeeds.
+ *
+ * ⚠ Individual connector shutdown failures are caught and logged inside
+ * `connectorsManager.shutdown()`, so they never reach this function and never
+ * poison anything. This lifecycle can only surface what that layer reports.
+ */
+declare function teardownTest(): Promise<void>;
 //#endregion
-export { setupTest };
+export { TestLifecycleError, TestSetupOptions, setupTest, teardownTest };
 //# sourceMappingURL=vitest-setup.d.mts.map

package/esm/tests/vitest-setup.d.mts.map

@@ -1 +1 @@
-{"version":3,"file":"vitest-setup.d.mts","names":[],"sources":["../../../../../../../core/src/tests/vitest-setup.ts"],"mappings":";;KAmBK,SAAA;EACH,UAAA,aAAuB,aAAa;AAAA;AAR2B;;;AAAA,iBAc3C,SAAA;EAAY;AAAA,IAAqB,SAAA,GAAc,OAAA"}
+{"version":3,"file":"vitest-setup.d.mts","names":[],"sources":["../../../../../../../core/src/tests/vitest-setup.ts"],"mappings":";;;KAoDY,gBAAA;EAAA;;;;AAS0B;AAOtC;;;EAPE,UAAA,GAAa,uBAAuB;AAAA;;;;AAQF;cADvB,kBAAA,SAA2B,KAAK;cACxB,OAAA;AAAA;;;;;;AAqC+C;AAgDpE;;;;AAA6C;;;;;;;;;;;;;;;;;iBAhDvB,SAAA,CAAU,OAAA,GAAU,gBAAA,GAAmB,OAAO;;;;;;;;;;;;;;;;;;iBAgD9C,YAAA,IAAgB,OAAO"}

package/esm/tests/vitest-setup.mjs

@@ -1,5 +1,3 @@
-import { config } from "../config/config-getter.mjs";
-import "../config/index.mjs";
 import { Application } from "../application/application.mjs";
 import { bootstrap } from "../bootstrap.mjs";
 import { connectorsManager } from "../connectors/connectors-manager.mjs";
@@ -7,30 +5,338 @@ import "../connectors/index.mjs";
 import { warlockConfigManager } from "../warlock-config/warlock-config.manager.mjs";
 import { filesOrchestrator } from "../dev-server/files-orchestrator.mjs";
 import { loadConfigFiles } from "../config/load-config-files.mjs";
+import { describeConnectorsSelection, isSameConnectorsSelection, normalizeConnectorNames, readRequestedConnectors, resolveEffectiveConnectors } from "./test-connectors-selection.mjs";
+import { getTestLifecycleRegistry } from "./test-lifecycle-state.mjs";
+import { DEFAULT_TEST_SETUP_TIMEOUT, describeExpiredSetup, readConfiguredSetupTimeout, scheduleRealTimeout } from "./test-setup-timeout.mjs";
 
 //#region ../core/src/tests/vitest-setup.ts
-let isSetupComplete = false;
 /**
-* Setup function that runs once per worker thread
+* Worker test lifecycle — `setupTest` / `teardownTest`.
+*
+* Implements `contracts/2026-08-12-test-worker-lifecycle.md`. The pair is
+* context-scoped, not "once per worker": Vitest runs `setupFiles` before EVERY
+* test file and rebuilds the module registry each time, so the harness that
+* calls `setupTest` owns pairing it with `teardownTest` in the same runtime
+* context.
+*
+* Ownership, stated once because teardown is wider than it looks:
+*
+* - the runtime assumes exclusive ownership of the process-local
+*   `connectorsManager` for its lifetime;
+* - it owns the framework bootstrap, the application shutdown hooks, and the
+*   connectors it starts — including the `connectors: false` case, where
+*   bootstrap still registers hooks;
+* - teardown is MANAGER-WIDE. `connectorsManager.shutdown()` has no selective
+*   ownership handle, so a lifecycle that started two connectors still closes
+*   every connector the manager holds. Mixing `setupTest` with manual connector
+*   startup in the same process is unsupported for exactly that reason.
+* - HTTP global setup stays separately owned by `startHttpTestServer` /
+*   `stopHttpTestServer`.
 */
-async function setupTest({ connectors = true } = {}) {
-	if (isSetupComplete) return;
+/**
+* Raised by the lifecycle itself, never by the runtime it manages — a conflict
+* between two calls, or a refusal to reuse a runtime that did not close.
+*/
+var TestLifecycleError = class extends Error {
+	constructor(message) {
+		super(message);
+		this.name = "TestLifecycleError";
+	}
+};
+const POISONED_MESSAGE = "setupTest() refuses to start a test runtime: an earlier teardownTest() reported a shutdown failure, so the connectors, ports and pools it owned are not known to be closed. Restart the Vitest worker before setting up again, or call teardownTest() to retry the shutdown — the lifecycle only returns to idle on a fully successful retry.";
+/**
+* Bootstrap the test runtime and start the selected connectors.
+*
+* ⚠ Runs once per TEST FILE, not once per worker: `setupFiles` is executed for
+* every file and its module registry is rebuilt with it, measured across both
+* pools with isolation on and off. The lifecycle state lives on the runtime
+* context rather than in this module precisely so that a rebuild cannot hide a
+* runtime that is still up.
+*
+* Repeated calls:
+*
+* - concurrent calls with the same effective selection share one startup;
+* - while ready, the same effective selection is a no-op;
+* - while starting or ready, a DIFFERENT effective selection rejects and leaves
+*   the live runtime untouched;
+* - a failed setup unwinds and returns to idle, so a clean retry is allowed;
+* - after a successful `teardownTest`, a later setup may use a different
+*   selection.
+*
+* @example
+* // let project config decide, falling back to the default set
+* await setupTest();
+*
+* @example
+* // bootstrap only — no connectors, whatever config says
+* await setupTest({ connectors: false });
+*/
+async function setupTest(options) {
+	const registry = getTestLifecycleRegistry();
+	const requested = readRequestedConnectors(options?.connectors);
+	if (registry.state === "poisoned") throw new TestLifecycleError(POISONED_MESSAGE);
+	if (registry.state === "stopping" && registry.teardownAttempt) {
+		await settled(registry.teardownAttempt);
+		return setupTest(options);
+	}
+	if (registry.state === "ready") {
+		assertReadySelectionMatches(registry.activeSelection, requested);
+		return;
+	}
+	if (registry.state === "starting" && registry.setupAttempt) {
+		const attempt = registry.setupAttempt;
+		await assertPendingSetupMatches(attempt, requested);
+		return attempt.completion;
+	}
+	return startTestRuntime(requested);
+}
+/**
+* Shut the test runtime down and release the lifecycle.
+*
+* - idle is a no-op;
+* - concurrent calls share one attempt;
+* - a call made while setup is still running waits for that attempt to settle,
+*   then closes the runtime if it succeeded;
+* - the local "ready" state is always cleared, including when shutdown rejects;
+* - a shutdown rejection is surfaced, never swallowed, and poisons the
+*   lifecycle — a reported close failure is not proof that anything closed, so
+*   later `setupTest` calls refuse until the worker is restarted or a retry
+*   fully succeeds.
+*
+* ⚠ Individual connector shutdown failures are caught and logged inside
+* `connectorsManager.shutdown()`, so they never reach this function and never
+* poison anything. This lifecycle can only surface what that layer reports.
+*/
+async function teardownTest() {
+	const registry = getTestLifecycleRegistry();
+	if (registry.state === "stopping" && registry.teardownAttempt) return registry.teardownAttempt;
+	if (registry.state === "starting" && registry.setupAttempt) {
+		await settled(registry.setupAttempt.completion);
+		return teardownTest();
+	}
+	if (registry.state === "idle") return;
+	registry.state = "stopping";
+	const attempt = Promise.resolve().then(() => runTestRuntimeShutdown());
+	registry.teardownAttempt = attempt;
+	return attempt;
+}
+/**
+* Arm the hang guard for one setup attempt.
+*
+* Armed at the default BEFORE the attempt runs, because `tests.setupTimeout` is
+* not readable until the attempt has loaded config — and loading config is
+* itself one of the steps that can hang. `rearm` then narrows or widens it the
+* moment config arrives.
+*/
+function armSetupBound(registry) {
+	const schedule = registry.scheduleTimeout ?? scheduleRealTimeout;
+	const armedAt = Date.now();
+	let handle;
+	let expired = false;
+	let closed = false;
+	let expire = () => void 0;
+	const expiry = new Promise((_resolve, reject) => {
+		expire = reject;
+	});
+	expiry.catch(() => void 0);
+	const expireNow = (bound) => {
+		if (closed) return;
+		closed = true;
+		expired = true;
+		handle?.cancel();
+		handle = void 0;
+		expire(new TestLifecycleError(describeExpiredSetup(bound)));
+	};
+	const armFor = (bound, delay) => {
+		if (closed) return;
+		handle?.cancel();
+		if (delay <= 0) {
+			expireNow(bound);
+			return;
+		}
+		handle = schedule(delay, () => expireNow(bound));
+	};
+	const initialBound = registry.setupTimeoutOverride ?? 12e4;
+	armFor(initialBound, initialBound);
+	return {
+		expiry,
+		rearm: (next) => armFor(next, next - (Date.now() - armedAt)),
+		settle: () => {
+			closed = true;
+			handle?.cancel();
+			handle = void 0;
+		},
+		hasExpired: () => expired
+	};
+}
+/**
+* Race one setup attempt against its bound.
+*
+* The losing attempt is NOT cancellable — nothing here can interrupt a bootstrap
+* stuck in a socket connect — so when the bound wins, the lifecycle is poisoned
+* and every later state write from that abandoned attempt is dropped. That
+* dropping happens in `runTestRuntimeStartup`, guarded on `hasExpired()`;
+* without it the still-running attempt would quietly overwrite `poisoned` with
+* `ready` or `idle` and hand the next caller a runtime nobody owns.
+*/
+async function awaitSetupWithinBound(attempt, bound, registry) {
+	try {
+		await Promise.race([attempt, bound.expiry]);
+	} catch (error) {
+		if (bound.hasExpired()) {
+			registry.state = "poisoned";
+			registry.activeSelection = void 0;
+			registry.setupAttempt = void 0;
+		}
+		throw error;
+	} finally {
+		bound.settle();
+	}
+}
+/**
+* Open a new setup attempt and publish it before it runs.
+*/
+function startTestRuntime(requested) {
+	const registry = getTestLifecycleRegistry();
+	let publishEffectiveSelection = () => void 0;
+	let failEffectiveSelection = () => void 0;
+	const effectiveSelection = new Promise((resolve, reject) => {
+		publishEffectiveSelection = resolve;
+		failEffectiveSelection = reject;
+	});
+	effectiveSelection.catch(() => void 0);
+	const bound = armSetupBound(registry);
+	const attempt = Promise.resolve().then(() => runTestRuntimeStartup(requested, publishEffectiveSelection, failEffectiveSelection, bound));
+	attempt.catch(() => void 0);
+	const completion = awaitSetupWithinBound(attempt, bound, registry);
+	registry.state = "starting";
+	registry.setupAttempt = {
+		requested,
+		effectiveSelection,
+		completion
+	};
+	return completion;
+}
+/**
+* The startup attempt itself.
+*
+* On failure: best-effort unwind, reset bookkeeping, rethrow the ORIGINAL error
+* unchanged. A cleanup failure is a secondary diagnostic and never replaces the
+* cause the caller needs to read.
+*/
+async function runTestRuntimeStartup(requested, publishEffectiveSelection, failEffectiveSelection, bound) {
+	const registry = getTestLifecycleRegistry();
 	try {
 		Application.setEnvironment("test");
 		await warlockConfigManager.load();
 		await bootstrap();
 		await filesOrchestrator.init();
 		await loadConfigFiles(true);
-		const connectorsToStart = config.get("tests", {})?.connectors ?? connectors;
-		if (connectorsToStart !== false) if (Array.isArray(connectorsToStart)) await connectorsManager.start(connectorsToStart);
-		else await connectorsManager.startWithout(["http"]);
-		isSetupComplete = true;
+		const configuredTimeout = readConfiguredSetupTimeout();
+		if (configuredTimeout !== void 0) bound.rearm(configuredTimeout);
+		const effectiveSelection = resolveEffectiveConnectors(requested);
+		if (!bound.hasExpired()) registry.activeSelection = effectiveSelection;
+		publishEffectiveSelection(effectiveSelection);
+		await startSelectedConnectors(effectiveSelection);
+		if (!bound.hasExpired()) {
+			registry.state = "ready";
+			registry.setupAttempt = void 0;
+		}
 	} catch (error) {
+		failEffectiveSelection(error);
+		await unwindPartialStartup();
+		if (!bound.hasExpired()) {
+			registry.state = "idle";
+			registry.activeSelection = void 0;
+			registry.setupAttempt = void 0;
+		}
 		console.error("[vitest-setup] Failed to setup test environment:", error);
 		throw error;
 	}
 }
+/**
+* `false` means none at all. Everything else starts something: an array starts
+* exactly those, and `true` starts the default set — all but http, which is the
+* global setup's job and shared across every worker.
+*/
+async function startSelectedConnectors(selection) {
+	if (selection === false) return;
+	if (Array.isArray(selection)) {
+		await connectorsManager.start(normalizeConnectorNames(selection));
+		return;
+	}
+	await connectorsManager.startWithout(["http"]);
+}
+/**
+* Best-effort teardown of whatever a failed startup managed to start.
+*
+* Runs while an error is already in flight, so no step here may throw and every
+* step is attempted independently.
+*/
+async function unwindPartialStartup() {
+	await attemptCleanupStep("application shutdown hooks", () => Application.runShutdownHooks());
+	await attemptCleanupStep("connectors shutdown", () => connectorsManager.shutdown());
+}
+/**
+* Run one cleanup step, isolating its failure so the next step still runs.
+*/
+async function attemptCleanupStep(step, run) {
+	try {
+		await run();
+	} catch (error) {
+		console.error(`[vitest-setup] Cleanup after a failed setup did not complete (${step}):`, error);
+	}
+}
+/**
+* The teardown attempt itself.
+*/
+async function runTestRuntimeShutdown() {
+	const registry = getTestLifecycleRegistry();
+	let shutdownSucceeded = false;
+	try {
+		await connectorsManager.shutdown();
+		shutdownSucceeded = true;
+	} finally {
+		registry.activeSelection = void 0;
+		registry.setupAttempt = void 0;
+		registry.teardownAttempt = void 0;
+		registry.state = shutdownSucceeded ? "idle" : "poisoned";
+	}
+}
+/**
+* Reject when a ready runtime was set up with a different selection.
+*/
+function assertReadySelectionMatches(activeSelection, requested) {
+	if (activeSelection === void 0) return;
+	assertSelectionsMatch(activeSelection, resolveEffectiveConnectors(requested));
+}
+/**
+* Reject when an in-flight setup attempt is starting a different selection.
+*/
+async function assertPendingSetupMatches(attempt, requested) {
+	const pending = attempt.requested;
+	if (!pending.isExplicit && !requested.isExplicit) return;
+	if (pending.isExplicit && requested.isExplicit) {
+		assertSelectionsMatch(pending.selection, requested.selection);
+		return;
+	}
+	assertSelectionsMatch(await attempt.effectiveSelection, resolveEffectiveConnectors(requested));
+}
+/**
+* Name both selections: a caller looking at this message has to be able to tell
+* which call to change without reading the framework's source.
+*/
+function assertSelectionsMatch(activeSelection, requestedSelection) {
+	if (isSameConnectorsSelection(activeSelection, requestedSelection)) return;
+	throw new TestLifecycleError(`setupTest() is already using ${describeConnectorsSelection(activeSelection)}, and this call asked for ${describeConnectorsSelection(requestedSelection)}. One test runtime serves one connector selection — call teardownTest() before setting up a different one.`);
+}
+/**
+* Await an attempt for its state transition only, not its result.
+*/
+function settled(attempt) {
+	return attempt.catch(() => void 0);
+}
 
 //#endregion
-export { setupTest };
+export { TestLifecycleError, setupTest, teardownTest };
 //# sourceMappingURL=vitest-setup.mjs.map

package/esm/tests/vitest-setup.mjs.map

@@ -1 +1 @@
-{"version":3,"file":"vitest-setup.mjs","names":[],"sources":["../../../../../../../core/src/tests/vitest-setup.ts"],"sourcesContent":["/**\n * Vitest Setup File\n *\n * This file runs in each Vitest worker thread before tests execute.\n * It bootstraps the framework and starts necessary connectors so tests\n * have access to database connections and other shared resources.\n */\nimport { GenericObject } from \"@mongez/reinforcements\";\nimport { Application } from \"../application/application\";\nimport { bootstrap } from \"../bootstrap\";\nimport { config } from \"../config\";\nimport { loadConfigFiles } from \"../config/load-config-files\";\nimport { ConnectorName, connectorsManager } from \"../connectors\";\nimport { filesOrchestrator } from \"../dev-server/files-orchestrator\";\nimport { warlockConfigManager } from \"../warlock-config/warlock-config.manager\";\n\n// Global flag to prevent duplicate setup within the same worker\nlet isSetupComplete = false;\n\ntype TestSetup = {\n  connectors?: boolean | ConnectorName[];\n};\n\n/**\n * Setup function that runs once per worker thread\n */\nexport async function setupTest({ connectors = true }: TestSetup = {}) {\n  // Skip if already set up in this worker\n  if (isSetupComplete) {\n    return;\n  }\n\n  try {\n    // 1. Set environment to test\n    Application.setEnvironment(\"test\");\n\n    await warlockConfigManager.load();\n    await bootstrap();\n\n    await filesOrchestrator.init();\n    await loadConfigFiles(true);\n\n    // 2. Load test configuration.\n    //\n    // The default matters: `config.get` resolves an absent key to its default,\n    // and ITS default is `null` — not `{}`. `warlock add test` does not generate\n    // `src/config/tests.ts`, so reading `.connectors` off the result threw\n    // \"Cannot read properties of null\" on the generated default path.\n    const testConfig = config.get<GenericObject>(\"tests\", {});\n\n    // 3. Choose the connectors.\n    //\n    // `??`, not `||`: `false` is a meaningful configured value (\"start none\")\n    // and `||` discarded it, falling through to the branch that starts\n    // everything. The type and the skill both document `false` as \"start none\",\n    // so the old behaviour was the exact opposite of the promise.\n    const connectorsToStart = testConfig?.connectors ?? connectors;\n\n    // `false` means none at all. Everything else starts something: an array\n    // starts exactly those, and `true` starts all but http — http is the global\n    // setup's job, shared across every worker.\n    if (connectorsToStart !== false) {\n      if (Array.isArray(connectorsToStart)) {\n        await connectorsManager.start(connectorsToStart);\n      } else {\n        await connectorsManager.startWithout([\"http\"]);\n      }\n    }\n\n    // Set even when no connectors were started: setup DID complete, and a second\n    // call in the same worker must stay a no-op either way.\n    isSetupComplete = true;\n  } catch (error) {\n    console.error(\"[vitest-setup] Failed to setup test environment:\", error);\n    throw error;\n  }\n}\n"],"mappings":";;;;;;;;;;;AAiBA,IAAI,kBAAkB;;;;AAStB,eAAsB,UAAU,EAAE,aAAa,SAAoB,CAAC,GAAG;CAErE,IAAI,iBACF;CAGF,IAAI;EAEF,YAAY,eAAe,MAAM;EAEjC,MAAM,qBAAqB,KAAK;EAChC,MAAM,UAAU;EAEhB,MAAM,kBAAkB,KAAK;EAC7B,MAAM,gBAAgB,IAAI;EAgB1B,MAAM,oBARa,OAAO,IAAmB,SAAS,CAAC,CAQpB,CAAC,EAAE,cAAc;EAKpD,IAAI,sBAAsB,OACxB,IAAI,MAAM,QAAQ,iBAAiB,GACjC,MAAM,kBAAkB,MAAM,iBAAiB;OAE/C,MAAM,kBAAkB,aAAa,CAAC,MAAM,CAAC;EAMjD,kBAAkB;CACpB,SAAS,OAAO;EACd,QAAQ,MAAM,oDAAoD,KAAK;EACvE,MAAM;CACR;AACF"}
+{"version":3,"file":"vitest-setup.mjs","names":[],"sources":["../../../../../../../core/src/tests/vitest-setup.ts"],"sourcesContent":["/**\r\n * Worker test lifecycle — `setupTest` / `teardownTest`.\r\n *\r\n * Implements `contracts/2026-08-12-test-worker-lifecycle.md`. The pair is\r\n * context-scoped, not \"once per worker\": Vitest runs `setupFiles` before EVERY\r\n * test file and rebuilds the module registry each time, so the harness that\r\n * calls `setupTest` owns pairing it with `teardownTest` in the same runtime\r\n * context.\r\n *\r\n * Ownership, stated once because teardown is wider than it looks:\r\n *\r\n * - the runtime assumes exclusive ownership of the process-local\r\n *   `connectorsManager` for its lifetime;\r\n * - it owns the framework bootstrap, the application shutdown hooks, and the\r\n *   connectors it starts — including the `connectors: false` case, where\r\n *   bootstrap still registers hooks;\r\n * - teardown is MANAGER-WIDE. `connectorsManager.shutdown()` has no selective\r\n *   ownership handle, so a lifecycle that started two connectors still closes\r\n *   every connector the manager holds. Mixing `setupTest` with manual connector\r\n *   startup in the same process is unsupported for exactly that reason.\r\n * - HTTP global setup stays separately owned by `startHttpTestServer` /\r\n *   `stopHttpTestServer`.\r\n */\r\nimport { Application } from \"../application/application\";\r\nimport { bootstrap } from \"../bootstrap\";\r\nimport { loadConfigFiles } from \"../config/load-config-files\";\r\nimport { connectorsManager } from \"../connectors\";\r\nimport { filesOrchestrator } from \"../dev-server/files-orchestrator\";\r\nimport { warlockConfigManager } from \"../warlock-config/warlock-config.manager\";\r\nimport {\r\n  describeConnectorsSelection,\r\n  isSameConnectorsSelection,\r\n  normalizeConnectorNames,\r\n  readRequestedConnectors,\r\n  resolveEffectiveConnectors,\r\n} from \"./test-connectors-selection\";\r\nimport type {\r\n  RequestedTestConnectors,\r\n  TestConnectorsSelection,\r\n} from \"./test-connectors-selection\";\r\nimport { getTestLifecycleRegistry } from \"./test-lifecycle-state\";\r\nimport type { TestLifecycleRegistry, TestSetupAttempt } from \"./test-lifecycle-state\";\r\nimport {\r\n  DEFAULT_TEST_SETUP_TIMEOUT,\r\n  describeExpiredSetup,\r\n  readConfiguredSetupTimeout,\r\n  scheduleRealTimeout,\r\n} from \"./test-setup-timeout\";\r\nimport type { TestTimeoutHandle } from \"./test-setup-timeout\";\r\n\r\nexport type { TestConnectorsSelection } from \"./test-connectors-selection\";\r\n\r\nexport type TestSetupOptions = {\r\n  /**\r\n   * Which connectors to start.\r\n   *\r\n   * Precedence is `explicit non-undefined option > tests.connectors config >\r\n   * true`. Omitting the property, or passing `undefined`, lets project config\r\n   * apply — so an optional variable that happens to be `undefined` cannot erase\r\n   * it.\r\n   */\r\n  connectors?: TestConnectorsSelection;\r\n};\r\n\r\n/**\r\n * Raised by the lifecycle itself, never by the runtime it manages — a conflict\r\n * between two calls, or a refusal to reuse a runtime that did not close.\r\n */\r\nexport class TestLifecycleError extends Error {\r\n  public constructor(message: string) {\r\n    super(message);\r\n\r\n    this.name = \"TestLifecycleError\";\r\n  }\r\n}\r\n\r\nconst POISONED_MESSAGE =\r\n  \"setupTest() refuses to start a test runtime: an earlier teardownTest() reported a shutdown failure, so the connectors, ports and pools it owned are not known to be closed. Restart the Vitest worker before setting up again, or call teardownTest() to retry the shutdown — the lifecycle only returns to idle on a fully successful retry.\";\r\n\r\n/**\r\n * Bootstrap the test runtime and start the selected connectors.\r\n *\r\n * ⚠ Runs once per TEST FILE, not once per worker: `setupFiles` is executed for\r\n * every file and its module registry is rebuilt with it, measured across both\r\n * pools with isolation on and off. The lifecycle state lives on the runtime\r\n * context rather than in this module precisely so that a rebuild cannot hide a\r\n * runtime that is still up.\r\n *\r\n * Repeated calls:\r\n *\r\n * - concurrent calls with the same effective selection share one startup;\r\n * - while ready, the same effective selection is a no-op;\r\n * - while starting or ready, a DIFFERENT effective selection rejects and leaves\r\n *   the live runtime untouched;\r\n * - a failed setup unwinds and returns to idle, so a clean retry is allowed;\r\n * - after a successful `teardownTest`, a later setup may use a different\r\n *   selection.\r\n *\r\n * @example\r\n * // let project config decide, falling back to the default set\r\n * await setupTest();\r\n *\r\n * @example\r\n * // bootstrap only — no connectors, whatever config says\r\n * await setupTest({ connectors: false });\r\n */\r\nexport async function setupTest(options?: TestSetupOptions): Promise<void> {\r\n  const registry = getTestLifecycleRegistry();\r\n  const requested = readRequestedConnectors(options?.connectors);\r\n\r\n  if (registry.state === \"poisoned\") {\r\n    throw new TestLifecycleError(POISONED_MESSAGE);\r\n  }\r\n\r\n  if (registry.state === \"stopping\" && registry.teardownAttempt) {\r\n    await settled(registry.teardownAttempt);\r\n\r\n    return setupTest(options);\r\n  }\r\n\r\n  if (registry.state === \"ready\") {\r\n    assertReadySelectionMatches(registry.activeSelection, requested);\r\n\r\n    return;\r\n  }\r\n\r\n  if (registry.state === \"starting\" && registry.setupAttempt) {\r\n    const attempt = registry.setupAttempt;\r\n\r\n    await assertPendingSetupMatches(attempt, requested);\r\n\r\n    return attempt.completion;\r\n  }\r\n\r\n  return startTestRuntime(requested);\r\n}\r\n\r\n/**\r\n * Shut the test runtime down and release the lifecycle.\r\n *\r\n * - idle is a no-op;\r\n * - concurrent calls share one attempt;\r\n * - a call made while setup is still running waits for that attempt to settle,\r\n *   then closes the runtime if it succeeded;\r\n * - the local \"ready\" state is always cleared, including when shutdown rejects;\r\n * - a shutdown rejection is surfaced, never swallowed, and poisons the\r\n *   lifecycle — a reported close failure is not proof that anything closed, so\r\n *   later `setupTest` calls refuse until the worker is restarted or a retry\r\n *   fully succeeds.\r\n *\r\n * ⚠ Individual connector shutdown failures are caught and logged inside\r\n * `connectorsManager.shutdown()`, so they never reach this function and never\r\n * poison anything. This lifecycle can only surface what that layer reports.\r\n */\r\nexport async function teardownTest(): Promise<void> {\r\n  const registry = getTestLifecycleRegistry();\r\n\r\n  if (registry.state === \"stopping\" && registry.teardownAttempt) {\r\n    return registry.teardownAttempt;\r\n  }\r\n\r\n  if (registry.state === \"starting\" && registry.setupAttempt) {\r\n    // A runtime that is still opening cannot be closed halfway. Wait for the\r\n    // attempt to settle: a failed one has already unwound itself and left the\r\n    // lifecycle idle, which the re-entry below then reads as \"nothing to do\".\r\n    await settled(registry.setupAttempt.completion);\r\n\r\n    return teardownTest();\r\n  }\r\n\r\n  if (registry.state === \"idle\") {\r\n    return;\r\n  }\r\n\r\n  registry.state = \"stopping\";\r\n\r\n  // Deferred by a microtask so the registry is fully published before the\r\n  // attempt's first line runs — a synchronous throw would otherwise reach the\r\n  // `finally` below, and reset the state, before this function had recorded\r\n  // that a teardown was in flight at all.\r\n  const attempt = Promise.resolve().then(() => runTestRuntimeShutdown());\r\n\r\n  registry.teardownAttempt = attempt;\r\n\r\n  return attempt;\r\n}\r\n\r\n/**\r\n * The setup attempt's hang guard, as the lifecycle consumes it.\r\n *\r\n * The bound's POLICY — the default, the config key, the message — lives in\r\n * `test-setup-timeout.ts`. What expiry MEANS lives here.\r\n *\r\n * @internal\r\n */\r\ntype SetupBound = {\r\n  /**\r\n   * Rejects with the expiry error. Never resolves: the attempt is the only side\r\n   * of the race that can succeed.\r\n   */\r\n  readonly expiry: Promise<never>;\r\n\r\n  /**\r\n   * Re-aim the bound at `next` ms measured from when the ATTEMPT STARTED, once\r\n   * config has made `tests.setupTimeout` readable.\r\n   */\r\n  rearm(next: number): void;\r\n\r\n  /** The race is over — cancel whatever timer is still pending. */\r\n  settle(): void;\r\n\r\n  /** Whether the bound, rather than the attempt, won the race. */\r\n  hasExpired(): boolean;\r\n};\r\n\r\n/**\r\n * Arm the hang guard for one setup attempt.\r\n *\r\n * Armed at the default BEFORE the attempt runs, because `tests.setupTimeout` is\r\n * not readable until the attempt has loaded config — and loading config is\r\n * itself one of the steps that can hang. `rearm` then narrows or widens it the\r\n * moment config arrives.\r\n */\r\nfunction armSetupBound(registry: TestLifecycleRegistry): SetupBound {\r\n  const schedule = registry.scheduleTimeout ?? scheduleRealTimeout;\r\n  const armedAt = Date.now();\r\n\r\n  let handle: TestTimeoutHandle | undefined;\r\n  let expired = false;\r\n  let closed = false;\r\n  let expire: (error: unknown) => void = () => undefined;\r\n\r\n  const expiry = new Promise<never>((_resolve, reject) => {\r\n    expire = reject;\r\n  });\r\n\r\n  // Only `awaitSetupWithinBound` observes this, and only until the attempt wins\r\n  // — after that nobody is listening, and an unobserved rejection surfaces as an\r\n  // unhandled rejection that fails an unrelated test file. Same reason as the\r\n  // `effectiveSelection` barrier below.\r\n  expiry.catch(() => undefined);\r\n\r\n  const expireNow = (bound: number): void => {\r\n    if (closed) {\r\n      return;\r\n    }\r\n\r\n    closed = true;\r\n    expired = true;\r\n\r\n    handle?.cancel();\r\n    handle = undefined;\r\n\r\n    expire(new TestLifecycleError(describeExpiredSetup(bound)));\r\n  };\r\n\r\n  const armFor = (bound: number, delay: number): void => {\r\n    if (closed) {\r\n      return;\r\n    }\r\n\r\n    handle?.cancel();\r\n\r\n    // Already overdue. A bound the attempt has ALREADY exceeded must fire now,\r\n    // not be rescheduled for time that was spent before it was known.\r\n    if (delay <= 0) {\r\n      expireNow(bound);\r\n\r\n      return;\r\n    }\r\n\r\n    handle = schedule(delay, () => expireNow(bound));\r\n  };\r\n\r\n  const initialBound = registry.setupTimeoutOverride ?? DEFAULT_TEST_SETUP_TIMEOUT;\r\n\r\n  armFor(initialBound, initialBound);\r\n\r\n  return {\r\n    expiry,\r\n\r\n    // Measured from `armedAt`, never from now: adding a configured bound to the\r\n    // time already spent would make the real bound default-plus-configured, and\r\n    // a project that lowered the key would get a LONGER guard than the default.\r\n    rearm: (next) => armFor(next, next - (Date.now() - armedAt)),\r\n\r\n    settle: () => {\r\n      closed = true;\r\n\r\n      handle?.cancel();\r\n      handle = undefined;\r\n    },\r\n\r\n    hasExpired: () => expired,\r\n  };\r\n}\r\n\r\n/**\r\n * Race one setup attempt against its bound.\r\n *\r\n * The losing attempt is NOT cancellable — nothing here can interrupt a bootstrap\r\n * stuck in a socket connect — so when the bound wins, the lifecycle is poisoned\r\n * and every later state write from that abandoned attempt is dropped. That\r\n * dropping happens in `runTestRuntimeStartup`, guarded on `hasExpired()`;\r\n * without it the still-running attempt would quietly overwrite `poisoned` with\r\n * `ready` or `idle` and hand the next caller a runtime nobody owns.\r\n */\r\nasync function awaitSetupWithinBound(\r\n  attempt: Promise<void>,\r\n  bound: SetupBound,\r\n  registry: TestLifecycleRegistry,\r\n): Promise<void> {\r\n  try {\r\n    await Promise.race([attempt, bound.expiry]);\r\n  } catch (error) {\r\n    if (bound.hasExpired()) {\r\n      registry.state = \"poisoned\";\r\n      registry.activeSelection = undefined;\r\n      registry.setupAttempt = undefined;\r\n    }\r\n\r\n    throw error;\r\n  } finally {\r\n    bound.settle();\r\n  }\r\n}\r\n\r\n/**\r\n * Open a new setup attempt and publish it before it runs.\r\n */\r\nfunction startTestRuntime(requested: RequestedTestConnectors): Promise<void> {\r\n  const registry = getTestLifecycleRegistry();\r\n\r\n  let publishEffectiveSelection: (selection: TestConnectorsSelection) => void = () => undefined;\r\n  let failEffectiveSelection: (error: unknown) => void = () => undefined;\r\n\r\n  const effectiveSelection = new Promise<TestConnectorsSelection>((resolve, reject) => {\r\n    publishEffectiveSelection = resolve;\r\n    failEffectiveSelection = reject;\r\n  });\r\n\r\n  // Only the mixed explicit/config comparison ever awaits this barrier, so its\r\n  // rejection is usually unobserved — and an unobserved rejection would surface\r\n  // as an unhandled rejection and fail an unrelated test file.\r\n  effectiveSelection.catch(() => undefined);\r\n\r\n  const bound = armSetupBound(registry);\r\n\r\n  const attempt = Promise.resolve().then(() =>\r\n    runTestRuntimeStartup(requested, publishEffectiveSelection, failEffectiveSelection, bound),\r\n  );\r\n\r\n  // The attempt outlives a bound that beat it, and by then `completion` has\r\n  // already rejected with the expiry error — so the attempt's own late rejection\r\n  // has no observer. Same unhandled-rejection hazard as above.\r\n  attempt.catch(() => undefined);\r\n\r\n  // `teardownTest` waits on this same promise, which is how a teardown requested\r\n  // during setup inherits the bound. There is deliberately no second timer and\r\n  // no separate teardown deadline.\r\n  const completion = awaitSetupWithinBound(attempt, bound, registry);\r\n\r\n  registry.state = \"starting\";\r\n  registry.setupAttempt = { requested, effectiveSelection, completion };\r\n\r\n  return completion;\r\n}\r\n\r\n/**\r\n * The startup attempt itself.\r\n *\r\n * On failure: best-effort unwind, reset bookkeeping, rethrow the ORIGINAL error\r\n * unchanged. A cleanup failure is a secondary diagnostic and never replaces the\r\n * cause the caller needs to read.\r\n */\r\nasync function runTestRuntimeStartup(\r\n  requested: RequestedTestConnectors,\r\n  publishEffectiveSelection: (selection: TestConnectorsSelection) => void,\r\n  failEffectiveSelection: (error: unknown) => void,\r\n  bound: SetupBound,\r\n): Promise<void> {\r\n  const registry = getTestLifecycleRegistry();\r\n\r\n  try {\r\n    Application.setEnvironment(\"test\");\r\n\r\n    await warlockConfigManager.load();\r\n    await bootstrap();\r\n\r\n    await filesOrchestrator.init();\r\n    await loadConfigFiles(true);\r\n\r\n    // The first point at which `tests.setupTimeout` is readable at all. An\r\n    // invalid value throws from here and takes the normal failure path — falling\r\n    // back to the default would silently erase what the project configured.\r\n    const configuredTimeout = readConfiguredSetupTimeout();\r\n\r\n    if (configuredTimeout !== undefined) {\r\n      bound.rearm(configuredTimeout);\r\n    }\r\n\r\n    // Resolved here and not at call time: the config layer is only readable once\r\n    // the four steps above have run.\r\n    const effectiveSelection = resolveEffectiveConnectors(requested);\r\n\r\n    // Every state write below is conditional on this attempt still being the one\r\n    // the lifecycle is waiting for. Once the bound has expired the lifecycle is\r\n    // poisoned and this attempt is abandoned — it may still be running, but it\r\n    // no longer speaks for the runtime.\r\n    if (!bound.hasExpired()) {\r\n      registry.activeSelection = effectiveSelection;\r\n    }\r\n\r\n    publishEffectiveSelection(effectiveSelection);\r\n\r\n    await startSelectedConnectors(effectiveSelection);\r\n\r\n    if (!bound.hasExpired()) {\r\n      registry.state = \"ready\";\r\n      registry.setupAttempt = undefined;\r\n    }\r\n  } catch (error) {\r\n    failEffectiveSelection(error);\r\n\r\n    await unwindPartialStartup();\r\n\r\n    if (!bound.hasExpired()) {\r\n      registry.state = \"idle\";\r\n      registry.activeSelection = undefined;\r\n      registry.setupAttempt = undefined;\r\n    }\r\n\r\n    console.error(\"[vitest-setup] Failed to setup test environment:\", error);\r\n\r\n    throw error;\r\n  }\r\n}\r\n\r\n/**\r\n * `false` means none at all. Everything else starts something: an array starts\r\n * exactly those, and `true` starts the default set — all but http, which is the\r\n * global setup's job and shared across every worker.\r\n */\r\nasync function startSelectedConnectors(selection: TestConnectorsSelection): Promise<void> {\r\n  if (selection === false) {\r\n    return;\r\n  }\r\n\r\n  if (Array.isArray(selection)) {\r\n    await connectorsManager.start(normalizeConnectorNames(selection));\r\n\r\n    return;\r\n  }\r\n\r\n  await connectorsManager.startWithout([\"http\"]);\r\n}\r\n\r\n/**\r\n * Best-effort teardown of whatever a failed startup managed to start.\r\n *\r\n * Runs while an error is already in flight, so no step here may throw and every\r\n * step is attempted independently.\r\n */\r\nasync function unwindPartialStartup(): Promise<void> {\r\n  // Two steps rather than one: `connectorsManager.shutdown()` runs the\r\n  // application hooks itself, but it runs them FIRST and does not isolate their\r\n  // rejection — so a hook that rejects would take the connector teardown down\r\n  // with it and leave every connector up. Both calls are idempotent, so running\r\n  // the hooks on their own first costs nothing and means neither failure can\r\n  // skip the other step.\r\n  await attemptCleanupStep(\"application shutdown hooks\", () => Application.runShutdownHooks());\r\n  await attemptCleanupStep(\"connectors shutdown\", () => connectorsManager.shutdown());\r\n}\r\n\r\n/**\r\n * Run one cleanup step, isolating its failure so the next step still runs.\r\n */\r\nasync function attemptCleanupStep(step: string, run: () => Promise<void>): Promise<void> {\r\n  try {\r\n    await run();\r\n  } catch (error) {\r\n    // Reported, not thrown — it is secondary to the startup error about to be\r\n    // rethrown, and losing that one to this would be the worse outcome.\r\n    console.error(`[vitest-setup] Cleanup after a failed setup did not complete (${step}):`, error);\r\n  }\r\n}\r\n\r\n/**\r\n * The teardown attempt itself.\r\n */\r\nasync function runTestRuntimeShutdown(): Promise<void> {\r\n  const registry = getTestLifecycleRegistry();\r\n  let shutdownSucceeded = false;\r\n\r\n  try {\r\n    // Manager-wide, and deliberately called whatever the selection was: with\r\n    // `connectors: false` nothing was started, but bootstrap still registered\r\n    // application shutdown hooks, and the manager runs those first (see\r\n    // `connectors-manager.ts` — `Application.runShutdownHooks()` is its first\r\n    // line). Skipping the call to \"match\" an empty selection would leak them.\r\n    await connectorsManager.shutdown();\r\n\r\n    shutdownSucceeded = true;\r\n  } finally {\r\n    // In a `finally`, not after the `await`: a rejected shutdown must not leave\r\n    // the lifecycle claiming a runtime it no longer owns. Poisoned rather than\r\n    // idle, because a cleared flag does not prove that ports, sockets, pools or\r\n    // timers closed.\r\n    registry.activeSelection = undefined;\r\n    registry.setupAttempt = undefined;\r\n    registry.teardownAttempt = undefined;\r\n    registry.state = shutdownSucceeded ? \"idle\" : \"poisoned\";\r\n  }\r\n}\r\n\r\n/**\r\n * Reject when a ready runtime was set up with a different selection.\r\n */\r\nfunction assertReadySelectionMatches(\r\n  activeSelection: TestConnectorsSelection | undefined,\r\n  requested: RequestedTestConnectors,\r\n): void {\r\n  if (activeSelection === undefined) {\r\n    return;\r\n  }\r\n\r\n  // Config is loaded by the time anything is ready, so the config-derived layer\r\n  // is resolvable right here.\r\n  const requestedSelection = resolveEffectiveConnectors(requested);\r\n\r\n  assertSelectionsMatch(activeSelection, requestedSelection);\r\n}\r\n\r\n/**\r\n * Reject when an in-flight setup attempt is starting a different selection.\r\n */\r\nasync function assertPendingSetupMatches(\r\n  attempt: TestSetupAttempt,\r\n  requested: RequestedTestConnectors,\r\n): Promise<void> {\r\n  const pending = attempt.requested;\r\n\r\n  // Two calls that both defer to project config resolve to the same thing by\r\n  // construction — knowable without waiting for config to load.\r\n  if (!pending.isExplicit && !requested.isExplicit) {\r\n    return;\r\n  }\r\n\r\n  if (pending.isExplicit && requested.isExplicit) {\r\n    assertSelectionsMatch(pending.selection, requested.selection);\r\n\r\n    return;\r\n  }\r\n\r\n  // Mixed: one side is config-derived and config is not readable until the\r\n  // running attempt has loaded it, so wait for that barrier first.\r\n  const activeSelection = await attempt.effectiveSelection;\r\n  const requestedSelection = resolveEffectiveConnectors(requested);\r\n\r\n  assertSelectionsMatch(activeSelection, requestedSelection);\r\n}\r\n\r\n/**\r\n * Name both selections: a caller looking at this message has to be able to tell\r\n * which call to change without reading the framework's source.\r\n */\r\nfunction assertSelectionsMatch(\r\n  activeSelection: TestConnectorsSelection,\r\n  requestedSelection: TestConnectorsSelection,\r\n): void {\r\n  if (isSameConnectorsSelection(activeSelection, requestedSelection)) {\r\n    return;\r\n  }\r\n\r\n  throw new TestLifecycleError(\r\n    `setupTest() is already using ${describeConnectorsSelection(activeSelection)}, and this call asked for ${describeConnectorsSelection(requestedSelection)}. One test runtime serves one connector selection — call teardownTest() before setting up a different one.`,\r\n  );\r\n}\r\n\r\n/**\r\n * Await an attempt for its state transition only, not its result.\r\n */\r\nfunction settled(attempt: Promise<void>): Promise<void> {\r\n  return attempt.catch(() => undefined);\r\n}\r\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAoEA,IAAa,qBAAb,cAAwC,MAAM;CAC5C,AAAO,YAAY,SAAiB;EAClC,MAAM,OAAO;EAEb,KAAK,OAAO;CACd;AACF;AAEA,MAAM,mBACJ;;;;;;;;;;;;;;;;;;;;;;;;;;;;AA6BF,eAAsB,UAAU,SAA2C;CACzE,MAAM,WAAW,yBAAyB;CAC1C,MAAM,YAAY,wBAAwB,SAAS,UAAU;CAE7D,IAAI,SAAS,UAAU,YACrB,MAAM,IAAI,mBAAmB,gBAAgB;CAG/C,IAAI,SAAS,UAAU,cAAc,SAAS,iBAAiB;EAC7D,MAAM,QAAQ,SAAS,eAAe;EAEtC,OAAO,UAAU,OAAO;CAC1B;CAEA,IAAI,SAAS,UAAU,SAAS;EAC9B,4BAA4B,SAAS,iBAAiB,SAAS;EAE/D;CACF;CAEA,IAAI,SAAS,UAAU,cAAc,SAAS,cAAc;EAC1D,MAAM,UAAU,SAAS;EAEzB,MAAM,0BAA0B,SAAS,SAAS;EAElD,OAAO,QAAQ;CACjB;CAEA,OAAO,iBAAiB,SAAS;AACnC;;;;;;;;;;;;;;;;;;AAmBA,eAAsB,eAA8B;CAClD,MAAM,WAAW,yBAAyB;CAE1C,IAAI,SAAS,UAAU,cAAc,SAAS,iBAC5C,OAAO,SAAS;CAGlB,IAAI,SAAS,UAAU,cAAc,SAAS,cAAc;EAI1D,MAAM,QAAQ,SAAS,aAAa,UAAU;EAE9C,OAAO,aAAa;CACtB;CAEA,IAAI,SAAS,UAAU,QACrB;CAGF,SAAS,QAAQ;CAMjB,MAAM,UAAU,QAAQ,QAAQ,CAAC,CAAC,WAAW,uBAAuB,CAAC;CAErE,SAAS,kBAAkB;CAE3B,OAAO;AACT;;;;;;;;;AAsCA,SAAS,cAAc,UAA6C;CAClE,MAAM,WAAW,SAAS,mBAAmB;CAC7C,MAAM,UAAU,KAAK,IAAI;CAEzB,IAAI;CACJ,IAAI,UAAU;CACd,IAAI,SAAS;CACb,IAAI,eAAyC;CAE7C,MAAM,SAAS,IAAI,SAAgB,UAAU,WAAW;EACtD,SAAS;CACX,CAAC;CAMD,OAAO,YAAY,MAAS;CAE5B,MAAM,aAAa,UAAwB;EACzC,IAAI,QACF;EAGF,SAAS;EACT,UAAU;EAEV,QAAQ,OAAO;EACf,SAAS;EAET,OAAO,IAAI,mBAAmB,qBAAqB,KAAK,CAAC,CAAC;CAC5D;CAEA,MAAM,UAAU,OAAe,UAAwB;EACrD,IAAI,QACF;EAGF,QAAQ,OAAO;EAIf,IAAI,SAAS,GAAG;GACd,UAAU,KAAK;GAEf;EACF;EAEA,SAAS,SAAS,aAAa,UAAU,KAAK,CAAC;CACjD;CAEA,MAAM,eAAe,SAAS;CAE9B,OAAO,cAAc,YAAY;CAEjC,OAAO;EACL;EAKA,QAAQ,SAAS,OAAO,MAAM,QAAQ,KAAK,IAAI,IAAI,QAAQ;EAE3D,cAAc;GACZ,SAAS;GAET,QAAQ,OAAO;GACf,SAAS;EACX;EAEA,kBAAkB;CACpB;AACF;;;;;;;;;;;AAYA,eAAe,sBACb,SACA,OACA,UACe;CACf,IAAI;EACF,MAAM,QAAQ,KAAK,CAAC,SAAS,MAAM,MAAM,CAAC;CAC5C,SAAS,OAAO;EACd,IAAI,MAAM,WAAW,GAAG;GACtB,SAAS,QAAQ;GACjB,SAAS,kBAAkB;GAC3B,SAAS,eAAe;EAC1B;EAEA,MAAM;CACR,UAAU;EACR,MAAM,OAAO;CACf;AACF;;;;AAKA,SAAS,iBAAiB,WAAmD;CAC3E,MAAM,WAAW,yBAAyB;CAE1C,IAAI,kCAAgF;CACpF,IAAI,+BAAyD;CAE7D,MAAM,qBAAqB,IAAI,SAAkC,SAAS,WAAW;EACnF,4BAA4B;EAC5B,yBAAyB;CAC3B,CAAC;CAKD,mBAAmB,YAAY,MAAS;CAExC,MAAM,QAAQ,cAAc,QAAQ;CAEpC,MAAM,UAAU,QAAQ,QAAQ,CAAC,CAAC,WAChC,sBAAsB,WAAW,2BAA2B,wBAAwB,KAAK,CAC3F;CAKA,QAAQ,YAAY,MAAS;CAK7B,MAAM,aAAa,sBAAsB,SAAS,OAAO,QAAQ;CAEjE,SAAS,QAAQ;CACjB,SAAS,eAAe;EAAE;EAAW;EAAoB;CAAW;CAEpE,OAAO;AACT;;;;;;;;AASA,eAAe,sBACb,WACA,2BACA,wBACA,OACe;CACf,MAAM,WAAW,yBAAyB;CAE1C,IAAI;EACF,YAAY,eAAe,MAAM;EAEjC,MAAM,qBAAqB,KAAK;EAChC,MAAM,UAAU;EAEhB,MAAM,kBAAkB,KAAK;EAC7B,MAAM,gBAAgB,IAAI;EAK1B,MAAM,oBAAoB,2BAA2B;EAErD,IAAI,sBAAsB,QACxB,MAAM,MAAM,iBAAiB;EAK/B,MAAM,qBAAqB,2BAA2B,SAAS;EAM/D,IAAI,CAAC,MAAM,WAAW,GACpB,SAAS,kBAAkB;EAG7B,0BAA0B,kBAAkB;EAE5C,MAAM,wBAAwB,kBAAkB;EAEhD,IAAI,CAAC,MAAM,WAAW,GAAG;GACvB,SAAS,QAAQ;GACjB,SAAS,eAAe;EAC1B;CACF,SAAS,OAAO;EACd,uBAAuB,KAAK;EAE5B,MAAM,qBAAqB;EAE3B,IAAI,CAAC,MAAM,WAAW,GAAG;GACvB,SAAS,QAAQ;GACjB,SAAS,kBAAkB;GAC3B,SAAS,eAAe;EAC1B;EAEA,QAAQ,MAAM,oDAAoD,KAAK;EAEvE,MAAM;CACR;AACF;;;;;;AAOA,eAAe,wBAAwB,WAAmD;CACxF,IAAI,cAAc,OAChB;CAGF,IAAI,MAAM,QAAQ,SAAS,GAAG;EAC5B,MAAM,kBAAkB,MAAM,wBAAwB,SAAS,CAAC;EAEhE;CACF;CAEA,MAAM,kBAAkB,aAAa,CAAC,MAAM,CAAC;AAC/C;;;;;;;AAQA,eAAe,uBAAsC;CAOnD,MAAM,mBAAmB,oCAAoC,YAAY,iBAAiB,CAAC;CAC3F,MAAM,mBAAmB,6BAA6B,kBAAkB,SAAS,CAAC;AACpF;;;;AAKA,eAAe,mBAAmB,MAAc,KAAyC;CACvF,IAAI;EACF,MAAM,IAAI;CACZ,SAAS,OAAO;EAGd,QAAQ,MAAM,iEAAiE,KAAK,KAAK,KAAK;CAChG;AACF;;;;AAKA,eAAe,yBAAwC;CACrD,MAAM,WAAW,yBAAyB;CAC1C,IAAI,oBAAoB;CAExB,IAAI;EAMF,MAAM,kBAAkB,SAAS;EAEjC,oBAAoB;CACtB,UAAU;EAKR,SAAS,kBAAkB;EAC3B,SAAS,eAAe;EACxB,SAAS,kBAAkB;EAC3B,SAAS,QAAQ,oBAAoB,SAAS;CAChD;AACF;;;;AAKA,SAAS,4BACP,iBACA,WACM;CACN,IAAI,oBAAoB,QACtB;CAOF,sBAAsB,iBAFK,2BAA2B,SAEE,CAAC;AAC3D;;;;AAKA,eAAe,0BACb,SACA,WACe;CACf,MAAM,UAAU,QAAQ;CAIxB,IAAI,CAAC,QAAQ,cAAc,CAAC,UAAU,YACpC;CAGF,IAAI,QAAQ,cAAc,UAAU,YAAY;EAC9C,sBAAsB,QAAQ,WAAW,UAAU,SAAS;EAE5D;CACF;CAOA,sBAAsB,MAHQ,QAAQ,oBACX,2BAA2B,SAEE,CAAC;AAC3D;;;;;AAMA,SAAS,sBACP,iBACA,oBACM;CACN,IAAI,0BAA0B,iBAAiB,kBAAkB,GAC/D;CAGF,MAAM,IAAI,mBACR,gCAAgC,4BAA4B,eAAe,EAAE,4BAA4B,4BAA4B,kBAAkB,EAAE,2GAC3J;AACF;;;;AAKA,SAAS,QAAQ,SAAuC;CACtD,OAAO,QAAQ,YAAY,MAAS;AACtC"}

package/package.json

@@ -36,13 +36,13 @@
     "@mongez/slug": "^1.0.7",
     "@mongez/supportive-is": "^2.1.3",
     "@mongez/time-wizard": "^1.0.6",
-    "@warlock.js/auth": "4.13.0",
-    "@warlock.js/cache": "4.13.0",
-    "@warlock.js/cascade": "4.13.0",
-    "@warlock.js/context": "4.13.0",
-    "@warlock.js/logger": "4.13.0",
-    "@warlock.js/seal": "4.13.0",
-    "@warlock.js/fs": "4.13.0",
+    "@warlock.js/auth": "4.14.0",
+    "@warlock.js/cache": "4.14.0",
+    "@warlock.js/cascade": "4.14.0",
+    "@warlock.js/context": "4.14.0",
+    "@warlock.js/logger": "4.14.0",
+    "@warlock.js/seal": "4.14.0",
+    "@warlock.js/fs": "4.14.0",
     "chokidar": "^5.0.0",
     "dayjs": "^1.11.19",
     "es-module-lexer": "^2.0.0",
@@ -68,15 +68,15 @@
     "react": "^19.2.3",
     "react-dom": "^19.2.3",
     "@react-email/render": "^2.0.5",
-    "@warlock.js/herald": "4.13.0",
-    "@warlock.js/ai": "4.13.0",
-    "@warlock.js/access": "4.13.0",
-    "@warlock.js/notifications": "4.13.0"
+    "@warlock.js/herald": "4.14.0",
+    "@warlock.js/ai": "4.14.0",
+    "@warlock.js/access": "4.14.0",
+    "@warlock.js/notifications": "4.14.0"
   },
   "bin": {
     "warlock": "bin/warlock.js"
   },
-  "version": "4.13.0",
+  "version": "4.14.0",
   "type": "module",
   "main": "./esm/index.mjs",
   "module": "./esm/index.mjs",

package/skills/test-http/SKILL.md

@@ -126,7 +126,7 @@ export default defineConfig({
   plugins: [lowerStage3Decorators(), mongezVite()],
   test: {
     globalSetup: "./src/test-global-setup.ts",  // ← starts the HTTP server
-    setupFiles: ["./src/test-setup.ts"],         // ← per-worker setupTest (see test-service skill)
+    setupFiles: ["./src/test-setup.ts"],         // ← setupTest + afterAll(teardownTest), per test file
     environment: "node",
     globals: false,
     include: ["src/app/**/*.test.ts"],
@@ -134,7 +134,13 @@ export default defineConfig({
 });
 ```
 
-Both files (and this config, with `lowerStage3Decorators()` first so decorated models load) are created by `warlock add test`. The split is intentional: `globalSetup` runs ONCE in the main vitest process; `setupFiles` runs per worker thread.
+Both files (and this config, with `lowerStage3Decorators()` first so decorated models load) are created by `warlock add test`. The split is intentional: `globalSetup` runs **ONCE** in the main vitest process; `setupFiles` runs **before every test file**.
+
+⚠ **Corrected in 4.14.0.** This line previously said `setupFiles` runs "per worker thread". **It does not** — Vitest runs it before each test file, and the setup module's registry is rebuilt every time. Measured across all four `pool` × `isolate` combinations.
+
+**So the service-layer framework is file-scoped: bootstrapped by `setupTest` and closed by the `afterAll(teardownTest)` the setup file registers, once per test file.** ⚠ **`setupTest` alone is not the whole wiring — the paired teardown is mandatory from 4.14.0**; see the `test-service` skill.
+
+**HTTP is the exception and stays in `globalSetup`**, which genuinely does run once in the main vitest process and owns a real port. **That split is the point:** one server for the whole run, one framework per test file.
 
 ## HTTP request helpers