hailin d083008001 fix(conversations): implement soft-delete for conversation deletion ... The delete conversation endpoint was a no-op — it verified ownership but never actually modified the record. Users saw conversations disappear (frontend optimistic removal) but they reappeared on refresh. Changes: - conversation.entity.ts: Add DELETED status, softDelete() and isDeleted() - conversation.service.ts: Call softDelete() + update instead of no-op - conversation-postgres.repository.ts: Exclude DELETED conversations from findByUserId() queries so they don't appear in user's list Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>		2026-02-06 20:49:03 -08:00
..
conversation-service	fix(conversations): implement soft-delete for conversation deletion	2026-02-06 20:49:03 -08:00
evolution-service	fix(analytics): handle statDate as string from database	2026-01-26 08:40:09 -08:00
file-service	fix(tenant): use TenantContextModule.forRoot() for global tenant context	2026-01-26 04:31:56 -08:00
knowledge-service	fix(db): add multi-tenancy migration for knowledge-service tables	2026-02-06 09:23:13 -08:00
payment-service	fix(tenant): use TenantContextModule.forRoot() for global tenant context	2026-01-26 04:31:56 -08:00
user-service	fix(nginx): fix admin location try_files path and add multi-tenancy migrations	2026-01-26 07:46:52 -08:00