- Shipped
- October 19, 2026 at 3:55 AM UTC
- Author
- Kamo
- Commit
- f2d5999
F12 (IoT close-out, SP14 routing): AlertChatService defaulted to organization 1 and the aliases "sage" / "kamo-monitor", which name nobody in production, so every cluster alert went by email only. Now, with nothing configured: the platform's top-level organization, its owner (the system member public-chat tickets and the Exec2Exec greeting use), from the System User's member there. No organization id or name is hard-coded; KAMO_ALERT_CHAT_ORG_ID / _RECIPIENT_ALIAS / _SENDER_ALIAS still override. The top-level organization never holds a System User member, so it answers NO_SENDER (email only) until a sender alias is configured; a configured id that names no organization is NO_ORGANIZATION. F14 (IoT SP10): an IOT_ALARM lifecycle push (ack/clear/close/shelve: iot-alarm-updates channel, iot-alarm-update category) carries no sound and the passive interruption level on iOS, as Android's quiet channel; new and escalated alarms keep their sound (urgent ones stay time-sensitive).