fix(codex): bracket setTimeout body to satisfy eslint no-promise-executor-return

wangmiao0668000666 · wangmiao0668000666 · commit 5bc1256617de · 2026-07-09T10:23:38.000+08:00
The burst-dedup test awaited `new Promise&lt;void&gt;((resolve) =&gt; setTimeout(() =&gt; resolve(), 100))`.
The arrow-body `() =&gt; resolve()` is flagged by eslint(no-promise-executor-return)
because the implicit `return resolve()` is read as "return in Promise executor".
Bracketing the body so resolve() is a statement (not an expression) clears the
rule while keeping the test behavior identical.

Caught by CI check-lint on the round-1 push.
diff --git a/extensions/codex/src/node-cli-sessions.test.ts b/extensions/codex/src/node-cli-sessions.test.ts
@@ -319,7 +319,9 @@ describe("runCodexExecResume stream error handling", () => {
         }),
       );
       await new Promise<void>((resolve) => {
-        setTimeout(() => resolve(), 100);
+        setTimeout(() => {
+          resolve();
+        }, 100);
       });
       const child = captured[0];
       expect(child).toBeDefined();
@@ -348,7 +350,9 @@ describe("runCodexExecResume stream error handling", () => {
         }),
       );
       await new Promise<void>((resolve) => {
-        setTimeout(() => resolve(), 100);
+        setTimeout(() => {
+          resolve();
+        }, 100);
       });
       const child = captured[0];
       expect(child).toBeDefined();
@@ -383,7 +387,11 @@ describe("runCodexExecResume stream error handling", () => {
       );
 
       // Wait for the real child to attach so we can wrap its kill.
-      await new Promise<void>((resolve) => setTimeout(() => resolve(), 100));
+      await new Promise<void>((resolve) => {
+        setTimeout(() => {
+          resolve();
+        }, 100);
+      });
       const child = captured[0];
       expect(child).toBeDefined();
       const realKill = child!.kill.bind(child!);
