[orbitingflea]

This pull request makes an agent message that a rewrite changed show the rewrite's time, not the time it was first sent.

改了什么行为

Behaviour change: yes, a user who reads a thread in a display mode sees an agent message that replace_send_to_user changed dated by the time that rewrite completed, in the message's time and in its hover tooltip (web and desktop). Before, the message kept the time of its first send, and only the "Edited" mark's tooltip had the edit time.

• The message stays where it was in the thread.
• Messages with no rewrite look as before.

Why

The display modes already store the rewrite time on the message as editedAt, for the "Edited" mark. The message's time line read only updatedAt, which stays at the first send. It now reads editedAt ?? updatedAt.

updatedAt itself stays at the first send. The turn fold reads it to work out an older turn's "Worked for" length. If it moved to the edit time, a turn that took 40 seconds would read as lasting until the later rewrite.

Checks

• A browser test renders a sent message, then its rewrite. It checks that the time and its tooltip show when the rewrite completed. It fails before the fix, where the message keeps the send time.
• The repo's checks for changed files pass.
• In the web app at desktop and phone width, a message rewritten three minutes after it was sent showed the rewrite time after a page load.

How to undo

Revert the two commits. No data or setting changes.

Design notes

• Upstream lines: TimelineAssistantRows.tsx +2 −2, the two timestamp lines of AssistantMessageMeta.
• Unchanged on purpose: queued-message edits (a queued message that starts is dated by its start, which comes after any edit), sub-thread reply lines (they already use the edit time), and the mobile app (it has no display modes).
• Known limit: in Chat + Replies, history from the server keeps only the newest rewrite of a message. After a reload, a rewrite back to the first text shows no edit, as the "Edited" mark already does.