@vanzxy/baileys 1.6.6 → 1.6.8

package/README.md

@@ -1,10 +1,12 @@
 <div align="center" id="top">
 
-# 🍃 @vanzxy/baileys
+<img src="https://capsule-render.vercel.app/api?type=waving&color=0:1d6a23,100:2ecc71&height=180&section=header&text=%40vanzxy%2Fbaileys&fontSize=42&fontColor=ffffff&animation=fadeIn&fontAlignY=38&desc=Next-generation%20Baileys%20fork%20—%20built%20different,%20built%20by%20Vanzxy&descAlignY=58&descSize=16" width="100%"/>
 
-### *"Next-generation Baileys fork — built different, built by Vanzxy."*
+<img src="https://files.catbox.moe/l72xji.svg" width="100%" alt="Sakura night banner"/>
 
-Extended interactive messages • native flow enhancements • status tools • quality-of-life fixes — built on top of WhiskeySockets/Baileys.
+<p>
+  <img src="https://readme-typing-svg.demolab.com?font=Fira+Code&size=18&pause=1200&color=2ECC71&center=true&vCenter=true&width=650&lines=Extended+interactive+messages+%26+native+flow;Status+tools+%2B+quality-of-life+fixes;Built+on+top+of+WhiskeySockets%2FBaileys" alt="Typing SVG" />
+</p>
 
 <p>
 <a href="https://www.npmjs.com/package/@vanzxy/baileys" target="_blank"><img src="https://img.shields.io/npm/v/@vanzxy/baileys?color=2ecc71&label=npm&style=for-the-badge" alt="npm version"/></a>
@@ -18,26 +20,63 @@ Extended interactive messages • native flow enhancements • status tools •
 <img src="https://img.shields.io/github/languages/code-size/vanzxysenpai/vanzxybaileys?color=e67e22&style=flat-square" alt="Code size"/>
 <img src="https://img.shields.io/badge/node-%3E%3D20-brightgreen?style=flat-square" alt="Node >=20"/>
 <img src="https://img.shields.io/badge/module-ESM-blue?style=flat-square" alt="ESM"/>
+<img src="https://img.shields.io/badge/types-included-blue?style=flat-square" alt="TypeScript types included"/>
 <img src="https://img.shields.io/badge/license-see%20NOTICE-lightgrey?style=flat-square" alt="License"/>
 </p>
 
 <p>
 <a href="#-why-vanzxybaileys">About</a> &#xa0;|&#xa0;
-<a href="#-built-with">Tech Stack</a> &#xa0;|&#xa0;
+<a href="#-comparison">Comparison</a> &#xa0;|&#xa0;
 <a href="#-features">Features</a> &#xa0;|&#xa0;
-<a href="#-exclusive-vanzxy-enhancements">Enhancements</a> &#xa0;|&#xa0;
 <a href="#-installation">Installation</a> &#xa0;|&#xa0;
+<a href="#-quick-start">Quick Start</a> &#xa0;|&#xa0;
 <a href="#-usage-examples">Examples</a> &#xa0;|&#xa0;
-<a href="#-fork-lineage">Fork Lineage</a> &#xa0;|&#xa0;
+<a href="#-faq--troubleshooting">FAQ</a> &#xa0;|&#xa0;
+<a href="#-contributing">Contributing</a> &#xa0;|&#xa0;
 <a href="#-credits">Credits</a> &#xa0;|&#xa0;
 <a href="#-maintainer">Maintainer</a>
 </p>
 
+<details>
+<summary>📖 Full table of contents</summary>
+<br/>
+
+- [🍃 Why @vanzxy/baileys](#-why-vanzxybaileys)
+- [🆚 Comparison](#-comparison)
+- [🧰 Built With](#-built-with)
+- [🔥 Features](#-features)
+- [✨ Exclusive Vanzxy Enhancements](#-exclusive-vanzxy-enhancements)
+- [📦 Installation](#-installation)
+- [🚀 Quick Start](#-quick-start)
+- [🔐 Authentication](#-authentication)
+- [🗄️ Store Backends](#-store-backends)
+- [💡 Usage Examples](#-usage-examples)
+  - [Buttons & Native Flow](#buttons--native-flow)
+  - [Poll](#poll)
+  - [Carousel](#carousel)
+  - [AIRich — rich response cards](#airich--rich-response-cards)
+- [📞 Voice & Video Calls](#-voice--video-calls)
+- [🔎 User Sync Queries](#-user-sync-queries)
+- [🧩 Utility Modules](#-utility-modules)
+- [🛎️ System Notification Filter](#-system-notification-filter)
+- [🛠 Recommended Environment](#-recommended-environment)
+- [📘 TypeScript Support](#-typescript-support)
+- [📚 Fork Lineage](#-fork-lineage)
+- [❓ FAQ & Troubleshooting](#-faq--troubleshooting)
+- [🤝 Contributing](#-contributing)
+- [🙏 Credits](#-credits)
+- [💖 Support](#-support)
+- [👑 Maintainer](#-maintainer)
+- [⚠️ Disclaimer](#-disclaimer)
+- [📝 Patch Notes](#-v4-patch-notes)
+
+</details>
+
 </div>
 
 ---
 
-## ✨ Why @vanzxy/baileys?
+## 🍃 Why @vanzxy/baileys?
 
 This fork focuses on:
 
@@ -49,6 +88,27 @@ This fork focuses on:
 | 🧩 | More interactive message types |
 | ⚡ | Cleaner implementation for bot developers |
 | 🔧 | Extra utilities not available in standard Baileys forks |
+| 🗄️ | Multiple auth & store backends out of the box (file, SQLite, MongoDB, MySQL, PostgreSQL, Redis) |
+| 📞 | Experimental voice-call (VoIP) support |
+
+---
+
+## 🆚 Comparison
+
+How `@vanzxy/baileys` stacks up against its own lineage and the wider Baileys fork ecosystem:
+
+| Capability | `@vanzxy/baileys` | `@itsliaaa/baileys` | `WhiskeySockets/Baileys` |
+|---|:---:|:---:|:---:|
+| Native Flow buttons (V1/V2/V3) | ✅ | ✅ | ⚠️ basic only |
+| Carousel messages | ✅ | ❌ | ❌ |
+| Rich response cards (AIRich) | ✅ | ❌ | ❌ |
+| Commerce flow (catalog/order/payment) | ✅ | ⚠️ partial | ❌ |
+| Voice calling (VoIP) | ✅ experimental | ❌ | ❌ |
+| Multi-backend store (SQL/Mongo/Redis) | ✅ | ⚠️ file/SQLite only | ⚠️ in-memory only |
+| Full `.d.ts` TypeScript definitions | ✅ | ⚠️ partial | ⚠️ partial |
+| User sync queries (WAUSync) | ✅ | ✅ | ✅ |
+
+> Tabel ini menggambarkan fitur di level package, bukan benchmark performa. PR untuk memperbarui/mengoreksi tabel ini dipersilakan lewat [Contributing](#-contributing).
 
 ---
 
@@ -78,10 +138,11 @@ This fork focuses on:
 <td valign="top">
 
 - Native Flow
-- Buttons
+- Buttons (V1 / V2 / V3)
 - Lists
 - Carousel Messages
-- Rich Response Messages
+- Poll & Quiz Messages
+- Rich Response Messages (AIRich)
 - CTA / Reply / URL Buttons
 - Call Buttons
 - OTP Buttons
@@ -116,13 +177,55 @@ This fork focuses on:
 </tr>
 </table>
 
+<table>
+<tr>
+<th align="center">🔐 Auth & Storage</th>
+<th align="center">📞 Realtime</th>
+<th align="center">🛠 Developer Tooling</th>
+</tr>
+<tr>
+<td valign="top">
+
+- Multi-file auth state
+- Single-file auth state
+- SQLite auth state
+- Cache-manager auth state
+- In-memory store
+- SQLite / MongoDB / MySQL /
+  PostgreSQL / Redis store adapters
+
+</td>
+<td valign="top">
+
+- Voice calling (VoIP, WASM engine)
+- User sync queries (WAUSync)
+- Presence / status / device lookup
+- Event buffer for high-volume bots
+
+</td>
+<td valign="top">
+
+- Full TypeScript definitions (`.d.ts`)
+- Anti-delete detection
+- Message search helpers
+- Auto-reply engine
+- Scheduling helpers
+- Message retry manager
+
+</td>
+</tr>
+</table>
+
 ---
 
-## 🌟 Exclusive Vanzxy Enhancements
+## ✨ Exclusive Vanzxy Enhancements
 
 ### Audio Group Status Fix
 Audio status uses a more compatible implementation to avoid unsupported-version errors on older WhatsApp clients.
 
+### AIRich — the rich-response message builder
+A chainable builder (`AIRich`, also exported as `AIVanzxy` / `LeafRich` / `VanzxyAI` / `VanzxyRich`) with 40+ `add*()`/`set*()` methods covering headings, formatted text (hyperlinks/citations/LaTeX), code blocks, tables, image/video/product/post cards, task & progress cards, tip banners, and quick-reply suggestions — the kind of rich card layout you'd normally only see from an official AI/assistant-style bot. See [Usage Examples](#airich--rich-response-cards) below.
+
 ### Native Flow Expansion
 
 <table>
@@ -198,28 +301,125 @@ Directly from GitHub:
 npm install github:vanzxysenpai/vanzxybaileys
 ```
 
+> Requires **Node.js 20+** — install will refuse to run below that (checked by `engine-requirements.js` on `preinstall`).
+
+### Optional peer dependencies
+
+Everything below is **optional** — the socket works without any of them. Install only what the features you use need; missing ones fail with a clear install hint instead of a silent crash.
+
+| Package | Unlocks |
+|---|---|
+| `sharp` | Fast image resizing/processing (used by the message builders' `Toolkit.resize`) |
+| `@napi-rs/image` | Lighter native alternative to `sharp` for image ops |
+| `jimp` | Pure-JS image fallback when neither of the above is installed |
+| `fluent-ffmpeg` | Audio/video conversion for media messages |
+| `audio-decode` | Audio waveform/duration extraction (voice notes, VoIP capture) |
+| `link-preview-js` | Rich link previews for URLs in outgoing text messages |
+| `better-sqlite3` | SQLite auth state **and** SQLite store adapter |
+| `mongodb` | MongoDB store adapter |
+| `mysql2` | MySQL store adapter |
+| `pg` | PostgreSQL store adapter |
+| `ioredis` | Redis store adapter |
+| `@roamhq/wrtc` | Native WebRTC bindings for [voice calling](#-voice--video-calls) |
+
 ---
 
 ## 🚀 Quick Start
 
 ```js
-import { makeWASocket } from '@vanzxy/baileys'
+import { makeWASocket, useMultiFileAuthState } from '@vanzxy/baileys'
+
+const { state, saveCreds } = await useMultiFileAuthState('auth_info')
 
 const sock = makeWASocket({
-    printQRInTerminal: true
+    auth: state
 })
 
+// persist credentials whenever Baileys updates them
+sock.ev.on('creds.update', saveCreds)
+
 sock.ev.on('connection.update', (update) => {
-    const { connection } = update
+    const { connection, qr } = update
+
+    // `printQRInTerminal` is deprecated upstream — render the QR yourself,
+    // e.g. with the `qrcode-terminal` package:
+    //   import qrcode from 'qrcode-terminal'
+    //   if (qr) qrcode.generate(qr, { small: true })
+    if (qr) console.log('Scan this QR:', qr)
+
     if (connection === 'open') console.log('🍃 Connected!')
 })
+
+sock.ev.on('messages.upsert', ({ messages }) => {
+    const msg = messages[0]
+    if (!msg.message || msg.key.fromMe) return
+    console.log('New message from', msg.key.remoteJid)
+})
+```
+
+---
+
+## 🔐 Authentication
+
+Four auth-state backends ship out of the box. All return the same `{ state, saveCreds }` shape expected by `makeWASocket({ auth })`, so they're drop-in interchangeable.
+
+| Function | Storage | Best for |
+|---|---|---|
+| `useMultiFileAuthState(folder)` | One JSON file per key, on disk | Default choice — simple, debuggable, works everywhere |
+| `useSingleFileAuthState(fileName)` | One JSON file, on disk | Small bots where a single file is easier to manage/back up |
+| `useSqliteAuthState(opts)` | SQLite (`better-sqlite3`) | Bots that already use SQLite, or want auth in one embedded DB file |
+| `useCacheManagerAuthState(store, sessionKey)` | Any [`cacheable`](https://www.npmjs.com/package/@cacheable/node-cache)-compatible store | Multi-session hosting panels, Redis-backed setups |
+
+```js
+import { makeWASocket, useMultiFileAuthState } from '@vanzxy/baileys'
+
+const { state, saveCreds } = await useMultiFileAuthState('auth_info')
+const sock = makeWASocket({ auth: state })
+sock.ev.on('creds.update', saveCreds)
+```
+
+```js
+// SQLite variant
+import { makeWASocket, useSqliteAuthState } from '@vanzxy/baileys'
+
+const { state, saveCreds } = await useSqliteAuthState({ database: './auth.db' })
+const sock = makeWASocket({ auth: state })
+sock.ev.on('creds.update', saveCreds)
+```
+
+`useMultiFileAuthState` also exports `pruneStaleAuthFiles(folder, options)` to clean up old sender-key files on a schedule — useful for long-running bots that accumulate thousands of stale key files.
+
+---
+
+## 🗄️ Store Backends
+
+`makeInMemoryStore()` from `lib/Store` gives you the classic in-memory chat/contact/message cache. For anything that needs to survive a restart, `makePersistentStore()` (from `PersistentStore.js`) wraps one of five backends behind the same interface:
+
+| Backend | Function |
+|---|---|
+| SQLite | `createSqliteStoreAdapter(opts)` |
+| MongoDB | `createMongoStoreAdapter(opts)` |
+| MySQL | `createMysqlStoreAdapter(opts)` |
+| PostgreSQL | `createPostgresStoreAdapter(opts)` |
+| Redis | `createRedisStoreAdapter(opts)` |
+
+```js
+import { makeWASocket, makeInMemoryStore } from '@vanzxy/baileys'
+
+const store = makeInMemoryStore({})
+store.readFromFile('./baileys_store.json')
+setInterval(() => store.writeToFile('./baileys_store.json'), 10_000)
+
+const sock = makeWASocket({ /* ...auth etc */ })
+store.bind(sock.ev)
 ```
 
 ---
 
 ## 💡 Usage Examples
 
-### Buttons
+### Buttons & Native Flow
+
 ```js
 import { Button } from '@vanzxy/baileys'
 
@@ -229,44 +429,153 @@ await new Button(sock)
     .setFooter('@vanzxy/baileys')
     .addReply('Klaim Sekarang', 'claim_promo')
     .addUrl('Lihat Katalog', 'https://example.com/catalog')
+    .addCall('Hubungi Kami', '628123456789')
     .send(jid)
 ```
 
-### AIRich (rich response cards)
+### Poll
+
+```js
+import { Poll } from '@vanzxy/baileys'
+
+await new Poll(sock)
+    .setName('Mau makan apa hari ini?')
+    .addOptions(['Nasi Goreng', 'Mie Ayam', 'Bakso'])
+    .setSelectable(1)
+    .send(jid)
+```
+
+### Carousel
+
+> Each card must be built with `Button(...).toCard()` first — a carousel card is really just a button card with an image/video header.
+
+```js
+import { Button, Carousel } from '@vanzxy/baileys'
+
+const cardA = await new Button(sock)
+    .setImage('https://example.com/a.jpg')
+    .setTitle('Produk A')
+    .addUrl('Lihat', 'https://example.com/a')
+    .toCard()
+
+const cardB = await new Button(sock)
+    .setImage('https://example.com/b.jpg')
+    .setTitle('Produk B')
+    .addUrl('Lihat', 'https://example.com/b')
+    .toCard()
+
+await new Carousel(sock)
+    .setBody('Pilih salah satu produk di bawah ini')
+    .addCard([cardA, cardB])
+    .send(jid)
+```
+
+### AIRich — rich response cards
+
 ```js
 import { AIRich } from '@vanzxy/baileys'
 
 await new AIRich(sock)
     .addHeading('Ringkasan Order')
     .addText('Pesananmu sedang diproses.')
-    .addTable(['Item', 'Qty'], [['Kopi Susu', '2']])
+    .addTable([
+        ['Item', 'Qty'],
+        ['Kopi Susu', '2']
+    ])
+    .addTip('Pesanan biasanya siap dalam 15 menit')
     .addSuggest('Lacak Order')
     .send(jid)
 ```
 
-### Carousel
+`AIRich` supports `{ id, insertAt }` on every `add*()`/`set*()` call, so you can insert a block relative to one you added earlier instead of always appending to the end — handy for streaming/edit-in-place style responses combined with `sendEdit(jid, id)`.
+
+Other builders worth knowing about: **`ButtonV2`** (simpler quick-reply-only buttons), **`ButtonV3`** (`loadFrom(msg)` to edit an existing template message in place), and **`Toolkit`** (static helpers: `Toolkit.resize()`, `Toolkit.fetchBuffer()`, `Toolkit.waitAllPromises()`, `Toolkit.extractIE()` for parsing `[label](url)` links/citations/LaTeX out of plain text).
+
+---
+
+## 📞 Voice & Video Calls
+
+Experimental audio-call support (ported from ourin-baileys) via a WASM call stack + WebRTC relay. Requires the optional `@roamhq/wrtc` peer dependency.
+
 ```js
-import { Carousel } from '@vanzxy/baileys'
+import { VoipClient } from '@vanzxy/baileys'
 
-const carousel = new Carousel()
-    .addCard({ title: 'Produk A', image: 'https://example.com/a.jpg' })
-    .addCard({ title: 'Produk B', image: 'https://example.com/b.jpg' })
+const voip = new VoipClient({ resourcesPath: './voip-resources' })
+await voip.connectWithSocket(sock)
 
-await sock.relayMessage(jid, carousel.build(), {})
+const call = await voip.call('628123456789')
+
+call.on('ringing', () => console.log('Ringing...'))
+call.on('connected', () => console.log('Call connected'))
+call.on('ended', (reason) => console.log('Call ended:', reason))
 ```
 
+`ActiveCall` (returned by `.call()`) and `CallState` are also exported directly if you need finer-grained control over call state.
+
+---
+
+## 🔎 User Sync Queries
+
+`WAUSync` (`USyncQuery` / `USyncUser` + protocols) lets you check things like WhatsApp registration, device lists, status, and username info for a JID before you message it — the same mechanism behind `sock.onWhatsApp()`.
+
+```js
+import { USyncQuery, USyncUser, USyncContactProtocol } from '@vanzxy/baileys'
+
+const query = new USyncQuery()
+    .withContext('interactive')
+    .withMode('query')
+    .withUser(new USyncUser().withPhone('628123456789'))
+
+query.protocols.push(new USyncContactProtocol())
+
+const result = await sock.executeUSyncQuery(query)
+```
+
+Available protocols: `USyncContactProtocol`, `USyncDeviceProtocol`, `USyncStatusProtocol`, `USyncUsernameProtocol`, `USyncDisappearingModeProtocol`, `UsyncBotProfileProtocol`, `UsyncLIDProtocol`.
+
+---
+
+## 🧩 Utility Modules
+
+A sample of the utilities exported from `lib/Utils` beyond the message builders above:
+
+| Module | What it does |
+|---|---|
+| `anti-delete` | Detect and recover messages the sender deleted for everyone |
+| `auto-reply` | Simple keyword/pattern-based auto-responder engine |
+| `message-search` | Search cached/stored messages, peeling off ephemeral/view-once wrappers first |
+| `message-retry-manager` | Handles WhatsApp's retry-receipt protocol for undecryptable messages |
+| `scheduling` | Schedule messages/actions for later delivery |
+| `business` | Business-profile & catalog helpers |
+| `chat-control` | Pin, mute, archive, and mark-read/unread helpers |
+| `chat-history-helpers` | Work with synced chat history payloads |
+| `link-preview` | Generate link preview metadata for outgoing messages |
+| `stickerpack` | Build and send sticker packs (including animated/Lottie) |
+| `templates` | Legacy WhatsApp Business template message helpers |
+| `vcard` | Build vCard (contact card) payloads |
+| `status` | Post and manage WhatsApp Status updates |
+| `event-buffer` | Buffers/coalesces high-volume socket events for heavier bots |
+
+Every module above ships a matching `.d.ts`, so your editor will show full hover-docs regardless of which ones you import.
+
 ---
 
 ## 🛠 Recommended Environment
 
 | Requirement | Version |
 |---|---|
-| Node.js | 18+ |
+| Node.js | 20+ |
 | Module system | ESM |
 | WhatsApp | Latest Multi Device |
 
 ---
 
+## 📘 TypeScript Support
+
+Every file in `lib/` ships a matching `.d.ts`, including the message builders (`MessageBuilder_d.ts`) and all `Types/*` definitions (Auth, Chat, Contact, Events, GroupMetadata, Message, Product, Signal, USync, and more). No `@types/` package needed — plain `import { ... } from '@vanzxy/baileys'` gets full autocomplete in TS or JS-with-checkJS projects.
+
+---
+
 ## 📚 Fork Lineage
 
 ```
@@ -279,38 +588,74 @@ Respect to all original maintainers and contributors.
 
 ---
 
-## 🙏 Credits
+## ❓ FAQ & Troubleshooting
 
-- **Nixel** (with contributions from **Ahmad tumbuh kembang**) — base implementation of the `MessageBuilder` (AIRich / Button / Carousel / Toolkit), originally "NIXCODE — Advanced WhatsApp Interactive Message Builder"
-- **vinikjkkj** ([zapo](https://github.com/vinikjkkj/zapo)) — button/list addon-kind resolution logic
-- **QueenAnya** (`@queenanya/baileys`) — interactive/native-flow button send layer
-- **WhiskeySockets/Baileys** & **@itsliaaa/baileys** — upstream base
+<details>
+<summary><b>Koneksi terus putus / reconnect loop</b></summary>
+<br/>
 
-Full details and license terms per component: see [`NOTICE.md`](./NOTICE.md).
+Cek `connection.update` untuk field `lastDisconnect.error`. Kalau status code-nya `401` (loggedOut), sesi memang sudah invalid dan perlu scan ulang QR — jangan auto-reconnect di kondisi ini. Untuk status lain (`428`, `440`, dsb.), reconnect dengan backoff biasanya cukup.
 
----
+</details>
 
-## 📈 Repo Activity
+<details>
+<summary><b>QR tidak muncul / tidak ke-scan</b></summary>
+<br/>
 
-<div align="center">
+`printQRInTerminal` sudah deprecated di upstream Baileys — pastikan kamu render QR sendiri dari event `qr` (lihat contoh di [Quick Start](#-quick-start)). Kalau QR muncul tapi gagal linking, biasanya karena versi WA Web (`version` di `makeWASocket`) sudah kedaluwarsa; fetch versi terbaru lewat `fetchLatestBaileysVersion()`.
 
-![Vanzxy's GitHub stats](https://github-readme-stats.vercel.app/api?username=vanzxysenpai&show_icons=true&theme=radical&hide_border=true)
+</details>
 
-</div>
+<details>
+<summary><b>Error "Bad MAC" / pesan gagal didekripsi</b></summary>
+<br/>
+
+Umumnya terjadi kalau folder auth state korup atau sesi dipakai di lebih dari satu proses secara bersamaan. Pastikan hanya satu instance yang menulis ke folder auth state yang sama, dan pertimbangkan `pruneStaleAuthFiles()` untuk membersihkan sender-key lama secara berkala.
 
-> Powered by [github-readme-stats](https://github.com/anuraghazra/github-readme-stats) — updates automatically, no setup needed on this repo.
+</details>
 
 <details>
-<summary>🎮 Want a 3D contribution graph on your own profile?</summary>
+<summary><b>Memory terus naik di bot yang jalan lama</b></summary>
+<br/>
+
+Kalau pakai `makeInMemoryStore()`, cache chat/message/contact akan terus tumbuh tanpa batas. Untuk bot yang jalan lama, pertimbangkan pindah ke salah satu backend `makePersistentStore()` (SQLite/Redis/dst) dan pakai `event-buffer` untuk meredam lonjakan event di trafik tinggi.
+
+</details>
 
+<details>
+<summary><b>Voice call gagal connect</b></summary>
 <br/>
 
-That's a separate, opt-in GitHub Action for your **profile** repo (`username/username`), not something this package ships — see [github-profile-3d-contrib](https://github.com/yoshi389111/github-profile-3d-contrib) if you want to set it up for yourself.
+Fitur ini masih experimental dan butuh peer dependency `@roamhq/wrtc` — pastikan sudah terinstall dan platform kamu didukung native binding-nya. Cek event `call.on('ended', reason => ...)` untuk detail penyebab gagalnya.
 
 </details>
 
 ---
 
+## 🤝 Contributing
+
+Kontribusi dipersilakan, terutama untuk perbaikan bug, dokumentasi, dan enhancement pada `MessageBuilder` / `AIRich`.
+
+1. Fork repo ini, buat branch dari `main` (`feat/nama-fitur` atau `fix/nama-bug`)
+2. Pastikan perubahan tetap ESM-only dan menyertakan/menyesuaikan `.d.ts` terkait
+3. Uji perubahan pada minimal satu jalur auth state + satu store backend sebelum PR
+4. Buka Pull Request dengan deskripsi singkat: apa yang berubah dan kenapa
+
+Untuk laporan bug, sertakan versi Node.js, cara reproduksi, dan potongan log `lastDisconnect.error` bila relevan.
+
+---
+
+## 🙏 Credits
+
+- **Nixel** (with contributions from **Ahmad tumbuh kembang**) — base implementation of the `MessageBuilder` (AIRich / Button / Carousel / Toolkit), originally "NIXCODE — Advanced WhatsApp Interactive Message Builder"
+- **vinikjkkj** ([zapo](https://github.com/vinikjkkj/zapo)) — button/list addon-kind resolution logic
+- **QueenAnya** (`@queenanya/baileys`) — interactive/native-flow button send layer
+- **WhiskeySockets/Baileys** & **@itsliaaa/baileys** — upstream base
+
+Full details and license terms per component: see [`NOTICE.md`](./NOTICE.md).
+
+---
+
 ## 👑 Maintainer
 
 **Vanzxy**
@@ -334,12 +679,14 @@ Use responsibly and follow WhatsApp Terms of Service.
 - Existing guarded fallbacks for platforms where the native bridge cannot load remain in place.
 - ESM-only package metadata is preserved; no CommonJS build is included.
 
-Reference audit: the supplied Ourin, Elaina, ItsLiaaa, and Noxleyss packages were compared before this patch. Their broader core changes were not copied wholesale because the current Vanzxy tree already contains additional LID, retry, media, interactive, and AIRich fixes that would risk regressions if replaced.
+Reference audit: the supplied Ourin, Elaina, ItsLiaaa, and Noxleyss packages were compared before this patch. Their broader core changes were not copied wholesale because the current Vanzxy tree already contains additional LID, retry, media, interactive, angd AIRich fixes that would risk regressions if replaced.
 
 ---
 
 <div align="center">
 
+<img src="https://capsule-render.vercel.app/api?type=waving&color=0:2ecc71,100:1d6a23&height=100&section=footer" width="100%"/>
+
 Made with 🍃 by **Vanzxy**
 
 Thanks for stopping by! ✌️

package/WAProto/index.js

@@ -3,7 +3,7 @@ import $protobuf from "protobufjs/minimal.js";
 
 const $Reader = $protobuf.Reader, $Writer = $protobuf.Writer, $util = $protobuf.util;
 
-const $root = $protobuf.roots["default"] || ($protobuf.roots["default"] = {});
+const $root = $protobuf.roots["vanzxy_baileys_wa_proto"] || ($protobuf.roots["vanzxy_baileys_wa_proto"] = {});
 
 function longToString(value, unsigned) {
 	if (typeof value === "string") {

package/lib/Utils/MessageBuilder.js

@@ -2977,6 +2977,14 @@ class AIRich extends BaseBuilder {
 	addWidget(data = {}, { layout } = {}) {
 		const items = Array.isArray(data) ? data : [data];
 
+		// Vanz@Fix (bug 44) --- layout: 'Single' forces `widgets[0]` below (a "Single" layout's
+		// view_model can only ever hold one `primitive`, never a `primitives` array — see
+		// newLayout()). Previously an explicit { layout: 'Single' } combined with a multi-item
+		// array silently dropped every item past the first with no error. Fail loud instead.
+		if (layout === 'Single' && items.length > 1) {
+			throw new TypeError(`addWidget(): layout "Single" can only hold one widget (got ${items.length}) — use "HScroll"/"ActionRow" (or omit layout) for multiple`);
+		}
+
 		items.forEach((item, i) => {
 			// header.title or top-level title required
 			const hasTitle = item?.title || item?.header?.title;
@@ -2994,6 +3002,13 @@ class AIRich extends BaseBuilder {
 			messageText: items.map((item) => item.header?.title ?? item.title).join(', '),
 		});
 
+		// Vanz@Fix (bug 45) --- auto tool_call_id used to be `idx` scoped per-item (ctas.map's own
+		// index), resetting to 0 for every widget item. Two items (or two separate addWidget()
+		// calls) that both omit tool_call_id/id ended up minting the identical auto id ("00"),
+		// so a CTA tap could route to the wrong widget's tool call. Track the counter on the
+		// instance instead so every auto-generated id is unique for this AIRich's lifetime.
+		this._widgetCtaCounter ??= 0;
+
 		const widgets = items.map((item) => {
 			const ctas = item.ctas ?? item.actions;
 			// header accepts either a string title (legacy) or an object { title, subtitle }
@@ -3007,11 +3022,11 @@ class AIRich extends BaseBuilder {
 				},
 				body: {
 					sections: item.sections ?? [],
-					ctas: ctas.map((cta, idx) => ({
+					ctas: ctas.map((cta) => ({
 						label: cta.label ?? '',
 						state: cta.state ?? 'PENDING',
 						kind: cta.kind ?? 'OTHER',
-						tool_call_id: cta.tool_call_id ?? cta.id ?? String(idx).padStart(2, '0'),
+						tool_call_id: cta.tool_call_id ?? cta.id ?? String(this._widgetCtaCounter++).padStart(2, '0'),
 						...(cta.toast !== false && {
 							toast: { label: typeof cta.toast === 'string' ? cta.toast : headerTitle, __typename: 'GenAI3PExtWidgetToast' },
 						}),

package/lib/Utils/anti-delete.js

@@ -80,12 +80,20 @@ export class MessageStore {
         stored.isDeleted = true;
         stored.deletedAt = now;
         stored.deletedBy = deletedBy;
+        // Vanz@Fix (bug 66): the old check (`deletedBy === stored.message.key.participant`)
+        // only works in groups, where `participant` identifies who sent/revoked a message.
+        // In a private chat `key.participant` is always undefined (it's a group-only field),
+        // while `deletedBy` there falls back to `remoteJid` — so the comparison could never
+        // match and isRevokedBySender was always false for every DM, even though
+        // delete-for-everyone in a DM can only be done by the original sender. Treat a
+        // missing `participant` (i.e. not a group message) as "revoked by sender" by definition.
+        const isGroupMessage = !!stored.message.key.participant;
         const info = {
             originalMessage: stored.message,
             key,
             deletedAt: now,
             deletedBy,
-            isRevokedBySender: !deletedBy || deletedBy === stored.message.key.participant
+            isRevokedBySender: !deletedBy || !isGroupMessage || deletedBy === stored.message.key.participant
         };
         this.deletedMessages.set(this.getKey(key), info);
         return info;

package/lib/Utils/generics.js

@@ -71,7 +71,25 @@ export const encodeBigEndian = (e, t = 4) => {
 };
 export const toNumber = (t) => typeof t === 'object' && t ? ('toNumber' in t ? t.toNumber() : t.low) : t || 0;
 /** unix timestamp of a date in seconds */
-export const unixTimestampSeconds = (date = new Date()) => date.getTime() / 1000 | 0;
+// Vanz@Fix (bug 69): unixTimestampSeconds(date) assumed `date` is always a real Date
+// instance and called date.getTime() unconditionally. Any caller that passed a raw
+// number (Date.now(), or an already-converted unix timestamp) or an ISO string instead
+// of a Date crashed here with "date.getTime is not a function" — this is a coercion
+// bug in THIS function, not a proto/BloksWidget/InteractiveMessage issue (traced and
+// confirmed: normalizeMessageContent/getContentType never touch nested message content,
+// and this function is called before any encode/serialize step even starts). Coerce the
+// common input shapes instead of assuming Date, but keep throwing on genuinely invalid
+// input (NaN) so silent bad-timestamp bugs don't get hidden.
+export const unixTimestampSeconds = (date) => {
+    if (date == null) date = new Date(); // null AND undefined both mean "now" (default params only catch undefined)
+    const d = date instanceof Date
+        ? date
+        : new Date(typeof date === 'number' && date < 1e12 ? date * 1000 : date); // treat sub-1e12 numbers as already-seconds
+    if (Number.isNaN(d.getTime())) {
+        throw new TypeError(`unixTimestampSeconds: invalid timestamp input (${typeof date}): ${date}`);
+    }
+    return d.getTime() / 1000 | 0;
+};
 export const debouncedTimeout = (intervalMs = 1000, task) => {
     let timeout;
     return {

package/lib/Utils/media-set.js

@@ -145,7 +145,11 @@ export const groupLabel = async (jid, text, sock) => {
                 type: 30,
                 memberLabel: {
                     label: text.slice(0, 30),
-                    labelTimestamp: Date.now()
+                    // Vanz@Fix (bug 67): this used Date.now() (milliseconds) while the
+                    // sibling groupSetMemberLabel() correctly uses unixTimestampSeconds()
+                    // for the same proto field — WA's *Timestamp fields are unix-seconds,
+                    // so this was sending a timestamp ~1000x too large.
+                    labelTimestamp: unixTimestampSeconds() || Date.now()
                 }
             }
         }, {

package/lib/WABinary/generic-utils.js

@@ -160,7 +160,9 @@ const FLOWS_MAP = {
     // routed anything real; kept as a harmless alias in case any external caller
     // is still constructing a raw button object with the old (wrong) name.
     flow: true,
-    flow_action: true,
+    // Vanz@Fix (bug 68): removed duplicate `flow_action: true` key — already declared
+    // above (Vanzxy extended button types block); this was a leftover copy-paste dupe,
+    // harmless (same value) but confusing on re-read.
     // Vanz@Fix (single_select never renders alone) --- single_select must NEVER get
     // its own dedicated native_flow node here. WhatsApp only renders a single_select
     // button through the generic <native_flow v='9' name='mixed'> node — the same one

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vanzxy/baileys",
-  "version": "1.6.6",
+  "version": "1.6.8",
   "description": "Enhanced Baileys fork by Vanzxy \u2014 based on @itsliaaa/baileys + @whiskeysockets/baileys with fixes for audio group status and clean media without newsletter button.",
   "type": "module",
   "main": "./lib/index.js",
@@ -34,16 +34,39 @@
     "NOTICE.md"
   ],
   "keywords": [
-    "automation",
-    "baileys",
-    "bot",
-    "interactive-messages",
-    "js-whatsapp",
-    "multi-device",
-    "whatsapp",
-    "whatsapp-api",
-    "whatsapp-bot",
-    "whatsapp-web"
+  "vanzxy",
+  "vanzxybaileys",
+  "vanzxy-baileys",
+  "vanzxy-whatsapp",
+  "vanzxy-baileys-md",
+  "baileys-fork-vanzxy",
+  "baileys",
+  "baileys-md",
+  "baileys-multi-device",
+  "baileys-multidevice",
+  "baileys-whatsapp",
+  "baileys-whatsapp-api",
+  "baileys-whatsapp-bot",
+  "baileys-bot",
+  "baileys-api",
+  "baileys-library",
+  "baileys-node",
+  "baileys-nodejs",
+  "baileys-javascript",
+  "baileys-js",
+  "baileys-esm",
+  "baileys-fork",
+  "whatsapp-baileys",
+  "whatsapp-bot-baileys",
+  "whatsapp-api-baileys",
+  "whatsapp-web-baileys",
+  "whatsapp-multi-device",
+  "whatsapp-automation",
+  "whatsapp-bot",
+  "whatsapp-api",
+  "whatsapp-web",
+  "multi-device",
+  "interactive-messages"
   ],
   "homepage": "https://github.com/vanzxysenpai/vanzxybaileys#readme",
   "author": "Vanzxy",

package/WAProto/CHANGELOG-proto-upgrade.md

@@ -1,111 +0,0 @@
-# WAProto upgrade — progress checkpoint
-
-Base: @vanzxy/baileys 1.6.6 WAProto (already the most complete of the 4 sources compared:
-716 types vs wa-proto-main 603 / Baileys-5 570 / raphaelvserafim 569).
-Diffed field-by-field against wa-proto-main (WA 2.3000.1046350168, newest available) to find real gaps.
-
-## ✅ Applied in this checkpoint (session 1)
-- `AIRichResponseMessage.originalRecipientMetadata` (field 5, type `AIRichResponseUnifiedResponse`)
-  — direct "airich" gap, full encode/decode/verify/fromObject/toObject wired.
-- `BotMetadata.responseStoppedByUser` (field 44, bool) — full round-trip wired.
-
-## ✅ Applied in this checkpoint (session 2 — pending queue cleared)
-- `Message.VideoMessage.dashManifestUrl` (field 33, string) — full encode/decode/fromObject/toObject
-  wired alongside the existing `videoSourceType` enum field (30/31).
-- `ContextInfo.experienceIds` (field 82, repeated packed uint32) — wired using the same packed-varint
-  pattern as `ADVKeyIndexList.validIndexes` (fork/ldelim on encode, packed-or-single fallback on decode).
-- `DeviceCapabilities.BusinessBroadcast.proCompanionSupportEnabled` (field 6, bool) — full round-trip
-  wired next to the existing `recipientLimit` field.
-- `Message.newsletterScheduledMessage` (field 132, reuses existing `FutureProofMessage` type) — wired
-  next to `botPlatformRegistrationSuccessMessage` (field 131).
-- 3 new nested types under `SyncActionValue`, each a single-bool message built from scratch off the
-  `StarAction`/`CtwaMessageReceivedAction` template, then wired into the parent message at fields 94–96:
-  - `SharedDeviceAllowlistAction` (bool `allowed`) — field 94
-  - `ContactManagerMetadataAction` (bool `isHidden`) — field 95
-  - `BusinessFolderActivationAction` (bool `activated`) — field 96
-
-**Pending queue is now empty** — every gap identified in the wa-proto-main diff has been applied.
-
-## Already confirmed complete, no changes needed
-Buttons (ButtonsMessage, TemplateButton, HydratedTemplateButton, ButtonsResponseMessage),
-InteractiveMessage + NativeFlowMessage (incl. bloksWidget/A2UI), TemplateMessage,
-ExtendedContentMessage (CTA buttons, XMA), ListMessage, all AIRichResponse* submessage types,
-MessageContextInfo — all field-complete vs every reference source checked.
-
-## Validation
-- `node --check WAProto/index.js` — syntax clean after all edits.
-- Functional round-trip (encode → decode → toObject) verified for all 5 session-2 fields, plus
-  regression checks confirming neighboring pre-existing fields (`videoSourceType`, `aiProvenance`,
-  `posterStatusId`, `botPlatformRegistrationSuccessMessage`, `ctwaMessageReceivedAction`, and
-  `BusinessBroadcast`'s other bool fields) still encode/decode correctly after the inserts.
-  Run against a hand-written wire-format shim (varint/string/bool/length-delimited), not the real
-  `protobufjs` package, since this sandbox has no network/registry access to install it — the shim
-  implements the exact subset of the protobufjs runtime API (`Writer`/`Reader`/`util`) that the
-  generated code calls, so it validates wire-format correctness but not protobufjs's own internals.
-  **Recommend re-running a quick smoke test against the real `protobufjs` package once installed in
-  your environment before shipping to production**, though the generated code path itself is
-  mechanically identical to every other field in this file.
-
-index.js syntax-validated with `node --check` after this checkpoint's edits.
-
-## Session 3 — full Button/AIRich/A2UI field audit (no gaps found)
-Ran an exhaustive field-by-field diff of every Button-, AIRich-, and Interactive/NativeFlow (A2UI)
--related message against `wa-proto-main` (the newest reference in this bundle) and cross-checked
-against `Baileys-5`:
-
-- **Buttons**: `ButtonsMessage` (+ nested `Button`/`ButtonText`/`NativeFlowInfo`), `ButtonsResponseMessage`,
-  `TemplateButton`/`HydratedTemplateButton` (+ `QuickReplyButton`/`URLButton`/`CallButton` variants) —
-  field-complete, 1:1 match.
-- **AIRich**: all 12 top-level `AIRichResponse*` messages (`Message`, `SubMessage`, `CodeMetadata`,
-  `ContentItemsMetadata`, `DynamicMetadata`, `GridImageMetadata`, `ImageURL`, `InlineImageMetadata`,
-  `LatexMetadata`, `MapMetadata`, `TableMetadata`, `UnifiedResponse`) — field-complete, including the
-  `originalRecipientMetadata` field added in session 1.
-- **A2UI / Interactive**: `InteractiveMessage` (+ `BloksWidget`, `Header` incl. its own nested
-  `bloksWidget` field 10, `Footer`, `Body`, `CarouselMessage`, `CollectionMessage`, `NativeFlowMessage`
-  + `NativeFlowButton`, `ShopMessage`), `InteractiveResponseMessage` (+ `Body`, `NativeFlowResponseMessage`),
-  `InteractiveAnnotation` — field-complete.
-- `Baileys-5` (older/less complete source per this file's header) contributes nothing extra relevant —
-  its only two extra top-level messages (`LIDMigrationMapping`/`LIDMigrationMappingSyncPayload`) are the
-  deprecated pre-migration types already superseded and handled in session 26-08-26.
-
-**Conclusion: the WAProto layer for Button/AIRich/A2UI is fully caught up — no further proto-level
-patches identified.** Next stage for these features is JS-level (`lib/Utils/MessageBuilder.js`,
-`lib/Utils/A2UI.js`) — wiring the newly-added fields (`dashManifestUrl`, `experienceIds`,
-`newsletterScheduledMessage`, etc.) into builder APIs where relevant, not further WAProto edits.
-
-## Session 4 — JS-level integration check
-Checked whether `MessageBuilder.js`/`A2UI.js` need whitelist updates to expose the new proto fields:
-
-- `dashManifestUrl` (VideoMessage) and `experienceIds` (ContextInfo): no gap. `setContextInfo(obj)`
-  merges the object verbatim (no field whitelist), and video-message construction elsewhere
-  (`sendPairedMedia`) spreads a plain object straight into `relayMessage` — any proto-valid field,
-  including these two, is already usable with zero code changes.
-- `DeviceCapabilities.proCompanionSupportEnabled`: no gap, but not because it's already wired —
-  `DeviceCapabilities` isn't referenced anywhere in `lib/` (not part of this fork's companion
-  registration flow), so there's nothing to update.
-- **Real gap found**: `lib/Utils/messages.js`'s `getFutureProofMessage()` — the whitelist function
-  `normalizeMessageContent()` uses to unwrap `FutureProofMessage`-typed fields — was missing
-  `botPlatformRegistrationSuccessMessage` (field 131, pre-existing) and `newsletterScheduledMessage`
-  (field 132, added this session). Both would have silently failed to unwrap: a message using either
-  wrapper would pass through `normalizeMessageContent()` unchanged instead of resolving to its inner
-  `message`. **Fixed** — both added to the whitelist. Syntax-checked (`node --check`) and functionally
-  verified both fields now correctly unwrap.
-
-Bumped package version 1.6.6 → 1.6.7.
-
-## Session 5 — resolved the standing "verify against live traffic" TODO
-`lib/Utils/process-message.js`'s `decodeLidMigrationMappingSyncPayload()` (the hand-written decoder
-from session 26-08-26, flagged since then as needing live-traffic verification) has now been
-cross-checked against an independent source: `Baileys-5`'s bundled `WAProto.proto`, an older compiled
-schema dump from before Meta stopped publishing this type's inner structure. It's an exact
-field-for-field match:
-- `LIDMigrationMappingSyncPayload { repeated pnToLidMappings = 1; optional chatDbMigrationTimestamp = 2 (uint64); }`
-- `LIDMigrationMapping { pn = 1; assignedLid = 2; latestLid = 3; all uint64 }`
-
-This isn't literal live WhatsApp traffic, but it is a real independent extraction agreeing byte-for-byte
-with the from-scratch guess — meaningfully stronger evidence than "seems plausible," since an
-independent tool derived the same field layout separately. Also ran a functional round-trip test
-(hand-encoded a payload matching this exact structure, fed it through the actual decoder function) —
-PASS. Updated the code comment to reflect this and removed the "TODO: verify" marker; the residual risk
-(Meta silently changing the inner layout with zero signal) is unchanged and can only be closed by
-actual live traffic, but the decoder is no longer running on-guess. Bumped package version 1.6.7 → 1.6.8.