Ole-Morten Duesund 8c3cd0c965 Don't nag for future doses: time-guard escalation resume ... 'Ta nå' + 'Angre' on a not-yet-due dose leaves a PENDING log with a future scheduledAt; armAll() (every app start/update) then resumed 'escalation' for it as if it were overdue — nagging hours early. Three layers: armAll only resumes escalation for past-due logs, the escalation receiver drops anything scheduled in the future (defense in depth), and undo resets nagCount + cancels any escalation so stale counts can't eat the real quota when the dose actually falls due. Emulator-verified with both cases side by side: past-due PENDING nags within the minute, future PENDING stays silent. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>		2026-06-11 18:26:46 +02:00
..
schemas/no.naiv.meddetsamme.data.MedDatabase	Inventory split: InventoryItem entity, schema v2 with tested migration, Lager screen	2026-06-10 15:13:28 +02:00
src	Don't nag for future doses: time-guard escalation resume	2026-06-11 18:26:46 +02:00
build.gradle.kts	New launcher icon, version 0.2.0, lint cleanup	2026-06-11 17:55:06 +02:00