2 Commits

Author	SHA1	Message	Date
TekH	111d2bf264	fix(domain): use DateTime.Now instead of DateTime.UtcNow for legacy compatibility ... CRITICAL FIX: Replace all DateTime.UtcNow with DateTime.Now throughout the application. Reason: Legacy VB.NET system uses local server time, and database stores all timestamps as local time. Using UTC breaks compatibility and causes incorrect time comparisons. Changes: - EmailProcessedEvent: ProcessedDate now uses DateTime.Now - EmailHistory.MarkAsProcessed(): ProcessedDate now uses DateTime.Now - EmailHistory.MarkAsFailed(): ProcessedDate now uses DateTime.Now - EmailProfile.UpdateLastPollTime(): LastPollTime now uses DateTime.Now - EmailProfile.ShouldPoll(): Poll interval comparison now uses DateTime.Now Documentation: - Added critical note to agents.md about DateTime usage - Includes examples and detailed explanation for future developers This ensures all date/time operations remain compatible with legacy database.	2026-07-08 10:36:13 +02:00
TekH	331b73000e	docs: add critical notes and future enhancements for agents ... Important notes: - Database schema must NEVER be modified - MessageId hash algorithm must match legacy system exactly - No git commits without explicit permission - Naming conventions (SNAKE_CASE DB, PascalCase C#) Future enhancements: - RabbitMQ queue implementation plan (replacing in-memory queue) - Complete migration path and configuration examples - Pending implementation tasks for each phase - Known issues and limitations (PdfSharp, windream COM) Architecture decisions: - Clean Architecture with DDD - CQRS pattern with MediatR - Repository pattern Development guidelines: - Code style conventions - Logging with Serilog - Configuration management - Error handling strategies - Deployment scenarios (IIS/Windows Service)	2026-07-07 18:59:57 +02:00