fix(qa): scope message-tool-cascade no-outbound check to post-cascade cursor

SunnyShu0925 · SunnyShu0925 · commit 0b340d42d443 · 2026-07-02T23:26:20.000+08:00
ClawSweeper P2: waitForNoOutbound was scanning from index 0, so it counted
the two already-observed cascade messages as violations and always failed.

Capture the outbound message count after the second cascade marker and pass
it as sinceIndex so the settle window only checks for messages that arrive
after both expected sends.
diff --git a/qa/scenarios/channels/message-tool-cascade-regression.yaml b/qa/scenarios/channels/message-tool-cascade-regression.yaml
@@ -82,10 +82,15 @@ flow:
                 params: [candidate]
                 expr: "candidate.conversation.id === config.conversationId && candidate.conversation.kind === 'group' && (candidate.text ?? '').includes(config.expectedMarker2)"
             - expr: liveTurnTimeoutMs(env, 180000)
+        - set: cascadeCursor
+          value:
+            expr: "state.getSnapshot().messages.filter((message) => message.direction === 'outbound').length"
         - call: waitForNoOutbound
           args:
             - ref: state
             - 15000
+            - sinceIndex:
+                ref: cascadeCursor
         - set: allOutbound
           value:
             expr: "state.getSnapshot().messages.filter((message) => message.direction === 'outbound' && message.conversation.id === config.conversationId && message.conversation.kind === 'group')"
