AnomalyDeviceOut

One entry in the GET /devices/anomaly-status response (Phase 132-01 / DASH-02).

id is the Device.id UUID (the primary key used across the device API), NOT the client-generated device_id string. This matches the rest of the device API surface (DeviceOut.id, /devices/{device_id} route, etc.).

anomalies is a non-empty subset of ["overdue", "stuck"], ordered with "overdue" first when both are present (severity ordering per 132-CONTEXT.md DASH-01).

idstring<uuid>required

anomaliesstring[]required

AnomalyDeviceOut

{
  "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
  "anomalies": [
    "string"
  ]
}