diff --git a/packages/cli/src/commands/__tests__/provider-settings.test.ts b/packages/cli/src/commands/__tests__/provider-settings.test.ts
index 1b9c17d109..cd68ac9298 100644
--- a/packages/cli/src/commands/__tests__/provider-settings.test.ts
+++ b/packages/cli/src/commands/__tests__/provider-settings.test.ts
@@ -4,14 +4,11 @@ import { describe, expect, it, vi } from "vitest";
 import { tempWorkspace } from "@fusion/test-utils";
 import { createReadOnlyProviderSettingsView, createProjectSettingsPersistence } from "../provider-settings.js";
 
-// All tests here are pure synchronous FS operations against a temp workspace,
-// so they shouldn't take more than a handful of milliseconds. They have
-// occasionally tripped vitest's default 5s timeout when the worker pool is
-// starved by a parallel FS-heavy suite (one slot stalls long enough that the
-// runner gives up before the test body even gets a turn). Bumping the
-// per-test cap rules out worker contention as a flake source without
-// changing what the tests actually verify.
-vi.setConfig({ testTimeout: 30000 });
+/*
+FNXC:CliTests 2026-06-14-01:47:
+Provider-settings tests are synchronous temp-workspace filesystem checks, so they must stay on Vitest's default 5s timeout.
+FN-6431 removed the hidden file-wide 30s timeout appeasement after FN-6430 fixed the shared CLI fixture isolation path that previously caused package-load starvation.
+*/
 
 function writeJson(path: string, value: Record<string, unknown>): void {
   writeFileSync(path, JSON.stringify(value, null, 2));