Marco Beretta f415ca0e38 fix: keep the forced-retention cascade re-runnable after a child failure ... cascadeForcedConversationRetention converted the parent conversation first and only backfilled its messages, shares, and files when that update modified a row. If a child backfill threw after the parent was converted, a later forced-retention write saw the parent already conforming (modifiedCount 0) and skipped the children, leaving not-yet-updated messages, shares, or files permanent. Gate on an in-memory conversationNeedsForcedRetention check and backfill the children before marking the parent conforming, so a failed child leaves the conversation non-conforming and the next write re-runs the whole cascade. The early return preserves the no-op-when-already-conforming behavior.		2026-07-05 00:12:26 +02:00
..
api	fix: enforce ephemeral retention on chat project membership changes	2026-07-03 15:03:09 +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: keep the forced-retention cascade re-runnable after a child failure	2026-07-05 00:12:26 +02:00