Marco Beretta d88182a163 fix: cap lagging children of already-conforming temporary conversations ... Both the migration sweep and the convert-on-touch cascade skipped a parent that already satisfied the forced-retention gap filter, so an already-temporary chat with dependent rows that lag behind it (permanent shares or later-window files created before the mode switch, or left by a partial earlier backfill) kept those children past the parent's TTL. Cap the children independently of the parent gap check: the single cascade runs the message/share/file caps before its parent conversion regardless of whether the parent needs converting (each cap is an indexed no-op once children conform; the bulk tag/project cascade already worked this way), and the sweep gains an alignment pass that walks already-conforming temporary conversations and caps their children to each parent's own deadline, reported via a new `aligned` count. The cap helpers now return their modified counts to support that reporting.		2026-07-05 01:57:14 +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: cap lagging children of already-conforming temporary conversations	2026-07-05 01:57:14 +02:00