PR #69869: fix(discord): keep slash follow-ups ephemeral

• Repository: openclaw/openclaw
• Author: gumadeiras
• State: closed | merged: True
• Link: https://github.com/openclaw/openclaw/pull/69869

Description (problem / solution / changelog)

Summary

Describe the problem and fix in 2–5 bullets:

• Problem: Discord slash command replies can be chunked into multiple follow-ups, but follow-up payloads did not preserve the command's ephemeral visibility.
• Why it matters: long /status replies could expose fallback model/runtime details publicly after the initial ephemeral response.
• What changed: thread the native command ephemeral policy through Discord interaction reply delivery, including chunked text and media follow-up chunks.
• What did NOT change (scope boundary): no Discord gateway startup, doctor, command routing, or model status content changes.

Change Type (select all)

• Bug fix
• Feature
• Refactor required for the fix
• Docs
• Security hardening
• Chore/infra

Scope (select all touched areas)

• Gateway / orchestration
• Skills / tool execution
• Auth / tokens
• Memory / storage
• Integrations
• API / contracts
• UI / DX
• CI/CD / infra

Linked Issue/PR

• Closes #
• Related #69841
• This PR fixes a bug or regression

Root Cause (if applicable)

• Root cause: Discord native slash commands set an ephemeral command policy and defer the interaction, but deliverDiscordInteractionReply built subsequent followUp() payloads without the ephemeral flag.
• Missing detection / guardrail: direct /status coverage asserted the reply text but not visibility across chunked follow-ups.
• Contributing context (if known): /status can exceed Discord chunk limits when fallback models/runtime details are included.

Regression Test Plan (if applicable)

• Coverage level that should have caught this:
  • Unit test
  • Seam / integration test
  • End-to-end test
  • Existing coverage already sufficient
• Target test or file: extensions/discord/src/monitor/native-command.status-direct.test.ts
• Scenario the test should lock in: long direct /status output sends multiple follow-ups, and every follow-up remains ephemeral.
• Why this is the smallest reliable guardrail: it exercises the Discord native command delivery helper directly without live Discord.
• Existing test that already covers this (if any): existing direct /status test covered dispatcher bypass but not chunk visibility.
• If no new test is added, why not: N/A

User-visible / Behavior Changes

Discord slash-command follow-up chunks now stay ephemeral when the command is configured for ephemeral replies.

Diagram (if applicable)

Before:
/status -> ephemeral defer -> first follow-up -> later chunks public

After:
/status -> ephemeral defer -> all follow-up chunks ephemeral

Security Impact (required)

• New permissions/capabilities? (Yes/No) No
• Secrets/tokens handling changed? (Yes/No) No
• New/changed network calls? (Yes/No) No
• Command/tool execution surface changed? (Yes/No) No
• Data access scope changed? (Yes/No) No
• If any Yes, explain risk + mitigation: N/A

Repro + Verification

Environment

• OS: macOS local dev
• Runtime/container: Node repo runtime via pnpm
• Model/provider: N/A
• Integration/channel (if any): Discord
• Relevant config (redacted): Discord native slash commands with ephemeral replies enabled

Steps

1. Configure Discord slash commands for ephemeral replies.
2. Run /status with enough status content to require multiple Discord follow-up messages.
3. Inspect follow-up payload visibility.

Expected

• Every /status follow-up remains ephemeral.

Actual

• Before this fix, later follow-up chunks could be sent without ephemeral and become public.

Evidence

Attach at least one:

• Failing test/log before + passing after
• Trace/log snippets
• Screenshot/recording
• Perf numbers (if relevant)

Regression coverage added in native-command.status-direct.test.ts; local changed gate passes.

Human Verification (required)

What you personally verified (not just CI), and how:

• Verified scenarios: long direct /status output produces multiple follow-ups and all follow-up payloads contain ephemeral: true.
• Edge cases checked: shared Discord changed-surface gate, including extension typecheck, lint, import cycles, and 54 Discord extension test files.
• What you did not verify: live Discord API behavior.

Review Conversations

• I replied to or resolved every bot review conversation I addressed in this PR.
• I left unresolved only the conversations that still need reviewer or maintainer judgment.

If a bot review conversation is addressed by this PR, resolve that conversation yourself. Do not leave bot review conversation cleanup for maintainers.

Compatibility / Migration

• Backward compatible? (Yes/No) Yes
• Config/env changes? (Yes/No) No
• Migration needed? (Yes/No) No
• If yes, exact upgrade steps: N/A

Risks and Mitigations

• Risk: Some non-status slash-command follow-ups now explicitly inherit the configured ephemeral policy.
  • Mitigation: this matches the existing command-level ephemeralDefault and preserves explicit overrides where call sites pass one.

Changed files

• CHANGELOG.md (modified, +4/-0)
• extensions/discord/src/monitor/native-command-ui.ts (modified, +3/-0)
• extensions/discord/src/monitor/native-command.command-arg.test.ts (added, +97/-0)
• extensions/discord/src/monitor/native-command.status-direct.test.ts (modified, +61/-0)
• extensions/discord/src/monitor/native-command.ts (modified, +23/-6)