- Shipped
- July 3, 2026 at 3:08 AM UTC
- Author
- kamo
- Commit
- abbc18d
myStatus from AvailabilityContext defaults to 'AVAILABLE' until two async fetches (/user-info then /members/me/availability) resolve, so on a browser refresh the lead-alert summary could resolve first and fire the popup — the false→true summary looked like a new lead and the default 'AVAILABLE' passed the status guard even when the member was BUSY/AWAY/DND. Adopt the first resolved summary as a silent baseline: the popup now only fires for leads that become acceptable while the page is open (a genuine new drop), by which point the real availability status has loaded.