getPendingCount and getDueCount in src/services/deferredReminders.service.ts (lines 110-129) are documented "Useful for monitoring and metrics," but a repo-wide search shows neither is called anywhere outside their own definitions — no health endpoint, admin route, or metrics gauge surfaces the number of pending or overdue deferred (quiet-hours-blocked) reminders. Given the separately-filed finding that milestone.reminders/milestone.reminders.digest are never actually scheduled to run in the first place, having no visibility into the deferred-reminder backlog compounds the risk of that feature silently accumulating unprocessed work with no operational signal. Wire these into the admin/health surface, or remove them if the deferred-reminder feature isn't being operated.
getPendingCountandgetDueCountinsrc/services/deferredReminders.service.ts(lines 110-129) are documented "Useful for monitoring and metrics," but a repo-wide search shows neither is called anywhere outside their own definitions — no health endpoint, admin route, or metrics gauge surfaces the number of pending or overdue deferred (quiet-hours-blocked) reminders. Given the separately-filed finding thatmilestone.reminders/milestone.reminders.digestare never actually scheduled to run in the first place, having no visibility into the deferred-reminder backlog compounds the risk of that feature silently accumulating unprocessed work with no operational signal. Wire these into the admin/health surface, or remove them if the deferred-reminder feature isn't being operated.