#23046: fix(whatsapp): detect LID JID in implicit reply-to-bot mention check

Fixes #23029. When someone swipe-replies to a bot message in a WhatsApp group, the reply's `participant` field sometimes comes back as `XXXX@lid` instead of `XXXX@s.whatsapp.net`. This is WhatsApp's LID (Linked Identity Device) format, and it's becoming more common as WhatsApp migrates to it. The `implicitMention` check in `applyGroupGating` only compares against `selfJid` (regular JID) and `selfE164` (phone number). When the reply sender shows up as a LID, both comparisons fail silently and the reply is dropped as "no mention detected." The bot's own LID is available at `sock.user?.lid`, but it was never extracted or threaded through to the gating check. ## What changed Three small changes: 1. `types.ts` — added `selfLid?: string | null` to `WebInboundMessage` 2. `monitor.ts` — extracted `selfLid = sock.user?.lid ?? null` and passed it into the inbound message object 3. `group-gating.ts` — added a third condition to `implicitMention`: `(selfLid && replySenderJid && selfLid === replySenderJid)` The device-suffix stripping (`.replace(/:\d+/, "")`) already handles `"98765432:1@lid"` → `"98765432@lid"` correctly, so no extra logic needed there. ## Relationship to #16655 PR #16655 resolves LID JIDs to E.164 via `lidLookup` when a mapping file exists. This handles the fallback case where that mapping is unavailable. Both fixes work together. ## Tests - New: reply with matching LID triggers implicit mention → `shouldProcess: true` - New: reply with non-matching LID does not trigger → `shouldProcess: false` - Existing 15 group gating tests unchanged Closes #23029 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> <!-- greptile_comment --> <h3>Greptile Summary</h3> This PR fixes a bug where swipe-replies to bot messages in WhatsApp groups were silently dropped when the reply's `participant` field used WhatsApp's LID (Linked Identity Device) format (`XXXX@lid`) instead of the standard JID format (`XXXX@s.whatsapp.net`). - Adds `selfLid` (from `sock.user?.lid`) to the `WebInboundMessage` type and threads it through from the inbound monitor to the group gating logic - Extends the `implicitMention` check in `applyGroupGating` with a third condition comparing the bot's own LID against the reply sender's JID, so LID-format replies are correctly recognized as replies to the bot - Complements PR #16655's `lidLookup` approach by handling the fallback case where no LID-to-E164 mapping is available - Adds two focused tests covering the matching and non-matching LID scenarios <h3>Confidence Score: 5/5</h3> - This PR is safe to merge — it adds a narrowly scoped fallback check with no impact on existing behavior. - The change is minimal and well-contained: one new optional field on a type, one new line extracting a value from an existing API, and one additional OR condition in a Boolean expression. The existing 15 group gating tests are unaffected, and two new tests specifically cover the LID matching logic. The device-suffix stripping regex is consistent with existing patterns. No security, performance, or correctness concerns. - No files require special attention. _{Last reviewed commit: 4615437} <!-- greptile_other_comments_section --> <!-- /greptile_comment -->