149e94b34b
The DingTalk card dropped the answer's opening (and any image reference in it) whenever the agent narrated its steps before answering: the text-only boundary heuristic (reasoningmode.BodyStartOffset) treats everything before the first structural line as narration, so a lead-in like "我已经找到了…" plus the image that follows it disappeared, leaving the card to start at the first heading. The event stream already knows the boundary: every agent step publishes its answer chunks under its own answer run id (data.event_id), and the final body is the last run that no tool/thinking event interrupts. WeKnora StreamEvent now carries the run id and run start offset; qa.Service tracks the observation and prefers it over the heuristic, falling back to the heuristic when the stream carries no run information. Verified: production turn efae317e (给我CRA5的负载图) lost 131 chars — lead-in + the load-curve image + separator — and now keeps them.