fix: include event type in duplicate detection key to prevent false positives #28

The duplicate detection logic was incorrectly treating issue_comment events
as duplicates of issues events because the key didn't include the event type.

Changed key from: issue-{number}-{action}-{assignee}
To: {eventType}-issue-{number}-{action}-{assignee}

This ensures issues and issue_comment events are tracked separately.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

src/jobQueue.js

@@ -86,11 +86,12 @@ export class JobQueue {
     if (eventType === 'issues' || eventType === 'issue_comment') {
       const issueNumber = payload.issue?.number;
       if (issueNumber) {
-        // Create a more specific key that includes action and assignee
+        // Create a more specific key that includes event type, action and assignee
         // This prevents blocking legitimate state changes (e.g., assignment after creation)
+        // and ensures issues and issue_comment events are tracked separately
         const action = payload.action || 'unknown';
         const assignee = payload.issue?.assignee?.username || 'none';
-        const key = `issue-${issueNumber}-${action}-${assignee}`;
+        const key = `${eventType}-issue-${issueNumber}-${action}-${assignee}`;
 
         const lastProcessed = this.recentlyProcessed.get(key);
         const now = Date.now();