openclaw - 💡(How to fix) Fix Inbound metadata timestamp should include seconds [1 pull requests]

Problem

The timestamp field in the conversation info metadata block (shown to agents as "untrusted metadata") only includes hours and minutes, not seconds:

"timestamp": "Wed 2026-05-27 18:32 GMT+8"

This makes it difficult to diagnose message delivery delays, since we can only tell the minute a message was sent, not the exact second.

Root Cause

formatEnvelopeTimestamp() in envelope-*.js calls formatZonedTimestamp() / formatUtcTimestamp() from format-datetime-*.js without setting displaySeconds: true.

The functions already support a displaySeconds option — it just is not enabled for inbound metadata timestamps.

Expected Behavior

The metadata timestamp should include seconds:

"timestamp": "Wed 2026-05-27 18:32:58 GMT+8"

Suggested Fix

Pass { displaySeconds: true } when calling formatZonedTimestamp / formatUtcTimestamp inside formatEnvelopeTimestamp() for inbound conversation metadata.

The underlying format functions already handle this:

• Zoned: 2024-01-15 14:30:05 EST
• UTC: 2024-01-15T14:30:05Z

Context

While debugging a ~2min message delivery delay from Cove → OpenClaw, the metadata timestamp only showed 18:32 while gateway logs showed receipt at 18:32:58. The lack of seconds precision made it impossible to determine from metadata alone whether the delay was on the sending platform side or the gateway side.