@oxidezap/whatsapp-rust-bridge 0.6.0 → 0.6.3

package/dist/whatsapp_rust_bridge.d.ts

@@ -91,1406 +91,6 @@ export interface Jid {
     integrator: number;
 }
 
-/** Addressing mode for a group (phone number vs LID). */
-export type AddressingMode = "pn" | "lid";
-
-/** A batched app-state sync finished without leaving every collection synced.  Collections are named as they appear on the wire (`critical_block`, `regular_high`, …) rather than as an enum, so the payload stays stable if the set of collections changes.  `fatal` is the one a consumer usually has to act on: the server refused the collection, and repeating the request gets the same answer. WhatsApp Web treats that as grounds to notify the primary device and log out; this library will not end a session on its own, so it reports the refusal and keeps the connection. When `connected` is true the client dispatched [`Event::Connected`] anyway and is usable, minus whatever those collections carry — for `critical_block` that includes the push name, so presence stays unavailable until it syncs. */
-export interface AppStateSyncFailed {
-    /** Refused outright by the server (400/404). Terminal for this connection. */
-    fatal: string[];
-    /** Did not sync, but a later attempt can. */
-    retryable: string[];
-    /** Another writer held the collection, so this sync did nothing for it. */
-    skipped: string[];
-    /** Whether the client went on to dispatch [`Event::Connected`]. */
-    connected: boolean;
-}
-
-/** App state synchronization key for WhatsApp's app state protocol. */
-export interface AppStateSyncKey {
-    key_data: Uint8Array;
-    fingerprint: Uint8Array;
-    timestamp: number | string;
-}
-
-export interface ArchiveUpdate {
-    /** The chat being archived or unarchived. */
-    jid: Jid;
-    timestamp: number;
-    action: ArchiveChatAction;
-    from_full_sync: boolean;
-}
-
-/** How a [`MessageBatch`] was delivered. This describes the delivery shape, not a message's provenance: whether a stanza came from the offline queue is `info.is_offline` on each [`InboundMessage`]. */
-export type BatchOrigin = "Live" | "OfflineDrain";
-
-/** Action to perform on a blocklist entry. */
-export type BlocklistAction = "block" | "unblock";
-
-export type BotEditType = "first" | "inner" | "last";
-
-export type BusinessHourMode = "open_24h" | "specific_hours" | "appointment_only" | string;
-
-/** Parsed `<notification type="business">` stanza. */
-export interface BusinessNotification {
-    from: Jid;
-    stanza_id: string;
-    timestamp: number | string;
-    notification_type: BusinessNotificationType;
-    jid?: Jid | null;
-    hash?: string | null;
-    verified_name?: VerifiedName | null;
-    product_ids: string[];
-    collection_ids: string[];
-    subscriptions: BusinessSubscription[];
-}
-
-/** Business notification type based on child element. */
-export type BusinessNotificationType = "remove_jid" | "remove_hash" | "verified_name_jid" | "verified_name_hash" | "profile" | "profile_hash" | "product" | "collection" | "subscriptions" | "unknown";
-
-/** Business status update notification. */
-export interface BusinessStatusUpdate {
-    /** The business account whose status changed. */
-    jid: Jid;
-    update_type: BusinessUpdateType;
-    timestamp: number;
-    target_jid?: Jid | null;
-    hash?: string | null;
-    verified_name?: string | null;
-    product_ids: string[];
-    collection_ids: string[];
-    subscriptions: BusinessSubscription[];
-}
-
-/** Business subscription information (SMB features). */
-export interface BusinessSubscription {
-    id: string;
-    status: string;
-    expiration_date?: number | string | null;
-    creation_time?: number | string | null;
-}
-
-/** Type of business status update. */
-export type BusinessUpdateType = "removed_as_business" | "verified_name_changed" | "profile_updated" | "products_updated" | "collections_updated" | "subscriptions_updated" | "unknown";
-
-/** Minimal cached form of a Noise certificate. Mirrors the JSON shape WA Web persists in `waNoiseInfo.certificateChainBuffer` (only `key` plus the validity window — signatures and issuer_serial are intentionally dropped). */
-export interface CachedNoiseCert {
-    /** 32-byte X25519 public key from `NoiseCertificate.Details.key`. */
-    key: Uint8Array;
-    /** Unix epoch seconds. Validation window from `NoiseCertificate.Details`. */
-    not_before: number | string;
-    not_after: number | string;
-}
-
-/** Cached form of the server's two-cert chain. `leaf.key` is the server static public key consumed by Noise IK; the intermediate is kept solely to mirror WA Web's expiry checks. */
-export interface CachedServerCertChain {
-    intermediate: CachedNoiseCert;
-    leaf: CachedNoiseCert;
-}
-
-/** Fields kept per-variant (not a shared `BasicCallMeta`) so the `serde` shape mirrors the stanza 1:1 for downstream JS consumers. */
-export type CallAction =
-| { type: "offer"; call_id: string; call_creator: Jid; caller_pn?: Jid | null; caller_country_code?: string | null; device_class?: string | null; joinable: boolean; is_video: boolean; audio: CallAudioCodec[]; group_jid?: Jid | null }
-| { type: "offer_notice"; call_id: string; call_creator: Jid; is_video: boolean; is_group: boolean }
-| { type: "preaccept"; call_id: string; call_creator: Jid; audio: CallAudioCodec[] }
-| { type: "accept"; call_id: string; call_creator: Jid; audio: CallAudioCodec[] }
-| { type: "reject"; call_id: string; call_creator: Jid; reason?: string | null }
-| { type: "terminate"; call_id: string; call_creator: Jid; reason?: string | null; duration?: number | null; audio_duration?: number | null }
-| { type: "transport"; call_id: string; call_creator: Jid; p2p_cand_round?: string | null; transport_message_type?: string | null }
-| { type: "relaylatency"; call_id: string; call_creator: Jid }
-| { type: "video"; call_id: string; call_creator: Jid; state: VideoState; orientation?: number | null; dec?: string | null }
-| { type: "group_update"; update: GroupCallUpdate }
-| { type: "enc_rekey"; rekey: GroupCallEncRekey }
-| { type: "waiting_room_update"; room: WaitingRoom }
-| { type: "user_action"; call_id: string; call_creator: Jid; raised: boolean }
-| { type: "screen_share"; call_id: string; call_creator: Jid; screen_share: ScreenShare };
-
-export interface CallAudioCodec {
-    enc: string;
-    rate: number;
-}
-
-/** An incoming call we were ringing for was resolved on ANOTHER of our devices (multi-device): the caller dismissed this device with a `<terminate reason="accepted_elsewhere"|"rejected_elsewhere">`. Distinct from [`MissedCall`] (a genuinely unanswered call) so a consumer can render "answered on another device" instead of a missed call. Mirrors WA Web's AcceptedElsewhere / Rejected outcomes. */
-export interface CallEndedElsewhere {
-    from: Jid;
-    /** The call id (from the `<offer>` action); distinct from the `<call>` stanza id. */
-    call_id: string;
-    timestamp: number;
-    outcome: ElsewhereOutcome;
-}
-
-/** Result of creating a reusable call link. */
-export interface CallLink {
-    token: string;
-    media: CallLinkMedia;
-}
-
-/** Admission state returned after joining a reusable call link. */
-export interface CallLinkJoin {
-    token: string;
-    media: CallLinkMedia;
-    call_id: string;
-    call_creator: Jid;
-    waiting_room_enabled: boolean;
-    in_waiting_room: boolean;
-    is_admin: boolean;
-    waiting_room?: WaitingRoom | null;
-    group?: GroupCallUpdate | null;
-}
-
-/** Audio/video mode of a reusable call link. */
-export type CallLinkMedia = "audio" | "video";
-
-/** Metadata returned without joining a reusable call link. */
-export interface CallLinkPreview {
-    token: string;
-    media: CallLinkMedia;
-    creator: Jid;
-    creator_pn?: Jid | null;
-    waiting_room_enabled: boolean;
-    is_admin: boolean;
-}
-
-/** Identifies a specific message within a chat. */
-export interface ChatMessageId {
-    chat: Jid;
-    id: string;
-}
-
-export type ChatPresence = "composing" | "paused";
-
-export type ChatPresenceMedia = "" | "audio";
-
-export interface ChatPresenceUpdate {
-    source: MessageSource;
-    state: ChatPresence;
-    media: ChatPresenceMedia;
-}
-
-/** Chat state type for typing indicators. */
-export type ChatStateType = "composing" | "recording" | "paused";
-
-/** A chat's messages were cleared (kept) on a linked device. */
-export interface ClearChatUpdate {
-    /** The chat being cleared. */
-    jid: Jid;
-    /** From the index, not the proto — ClearChatAction only has messageRange. */
-    delete_starred: boolean;
-    /** From the index, not the proto. */
-    delete_media: boolean;
-    timestamp: number;
-    action: ClearChatAction;
-    from_full_sync: boolean;
-}
-
-export interface ClientOutdated {
-    /** The whole `<failure>` stanza, so no attribute is lost to a log line. */
-    raw?: any | null;
-}
-
-export interface ConnectFailure {
-    reason: ConnectFailureReason;
-    /** The server's `message` attribute on the `<failure>` stanza, when present. */
-    message?: string | null;
-    raw?: any | null;
-}
-
-/** Wire codes: 400=Generic, 401=LoggedOut, 402=TempBanned, 403=AccountLocked, 406=UnknownLogout, 405=ClientOutdated, 409=BadUserAgent, 413=CatExpired, 414=CatInvalid, 415=NotFound, 418=ClientUnknown, 500=InternalServerError, 501=Experimental, 503=ServiceUnavailable */
-export type ConnectFailureReason = number;
-
-/** A contact changed their phone number.  Emitted from `<notification type="contacts"><modify old="..." new="..." old_lid="..." new_lid="..."/>`.  The library updates the global LID-PN cache when both `old_lid` and `new_lid` are present, mirroring `WAWebDBCreateLidPnMappings`. No Signal session is wiped (WA Web `WAWebHandleContactNotification` also leaves sessions intact). Group participant updates arrive via separate `w:gp2` notifications, so per-group caches are not touched here. Consumers can subscribe and refresh their own caches if needed. */
-export interface ContactNumberChanged {
-    /** Old phone number JID. */
-    old_jid: Jid;
-    /** New phone number JID. */
-    new_jid: Jid;
-    /** Old LID (if provided by server). */
-    old_lid?: Jid | null;
-    /** New LID (if provided by server). */
-    new_lid?: Jid | null;
-    timestamp: number;
-}
-
-/** Server requests a full contact re-sync.  Emitted from `<notification type="contacts"><sync after="..."/>`. */
-export interface ContactSyncRequested {
-    after?: number | null;
-    timestamp: number;
-}
-
-export interface ContactUpdate {
-    /** The chat/contact this sync action applies to. */
-    jid: Jid;
-    timestamp: number;
-    action: ContactAction;
-    from_full_sync: boolean;
-}
-
-/** A contact's profile changed (server notification).  Emitted from `<notification type="contacts"><update jid="..."/>`. WA Web resets cached presence and refreshes the profile picture on this event — consumers should invalidate any cached presence/profile data.  Not to be confused with [`ContactUpdate`] which comes from app-state sync mutations (different source, different payload). */
-export interface ContactUpdated {
-    /** The contact whose profile was updated. */
-    jid: Jid;
-    timestamp: number;
-}
-
-export type DayOfWeek = "sun" | "mon" | "tue" | "wed" | "thu" | "fri" | "sat" | string;
-
-export type DecryptFailMode = "show" | "hide";
-
-export interface DeleteChatUpdate {
-    /** The chat being deleted. */
-    jid: Jid;
-    /** From the index, not the proto — DeleteChatAction only has messageRange. */
-    delete_media: boolean;
-    timestamp: number;
-    action: DeleteChatAction;
-    from_full_sync: boolean;
-}
-
-export interface DeleteMessageForMeUpdate {
-    /** The chat containing the deleted message. */
-    chat_jid: Jid;
-    participant_jid?: Jid | null;
-    message_id: string;
-    from_me: boolean;
-    timestamp: number;
-    action: DeleteMessageForMeAction;
-    from_full_sync: boolean;
-}
-
-export interface Device {
-    pn?: Jid | null;
-    lid?: Jid | null;
-    registration_id: number;
-    noise_key: KeyPair;
-    identity_key: KeyPair;
-    signed_pre_key: KeyPair;
-    signed_pre_key_id: number;
-    signed_pre_key_signature: Uint8Array;
-    adv_secret_key: Uint8Array;
-    account?: ADVSignedDeviceIdentity | null;
-    push_name: string;
-    app_version_primary: number;
-    app_version_secondary: number;
-    app_version_tertiary: number;
-    app_version_last_fetched_ms: number | string;
-    /** Edge routing info received from server, used for optimized reconnection. When present, this should be sent as a pre-intro before the Noise handshake. */
-    edge_routing_info?: Uint8Array | null;
-    /** Hash from the last props (A/B experiment config) fetch. Sent on subsequent connects to enable delta updates instead of full fetches. */
-    props_hash?: string | null;
-    /** Monotonically increasing counter for one-time pre-key ID generation. Matches WhatsApp Web's `NEXT_PK_ID` pattern: only increases, never resets. Advances at GENERATION time (WA Web `savePreKeys`), so it covers every key that exists in the store, uploaded or not. */
-    next_pre_key_id: number;
-    /** Watermark of the first generated-but-not-yet-uploaded one-time prekey, matching WA Web's `FIRST_UNUPLOAD_PK_ID`. `next_pre_key_id - this` is the pool of leftover keys an upload re-offers before generating new ones. `0` = unset (legacy device); initialised on the first upload. */
-    first_unupload_pre_key_id: number;
-    /** Persisted flag matching WA Web's `signal_sever_has_pre_keys` metadata. */
-    server_has_prekeys: boolean;
-    /** NCT salt provisioned by the server via app state sync or history sync. */
-    nct_salt?: Uint8Array | null;
-    /** Server cert chain cached from the last successful XX (or XX-fallback) handshake. Enables Noise IK on the next connect by exposing `leaf.key` as the server's static public key, and lets us reject stale entries via `not_after` before even attempting IK. `None` forces XX on the next connect. */
-    server_cert_chain?: CachedServerCertChain | null;
-    /** Login counter sent as `ClientPayload.lc` on every login. WA Web's `WAWebUserPrefsGeneral.getLoginCounter()` reads (and bumps) this from localStorage on each connect; the server uses it as an anti-abuse signal. Persisted so it survives restarts. */
-    login_counter: number;
-    /** WA Web's `WAIsAccountLidFieldMigrated` pref: whether the account is 1:1-LID-migrated. Set from `ClientPairingProps.isChatDbLidMigrated` at pair time or when the primary pushes migration mappings. Gates outbound DM wire addressing (LID vs PN); the Signal session layer stays LID-first regardless, mirroring WAWebSignalAddress. Once set it never reverts, like the WA Web pref. */
-    lid_migrated: boolean;
-    /** Wall-clock ms of the last signed-pre-key rotation, driving WA Web's `RotateKeyJob` cadence. Fresh devices baseline off creation; devices persisted before this field existed deserialize to `0`, which the rotation path treats as "seed the baseline, don't rotate yet". */
-    last_signed_pre_key_rotation_ms: number | string;
-    /** true means the account's `readreceipts` privacy is `none`, so DM read/played receipts go out as `*-self` (which don't notify the sender). Persisted so the value is known on reconnect before the privacy fetch completes; `false` (WA default `all`) sends plain `read`/`played`. */
-    read_receipts_disabled: boolean;
-}
-
-/** Device element from notification.  Wire format: ```xml <device jid="185169143189667:75@lid" key-index="2" lid="..."/> ```  Device ID is extracted from the JID's device part (e.g., 75 from "user:75@lid").  Per WhatsApp Web: if both `jid` and `lid` attributes are present, the device IDs must match or the notification is rejected. */
-export interface DeviceElement {
-    /** Device JID (contains user and device ID) */
-    jid: Jid;
-    /** Optional key index */
-    key_index?: number | null;
-    /** Optional LID (device ID must match jid's device ID if present) */
-    lid?: Jid | null;
-}
-
-/** Device information for registry tracking. */
-export interface DeviceInfo {
-    /** The device ID (0 = primary device, 1+ = companion devices) */
-    device_id: number;
-    /** The key index, if known */
-    key_index?: number | null;
-    /** Whether the device uses the hosted PN/LID address space. */
-    is_hosted: boolean;
-}
-
-/** Device list record matching WhatsApp Web's DeviceListRecord structure. */
-export interface DeviceListRecord {
-    /** The user part of the JID (phone number or LID) */
-    user: string;
-    /** List of known devices for this user */
-    devices: DeviceInfo[];
-    /** Timestamp when this record was last updated */
-    timestamp: number | string;
-    /** Participant hash from usync, if available */
-    phash?: string | null;
-    /** ADV raw_id from `ADVKeyIndexList` — used to detect identity changes. When this changes, all sessions and sender keys for the user must be cleared. */
-    raw_id?: number | null;
-}
-
-/** Device list update notification. Emitted when a user's device list changes (device added/removed/updated). */
-export interface DeviceListUpdate {
-    /** The user whose device list changed (from attribute) */
-    user: Jid;
-    /** Optional LID user (for LID-PN mapping) */
-    lid_user?: Jid | null;
-    /** Type of update (add/remove/update) */
-    update_type: DeviceListUpdateType;
-    /** Affected devices with detailed info */
-    devices: DeviceNotificationInfo[];
-    /** Key index info (for add/remove) */
-    key_index?: KeyIndexInfo | null;
-    /** Contact hash (for update - used for contact lookup) */
-    contact_hash?: string | null;
-}
-
-/** Type of device list update notification. Matches WhatsApp Web's device notification types. */
-export type DeviceListUpdateType = "add" | "remove" | "update";
-
-/** Parsed device notification stanza.  Wire format: ```xml <notification from="185169143189667@lid" id="..." t="..." type="devices" lid="..."> <remove> <device jid="185169143189667:75@lid"/> <key-index-list ts="1769296600"/> </remove> </notification> ```  Reference: WhatsApp Web `WAWebHandleDeviceNotification` parser (5Yec01dI04o.js:23125-23183)  Per WhatsApp Web: Only ONE operation per notification is processed. Priority order: remove > add > update */
-export interface DeviceNotification {
-    /** User JID (from attribute) */
-    from: Jid;
-    /** Optional LID user (for LID-PN mapping learning) */
-    lid_user?: Jid | null;
-    /** Stanza ID (for ACK) */
-    stanza_id: string;
-    /** Timestamp */
-    timestamp: number | string;
-    /** The operation (one per notification, priority: remove > add > update) */
-    operation: DeviceOperation;
-}
-
-/** Device information from notification. */
-export interface DeviceNotificationInfo {
-    /** Device ID (extracted from JID) */
-    device_id: number;
-    /** Optional key index */
-    key_index?: number | null;
-}
-
-/** Device notification operation type.  Wire format: Child element tag of `<notification type="devices">` - `<add>` - Device was added - `<remove>` - Device was removed - `<update>` - Device info updated (hash-based lookup) */
-export type DeviceNotificationType = "add" | "remove" | "update";
-
-/** Operation content (add/remove/update child element).  Wire format per WhatsApp Web (5Yec01dI04o.js:23141-23180): ```xml <add> <device jid="user:75@lid" key-index="2"/> <key-index-list ts="...">SIGNED_BYTES</key-index-list> </add> <!-- OR --> <remove> <device jid="user:75@lid"/> <key-index-list ts="..."/>  <!-- ts required for remove --> </remove> <!-- OR --> <update hash="CONTACT_HASH"/> ```  Note: WhatsApp Web does NOT read any attributes from add/remove nodes. The `device_hash` attribute (if present) is not used by the official client. */
-export interface DeviceOperation {
-    /** Operation type (add/remove/update) */
-    operation_type: DeviceNotificationType;
-    /** Contact hash (for update only) - from `hash` attribute, used for contact lookup */
-    contact_hash?: string | null;
-    /** Device elements (for add/remove, single device per WhatsApp Web) */
-    devices: DeviceElement[];
-    /** Key index info (required for add/remove per WhatsApp Web) */
-    key_index?: KeyIndexInfo | null;
-}
-
-export interface DeviceSentMeta {
-    destination_jid: string;
-    phash: string;
-}
-
-/** A valid `<ib><dirty>` marker received from the server.  The client still performs its built-in clean/resync work; this event lets consumers refresh domain-specific derived state without observing every raw stanza. */
-export interface DirtyState {
-    dirty_type: DirtyType;
-    timestamp?: number | string | null;
-}
-
-export type DirtyType = "account_sync" | "groups" | "syncd_app_state" | "newsletter_metadata" | string;
-
-export type DisallowedListAction = "add" | "remove";
-
-/** A contact's default disappearing messages setting changed.  Sent by the server as `<notification type="disappearing_mode">`. WA Web: `WAWebHandleDisappearingModeNotification` → `WAWebUpdateDisappearingModeForContact`. */
-export interface DisappearingModeChanged {
-    /** The contact whose setting changed. */
-    from: Jid;
-    /** New duration in seconds (0 = disabled, 86400 = 24h, etc.). */
-    duration: number;
-    /** When the setting was changed. Consumers should only apply this if it's newer than their stored value. */
-    setting_timestamp: number;
-}
-
-/** Why the transport connection ended. Lets a benign server-initiated stream recycle (a clean Close frame) be told apart from an abrupt EOF or a real read error when diagnosing reconnect behavior.  Serialize: carried by `events::Disconnected`, whose payload consumers forward as JSON (webhooks, dashboards) — snake_case so the wire shape doesn't leak Rust variant naming. */
-export type DisconnectReason =
-| { "server_close": { code?: number | null; reason: string } }
-| "stream_ended"
-| { "read_error": string }
-| "unknown";
-
-export interface Disconnected {
-    /** Why the transport ended — lets consumers tell a routine server stream recycle (`reason.is_clean_shutdown()`) from a genuine transport failure without parsing logs. */
-    reason: DisconnectReason;
-}
-
-export type EditAttribute = "" | "1" | "2" | "3" | "7" | "8" | string;
-
-/** Which terminal outcome another of our devices reached for a call we were ringing for. */
-export type ElsewhereOutcome = "accepted" | "rejected";
-
-/** Review state for an appeal on a suspended group. */
-export type GroupAppealStatus = "approved" | "in_review" | "none" | "rejected";
-
-/** One device in an authoritative group-call roster. */
-export interface GroupCallDevice {
-    jid: Jid;
-    platform?: string | null;
-    pid?: number | null;
-    capability_version?: number | null;
-}
-
-/** One encrypted keygen-v2 epoch delivered to a participant device. */
-export interface GroupCallEncRekey {
-    call_id: string;
-    call_creator: Jid;
-    transaction_id: number;
-    key_generation: number;
-    encryption_type: string;
-    encryption_version: number;
-}
-
-/** One user in an authoritative group-call roster. */
-export interface GroupCallParticipant {
-    jid: Jid;
-    state?: string | null;
-    participant_type?: string | null;
-    devices: GroupCallDevice[];
-}
-
-/** Shared relay allocation embedded in a group snapshot. */
-export interface GroupCallRelay {
-    transaction_id?: number | null;
-    self_pid?: number | null;
-    uuid: string;
-    participant_uuid: string;
-    attribute_padding: boolean;
-    warp_mi_tag_len?: number | null;
-    endpoints: GroupCallRelayEndpoint[];
-}
-
-/** One address advertised by the shared group relay. */
-export interface GroupCallRelayEndpoint {
-    relay_id: number;
-    token_id: number;
-    auth_token_id: number;
-    relay_name: string;
-    domain_name?: string | null;
-    rtt_ms?: number | null;
-    is_fna: boolean;
-    ipv4?: string | null;
-    port?: number | null;
-}
-
-/** One transaction-ordered authoritative group-call snapshot. */
-export interface GroupCallUpdate {
-    call_id: string;
-    call_creator: Jid;
-    group_jid?: Jid | null;
-    transaction_id: number;
-    media: string;
-    connected_limit: number;
-    joinable: boolean;
-    av_upgradable: boolean;
-    rekey_requested: boolean;
-    participants: GroupCallParticipant[];
-    relay?: GroupCallRelay | null;
-}
-
-/** Delivery state for history shared with a newly joined participant. */
-export type GroupHistorySentState = "HISTORY_NOT_SENT" | "HISTORY_SENT" | "NOTICE_SENT";
-
-export interface GroupInfo {
-    participants: Jid[];
-    addressing_mode: AddressingMode;
-    /** Whether this group is a Community Announcement Group (WA Web `isCag`, derived from `default_sub_group`). `None` means the persisted blob predates the field, so the answer is unknown and callers must re-query. */
-    is_community_announce?: boolean | null;
-    /** Maps a LID user identifier (the `user` part of the LID JID) to the corresponding phone-number JID. This is used for device queries since LID usync requests may not work reliably. */
-    lid_to_pn_map: Record<string, Jid>;
-}
-
-/** All possible group notification action types.  Maps 1:1 to `GROUP_NOTIFICATION_TAG` child element tags from WhatsApp Web.  The `#[wire = "..."]` attribute is the SINGLE source of truth for each variant's wire tag: the JSON discriminator (via the auto-derived `Serialize`), the parser dispatch (via the auto-generated sibling `GroupNotificationActionTag` enum), and `wire_tag()` / `tag_name()` all read from the same table. */
-export type GroupNotificationAction =
-| { type: "add"; participants: GroupParticipantInfo[]; reason?: string | null }
-| { type: "remove"; participants: GroupParticipantInfo[]; reason?: string | null }
-| { type: "promote"; participants: GroupParticipantInfo[] }
-| { type: "demote"; participants: GroupParticipantInfo[] }
-| { type: "modify"; participants: GroupParticipantInfo[] }
-| { type: "subject"; subject: string; subject_owner?: Jid | null; subject_time?: number | string | null }
-| { type: "description"; id: string; description?: string | null }
-| { type: "locked"; threshold?: string | null }
-| { type: "unlocked" }
-| { type: "announcement" }
-| { type: "not_announcement" }
-| { type: "ephemeral"; expiration: number; trigger?: number | null }
-| { type: "membership_approval_mode"; enabled: boolean }
-| { type: "membership_approval_request"; request_method: MembershipRequestMethod; parent_group_jid?: Jid | null }
-| { type: "created_membership_requests"; request_method: MembershipRequestMethod; parent_group_jid?: Jid | null; requests: GroupParticipantInfo[] }
-| { type: "revoked_membership_requests"; participants: Jid[] }
-| { type: "member_add_mode"; mode: string }
-| { type: "no_frequently_forwarded" }
-| { type: "frequently_forwarded_ok" }
-| { type: "invite"; code: string }
-| { type: "revoke" }
-| { type: "growth_locked"; expiration: number; lock_type: string }
-| { type: "growth_unlocked" }
-| { type: "create" }
-| { type: "delete"; reason?: string | null }
-| { type: "link"; link_type: string }
-| { type: "unlink"; unlink_type: string; unlink_reason?: string | null }
-| { type: "linked_group_promote"; participants: GroupParticipantInfo[] }
-| { type: "linked_group_demote"; participants: GroupParticipantInfo[] }
-| { type: "suspended" }
-| { type: "unsuspended" }
-| { type: "auto_add_disabled" }
-| { type: "is_capi_hosted_group" }
-| { type: "group_safety_check" }
-| { type: "limit_sharing_enabled"; trigger?: number | null }
-| { type: "allow_admin_reports" }
-| { type: "not_allow_admin_reports" }
-| { type: "reports" }
-| { type: "allow_non_admin_sub_group_creation" }
-| { type: "not_allow_non_admin_sub_group_creation" }
-| { type: "created_sub_group_suggestion" }
-| { type: "revoked_sub_group_suggestions" }
-| { type: "change_number"; new_owner?: Jid | null; sub_group_suggestions: Jid[] }
-| { type: string; tag: string };
-
-/** Participant info extracted from `<participant>` child elements.  Wire format: ```xml <participant jid="..." type="..." lid="..." phone_number="..." username="..." display_name="..." join_time="..."/> ```  `display_name` is the server-rendered label (e.g. `"+55∙∙∙∙∙∙∙∙∙79"` when the requester is not in the participant's contacts). `type` flags admin/superadmin tier; LID-addressed groups also carry `lid` and `username`. WA Web's `WAWebHandleGroupNotification` y() reads all of these into the participant model so the UI can render notifications and patch admin caches without resolving the contact locally. */
-export interface GroupParticipantInfo {
-    jid: Jid;
-    phone_number?: Jid | null;
-    /** Server-provided display label for this participant. Only populated for `<participant>` children inside group notifications; `None` for `<requested_user>` (WA Web doesn't read it there either). */
-    display_name?: string | null;
-    /** Admin tier. Defaults to `Participant` when the attr is missing. */
-    type?: GroupParticipantType | null;
-    /** LID JID when this `<participant>` carries a separate `lid` attr. Distinct from `jid` which may already be a LID. */
-    lid?: Jid | null;
-    /** Username, gated by `WAWebUsernameGatingUtils`. Empty in classic PN-addressed groups. */
-    username?: string | null;
-    /** Unix seconds since the participant joined the group. Used by admin UI for tenure display. */
-    join_time?: number | string | null;
-    /** Delivery state for post-join group history. */
-    group_history_sent_state?: GroupHistorySentState | null;
-}
-
-/** Admin tier from `<participant type="...">`. Mirrors `GROUP_PARTICIPANT_TYPES` in `WAWebGroupApiConst`. */
-export type GroupParticipantType = "participant" | "admin" | "superadmin";
-
-/** Query request type. */
-export type GroupQueryRequestType = "interactive";
-
-/** Group update notification.  Emitted for each action in a `<notification type="w:gp2">` stanza. A single notification may produce multiple `GroupUpdate` events (one per action). */
-export interface GroupUpdate {
-    /** The group this update applies to */
-    group_jid: Jid;
-    /** Identifier of the source notification stanza. */
-    notification_id?: string | null;
-    /** Display name supplied with the source notification. */
-    notify?: string | null;
-    /** Raw offline-delivery marker supplied with the source notification. */
-    offline?: string | null;
-    /** Zero-based emitted-action index within the source notification. */
-    action_index: number;
-    /** The admin/user who triggered the change (`participant` attribute) */
-    participant?: Jid | null;
-    /** Phone number JID of the participant (for LID-addressed groups) */
-    participant_pn?: Jid | null;
-    /** Username of the participant, when supplied by the group notification. */
-    participant_username?: string | null;
-    /** Country code supplied for the participant by the server. */
-    participant_country_code?: string | null;
-    /** When the change occurred */
-    timestamp: number;
-    /** Whether the group uses LID addressing mode */
-    is_lid_addressing_mode: boolean;
-    /** Whether participant identity information was incomplete in the source stanza. */
-    has_incomplete_participant_information: boolean;
-    /** The specific action */
-    action: GroupNotificationAction;
-}
-
-export type HostType = "primary" | "fallback" | string;
-
-/** Identity key changed for a user (e.g., user reinstalled WhatsApp). Emitted after device record cleanup so sessions and sender keys are cleared. */
-export interface IdentityChange {
-    /** The user whose identity changed */
-    user: Jid;
-    /** Optional LID for the user */
-    lid_user?: Jid | null;
-    /** `true` when detected locally while saving a peer's new identity during decrypt (mirrors WA Web `saveIdentity` -> `handleNewIdentity`), `false` when triggered by the server's `<identity/>` notification. */
-    implicit: boolean;
-}
-
-/** One decrypted inbound message. The same items (and order) back both consumer surfaces: the durability hook's batch and [`Event::Messages`]. */
-export interface InboundMessage {
-    message: any;
-    info: MessageInfo;
-}
-
-export interface IncomingCall {
-    from: Jid;
-    /** Stanza id; distinct from `CallAction::call_id`. */
-    stanza_id: string;
-    notify?: string | null;
-    platform?: string | null;
-    version?: string | null;
-    /** Companion-routing metadata copied from the outer `<call>` wrapper. */
-    participant?: Jid | null;
-    /** Companion recipient metadata copied from the outer `<call>` wrapper. */
-    recipient?: Jid | null;
-    timestamp: number;
-    offline: boolean;
-    action: CallAction;
-    /** Group snapshot embedded in an initial offer or active-call invitation. */
-    group?: GroupCallUpdate | null;
-}
-
-/** IQ request type for WhatsApp protocol queries. */
-export type InfoQueryType = "set" | "get";
-
-/** Key index information from `<key-index-list>` element.  Wire format: ```xml <!-- For add: has signed bytes content --> <key-index-list ts="1769296600">SIGNED_BYTES</key-index-list> <!-- For remove: empty, ts required --> <key-index-list ts="1769296600"/> ```  Required for add/remove operations per WhatsApp Web. */
-export interface KeyIndexInfo {
-    /** Timestamp (required for remove per WhatsApp Web) */
-    timestamp: number | string;
-    /** Signed key index bytes (only present for add) */
-    signed_bytes?: Uint8Array | null;
-}
-
-/** A label was associated with or removed from a chat on a linked device. `action.labeled == Some(true)` means the label was added to the chat. */
-export interface LabelAssociationUpdate {
-    /** The label identifier. */
-    label_id: string;
-    /** The chat the label was associated with or removed from. */
-    chat_jid: Jid;
-    timestamp: number;
-    action: LabelAssociationAction;
-    from_full_sync: boolean;
-}
-
-/** A label was created, renamed/recolored, or deleted on a linked device. `action.deleted == Some(true)` means the label was removed. */
-export interface LabelEditUpdate {
-    /** The label identifier (the index key, not a JID). */
-    label_id: string;
-    timestamp: number;
-    action: LabelEditAction;
-    from_full_sync: boolean;
-}
-
-/** The source from which a LID-PN mapping was learned.  The source is load-bearing, not just provenance: it selects the write policy applied when the pair reaches the cache — see `lid_pn_write_policy` in the `whatsapp-rust` client, which mirrors WhatsApp Web's `createLidPnMappings` `switch (learningSource)`. Directed sources overwrite on any change; observational bulk sources (`Other` and friends, WA Web `"other"`) only seed new LIDs and re-resolve conflicts via a live query; known-stale sources are stamped `created_at = 0` so they never outrank a fresher mapping for the same phone (the PN→LID resolution direction; the LID→PN reverse map always takes the latest write). */
-export type LearningSource = "usync" | "peer_pn_message" | "peer_lid_message" | "recipient_latest_lid" | "migration_sync_latest" | "migration_sync_old" | "blocklist_active" | "blocklist_inactive" | "pairing" | "device_notification" | "other";
-
-/** An entry in the LID-PN cache containing the full mapping information. */
-export interface LidPnEntry {
-    /** The LID user part (e.g., "100000012345678"). `Arc<str>`: the cache stores each mapping under both directions, so the identifier strings are shared between the entry and the cache keys instead of re-allocated per copy (this cache is unbounded by design). */
-    lid: string;
-    /** The phone number user part (e.g., "559980000001") */
-    phone_number: string;
-    /** Unix timestamp when the mapping was first learned */
-    created_at: number | string;
-    /** The source from which this mapping was learned */
-    learning_source: LearningSource;
-}
-
-/** Entry representing a LID to Phone Number mapping. */
-export interface LidPnMappingEntry {
-    /** The LID user part (e.g., "100000012345678") */
-    lid: string;
-    /** The phone number user part (e.g., "559980000001") */
-    phone_number: string;
-    /** Unix timestamp when the mapping was first learned */
-    created_at: number | string;
-    /** Unix timestamp when the mapping was last updated */
-    updated_at: number | string;
-    /** The source from which this mapping was learned (e.g., "usync", "peer_pn_message") */
-    learning_source: string;
-}
-
-export interface LoggedOut {
-    on_connect: boolean;
-    reason: ConnectFailureReason;
-    /** Server-supplied logout copy, when it sent any. Present in practice on [`ConnectFailureReason::AccountLocked`]. */
-    logout_message?: LogoutMessage | null;
-    /** The whole stanza that caused the logout, when one did.  Two shapes reach here, so dispatch on `raw.tag` rather than assuming one: `<failure>` for a server-side refusal (`on_connect` is then true), and `<stream:error>` for a `<conflict>`, a 516 device removal or a 401. `None` when nothing was received at all — a locally initiated logout has no stanza to report.  A forced logout is where the server puts data it will never repeat: an account lock carries a one-time `appeal_token` plus `violation_reason` and `vt`, which WA Web ignores (its own appeal flow is native) but which an embedder cannot recover once the stanza is gone. Parsing policy stays with the consumer — `violation_reason` is not a closed set — but the bytes have to survive the dispatch. */
-    raw?: any | null;
-}
-
-/** Localized text the server wants shown when it forces a logout, from `logout_message_header` / `logout_message_subtext` on `<failure>`.  `locale` is what makes the text safe to render: WA Web (`WAWebHandleFailure`) shows the header/subtext only when the locale equals the client's current one, and otherwise falls back to its own generic copy. It travels with the text so a consumer can apply the same rule. */
-export interface LogoutMessage {
-    header?: string | null;
-    subtext?: string | null;
-    /** e.g. `"pt_BR"`. Compare against the consumer's locale before rendering. */
-    locale?: string | null;
-}
-
-export interface MarkChatAsReadUpdate {
-    /** The chat being marked as read or unread. */
-    jid: Jid;
-    timestamp: number;
-    action: MarkChatAsReadAction;
-    from_full_sync: boolean;
-}
-
-/** Member link mode for group invite links. */
-export type MemberLinkMode = "admin_link" | "all_member_link";
-
-/** Who can share message history with new members. */
-export type MemberShareHistoryMode = "admin_share" | "all_member_share";
-
-/** How a membership request was initiated.  Maps to `WAWebRequestMethodType` in WhatsApp Web JS. */
-export type MembershipRequestMethod = "invite_link" | "linked_group_join" | "non_admin_add";
-
-/** Payload of [`Event::Messages`]: the decrypted messages of one durable commit, in arrival order. Behaves as a collection of its messages — `for msg in &batch`, `batch.iter()`, `batch.len()` — with `origin` carrying the delivery shape alongside. */
-export interface MessageBatch {
-    messages: InboundMessage[];
-    origin: BatchOrigin;
-    /** Whether an inbound durability hook already committed these messages before this event was dispatched.  Orthogonal to [`origin`](Self::origin), which describes delivery shape: a hook commits live batches and drain batches alike. What this answers is whether the consumer's own durable copy already exists, so a materializer that the hook feeds can skip the batch instead of rewriting every row (and re-firing every invalidation) a second time.  `false` for the producers that dispatch `Event::Messages` while deliberately bypassing the commit pipeline — newsletters and PDO-recovered messages — because for those the materialization on this event is the only one there is. */
-    hook_committed: boolean;
-}
-
-export type MessageCategory = "" | "peer" | string;
-
-export interface MessageInfo {
-    source: MessageSource;
-    id: string;
-    server_id: number;
-    type: string;
-    push_name: string;
-    timestamp: number;
-    category: MessageCategory;
-    multicast: boolean;
-    media_type: string;
-    edit: EditAttribute;
-    bot_info?: MsgBotInfo | null;
-    meta_info: MsgMetaInfo;
-    /** Decoded `<verified_name>` child cert of business senders; the display name is in `.name`. Boxed: most messages carry none. */
-    verified_name?: VerifiedName | null;
-    device_sent_meta?: DeviceSentMeta | null;
-    /** Ephemeral duration in seconds, extracted from `contextInfo.expiration`. */
-    ephemeral_expiration?: number | null;
-    /** Whether this message was delivered during offline sync. */
-    is_offline: boolean;
-    /** Set when this message was recovered via PDO rather than normal decryption. Contains the PDO request message ID. */
-    unavailable_request_id?: string | null;
-    /** Server-store timestamp in microseconds (envelope `sts` attr). Used by WA Web for read-self watermark ordering across companion devices. */
-    server_timestamp_us?: number | string | null;
-    /** Envelope `verified_level` attr (e.g. "unknown"/"low"/"high"). For business messages this is the server-asserted verification tier; for regular messages it is absent. */
-    verified_level?: string | null;
-    /** Envelope `verified_name` int attr (business name certificate serial). Separate from the `verified_name` child cert bytes already on this struct. */
-    verified_name_serial?: number | string | null;
-    /** Envelope `peer_recipient_pn` attr. Present on companion-device self-synced DM stanzas to identify the peer's PN (so the receipt goes to the right routing target). */
-    peer_recipient_pn?: Jid | null;
-    /** Parent post key when the dispatched message is a decrypted CAG channel comment (`enc_comment_message`). The inner `Message` proto has no slot for the threading link, so it surfaces here. */
-    comment_target?: MessageKey | null;
-    /** Broadcast-contact-list recipients from `<participants><to jid>` on an incoming broadcast/status stanza. Populated only for broadcasts; used to validate a `deviceSentMessage.phash` (WA Web `validateBclHash`). Empty otherwise. */
-    bcl_participants: Jid[];
-}
-
-export interface MessageSource {
-    chat: Jid;
-    sender: Jid;
-    is_from_me: boolean;
-    is_group: boolean;
-    addressing_mode?: AddressingMode | null;
-    sender_alt?: Jid | null;
-    recipient_alt?: Jid | null;
-    broadcast_list_owner?: Jid | null;
-    recipient?: Jid | null;
-}
-
-/** MEX GraphQL error extensions. */
-export interface MexErrorExtensions {
-    error_code?: number | null;
-    is_summary?: boolean | null;
-    is_retryable?: boolean | null;
-    severity?: string | null;
-}
-
-/** MEX GraphQL error. */
-export interface MexGraphQLError {
-    message: string;
-    extensions?: MexErrorExtensions | null;
-}
-
-/** `payload` shape depends on `op_name`. `offline` mirrors the raw string the server sets when replaying backlog (often a timestamp); presence alone signals backlog vs live. */
-export interface MexNotification {
-    op_name: string;
-    from?: Jid | null;
-    stanza_id?: string | null;
-    offline?: string | null;
-    payload: Value;
-}
-
-/** MEX GraphQL response. */
-export interface MexResponse {
-    data?: Value | null;
-    errors?: MexGraphQLError[] | null;
-}
-
-/** A call that must NOT ring: surfaced instead of [`IncomingCall`] so a consumer cannot auto-accept it. Currently this is an offer the server replayed from the offline queue on reconnect (the `<call>` carried the `offline` attribute) -- the call is long dead (no relay, not connectable). Mirrors WA Web's `cancel_call` + `missed_call` path for `offerReceivedWhileOffline`. */
-export interface MissedCall {
-    from: Jid;
-    /** The call id (from the `<offer>` action); distinct from the `<call>` stanza id. */
-    call_id: string;
-    timestamp: number;
-    reason: MissedReason;
-}
-
-/** Why a call surfaced as missed rather than ringing. */
-export type MissedReason = "offline" | "remote";
-
-export interface MsgBotInfo {
-    edit_type?: BotEditType | null;
-    edit_target_id?: string | null;
-    edit_sender_timestamp_ms?: number | null;
-}
-
-export interface MsgMetaInfo {
-    target_id?: string | null;
-    target_sender?: Jid | null;
-    /** `<meta target_chat_jid="…">` — present when the bot reply addresses a chat distinct from the stanza-level `from` (used for msmsg secret lookup; see WA Web `decryptMsmsgBotMessage`). */
-    target_chat?: Jid | null;
-    deprecated_lid_session?: boolean | null;
-    thread_message_id?: string | null;
-    thread_message_sender_jid?: Jid | null;
-    /** `<meta content_type=...>` attr. Server marks reactions/edits as `"add_on"`; mirrors `WAWebHandleMsgParser` b()'s metadata read. */
-    content_type?: string | null;
-    /** `<meta appdata=...>` attr. `"default"` is the only observed value. */
-    appdata?: string | null;
-    /** `<reporting><reporting_tag>` content bytes (16 or 20). Pre-requisite for the server-side report-abuse flow. */
-    reporting_tag?: Uint8Array | null;
-    /** `<reporting><reporting_token>` content bytes (16). Pre-requisite for the server-side report-abuse flow. */
-    reporting_token?: Uint8Array | null;
-    /** `v` attr on `<reporting_token>`. WA Web defaults to 1 when missing. */
-    reporting_token_version?: number | string | null;
-}
-
-/** Message-secret write entry keyed by chat, sender, and message ID. */
-export interface MsgSecretEntry {
-    /** Canonical non-AD chat JID. Shared across entries from the same history conversation instead of allocating one identical string per message. */
-    chat: string;
-    /** Canonical non-AD sender JID. Often aliases `chat` for direct messages. */
-    sender: string;
-    /** Message identifier. `Arc<str>` keeps entry clones used by buffered persistence cheap without changing the serialized representation. */
-    msg_id: string;
-    secret: MessageSecret;
-    /** Absolute unix-seconds retention deadline. `0` means never expire. Computed by the caller from the parent message's event time plus a per-add-on-kind horizon (see `MsgSecretRetention`). The store prunes rows whose deadline has passed; it does not know the horizon itself. */
-    expires_at: number | string;
-    /** Parent message event time (unix seconds), or `0` when unknown. Kept so the receive path can enforce the edit-processing window (`editTs < message_ts + window`) the same way WhatsApp Web does. */
-    message_ts: number | string;
-}
-
-export interface MuteUpdate {
-    /** The chat being muted or unmuted. */
-    jid: Jid;
-    timestamp: number;
-    action: MuteAction;
-    from_full_sync: boolean;
-}
-
-/** Wire codes: 421=StaleGroupAddressingMode, 475=NewChatMessagesCapped, 487=ParsingError, 488=UnrecognizedStanza, 489=UnrecognizedStanzaClass, 490=UnrecognizedStanzaType, 491=InvalidProtobuf, 493=InvalidHostedCompanionStanza, 495=MissingMessageSecret, 496=SignalErrorOldCounter, 499=MessageDeletedOnPeer, 500=UnhandledError, 550=UnsupportedAdminRevoke, 551=UnsupportedLIDGroup, 552=DBOperationFailed */
-export type NackReason = number;
-
-/** A newsletter live update notification, typically containing updated reaction counts for one or more messages. */
-export interface NewsletterLiveUpdate {
-    /** The newsletter channel this update belongs to. */
-    newsletter_jid: Jid;
-    messages: NewsletterLiveUpdateMessage[];
-}
-
-/** A single message entry in a newsletter live update. */
-export interface NewsletterLiveUpdateMessage {
-    server_id: number | string;
-    reactions: NewsletterLiveUpdateReaction[];
-}
-
-/** A reaction count in a newsletter live update. */
-export interface NewsletterLiveUpdateReaction {
-    code: string;
-    count: number | string;
-}
-
-export type NewsletterMessageType = "text" | "media" | "reaction" | "revoke" | "poll_creation" | "poll_vote" | "edit" | string;
-
-export interface OfflineSyncCompleted {
-    count: number;
-}
-
-/** `total` is authoritative; the per-kind counts need not sum to it. */
-export interface OfflineSyncPreview {
-    total: number;
-    app_data_changes: number;
-    messages: number;
-    notifications: number;
-    receipts: number;
-    calls: number;
-    statuses: number;
-}
-
-/** How the server refused a pair-code request, as a matchable status.  The five named variants are the complete set WA Web's own response parser accepts (`WASmaxInMdIqMixinErrors.parseIqMixinErrors`, reached from `WASmaxInMdCompanionHelloResponseError`); anything else makes its RPC throw "unknown error". They exist so a consumer can branch on the refusal instead of matching the formatted message, which is not a stable surface.  Both stages report through this, though they were read off `companion_hello` and the `companion_finish` parser is narrower — `WASmaxInMdCompanionFinishErrors` admits only `bad-request` and `internal-server-error`, and WA Web shows its generic failure for anything else. A code outside that pair is still classified here rather than discarded: what a consumer does about a refusal follows from the code, which is one namespace across both requests, and answering "nothing was refused" to a refusal we can read would be worse than naming it.  The numbers are the `code` attribute, and each is the enum's whole wire form — [`code()`](Self::code) is what `Serialize` emits and what `From<i32>` reads back. WA Web pairs each code with a literal `text` (`429`/`rate-overlimit`, `452`/`feature-not-available`, …) and rejects a response whose two disagree, so construct these through [`from_server`](Self::from_server) rather than from a code alone: it is the only constructor that sees both attributes, and the only one that can decline to classify.  WA Web branches on exactly two of them (`DevicePhoneNumberCodeScreen`, on `CompanionHelloError.type.name`): [`RateOverlimit`](Self::RateOverlimit) becomes "too many attempts, try again later" and [`FeatureNotAvailable`](Self::FeatureNotAvailable) becomes "not available to you yet, link with QR code instead". The rest share a generic "try again or link with the QR code". In every case it resets the linking flow and waits for the person to act — it never retries on its own, and never reads the `backoff` hint, so treat that value as the server's advice rather than a schedule WA Web is known to follow. Wire codes: 400=BadRequest, 403=Forbidden, 429=RateOverlimit, 452=FeatureNotAvailable, 500=InternalServerError */
-export type PairCodeRejection = number;
-
-export interface PairError {
-    id: Jid;
-    lid: Jid;
-    business_name: string;
-    platform: string;
-    error: string;
-}
-
-/** Payload for [`Event::PairPasskeyConfirmation`]. */
-export interface PairPasskeyConfirmation {
-    code: string;
-    skip_handoff_ux: boolean;
-}
-
-/** Payload for [`Event::PairPasskeyError`]. */
-export interface PairPasskeyError {
-    error: string;
-    continuation: boolean;
-}
-
-/** Payload for [`Event::PairPasskeyRequest`]. */
-export interface PairPasskeyRequest {
-    /** Verbatim `PublicKeyCredentialRequestOptions` JSON from the server. Pass it straight to a WebAuthn `get` (e.g. Android Credential Manager), or parse it with `whatsapp_rust::passkey::parse_request_options`. */
-    request_options_json: string;
-}
-
-export interface PairSuccess {
-    id: Jid;
-    lid: Jid;
-    business_name: string;
-    platform: string;
-}
-
-/** Generated pair code for phone number linking. User should enter this code on their phone in WhatsApp > Linked Devices. */
-export interface PairingCode {
-    /** The 8-character pairing code to display. */
-    code: string;
-    /** Approximate validity duration (~180 seconds). */
-    timeout: number;
-}
-
-/** A phone-number pair-code flow failed, so no linking will come of it.  The counterpart to [`PairingCode`] on the failure path, and the only surface that reports it when pairing is driven by `BotBuilder::with_pair_code` — that request runs in a detached task, so nothing returns its error to the caller. `Client::pair_with_code` dispatches this in addition to returning `Err`, matching how the success path both returns the code and emits [`PairingCode`].  Both of the flow's server round trips report here, and the consumer's move is the same either way — this code is finished, request another or fall back to the QR. The later one arrives after a code was already displayed and entered: the phone answered, but the server refused the key bundle that answer produced. Silence at that stage is not this event, because nothing was refused; it surfaces as [`PairingCodeRefresh`] once the timer runs out.  Fires for every failure, including local validation (a phone number that is too short never reaches the server): a consumer waiting on a code needs to learn that it is not coming, whatever the reason. [`rejection`](Self::rejection) is what distinguishes the two — `None` means the request never got an answer from the server.  A claim the failed request itself took is released before this fires, so nothing is left holding the flow and `pair_with_code` can be called again.  Two failures do **not** arrive here, because for them a code may still be on its way and this event would say the opposite — a consumer acting on it would tear down a code that is about to arrive:  - `CodeAlreadyOutstanding` — refused precisely because an earlier code is still live, and the consumer already has it from the [`PairingCode`] that minted it. Retrying is futile until `cancel_pair_code` runs or the window closes. - `Cancelled` — the caller withdrew this request, and a replacement may already own the slot. A superseded request can return this *after* its replacement started, so the event would be uncorrelated with the flow that is actually running.  Both follow from something the caller did, so neither is news, and a direct caller still gets the `Err`.  Whether to retry at all is the point of the fields: back off on [`PairCodeRejection::is_throttled`](crate::pair_code::PairCodeRejection::is_throttled), stop on [`PairCodeRejection::FeatureNotAvailable`](crate::pair_code::PairCodeRejection::FeatureNotAvailable). */
-export interface PairingCodeError {
-    /** The server's refusal, when it answered with one. `None` when the failure was local (validation, no connection) or the request went unanswered (timeout) — nothing was refused, so there is no status to report. */
-    rejection?: PairCodeRejection | null;
-    /** How long the server asked the client to wait, from the `backoff` attribute. Usually absent — WA Web does not read it on this path — but when present it is the server naming its own retry delay, which beats any interval the consumer would pick. */
-    backoff?: number | null;
-    /** The failure rendered for logs. Do not branch on it; use [`rejection`](Self::rejection). */
-    error: string;
-}
-
-/** The in-progress phone-number pairing code should be replaced.  Emitted for the two cases WA Web regenerates on (`Alt/DeviceLinkingApi.js` + `Link/DevicePhoneNumberCodeScreen.react.js`): the server asking for it (`refreshAltLinkingCode` / `forceManualRefresh`, ref-gated against the outstanding flow), and a `companion_finish` that went unanswered for a minute — a primary that could not open the key bundle just goes quiet, so silence is the only signal there is.  The outstanding flow is cleared before this fires, so the consumer can call `pair_with_code` straight away. The previous code is no longer valid. */
-export interface PairingCodeRefresh {
-    /** `true` when the server set `force_manual_refresh` — the code must be re-requested explicitly rather than auto-rotated. */
-    force_manual: boolean;
-}
-
-/** A QR code the consumer renders during multi-device pairing. */
-export interface PairingQrCode {
-    /** The QR payload to render. */
-    code: string;
-    /** How long this code stays valid before the next one rotates in. */
-    timeout: number;
-}
-
-/** The server's `<pair-device>` refs are used up: there is no QR left to render until the connection is re-established.  WA Web's rotation timer (`Handle/PairDevice.js`) reports `UNPAIRED_IDLE` here and stops — it does not close the socket, because an alt-linking (phone-number) flow may still be riding the same connection. */
-export interface PairingQrCodesExhausted {
-    /** `true` when the client closed the connection itself, which it only does with no pair-code flow outstanding. `false` means the socket was left up and reconnecting is the consumer's call. */
-    disconnected: boolean;
-}
-
-/** Participant type (admin level). */
-export type ParticipantType = "member" | "admin" | "superadmin";
-
-export interface PictureUpdate {
-    /** The JID whose picture changed (user or group). */
-    jid: Jid;
-    /** The user who made the change. Present for group picture changes (the admin who changed it). `None` for personal picture updates. */
-    author?: Jid | null;
-    timestamp: number;
-    /** Whether the picture was removed (true) or set/updated (false). */
-    removed: boolean;
-    /** The server-assigned picture ID (from `<set id="..."/>`). `None` for deletions. */
-    picture_id?: string | null;
-}
-
-export interface PinUpdate {
-    /** The chat being pinned or unpinned. */
-    jid: Jid;
-    timestamp: number;
-    action: PinAction;
-    from_full_sync: boolean;
-}
-
-export type PreKeyFetchReason = "identity" | "retry" | string;
-
-export type Presence = "available" | "unavailable";
-
-export interface PresenceUpdate {
-    /** The contact whose presence changed. */
-    from: Jid;
-    unavailable: boolean;
-    last_seen?: number | null;
-}
-
-export type PrivacyCategory = "last" | "online" | "profile" | "status" | "groupadd" | "readreceipts" | "calladd" | "messages" | "defense" | string;
-
-export type PrivacySensitiveType = "1";
-
-export type PrivacyValue = "all" | "contacts" | "none" | "contact_blacklist" | "match_last_seen" | "known" | "off" | "on_standard" | string;
-
-/** Profile picture type (preview thumbnail or full-size). */
-export type ProfilePictureType = "preview" | "image";
-
-export interface PushNameUpdate {
-    /** The contact who changed their push name. */
-    jid: Jid;
-    message: MessageInfo;
-    old_push_name: string;
-    new_push_name: string;
-}
-
-export type PushPriority = "high" | "high_force";
-
-export interface Receipt {
-    source: MessageSource;
-    message_ids: string[];
-    timestamp: number;
-    type: ReceiptType;
-    /** True when the receipt carried the `offline` attribute, i.e. it was drained from the server's offline queue on reconnect rather than delivered live. Mirrors WA Web `incomingMsgReceiptParser` (`offline: maybeAttrString`). */
-    offline: boolean;
-}
-
-/** Chat state type as received from incoming stanzas.  Aligned with WhatsApp Web's `WAChatState` constants: - `typing` = ACTIVE_CHAT_STATE_TYPE.TYPING - `recording_audio` = ACTIVE_CHAT_STATE_TYPE.RECORDING_AUDIO - `idle` = IDLE_CHAT_STATE_TYPE.IDLE */
-export type ReceivedChatState = "typing" | "recording_audio" | "idle";
-
-/** Parsed screen-share state for one participant. */
-export interface ScreenShare {
-    state: ScreenShareState;
-    version: number;
-    screen_share_id?: number | null;
-}
-
-/** Wire state of a screen-share transition. Wire codes: 1=Started, 2=Stopped */
-export type ScreenShareState = number;
-
-export interface SelfPushNameUpdated {
-    from_server: boolean;
-    old_name: string;
-    new_name: string;
-}
-
-/** Payload of [`Event::ServerAck`]: the server acknowledged (or nacked) an outgoing stanza. Server acks cover every outgoing stanza class — message, receipt, notification, call — so consumers should filter on [`class`](Self::class) before correlating ids. */
-export interface ServerAck {
-    /** Id of the acked stanza (for a sent message, its message id). */
-    id: string;
-    /** Stanza class the ack refers to (`"message"`, `"receipt"`, `"notification"`, `"call"`, …). `None` when the server omits it. */
-    class?: string | null;
-    /** Chat/entity the ack refers to, when present and parseable. */
-    from?: Jid | null;
-    /** Server timestamp from the ack's `t` attribute, when present. For a message ack this is the authoritative send timestamp (whatsmeow reads the same attribute into `SendResponse.Timestamp`). */
-    timestamp?: number | null;
-    /** Nack code (e.g. `"479"`) when the server rejected the stanza; `None` for a plain ack. */
-    error?: string | null;
-}
-
-/** The type of spam flow indicating the source of the report. */
-export type SpamFlow = "GroupSpamBannerReport" | "GroupInfoReport" | "MessageMenu" | "ContactInfo" | "StatusReport";
-
-export interface StarUpdate {
-    /** The chat containing the starred or unstarred message. */
-    chat_jid: Jid;
-    /** The participant who sent the message. `Some` for group messages from others, `None` for self-authored or 1-on-1 messages (wire value `"0"`). */
-    participant_jid?: Jid | null;
-    message_id: string;
-    from_me: boolean;
-    timestamp: number;
-    action: StarAction;
-    from_full_sync: boolean;
-}
-
-/** Privacy setting sent in the `<meta>` node of the status stanza. Matches WhatsApp Web's `status_setting` attribute. */
-export type StatusPrivacySetting = "contacts" | "allowlist" | "denylist";
-
-export interface StreamError {
-    code: string;
-    raw?: any | null;
-}
-
-/** Trusted contact privacy token entry.  Matches WhatsApp Web's Chat.tcToken / tcTokenTimestamp / tcTokenSenderTimestamp. */
-export interface TcTokenEntry {
-    /** Raw token bytes received from the server. */
-    token: Uint8Array;
-    /** Unix timestamp (seconds) when the token was received. */
-    token_timestamp: number | string;
-    /** Unix timestamp (seconds) when we last issued our token to this contact. */
-    sender_timestamp?: number | string | null;
-}
-
-/** Wire codes: 101=SentToTooManyPeople, 102=BlockedByUsers, 103=CreatedTooManyGroups, 104=SentTooManySameMessage, 106=BroadcastList */
-export type TempBanReason = number;
-
-export interface TemporaryBan {
-    code: TempBanReason;
-    /** How long the ban lasts — the wire's `expire` is a duration in seconds, not a deadline (WA Web renders it as "You'll be able to use WhatsApp again in {duration}").  Dispatched only when the server sent an `expire` that fits a `Duration`; a ban stanza missing `code`/`expire`, or carrying one that does not, surfaces as [`Event::ConnectFailure`] instead, the way WA Web rejects it rather than inventing a zero. */
-    expire: number;
-    /** The server's `message` attribute, when present. */
-    message?: string | null;
-    /** Support/appeal link the official UI opens for the ban. */
-    url?: string | null;
-    /** The whole `<failure>` stanza. */
-    raw?: any | null;
-}
-
-export type UnavailableType = "unknown" | "view_once" | "hosted" | "bot";
-
-export interface UndecryptableMessage {
-    info: MessageInfo;
-    is_unavailable: boolean;
-    unavailable_type: UnavailableType;
-    decrypt_fail_mode: DecryptFailMode;
-}
-
-export interface UserAboutUpdate {
-    /** The contact whose about text changed. */
-    jid: Jid;
-    status: string;
-    timestamp: number;
-}
-
-/** A contact/group/newsletter's status updates were muted/unmuted on a linked device. */
-export interface UserStatusMuteUpdate {
-    /** The entity whose status was (un)muted. */
-    jid: Jid;
-    /** `true` = status muted, `false` = unmuted. */
-    muted: boolean;
-    timestamp: number;
-    action: UserStatusMuteAction;
-    from_full_sync: boolean;
-}
-
-/** Addressing mode used by the contact subprotocol. */
-export type UsyncAddressingMode = "pn" | "lid";
-
-export interface UsyncBotCommand {
-    name: string;
-    description: string;
-}
-
-export type UsyncBotProfessionalType = "unknown" | "yes" | "no" | string;
-
-export interface UsyncBotProfileResult {
-    name: string;
-    attributes: string;
-    description: string;
-    category: string;
-    is_default: boolean;
-    prompts: UsyncBotPrompt[];
-    persona_id: string;
-    commands: UsyncBotCommand[];
-    commands_description: string;
-    is_meta_created?: boolean | null;
-    creator_name?: string | null;
-    creator_profile_url?: string | null;
-    posing_as_professional?: UsyncBotProfessionalType | null;
-}
-
-export interface UsyncBotPrompt {
-    emoji: string;
-    text: string;
-}
-
-export interface UsyncBusinessResult {
-    verified_name?: VerifiedName | null;
-}
-
-export interface UsyncContactResult {
-    contact_type: string;
-    username?: string | null;
-    content?: string | null;
-}
-
-/** Usync context. */
-export type UsyncContext = "interactive" | "background" | "message" | "voip";
-
-export interface UsyncDeviceListResult {
-    hash?: string | null;
-    devices: UsyncDeviceResult[];
-}
-
-export interface UsyncDeviceResult {
-    id: number;
-    key_index?: number | null;
-    is_hosted: boolean;
-}
-
-/** Per-user cache hints carried by the devices v2 subprotocol. */
-export interface UsyncDeviceSyncHint {
-    /** Cached device-list hash, if known. */
-    device_hash?: string | null;
-    /** Timestamp associated with the cached hash. */
-    timestamp?: number | string | null;
-    /** Expected timestamp used to detect stale key-index state. */
-    expected_timestamp?: number | string | null;
-}
-
-export interface UsyncDevicesResult {
-    device_list?: UsyncDeviceListResult | null;
-    key_index?: UsyncKeyIndexResult | null;
-}
-
-export interface UsyncDisappearingModeResult {
-    duration_seconds: number;
-    setting_timestamp: number | string;
-    ephemerality_disabled: boolean;
-}
-
-/** Feature names accepted by the USync feature protocol. */
-export type UsyncFeature = "document" | "encrypt" | "encrypt_blist" | "encrypt_contact" | "encrypt_group_gen2" | "encrypt_image" | "encrypt_location" | "encrypt_url" | "encrypt_v2" | "voip" | "multi_agent";
-
-export interface UsyncFeatureResult {
-    feature: UsyncFeature;
-    value: string;
-}
-
-export interface UsyncKeyIndexResult {
-    timestamp: number | string;
-    signed_key_index_bytes?: Uint8Array | null;
-    expected_timestamp?: number | string | null;
-}
-
-/** Usync mode. */
-export type UsyncMode = "query" | "full" | "delta";
-
-/** A protocol value or its per-user error. Errors are boxed because they are rare and contain owned strings; this keeps every successful result variant from inheriting their size. */
-export type UsyncOutcome<T> =
-| { type: "value"; data: T }
-| { type: "error"; data: UsyncSubprotocolError };
-
-/** A known, typed USync subprotocol request. */
-export type UsyncProtocol =
-| { type: "contact"; data: { addressing_mode: UsyncAddressingMode } }
-| { type: "devices" }
-| { type: "status" }
-| { type: "text_status" }
-| { type: "disappearing_mode" }
-| { type: "business" }
-| { type: "picture" }
-| { type: "lid" }
-| { type: "username" }
-| { type: "bot" }
-| { type: "feature"; data: UsyncFeature[] };
-
-/** Known USync protocol tags from the captured WhatsApp Web client. */
-export type UsyncProtocolKind = "feature" | "devices" | "contact" | "picture" | "status" | "business" | "disappearing_mode" | "lid" | "bot" | "username" | "text_status";
-
-/** Sparse per-user result. Large, uncommon payloads are boxed so their layout does not inflate every status/contact/device item in large sync responses. */
-export type UsyncProtocolResult =
-| { type: "contact"; data: UsyncOutcome<UsyncContactResult> }
-| { type: "devices"; data: UsyncOutcome<UsyncDevicesResult> }
-| { type: "status"; data: UsyncOutcome<UsyncStatusResult> }
-| { type: "text_status"; data: UsyncOutcome<UsyncTextStatusResult> }
-| { type: "disappearing_mode"; data: UsyncOutcome<UsyncDisappearingModeResult> }
-| { type: "business"; data: UsyncOutcome<UsyncBusinessResult> }
-| { type: "picture"; data: UsyncOutcome<number | string> }
-| { type: "lid"; data: UsyncOutcome<Jid | null> }
-| { type: "username"; data: UsyncOutcome<string | null> }
-| { type: "bot"; data: UsyncOutcome<UsyncBotProfileResult> }
-| { type: "feature"; data: UsyncOutcome<UsyncFeatureResult[]> };
-
-/** Result-level state for a single protocol. */
-export interface UsyncProtocolState {
-    protocol: UsyncProtocolKind;
-    refresh_seconds?: number | null;
-    error?: UsyncSubprotocolError | null;
-}
-
-/** A complete typed USync query, validated before it reaches the network.  Deserialization always delegates to [`Self::new`], so a serialized input cannot bypass protocol uniqueness or per-user validation. */
-export interface UsyncQuery {
-    mode: UsyncMode;
-    context: UsyncContext;
-    protocols: UsyncProtocol[];
-    users: UsyncUser[];
-}
-
-/** Full neutral response from a typed USync query.  Its serialization walks this model by reference; no projection tree is constructed by the core. */
-export interface UsyncResponse {
-    protocol_states: UsyncProtocolState[];
-    users: UsyncUserResult[];
-}
-
-/** About/status payload. WhatsApp Web consumes only `status`, while the optional wire timestamp is retained for callers that need a lossless projection of responses carrying `t`. */
-export interface UsyncStatusResult {
-    status?: string | null;
-    timestamp?: number | string | null;
-}
-
-export interface UsyncSubprotocolError {
-    code?: number | null;
-    text?: string | null;
-    backoff?: number | null;
-}
-
-export interface UsyncTextStatusResult {
-    text?: string | null;
-    emoji?: string | null;
-    ephemeral_duration_seconds?: number | null;
-    last_update_time?: string | null;
-}
-
-/** A USync user input.  Constructors establish an identity and protocol-specific additions use explicit builder methods. Deserialization applies the same phone and JID normalization as those constructors; all invariants are validated when the user becomes part of [`UsyncQuery::new`]. */
-export interface UsyncUser {
-    id?: Jid | null;
-    pn_jid?: Jid | null;
-    phone?: string | null;
-    known_lid?: Jid | null;
-    device_sync?: UsyncDeviceSyncHint | null;
-    persona_id?: string | null;
-    username?: string | null;
-    username_pin?: string | null;
-    contact_type?: string | null;
-    tc_token?: Uint8Array | null;
-}
-
-/** Per-user response. `id` is optional because contact-only results without a JID are accepted by WhatsApp Web. */
-export interface UsyncUserResult {
-    id?: Jid | null;
-    pn_jid?: Jid | null;
-    protocols: UsyncProtocolResult[];
-}
-
-/** Verified name certificate information. */
-export interface VerifiedName {
-    name?: string | null;
-    serial?: string | null;
-    issuer?: string | null;
-    certificate?: Uint8Array | null;
-}
-
-/** In-call `<video state=N>` handshake states (audio→video upgrade, video→audio downgrade). Values verified against WA Web captures relayed by the mock server; unknown future states land in `Unknown` so a new server value degrades to an observable no-op instead of a parse failure. Wire codes: 0=Disabled, 1=Enabled, 2=Paused, 3=UpgradeRequest, 4=UpgradeAccept, 5=UpgradeReject, 6=Stopped, 7=UpgradeRejectByTimeout, 8=UpgradeCancel, 9=UpgradeCancelByTimeout, 10=UnknownPeer, 11=UpgradeRequestV2, 20=Error */
-export type VideoState = number;
-
-/** Authoritative waiting-room state for a call-link call. */
-export interface WaitingRoom {
-    call_id: string;
-    call_creator: Jid;
-    link_token: string;
-    media: CallLinkMedia;
-    enabled: boolean;
-    is_admin: boolean;
-    transaction_id?: number | null;
-    users: WaitingRoomUser[];
-}
-
-/** One user in a waiting-room snapshot. */
-export interface WaitingRoomUser {
-    jid: Jid;
-    pn?: Jid | null;
-    state: string;
-}
-
 
 
 export function getWasmAllocationSnapshot(): WasmAllocationSnapshot;
@@ -3768,9 +2368,9 @@ export interface InitOutput {
     readonly intounderlyingsource_cancel: (a: number) => void;
     readonly intounderlyingsource_pull: (a: number, b: number) => number;
     readonly __wasm_bindgen_func_elem_3793: (a: number, b: number, c: number) => void;
+    readonly __wasm_bindgen_func_elem_24617: (a: number, b: number, c: number, d: number) => void;
     readonly __wasm_bindgen_func_elem_24619: (a: number, b: number, c: number, d: number) => void;
-    readonly __wasm_bindgen_func_elem_24621: (a: number, b: number, c: number, d: number) => void;
-    readonly __wasm_bindgen_func_elem_8208: (a: number, b: number, c: number) => void;
+    readonly __wasm_bindgen_func_elem_8209: (a: number, b: number, c: number) => void;
     readonly __wasm_bindgen_func_elem_3792: (a: number, b: number, c: number) => void;
     readonly __wasm_bindgen_func_elem_3791: (a: number, b: number) => void;
     readonly __wbindgen_export: (a: number, b: number) => number;