6 Commits

Include renames

Author	SHA1	Message	Date
FreeTLab	3ebb41aa9d	fix(alarm): arm a just-passed occurrence instead of skipping it a day ... The native next-occurrence recompute required the trigger to be strictly in the future, while the Dart side keeps an occurrence whose trigger passed within a 90s tolerance. When the periodic resync re-armed an alarm microseconds after its trigger (app foregrounded, the 60s tick straddling the trigger instant), computeNextTriggerMillis recomputed the next weekday/daily occurrence as tomorrow and, through the shared FLAG_UPDATE_CURRENT fire PendingIntent, replaced the in-flight fire before AlarmManager delivered it. The alarm never rang until the screen was turned on and the Dart watchdog caught it late. computeNextTriggerMillis now mirrors Dart's toleranciaDisparoInminente: base is lowered by a 90s grace window so a just-passed occurrence is armed (and delivered ~immediately) rather than pushed to the next day. The handledFloor (lastHandledAtMillis + 60s) stays a hard lower bound, so an already-fired occurrence can never be re-selected — no double-fire. Dart contract tests lock the boundary the native constant must track. Native verification is on-device (no JVM test harness).	2026-07-11 23:02:14 +02:00
Javier Bautista Fernández	d45fbe60db	fix(alarms): skip handled occurrence when recalculating	2026-05-29 13:29:41 +02:00
Javier Bautista Fernández	659e6da189	fix(alarms): harden native playback and pre-notice actions	2026-05-28 12:03:58 +02:00
FreeTLab	896349ad5f	feat(app): add onboarding and harden alarms	2026-05-23 01:22:49 +02:00
FreeTLab	a48dd6ddf9	fix(alarms): refresh next execution reliably	2026-05-22 18:42:11 +02:00
FreeTLab	fb808ebb60	feat(alarm): add musical alarm foundation	2026-05-21 23:47:06 +02:00