Marco Beretta da5b1e222b fix: backfill lagging messages when capping to an already-sooner parent ... When a message-only forced save caps to a parent that is already temporary and expires before the freshly computed window, the gated cascade leaves the parent untouched (modifiedCount 0) and skips the message backfill. Older messages with expiredAt null or a later deadline then survive after the parent's TTL deletes the conversation. Extract the cap logic into capForcedRetentionToParent, shared by saveMessage and applyForcedRetention, which now also backfills the conversation's non-conforming messages to the parent's earlier deadline. The hot normal-send path does not cap, so it keeps the gated cascade with no extra per-message work.		2026-07-01 19:38:01 +02:00
..
api	fix: cap shared-link expiry at source conversation and enforce retention on assistant saves	2026-06-30 04:51:45 +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: backfill lagging messages when capping to an already-sooner parent	2026-07-01 19:38:01 +02:00