fix(send_message): accept WhatsApp LID targets

[doncazper]

Summary

• recognize WhatsApp digits@lid targets as explicit direct targets via a WhatsApp-only parser branch
• keep LID handling from broadening Signal/SMS/Photon target parsing
• add parser and send_message_tool regression coverage for whatsapp:37576702443707@lid without home-channel fallback

Fixes #59136

Tests

• python -m py_compile tools/send_message_tool.py tests/tools/test_send_message_tool.py
• uv run --extra dev --extra messaging python -m pytest tests/tools/test_send_message_tool.py -q (152 passed, 1 warning: discord.py audioop deprecation)
• uv run --extra dev ruff check tools/send_message_tool.py tests/tools/test_send_message_tool.py
• uv run --extra dev --extra messaging python -m py_compile tools/send_message_tool.py tests/tools/test_send_message_tool.py

[teknium1]

Thanks for the focused regression coverage. This is already resolved on current main (automated hermes-sweeper review).

• ea49a79633d93202d8e495648b2586ee5a1fbecc added native WhatsApp JID parsing, including @lid.
• tools/send_message_tool.py:47–49 includes lid in _WHATSAPP_JID_RE, and tools/send_message_tool.py:590–595 returns matching WhatsApp JIDs as explicit targets.
• tools/send_message_tool.py:367–378 only resolves the channel directory for non-explicit targets, so an @lid target does not fall back to the home channel.
• tests/tools/test_send_message_tool.py:1594–1614 already covers the LID behavior and confirms it remains WhatsApp-only.
• The existing fix shipped in v2026.6.19.

This also confirms the prior resolution noted on #59136.