# The "this session already died, I told you" memory now survives restarts

When a session genuinely dies of "conversation too long", the monitor tells you ONCE — there's a little memory of which deaths it already announced, so it doesn't repeat itself every minute. That memory lived in RAM only. Every time the server restarted (which happens a lot — every auto-update bounces it), the memory was wiped, so the monitor would look at the same dead session and announce the same death again — once per restart. On an update-heavy day that meant the same "conversation too long" message landing in your chat over and over (the overnight wall of 26 messages in the API-errors topic, and 4-in-2-hours on another).

The fix: that memory is now written to a small file on disk (one line per topic: which session's death was announced and when). On boot the monitor reads it back, so a restart no longer forgets. A successful recovery still clears the entry (a FUTURE genuine death will announce normally), entries older than a week are dropped automatically, and if the file is ever missing or corrupted the monitor just starts with an empty memory — worst case is one repeat notice, exactly the old behavior, never broken monitoring.
