bin/lib/onboard.js (1)

546-549: Harden .env* deletion pipeline to handle directories and filenames with whitespace.

At Line 549, find ... | xargs rm -f fails to remove directories and mishandles filenames with whitespace or newlines. Use null-delimited output with xargs -0 and rm -rf instead:

Proposed diff

-  run(`find "${buildCtx}/nemoclaw-blueprint" -maxdepth 1 -name ".env" -o -name ".env.*" | xargs rm -f 2>/dev/null`, { ignoreError: true });
+  run(
+    `find "${buildCtx}/nemoclaw-blueprint" -maxdepth 1 \\( -name ".env" -o -name ".env.*" \\) -print0 | xargs -0 rm -rf -- 2>/dev/null`,
+    { ignoreError: true }
+  );

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@bin/lib/onboard.js` around lines 546 - 549, The deletion pipeline in the loop
uses run(...) and the subsequent find + xargs pipeline that calls rm -f fails on
directories and filenames with whitespace/newlines; update the command invoked
by run for removing .env* entries in the ktermbuild context (the existing call
that references buildCtx and "nemoclaw-blueprint") to use null-delimited output
and recursive removal (e.g., use find ... -print0 piped to xargs -0 rm -rf) so
directories are removed and names with spaces/newlines are handled safely; keep
the run(..., { ignoreError: true }) invocation and only change the shell
pipeline invoked.