Pay Cat Connect Changelog

Added GET /v1/business/{businessId}/list/awards to list installed KeyPay awards with their current status and, for updateable awards, whether the current date is before, inside, or after the first full business pay period on or after the award latestVersionDate. They are returned with a user-facing status message and a recommendUpdate flag to guide the user on whether to submit an award update request.

Live-file employee sync now imports employees from the lightweight KeyPay employee details report instead of the full employee listing endpoint, while preserving employment-agreement derivation and imported tag handling.
Live-file employee reads and costing requests now auto-refresh the KeyPay employee snapshot when it is missing or stale, instead of returning a sync-required conflict error.
POST /v1/business/{businessId}/awards/update can now be called without an awardName to automatically queue all updateable awards where timing is appropriate.

POST /v1/business/create and POST /v1/business/connect now reject business credentials so only CRM/admin callers can create or connect businesses, preventing newly created businesses from inheriting another business's name as crmName.
PATCH /v1/crms/{clientId} is now admin-only so CRM tenants cannot rename their own CRM records.

To support changes to the treatment of sleepovers in SCHADS, new fields have been added to the employee model:
- sleepoverSettings (optional object) with hasAgreedToWorkExtendedShifts (boolean) and grandfatheredShiftPenalties (boolean) properties.
- hasAgreedToWorkExtendedShifts indicates whether the employee has agreed to work extended shifts adjoining sleepovers, which affects overtime calculations under SCHADS.
- grandfatheredShiftPenalties if true, an employee will receive night shift penalty for all work attached to a sleepover (excluding where a higher penalty applies). If false, the sections before and after a sleepover are assessed individually.

GET /v1/business/{businessId}/list/tags now returns tag objects with name and award instead of plain tag-name strings.
GET /v1/business/{businessId}/employees now returns employees reshaped back into the front-facing CostingEmployee contract instead of the previous minimal summary payload.

Employee validation now accepts classificationOverride together with schadsSector, and employment agreement lookup continues to prefer the explicit classification override when both are present.
Employee email and business contactEmail inputs are now trimmed before validation/persistence to allow for accidental leading/trailing whitespace without causing validation failures.

Added POST /v1/business/{businessId}/awards/update to submit KeyPay award update jobs on non-live businesses using a user-supplied awardName, including specific handling for KeyPay award-update throttling so requests return a clear retryable error when KeyPay responds with 400 and "A maximum of 2 running award installations is allowed" (work in progress while broader award-update flows are being implemented).

Business API responses now include keypayBusinessId and crmName.
Updated the static pay category label definitions used for costing explanation labels.