Alert channels configured beyond logging

Log-only alerting means a human must be watching logs at the exact moment an email system failure occurs. A Slack webhook or PagerDuty alert configured for queue backlog and ESP failure conditions changes the detection model from passive (someone notices) to active (system notifies). ISO 25010 reliability.operability requires that operational problems are communicated to operators without manual monitoring. Teams that rely on log scraping during on-call hours routinely miss email incidents for 30–90 minutes — long enough for complaint rates to spike above Gmail's 0.1% threshold.

Wire push notifications to at least two alert conditions in a shared utility (e.g., src/lib/alerts.ts):

async function alertOps(message: string, severity: 'warning' | 'critical') {
  await fetch(process.env.SLACK_WEBHOOK_URL, {
    method: 'POST',
    headers: { 'Content-Type': 'application/json' },
    body: JSON.stringify({ text: `[${severity.toUpperCase()}] Email system: ${message}` })
  })
}

Call alertOps() on ESP failover events, bounce rate threshold breaches, and queue depth spikes. A Slack SDK installed but never called on error conditions does not satisfy this check.