Summary

Per-topic requireMention override is ignored in Telegram forum supergroups — group-level setting always wins.

Fixes openclaw#49864

Root Cause

In bot-message-context.ts, the requireMention resolution chain used firstDefined() with this order:

const requireMention = firstDefined(
    activationOverride,          // from /activate /deactivate session state
    topicConfig?.requireMention, // topic-level config — NEVER REACHED
    groupConfig?.requireMention, // group-level config
    baseRequireMention,          // channel default
);

activationOverride (persisted from /activate or /deactivate commands) was evaluated before topicConfig?.requireMention, so any persisted activation state would override explicit per-topic config.

Fix

Reorder firstDefined() so topic config is evaluated first:

const requireMention = firstDefined(
    topicConfig?.requireMention,  // topic config always wins
    activationOverride,           // then runtime activation
    groupConfig?.requireMention,
    baseRequireMention,
);

Testing

Added 4 new tests in a dedicated test file:

1. Topic requireMention=false overrides group requireMention=true
2. Topic config overrides activationOverride
3. Group-level requireMention still works when no topic config
4. activationOverride still works when no topic config

All 4 tests pass.

Made-with: Claude Code (Claude Opus 4.6)