Free, Open Source, Self-Hosted WhatsApp API Gateway
TypeScript apibotgatewayself-hostedwhatsappwhatsapp-apiwhatsapp-automationwhatsapp-botwhatsapp-gatewaywhatsapp-gateway-apiwhatsapp-webwhatsapp-web-api
docs(engine): cite symbols instead of line numbers in docs/29
Yudhi Armyndharis629b95fb576f
diff --git a/docs/29-engine-capability-matrix.md b/docs/29-engine-capability-matrix.mdindex d685ef038..453f78220 100644--- a/docs/29-engine-capability-matrix.md+++ b/docs/29-engine-capability-matrix.md@@ -144,7 +144,7 @@ reaching READY is not evidence that every patch landed. See docs/12 for the oper| # | Patcher | Library target | What it repairs | Stand-down predicate || ---- | ---------------------------------------------------------- | ------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |-| 🔧¹ | `scripts/patch-wwebjs-201832.js` (+ `wwebjs-201832.patch`) | whatsapp-web.js models | WhatsApp Web 2.3000.x renamed the serialized message-id property `id._serialized` → `id.$1`; 1.34.7 reads the old name in the `Message` constructor and ~40 downstream sites, so message ids, acks, quoted-message resolution and media downloads break. Backports upstream fix #201832 (`Base._normalizeId()`). One known harmless reject on 1.34.7 (a LID-aware `Contact.js` path that does not exist there); any other reject aborts the build. | no-ops once `_normalizeId` exists upstream. Runtime double-check: `src/engine/adapters/wwebjs-backport-check.ts` detects an unpatched install and logs an error naming the fix as the wwjs session starts (`whatsapp-web-js.adapter.ts:446`). It is diagnostic, **not** preventive — startup continues, so a session reaching READY is not evidence the patch landed. |+| 🔧¹ | `scripts/patch-wwebjs-201832.js` (+ `wwebjs-201832.patch`) | whatsapp-web.js models | WhatsApp Web 2.3000.x renamed the serialized message-id property `id._serialized` → `id.$1`; 1.34.7 reads the old name in the `Message` constructor and ~40 downstream sites, so message ids, acks, quoted-message resolution and media downloads break. Backports upstream fix #201832 (`Base._normalizeId()`). One known harmless reject on 1.34.7 (a LID-aware `Contact.js` path that does not exist there); any other reject aborts the build. | no-ops once `_normalizeId` exists upstream. Runtime double-check: `src/engine/adapters/wwebjs-backport-check.ts` detects an unpatched install and logs an error naming the fix as the wwjs session starts, in `WwebjsLifecycle.initialize()`. It is diagnostic, **not** preventive — startup continues, so a session reaching READY is not evidence the patch landed. || 🔧² | `scripts/patch-wwebjs-status.js` | whatsapp-web.js injected status send | Two independent breakages in current WhatsApp Web builds: (1) the `canCheckStatusRankingPosterGating()` helper is gone and its call threw before any status send — now called when present, `false` (pre-gating meaning) when not; (2) `sendStatusMediaMsgAction` changed signature from positional `(msg, mediaUpdate)` to a single options object — adopted from upstream PR #201816. The two edits of the media repair are all-or-nothing. | exact-shape match; unknown shape fails the build. || 🔧³ | `scripts/patch-wwebjs-newsletter-preview.js` | whatsapp-web.js `Injected/Utils.js` | Link-preview generation omitted the destination chat, so WhatsApp Web could not select the newsletter preview transport: `getLinkPreview(link)` → `getLinkPreview(link, chat)`. | exact-shape match; unknown shape fails the build. || 🔧⁴ | `scripts/patch-wwebjs-ready-sync.js` | whatsapp-web.js readiness pipeline | Two live-observed races: on a warm profile the page can reach `hasSynced=true` before the edge listener attaches (the whole post-auth pipeline silently never runs), and a partial `attachEventListeners` failure was swallowed (message bridge dead while sends still work). Adds an `eventsAttached` completion marker and fires the handler once when the level is already true; double-fire is deduped by the adapter. | exact-shape, one group all-or-nothing; unknown shape fails the build. |@@ -909,15 +909,15 @@ adapter boundary — none silently stubs.- **Media sends to a channel JID (wwjs) answer 501.** `sendImageMessage`, `sendVideoMessage`,`sendAudioMessage`, `sendDocumentMessage` and `sendStickerMessage` are ✅ on wwjs for chats andgroups, but a `<id>@newsletter` recipient throws `ChannelMediaNotSupportedError` (a- `NotImplementedException` → HTTP 501) at `ensureNotChannelRecipient`- (`wwebjs-messaging.ts:446` for the media funnel, `:515` for stickers). whatsapp-web.js calls- `msg.avParams()`, removed in a recent WA Web build (upstream wwebjs#201823, unresolved).+ `NotImplementedException` → HTTP 501) at `ensureNotChannelRecipient` (`wwebjs-messaging.ts`, in+ `sendMediaMessage` for the media funnel and in `sendStickerMessage` for stickers). whatsapp-web.js+ calls `msg.avParams()`, removed in a recent WA Web build (upstream wwebjs#201823, unresolved).Unquoted text→channel is unaffected, and Baileys has no such restriction, so these five rows answer`501` without a per-row ❌ in 29.4. A few other sends answer `501` on wwjs by recipient, becausewhatsapp-web.js drops them without touching the page (`Client.js` `sendMessage` returns `null`): areply (any send carrying a quoted message), a location or a contact card to a channel,`status@broadcast` or a broadcast list, and a poll or a sticker to `status@broadcast` or a- broadcast list. `ensureSendable` (`wwebjs-messaging.ts:206`) refuses them before the library is+ broadcast list. `ensureSendable` (`wwebjs-messaging.ts`) refuses them before the library iscalled, so nothing is sent. The Baileys adapter refuses none of them.- **`sendStickerMessage` — what each engine converts.** Both engines guarantee the payload really isWebP, but they reach it differently and they do not accept the same inputs. whatsapp-web.js passes