Integrate Employer Fatigue Dashboard with Backend Fatigue Logic

[allistyre]

Summary

This push builds from the Shift Fatigue Monitoring section from PR #397 and instead integrates the Employer Fatigue Dashboard with the existing backend fatigue logic, replacing the duplicated frontend fatigue calculations identified in PR #397

Changes

• Added an employer fatigue dashboard backend endpoint.
• Removed duplicated frontend fatigue calculations
• Fixed the incorrect date/time display in the fatigue modal/card highlighted in the PR review
• Added loading, error and empty states
• Current guard fatigue assessment based on assigned/completed shifts
• Preserved the existing fatigue dashboard and the details modal whilst adding a Warnings and Current Workload section

Testing

• Normal guard displays no fatigue warning
• Fatigued guard displays a daily hour warning
• No monitored guards shows correctly
• Duplicate guard IDs are handled
• Loading state and an error state
• Date/time works and modal works and details are shown

[allistyre]

The latest main conflicts have been resolved and all CI checks have passed

[LoopyB]

Thanks Alli, this is great work and the overall approach looks solid. Thanks for your amazing effort in getting this done. The Backend is now the source of truth for fatigue calculations and the duplicated Frontend fatigue logic has been removed.

I’ve found one blocking issue before merge:

• /shifts/fatigue is currently declared after /:id, so Express may match "fatigue" as the shift ID and never reach the fatigue controller. Please could you move the static /fatigue route above /:id.

I’d also like a few focused automated tests around the new endpoint, particularly:

• route resolution;
• employer authorization/scoping;
• normal/fatigued/empty scenarios.

There are a couple of smaller non-blocking comments around the modal/date handling and formatting churn, but the core architecture is sound.

Once the route and focused tests are done, I’m happy to review again. Great work!

[LoopyB]

Thanks Alli - one merge blocker remains. Please register /shifts/fatigue before the dynamic /:id route. At present Express interprets "fatigue" as a shift ID, so the new endpoint is unreachable. A quick fix, and once that route order is corrected, let me know and I'll re-review. Thanks!

[allistyre]

Hey Lou, I've followed up on this PR request and made the changes you've wanted including the route fix, i've moved that above /:id route and I've also created a new shift.fatigue.test.js file using the admin.guards.test.js file as a reference.

The following tests that you've requested have been added: employer scoping test, normal, fatigued, and empty scenarios, employer authorisation and guard authorisation.

All 6 fatigue dashboard tests pass locally as per screenshot here:

[LoopyB]

Looks good thanks - the /fatigue route-order issue is fixed, CI is green, and the focused fatigue tests pass 6/6. Approved.