Ring the Alarm style from a foreground service; roll a passed time forward

[mapgie]

Why

Alarm-style memos arrived as a silent heads-up (Samsung, vibrate mode, every permission row green), while the Settings test ring worked locked or unlocked.

The LESSONS #52 fix started AlarmActivity directly from AlarmReceiver. An alarm receiver has no background-activity-launch exemption. The start only succeeds within the few seconds after the app was on screen, which is exactly when the 10-second test ring fired. A real memo fires later, the launch is blocked without an exception, and the only sound left is the notification's, on the muted notification stream.

What

Ring service

• New AlarmRingService, a foreground service with type systemExempted (reserved for exact-alarm holders that keep an alarm ringing). AlarmReceiver starts it through NotificationHelper.deliverOnTime. It posts the alert with startForeground and loops AlarmRinger on the alarm stream until the alarm is answered or swiped away, or the 2-minute timeout ends the ring. A timeout leaves the notification in the shade.
• AlarmActivity is now the answer screen only. It rings itself only when the service isn't ringing, which covers late deliveries from BootWorker and a refused service start.
• Every answer path silences the ring by one id (AlertIds): the notification's Done and Snooze, swiping it away (new delete intent), the ring screen, the in-app nudge, and opening the app from the alert.
• If Android refuses the service start, the alert is posted as a plain notification, as before.
• Manifest: adds FOREGROUND_SERVICE and FOREGROUND_SERVICE_SYSTEM_EXEMPTED, each with a comment. The permission list in CLAUDE.md is updated to match.

Test ring

• Fires after 1 minute instead of 10 seconds, and asks the user to leave the app first, so it runs in the same conditions a real alarm does.

Edit sheet

• Changing the time of a once-only memo to a time that has already passed moves the ring to that time's next occurrence (ringForPickedTime).
• A ring moved into the past can't be saved (onceOnlyRingSavable). A memo that has already rung can still be saved as long as its ring is unchanged, so renaming it still works.

Docs

• LESSONS fix(fonts): bundle Nunito and Lora TTFs instead of downloading at runtime #66 records the background-start trap. Bump mapgie/android-Actions/.github/workflows/license-sync.yml from 87b0b6408e7168235e4977377add51c312ebab71 to 252cf0054ab486b6aa3e87563bc12146d97ff891 #52 now points to it.

Tests

• ReminderPickedTimeTest: roll-forward and save rules. All 8 cases also ran locally against the extracted functions.
• DeliveryStyleTest: alert ids stay distinct between memos and tasks, and keep the values alerts already in the shade were posted under.
• a11y_check.py and check_changelog_fragment.py are clean.

To verify on device

1. Set a memo 3 minutes out, swipe the app away, and leave the phone unlocked in vibrate mode. It should ring on the alarm stream with a heads-up.
2. Same again with the phone locked. The ring screen should show over the lock screen, and Done or Snooze should stop the ring.
3. Swiping the ringing notification away should stop the ring.

🤖 Generated with Claude Code

https://claude.ai/code/session_012c2DoXy9u68tYVUnmziZPy