fix: preserve lazy memory teardown boundary

This commit is contained in:
Frank Yang
2026-03-10 00:11:11 +08:00
parent 9f0071b314
commit 0e600e89cf
2 changed files with 2 additions and 2 deletions

View File

@@ -28,7 +28,7 @@ vi.mock("../infra/runtime-guard.js", () => ({
assertSupportedRuntime: assertRuntimeMock,
}));
vi.mock("../memory/index.js", () => ({
vi.mock("../memory/search-manager.js", () => ({
closeAllMemorySearchManagers: closeAllMemorySearchManagersMock,
}));

View File

@@ -15,7 +15,7 @@ import { normalizeWindowsArgv } from "./windows-argv.js";
async function closeCliMemoryManagers(): Promise<void> {
try {
const { closeAllMemorySearchManagers } = await import("../memory/index.js");
const { closeAllMemorySearchManagers } = await import("../memory/search-manager.js");
await closeAllMemorySearchManagers();
} catch {
// Best-effort teardown for short-lived CLI processes.