USR369 deleted the 08/24/26 workout (DLM-082426-025, id 1787532373855) from the Gym Logger HTML app. On inspection, the id was correctly added to the __tombstone_DLM__ deleted_ids list, but the SAME id's raw storage slot had also been overwritten with content matching the separate legitimate 08/22/26 session (id 1787417417563, code DLM-082226-024) -- a duplicate-content overwrite, not a clean delete. Root cause not fully diagnosed (likely an id-reuse/draft-collision pattern in the same family as K360), left as a finding, not chased further per USR369's specific ask (restore only). Recovered the full original 08/24 record (4 exercises, cardio warmup/main/cooldown, sauna 11:51-12:18, swimming 12:19-13:05 5-stroke breakdown, stretching 10:30-10:55) from a pre-deletion fetch captured earlier this same session (before the app-side deletion happened), and wrote it back as a NEW session record (fresh id 1788023671627, same code label DLM-082426-025 for continuity) rather than reusing the tombstoned/corrupted id 1787532373855, since that id will be filtered out on next Sync regardless of its content. Left the corrupted/tombstoned slot (1787532373855, now holding duplicate 08/22 content) untouched -- it is already correctly marked for deletion and removing it further was outside scope of what was asked.