Lambda b0b667b907 refactor(handler): drop @mention coalescing dedup, enqueue per trigger ...

Each @mention or assignee comment now creates its own queued task instead
of folding into a single pending task per (issue, agent). The previous
HasPendingTaskForIssueAndAgent short-circuit in enqueueMentionedAgentTasks
and shouldEnqueueOnComment is gone; ClaimAgentTask already enforces
per-(issue, agent) serial execution at claim time, so multiple queued rows
drain one-by-one without overlap.

Why: see docs/rfcs/0001-mention-dedup-policy.md. Coalescing dropped the
trigger comment for every mention after the first, gave no UI feedback,
and collapsed distinct intents (different threads, different requests).

Drops the unused HasPendingTaskForIssue and HasPendingTaskForIssueAndAgent
queries and regenerates sqlc.

Adds TestRepeatedMentionsEnqueueSeparateTasks pinning the new contract:
two back-to-back @mentions queue two tasks with distinct trigger_comment_ids.

Co-authored-by: multica-agent <github@multica.ai>

2026-05-09 14:29:55 +08:00

..

agent

fix(agent): scope pi colon-to-slash normalization to legacy format (#2309)

2026-05-09 13:56:49 +08:00

db

refactor(handler): drop @mention coalescing dedup, enqueue per trigger

2026-05-09 14:29:55 +08:00

protocol

feat(comments): resolve threads with collapsible bar (MUL-1895) (#2300)

2026-05-09 05:49:33 +02:00

redact

…