Alexandre Brandizzi 47060f6a73 fix(work-orders): never return a severity on an Overdue board row ... A standalone severity patch on an Overdue WO still stores the value, because the board patches severity before type when correcting Overdue to Emergency/Reactive and that write must not be dropped or rejected. Project the severity as null for Overdue in the board row mapping, which also feeds the PATCH response, search results and the detail view, so a stored value never surfaces on a type that carries no severity.		2026-09-25 13:41:19 -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(work-orders): add Overdue work order type	2026-09-25 10:57:34 -03:00
Exceptions	fix: map concurrent uplift inserts to conflict	2026-09-23 01:26:15 -03:00
Helpers	feat(work-orders): add Overdue work order type	2026-09-25 10:57:34 -03:00
Implementation	fix(work-orders): never return a severity on an Overdue board row	2026-09-25 13:41:19 -03:00
Interfaces	Merge pull request #149 from Sea-Haven-Industries/feat/ab/sh-292-notification-center	2026-09-18 22:54:54 +00: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