Alarm() handler storage writes guarante & coalesce?

Do storage writes coalesce and guarantee execution for alarm() handler if I don’t await them like the fetch handler? I am assuming so but I couldn’t find anything in the docs on it specifically and not sure an accurate test for this since it might(?) involve failover.

For example if I have:

alarm() {
  // blah"k", "v")"a", "b")

Will those 2 final put operations guarantee to happen before the alarm() handler is deemed successfully run, and if it fails, the object will be evicted, restarted, and that alarm handler will run again?

The reason I suspect this would be the case is that disabling the alarm (calling execution successful) would need to write to storage. And since in this alarms blog post they mention that the get() and set() for alarm methods include write coalescing, then that would merge with operations in the alarm handler as well.

same behaviors as fetches, alarm completion is subject to the output lock just as returning a response is, i.e we won’t confirm the alarm as having succeeded unless any writes it makes have succeeded too

Thank you!