docs(qa): describe whatsapp qa lane coverage

mcaxtr · mcaxtr · commit 5f54b8b8a074 · 2026-06-30T23:13:20.000-03:00
diff --git a/docs/channels/broadcast-groups.md b/docs/channels/broadcast-groups.md
@@ -20,6 +20,8 @@ Current scope: **WhatsApp only** (web channel).
 
 Broadcast groups are evaluated after channel allowlists and group activation rules. In WhatsApp groups, this means broadcasts happen when OpenClaw would normally reply (for example: on mention, depending on your group settings).
 
+The live WhatsApp QA lane includes `whatsapp-broadcast-group-fanout`, which verifies that one mentioned group message can produce distinct visible replies from two configured agents.
+
 ## Use cases
 
 <AccordionGroup>
diff --git a/docs/concepts/qa-e2e-automation.md b/docs/concepts/qa-e2e-automation.md
@@ -735,52 +735,89 @@ Required env when `--credential-source env`:
 Optional:
 
 - `OPENCLAW_QA_WHATSAPP_GROUP_JID` enables group scenarios such as
-  `whatsapp-mention-gating` and `whatsapp-group-allowlist-block`.
+  `whatsapp-mention-gating`, `whatsapp-group-pending-history-context`,
+  `whatsapp-broadcast-group-fanout`, `whatsapp-group-activation-always`,
+  `whatsapp-group-reply-to-bot-triggers`, group action/media/poll scenarios, and
+  `whatsapp-group-allowlist-block`.
 - `OPENCLAW_QA_WHATSAPP_CAPTURE_CONTENT=1` keeps message bodies in
   observed-message artifacts.
 
 Scenario catalog (`extensions/qa-lab/src/live-transports/whatsapp/whatsapp-live.runtime.ts`):
 
 - Baseline and group gating: `whatsapp-canary`, `whatsapp-pairing-block`,
-  `whatsapp-mention-gating`, `whatsapp-top-level-reply-shape`,
-  `whatsapp-restart-resume`, `whatsapp-group-allowlist-block`.
+  `whatsapp-mention-gating`, `whatsapp-group-pending-history-context`,
+  `whatsapp-group-activation-always`,
+  `whatsapp-group-reply-to-bot-triggers`,
+  `whatsapp-top-level-reply-shape`, `whatsapp-restart-resume`,
+  `whatsapp-group-allowlist-block`.
 - Native commands: `whatsapp-help-command`, `whatsapp-status-command`,
   `whatsapp-commands-command`, `whatsapp-tools-compact-command`,
   `whatsapp-whoami-command`, `whatsapp-context-command`,
   `whatsapp-native-new-command`.
 - Reply and final-output behavior: `whatsapp-tool-only-usage-footer`,
   `whatsapp-reply-to-message`, `whatsapp-group-reply-to-message`,
-  `whatsapp-reply-context-isolation`, `whatsapp-reply-delivery-shape`,
-  `whatsapp-stream-final-message-accounting`.
+  `whatsapp-reply-to-mode-batched`, `whatsapp-reply-context-isolation`,
+  `whatsapp-reply-delivery-shape`, `whatsapp-stream-final-message-accounting`.
+- User-path message actions: `whatsapp-agent-message-action-react` starts from
+  a real driver DM, lets the model call the `message` tool, and observes the
+  native WhatsApp reaction. `whatsapp-agent-message-action-upload-file` uses
+  the same posture for `message(action=upload-file)` and observes native
+  WhatsApp media. `whatsapp-group-agent-message-action-react` and
+  `whatsapp-group-agent-message-action-upload-file` prove the same user-visible
+  actions in a real WhatsApp group.
+- Group fanout: `whatsapp-broadcast-group-fanout` starts from one mentioned
+  WhatsApp group message and verifies distinct visible replies from `main` and
+  `qa-second`.
+- Group activation: `whatsapp-group-activation-always` changes a real group
+  session to `/activation always`, proves an unmentioned group message wakes
+  the agent, then restores `/activation mention`. `whatsapp-group-reply-to-bot-triggers`
+  seeds a bot reply, sends a native quoted reply to it without an explicit
+  mention, and verifies the agent wakes from that reply context.
 - Inbound media and structured messages: `whatsapp-inbound-image-caption`,
   `whatsapp-audio-preflight`, `whatsapp-inbound-structured-messages`,
-  `whatsapp-group-audio-gating`. These send real WhatsApp image, audio,
-  document, location, contact, and sticker events through the driver.
-- Outbound Gateway and message action coverage:
+  `whatsapp-group-audio-gating`, `whatsapp-inbound-reaction-no-trigger`.
+  These send real WhatsApp image, audio, document, location, contact, sticker,
+  and reaction events through the driver.
+- Direct Gateway contract probes:
   `whatsapp-outbound-media-matrix`,
   `whatsapp-outbound-document-preserves-filename`, `whatsapp-outbound-poll`,
-  `whatsapp-message-actions`.
+  `whatsapp-group-outbound-media`, `whatsapp-group-outbound-poll`,
+  `whatsapp-message-actions`, `whatsapp-reply-context-isolation`,
+  `whatsapp-reply-delivery-shape`. These bypass model prompting on purpose and
+  prove deterministic Gateway/channel `send`, `poll`, and `message.action`
+  contracts.
 - Access-control coverage: `whatsapp-access-control-dm-open`,
   `whatsapp-access-control-dm-disabled`, `whatsapp-access-control-group-open`,
   `whatsapp-access-control-group-disabled`, `whatsapp-group-allowlist-block`.
 - Native approvals: `whatsapp-approval-exec-deny-native`,
   `whatsapp-approval-exec-native`, `whatsapp-approval-exec-reaction-native`,
+  `whatsapp-approval-exec-group-reaction-native`,
   `whatsapp-approval-plugin-native`.
-- Status reactions: `whatsapp-status-reactions`.
+- Status reactions: `whatsapp-status-reactions`,
+  `whatsapp-status-reaction-lifecycle`.
 
-The catalog currently contains 36 scenarios. The `live-frontier` default lane is
+The catalog currently contains 50 scenarios. The `live-frontier` default lane is
 kept small at 10 scenarios for fast smoke coverage. The `mock-openai` default
-lane runs 31 deterministic scenarios through the real WhatsApp transport while
+lane runs 44 deterministic scenarios through the real WhatsApp transport while
 mocking only model output. Approval scenarios and a few heavier/blocking checks
 remain explicit by scenario id.
 
 The WhatsApp QA driver observes structured live events (`text`, `media`,
 `location`, `reaction`, and `poll`) and can actively send media, polls,
 contacts, locations, and stickers. QA Lab imports that driver through the
 `@openclaw/whatsapp/api.js` package surface instead of reaching into private
-WhatsApp runtime files. Message content is redacted by default. Outbound
-poll and upload-file coverage run through deterministic gateway `poll` and
-`message.action` calls instead of model-prompt-only tool invocation.
+WhatsApp runtime files. For group observations, `fromJid` is the group JID while
+`participantJid` and `fromPhoneE164` identify the participant sender. Message
+content is redacted by default. Direct Gateway
+poll, upload-file, media, group poll, group media, and reply-shape probes are transport/API contract
+checks; they are not treated as proof that a user prompt made the agent choose
+the same action. User-path action proof comes from scenarios such as
+`whatsapp-agent-message-action-react` and
+`whatsapp-group-agent-message-action-react`, where the driver sends a normal
+WhatsApp message and QA Lab observes the resulting native WhatsApp artifact.
+WhatsApp reports include each scenario's posture (`user-path`, `direct-gateway`,
+or `native-approval`) so evidence cannot be mistaken for a stronger contract
+than it actually proves.
 
 Output artifacts:
 
