fix: skip merged-away members in llm merges

[skwowet]

Summary

mergeMembersWithLLM was failing roughly every 2 hours when a batch contained overlapping member IDs: after merging pair A–B, async finishMemberMerging hard-deleted B, then a later pair like C–B hit memberNoMerge FK (memberNoMerge_noMergeId_fkey) and killed the run.

Changes

• Track secondaries merged in the current run and skip (then remove) later suggestions that still reference them before fetching member data for the LLM
• Guard insertMemberNoMerge with EXISTS checks so no-merge rows are only inserted when both member IDs still exist

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[Copilot]

Pull request overview

Prevents stale member merge suggestions from failing LLM merge workflows.

Changes:

• Skips suggestions referencing secondaries merged in the current batch.
• Checks member existence before inserting no-merge records.

Reviewed changes

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

File	Description
services/libs/data-access-layer/src/member_merge/index.ts	Guards no-merge inserts against missing members.
services/apps/merge_suggestions_worker/src/workflows/mergeMembersWithLLM.ts	Tracks merged-away members within a workflow run.

---

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