* 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
* core, ui: plan name alert tests against core fixtures
* core: write name lookup responses to app fixtures in name tests
* android, desktop: name alerts tested against core fixtures
* core, ios: plan Swift fixtures and iOS unit tests of name alerts
* core: write name lookup responses in the Swift form to iOS fixtures
* ios: name alerts tested against core fixtures
* core: write both app fixtures of a name test in one run
* ui: add name lookup responses written by the core tests as fixtures
* core: keep the fixture writer of name tests to the forms it receives
* desktop: run name alert tests in the US locale
* ios: one switch for the title and effect of name alert actions
* docs: name alert tests in the app specs, CI guide and plan
* docs: known gaps of the name alert tests in the plan
* ui: restore the name alert code and the iOS project of master
* core: record name lookup responses and name parses for app tests
* android, desktop: test name alerts of planAndConnect on recorded responses
* ci: run the app tests for a change of the name fixtures
* core: name lookup responses and name parses recorded by the core tests
* docs: plan of app views tested on core responses
* ios: test name alerts of planAndConnect on recorded responses
* ci: iOS unit tests in the iOS job, the app launched on stub migrations
* android, desktop: core hooks below the externals, in the specs
* ios: name alert tests compile with the converter at file scope
* ui: the moved name test expects the alert to open a chat with the new address
* core, ui: app test fixtures under tests/fixtures/api
* core: record the responses of the name lookup flows that the apps test
* core: record URI parses, and normalize the random values of fixtures
* android, desktop: URI parse hook and event processing for tests
* ios: URI parse hook for tests
* desktop: full failure messages of tests
* core: domain errors view compiles with GHC 8.10.7
* core: normalize parses and profile send times in fixtures
* core: record the parses of the chat list search
* core: recorded responses of the name flows and the contact address
* android, desktop: test name alerts, buttons, search and name view
* ios: test name alerts, buttons, search and the moved event
* docs: plan, specs and CI guide of the app tests
* core: record lapsed names without grace, channels lapsed, moved, failed
* android, desktop: test the prepare domain, cleanup, search row and reasons
* ios: test the prepare domain, onOpen and the event's terminal text
* core: the grace date of an expired name in tests is in seconds
* core: recorded plans of lapsed, moved and unverified names; relays normalized
* ios, android, desktop: test lapsed, moved and unverified channel names
* docs: the follow-up tests and the gaps they leave
* ios: wait for the alert of a failed prepare before the next test
* ios: show the alert of a failed new chat on the main thread
* core, ui: plan name alert tests against core fixtures
* core: write name lookup responses to app fixtures in name tests
* android, desktop: name alerts tested against core fixtures
* core, ios: plan Swift fixtures and iOS unit tests of name alerts
* core: write name lookup responses in the Swift form to iOS fixtures
* ios: name alerts tested against core fixtures
* core: write both app fixtures of a name test in one run
* ui: add name lookup responses written by the core tests as fixtures
* core: keep the fixture writer of name tests to the forms it receives
* desktop: run name alert tests in the US locale
* ios: one switch for the title and effect of name alert actions
* docs: name alert tests in the app specs, CI guide and plan
* docs: known gaps of the name alert tests in the plan
* ui: restore the name alert code and the iOS project of master
* core: record name lookup responses and name parses for app tests
* android, desktop: test name alerts of planAndConnect on recorded responses
* ci: run the app tests for a change of the name fixtures
* core: name lookup responses and name parses recorded by the core tests
* docs: plan of app views tested on core responses
* ios: test name alerts of planAndConnect on recorded responses
* ci: iOS unit tests in the iOS job, the app launched on stub migrations
* android, desktop: core hooks below the externals, in the specs
* ios: name alert tests compile with the converter at file scope
* ui: the moved name test expects the alert to open a chat with the new address
* core, ui: app test fixtures under tests/fixtures/api
* core: record the responses of the name lookup flows that the apps test
* core: record URI parses, and normalize the random values of fixtures
* android, desktop: URI parse hook and event processing for tests
* ios: URI parse hook for tests
* desktop: full failure messages of tests
* core: domain errors view compiles with GHC 8.10.7
* core: normalize parses and profile send times in fixtures
* core: record the parses of the chat list search
* core: recorded responses of the name flows and the contact address
* android, desktop: test name alerts, buttons, search and name view
* ios: test name alerts, buttons, search and the moved event
* docs: plan, specs and CI guide of the app tests
* ios: test call commands and chat suspension after call pushes
* ios: validate ICE candidate index in calls
* ios: handle call answers that reject media sections
* ios: suspend chat after expired calls and calls iOS does not show
* ios: begin chat suspension when an expired call is reported
* ios: remove VoIP push test
* ios: test each path of call commands and call pushes
* ios: test declined calls, candidates without index and old-version video
* ios: test old-version answers without a shared video track
* ios: test call answers on the offer the app sends, without candidates
* ios: test call commands without ICE servers and local audio
* ios: test call answers without connection events
* ios: suspend chat when answering a call fails
* ios: test answers that fail after call pushes
* ios: keep chat suspended after expired call pushes
* ios: suspend chat on the main thread after an answer times out
* ios: test that expired call pushes keep chat suspended
* website: two publications on the links page
* website: shorter link descriptions
* website: preview images for the two new links
* website: 30 more 2026 links, Freedom.Tech review address
* website: distinct title for the Flux entry, to keep the Whonix anchor
* mcp: free memory and disk in the status line
* mcp: free memory and disk in the end line of answers
* mcp: ❗️ after a low part of the end line, RAM below 5%
* plan: mcp-flat-sessions
* plan: mcp-flat-sessions, the user's answers
* plan: mcp-flat-sessions, image widths and times per platform
* plan: mcp-flat-sessions, one flat media width and smaller avatars
* plan: mcp-flat-sessions, list breaks
* plan: mcp-flat-sessions, visible avatar gaps and the gap below the sender row
* plan: mcp-flat-sessions, equal gaps around the name
* plan: mcp-flat-sessions, restore the approved gaps
* mcp: open the groups of new sessions in the Flat layout
* ui: avatar on the name line and full-width messages in the flat layout
* ui: record the snapshot references of the flat layout
* ui: flat media beside the go-to button, text below tall name lines
* mcp: source of the session image, Main group check in the e2e test
* plan: mcp-flat-sessions, as implemented
* plans: flat sessions, the tests run on master
* android, desktop: keep the width limit of the media box in intrinsic measurement
* android, desktop: test the intrinsic height of media at an unbounded width
* ui: flat name rows close to their messages, cards at the text edge
* desktop: flat group snapshot references, the media scene
* plans: flat sessions, avatars and flat-layout defects
* desktop: avatar snapshot scenes with photos and placeholders
* ios: flat snapshot references, the deleted items scene
* desktop: avatar snapshot scenes of share, contact and user lists, calls, channel members
* android, desktop: avatars without inner padding, each in its former box
* ios: snapshot scenes of hidden integrity errors in Flat rows and bubbles
* desktop: avatar snapshot references, recorded before the inset removal
* android, desktop: snapshot scenes of hidden integrity errors in Flat rows and bubbles
* ios: hidden integrity errors take no space in the chat
* plans: flat sessions, the user's answers, avatar call sites as implemented, hidden rows
* ios: scenes of the time before deleted items, unread users, appearance
* ios: avatars in Flat rows pass the letters' edge by 2 pt
* ios: 6 pt from the avatar to the message below it in Flat rows
* ios: time on the last line of messages ending with empty lines in Flat
* ios: code cards as wide as the code, the time beside them, in Flat rows
* ios: delivery status only with the time in Flat rows
* ios: time shown on a message before a deleted or hidden item
* ios: no gap below a reactions row between one sender's messages in Flat
* ios: no early wrap of the last word before the time in Flat rows
* ios: name the condition that shows the time before deleted items
* ios: spec links to the moved lines of TerminalItemView
* ios: test of the delivery status without the time in Flat rows
* desktop: snapshot references after the inset removal, hidden integrity error scenes
* android, desktop: blur of blocked members' photos as on iOS
* ios: user picker scene with the chat running, as in the app
* android, desktop: snapshot scenes of the Flat defects and the chat banner
* ios: status without the time only for partial delivery and errors
* ios: snapshot references of the Flat avatar overshoot, gap and defect fixes
* ios: snapshot references without the empty line after a hidden time
* android, desktop: hidden integrity errors take no space; the time before deleted and hidden items
* android, desktop: chat banner 20 dp above its avatar and 10 dp below
* android, desktop: Flat avatars 2 dp past the letters, 6 dp above the text, four layout defects
* android, desktop: share list shows each chat's own avatar
* android, desktop: business, bot and agent placeholders as on iOS
* plans: flat sessions, the decisions as implemented on Android and desktop
* ios: scene of a hidden item between two messages of one sender
* ios: sender name 12 pt after the visible avatar in Flat rows
* ios: rows around hidden items grouped as if the hidden items were absent
* ios: full time in a deleted message bubble
* android, desktop: rows skip hidden items as neighbours; the time before deleted items in Flat rows only
* android, desktop: Flat sender names 12 dp after the avatar
* android, desktop: avatar placeholders from their own assets; unused icons removed
* plans: flat sessions, questions numbered as answered, neighbours of hidden rows, overshoot note
* ios: snapshot references of rows around hidden items and the name start
* android, desktop: hidden rows keep one date separator; marked deleted errors shown; rows rebuilt on the developer setting
* desktop: snapshot references of the Flat decisions, defects, banner and rows around hidden items
* spec, plans: Flat row layout, hidden rows and their neighbours, status with the time; avatar assets as implemented
* android, desktop: new, unread and read statuses only with the time in Flat rows, as on iOS
* desktop: snapshot references of the Flat defects scene with an unread message; plans: partial delivery wording
* mcp: session image with the Flat row geometry: avatar 2 pt past the letters, text 6 pt below it
* mcp: session image with a shorter answer, so the first row shows in full
* ios: user picker snapshot scenes at the height of the sheet
* plans: flat sessions, an avatar column with tighter paddings
* ios: snapshot references of the user picker at the height of the sheet
* plans: flat sessions, the avatar column with only the gap open
* ui: Flat avatar column, the avatar 2 into the padding, text 10 after it
Names, items, later rows of one sender, events and deleted cards sit in the message column; media widths are measured from it. Chats without avatars keep 12 on both sides. The session scene on both platforms; the README image redrawn with the column.
* ui: snapshot references of the Flat avatar column and the session scene
* ui: Flat cards and pills take their corners from the roundness setting
Deleted, marked deleted, moderated, blocked, error and decryption error cards and group invitations: 18 × roundness without a tail, as media, on iOS and Android/desktop. A scene of each platform at roundness 0.3.
* ui: Flat pill text on the text start, sender rows at master's pitch
Deleted, marked deleted, moderated, blocked and error pills start at the message column, so their text lines up with the messages, as on master; in chats without avatars they keep 12 from the screen edge. The name line of a sender row starts at the row gap, as on master; the avatar is centred on it and reaches into the gap above, on both platforms.
* android, desktop: avatars in a box drawn at exactly 5/6 of it, as master's padded placeholders
centeredIn scales its child to 5/6 of the box and centres it with fractional placement, so placeholder edges match master at the pixel at every font scale. Photos and the incognito icon take the same size, up to 1 px larger than master's rounded photo padding. The chat-link thumbnail of the chat list uses the same box, 44 sp.
* android, desktop: avatars in a box at whole pixels, photos fill the drawn box
centeredIn places its child at box/12 rounded down and sizes it to the box less twice that, so placeholders keep master's first and last ink pixel and stay sharp. Photos take their rounded square from the drawn box in pixels.
* ui: photo corners from the nominal size; iOS references of pills, corners and sender rows
The rounded square of a photo keeps its corner radius from the size argument. iOS references for the pill alignment, the corner radius from the roundness setting with a 0.3 scene, and sender rows at master's pitch.
* android, desktop: snapshot references of pills, corners, sender rows and avatars at whole pixels
* ui: what's new in v7.1.4, security audit by Trail of Bits; blog placeholder
* ci: iOS and desktop references of v7.1.4 what's new
* blog: placeholder moved to its own PR
* ui: shorter v7.1.4 what's new texts
* ui: v7.1.4 audit item: ask contacts to upgrade, report soon
* android, desktop: crowdfunding image says you own your identity
* android, desktop: crowdfunding image sizes from the 1200x400 source
* ci: desktop references of v7.1.4 what's new with the new image and texts
* ui: crowdfunding caption as before, page headline Own a part of SimpleX Chat, report on its own line
* android, desktop: phone corner as in the original crowdfunding image
* blog: Trail of Bits security audit permalink
* blog: fixes in previous versions, no section placeholders
* blog: Anthropic OSS Scanner program
* blog: using frontier models
* blog: OSS Scanner program that uses frontier models
* blog: upgrade to v7.1.4+
* blog: fixes in SimpleX Chat apps
* blog: fixes in SimpleX Chat app
* blog: fixes first
* blog: security process line
* blog: OSS Scanner in the security process line only
* blog: links to Trail of Bits and OSS Scanner
* website: gold text holds its colour to the end
* website: gold text ends in the original colour
* website: stretch the gold gradient instead of extra stops
* store: names page pinned to a commit outside its branch
* store: master merge restored the removed badge poller
* store: lazy stateTVar left in the store service by the merge
* store: names group tests used query helpers master replaced
---------
Co-authored-by: sh-agents <350651734+sh-agents@users.noreply.github.com>
* mcp: step lines end with their duration in small print, without the check mark
* mcp: the whole step line in small print
* mcp: a ! in a step line shows as ǃ, so the whole line stays in small print
* plan: mcp-activity
* plan: mcp-activity list format
* plan: mcp-activity answers and live step lines
* mcp: a silent line per step of Claude's work, completed at its end
* plan: mcp-activity as implemented
* mcp: finalize step lines within a day and load only the hook's modules
* plan: mcp-activity review decisions as implemented
* plan: mcp-session-usage
* plan: mcp-live-answers
* plan: mcp-live-answers answers and the end line with the usage
* plan: mcp-session-usage, plan usage by the status line, one end line
* plan: mcp-session-usage, the end line settled with live-answers
* plan: mcp-live-answers end line with the plan usage, shared fast request
* plan: mcp-live-answers keeps tokens in context
* plan: mcp-session-usage, status line through postToService
* mcp: end live step lines by the wall clock
* mcp: exact spec ranges and measured hook load time
* mcp: Claude's answers live as Claude writes them, and one end line per turn
A prompt that starts a turn gets an empty silent live message, which the turn's first text, step or answer fills. The MessageDisplay hook, dist/display.js, passes each batch of Claude's text to the service, and the hub streams each text into a silent live message, updated at most every 3 s and finalized at its end. At Stop the streamed answer is claimed, or the answer is posted silent, and the end line !- ✅ Done in DURATION! follows as the turn's only alert.
* plan: mcp-live-answers as implemented
* mcp: usage of each turn in its end line, model and effort switch lines
* plan: mcp-session-usage as implemented
* mcp: one refusal post for a refused answer, in the turn's opening message
A text that a group preference refuses counts as the answer at Stop, so the answer is not posted again. A refused post that would fill the opening message fills it with its refusal text. A refused text ends at once, also when it outgrows a message, and an update scheduled before its end is skipped. Plan decision 37.
* mcp: live posts survive a lost opening message and end within a day
A failed update of the opening message drops it, and the post is sent as a new message; a text that was never posted no longer stands for the answer. Texts and opening messages end 23 hours after their send by the wall clock, as steps do. When the update with a refusal fails too, the opening message gets ⏹️ Stopped and the end line follows. The opening message is kept before User's post and sent after it.
* docs: the status line step of the plugin README
* mcp: a dropped opening message ends with ⏹️ Stopped
When the update of the opening message fails without a refusal, the hub finalizes it, so after a transient failure it does not stay live.
* mcp: effort level only from the status line once it reports
Hooks report the turn's level, xhigh after ultrathink, while the status line reports the session's level; docs: effort updated at each tool step, data folder writable only by the user.
* mcp: end line without the check mark, small print only
* mcp: one token format, the compaction line's, in the end line
* mcp: append the end line to the last message of the answer
* mcp: keep a finished text live until Stop adds the end line, docs
* mcp: priority 1 in the update that adds the end line, quotes of answers without it
* mcp: an answer without a turn record quotes no prompt pushed before the latest answer
* store: serve the pages as built, settings from /api/config
* store: badges page reads its Stripe key from the API
* store: badges worker waits for a slow page, not the old build
* store: badges page kept a stale Stripe key after the tab returned
* store: names page read settings the service no longer writes
* store: Caddy had no built sites to serve once the export was gone
* store: two page folders where one mount would do
* store: example Caddyfile missed the bare /api and /webhooks paths
* store: a hand-written page copy script where rsync does it
---------
Co-authored-by: sh-agents <350651734+sh-agents@users.noreply.github.com>
* core: lock delivery and relay request work items on PostgreSQL
* core: retry store transactions aborted by PostgreSQL deadlocks
* core: show skipped messages followed by agent messages
* core: read delivery and relay request work items in one snapshot
* core: use the conflict retry of the store transaction for work item reads
* core: show integrity errors of agent messages from MSG without body
* core: show integrity errors from MSGERR, log MSGERR without an error
* core: update simplexmq, set server forward workers in tests
* core: update simplexmq
* plan: mcp-activity
* plan: mcp-activity list format
* plan: mcp-activity answers and live step lines
* mcp: a silent line per step of Claude's work, completed at its end
* plan: mcp-activity as implemented
* mcp: finalize step lines within a day and load only the hook's modules
* plan: mcp-activity review decisions as implemented
* plan: mcp-live-answers
* plan: mcp-live-answers answers and the end line with the usage
* plan: mcp-live-answers end line with the plan usage, shared fast request
* plan: mcp-live-answers keeps tokens in context
* mcp: end live step lines by the wall clock
* mcp: exact spec ranges and measured hook load time
* mcp: Claude's answers live as Claude writes them, and one end line per turn
A prompt that starts a turn gets an empty silent live message, which the turn's first text, step or answer fills. The MessageDisplay hook, dist/display.js, passes each batch of Claude's text to the service, and the hub streams each text into a silent live message, updated at most every 3 s and finalized at its end. At Stop the streamed answer is claimed, or the answer is posted silent, and the end line !- ✅ Done in DURATION! follows as the turn's only alert.
* plan: mcp-live-answers as implemented
* mcp: one refusal post for a refused answer, in the turn's opening message
A text that a group preference refuses counts as the answer at Stop, so the answer is not posted again. A refused post that would fill the opening message fills it with its refusal text. A refused text ends at once, also when it outgrows a message, and an update scheduled before its end is skipped. Plan decision 37.
* mcp: live posts survive a lost opening message and end within a day
A failed update of the opening message drops it, and the post is sent as a new message; a text that was never posted no longer stands for the answer. Texts and opening messages end 23 hours after their send by the wall clock, as steps do. When the update with a refusal fails too, the opening message gets ⏹️ Stopped and the end line follows. The opening message is kept before User's post and sent after it.
* mcp: a dropped opening message ends with ⏹️ Stopped
When the update of the opening message fails without a refusal, the hub finalizes it, so after a transient failure it does not stay live.
* plan: mcp-agent-profile
* plan: mcp-agent-profile, answers Q1 (b) and Q2 (b)
* plan: mcp-agent-profile, lists render on GitHub
* mcp: User has the peer type of a person
* ui: show the peer type placeholder of members and contacts
* plan: mcp-agent-profile, answers to the user's notes
* ui: compare link icons with peerTypeIcon in the desktop test
* ui: snapshot references of the peer type placeholders
* android: peer type placeholder of a caller on the lock screen
* ios: agent icon of a link in the compose context at text size
* plan: mcp-agent-profile, review fixes
* ios: snapshot references with the compose context line of a link
* core: send a change of the peer type alone to groups
* mcp: User's peer type reaches existing session groups
* plan: mcp-agent-profile, Q1 (a)
* mcp: mark the agent profile item delivered in the roadmap
* store: Prometheus metrics of name orders and registrar funds
* store: keep the service running when the metrics port fails
* store: describe held balances and the funds read time exactly
* store: export badge, payment provider and chain node metrics
* store: rename a test binding that shadowed hspec's before
* store: count the names on chain in the metrics
* store: check the scraped samples one by one
* store: answer 0 for metrics labels with no rows
---------
Co-authored-by: sh-agents <350651734+sh-agents@users.noreply.github.com>
* plan: mcp-activity
* plan: mcp-activity list format
* plan: mcp-activity answers and live step lines
* mcp: a silent line per step of Claude's work, completed at its end
* plan: mcp-activity as implemented
* mcp: finalize step lines within a day and load only the hook's modules
* plan: mcp-activity review decisions as implemented
* plan: mcp-session-list
* plan: mcp-session-list, every session in one message (Q2 B)
* mcp: end live step lines by the wall clock
* mcp: exact spec ranges and measured hook load time
* mcp: a list of every session and its state in the Main group
* plan: mcp-session-list as implemented
* mcp: list of sessions: unknown states count cards, bounded record reads, stop edit before the card wait
* plan: mcp-session-list merged with master
* mcp: ROADMAP marks the items delivered since 0.3.0 with ✅
* plan: mcp-context-summary
* plan: mcp-context-summary answers and gear emoji
* mcp: a line when a session's context is summarised
* mcp: take only a compaction boundary created before the hook started
* plan: mcp-activity
* plan: mcp-activity list format
* plan: mcp-activity answers and live step lines
* mcp: a silent line per step of Claude's work, completed at its end
* plan: mcp-activity as implemented
* mcp: finalize step lines within a day and load only the hook's modules
* plan: mcp-activity review decisions as implemented
* plan: mcp-allow-tool
* mcp: approve a tool for the rest of a session with one tap
* plan: mcp-allow-tool as implemented
* mcp: docs of the approval of a tool for the rest of a session
* mcp: record the checks of the PreToolUse hook with Claude Code
* plan: mcp-allow-tool citations of the new code
* mcp: keep the approvals of tools while the session's process re-attaches
* plan: mcp-allow-tool review round 1
* mcp: end the approvals of tools when the session's group is lost
* mcp: tool approvals end when the session's group is lost, docs and tests
* mcp: tool approvals follow the process that opened the session last
A process is identified by its ID and its start time, read from /proc/PID/stat on Linux and from ps on macOS. A registration from a process with the same ID and another start time ends the approvals.
/attach has the session server's parent process ID. While two processes have the session attached, only the attachments of the process of the last /session get the approved tools; the others get an empty list.
Tests cover the end of the approvals at a load of a lost group.
* plan: mcp-allow-tool decisions 36 and 37, the group's loss in the rules and the design
* mcp: a process whose start time is unknown counts as another process
A registration of the session's process ends the tool approvals when its start time can't be read, on systems other than Linux and macOS and after a failed read. The start time is read only for a process ID that is a positive integer; on macOS, /bin/ps runs with a 2 s timeout.
* docs: MCP specs link files and name functions, without line numbers
* mcp: spec pointers above the functions, checked by a unit test
* mcp: spec pointers to API sections first, for every declaration described
* mcp: spec test reports malformed pointers and those not above a declaration
* plan: mcp-reactions
* plan: mcp-replies
* plan: mcp-replies, one vocabulary with reactions
* plan: mcp-reactions, quote vocabulary of mcp-replies
* plan: mcp-reactions, ReplyTo names of mcp-replies
* plan: mcp-replies, replyTo from callers, file name in quotes
* plan: mcp-replies, itemSender stays private, quoted file names
* plan: mcp-reactions, Claude named by the hub's profile name
* plan: mcp-replies, Q1 decided: serve returns the new reply_to
* plan: mcp-reactions, Q1 decided, Q2 with a receipt reaction
* plan: mcp-replies, quote line before the reply, as the user asked
* plan: mcp-reactions, Q2 decided, reply form with a quote line
* plan: mcp-reactions, quote line cut at 200 characters
* plan: mcp-replies, quote of 200 characters, ellipsis when cut
* plan: mcp-replies, one quote line of 200 characters with media type
* plan: mcp-reactions, quote line with the media type
* plan: mcp-reactions, blank lines before continued decision lists
* plan: mcp-replies, blank lines before the numbered lists
* mcp: tests of the quoted message of a reply
* mcp: Claude gets the message a reply quotes
* docs: line links of protocol types in the MCP architecture
* mcp: quote lines end at every line break and keep emoji whole
* mcp: tests of reactions passed to Claude
* mcp: spec links of the reply change cite the queue and push lines, labels equal their anchors
* plan: mcp-replies, tests of the review fixes, test names as in the code, the closing-tag escape of Claude Code
* mcp: quotes for Claude drop bidi controls
* mcp: Claude gets reactions as emoji replies to the reacted message
* plan: mcp-reactions, decisions on the merged replies code
* mcp: reaction tests use the hub's Main group and the typed unknown reaction
* mcp: reactions reach Claude as the apps show them
* mcp: only known reactions reach Claude, others get a reply
* mcp: one reply per member and message for reactions Claude does not receive
* ui: show "Why SimpleX is built." in About opened from Settings
* docs: "Why SimpleX is built." in About opened from Settings
* android, desktop: keep About and its text clear of the bottom bar
* android, desktop: no blank bar above the text with the bottom bar
* android, desktop: About and why-built references
* ios: About from Settings references
* ui: revert About's iOS spacer and preview, the text's pane and top space
* docs: revert the About link notes in the apps' settings docs
* android, desktop: update the why-built page's preview references
* android, desktop: scroll the why-built page's text under the toolbar
* ios: keep the About link at the bottom of the screen, as in onboarding
---------
Co-authored-by: spaced4ndy-agents <342056592+spaced4ndy-agents@users.noreply.github.com>
* android, desktop: readable error when a server test fails
* android, desktop: network and proxy details in server test errors
* android, desktop: test the text of server test errors
* android, desktop: set the server error test's locale and case name
* android, desktop: narrow the server test error text fix
---------
Co-authored-by: spaced4ndy-agents <342056592+spaced4ndy-agents@users.noreply.github.com>
* plan: mcp-activity
* plan: mcp-activity list format
* plan: mcp-activity answers and live step lines
* mcp: a silent line per step of Claude's work, completed at its end
* plan: mcp-activity as implemented
* mcp: finalize step lines within a day and load only the hook's modules
* plan: mcp-activity review decisions as implemented
* mcp: end live step lines by the wall clock
* mcp: exact spec ranges and measured hook load time
* mcp: cite the hook's skip of tool uses exactly
* store: register names across a commitment lapse without signing again
* store: count every commit toward Try again and moves
* store: update the names webapp submodule
* store: update the names webapp submodule
---------
Co-authored-by: sh-agents <350651734+sh-agents@users.noreply.github.com>
* core: show the latest item in chat previews
* core: update query plans
* tests: pass values to badge test queries as parameters
* core: update query plans
* store: tip transactions at the recent blocks' median tip
* store: write the minimum tip with digit separators
---------
Co-authored-by: sh-agents <350651734+sh-agents@users.noreply.github.com>