jackandGitHub a1711bd399 Retry unacknowledged DMs after Noise replacement (#1462) ...

DMs sent through an established Noise session are retained in the durable MessageRouter outbox until an authenticated delivery/read ack, and retried under the same message ID when the peer's replacement handshake authenticates — fixing DMs silently lost into stale local sessions after a remote app restart. Mesh ack handling is peer-scoped end-to-end (alias-scoped delivery status, peer-bound markDelivered, PeerMessageKey retry state), so a colliding message ID from another conversation can no longer clear or promote foreign state; bridge-drop dedup keys are recipient-scoped with hashed persistence.

Includes review fix: acks arriving after a relaunch (durable outbox restored, conversation not) now clear the peer-scoped router entry unconditionally — only the UI status transition is gated on conversation presence — so a delivered message can no longer re-send to the attempt cap and be marked failed despite delivery. Regression test simulates the relaunch through real store persistence; the dead allowedPeerIDs parameter (unscoped-tombstone trap) is removed.

2026-07-26 15:37:50 +02:00

..

perf-floors.json

Avoid conversation index rebuilds at retention cap (#1435)

2026-07-26 10:52:28 +02:00

PerformanceBaselineTests.swift

Retry unacknowledged DMs after Noise replacement (#1462)

2026-07-26 15:37:50 +02:00