Critical: In-Memory Presence State Not Persisted

[pablopunk]

Description

src/server/presence/manager.ts:59 uses in-memory Map for presence tracking.

Impact

All presence data lost on server restart. Running containers may stop unexpectedly when all viewers disconnect before reaper runs.

Fix

Persist presence state to database.

File

src/server/presence/manager.ts:59

[pablopunk]

Downgrading severity from 'Critical'. While presence tracking is still in-memory (presenceMap), the impact is limited: containers auto-stop on idle timeout and restart on next heartbeat. The core project/container state lives in DB. This is an operational enhancement for graceful restart behavior, not a critical bug.

[pablopunk]

Closing: After review, this is low-impact for self-hosted use. Containers auto-recover on reconnect, and the core state is in DB. The jarring experience of container restart on server reboot is acceptable for now. Can revisit if users complain.