feat: MAJOR - implement webhook-first architecture with database priority
Revolutionary Workflow Changes (v0.7.0): This fundamentally changes how NFOGuard handles timestamps and processing priority. Webhooks = Source of Truth: - First webhook fires → Use current timestamp → Store as permanent database entry - Subsequent webhooks (upgrades) → Check database → Use original first-seen timestamp - No more API calls during webhook processing → Webhook timing is ultimate authority - Movies and TV episodes both use webhook-first approach Manual Scans = Smart Fallback Logic: - Priority 1: Our database (webhook timestamps) - database always wins - Priority 2: Sonarr/Radarr import history (first import only) - Priority 3: Air date as dateadded (final fallback) Technical Implementation: - Enhanced _get_webhook_episode_date() to use current timestamp as source of truth - Added webhook_mode parameter to process_movie() for separate webhook logic - All manual scans prioritize database entries before making API calls - All timestamps converted to container timezone (Eastern Time) - Enhanced debug logging for database lookups and timestamp decisions Expected Workflow: First download at 8:30am → webhook timestamp stored in database Upgrade at 2:00pm → database entry found → original 8:30am timestamp preserved Manual scan → database entry found → 8:30am timestamp used This ensures the first-seen webhook timestamp is the permanent source of truth, with upgrades and manual scans always preserving the original download time.
This commit is contained in:
