v3.27.2

• dsh: a resumed session no longer re-reads every image in its history (#122). Paste evidence lived only in memory, so after dsh restarted or resumed a session, the first request sent every image in the history back through the engine one by one, and a history of 20 images froze the session for minutes. Each successful reading is now kept in ~/.modlens/dsh-evidence/ and a restarted plugin answers from there. The session log is untouched. Only attachments whose id is the sha256 of their bytes are kept, so an entry can never answer for a different picture, and the original file name is not stored. Entries are tied to the engine in ~/.modlens/config.json, so switching provider or model reads the images again. The directory is 0700 and its files 0600. Entries unread for 30 days are removed, the store is capped at 64 MB with the least recently read going first, and deleting the directory is always safe. The engine still reads one image at a time: running several at once could trip a rate limit that cools the API key for every harness sharing it. Thanks to @cutefelix.