USR369 deleted the 08/24/26 workout in-app; the id was correctly tombstoned but its raw storage slot got overwritten with a duplicate of the separate 08/22/26 session's content instead of cleanly clearing. Recovered the true 08/24 content from a pre-deletion fetch captured earlier the same session and wrote it back as a new record (fresh id) rather than reuse the corrupted/tombstoned slot. Root cause not fully diagnosed, likely same family as K360 (id-reuse/draft-collision), not chased further per USR369's specific ask (restore only).