At the moment we deliberately don't point the downloads page just to the "latest" image, because it makes sense to do at least some basic testing before throwing out an image as default download. And in that case, the page may just as well point at the latest image.

Having a "latest" symlink to the currently most recent directory with build artifacts makes sense to me (already on the "nice to have" list), however I don't see the point of making ISO image symlinks with a generic name. Why would we want that? Scripts could just fetch the images with some simple processing, and should check the checksums afterwards anyway. What we would get with a generic name is some more confusion about what build of PureOS was actually just downloaded, the reason why we added versioning to ISO images in the first place (they had generic names initially).

makes sense to do at least some basic testing before throwing out an image

Mea culpa. Please interpret "latest" as "latest actual release", rather that literally the very latest image we are hosting; naturally we would want to test it. How about current to avoid confusion? I will rename this issue to match and IIRC this is the noun uses by the Debian Installer team.

I don't see the point of making ISO image symlinks with a generic name. [Scripts] could just fetch the images with some simple processing

Unfortunately there are a few cases (including osinfo) that cannot do any processing as they are "just" XML files.

confusion about what build of PureOS was actually just downloaded, the reason why we added versioning to ISO images

Absolutely true. Could we solve this by using a HTTP redirect rather than a symlink?