Marco Beretta fb095b9241 fix: return the converted conversation after forced project retention ... assignConversationToProject captured the findOneAndUpdate result before running the forced-retention conversion, so under ephemeral mode the returned object was a stale pre-conversion snapshot. The client writes that object straight into the active conversation and the React Query cache, so an assigned/removed permanent chat was cached as non-temporary with no expiredAt until a later refetch. Run the retention conversion before capturing the updated document so the findOneAndUpdate result carries the isTemporary/expiredAt fields alongside the chatProjectId change. A no-op outside forced retention.		2026-07-04 16:07:33 +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: return the converted conversation after forced project retention	2026-07-04 16:07:33 +02:00