PR #84191: Expose messageId in message CLI JSON output

• Repository: openclaw/openclaw
• Author: 100menotu001
• State: closed | merged: True
• Link: https://github.com/openclaw/openclaw/pull/84191

Description (problem / solution / changelog)

Summary

Adds a top-level messageId to openclaw message send --json output when the provider receipt contains one.

Motivation

Closes #84186.

The raw provider payload remains useful, but automation should not need provider-specific knowledge to find the id of the message it just sent.

Change Type

• Bug fix
• CLI output improvement

Scope

• Extracts messageId from direct and nested send receipt shapes.
• Adds top-level messageId only when present.
• Preserves the existing raw payload object unchanged.
• Adds a focused CLI JSON test for nested receipt output.

Linked Issue/PR

Closes #84186.

Real Behavior Proof

Behavior or issue addressed: openclaw message send --json must expose a top-level messageId when the provider receipt includes one while preserving the original provider payload.

Real environment tested: Redacted OpenClaw development checkout on this PR branch, using the real message CLI and Discord provider send path with IDs removed from public proof.

Exact steps or command run after this patch: Ran openclaw message send --channel discord --target channel:<redacted> --message <redacted> --json and transformed only the returned IDs to REDACTED_ID before publishing the output.

Evidence after fix: Redacted real CLI output:

{
  "action": "send",
  "channel": "discord",
  "topLevelMessageId": "REDACTED_ID",
  "payloadResultMessageId": "REDACTED_ID",
  "payloadPreserved": true
}

Observed result after fix: The JSON output included the new top-level message id, retained the nested provider message id, and preserved the existing provider payload object.

Not tested: No additional provider families were exercised; this proof covers the Discord CLI send path and the formatter path covered by the regression test.

Root Cause

buildMessageCliJson returned the raw provider payload but did not normalize common receipt identifiers into a stable CLI field.

Regression Test Plan

• pnpm exec vitest run src/commands/message.test.ts

Result: 1 file passed, 6 tests passed.

User-visible / Behavior Changes

openclaw message send --json may now include messageId at the top level when available. Existing consumers can continue reading payload.

Diagram

N/A. This is a CLI JSON shape improvement.

Security Impact

No secrets, new permissions, or external calls. The id is already present in the existing payload.

Repro + Verification

Before this change, callers had to inspect nested provider payload fields. The new test verifies a nested payload.result.messageId becomes top-level messageId, and the redacted real CLI send confirms the field is present on actual Discord message delivery while preserving the original payload.

Evidence

• Focused regression command passed.
• Redacted real CLI send output above confirms top-level messageId and preserved payload.

Human Verification

Real provider send path was exercised with IDs redacted from public proof.

Compatibility / Migration

Backward compatible. This only adds a field when it can be derived.

Risks

Low. Existing output fields are preserved.

Changed files

• CHANGELOG.md (modified, +1/-0)
• src/commands/message.test.ts (modified, +34/-0)
• src/commands/message.ts (modified, +21/-0)