Don't snooze high alarm when there is no IOB (#6348)

[IsraelAfangideh]

Fixes #6348.

Problem

The Bolus Wizard Preview plugin snoozes a high alarm when prop.bolusEstimate < snoozeBWP, treating a near-zero estimate as "there is enough insulin on board to cover the high". But bolusEstimate starts at 0 and stays 0 in a case that has nothing to do with IOB coverage:

• the BG is above the alarm threshold (bgTargetTop) yet still below the profile high target, so neither the high nor the low branch of calc() runs.

With no insulin on board, bolusEstimate is then left at its initial 0, and a genuine high alarm gets silenced. This matches the report in #6348: a complete profile, a default ISF, and no insulin treatments. (The exact target_high from the report is not in the issue, so this is the most likely mechanism consistent with it rather than a certainty.)

Because the snooze is requested at URGENT level and notifications.snoozedBy() matches by level across the group, this can also suppress other urgent alarms for the snooze duration.

Note: the other path that leaves bolusEstimate at 0 — calc() returning early with errors (missing profile/IOB, stale data) — is already handled, since checkNotifications() returns early when prop.errors is non-empty before highSnoozedByIOB is ever called. So this change targets only the no-error, no-IOB case above.

Fix

Guard the snooze on prop.iob > 0, so a high alarm is only snoozed when there is actually insulin on board to cover it:

return high && prop.iob > 0 && prop.bolusEstimate < settings.snoozeBWP;

Legitimate enough-IOB snoozing is unchanged. No new dependencies.

Tests

Added to tests/boluswizardpreview.test.js:

• does not snooze a high alarm with no IOB when the BG sits below the profile high target (the Alarms Snoozed when IOB add-on enabled but not being used #6348 scenario — fails without the fix, passes with it)
• still snoozes a high alarm when real IOB covers it (unchanged behavior)

Full suite green locally (1346 passing).

🤖 Generated with Claude Code