Add automod event logging to user mod threads

[vcarl]

• Add AutoModerationExecution intent to Discord client
• Handle AutoModerationActionExecution events in automod.ts
• Create reportAutomod() function for cases where message isn't available
• Modify escalationControls() to accept userId string directly
• Add automod enum value to ReportReasons

When automod triggers, the bot now logs the action to the user's mod thread. If the message is still available, it uses the full reportUser() flow. If blocked/deleted by automod, it uses a fallback that logs available context (rule name, matched content, action type).

[what-the-diff]

PR Summary

• Logging for Discord Built-in Automoderation Events
  The team has added a new feature to keep a record of built-in automoderation events on Discord to user moderation threads.

• Automod Event Handling
  An event handler has been set up to help manage automoderation actions. However, for 'Timeout' actions, no logs are being kept as these events generally don't include any message content.

• Message Fetch and Report
  The PR includes some improvements in how we handle messages. When a 'messageId' is available, the system tries to fetch the message. If this is successful, the system uses 'reportUser()'. If it fails, the system falls back on a 'reportAutomod()' function.

• New 'reportAutomod()' Function
  A new feature of logging is introduced in case we do not have a full 'Message' object available.

• Escalation Controls
  The escalation controls have been updated. Now they can accept a 'Message' or a 'userId' string.

• ReportReasons Update
  The 'ReportReasons' category has been updated to include 'automod'.

• New Documentation
  The team has created new documentation explaining the changes and the thought process behind these changes.

[vcarl]

I still need to properly review and vet this, there are probably a couple of significant improvements left to be made

[Copilot]

Pull request overview

This PR adds logging functionality for Discord's built-in automod trigger events to user moderation threads.

Changes:

• Added AutoModerationExecution gateway intent to receive automod events
• Implemented event handler for automod actions with two-path approach: full message logging when available, fallback logging otherwise
• Created reportAutomod() function for logging automod actions without full message objects
• Modified escalationControls() to accept either Message or userId for broader compatibility
• Added automod enum value to ReportReasons

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 6 comments.

Show a summary per file

File	Description
notes/2026-01-13_1_automod-logging.md	Documentation of implementation approach and design decisions
app/models/reportedMessages.server.ts	Added automod reason enum value
app/helpers/modLog.ts	Implemented reportAutomod() function and helper for thread creation
app/helpers/escalate.tsx	Made escalationControls() accept Message or userId string
app/discord/client.server.ts	Added AutoModerationExecution intent
app/discord/automod.ts	Implemented AutoModerationActionExecution event handler

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[github-actions]

Preview environment removed

The preview for this PR has been cleaned up.

[github-actions]

✅ E2E Tests Passed

View Report · View Run

Tested against: https://243.euno-staging.reactiflux.com