shoc-backend/SeaHaven.Services
Alexandre Brandizzi 14c8e46dd0 feat(notifications): SEV response-window alerts and breach acknowledgement
Reactive/Emergency work orders with a SEV 1-5 level are timed from their
creation against the SEV Respond deadline (2/4/8/24/72 hours, one backend
table). From 50% they are at risk: a dismissable High row in the "SLA at
Risk" section and an entry in the feed's slaAtRisk set with the server
clock (start, deadline, percent) for the banner and toast. From 100% they
are a Critical acknowledge row that only acknowledging removes.

POST /api/notifications/sla/{id}/acknowledge records who and when as a
work-order audit entry ("SLA breach acknowledged by <name>"), scoped to the
caller's feed audience: 404 outside it, 409 before the deadline, 204 when
recorded or already recorded. A later severity change is a new breach.
2026-09-25 11:16:21 -03:00
..
Configuration feat(permissions): protect configured account owner (SH-329) 2026-09-16 21:40:22 -03:00
Constants feat(team-members): support pending member creation (SH-325) 2026-09-16 21:41:55 -03:00
DependencyInjection feat(permissions): protect configured account owner (SH-329) 2026-09-16 21:40:22 -03:00
DTOs feat(notifications): SEV response-window alerts and breach acknowledgement 2026-09-25 11:16:21 -03:00
Exceptions fix: map concurrent uplift inserts to conflict 2026-09-23 01:26:15 -03:00
Helpers feat(notifications): SEV response-window alerts and breach acknowledgement 2026-09-25 11:16:21 -03:00
Implementation feat(notifications): SEV response-window alerts and breach acknowledgement 2026-09-25 11:16:21 -03:00
Interfaces feat(notifications): SEV response-window alerts and breach acknowledgement 2026-09-25 11:16:21 -03:00
Validation feat(locations): manage ordered site contacts 2026-09-15 19:03:54 -03:00
SeaHaven.Services.csproj refactor: enforce backend boundaries and optimize dispatch (#30) 2026-07-24 17:35:34 -03:00