Outbreak digest mode (batch notifications on high-activity days)

claude-bot commented

2026-07-18 05:31:38 +00:00

Contributor

On high-activity days the current design can send dozens of per-alert messages per channel; a per-subscription "digest above N alerts/hour" batching option. Real value, but interacts with F-11's delivery redesign — sequence after it. Effort M.

Filed from the 2026-07-17 codebase audit (docs/.internal/report-2026-07-17.md), finding I-06.

On high-activity days the current design can send dozens of per-alert messages per channel; a per-subscription "digest above N alerts/hour" batching option. Real value, but interacts with F-11's delivery redesign — sequence after it. Effort M. --- _Filed from the 2026-07-17 codebase audit (`docs/.internal/report-2026-07-17.md`), finding I-06._

claude-bot added this to the v1.5.0 - Feature enhancements milestone

2026-07-18 05:31:38 +00:00

claude-bot added the

area:notifications

type:feature

labels

2026-07-18 05:31:38 +00:00

rbrooks referenced this issue from a commit

2026-07-19 16:31:03 +00:00

Add outbreak digest mode (#76)

claude-bot referenced this issue from a pull request that will close it,

2026-07-19 16:31:14 +00:00

v1.5.0 Phase 5: outbreak digest mode (#76) #116

claude-bot closed this issue

2026-07-19 16:38:30 +00:00

claude-bot referenced this issue from a commit

2026-07-19 16:38:31 +00:00

Merge pull request 'v1.5.0 Phase 5: outbreak digest mode (#76)' (#116) from feat/v1.5.0-phase5-digest into main

claude-bot commented

2026-07-19 16:38:41 +00:00

Author

Contributor

Done in #116 (merged). Per-subscription opt-in digest_threshold (null = off, default): once a (channel, location) sub has sent that many alerts within DIGEST_WINDOW_MINUTES (60), further advisory/watch alerts are batched and delivered as one periodic digest by a flush_alert_digests job every DIGEST_FLUSH_MINUTES (30). The digest is a synthetic "Weather Alert Digest" NWSAlert dispatched through the existing per-notifier send path (no new per-notifier code), double-send-safe (pending flag cleared atomically with a kind="digest" ledger row the outbox never re-drives), quiet-hours-aware, fail-soft per group.

Safety decision: warning-class alerts are never batched — they always dispatch immediately (holding a life-safety warning up to the flush interval is unacceptable, and an operator taming advisory spam wouldn't expect it). Only advisories/watches digest. If you'd prefer everything batched during an outbreak instead, it's a one-line change. Migration 0028; 7 tests (incl. test_warning_class_never_defers); bulk 746 passed.

Done in #116 (merged). Per-subscription opt-in `digest_threshold` (null = off, default): once a (channel, location) sub has sent that many alerts within `DIGEST_WINDOW_MINUTES` (60), further **advisory/watch** alerts are batched and delivered as one periodic digest by a `flush_alert_digests` job every `DIGEST_FLUSH_MINUTES` (30). The digest is a synthetic "Weather Alert Digest" `NWSAlert` dispatched through the existing per-notifier send path (no new per-notifier code), double-send-safe (pending flag cleared atomically with a `kind="digest"` ledger row the outbox never re-drives), quiet-hours-aware, fail-soft per group. **Safety decision:** warning-class alerts are **never** batched — they always dispatch immediately (holding a life-safety warning up to the flush interval is unacceptable, and an operator taming advisory spam wouldn't expect it). Only advisories/watches digest. If you'd prefer everything batched during an outbreak instead, it's a one-line change. Migration 0028; 7 tests (incl. `test_warning_class_never_defers`); bulk 746 passed.

claude-bot referenced this issue

2026-07-19 16:39:52 +00:00

Add v1.5.0 changelog #117

Rows
Columns

Outbreak digest mode (batch notifications on high-activity days) #76