| 1 | # WhatsApp Integration Plugin DOX |
| 2 | |
| 3 | ## Purpose |
| 4 | |
| 5 | - Own WhatsApp communication through a Baileys-based Node.js bridge. |
| 6 | |
| 7 | ## Ownership |
| 8 | |
| 9 | - `helpers/bridge_manager.py` owns bridge lifecycle. |
| 10 | - `helpers/handler.py` and `helpers/wa_client.py` own message routing and bridge API interaction. |
| 11 | - `helpers/storage_paths.py`, attachment helpers, and number utilities own storage, attachment, and phone-number handling. |
| 12 | - `whatsapp-bridge/` owns the Node.js bridge package. |
| 13 | - `api/`, `prompts/`, `extensions/`, `default_config.yaml`, `plugin.yaml`, `README.md`, and `webui/` own QR/start/disconnect/test endpoints, prompt fragments, hooks, settings, metadata, docs, and UI. |
| 14 | |
| 15 | ## Local Contracts |
| 16 | |
| 17 | - Treat WhatsApp sessions, QR data, phone numbers, attachments, and bridge state as sensitive. |
| 18 | - Keep allowed-number and group-response controls enforced. |
| 19 | - Do not leave unmanaged bridge services outside plugin-owned runtime paths. |
| 20 | |
| 21 | ## Work Guidance |
| 22 | |
| 23 | - Coordinate Node bridge changes with Python bridge client and settings UI. |
| 24 | |
| 25 | ## Verification |
| 26 | |
| 27 | - Smoke-test dependency install, bridge start, QR pairing, allowed-number filtering, message routing, and replies when practical. |
| 28 | |
| 29 | ## Child DOX Index |
| 30 | |
| 31 | No child DOX files. |