Diary and Photos keep their photos as records of the account's entity data
(Daochi docs/entity-data.md): entity.photos.<sha256>, synced as
private.entity.v1.photos in Inbe's own signed v6 sync and sealed in Daochi's
record profile with the account's photos key, the same bytes libsodium writes.
A photo's bytes travel as sealed chunks of at most 8 MiB at
/api/v1/blobs/entity/, so the same picture is stored once per node for every
app of the account.
Photos released versions kept move there by themselves: library photos once
their bytes are on the device, and Diary files that an entry includes, named
and dated as before. An old copy goes only after the sync node confirmed the
photo's record and chunks and they came back whole; then the old records name
the photo and keep every field for released versions, which read them through
2027-10-24, the Diary file leaves the device, hex chunks shrink, and the old
copies are deleted from each node. Any failure keeps the old copy for a later
pass, and a delegate device moves nothing.