Greptile Summary

This PR fixes silent failures in Discord auto-ACK reactions when using SecretRef-based token storage. The root cause was that reactMessageDiscord and removeReactionDiscord were called without a cfg argument, causing them to fall back to loadConfig() which returns unhydrated config — breaking SecretRef resolution at runtime.

Key changes:

• Core fix: cfg is now passed to both reactMessageDiscord and removeReactionDiscord in the StatusReactionAdapter callbacks, using the already-hydrated config from processDiscordMessage's ctx. The DiscordReactOpts.cfg field and the opts.cfg ?? loadConfig() fallback in send.reactions.ts were already in place, so only the call-site was missing the value.
• Diagnostic logging: Verbose process:start, process:setQueued, and process:setQueued-skipped log lines are added around the ACK-reaction path to aid future debugging.
• Import ordering: resolveChunkMode and finalizeInboundContext imports are moved to their correct alphabetical position among the openclaw/plugin-sdk/reply-* imports.

Confidence Score: 4/5

Safe to merge — the fix is minimal, targeted, and uses existing typed plumbing that was already in place.

The change is a single-line fix per call-site that closes a clear SecretRef regression. The cfg field was already defined on DiscordReactOpts and the ?? loadConfig() fallback pattern in send.reactions.ts confirms the intended contract. New verbose logging follows established patterns and is guarded by shouldLogVerbose(). The only remark is cosmetic (cfg: cfg vs shorthand cfg). No logic or data-flow concerns.

No files require special attention beyond the cosmetic shorthand nit in extensions/discord/src/monitor/message-handler.process.ts.

This is a comment left during a code review.
Path: extensions/discord/src/monitor/message-handler.process.ts
Line: 201-210

Comment:
**Use ES6 shorthand property syntax for `cfg`**

`cfg: cfg` can be shortened to just `cfg` since the variable name matches the property name. The rest of the codebase (including `deliverDiscordReply` calls nearby) uses shorthand property syntax consistently.

```suggestion
      await reactMessageDiscord(messageChannelId, message.id, emoji, {
        rest: discordRest,
        cfg,
      });
```

Same applies to the `removeReaction` callback a few lines below:

```suggestion
      await removeReactionDiscord(messageChannelId, message.id, emoji, {
        rest: discordRest,
        cfg,
      });
```

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "fix(discord): pass hydrated config to ac..." | Re-trigger Greptile}

Landed via temp rebase onto main.\n\n- Gate: pnpm check; pnpm build; pnpm test -- extensions/discord/src/monitor/message-handler.process.test.ts; pnpm test -- src/auto-reply/reply/commands.test.ts -t "accepts Telegram /approve from exec target recipients when native approvals are disabled"; pnpm test -- src/secrets/runtime.test.ts -t "skips inactive-surface refs and emits diagnostics"\n- Land commit: 0fd5550\n- Merge commit: b7f524a\n\nThanks @FunJim!