Bug fixes
${md5}now works for images pasted from the clipboard. The token could only be resolved for attachments that already existed on disk, so a pasted screenshot fell back to a UUID. The content is now hashed directly in memory, and the resulting name is the true MD5 of the file — identical to what the same image would get when dragged in from Finder, so the two import routes agree.
Attachments requested by other plugins through FileManager.getAvailablePathForAttachment() still fall back to a UUID for ${md5}: on that route the file content does not exist yet, anywhere, at the moment the destination has to be chosen.
Full changelog: 1.6.1...1.6.2