The notice now follows the engine's upcoming() list, so a snackbar
already on screen comes down when its alarm is switched off by another
path, and one whose ring moved, such as a skip armed from the
notification, shows the new countdown. Consuming matches the
announcement, not the words.
Editor writes that move a fire time, skip-next and delete run on the
application scope through one fair queue, entered undispatched so they
commit in tap order. Without it, "skip next" followed at once by
untapping the only repeat day could land out of order and leave a
one-shot with a skip armed, which disables it.
Refs #19
makiolaj
ff49667d39