Ambiguous duplicate‑key resolution when applying JSON Merge Patch
Goal: determine how a JSON Merge Patch should handle duplicate member names in the target document during a zero‑downtime format migration of a small application. Constraint: RFC 7386 leaves the behavior undefined when the target contains duplicate keys, and popular libraries (Jackson, Gson, json‑cpp) may keep the last occurrence but this is not guaranteed a
json