Answer
Treat this as a possible known client-side defect tied to a specific upgrade rather than a data problem — this class of cosmetic-but-alarming client error (appearing after an otherwise-successful save) has been reported and tracked as a defect on more than one occasion, so check for a matching known issue at your patch level before spending time on a data investigation.