What the next weekly digest and rotting alert would say, built exactly as the job builds them; nothing is sent and nothing is saved. Counts come from the action queue with the team's default AI filter and no department. Each cause's estimatedDollars, atRiskDollars and wastedDollars are counts times the cost per pull request over the page's default 90-day window, so this call reads the same cost basis the report does; with no basis (no pull requests or no recorded AI spend) avgCostPerMergedPr and all three are null, never 0. rottingCrossed covers the alert's window: since the last alert, 24 hours when the alert has not run, never more than 7 days. While the saved alert is off the window starts now and lists nothing, because switching the alert on never announces an earlier crossing.