What Problem This Solves

In the gateway's chat abort handling, if the project session terminal persistence fails, the promise catch block silently deletes the abort controller without logging the error. This means terminal states can fail to persist in production without any trace in the telemetry or logs.

Expected vs Actual Behavior

Expected: If a critical background persistence operation fails, it should be logged via log.error so operators can monitor database or file-system health.
Actual: The error is swallowed completely.

Code Link

https://github.com/openclaw/openclaw/blob/main/src/gateway/chat-abort.ts#L168-L180

Proposed Solution

Add proper error logging inside the .catch() block:

.catch((err) => {
  log.error?.(`Failed to persist chat abort terminal state for run ${params.runId}: ${err}`);
  if (params.chatAbortControllers.get(params.runId)?.controller === controller) {
    params.chatAbortControllers.delete(params.runId);
  }
});