ba35e251be
Streamed card content is replayed by the DingTalk client with a typewriter animation it drives itself, so an answer that is already complete on the server can still be typed out - and a client that leaves the foreground pauses that animation, which reads as 'streaming stopped, it continues when I switch back' long after the final frame was pushed. Add DINGTALK_CARD_FINAL_WRITE (streaming default | update): in update mode the streaming finalize is followed by one plain PUT /v1.0/card/instances write with the identical template variables, so the terminal content has no typewriter queue behind it. The follow-up write never fails a delivered answer.