Decide a proposed pay reduction.

THE POINT OF THIS ENDPOINT: the algorithm never applies a pay cut on its own. It computes a multiplier, and a row it wants to pay below the posted rate is held until a person acts here. An automated reduction and a proposed reduction a human approves are materially different objects, legally and ethically, and this route is the difference between them.

pay_full_rate overrides the proposal and pays the posted rate, because the person deciding is allowed to disagree with the model. Either way the decision is attributed and timestamped: reducing a physician's pay is consequential and an unattributable reduction cannot be appealed.

Releasing does not itself approve the row. It removes the hold, and the normal ledger rules (a verdict, or the auto-approve window) then apply, so this endpoint decides ONE question and does not quietly decide others.