(Gj!!dZddlmZddlZddlZddlZddlmZeje Z ej dZ ddl mZdd Zej d Zdd ZddZddZdS)uShared helpers for canonicalising WhatsApp sender identity. WhatsApp's bridge can surface the same human under two different JID shapes within a single conversation: - LID form: ``999999999999999@lid`` - Phone form: ``15551234567@s.whatsapp.net`` Both the authorisation path (:mod:`gateway.run`) and the session-key path (:mod:`gateway.session`) need to collapse these aliases to a single stable identity. This module is the single source of truth for that resolution so the two paths can never drift apart. Public helpers: - :func:`normalize_whatsapp_identifier` — strip JID/LID/device/plus syntax down to the bare numeric identifier. - :func:`canonical_whatsapp_identifier` — walk the bridge's ``lid-mapping-*.json`` files and return a stable canonical identity across phone/LID variants. - :func:`expand_whatsapp_aliases` — return the full alias set for an identifier. Used by authorisation code that needs to match any known form of a sender against an allow-list. Plugins that need per-sender behaviour on WhatsApp (role-based routing, per-contact authorisation, policy gating in a gateway hook) should use ``canonical_whatsapp_identifier`` so their bookkeeping lines up with Hermes' own session keys. ) annotationsN)Setz^[A-Za-z0-9@.+\-]+$)get_hermes_dirvaluestrreturnct|pddddddddddS)aNStrip WhatsApp JID/LID syntax down to its stable numeric identifier. Accepts any of the identifier shapes the WhatsApp bridge may emit: ``"60123456789@s.whatsapp.net"``, ``"60123456789:47@s.whatsapp.net"``, ``"60123456789@lid"``, or a bare ``"+601****6789"`` / ``"60123456789"``. Returns just the numeric identifier (``"60123456789"``) suitable for equality comparisons. Useful for plugins that want to match sender IDs against user-supplied config (phone numbers in ``config.yaml``) without worrying about which variant the bridge happens to deliver. +:r@)rstripreplacesplit)rs ?/home/rurouni/.hermes/hermes-agent/gateway/whatsapp_identity.pynormalize_whatsapp_identifierr0s\ EKR  b!   sAq  sAq  z^\+?[\d\s().\-]+$cN|sdSt|}d|vr>d|vr:|d\}}}|dddd|}d|vr|St|rt jdd|}|r|dS|S)uNormalize an *outbound* WhatsApp target to a bridge-safe JID. Baileys' ``jidDecode`` crashes on a bare phone number — it expects a fully-qualified JID such as ``50766715226@s.whatsapp.net``. This helper is the inverse of :func:`normalize_whatsapp_identifier`: instead of stripping a JID down to its numeric core for comparison, it *builds* the JID a send must use. Behaviour: - ``"+50766715226"`` / ``"50766715226"`` → ``"50766715226@s.whatsapp.net"`` - ``"50766715226@s.whatsapp.net"`` → unchanged - ``"group-id@g.us"`` / ``"130631430344750@lid"`` → unchanged - ``"user:device@s.whatsapp.net"`` style colon-before-``@`` → ``@`` form - anything that isn't a recognizable bare phone → returned unchanged so the bridge can surface a meaningful error rather than us mangling it. Returns ``""`` for an empty/whitespace input. r r rr rz\D+z@s.whatsapp.net)rr partitionr_BARE_PHONE_RE fullmatchresub)r normalizedprefix_domaindigitss rto_whatsapp_jidr Ms( rU!!##J  jSJ..&00556 S!,,Q/::&::  j ++.J//  .--- - r identifierSet[str]ct|}|stStdd}t}|g}|r|d}|r||vrt|s:||dD]}|d||dz }|s" ttj | d}n?#ttj f$r&} td || Yd } ~ d } ~ wwxYw|r||vr||||S) aResolve WhatsApp phone/LID aliases via bridge session mapping files. Returns the set of all identifiers transitively reachable through the bridge's ``$HERMES_HOME/whatsapp/session/lid-mapping-*.json`` files, starting from ``identifier``. The result always includes the normalized input itself, so callers can safely ``in`` check against the return value without a separate fallback branch. Returns an empty set if ``identifier`` normalizes to empty. zplatforms/whatsapp/sessionzwhatsapp/sessionr)r _reversez lid-mapping-z.jsonzutf-8)encodingz(whatsapp_identity: failed to read %s: %sN)rsetrpop_SAFE_IDENTIFIER_REmatchaddexistsjsonloads read_textOSErrorJSONDecodeErrorloggerdebugappend) r!r session_dirresolvedqueuecurrentsuffix mapping_pathmappedexcs rexpand_whatsapp_aliasesr<ys/z::J uu  !=?QRRKH LE %))A,, 'X-- #((11   W& % %F&)N)N)N)N)NNL&&((  6J|55w5GGHHT12    GWZ[[[  %&00 V$$$9 %< Os55C++D'D""D'cjt|}|sdSt|}t|dS)uReturn a stable WhatsApp sender identity across phone-JID/LID variants. WhatsApp may surface the same person under either a phone-format JID (``60123456789@s.whatsapp.net``) or a LID (``1234567890@lid``). This applies to a DM ``chat_id`` *and* to the ``participant_id`` of a member inside a group chat — both represent a user identity, and the bridge may flip between the two for the same human. This helper reads the bridge's ``whatsapp/session/lid-mapping-*.json`` files, walks the mapping transitively, and picks the shortest (numeric-preferred) alias as the canonical identity. :func:`gateway.session.build_session_key` uses this for both WhatsApp DM chat_ids and WhatsApp group participant_ids, so callers get the same session-key identity Hermes itself uses. Plugins that need per-sender behaviour (role-based routing, authorisation, per-contact policy) should use this so their bookkeeping lines up with Hermes' session bookkeeping even when the bridge reshuffles aliases. Returns an empty string if ``identifier`` normalizes to empty. If no mapping files exist yet (fresh bridge install), returns the normalized input unchanged. r c$t||fS)N)len) candidates rz/canonical_whatsapp_identifier..ss9~~y.Ir)key)rr<min)r!raliasess rcanonical_whatsapp_identifierrEsD2/z::J r &j11G wII J J JJr)rrrr)r!rrr")r!rrr)__doc__ __future__rr,loggingrtypingr getLogger__name__r1compiler(hermes_constantsrrrr r<rErrrOs<#"""""    8 $ $ !bj!788++++++4011))))X1111h!K!K!K!K!K!Kr