fix(openclaw): preserve rewrite stdout on non-zero exit

[jhenderiks]

Summary

• preserve rtk rewrite stdout when the child process exits non-zero
• fix the OpenClaw plugin path where execSync(...) throws and the rewrite is discarded
• closes bug(openclaw): plugin discards rewrite stdout on non-zero exit #1388

Why this change

The current OpenClaw plugin assumes that useful rewrite output only arrives on exit 0.

That is brittle. If rtk rewrite emits a rewritten command on stdout together with a non-zero exit status, the current execSync(...) path throws and the plugin drops the rewrite.

This PR makes the plugin preserve rewritten stdout on non-zero exit instead of treating all non-zero exits as unrecoverable.

Test plan

• bun --eval 'await import("./openclaw/index.ts")'
• cargo fmt --all && cargo clippy --all-targets && cargo test
• Manual verification in an environment where rtk rewrite emits rewritten stdout with non-zero exit

Notes

I am intentionally framing this as a defensive correctness fix.

I originally saw a repro where rtk rewrite emitted rewritten stdout with a non-zero exit, but I did not re-confirm that exact exit behavior on every RTK/environment combination before sending this PR.

[CLAassistant]

All committers have signed the CLA.

[pszymkowiak]

[w] wshm · Automated triage by AI

📊 Automated PR Analysis

🐛 Type	bug-fix
🟢 Risk	low

Summary

Fixes the OpenClaw plugin to preserve stdout from rtk rewrite when the child process exits with status 3. Previously, execSync would throw on non-zero exit codes, discarding the rewritten output. The fix extracts the exit status and stdout from the caught error object and returns the rewritten command when appropriate.

Review Checklist

• Tests present
• Breaking change
• Docs updated

Linked issues: #1388

---

Analyzed automatically by wshm · This is an automated analysis, not a human review.