test(gateway-lock): assert hashed lock path in writeFile failure test

zhangLei99586 · zhangLei99586 · commit 99a5ecacba52 · 2026-07-02T23:31:15.000+08:00
The test previously hardcoded lockPath as gateway.lock, but the actual
lock path uses SHA256 hash. Use resolveLockPath(env).lockPath so the
cleanup assertion matches the real acquireGatewayLock behavior.
diff --git a/src/infra/gateway-lock.test.ts b/src/infra/gateway-lock.test.ts
@@ -377,10 +377,11 @@ describe("gateway lock", () => {
     openSpy.mockRestore();
   });
 
-  it("closes handle and removes partial lock on writeFile failure after open", async () => {
+  it("closes handle and removes lock file on writeFile rejection after open", async () => {
     vi.useRealTimers();
     const env = await makeEnv();
-    const lockPath = path.join(resolveTestLockDir(), "gateway.lock");
+    const { lockPath } = resolveLockPath(env);
+    await fs.mkdir(path.dirname(lockPath), { recursive: true });
 
     let closeCalled = false;
     const fakeHandle = {
@@ -394,7 +395,6 @@ describe("gateway lock", () => {
 
     await expect(acquireForTest(env)).rejects.toThrow("failed to acquire gateway lock");
     expect(closeCalled).toBe(true);
-    // Partial lock file cleaned up — should not exist on disk.
     await expect(fs.access(lockPath)).rejects.toThrow();
 
     openSpy.mockRestore();
