Repository navigation
[Feature] Wellness alerts, freshness monitoring, and alert history #98
Description
Outcome
Make OpenGlucose operational in daily use with trustworthy, user-configured freshness, disconnect, and optional glucose-threshold notifications—without claiming medical-grade emergency monitoring.
Dependencies and coordination
- Wait for the warmup/live-notification work in PR Fix sensor warmup, scan recovery, and live glucose updates #35 to merge.
- Coordinate with release/hardware work in Release readiness: Android compatibility, stable 0.1, and external TestFlight #34.
- Reuse the existing live payload and background state contracts.
- This is serialized with any work touching iOS Live Activity, Android live notification service, or shared live payload files.
Scope
- Pure-Dart evaluator for stale data, disconnect, and optional high/low wellness thresholds.
- User-configurable values, units, quiet hours, repeat/snooze behavior, and disable controls.
- Foreground and background local delivery on supported platforms.
- In-app alert history with trigger evidence, freshness/source state, dismissal, and retention.
- Explicit behavior during warmup, reconnection, sensor expiry, sample mode, and missing permissions.
- Rate limiting and deduplication across restarts/background transitions.
- Separate private lock-screen content consent from alert enablement.
Product language
These are wellness/self-experimentation notifications, not clinical hypo/hyper alarms, diagnosis, treatment guidance, or emergency monitoring.
Parallelization
Blocked and serialized until PR #35 lands. The pure-Dart evaluator and fixtures may be designed in parallel, but native notification files have one owner.
Acceptance criteria
- Threshold, stale, and disconnect rules are deterministic and unit tested.
- Warmup values never trigger glucose-threshold alerts.
- Stale/disconnected notifications distinguish freshness failure from a glucose value.
- Duplicate/repeated/background transitions do not spam.
- Permission denied/revoked, reboot, app kill, timezone, quiet hours, and sensor replacement are tested.
- Alert history shows why an alert fired and which timestamp/source state supported it.
- Sensitive lock-screen values remain redacted by default and consent revocation fails closed.
- Sample/demo data generates no personal notifications.
- Physical-device Android/iOS evidence and R2 independent review are complete.
Repository-owner recreation of the legacy issue at #45. The original discussion remains available there.
Activity