fix(streaming): Prioritize using task_name/task_id from events, fallb…

[howiefh]

Prioritize using task_name/task_id from events, fallback to current_task_info to ensure correct task_id and task_name are obtained in StreamChunk

---

Note

Ensures StreamChunk uses task identifiers from the incoming LLMStreamChunkEvent when available.

• In _create_stream_chunk, set task_name and task_id to event.task_name/event.task_id with fallback to current_task_info

^{Written by Cursor Bugbot for commit d4108a4. This will update automatically on new commits. Configure here.}

[cursor]

This PR is being reviewed by Cursor Bugbot

Details

Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

[cursor]

Inconsistent task_index when event has different task info

The task_index is always sourced from current_task_info, while task_name and task_id now preferentially come from the event. If an event's task_id/task_name differs from current_task_info, the resulting StreamChunk will have task_index pointing to a different task than task_id/task_name. Before this change, all three fields came from the same source and were guaranteed consistent. Consumers of StreamChunk may expect these fields to reference the same task.