PR #84190: Log Discord component registry error details

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

Description (problem / solution / changelog)

Summary

Logs structured details when the Discord persistent component registry falls back after a state-store failure.

Motivation

Closes #84185.

The fallback is intentionally recoverable, but the warning previously only logged String(error), which made storage and runtime failures harder to distinguish.

Change Type

• Bug fix

Scope

• Formats thrown registry errors into structured warning metadata.
• Includes error name, message, stack, and cause details when available.
• Leaves fallback behavior unchanged.
• Adds coverage for cause metadata in the warning.

Linked Issue/PR

Closes #84185.

Real Behavior Proof

Behavior or issue addressed: When the Discord persistent component registry cannot open its keyed store, fallback behavior must still work and the real plugin runtime logger must preserve structured error and cause metadata.

Real environment tested: Redacted OpenClaw development checkout on this PR branch, using the Discord component registry runtime with a deliberately failing keyed-store open path.

Exact steps or command run after this patch: Ran a runtime diagnostic using createRuntimeLogging(), injected a store-open failure with an Error cause, registered Discord component entries, resolved a fallback entry, and captured the redacted JSON log record emitted through the real runtime logging adapter.

Evidence after fix: Redacted runtime output:

{
  "fallbackEntryAvailable": true,
  "warningMessage": "Discord persistent component registry state failed",
  "structuredMetadata": {
    "errorName": "Error",
    "errorMessage": "redacted registry state open failed",
    "errorCauseName": "TypeError",
    "errorCauseMessage": "redacted state backend unavailable"
  }
}

Earlier call-site diagnostic before the runtime adapter fix:

{
  "fallbackEntryAvailable": true,
  "warning": {
    "message": "Discord persistent component registry state failed",
    "errorName": "Error",
    "errorMessage": "redacted registry state open failed",
    "errorCauseName": "TypeError",
    "errorCauseMessage": "redacted state backend unavailable"
  }
}

Observed result after fix: Fallback registry resolution remained available, and the warning emitted through the real runtime logging adapter retained errorName, errorMessage, errorCauseName, and errorCauseMessage metadata.

Not tested: No live Discord provider send was needed for this persistent-registry fallback logging path.

Root Cause

The registry warning collapsed the thrown value to a single string, discarding structured Error fields and cause context.

Regression Test Plan

• node scripts/run-vitest.mjs extensions/discord/src/components.test.ts src/plugins/runtime/runtime-logging.test.ts

Result: 2 files passed, 10 tests passed.

User-visible / Behavior Changes

No user-facing behavior change. Operators get more actionable warning metadata when persistent component state fails and OpenClaw falls back to in-memory state.

Diagram

N/A. This is warning metadata only.

Security Impact

No new secrets, permissions, or external calls. The logged metadata is limited to the caught error details already available in-process.

Repro + Verification

Before this change, the fallback warning only included String(error), and the production runtime logging adapter dropped metadata arguments. The new regression tests verify name, message, and cause details at the Discord call site and metadata forwarding in the runtime logger adapter; the redacted runtime diagnostic confirms fallback remains available and the real log record carries the structured metadata.

Evidence

• Focused regression command passed.
• Redacted runtime diagnostic above confirms the fallback entry remains available and the real runtime log record includes structured error and cause metadata.

Human Verification

No live Discord service is required for this deterministic fallback logging path.

Compatibility / Migration

Backward compatible. The warning message text is unchanged, and metadata gains additional fields.

Risks

Low. The formatter is best-effort and is wrapped by the existing logging guard.

Changed files

• extensions/discord/src/components-registry.ts (modified, +49/-1)
• extensions/discord/src/components.test.ts (modified, +15/-2)
• src/plugins/runtime/runtime-logging.test.ts (added, +55/-0)
• src/plugins/runtime/runtime-logging.ts (modified, +20/-4)