Keep the synthetic Codex test binding outside server compilation

Resolve the offline fixture module at runtime, preserving the server rootDir boundary.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
This commit is contained in:
DottaandPaperclip committed 2026-10-09 11:55:41 -05:00
1 parent 6c1f1038b5
commit d966fa578e
1 file changed
+1 -1
@@ -762,7 +762,7 @@ const recoveryFakeCodex = resolve(
await chmod(command, 0o700);
// Installed dependency selection intentionally precedes PATH on mainline.
// Bind this fixture's synthetic provider explicitly at that boundary.
const codexCommandModule = await import("../../../../packages/paperclip-runner/src/drivers/codex/codex-command.js");
const codexCommandModule = await import(new URL("../../../../packages/paperclip-runner/src/drivers/codex/codex-command.ts", import.meta.url).href);
const codexCommandSelection = vi.spyOn(codexCommandModule, "resolveCodexCommand").mockReturnValue(command);
restoreCodexCommand = () => codexCommandSelection.mockRestore();
await new Promise<void>((done) => server.listen(0, "127.0.0.1", done));