openclaw - 💡(How to fix) Fix [Bug] MEMORY.md loads in Discord guild channels despite documentation stating otherwise

Bug Description

MEMORY.md (long-term memory file) loads and is accessible in Discord guild/server channels, contrary to the official documentation which states "By default, long-term memory (MEMORY.md) only loads in DM sessions. Guild channels do not auto-load MEMORY.md."

Steps to Reproduce

1. Add OpenClaw Discord bot to a server with guild channels configured
2. Join a guild channel (e.g., #general)
3. Ask the bot a personal question that would require MEMORY.md data (e.g., "What's my birthday?")
4. Bot responds correctly with information from MEMORY.md

Expected vs Actual

• Expected: MEMORY.md should NOT be accessible in guild channels (per docs)
• Actual: MEMORY.md loads and bot can retrieve personal information (e.g., birthdate: October 13, 1993) in group channel context

Evidence

Screenshot available at: [will attach via comment]

The bot displayed "Memory Search" status before correctly answering "October 13, 1993! 🔥 You're turning 33 later this year." in a Discord #general channel after starting a new session.

Impact

Personal private information stored in MEMORY.md (birthdays, addresses, phone numbers, etc.) is accessible to anyone in Discord group channels where the bot is present. This is a privacy leak.

Additional Context

• The documentation explicitly states guild channels should not auto-load MEMORY.md — this is not working as documented
• QMD scope default denies chatType: "channel" but memory_search still works in guild channels, suggesting the leak is in workspace bootstrap injection, not QMD search
• User-level workaround (configuring QMD scope explicitly) did not resolve the issue

Environment

• OpenClaw version: latest
• Channel: Discord guild (tested in #general)
• Session type: Guild channel session (agent:*:discord:channel:*)