backend/src/api/public/v1/members/identities/createMemberIdentity.ts:108

• When data.verified is true, the transaction also verifies every same-value identity in the loop above. If one of those identities conflicts on a different platform, this reports and deduplicates the alert using data.platform, so the Slack alert points to the wrong identity. Track the identity associated with the failing insert/update and pass that subject here.

          rethrowIdentityConflict(req, error, {
            memberId,
            platform: data.platform,
            value: data.value,
            type: data.type,

backend/src/api/public/alerts/identityConflict.ts:20

• The dedupe key uses the caller's raw casing, but the active uniqueness constraint is on lower(value) (V1785255019__member_identities_case_insensitive_unique_indexes.sql:9-12). Requests for Foo and foo therefore hit the same conflict but generate different Redis keys and duplicate Slack alerts within the hour. Canonicalize the value for the key.

    identity.value,

backend/.eslintrc.js:50

• This disables no-void for every backend TypeScript file to support two local fire-and-forget calls, weakening lint coverage outside this change. Keep the project-wide rule and scope the suppression or rejection handling to those call sites instead; the protected-files hook also identifies ESLint configuration as project-wide infrastructure.

        'no-void': 'off',

backend/src/api/public/alerts/identityConflict.ts:20

• The dedupe key keeps the request's original casing, but the identity uniqueness constraint compares lower(value) (backend/src/database/migrations/V1785255019__member_identities_case_insensitive_unique_indexes.sql:9-12). Equivalent conflicts such as Foo@example.com and foo@example.com therefore reserve different Redis keys and can emit duplicate alerts. Normalize the value according to the constraint when constructing the key.

    identity.value,