fix(test): sandbox tool-config tests away from the live ~/.airtable-user-mcp

switchProfile()/toggleTool()/toggleCategory() all save() to
tools-config.json; the main ToolConfigManager suite ran unsandboxed, so
every run rewrote the user's LIVE config — a Windows EPERM rename race
when the real daemon holds the file, and it could flip the real active
profile mid-run. A file-level AIRTABLE_USER_MCP_HOME tmp-dir hook now
covers the whole file (paths resolve lazily, so the env override takes
effect at call time).

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

Author: ARHAEEM

packages/mcp-server/test/test-tool-config.test.js

@@ -14,6 +14,22 @@ import {
   BUILTIN_PROFILES,
 } from '../src/tool-config.js';
 
+// Sandbox the WHOLE file: switchProfile()/toggleTool()/toggleCategory() all
+// call save(), which writes tools-config.json. Without this, tests write the
+// LIVE ~/.airtable-user-mcp/tools-config.json — a Windows EPERM rename race
+// when the real daemon holds the file, and they flip the user's real profile.
+const FILE_HOME = join(tmpdir(), `tool-config-test-${process.pid}-${Date.now()}`);
+const PREV_FILE_HOME = process.env.AIRTABLE_USER_MCP_HOME;
+before(async () => {
+  await mkdir(FILE_HOME, { recursive: true });
+  process.env.AIRTABLE_USER_MCP_HOME = FILE_HOME;
+});
+after(async () => {
+  if (PREV_FILE_HOME === undefined) delete process.env.AIRTABLE_USER_MCP_HOME;
+  else process.env.AIRTABLE_USER_MCP_HOME = PREV_FILE_HOME;
+  await rm(FILE_HOME, { recursive: true, force: true });
+});
+
 describe('TOOL_CATEGORIES', () => {
   it('maps all tools to valid categories', () => {
     const tools = Object.keys(TOOL_CATEGORIES);