Best possible solution:

Close this branch and continue review on #85543 while keeping #85202 open until a real node exec fix lands.

Do we have a high-confidence way to reproduce the issue?

Yes for the underlying bug at source level: current main still builds non-Windows node exec as /bin/sh -lc and the node host spawns argv[0], while the linked issue adds live Linux headless reproduction evidence. This PR itself does not exercise that path.

Is this the best way to solve the issue?

No. This PR is not a valid solution because it changes unrelated Feishu/macOS tests; the maintainable path is a focused node shell/runtime fix such as the separate open candidate PR.

Security review:

Security review cleared: The diff only changes test formatting/trailing whitespace and introduces no dependency, workflow, secret, permissions, or runtime security surface.

What I checked:

• PR diff is unrelated to the reported runtime path: The pull files API shows only a trailing blank-line change in a macOS IPC test and assertion wrapping in a Feishu media test; no node exec, node-host, shell selection, or Linux runtime file is touched. (7c420e536132)
• Current main still hardcodes the Linux/non-Windows node shell: Current main returns ['/bin/sh', '-lc', command] for non-Windows node exec, so the submitted branch does not change the reported shell selection behavior. (src/infra/node-shell.ts:8, 06bf302864b6)
• Current main still forwards that argv to host=node execution: The exec host=node target still builds argv via buildNodeShellCommand before invoking the node, which is the code path described by the linked issue. (src/agents/bash-tools.exec-host-node-phases.ts:141, 06bf302864b6)
• Current main still directly spawns argv[0] on the node host: The node-host runCommand path still calls spawn(argv[0], argv.slice(1), ...), matching the reported spawn /bin/sh ENOENT failure shape. (src/node-host/invoke.ts:152, 06bf302864b6)
• Linked issue has live reproduction evidence: The linked issue comments include a reporter follow-up saying the failure reproduces on three Linux headless node hosts running as user systemd services on OpenClaw 2026.5.20.
• Canonical open fix candidate exists: GitHub search and the PR API show Retry node shell fallback on ENOENT #85543 is open, links the same issue, and changes src/infra/node-shell.ts plus src/node-host/invoke.ts with focused fallback tests and proof. (fd0fdfb445e2)

Likely related people:

• Ayaan Zaidi: Current-main blame on the node shell builder, exec host=node target construction, node-host spawn path, and the touched test files points to commit 63a2f69. (role: recent area contributor; confidence: high; commits: 63a2f69601ea; files: src/infra/node-shell.ts, src/agents/bash-tools.exec-host-node-phases.ts, src/node-host/invoke.ts)
• clawSean: The open related PR Retry node shell fallback on ENOENT #85543 directly targets the same Linux node shell fallback issue with changes to the node shell and node-host runtime path. (role: open canonical fix author; confidence: medium; commits: fd0fdfb445e2; files: src/infra/node-shell.ts, src/node-host/invoke.ts, src/node-host/invoke.node-shell-fallback.test.ts)

Codex review notes: model gpt-5.5, reasoning high; reviewed against 06bf302864b6.