chahinebrini 5b57bea9c0 perf(mail): kill redundant 30min scan-cron + in-flight scan guard ...

Backend-Lag-Fix Phase 1 — entlastet die CPU-Dauerschleife im Mail-Stack:
- delete mail-scan-cron.ts: der 30-Min-Nitro-Cron scannte alle User parallel
  (Promise.allSettled) und war redundant zum IMAP-IDLE-Daemon (Single Source
  of Truth). Reine Dauerlast ohne Mehrwert.
- imap-idle: In-Flight-Guard (scanInFlight + coalescePending). triggerScan ist
  jetzt re-entry-safe — pro Connection max. 1 aktiver + 1 pending Scan statt
  bis zu 8 gestapelt pro 2-Min-NOOP-Tick. Gilt für NOOP + exists-Event.
- plan-features: Pro mailAgents 3->2 (+ Math.min-Hack in coach/message aufgeräumt).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-05 10:38:06 +02:00

..

blocklist-cron.ts

initial commit: rebreak-monorepo (RN app + standalone Nitro backend)

2026-05-06 07:13:43 +02:00

device-lock-cron.ts

feat(backend): device-account binding for pro/legend users

2026-05-16 00:29:35 +02:00

mail-retention-cron.ts

feat(backend): mail_classification_samples row-cap (100k max)

2026-06-01 09:44:55 +02:00

pro-trial-expiry-cron.ts

feat(profile): DiGA-Demographics + Pro-Trial-Reward + 7 Profile-Endpoints

2026-05-07 21:14:06 +02:00