R2 backup does not run: Sync aborted: no config file found

[circlekco]

The backup sync tests for the existence of the file test -f /root/.openclaw/openclaw.json. Through the chat interface, I've had the agent verify that this file does, in fact, exist. However, in sync.js the exitCode seems to return null, therefore aborting the backup sync to R2.

const checkNew = await sandbox.startProcess('test -f /root/.openclaw/openclaw.json');
await waitForProcess(checkNew, 5000);
if (checkNew.exitCode !== 0) {
...

This is as of commit 5593ac1.

[isaacrowntree]

Fix submitted in #215.

Root cause: The sandbox API returns null for process.exitCode even when the process succeeds. The check checkNew.exitCode !== 0 evaluates null !== 0 as true, so sync always aborts regardless of whether the config file exists.

Fix: Switch from test -f openclaw.json (exitCode-based) to ls -A (stdout-based) directory content detection. This is reliable regardless of exitCode and also handles OpenClaw versions that store config data in subdirectories without openclaw.json.