* 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
* support bot light: check config and database with --dry-run
* ci: test the light support bot
---------
Co-authored-by: sh-agents <350651734+sh-agents@users.noreply.github.com>
* bots, nodejs: document chat, connection, member contact and network commands, typed commands in library
* bots, nodejs: restore apiConnect, wrap domain once, test all connect responses
* nodejs: JSDoc for new methods
* docs: plan for bot API commands and typed Node library methods
* tests: channel prepared with a domain has a verified SimpleX name
* docs: apply review fixes to the plan for bot API commands
* docs: apply second review pass to the plan for bot API commands
* docs: refer the bot API plan to the rewritten test commit
* docs: record decisions in the plan for bot API commands
* docs: plan tests of the generated Python command strings
* python: test the generated strings of the documented commands
* docs: plan for files, /leave and library methods in the MCP server
* docs: wait at stop in the MCP plan
* docs: library methods and /leave mechanics in the MCP plan
* mcp: typed library methods for chat commands
* docs: plan the message information command for bots
* mcp: /leave CHAT owner command to leave a chat at once
* docs: file servers, GIF and video choices decided in the MCP plan
* docs: file mechanics in the MCP plan
* mcp: files of received messages
* bots, nodejs: message information with the file servers for bots
* docs: plan the relay approval option of receiving files in Node
* mcp: download of received files with owner approval
* docs: name the xftp-server test helper in the files plan
* nodejs: receive files without approving unknown relays
* docs: plan the user servers command for bots
* bots, nodejs: user servers and relays by operator for bots
* nodejs: document the message information method
* docs: plan the file upload progress event for bots
* mcp: send files with owner approval, refusing private keys
* bots: file upload progress event for bots
* mcp: /leave template in the agent control chat menu
* docs: sent copies are deleted for contacts too, at sndFileCompleteXFTP
* bots: drop the file upload progress event
* docs: drop the upload progress event plan
* nodejs: document user servers and relay approval of received files
* mcp: download cards name unknown file servers after the upload
* docs: record the wait for the file description in the files plan
* mcp: fixed wait at stop for cancelled cards, without /sql
* docs: record decision C4, a fixed wait at stop, in the files plan
* ci: test the MCP server package on pull requests
* ci: state when the MCP workflow can be dispatched
* ci: run the MCP server tests when its libraries change
* mcp: log the errors of image previews and resizing
* mcp: keep files in transfer in the data folder
* mcp: restrict sent files by the real paths of refused folders
* mcp: validate the file at the send by its inode and change time
* mcp: limit ffmpeg and ffprobe to local files and no input commands
* mcp: ask the owner for unknown file servers; read approvals at creation
* mcp: name downloaded files by their ID; return paths of downloads only
* mcp: end each download with a result for the agent and the card
* mcp: show files above their sender's size limit as failed
* mcp: refuse empty files, as without file and captions too long to send
* mcp: tell the owner about failed uploads and unposted received files
* mcp: delete resized copies left by the last run at start
* mcp: name downloads and leaving in the help and greeting, align docs
* mcp: compute the download path for received files only
* mcp: send a /receive file to the owner under its name
* mcp: keep files received without a download in the chat's folder
* mcp: keep a left chat's files and delete them with /delete CHAT files
* mcp: test that sent images are resized by the core
* mcp: wait 30 minutes for a download's progress before cancelling it
* mcp: end a download as deleted only when its message is not found
* mcp: delete the copy of a /receive file whose post fails
* mcp: count the quoted content in a message's length, as the core sends it
* mcp: name received bytes, unknown-server downloads and left chat files plainly
* mcp: test refused folders, file changes and download approvals
* docs: align MCP server docs with refused folders, leaves and download waits
* mcp: move received files only in full, delete partials only of downloads
* mcp: report a received file missing from its folder as failed
* mcp: move received files of a group's member chats into its folder
* mcp: read a video's preview and duration as an MP4 or QuickTime file
* mcp: 0.2.0 on simplex-chat 7.1.0-beta.10.1
* mcp: file folders by chat type, /delete cancels downloads, files reply
* docs: MCP server specs and plan for 0.2.0
* mcp: /receive gives the agent a file, /forward sends it to the owner
* docs: MCP server specs for /receive and /forward of download cards
* docs: MCP plan records the temp folder command as a library exception
* mcp: /delete cancels resumed downloads; /forward quote fits the limit
* docs: MCP specs and plans for /forward quotes and resumed downloads
* docs: MCP specs name the source commit they are checked against
* docs: MCP PLAN states the /forward quote and move rules
* mcp: a download moves its completed file whatever its size
* mcp: /receive N all covers its card and later files, not pending ones
* docs: MCP files approval scope, reply text and README server wording
* mcp: a download approves relays only for a card naming unknown servers
* mcp: files in member chats of a group are tracked as in the main chat
* docs: MCP relay approval of downloads and files in member chats
* mcp: a rejected file gets a card again under the files approval
* docs: MCP rejected files under the files approval, README scope
* mcp: an offered file without a description gets no card or action
* docs: MCP a file without a description is not downloaded
* mcp: 0.2.0 on simplex-chat 7.1.0-beta.10.2
* ci: test the MCP server as a scope of build-linux
* ci: reduced build of changed scopes on drafts and manual runs
* ci: tests only when selected in reduced builds
* ci: test selection and retries in scripts/ci/run-tests.sh