fix(queue): deduplicate followup queue entries to prevent duplicate responses

## Problem

When messages arrived while the agent was busy processing a previous message,
the same message could be enqueued multiple times into the followup queue.
This happened because Discord's event system can emit the same message multiple
times (e.g., during reconnects or due to slow listener processing), and the
followup queue had no deduplication logic.

This caused the bot to respond to the same user message 2-4+ times.

## Solution

Add simple exact-match deduplication in `enqueueFollowupRun()`: if a prompt
is already in the queue, skip adding it again. Extracted into a small
`isPromptAlreadyQueued()` helper for clarity.

## Testing

- Added test cases for deduplication (same prompt rejected, different accepted)
- Manually verified on Discord: single response per message even when multiple
  events fire during slow agent processing

src/auto-reply/reply/queue.ts

@@ -337,6 +337,16 @@ function getFollowupQueue(
   FOLLOWUP_QUEUES.set(key, created);
   return created;
 }
+/**
+ * Check if a prompt is already queued using exact match.
+ */
+function isPromptAlreadyQueued(
+  prompt: string,
+  queue: FollowupQueueState,
+): boolean {
+  return queue.items.some((item) => item.prompt === prompt);
+}
+
 export function enqueueFollowupRun(
   key: string,
   run: FollowupRun,
@@ -345,6 +355,12 @@ export function enqueueFollowupRun(
   const queue = getFollowupQueue(key, settings);
   queue.lastEnqueuedAt = Date.now();
   queue.lastRun = run.run;
+
+  // Deduplicate: skip if the same prompt is already queued.
+  if (isPromptAlreadyQueued(run.prompt, queue)) {
+    return false;
+  }
+
   const cap = queue.cap;
   if (cap > 0 && queue.items.length >= cap) {
     if (queue.dropPolicy === "new") {