fix(moderation): route context menus in the live event handler

[LucasSantana-Dev]

What

The Move message context menu silently failed in production — Discord showed "The application did not respond" with zero bot logs.

Root cause

The context-menu + channel-select routing was added to interactionHandler.ts, but that file is dead code — nothing wires its handleInteraction. The actually-wired InteractionCreate listener is eventHandler.ts's handleInteractionCreate, whose if (!interaction.isChatInputCommand()) return dropped every context-menu and select-menu interaction before it could route. Slash commands worked (they hit isChatInputCommand), so the gap was invisible until the first context menu.

Fix

Route inside the live handler, before the chat-input guard:

• isMessageContextMenuCommand() → executeContextMenu
• isChannelSelectMenu() + movemsg: prefix → handleMoveMessageSelect

Plus eventHandler.spec.ts regression tests so a context-menu / select routing miss is caught in CI (the original tests covered the dead handler, which is why this slipped).

Verification

• tsc clean across workspaces (pre-commit).
• Proven live in prod via a temporary hot-patch of this exact change (right-click → Apps → Move message → picker → move succeeded).
• Full suite runs in CI here.

Follow-up (separate issue)

interactionHandler.ts is dead/duplicate of eventHandler.ts — it should be deleted so this class of "edited the wrong handler" bug can't recur. Filing separately.

Non-destructive change (routing only — no new irreversible Discord API calls), so the destructive-interaction gate does not apply.

---

Summary by cubic

Fixes routing for message context menus and the move-message channel select in the live InteractionCreate handler so the Move message action works again in production.

• Bug Fixes
  • Route isMessageContextMenuCommand() to executeContextMenu.
  • Route isChannelSelectMenu() with movemsg: prefix to handleMoveMessageSelect.
  • Added eventHandler.spec.ts tests to cover context-menu and select routing.

^{Written for commit 110bb27. Summary will update on new commits.}

[greptile-apps]

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
lucky	Ready	Preview, Comment	Jun 22, 2026 1:22pm

[coderabbitai]

Warning

Review limit reached

@LucasSantana-Dev, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 44 minutes and 13 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: d964fb6e-d4fa-41d3-b1cd-a82ab3937a27

📥 Commits

Reviewing files that changed from the base of the PR and between 4da919c and 110bb27.

📒 Files selected for processing (2)

• packages/bot/src/handlers/eventHandler.spec.ts
• packages/bot/src/handlers/eventHandler.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/move-message-event-handler-routing

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Failed to generate code suggestions for PR

[cubic-dev-ai]

1 issue found across 2 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="packages/bot/src/handlers/eventHandler.ts">

<violation number="1" location="packages/bot/src/handlers/eventHandler.ts:288">
P3: catch block casts all interactions to ChatInputCommandInteraction. ChannelSelectMenuInteraction has no commandName — telemetry logs undefined.</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud