Bug Report

Version: 2026.2.26 (wizard migrated from 2026.2.22-2 to 2026.2.26 via doctor --fix on 2026-02-28)

Description:
After a gateway restart + openclaw doctor --fix migration, WhatsApp messages routed to a local relay agent (using openai-completions provider / local-relay/hardcoded-relay model) no longer include the Conversation info (untrusted metadata) envelope in the user message. The message body is delivered, but sender info is completely absent.

Setup:

{
  "agentId": "whatsapp-relay-agent",
  "model": { "primary": "local-relay/hardcoded-relay" },
  "match": { "channel": "whatsapp" }
}

Local relay server receives OpenAI-completions API calls from the gateway at localhost:8001.

Before restart (working):

messages[N] = {
  "role": "user",
  "content": "Conversation info (untrusted metadata):\n```json\n{\"message_id\": \"AC...\", \"sender\": \"+491...\"}\n```\n<message body>"
}

After restart (broken):

messages[N] = {
  "role": "user",
  "content": "<message body only — no envelope>"
}

Attempted fixes (none worked):

• Cleared relay agent session files
• Added peer-specific bindings for each contact (instead of catch-all)
• Checked HTTP request headers — no sender info there either
• Multiple gateway restarts

Timeline: Worked continuously Feb 23–27. Stopped after openclaw doctor --fix ran and updated wizard.lastRunVersion from 2026.2.22-2 to 2026.2.26 on Feb 28.

Impact: Relay agent can no longer identify message sender, breaking the relay pipeline for WA → Telegram forwarding.

Related: #29771 (per-agent params schema issue, same session)