Replace Limits at the Inspected Version

Context

Two managers must be able to detect a conflicting configuration edit without losing each other’s work.

Decision

Submit complete editable limits with the inspected version, reject stale changed values and treat matching existing values as an unchanged replay.

Alternatives Considered

Save isolated fields without a complete intended state: It makes the intended replacement harder to inspect; this service instead uses a full value set.

Use last-writer-wins saves: It can silently replace another manager’s changes.

Consequences

A matching existing row returns unchanged without another audit or version increment. Omitted optional cap and note select their replacement defaults. The future editor must submit the displayed version and complete editable values. Identical competing first inserts can still conflict before an existing row is available for replay comparison.