Dismiss a model deprecation finding
Suppresses a finding at its current urgency band. It reopens automatically — exactly once, and notifies again — the next time the daily scan finds the band has tightened (90 → 30 → 7 days, or into retired). A band that widens, which only happens when a feed correction pushes the retirement date further out, never reopens a dismissal.
Authenticated with a dashboard session (browser cookie), not x-api-key, and requires the alerts:manage permission — dismissing a finding is the same shape of decision as editing an alert rule.
Body
Required. A dismissal with no stated reason is exactly what a later reviewer needs and can't reconstruct.
1 - 500Response
The updated, now-dismissed finding.
One (project, model) deprecation finding. callVolume30d, cost30dUsd, successorCallVolume30d, and costDeltaPerCallUsd are all measured from real ClickHouse trace data over the trailing 30 days — never estimated, and never a quality or regression figure.

