v0.7.20

Fixed

• Sends to a LID-migrated contact no longer intermittently fail with HTTP 500 on the whatsapp-web.js engine. The v0.7.19 fix resolves such a contact's phone id to its @lid before sending, but that resolution is a WhatsApp Web round-trip that occasionally throws an internal error — in which case the send fell back to the phone id and hit No LID for user again, so the message tester (and the API) still returned a 500 now and then. The engine now caches each contact's confirmed resolution for the session (both a migrated @lid and a confirmed non-migrated @c.us), so a later flaky resolution reuses the known-good id and ordinary contacts are not re-probed on every send. If a send still fails with No LID for user — e.g. a contact that migrates mid-session — the engine drops the stale mapping, re-resolves once, and retries. (#580) Thanks @lexcorp.
• The typing indicator no longer logs a misleading ERROR when sending to a LID-migrated contact. The best-effort "typing…" presence step is already caught and never affects the send, but a failed attempt (No LID for user) was logged at ERROR, which read as a fault even though nothing broke. It now logs at WARN and the typing target is resolved the same way as the send. (#582) Thanks @lexcorp.