Acknowledge a Signals raw alert

Method	Path
POST	/v1/signals/raw-alerts/:alertId/ack

Shared authentication, project scope, and response conventions.

Acknowledges and resolves one individual alert. A later breaching reading can create another alert. Unlike episode acknowledgement, this route works when episodicAlerts is off.

Requirement or result	Details
Access policy	signals_alerts:update and Patient update
Caller profile	A person profile is required and recorded as acknowledgedActor.
Request	No body. :alertId is the Signals alert id.
Success	200 with the updated raw alert and noteCount: null.
Idempotency	A previously acknowledged alert remains acknowledged; Ovok records the repeated call and returns the existing alert.

curl --request POST \
  --url 'https://api.sandbox.ovok.com/v1/signals/raw-alerts/7c2e9a4b-1f3d-4b8e-a6c5-2d9f0e1b3a7c/ack' \
  --header "Authorization: Bearer ${OVOK_TOKEN}"

Status	Meaning
403	Missing signals_alerts:update, Patient update access, or person profile.
404	Alert is missing, outside the project, or tied to an unreadable Patient.
409	Another acknowledgement for this alert is running.
503 signals_audit_failed	The audit record could not be created, so the acknowledgement was not sent. Retrying is safe.