uninstall.sh --purge again removes the database copies older releases kept beside a linked database. When data.db_file is a link, a restore made by a release before 3.4.149 kept its safety copy of the database (<name>.bak.<date>.pre-restore) next to the link, not next to the file it points to. 3.4.159 taught purge to follow the link, and in doing so it stopped looking beside the link, so those older copies were left behind. Purge now removes them too, along with everything 3.4.159 already removes. Nothing else changes: without --purge you're still asked first, and --keep still keeps everything.
Six unused screenshots are gone from the docs. They showed pages from much older versions and nothing linked to them. Every image under docs/ is now made by scripts/screenshots.py from invented data.
Operational notes
This is an ordinary update with a normal restart and no database change.
Behind the scenes
In uninstall.sh, a linked db_file adds the link and <link>.bak.*.pre-restore to the database's delete set (_LINK_SIDE), next to the real file's set. A new test covers it and fails on 3.4.159. The daily-summary state needed no such care: it has always been written beside the real file. scripts/reviewed-doc-images.sha256 is now empty, but the image gate still requires any hand-made image under docs/ to be listed there with its reviewed sha256. Its test now reviews a fixture image of its own.