Marco Beretta 0247fce256 fix: apply retention to forked and duplicated conversations ... The fork and duplicate paths created the import batch builder without the runtime interface config, so under retentionMode "ephemeral" a fork or duplicate of an existing permanent conversation skipped the forced isTemporary/expiredAt fields and bypassed the policy. Plumb req.config.interfaceConfig through forkConversation and duplicateConversation into the builder so cloned records honor retention.		2026-06-23 16:40:21 +02:00
..
__data__
defaults.js
defaults.spec.js
fork.js
fork.spec.js
importBatchBuilder.js
importConversations.js
importers-timestamp.spec.js
importers.js
importers.spec.js
index.js