[0xbrayo]

Part of #333.

NotifyWorker remembers which thresholds already fired with a triggered_<category>_<configHash>_<logicalDate> key per alert per day. Keys from earlier days were never removed, so aw_notify_prefs kept growing, by one key per alert per day plus one for every reconfiguration. SharedPreferences parses the whole file into memory on first access and rewrites all of it on each apply(), so that cost grows with every day the app is installed.

Change

• Before checking thresholds, remove `triggered_*` keys more than two logical days older than the current one (`staleTriggeredKeys`).
• Recent days are kept on purpose: moving `startOfDay` later (e.g. 04:00 → 06:00) can move the logical day back by one, and that day's fired thresholds must still be recorded so alerts don't fire twice.
• Keys whose date can't be parsed are left alone.

Testing

• New NotifyWorkerTest cases: keys outside the window are dropped (including the null/"All" category), recent days and unrelated or unparseable keys are kept, and yesterday's keys survive when the logical day moves back.
• ./gradlew :mobile:testStandardDebugUnitTest passes.

[greptile-apps]

Confidence Score: 5/5

[Medium impact] This PR appears safe to merge.

Summary

This PR removes old alert-trigger keys from aw_notify_prefs.

• Notification alert keys older than two logical days are cleared.

The previous unnumbered finding is fixed: changing startOfDay can move the logical day back by one without losing that day’s fired thresholds.

_{Reviews (3) · Last reviewed commit: "fix(notify): keep two recent days of ale..." · Reviewed by Greptile}

[0xbrayo]

🤖 Claude, on behalf of @0xbrayo

@greptile review

[0xbrayo]

🤖 Claude, on behalf of @0xbrayo

@greptile review