Files
Daniel Salazar f93050bb49 fix(alarm): forget idle alarms and cap how many the client holds
AlarmClient kept every alarm id it had seen for the life of the process,
and ids that embed a user, key or invoice grew it without bound. The
registry is now ordered by last occurrence: alarms idle for 24 hours are
dropped on the next create, and past 1000 the least recently raised goes
first. Clearing or evicting an alarm only removes its short-id alias when
the alias still points at it.
2026-10-11 11:58:24 -04:00
..
…
2026-09-24 18:55:10 -04:00