PR #64387: fix(plugins): include activationSourceConfig in loadOpenClawPlugins destructuring

• Repository: openclaw/openclaw
• Author: hteo1337
• State: open | merged: False
• Link: https://github.com/openclaw/openclaw/pull/64387

Description (problem / solution / changelog)

Summary

• resolvePluginLoadCacheContext returns activationSourceConfig in its result object (used to thread the original raw config through to activation-source creation)
• loadOpenClawPlugins destructures the result but omits activationSourceConfig
• The compiled build (2026.4.9, loader-BSIqIOsD.js) injects a diagnostic log inside loadOpenClawPlugins that references activationSourceConfig as a bare variable
• Since the variable was never destructured, this causes ReferenceError: activationSourceConfig is not defined, crash-looping the gateway on every startup attempt

One-line fix

Add activationSourceConfig to the destructuring at loadOpenClawPlugins line ~1092.

Reproduction

1. Install OpenClaw 2026.4.9 via pnpm/npm
2. Start the gateway (openclaw gateway start or via LaunchAgent)
3. Gateway crash-loops: starting... → loading configuration… → resolving authentication… → crash → repeat every ~4s
4. ~/.openclaw/logs/gateway.err.log shows: Gateway failed to start: ReferenceError: activationSourceConfig is not defined

Evidence

Gateway error log (repeating every ~4 seconds):

2026-04-10T14:14:03.652+03:00 Gateway failed to start: ReferenceError: activationSourceConfig is not defined
2026-04-10T14:14:07.982+03:00 Gateway failed to start: ReferenceError: activationSourceConfig is not defined
2026-04-10T14:14:12.218+03:00 Gateway failed to start: ReferenceError: activationSourceConfig is not defined

Compiled code trace

In loader-BSIqIOsD.js:

Line ~1996 — resolvePluginLoadCacheContext declares and returns activationSourceConfig:

const activationSourceConfig = options.activationSourceConfig ?? options.config ?? {};
// ...
return { env, cfg, normalized, activationSourceConfig, activationSource, ... };

Line ~2336 — loadOpenClawPlugins destructures but omits it:

const { env, cfg, normalized, activationSource, autoEnabledReasons, ... } = resolvePluginLoadCacheContext(options);
//                              ^ missing activationSourceConfig here

Line ~2446 — a diagnostic log references it as a bare variable:

if (shouldActivate) logger.warn(`[plugins-diag] ... activation.plugins=${JSON.stringify(activationSourceConfig?.plugins ?? null)}`);
// ReferenceError: activationSourceConfig is not defined

Environment

• OpenClaw: 2026.4.9 (0512059)
• Node.js: v25.9.0
• OS: macOS 26.3.1 (arm64)

AI-assisted

• AI-assisted (Claude Code / Opus 4.6)
• Tested locally: applied equivalent patch to compiled loader-BSIqIOsD.js, confirmed gateway starts successfully
• I understand what the code does

Related issues

Fixes #64357

Related (same symptom family — false plugins.allow is empty warnings):

• #62049, #64170, #62521, #63693, #63182

Possibly related (plugin loading crashes/hangs):

• #64306, #64354

Test plan

• pnpm build && pnpm check && pnpm test passes
• Gateway starts without crash-loop on fresh install
• openclaw doctor no longer shows activationSourceConfig ReferenceError

Changed files

• scripts/check-no-raw-channel-fetch.mjs (modified, +1/-1)
• src/plugins/loader.ts (modified, +2/-0)
• test/scripts/lint-suppressions.test.ts (modified, +1/-0)