PR #84187: Preserve reusable Discord presentation buttons

• Repository: openclaw/openclaw
• Author: 100menotu001
• State: open | merged: False
• Link: https://github.com/openclaw/openclaw/pull/84187

Description (problem / solution / changelog)

Summary

Adds reusable to portable presentation buttons, preserves it through Discord presentation mapping, and documents the field for message presentation authors.

Motivation

Closes #84182.

Presentation buttons can represent repeatable actions such as refresh or more-detail, but the portable schema and Discord mapper dropped the reusable intent before registry entries were created.

Change Type

• Bug fix
• Documentation

Scope

• Adds reusable?: boolean to the presentation button type and tool schema.
• Carries reusable: true from presentation buttons into Discord button specs.
• Preserves per-button reusable state when Discord component entries are built.
• Documents reusable?: boolean in docs/plugins/message-presentation.md.

Linked Issue/PR

Closes #84182.

Real Behavior Proof

Behavior or issue addressed: A portable presentation button with reusable: true must keep that flag through Discord mapping and component registry dispatch so repeatable actions are not consumed after the first callback.

Real environment tested: Redacted OpenClaw development checkout on this PR branch, using the Discord extension runtime path that maps presentation payloads into component entries.

Exact steps or command run after this patch: Ran a runtime diagnostic against this branch that created a reusable presentation button, mapped it to a Discord button spec, built component entries, and performed two dispatch-style lookups against the same callback data.

Evidence after fix: Redacted runtime output:

{
  "componentSpecButton": {
    "label": "More detail",
    "style": "secondary",
    "callbackData": "detail",
    "reusable": true
  },
  "entryReusable": true,
  "handlerConsumePolicy": false,
  "firstDispatch": {
    "label": "More detail",
    "callbackData": "detail"
  },
  "secondDispatch": {
    "label": "More detail",
    "callbackData": "detail"
  }
}

Observed result after fix: The Discord button spec contains reusable: true, the registered entry retains entryReusable: true, handler consume policy is false, and both lookup attempts return the same button metadata.

Not tested: No live Discord provider send was needed for this field-propagation path; the exercised behavior is the runtime mapping and registry decision that controls whether the callback is consumed.

Root Cause

Discord component entries supported reusable behavior, but portable presentation buttons had no reusable schema field and the Discord presentation mapper only copied label, style, callback data, and URL.

Regression Test Plan

• pnpm exec vitest run extensions/discord/src/shared-interactive.test.ts extensions/discord/src/components.test.ts

Result: 2 files passed, 15 tests passed.

User-visible / Behavior Changes

Message senders can now use presentation.blocks[].buttons[].reusable for Discord presentation buttons.

Diagram

N/A. This is a direct schema, adapter, component-entry, and docs propagation fix.

Security Impact

No new secrets or network calls. The change only preserves an explicit boolean in already-authored message payloads.

Repro + Verification

Before this change, a presentation button authored with reusable intent could not carry that intent through the message tool schema and Discord presentation mapper. The new test asserts that the generated Discord component spec retains it, and the redacted runtime diagnostic confirms the handler sees it as non-consuming.

Evidence

• Focused regression command passed.
• Redacted runtime diagnostic above confirms the mapped button remains reusable through component registration and dispatch-style resolution.

Human Verification

No live Discord service is required for this field-propagation fix; the proof exercises the runtime path that decides whether an interaction callback is consumed.

Compatibility / Migration

Backward compatible. Existing payloads are unchanged unless they opt into reusable: true.

Risks

Low. The flag is only emitted when explicitly set to true.

Changed files

• docs/plugins/message-presentation.md (modified, +5/-0)
• extensions/discord/src/components.builders.ts (modified, +1/-0)
• extensions/discord/src/components.types.ts (modified, +2/-0)
• extensions/discord/src/shared-interactive.test.ts (modified, +22/-0)
• extensions/discord/src/shared-interactive.ts (modified, +6/-0)
• src/agents/tools/message-tool.ts (modified, +1/-0)
• src/interactive/payload.ts (modified, +3/-0)