PR #34948: fix(web): release responding lock on annotation-reply message_end

• Repository: langgenius/dify
• Author: HamzaSwitch
• State: open | merged: False
• Link: https://github.com/langgenius/dify/pull/34948

Description (problem / solution / changelog)

Fixes #34885. Same root cause as the prematurely-closed #33103.

When a Chatflow message matches an annotation reply, the backend fires a single message_end event with metadata.annotation_reply and closes the stream without going through the normal terminal event that triggers onCompleted. So handleResponding(false), which normally runs inside onCompleted, never fires, and the chat UI stays stuck in "generating" until the SSE connection physically closes.

The file already has a working version of this path. The regenerate-flow onMessageEnd handler around line 881 correctly does handleResponding(false); return in its annotation branch. The initial-send handler around line 359 just wasn't doing the same thing. I restructured it to match: check for annotation_reply at the callback level, apply the annotation via updateChatTreeNode, release the responding lock, return. Non-annotation branch is untouched.

686 tests in app/components/base/chat/chat/ pass, lint and types clean. I don't have an annotation configured on a live Dify to reproduce visually, but since I'm mirroring a sibling function in the same file I'm pretty confident in the shape of the fix.

Changed files

• web/app/components/base/chat/chat/hooks.ts (modified, +16/-6)