AlarmKit: suppress overdue alarm playback before first unlock after reboot?

On a physical iPhone running iOS 27.0.1, an AlarmKit alarm due while the device was powered off sounded immediately after restart, approximately two minutes after its deadline, before the first passcode entry or app launch. We observed this with both fixed(Date) and relative hour/minute with repeats: .never. A normal control rang on time. Inspection of the public AlarmKit interface in iPhoneOS SDK 27.0 found no expiry parameter.

Is this overdue replay expected? Is there a supported validity window or guaranteed pre-presentation mechanism that suppresses expired opportunities while retaining valid future opportunities? Cleanup after app launch is too late. Should this be filed as a bug or enhancement request?

I don't know of a public AlarmKit setting that gives an alarm an expiry window or lets an app filter it before the system presents it. Since the device was powered off, cleanup in your app after launch would be too late for this case.

I'd file this with Feedback Assistant as a reproducible behavior or API request, including the exact iPhone model, iOS build, alarm configuration, due time, shutdown/restart times, and whether the device was unlocked afterward. A small sample app would help Apple determine whether this is expected behavior or a bug. If anyone has found a documented AlarmKit API for this, I'd be interested too.