Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

docs(engine): count chats.delete among consumed Baileys events

Yudhi Armyndharis540a5615e9c8
diff --git a/docs/29-engine-capability-matrix.md b/docs/29-engine-capability-matrix.md
index 386ea4c05..17c74c53b 100644
--- a/docs/29-engine-capability-matrix.md
+++ b/docs/29-engine-capability-matrix.md
@@ -1010,7 +1010,7 @@ adapter sources — re-derive the same way when anything changes:
3 internal wiring, 1 class plumbing, **35 ❌ not exposed** (27 real capabilities + 8
session/transport settings that are not WhatsApp capabilities). The backlog is the ❌ rows minus
those 8 settings; 🔩 plumbing is correctly never exposed.
-- Events: Baileys **34** (16 consumed / 18 dropped), wwjs **31** (16 consumed / 15 dropped).
+- Events: Baileys **34** (17 consumed / 17 dropped), wwjs **31** (16 consumed / 15 dropped).
- **0** capabilities in 29.5.3: every capability with first-class symbols on both libraries is
either wired or classified with evidence. Some are Baileys-only despite typed whatsapp-web.js
symbols: `createGroup`, whose injected evaluate reaches a page internal without `findImpl`;