The exact Monday digest in your inbox.
Same HTML, same plain-text as the 07:30 Monday note that goes to engineering, security, and compliance. One source of truth in @/lib/email/templates#mondayDigestEmail.
The on-screen card.
Rendered directly from the same helper the Monday cron uses to dispatch the inbox email. The plain-text alternative underneath matches the text-only fallback that ships to clients that block HTML.
- A one-sentence escalation summary at the top, called out only when needed.
- Up to four per-fix lines — each names the package, the version bump, the PR, and the rationale.
- Closes with the next nightly run time so the reader knows when the loop repeats.
Why five, not a list of sixty?
The brief is 'calm Monday note'. We cap at four fix entries (top by score) plus a one-line escalation summary above them — every other finding has already been batched into the PR list.
Is this the same as what the cron sends?
Yes. The route handler composes the digest through the same `mondayDigestEmail()` helper the email module ships — the inbox copy and this page copy start from a single function call.
Why is a sample showing on a freshly-seeded DB?
If no `ConnectedRepo` exists, or no `FixDraft` reconciled this ISO week, the page falls back to a representative sample so the preview is always screenshot-ready.