* core, ui: chatItemUpdated event has the previous item
Apps change counters by the difference between the previous and the new item, and insert an updated item only when the update created it.
* core, ui: a recreated item is sent as newChatItems
An update of a locally deleted message creates it again and sends it as a new item, so chatItemUpdated always has the previous item and the apps never insert on an update.
* core, ui: previous item is optional and has no chat info
Events from older remote hosts decode without it; the apps then insert the item if it is not loaded and change no counters.
* core: catch-up subscriber gets an edited history post as a new item
* ui: updates in another profile do not notify, as on iOS
* core, ui: one type for the updated item and its previous version
AChatItemUpdate has the chat info, the new item and the previous item with the same chat type and direction. Its JSON is the JSON of AChatItem with an optional prevChatItem; the event keeps the key chatItem.
* core: tested event key, previous item reactions, cleared mentions
One function renames the event field to chatItem for JSON and docs, and the test checks the wire key and compatibility with AChatItem. The previous item of a direct edit has its reactions. An edit that removes all mentions sends the item without them.
* core: test that an edit removing mentions sends the item without them
* core: event JSON field mapping inline in the TH options, for the Windows build
* core: file chat item update checked in one store transaction
* core: test that a file reset by unknown relays sends its previous item
* core, ui: chatItemUpdated event key chatItemUpdate
* core, ui: chatItemUpdated always has the previous item
* ci: mcp scope tests the plugin with its published dependencies
* core: mention of the user follows edits of a group message
* core: previous item of a prohibited file is read before the prohibition
* android, desktop: missed call check inline, counter test with core pairs
* ios: spec link of the chatItemUpdated event
* core: mention edits in support chats update members requiring attention
* core: one rule for the mention of the user in received and edited items
* core: record item events of updates for app tests
* android, desktop: remove the missed call notification of updates, never shown
* android, desktop: test item updates on events recorded by the core
* ios: test item updates on events recorded by the core
* docs: plan of app tests of item updates, recording tests in the CI guide
* core: record the response to an update after its item status is final
* ios: notification manager replaceable in tests
* ios: test notifications of updates and the update response
* android, desktop: test the recorded update response
* docs: plan with iOS notifications and the update response
* core: recorded response to an update of a sent message
* plan: UI improvements to improve LLM usage via SimpleX
* core, ui: types for chat layout
* core, ui: settings for alternative terminal-like chat layout for managing LLMs or other service bots
* plan: message priority
* fixes
* query plan
* update plans
* remove silent messages plan
* rename migrations
* implement layout
* amend
* fix
* fix
* fix
* improve
* time on the right, sender name in blue
* no avatar in direct chats
* better previews
* update, fixes
* update
* time gap
* changes
* ui: terminal layout line heights, gaps and time placement
* ui: simplify terminal meta layout, correct its docs and tests
* ui: right-to-left emoji edge in terminal rows, time placement tests
* android, desktop: raise Kotlin compiler memory to 4 GB
* ui: terminal captions as follow-up text, classic event separators
* ui: terminal media edge and overlay time, plan decisions
* ui: simplify terminal row separation, correct doc line references
* ui: keep the media time inside terminal rows, restore caption conditions
* ui: terminal heading capitals at large font scales, idle live message time
* ui: rename the classic voice-with-text flag, correct the meta copy docs
* ui: smaller terminal layout diff, sender gap and meta names
* ui: terminal row as tall as the media time
* docs: remove the chat layout section from the bots readme
* docs: shorten the terminal layout section of the chat view
* core: address settings API as on master, /auto_accept reads the stored layout
* ui: smaller terminal headings
* ui: classic sender rows and avatar rule as on master
* ui: classic reply quote text colour as on master
* ios: keep the chat layout setting with other UI settings
* ui: go-to button at the end of terminal rows, no gutter in direct chats
* ui: forwarded arrow on the header line of terminal rows, above the time
* ui: forwarded arrow centred above the time line of terminal rows
---------
Co-authored-by: Evgeny Poberezkin <evgeny@poberezkin.com>
The desktop app polled full clipboard contents every second on the AWT
event thread to update ChatModel.clipboardHasText. On X11, each read
blocks up to sun.awt.datatransfer.timeout (10s) when the selection owner
does not respond (e.g. after KeePassXC's clipboard auto-clear), making
every click/scroll wait ~9s. clipboardHasText has had no readers since
its only consumer was removed in #4398, so the whole mechanism (desktop
poll, Android clip listener, onResume refresh, expect/actual, state
field) is deleted. See plans/2026-07-11-fix-desktop-clipboard-freeze.md.