fix: dispatch OnAfterMessageSentEvent after streaming delivery

[bingchengcc]

The streaming output path in RespondStage early-returns after send_streaming(), skipping the OnAfterMessageSentEvent dispatch that the non-streaming path performs.

This means plugins hooking after_message_sent (e.g. simple_memory _capture) never fire for streaming platforms such as webchat.

Change

Add the same OnAfterMessageSentEvent dispatch after send_streaming() completes, matching the non-streaming path:

             await event.send_streaming(result.async_stream, realtime_segmenting)
+            if await call_event_hook(event, EventType.OnAfterMessageSentEvent):
+                return
+            event.clear_result()
             return

Test plan

• Webchat: send a message, verify after_message_sent hook fires
• Non-streaming (QQ): verify behavior unchanged

Summary by Sourcery

Bug Fixes:

• Dispatch the after-message-sent event after streaming delivery so post-send hooks also run for streaming platforms.

Fixes #9740

[sourcery-ai]

Hey - I've left some high level feedback:

• To keep the streaming and non-streaming paths from diverging again, consider extracting the shared OnAfterMessageSentEvent + clear_result logic into a small helper so both branches call the same code.
• Double-check that calling event.clear_result() after send_streaming matches the non-streaming path ordering (i.e., hooks can still access any required response data before it is cleared); if not, you may want to clear earlier or pass required data into the hook explicitly.
• It may be worth wrapping send_streaming and the subsequent hook invocation in a try/finally to guarantee event.clear_result() is called even if streaming or hook execution raises, avoiding potential state leaks between requests.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- To keep the streaming and non-streaming paths from diverging again, consider extracting the shared `OnAfterMessageSentEvent` + `clear_result` logic into a small helper so both branches call the same code.
- Double-check that calling `event.clear_result()` after `send_streaming` matches the non-streaming path ordering (i.e., hooks can still access any required response data before it is cleared); if not, you may want to clear earlier or pass required data into the hook explicitly.
- It may be worth wrapping `send_streaming` and the subsequent hook invocation in a `try`/`finally` to guarantee `event.clear_result()` is called even if streaming or hook execution raises, avoiding potential state leaks between requests.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}