Marco Beretta 75110c70e5 fix: preserve earlier message and file expiries under forced retention ... Two leftover paths still extended data that was already scheduled to expire sooner when forcing ephemeral retention: - forceConversationMessagesTemporary (and the by-tag message backfill) rewrote every gap-matched message to the forced deadline, overwriting carried-over `all`-mode messages whose own per-message TTL was already sooner. Use a $min aggregation update so each message keeps its earlier deadline while still being marked temporary and capped if later. - File uploads under ephemeral retention skipped the conversation lookup and got a fresh TTL, so a new attachment to a chat with a preserved earlier expiry could outlive the TTL-deleted conversation. Cap ephemeral file expiry to the minimum of the fresh window and the active parent conversation expiry, mirroring the message and shared-link paths.		2026-07-01 19:38:20 +02:00
..
api	fix: preserve earlier message and file expiries under forced retention	2026-07-01 19:38:20 +02:00
client	🧪 ci: Resolve DataTable test infinite re-render (#13947)	2026-06-24 23:40:18 -04:00
data-provider	feat: add ephemeral retention mode for forced temporary chats	2026-06-30 04:51:45 +02:00
data-schemas	fix: preserve earlier message and file expiries under forced retention	2026-07-01 19:38:20 +02:00